METHODS FOR ENCOURAGING SPATIAL MAPPING SERVICES

Abstract

The invention relates to systems and methods for providing spatial mapping services. A spatial mapping server can generate, based on a first request from one or more of the first VAL servers or first VAL clients, a spatial map of the area of ​​interest and including one or more required layers of spatial map information. A spatial mapping server can receive, from one or more of the second VAL servers or second VAL clients, a second request for a spatial map conforming to spatial map discovery criteria. A spatial mapping server can send, to one or more second VAL servers or second VAL clients and respond with permission to spatial map discovery, a response to one or more second VAL servers or second VAL clients including an indicator of the spatial map.

Description

METHODS TO ENABLE SPATIAL MAPPING SERVICESCROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Patent Application Number 63 / 591,663, filed on October 19, 2023.BACKGROUND

[0002] Emerging technologies, for example augmented reality (AR) and virtual reality (VR) may enhance user experience by immersing users with a surrounding environment, whether physical or virtual. A user may receive access to information to enrich an augmented reality experience or to be totally immersed with a virtual reality experience. Spatial anchors may play an important role in both AR and VR technologies and may enable users to interact with the augmented or virtual worlds more effectively. Spatial anchors may connect locations in a VR or an AR environment with digital content. Spatial anchors may be anchored to physical locations, for example store fronts on a city street. Spatial anchors may be rendered and viewed on a personal device, for example smart phones, watches or glasses as a user walks down a city street. The spatial anchors may be anchored to a location within a spatial map.SUMMARY

[0003] 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. Furthermore, the claimed subject matter is not limited to limitations that solve any or all disadvantages noted in any part of this disclosure.

[0004] To address the objectives herein, the present disclosure defines methods and procedures to enhance a system, for example a 3 GPP system, with spatial mapping services. The spatial mapping services may comprise a spatial mapping server to interact with vertical application layer (VAL) servers and VAL clients, determine spatial anchors, build spatial maps, update spatial anchors and spatial maps, and the like.BRIEF DESCRIPTION OF THE DRAWINGS

[0005] Figure 1 shows an example system.

[0006] Figure 2 shows an example system.

[0007] Figure 3 shows an example system.

[0008] Figure 4 shows an example system.

[0009] Figure 5 shows an example system.

[0010] Figure 6 shows an example method.

[0011] Figure 7 shows an example method.

[0012] Figure 8 shows an example method.

[0013] Figure 9 shows an example method.

[0014] Figure 10 shows an example method.

[0015] Figure 11 shows an example method.

[0016] Figure 12 shows an example method.

[0017] Figure 13 shows an example method.

[0018] Figure 14 shows an example method.

[0019] Figure 15 shows an example method.

[0020] Figure 16 shows an example method.

[0021] Figure 17 shows an example method.

[0022] Figure 18 shows an example method.

[0023] Figure 19 shows an example method.

[0024] Figure 20 shows an example method.

[0025] Figure 21 shows an example system.

[0026] Figure 22A shows an example communications system.

[0027] Figure 22B shows an example apparatus configured for wireless communications.

[0028] Figure 22C shows an example system.

[0029] Figure 22D shows an example system.

[0030] Figure 22E shows an example system.

[0031] Figure 22F shows an example system.

[0032] Figure 22G shows an example system.DETAILED DESCRIPTION

[0033] Methods and apparatuses are described herein for enabling spatial mapping services.

[0034] The following abbreviations may be used herein:

[0035] Emerging technologies, for example augmented reality (AR) and virtual reality (VR), may enhance user experience by immersing users with the users’ surrounding environments, whether physical or virtual. A user may receive access to information to enrich an augmented reality experience or to be totally immersed with a virtual reality experience. Spatial anchors may play an important role in both AR and VR technologies and enable users to interact with the augmented or virtual worlds more effectively.

[0036] Spatial anchors may connect locations in a virtual (VR) and / or real-world (AR) environment with digital content. For example, Figure 1 shows spatial anchors in a real-world AR example . In this example, spatial anchors are anchored to the locations of store fronts on a city street. Each spatial anchor also has associated digital content (e.g., type of location, icon, rating, distance away). These spatial anchors are used to attract potential customers into the stores and guide them to products which meet their personalized shopping preferences (e.g.,personalized advertisements and discounts on products they typically buy). Spatial anchors may be rendered and viewed on personal device such as smart phones, watches or glasses as a user walks down a city street.

[0037] In order for spatial anchors to have purpose and provide value, they must be anchored to a location within a spatial map. For example, in Figure 1 each of the spatial anchors are anchored to the location of a storefront. For outdoor navigation examples like this one, the spatial map may be based on Global Positioning System (GPS) coordinates. Each spatial anchor may have an associated latitude and longitude coordinates of the location they are anchored to. In doing so, the coordinates enable outdoor spatial anchors to be easily integrated with personal navigation systems supporting GPS based maps of streets and points of interest such as businesses and landmarks.

[0038] In contrast, for indoor examples such as the shopping example shown in Figure 2, the use of GPS based maps may not be an option due to the lack of satellite coverage indoors. In addition, for both indoor and outdoor examples, GPS has limitations regarding location precision (several meters). Instead, other types of location technologies (e.g. WiFi and / or 3GPP positioning and ranging) coupled with indoor mapping and localization services may be required. For example, mapping of indoor spaces has a unique set of challenges compared to mapping of outdoor spaces. Unlike streets and landmarks, many indoor spaces have an increased likelihood and frequency of changes. For example, it is not uncommon for the layout of aisles, shelves and merchandise within a store to change on a frequent basis. As a result, frequent remapping of the sales floor of the store may be required. Indoor mapping technologies for these types of examples must be agile and support dynamic updating of indoor maps to support spatial anchors that may move about within a spatial map.

[0039] 3GPP systems currently lacks services to assist VAL servers and VAL clients with the creation and management of spatial maps. Some examples of spatial mapping capabilities currently lacking are the following:

[0040] 1) Capability to receive requests from VAL servers and / or VAL clients to create spatial maps for specified areas of interest to the VAL servers and / or VAL clients,

[0041] 2) Capability to determine spatial anchors residing within these specified areas of interest (e.g., spatial anchors anchored to objects within the area of interest),

[0042] 3) Capability to build a spatial map comprising the spatial anchors residing within a specified area of interest and their relative position and orientation with respect to one another,

[0043] 4) Capability to keep a spatial map updated if / when changes in position and / or orientation occur for the spatial anchors comprising the spatial map (e.g., spatial anchors enter, exit or move within an area of interest),

[0044] 5) Capability to enable VAL servers and / or VAL clients to securely discover spatial maps of interest,

[0045] 6) Capability to enable VAL servers and / or VAL clients to subscribe to receive updates if / when changes to spatial maps occur (e.g., layout of spatial map changes due to movement of objects / spatial anchors).

[0046] To address the aforementioned shortcomings, this disclosure defines methods and procedures to enhance a 3GPP system with spatial mapping services. The following is a summary of proposed capabilities of the spatial mapping services.

[0047] A spatial mapping server capable of:

[0048] 1) Receiving a request from a VAL server or spatial mapping client to create a spatial map for a specified area of interest to the VAL server or to VAL clients interfacing to the spatial mapping server via the spatial mapping client, wherein the request may comprise one or more of the information elements defined in Table 1 (e.g., a required spatial map boundary or spatial map precision),

[0049] 2) Determining a set of spatial anchors residing within the specified areas of interest based on information provided in the request and / or by interfacing with other entities in the system such as a spatial anchor server, location management server, group management server, and / or 3 GPP core network,

[0050] 3) Sending one or more requests to a spatial anchor server, location management server, group management server, and / or 3GPP core network comprising information regarding an area of interest such as a boundary or perimeter of the area, and in response receiving information regarding a set of a spatial anchors located within the specified area of interest,

[0051] 4) Generating a spatial map based on the determined set of spatial anchors residing within a specified area of interest and their relative position and orientation with respect to one another,

[0052] 5) Tracking the relative position and orientation of the set of spatial anchors of the spatial map by subscribing to receive updated positioning and orientation information for each of the spatial anchors from one or more entities in the system such as a spatial anchor server, location management server, group management server, and / or 3GPP core network

[0053] 6) Determining the relative position and orientation of the set of spatial anchors by comparing the position and orientation of each spatial anchor against the position and orientation of the other spatial anchors in the spatial map to compute relative positions and orientations between all of the spatial anchors,

[0054] 7) Determining if / when changes in position and / or orientation occur for the spatial anchors within the spatial map (e.g., spatial anchors enter, exit or move within an area of interest) and keeping the spatial map updated by recomputing the relative positions and orientations between all of the spatial anchors,

[0055] 8) Receiving a request from a VAL server and / or spatial mapping client to securely discover and retrieve a spatial map, determining if the requestor is permitted access the spatial map, and responding with spatial map information if permitted, wherein the response comprises spatial map(s) matching criteria specified by the requestor (e.g., a spatial map for a specified area of interest, or supported level of positioning or orientation precision)

[0056] 9) Receiving a request from a VAL server and / or spatial mapping client to subscribe to receive updates if / when changes to a spatial map occurs (e.g., layout of spatial map changes due to movement of objects / spatial anchors), detecting changes of interest in the spatial map, and sending a notification to the subscriber comprising updated spatial map information.

[0057] The following is a summary of certain features targeting a spatial mapping client as defined herein:

[0058] 1) Receiving a request from a VAL client to create a spatial map for a specified area of interest to the VAL client, wherein the request may comprise one or more of the information elements defined in Table 1 (e.g., a required spatial map boundary or spatial map precision,

[0059] 2) Sending a request to a spatial mapping server to create a spatial map based on the request received from the VAL client,

[0060] 3) Receiving a response from the spatial mapping server comprising spatial map information such as information elements defined in Table 1,

[0061] 4) Determining whether to store spatial map information returned in the response locally at the spatial mapping client such that the information may be used for future spatial map related requests from VAL clients,

[0062] 5) Sending a spatial map to a VAL client indicating a created spatial map,

[0063] 6) Subscribing to a spatial mapping server to receive spatial map updates, receiving a notification comprising a spatial map update from the spatial mapping server, and updating the locally stored spatial map to keep the local spatial map synchronized with the spatial map stored in the network,

[0064] 7) Receiving a request comprising spatial anchor information from a VAL client to update a spatial map, updating the spatial map stored locally at the spatial mapping client, and sending a spatial map update request to a spatial mapping server to keep the spatial map stored in the network synchronized with the spatial map stored locally

[0065] Figure 3 describes a proposed architecture for supporting spatial mapping services within the context of a 3GPP system. The architecture may support spatial mapping client(s) and server(s). A spatial mapping server may be accessed by one or more VAL servers to create and offload the management of VAL server defined spatial maps to the spatial mapping server. The spatial mapping server may also be accessed by a spatial mapping client on behalf of VAL clients which interface to the spatial mapping server. To generate and maintain spatial maps, the spatial mapping server may interface to other functions and services in a 3GPP system such as but not limited to those shown in Figure 3. For example, one or more of the interfaces shown in Figure 3 and described below may be supported by spatial mapping clients and servers.

[0066] 1) Interface A between spatial mapping server and VAL server(s)

[0067] 2) Interface B between spatial mapping server and spatial anchor server(s)

[0068] 3) Interface C between spatial mapping server and spatial mapping client(s)

[0069] 4) Interface D between spatial mapping server and 3 GPP core network(s)

[0070] 5) Interface E between spatial mapping server and group management server(s)

[0071] 6) Interface F between spatial mapping server and location management server(s)

[0072] 7) Interface G between spatial mapping server and other spatial mapping server(s)

[0073] 8) Interface H between spatial mapping client and VAL client(s)

[0074] 9) Interface I between spatial mapping client and spatial anchor client(s)

[0075] 10) Interface J between spatial mapping client and location management client(s)

[0076] 11) Interface K between spatial mapping client and group management client(s)

[0077] Via the above interfaces the spatial mapping client and server may support one or more of the features defined herein. One or more of the interfaces defined above may be mapped to existing interfaces defined in a 3GPP system. These existing interfaces may be enhanced with one or more of the features defined herein.

[0078] Note, one skilled in the art may recognize that the architecture shown in Figure 3 is not intended to limit or exclude other possible architectural options for supporting spatial mapping services within a 3GPP system. For example, alternatively the spatial mapping functionality may be realized as features of other services within a 3GPP system such as but not limited to an XR, metaverse, or location management service in a 3GPP system.

[0079] Note that the spatial mapping services shown in Figure 3 and described herein may also be deployed by a cloud service provider offering spatial mapping services which may or may not communicate with a 3 GPP network. The cloud service provider, serving as spatial mapping servers, may expose API’s for VAL clients to access the spatial map services described herein.

[0080] Note, one skilled in the art may also recognize that the term client and server referenced throughout this disclosure may, for example be realized as software deployed on one or more network apparatuses comprising processor(s), memory, and network interface(s). The apparatuses may be deployed as cloud apparatuses, edge apparatuses, or device apparatuses. One or more servers and / or clients of the same or different type may be deployed on a single apparatus. A single server or client may be split and deployed across multiple apparatuses. The functionality of one type of server or client may be combined or consolidated with the functionality of another type of server or client and deployed together with one another on one or more apparatuses

[0081] Table 1 defines spatial mapping context information that may be transmitted, received, stored, updated, processed, and / or generated by various entities in a 3GPP system such as but not limited to a spatial mapping client or server, location management client or server, group management client or server, and / or a 3GPP core network. One skilled in the art may recognize that spatial mapping context information may be comprised of additional information elements not captured in Table 1. Note that the spatial mapping context information may also be used in a cloud service platform between spatial mapping clients or servers.Table 1 - Spatial Mapping Context Information

[0082] The spatial mapping server and / or client may perform one or more of the following spatial mapping operations to create and maintain a spatial map. These spatial mapping operations may leverage spatial mapping context information such as but not limited to the information defined in Table 1 that the spatial mapping server or client stores and maintain locally or receives from other entities in the system as described in the aforementioned methods.

[0083] The spatial mapping server and / or client may determine a group of one or more spatial anchors within the location, area of interest, and / or boundary of a spatial map. The spatial anchors may be associated with objects and / or features of a spatial map. For example, Figure 4 shows a spatial map of a room. Within the room, spatial anchors may be anchored to walls, doors, windows, and / or furniture. A spatial mapping server and / or client may create and managea spatial map comprising the group of one or more spatial anchors and their associated objects and features they are anchored to.

[0084] The spatial mapping server and / or client may determine relationships between spatial anchors within the location, area of interest, and / or boundary of a spatial map. A relationship may be spatial in nature. For example, spatial anchors within a certain location, range, and / or orientation with respect to one another. A relationship may also be based on a certain object or feature. For example, spatial anchors anchored to the same object but different points of the object (e.g., a piece of furniture within a room). For example, Figure 5 shows relationships between spatial anchors within a spatial map of a room. Relationships are shown between spatial anchors of a common object (e.g., a desk) as well as between the object and the walls within the room. Based on these relationships, the spatial mapping server and / or client may create and manage a spatial map comprising the group of one or more spatial anchors and their associated objects and features they are anchored to, and their relationships between one another. If / when an object / feature of the room is changed (e.g., desk is repositioned in the room), the spatial mapping server and / or client, may update the spatial map. The updating of the spatial map may involve updating attributes of individual spatial anchors (e.g., their position and orientation) as well as relationships between spatial anchors.

[0085] Figure 6 provides an overview of the different types of spatial mapping methods proposed herein. For each of the methods defined in Figure 6, separate detailed descriptions are defined herein. Note, the separate methods may be sequenced and performed in an order different than the order shown in Figure 6.

[0086] Step 1 : A spatial map may be created and / or updated by a spatial mapping server and / or client. This operation may be initiated by a VAL server or client. For example, a VAL server or client may send a request to a spatial mapping server or client. The request may comprise information and / or policies which may be used by the spatial mapping server or client to create or update the spatial map. To create or update a spatial map, the spatial mapping server and / or client may perform one or more operations based on the information and / or policies. For example, the spatial mapping server and / or client may determine a boundary / perimeter of a spatial map, a group of one or more spatial anchors residing within this boundary, and the position and orientation of these spatial anchors with respect to one another. In turn, the spatial mapping server and / or client may create and / or update a spatial map. The spatial mapping serverand client may also interact with one or more other entities in the system such as but not limited to those shown in Figure 6 when creating and / or updating spatial maps.

[0087] Step 2: A spatial may be discovered and / or retrieved via the spatial mapping server and / or client. This operation may be initiated by a VAL server or client sending a discovery and / or retrieve request to a spatial mapping server and / or client. This request may comprise spatial map query conditions. The conditions may comprise names of spatial map information elements and their values that are of interest to a VAL server or client. For example, one or more of the information elements defined in Table 1. Based on the request, a spatial mapping server and / or client, may determine whether a spatial map exists which satisfies the request, and if so, return information about this spatial map to the VAL server or client. During this retrieve and / or discovery operation, the spatial mapping server and / or client may interact with other services and functions in the system such as but not limited to those shown in Figure 6.

[0088] Step 3: A subscription to a spatial map may be made via the spatial mapping server and / or client. This operation may be initiated by a VAL server or client sending a spatial map subscription request to a spatial mapping server and / or client. This request may comprise spatial map notification criteria. The notification criteria may comprise names of spatial map information elements and their values that are of interest to a VAL server or client. For example, one or more of the information elements defined in Table 1. Based on the request, a spatial mapping server and / or client, may monitor and detect if / when the spatial map notification criteria have been met, and in turn send spatial map notifications to a VAL server and / or client. While processing spatial map subscriptions, monitoring spatial map notification criteria, and / or generating spatial map notifications, the spatial mapping server and / or client may interact with other services and functions in the system such as but not limited to those shown in Figure 6.

[0089] Step 4: A subscription to a spatial map may be cancelled via the spatial mapping server and / or client. This operation may be initiated by a VAL server or client sending a spatial map unsubscribe request to a spatial mapping server and / or client. This request may comprise an identifier of one or more spatial map subscriptions. Upon receiving the request, the spatial mapping server and / client may delete the subscription(s), stop monitoring the spatial map notification criteria, and discontinue sending spatial map notifications associated with the subscription(s). While processing a spatial map unsubscribe request, the spatial mapping serverand / or client may interact with other services and functions in the system such as but not limited to those shown in Figure 6.

[0090] Step 5: A spatial map may be deleted. This operation may be initiated by a VAL server or client sending a spatial map delete request to a spatial mapping server and / or client. This request may comprise an identifier and / or one or more deletion criteria of one or more spatial maps to be deleted. Upon receiving the request, the spatial mapping server and / client may delete the spatial map based on the information provided in the request. While processing a spatial map delete request, the spatial mapping server and / or client may interact with other services and functions in the system such as but not limited to those shown in Figure 6.

[0091] Systems and methods are presented herein for enabling spatial mapping services. For example, the method described in Figure 6 generally, and the examples in Figures 7-20 may describe examples of preparing spatial maps, providing spatial maps to requesting devices in spatial map discovery operations, subscribing and unsubscribing users to spatial maps, and deleting spatial maps. The methods described herein may comprise receiving, by a spatial mapping server and from at least one of a first vertical application layer (VAL) server or a first spatial mapping client, a first request to create a spatial map, wherein the first request comprises an area of interest, an access control policy associated with the spatial map, and one or more requested layers of information associated with the spatial map. The method may comprise creating, based on the first request, the spatial map for the area of interest comprising the one or more requested layers of spatial map information. The method may further comprise generating a spatial map identifier associated with the spatial map. The method may further comprise sending a response to the at least one first VAL server or first spatial mapping client, the response comprising the spatial map identifier and an indication of at least one of a successful creation of the spatial map or a failure to create the spatial map. The method may further comprise receiving, from at least one of a second VAL server or a second spatial mapping client, a second request, wherein the second request comprises spatial map discovery criteria and an identifier of at least one of the second VAL server or the second spatial mapping client. The method may further comprise determining, based on the access control policy associated with the spatial map and the identifier of the at least one of the second VAL server or the second spatial mapping client, at least one of a permission to discover the spatial map or a denial of discovery of the spatial map. The method may further comprise determining the spatial map matches the spatialmap discovery criteria. The method may further comprise sending, to the at least one of the second VAL server or the second spatial mapping client, a second response comprising an indication of the spatial map.

[0092] The method described in Figure 6 may further comprise wherein the spatial map discovery criteria comprises an area of interest.

[0093] The method described in Figure 6 may further comprise wherein the indication of the spatial map comprises the spatial map identifier.

[0094] The method described in Figure 6 may further comprise wherein the creating the spatial map further comprises determining one or more spatial anchors associated with the spatial map.

[0095] The method described in Figure 6 may further comprise sending, to a spatial anchor server, a request comprising spatial map information associated with the spatial map, and receiving, from the spatial anchor server, a response comprising one or more spatial anchors associated with the spatial map.

[0096] The method described in Figure 6 may further comprise wherein each one of the one or more spatial anchors associated with the spatial map comprise a spatial anchor identifier.

[0097] The method described in Figure 6 may further comprise wherein each one of the one or more spatial anchors associated with the spatial map is associated with a location in the spatial map.

[0098] The method described in Figure 6 may further comprise receiving, from a user device associated with the second spatial mapping client, a subscription request associated with the spatial map. The method may further comprise sending, to the user device and in response to the subscription request, subscription information associated with the spatial map. The method may further comprise sending, to the user device, one or more notifications associated with the spatial map.

[0099] For example, the system described in Figure 6 may comprise an apparatus comprising a processor and a memory, the apparatus further comprising computer-executable instructions stored in the memory of the apparatus which, when executed by the processor of the apparatus, cause the apparatus to perform operations. The operations may comprise sending, to a spatial mapping server and by a spatial mapping client of the apparatus, a first request to create a spatial map, wherein the first request comprises an area of interest, an access control policyassociated with the spatial map, and one or more requested layers of information associated with the spatial map. The operations may further comprise receiving a response from the spatial mapping server, the response comprising an identifier associated with the spatial map and an indication of at least one of a successful creation of the spatial map or an indication of a failure to create the spatial map. The operations may further comprise sending, to the spatial mapping server, a second request, wherein the second request comprises spatial map discovery criteria and an identifier of the spatial mapping client of the apparatus. The operations may further comprise receiving, from the spatial mapping server and based on the spatial map discovery criteria, a second response comprising an indication of the spatial map.

[0100] The system described in Figure 6 may further comprise wherein the spatial map discovery criteria comprises an area of interest.

[0101] The system described in Figure 6 may further comprise wherein the receiving the second response comprises receiving an identifier of a second spatial map matching the spatial map discovery criteria.

[0102] The system described in Figure 6 may further comprise wherein the first request to create the spatial map comprises a request to associate one or more spatial anchors with the spatial map.

[0103] The system described in Figure 6 may further comprise wherein the one or more spatial anchors associated with the spatial map each correspond to a location in the spatial map.

[0104] The system described in Figure 6 may further comprise operations of sending, to the spatial mapping server, a subscription request associated with the spatial map, receiving subscription information associated with the spatial map, subscribing, based on the receiving the subscription information, with the spatial map, and receiving one or more notifications associated with the spatial map.

[0105] As shown in Figure 7, a VAL server may trigger the create or update of a spatial map by initiating a request to a spatial mapping server. The creation or update of a spatial map may involve the exchange of spatial mapping context information as defined in Table 1 between the VAL server and the spatial mapping server.

[0106] Step 1 : To create or update a spatial map, a VAL server may issue a spatial map create or update request to a spatial mapping server, where the request may comprise but is notlimited to one or more of the information elements defined in Table 1 . In the case of an update request, the VAL server may comprise a spatial map identifier.

[0107] Step 2: Upon receiving the spatial map create or update request, the spatial mapping server may process the request by first checking whether the VAL server originating the request has permissions to create or update the spatial map on the spatial mapping server. This check may be performed by the spatial mapping server checking that the VAL server ID specified in the request matches an ID specified in the access control privileges of the spatial mapping server. The check may also be performed by checking whether a token specified in the request matches a token known by the spatial mapping server. The check may also comprise verifying the type of spatial map operation requested is allowed and if the operation is allowed to be performed at the current time and / or from the current location that the VAL server resides. If allowed, the spatial mapping server may create or update the spatial map. When creating or updating the spatial map, the spatial mapping server may perform one or more of the following operations. These operations may be based on spatial mapping context information provided in the request, based on pre-configured spatial mapping server policies, and / or via interacting with other entities in the system such as but not limited to the entity shown in Figure 6:

[0108] a) Assign a spatial map name, ID and / or address to the spatial map if one is not already assigned and / or provided in the request,

[0109] b) Identify one or more spatial maps associated with the received request. If a spatial map is being created and a spatial map ID is not specified in the request, a new spatial map ID may be generated and assigned to the spatial map by the spatial mapping server. If the spatial map(s) is being updated by the request, the spatial mapping context information in the request may be used to update one or more information elements of the existing spatial map(s),

[0110] c) Store the created or updated spatial map locally within the spatial mapping server and / or elsewhere in the system such as but not limited to those entities shown in Figure 6,

[0111] d) Determine a location associated with the spatial map, the location may be a physical location such as GPS coordinates (e.g. for AR applications) and / or a virtual location such as a URL / URI (e.g. for VR applications),

[0112] e) Determine a perimeter or shape associated with the spatial map,

[0113] f) Determine spatial anchors within the boundary / perimeter of the spatial map, e.g. by issuing a discovery request to a spatial anchor server and specifying the boundary / perimeter in the discovery criteria,

[0114] g) Determine relationships between the spatial anchors within the boundary / perimeter of the spatial map, e.g. by issuing a position, orientation and / or ranging request to the 3 GPP core network to track the distance among spatial anchors,

[0115] h) Determine a positioning, ranging or orientation precision capability of the spatial map,

[0116] i) Determine an expiration time of the spatial map,

[0117] j) Determine an operational status of the spatial map,

[0118] k) Determine a operational schedule of the spatial map,

[0119] 1) Determine access control policies and / or access tokens of the spatial map.

[0120] Step 3 : Generate and return a spatial map create or update response to the VAL server that originated the request. Where the response may comprise but is not limited to one or more of the information elements defined in Table 1 and / or a status indication of whether the request was successfully processed or not.

[0121] As shown in Figure 8, a spatial mapping client may also create or update a spatial map by initiating a request to a spatial mapping server. The creation or update of a spatial map may involve the exchange of spatial mapping context information as defined in Table 1 between the spatial mapping client and the spatial mapping server. The spatial mapping client may be triggered to generate this request when receiving a request from another entity on a UE such as one or more VAL clients hosted on the UE or on another UE or device.

[0122] Step 1 : To create or update a spatial map, a VAL client may issue a spatial map create or update request to a spatial mapping client. The request may comprise but is not limited to one or more of the information elements defined in Table 1. In the case of an update request, a VAL client may provide a spatial map identifier of an existing spatial map.

[0123] Step 2: Upon receiving a spatial map create or update request, the spatial mapping client may process the request by first checking whether a VAL client originating the request has permissions to create or update a spatial map. This check may be performed by the spatial mapping client checking that the VAL client ID specified in a request matches an ID specified in the access control privileges associated with the spatial mapping client and / or a specific spatialmap. The check may also be performed by checking whether a token specified in the request matches a token configured / pre-configured in the spatial mapping client. The check may also comprise verifying a type of spatial map operation being performed is allowed as well as if the operation is allowed to be performed for a current time and / or from a current location that the VAL client resides. The spatial mapping client may also interact with other entities in the system to perform these checks (e.g., a spatial mapping server and / or security server in the system). If allowed, the spatial mapping client may trigger a spatial map update or create operation to the spatial mapping server.

[0124] Step 3: The operations may be performed locally and independently by the spatial mapping client. Alternatively, the spatial mapping client may send a spatial map create or update request to a spatial mapping server. The request may comprise but is not limited to one or more of the information elements defined in Table 1. These information elements may be the same information elements provided in the request(s) which the spatial mapping client receives from VAL client(s). A spatial mapping client may also provide additional information elements not received from VAL clients. For example, a spatial mapping client may add additional spatial mapping client specific information and / or information based on local spatial map operations the spatial mapping client performs. In addition, the spatial mapping client may be configured with one or more policies used to determine the information the spatial mapping client provides in requests the spatial mapping client sends to the spatial mapping server.

[0125] Step 4: Upon receiving the request from the spatial mapping client, the spatial mapping server processes the request. The processing may comprise similar aforementioned operations as defined when the spatial mapping server receives a spatial map create or update request from a VAL server. However, rather than authorizing the VAL server, the spatial mapping server may instead authorize the spatial mapping client and / or one or more VAL clients to perform the spatial map request. A spatial mapping server may interact with one or more VAL servers when processing the request from the spatial mapping client. For example, the VAL client, spatial mapping client, and / or spatial mapping server may not have all the information needed for creating the spatial map. In this case, the spatial mapping server may send request(s) to one or more VAL servers to get the needed information, and create a spatial map based on this information as well as the information made available by the VAL client, spatial mapping client and / or spatial mapping server.

[0126] Step 5: The spatial mapping server may return a response to the spatial mapping client. The response may comprise one or more spatial map information elements such as but not limited to those defined in Table 1. In addition, the spatial mapping server may comprise a status indication of whether the request was successfully processed or not.

[0127] Step 6: Upon receiving the response, the spatial mapping client may determine whether the spatial map was successfully created or updated by the spatial mapping server. If successful, the spatial mapping client may store a local copy of the spatial mapping context information returned in the response. The spatial mapping client may use this locally stored information to service future spatial map requests from VAL clients. To keep this local spatial map information up-to-date and in sync with the spatial mapping context information stored elsewhere in the system, the spatial mapping client may subscribe to receive spatial map updates from the spatial mapping server (not shown in Figure 8). Alternatively, the spatial mapping client may initiate spatial map retrieve requests from the spatial mapping server (also not shown in Figure 8). These retrieve requests may be scheduled by the spatial mapping client. For example, the spatial mapping client may retrieve and update locally stored spatial mapping context information periodically, based on a schedule, or based on a detected event. The spatial mapping client may rely on spatial map schedule information received from the spatial mapping server, local policies, and / or information received by VAL clients to determine the refresh rate or schedule and if / when to update a spatial map.

[0128] Step 7: The spatial mapping client may send one or more spatial map create or update responses to VAL client(s). The responses may comprise information elements such as but not limited to those defined in Table 1. In addition, the spatial mapping client may comprise a status indication of whether the request was successfully processed or not.

[0129] As shown in Figure 9, one or more network entities may initiate a request to a spatial mapping server to discover and / or retrieve information regarding one or more spatial maps. Some examples of network entities may comprise a VAL server, location management server, etc.

[0130] Step 1 : A network entity may issue a request to a spatial mapping server to discover and / or retrieve information regarding one or more spatial maps. The request may comprise one or more information elements such as but not limited to those specified in Table 1. For example, the request may comprise an identifier of a specific spatial map or spatial mapdiscovery criteria. The discovery criteria may define filters specifying spatial map(s) of interest to the network entity. For example, a filter may be specified with a spatial map name, location, type or ID or interest.

[0131] Step 2: Upon receiving the request to retrieve or discover spatial maps, the targeted spatial mapping server may process the request by first checking whether the network entity originating the request has permissions to retrieve or discover spatial map(s). This check may be performed by the spatial mapping server checking that the network entity ID specified in the request matches an ID specified in the access control privileges of the spatial mapping server. The check may also be performed by checking whether a token specified in the request matches a token specified in the targets spatial map(s). The check may also comprise verifying the spatial map retrieve or discover operation being performed is allowed at the current time and / or from the current location that the network entity resides. If allowed, the spatial mapping server may process the request. When processing the request, the spatial mapping server may check whether the request comprises discovery criteria. If present, the spatial mapping server may compare the specified discovery criteria against context information within one or more spatial maps stored locally by the spatial mapping server. The spatial mapping server may also send one or more requests to other entities in the network to retrieve or discover spatial maps stored elsewhere in the network (e.g., stored within a location management server). When comparing the spatial map discovery criteria, the spatial mapping server may determine whether any spatial mapping context information matches the specified discovery criteria.

[0132] Step 3 : If one or more spatial maps are found to match the spatial map identifier and / or discovery criteria, spatial mapping context information such as but not limited to the information elements defined in Table 1 may be returned. A status indication may also be provided indicating the discovery or retrieve operations completed successfully. Otherwise, an error indication may be returned in the response indicating no spatial maps matching the specified discovery criteria were found. If / when a spatial map is not found, this may trigger the creation of a spatial map by the spatial mapping server.

[0133] As shown in Figure 10, a spatial mapping client may initiate a spatial map discovery or retrieve request to a spatial mapping server. The request may comprise the exchange of spatial mapping context information as defined in Table 1 between the spatial mapping client and the spatial mapping server. The spatial mapping client may be triggered togenerate this request via receiving a request from another entity on the UE such as one or more VAL clients hosted on the UE or on another UE or device.

[0134] Step 1 : A VAL client may issue a request to a spatial mapping client to retrieve or discover one or more spatial maps. The retrieval or discovery request may be comprised of one or more spatial mapping context information elements such as but not limited to those defined in Table 1. For example, the request may comprise spatial map discovery criteria. In the case of a retrieve request, a VAL client may provide one or more spatial map identifiers of existing spatial maps.

[0135] Step 2: Upon receiving spatial map retrieve or discovery request(s), the spatial mapping client may process the request(s) by first checking whether a VAL client originating the request has permissions to retrieve or discover a spatial map. This check may be performed by the spatial mapping client checking that the VAL client ID specified in a request matches an ID specified in the access control privileges of the spatial mapping client. The check may also be performed by checking whether a token specified in the request matches a token pre-configured in the spatial mapping client. The check may also comprise verifying retrieve or discovery of a spatial map is allowed to be performed at the current time and / or from the current location that a VAL client resides. The spatial mapping client may also interact with other entities in the system to perform these checks (e.g., a spatial mapping server and / or security server in the system). If allowed, the spatial mapping client may trigger a spatial map retrieve or discovery operation to the spatial mapping server.

[0136] Step 3 : The operations may be performed locally and independently by the spatial mapping client. Alternatively the spatial mapping client may send a spatial map retrieve or discovery request to a spatial mapping server. The request may comprise but is not limited to one or more of the information elements defined in Table 1. These information elements may be the same information elements provided in one or more requests which the spatial mapping client received from VAL client(s). A spatial mapping client may also provide additional information elements which were not receive from VAL clients. For example, a spatial mapping client may add additional spatial mapping client specific information and / or information based on local spatial map operations the spatial mapping client performs. In addition, the spatial mapping client may be configured with one or more policies which used to determine the information the spatial mapping client provides in requests sent to the spatial mapping server.

[0137] Step 4: Upon receiving the request from the spatial mapping client, the spatial mapping server may process the request. The processing may comprise similar aforementioned operations as defined when the spatial mapping server receives a spatial map retrieve or discovery request from a VAL server. However, rather than authorizing the VAL server, the spatial mapping server may instead authorize the spatial mapping client and / or one or more VAL clients to perform the spatial map retrieve or discovery request.

[0138] Step 5: The spatial mapping server may return a response to the spatial mapping client. The response may comprise one or more spatial map information elements such as but not limited to those defined in Table 1. In addition, the spatial mapping server may provide a status indication of whether the request was successfully processed or not.

[0139] Step 6: Upon receiving the response, the spatial mapping client may determine whether the spatial map was successfully retrieved or discovery by the spatial mapping server. If successful, the spatial mapping client may store a local copy of the spatial mapping context information returned in the response. The spatial mapping client may use this locally stored information to service future spatial map requests from VAL clients. To keep this local spatial map information up-to-date and in sync with the spatial mapping context information stored elsewhere in the system, the spatial mapping client may perform similar operations as described in Step 6 of the aforementioned spatial map create or update method.

[0140] Step 7: The spatial mapping client may send one or more spatial map retrieve or discovery responses to VAL client(s). The responses may comprise information elements such as but not limited to those defined in Table 1. In addition, the spatial mapping client may provide a status indication of whether the request was successfully processed or not.

[0141] As shown in Figure 11, one or more network entities may initiate a request to a spatial mapping server to subscribe to spatial map related events of interest to the VAL server which may be detected by the spatial mapping server. Some examples of network entities may comprise a VAL server, location management server, etc.

[0142] Step 1 : A network entity may issue a spatial map subscription request to a spatial mapping server. The request may comprise one or more spatial mapping context information elements such as but not limited to those defined in Table 1. For example, the request may comprise spatial map subscription criteria to changes to a spatial map such as changes to spatialanchors in the spatial map or changes in the relationships between spatial anchors in the spatial map.

[0143] In addition, the subscription operation may comprise service criteria such as: support for “confirmation” of maps, related subscribed services, etc.

[0144] Step 2: Upon receiving the spatial map subscription request, the spatial mapping server may process the request by first checking whether the network entity originating the request has permissions to subscribe to a spatial map on the spatial mapping server. This permissions check may be performed in a manner similar to the methods defined in Step 2 of the spatial map create or update method. If permissions are granted, the spatial mapping server may process the request. When processing the request, the spatial mapping server may subscribe to other entities in the system such as but not limited to those defined in Figure 6. For example, the spatial mapping server may subscribe to a spatial anchor server, 3GPP network , and / or location management server to receive location updates for spatial anchors within the spatial map.

[0145] Step 3: The spatial mapping server may send a spatial map subscription response to the network entity. The response may comprise one or more spatial mapping context information elements such as but not limited to those defined in Table 1. For example, the response may comprise an identifier of a spatial map subscription and / or a subscription expiration time. The response may also provide an indication of whether the spatial map subscription request was successfully processed or not.

[0146] Step 4: The spatial mapping server may monitor spatial map subscription criteria to determine if / when the criteria have been met. For example, the spatial mapping server may detect if / when one or more spatial anchors within the spatial map change their position or orientation and in turn if / when relationships between the spatial anchors within the spatial map change with respect to one another resulting in changes to the spatial map. If / when spatial map subscription criteria are met, the spatial mapping server may trigger the generation and sending of spatial map notifications. A spatial mapping server may send spatial map notifications to a network entity as well as other entities in the system. The spatial map notifications may comprise one or more spatial map content information elements defined in Table 1. Upon receiving the notifications, the network entity may process the spatial mapping context information within the notifications.

[0147] As shown in Figure 12, a spatial mapping client may initiate a spatial map subscription request to a spatial mapping server to subscribe to spatial map related events of interest to the spatial mapping client and / or one or more VAL clients serviced by the spatial mapping client. The request may comprise spatial mapping context information as defined in Table 1. The spatial mapping client may be triggered to generate this request via receiving a request from another entity on the UE such as one or more VAL client hosted on the UE or on another UE or device.

[0148] Step 1 : A VAL client may issue a request to a spatial mapping client to subscribe to events of interests pertaining to one or more spatial maps. The subscription request may comprise one or more spatial mapping context information elements such as but not limited to those defined in Table 1. For example, the request may comprise spatial map subscription criteria applicable to one or more spatial maps, and / or one or more spatial map identifiers of targeted spatial maps.

[0149] Step 2: Upon receiving the spatial map subscription request, the spatial mapping client may process the request by first checking whether the VAL client originating the request has permissions to subscribe to a spatial map on the spatial mapping server. This check may be performed in a similar manner to the permissions check defined in Step 2 of the spatial map create or update method. If permissions are granted, the spatial mapping client may create a subscription to a locally stored spatial map at the spatial map client. Alternatively, the spatial mapping client may trigger the sending of a spatial map subscription request to a spatial mapping server. Alternatively, the spatial mapping client may trigger a spatial map subscription request independent of a receiving a request from a VAL client. For example, the spatial mapping client may trigger a spatial map subscription request to a spatial mapping server if / when the spatial mapping client stores spatial mapping context information locally at the spatial mapping client. This subscription may be used by the spatial mapping client to receive spatial map notifications from a spatial mapping server if / when the server updates the spatial map on the server. These spatial map notifications may be used by the spatial mapping client to keep its locally stored spatial map in sync with the spatial map stored at the spatial mapping server.

[0150] Step 3: The spatial mapping client may send a spatial map subscription request to a spatial mapping server. The request may comprise but is not limited to one or more of the information elements defined in Table 1. These information elements may be the sameinformation elements provided in one or more requests which the spatial mapping client receives from VAL client(s). A spatial mapping client may also provide information elements not received from VAL clients. For example, a spatial mapping client may add additional spatial mapping client specific information and / or information based on local spatial map operations the spatial mapping client performs. In addition, the spatial mapping client may be configured with one or more policies used to determine the information the spatial mapping client provides in spatial map subscription requests sent to the spatial mapping server.

[0151] Step 4: Upon receiving the request from the spatial mapping client, the spatial mapping server processes the request. The processing may comprise similar aforementioned operations as defined when the spatial mapping server receives a spatial map retrieve or discovery request from a VAL server. However, rather than authorizing the VAL server, the spatial mapping server may instead authorize the spatial mapping client and / or one or more VAL clients to perform the spatial map subscribe request.

[0152] Step 5: The spatial mapping server may return a spatial map subscription response to the spatial mapping client. The response may comprise one or more spatial map information elements such as but not limited to those defined in Table 1. For example, a spatial map subscription identifier and / or subscription expiration time may be provided. In addition, the spatial mapping server may provide a status indication of whether the request was successfully processed or not.

[0153] Step 6: Upon receiving the response, the spatial mapping client may determine whether the spatial map subscription was successfully received and processed by the spatial mapping server. If successful, the spatial mapping client may store a local copy of the spatial map subscription information returned in the response. The spatial mapping client may store this information and use the information to manage the spatial map subscription. For example, the spatial mapping client may update spatial map subscriptions at the spatial mapping server such that they do not expire.

[0154] Step 7: The spatial mapping client may send one or more spatial map subscription responses to VAL client(s). The responses may comprise information elements such as but not limited to those defined in Table 1. In addition, the spatial mapping client may provide a status indication of whether the request was successfully processed or not.

[0155] Step 8: The spatial mapping client and / or server may monitor spatial map subscription criteria to determine if / when the criteria have been met. If / when met, the spatial mapping client and / or server may trigger the generation and sending of spatial map notifications. A spatial mapping server may send spatial map notifications to a spatial mapping client. The spatial map notifications may comprise one or more spatial map content information elements defined in Table 1. Upon receiving the notifications, the spatial mapping client may process the spatial mapping context information within the notifications. For example, the information may be used by the spatial mapping client to update a local copy of a spatial map that the spatial mapping client stores locally. The spatial mapping client may also forward spatial mapping notifications received from spatial mapping server(s) to one or more VAL clients. The spatial mapping client may also generate spatial map notifications independently of the spatial mapping server. For example, the spatial mapping client may generate notifications if / when an update is made to a spatial map stored locally by the spatial mapping client.

[0156] As shown in Figure 13, one or more network entities may initiate a request to a spatial mapping server to unsubscribe from a spatial map such that the spatial mapping server discontinues sending notifications associated with the subscription to the network entity. Some examples of network entities may comprise a VAL server, location management server, etc. Note, an unsubscribe operation may alternatively be combined and / or supported via a spatial map delete operation which deletes one or more spatial map subscriptions and / or a spatial map and its corresponding spatial map subscriptions.

[0157] Step 1 : A network entity may unsubscribe from a spatial map by issuing a request to delete a specified spatial map subscription from a spatial mapping server. The request may comprise but is not limited to one or more of the information elements defined in Table 1. For example, a spatial map subscription identifier may be provided in the request.

[0158] Step 2: Upon receiving the spatial map unsubscribe request, the spatial mapping server may process the request by first checking whether the network entity originating the request has permissions to unsubscribe from the spatial mapping server. This permissions check may be performed in a manner similar to the methods defined in Step 2 of the spatial map create or update method. If permissions are granted, the spatial mapping server may process the request by performing one or more of the following operations:

[0159] Delete the subscription information (stored locally at the spatial mapping server and / or stored elsewhere in the system) for the specified spatial map subscription.

[0160] Delete any additional subscriptions that the spatial mapping server created with other functions and services in the 3GPP system in order to service this spatial map subscription (e g., subscriptions to location management server, group management server, spatial anchor server, 3 GPP network, spatial mapping clients)

[0161] Step 3: The spatial mapping server may generate and return a spatial map unsubscribe response to the network entity that originated the request. The response may comprise but is not limited to one or more of the information elements defined in Table 1. In addition, a status indication of whether the spatial map unsubscribe request was successfully processed or not may also be provided.

[0162] As shown in Figure 14, a spatial mapping client may initiate a spatial map unsubscribe request to a spatial mapping server such that the spatial mapping server discontinues sending notifications associated with the subscription to the spatial mapping client. The spatial mapping client may be triggered to generate this request via receiving a request from another entity on the UE such as one or more VAL clients hosted on the UE or on another UE or device.

[0163] Step 1 : A VAL client may unsubscribe from a spatial map by issuing a request to a spatial mapping client to delete a specified spatial map subscription. The request may comprise but is not limited to one or more of the information elements defined in Table 1. For example, the VAL client may provide the identifier of a spatial map subscription.

[0164] Step 2: Upon receiving the spatial map unsubscribe request, the spatial mapping client may process the request by first checking whether the VAL client originating the request has permissions to delete a spatial map subscription. This check may be performed in a similar manner to the permissions check defined in Step 2 of the spatial map create or update method. Alternatively, the spatial mapping client map may trigger a spatial map unsubscribe request independent of receiving a request from a VAL client. For example, the spatial mapping client may trigger a spatial map unsubscribe request to a spatial mapping server if / when the spatial mapping client deletes a spatial map locally stored at the spatial mapping client.

[0165] Step 3: The spatial mapping client may send a spatial map unsubscribe request to a spatial mapping server. The request may comprise but is not limited to one or more of the information elements defined in Table 1. These information elements may be the sameinformation elements provided in one or more requests which the spatial mapping client receives from VAL client(s). A spatial mapping client may also provide information elements not received from VAL clients. For example, a spatial mapping client may add additional spatial mapping client specific information. In addition, the spatial mapping client may be configured with one or more policies used to determine the information the spatial mapping client provides in spatial map unsubscribe requests sent to the spatial mapping server.

[0166] Step 4: Upon receiving the request from the spatial mapping client, the spatial mapping server processes the request. The processing may comprise similar aforementioned operations as defined when the spatial mapping server receives a spatial map retrieve or discovery request from a VAL server. However, rather than authorizing the VAL server, the spatial mapping server may instead authorize the spatial mapping client and / or one or more VAL clients to perform the spatial map unsubscribe request.

[0167] Step 5: The spatial mapping server may return a spatial map unsubscribe response to the spatial mapping client. The response may comprise a status indication of whether the request was successfully processed or not.

[0168] Step 6: Upon receiving the response, the spatial mapping client may determine whether the spatial map unsubscribe request was successfully received and processed by the spatial mapping server. If successful, the spatial mapping client may delete any information stored and maintained locally for the spatial map subscription.

[0169] Step 7: The spatial mapping client may send one or more spatial map unsubscribe responses to VAL client(s). The spatial mapping client may provide a status indication of whether the request was successfully processed or not.

[0170] As shown in Figure 15, one or more network entities may initiate a request to a spatial mapping server to delete a spatial map or any spatial mapping context information stored locally at the spatial mapping server or elsewhere in the system. Some examples of network entities may comprise a VAL server, location management server, etc. Note that deleting a spatial map may comprise deleting all context information associated with the spatial map.

[0171] Step 1 : A network entity may delete a spatial map or contexts of a spatial map by issuing a spatial map delete request to a spatial mapping server. The request may comprise but is not limited to one or more of the information elements defined in Table 1. For example, an identifier of a spatial map may be specified.

[0172] Step 2: Upon receiving the spatial map delete request, the spatial mapping server may process the request by first checking whether the network entity originating the request has permissions to delete a spatial map. This permissions check may be performed in a manner similar to the methods defined in Step 2 of the spatial map create or update method. If permissions are granted, the spatial mapping server may process the request. Before deleting a spatial map, a spatial mapping server may check whether the spatial map is in active use. To make this determination, the spatial mapping server may check one or more spatial mapping context information elements such as but not limited to the spatial map status and / or spatial map schedule defined in Table 1. In addition, the spatial mapping server may also check if any spatial map subscriptions exist for the spatial map. If the spatial mapping server determines that a spatial map is actively being used, the spatial mapping server may delay and / or reject the deleting of the spatial map until the spatial map is no longer in active use.

[0173] Step 3: The spatial mapping server may generate and return a spatial map delete response to the network entity that originated the request, where the response may comprise a status indication of whether the spatial map was successfully deleted or not.

[0174] As shown in Figure 16, a spatial mapping client may initiate a spatial map delete request to a spatial mapping server to delete a spatial map or any spatial mapping context information stored locally at the spatial mapping server or elsewhere in the network. The spatial mapping client may be triggered to generate this request when receiving a request from another entity on the UE such as one or more VAL clients hosted on the UE or on another UE or device. Note that deleting a spatial map may comprise deleting all context information associated with the spatial map.

[0175] Step 1 : A VAL client may issue a request to a spatial mapping client to delete a specified spatial map. The request may comprise but is not limited to one or more of the information elements defined in Table 1. For example, the VAL client may provide the identifier of a spatial map.

[0176] Step 2: Upon receiving the spatial map delete request, the spatial mapping client may process the request by first checking whether the VAL client originating the request has permissions to delete a spatial map. This check may be performed in a similar manner to the permissions check defined in Step 2 of the spatial map create or update method. Alternatively, the spatial mapping client may trigger a spatial map delete request independent of a receiving arequest from a VAL client. For example, the spatial mapping client may trigger deleting a spatial map if the spatial map has been inactive for a certain amount time. This determination may be made by the spatial mapping client by detecting the age of a spatial map exceeds the age defined in a spatial map expiration time defined in Table 1.

[0177] Step 3: A spatial mapping client may send a spatial map delete request to a spatial mapping server. The request may comprise but is not limited to one or more of the information elements defined in Table 1. These information elements may be the same information elements provided in one or more requests which the spatial mapping client receives from VAL client(s). A spatial mapping client may also provide information elements not received from VAL clients. For example, a spatial mapping client may add additional spatial mapping client specific information. In addition, the spatial mapping client may be configured with one or more policies used to determine the information the spatial mapping client provides in spatial map delete requests sent to the spatial mapping server.

[0178] Step 4: Upon receiving a spatial map delete request from a spatial mapping client, the spatial mapping server processes the request. The processing may comprise similar aforementioned operations as defined when the spatial mapping server receives a spatial map delete request from a VAL server. However, rather than authorizing the VAL server, the spatial mapping server may instead authorize the spatial mapping client and / or one or more VAL clients to perform the spatial map delete request.

[0179] Step 5: The spatial mapping server may return a spatial map delete response to the spatial mapping client. The response may comprise a status indication of whether the request was successfully processed or not.

[0180] Step 6: Upon receiving the response, the spatial mapping client may determine whether the spatial map delete request was successfully received and processed by the spatial mapping server. If successful, the spatial mapping client may delete any information stored and maintained locally for the spatial map.

[0181] Step 7: The spatial mapping client may send one or more spatial map delete responses to VAL client(s). The spatial mapping client may provide a status indication of whether the request was successfully processed or not.

[0182] As shown in Figure 17, a spatial mapping server may interface with a spatial anchor server in the system. The spatial mapping server may send one or more requests to aspatial anchor server to discover, retrieve, create, update, delete or subscribe to one or more spatial anchors managed by the spatial anchor server and which are applicable to a spatial map. The spatial mapping server may also receive spatial anchor notifications from a spatial anchor server for one or more spatial anchors applicable to a spatial map.

[0183] Step 1 : A spatial mapping server may determine a spatial map boundary (e.g., perimeter), location and / or area of interest of a spatial map. This information may comprise elements such as but not limited to the spatial map elements defined in Table 1.

[0184] Step 2 : A spatial mapping server may issue one or more requests to a spatial anchor server to discover spatial anchors applicable to a spatial map. The request may comprise discovery criteria. The discovery criteria may comprise one or more information elements defined in Table 1 such as a spatial map location, boundary, and / or precision. The discovery criteria may also comprise information for one or more spatial anchors of interest such as spatial anchor names, types, identifiers or locations. In response, the spatial mapping server may receive discovery results from the spatial anchor server comprising information of spatial anchors matching the discovery criteria. For example, a list of spatial anchor identifiers and / or a list of one or more representations of spatial anchors residing within the boundary of the spatial map may be returned, where a spatial anchor representation may comprise one or more spatial anchor context information elements for an individual spatial anchor (e.g., spatial anchor name, position, orientation, etc.).

[0185] Step 3: A spatial mapping server may issue one or more requests to a spatial anchor server to subscribe to receive notifications regarding one or more spatial anchors associated with a spatial map. The request may comprise subscription event criteria. The subscription event criteria may comprise one or more information elements defined in Table 1 such as a spatial map location, boundary, and / or precision. The subscription event criteria may also comprise information for one or more spatial anchors of interest such as spatial anchor names, types, identifiers or locations. In response, the spatial mapping server may receive a response indicating whether the subscription was successfully processed and established or not. Thereafter, the spatial mapping server may receive notifications from the spatial anchor server. The notifications may comprise information pertaining to spatial anchors applicable to a spatial map. For example, a notification may be sent to the spatial mapping server if / when a spatial anchor is added or removed within the spatial map boundary. The notifications may comprisespatial anchor context information such as a list of spatial anchor identifiers and / or a list of one or more representations of spatial anchors applicable to the spatial map, where a spatial anchor representation may comprise one or more spatial anchor context information elements for an individual spatial anchor (e.g., spatial anchor name, identifier, type). Notifications may trigger a spatial map update operation to be performed by a spatial mapping server.

[0186] Step 4: A spatial mapping server may issue one or more requests to a spatial anchor server to retrieve spatial anchors context information applicable to a spatial map. The retrieve may comprise a query criteria. The query criteria may comprise information for one or more spatial anchors of interest such as spatial anchors having certain names, types, identifiers, positions, orientations, and / or distances. In response, the spatial mapping server may receive retrieve results from the spatial anchor server comprising information of spatial anchors matching query criteria if specified. For example, a list of spatial anchor identifiers and / or a list of one or more representations of spatial anchors matching the query criteria. The spatial anchor representation may comprise one or more spatial anchor context information elements for an individual spatial anchor (e.g., spatial anchor name, position, orientation, distance, etc.).

[0187] Step 5: A spatial mapping server may issue one or more requests to a spatial anchor server to subscribe to receive notifications regarding updates to an individual spatial anchor such as its position or orientation, or its distance / range from other spatial anchors or objects. The request may comprise subscription event criteria. The subscription event criteria may comprise information for one or more spatial anchors of interest such as spatial anchor names, types, identifiers. The criteria may also indicate that the spatial mapping server is interested in receiving notifications regarding position, orientation, or ranging changes to a spatial anchor or objects associated with a spatial anchor. The criteria may comprise thresholds that define the amount of change in position, orientation or ranging that must occur before a notification is generated. The spatial mapping server may receive a response indicating whether the subscription request was successfully processed and established or not. Thereafter, the spatial mapping server may receive notifications from the spatial anchor server. The notifications may comprise position, orientation or ranging updates for spatial anchors applicable to a spatial map.

[0188] Step 6: Based on spatial anchor information which a spatial mapping server receives from a spatial anchor server, the spatial mapping server may use this information to create and update a spatial map as described by the hereinafter methods.

[0189] As shown in Figure 18, a spatial mapping server may interface with a 3GPP core network to collect information needed to create and maintain spatial maps. The spatial mapping server may send one or more requests to a 3GPP core network functions and APIs (e.g., 3GPP defined NEF APIs) which the 3GPP core network exposes to the spatial mapping server. The spatial mapping server may also receive notifications from a 3GPP core network. For example, a spatial mapping server may use location, positioning, orientation, and / or ranging, information provided by the 3GPP core network for one or more UEs and / or objects which the 3GPP core network monitors and tracks.

[0190] Step 1 : A spatial mapping server may send a group management request to a 3 GPP core network regarding one or more UEs associated with a spatial map. The UEs may be functioning as spatial anchors. The request may be to discover, create, update, or disband one or more grouped UEs within a spatial map location, area and / or boundary specified by the spatial map server. The request may comprise information such as but not limited to the information elements defined in Table 1. For example, a spatial map location, and / or boundary. Upon receiving the request, the 3GPP core network may discover, create, update or disband the one or more grouped UEs within the spatial map location, area, and / or boundary and return a response to the spatial mapping server indicating the status of the group management operation performed. The response may comprise an identifier for the one or more grouped UEs.

[0191] Step 2: A spatial mapping server may send one or more location monitoring requests to a 3 GPP core network to monitor the location of UEs that are within the boundary of a spatial map. The request may comprise information such as but not limited to the information elements defined in Table 1. For example, a spatial map location, and / or boundary. The request may also comprise one or more identifiers of individual UEs or a group identifier for UEs associated with the spatial map (i.e., are known to be in the boundary of the spatial map). Upon receiving the request, the 3 GPP core network may monitor the location of one or more UEs and notify the spatial mapping server if / when one or more of the UEs enter or leave the boundary of the spatial map.

[0192] Step 3: A spatial mapping server may send one or more positioning, orientation, and / or ranging requests to a 3GPP core network to track and / or monitor the position, orientation and / or range of a UE with respect to one or more other UEs associated with a spatial map. The request may comprise information such as but not limited to the information elements defined inTable 1 . For example, a spatial map location, and / or boundary. The request may also comprise an identifier of one or more individual UEs or a group identifier for UEs associated with the spatial map (i.e., are known to be in the boundary of the spatial map). The request may also comprise position, orientation, ranging thresholds. Upon receiving the request, the 3GPP core network may determine the position, orientation and / or range of one or more UEs with respect to one or more other UEs. The determination may be using threshold values provided in the request. The spatial mapping server may receive position, orientation and / or range results back in a response from the 3GPP core network. The spatial mapping server may also receive one or more notifications from the 3GPP core network sometime thereafter. The notifications may be sent if / when changes in the position, orientation, and / or ranging of one or more UEs associated with the spatial map are detected by the 3 GPP core network.

[0193] Step 4: Based on the information from the 3GPP core network, the spatial mapping server may create and update a spatial map as described by the hereinafter methods.

[0194] As shown in Figure 19, a spatial mapping server may interface with one or more location management servers in the system to collect information needed to create and maintain spatial maps. Note, this may be in addition to or instead of interfacing to a spatial anchor server and / or 3GPP core network to collect this information as described in the aforementioned methods. The spatial mapping server may send one or more requests to location management servers. The spatial mapping server may receive one or more responses from the location management server. In addition, the spatial mapping server may also receive notifications from a location management server. For example, a spatial mapping server may receive updated location, positioning, orientation, distance notifications provided by a location management server for one or more UEs and / or spatial anchors which the spatial mapping server monitors and tracks.

[0195] Step 1: A spatial mapping server may determine a spatial map boundary (e.g., perimeter), location and / or area of interest of a spatial map. The information may comprise elements such as but not limited to the spatial map elements defined in Table 1.

[0196] Step 2: A spatial mapping server may issue one or more requests to a location management server to discover UEs and / or spatial anchors applicable to a spatial map. The request may comprise discovery criteria. The discovery criteria may comprise one or more information elements defined in Table 1 such as a spatial map name, type, identifier, location,boundary, and / or precision. The discovery criteria may also comprise information for one or more UEs and / or spatial anchors of interest such as UE and spatial anchor types, identifiers or locations. In response, the spatial mapping server may receive discovery results from the location management server comprising information of UEs and / or spatial anchors matching the discovery criteria. For example, a list of UE and / or spatial anchor identifiers residing within the boundary of the spatial map may be returned. Additional information regarding UEs and spatial anchors may also be returned such as position and orientation of the UE and / or spatial anchor.

[0197] Step 3: A spatial mapping server may issue one or more requests to a location management server to subscribe to receive notifications regarding one or more UEs and / or spatial anchors applicable to a spatial map. The request may comprise subscription event criteria. The subscription event criteria may comprise one or more information elements defined in Table 1 such as a spatial map name, type, identifier, location, boundary, and / or precision. The subscription event criteria may also comprise information for one or more UEs and / or spatial anchors of interest such as names, types, identifiers or locations. In response, the spatial mapping server may receive a response indicating whether the subscription was successfully processed and established or not. Thereafter, the spatial mapping server may receive UE and / or spatial anchor notifications from the location management server. The notifications may comprise information pertaining to UE and / or spatial anchors applicable to a spatial map. For example, a notification may be sent to the spatial mapping server if / when a UE and / or spatial anchor is added or removed within the spatial map boundary. The notifications may comprise UE and / or spatial anchor context information such as a list of UE and / or spatial anchor identifiers and / or a list of one or more representations of UEs and / or spatial anchors applicable to the spatial map, where a UE and / or spatial anchor representation may comprise one or more UE and / or spatial anchor context information elements for an individual UE and / or spatial anchor (e g., UE and / or spatial anchor name, identifier, type).

[0198] Step 4: A spatial mapping server may issue one or more requests to a location management server to retrieve UE and / or spatial anchors context information applicable to a spatial map. The request may comprise query criteria. The query criteria may comprise information for one or more UEs and / or spatial anchors of interest such as UEs and / or spatial anchors having certain names, types, identifiers, positions, orientations, and / or distances. In response, the spatial mapping server may receive retrieve results from the location managementserver comprising information of UEs and / or spatial anchors matching query criteria if specified. For example, a list of UEs and / or spatial anchor identifiers and / or a list of one or more representations of UEs and / or spatial anchors matching the query criteria. The UE and / or spatial anchor representation may comprise one or more spatial anchor context information elements for an individual UE and / or spatial anchor (e.g., UE and / or spatial anchor name, position, orientation, distance, etc.).

[0199] Step 5: A spatial mapping server may issue one or more requests to a location management server to subscribe to receive notifications regarding updates to an individual UE and / or spatial anchor such as its position or orientation, or its distance / range from other UE and / or spatial anchors or objects. The request may comprise subscription event criteria. The subscription event criteria may comprise information for one or more UE and / or spatial anchors of interest such as UE and / or spatial anchor names, types, identifiers. The criteria may also indicate that the spatial mapping server is interested in receiving notifications regarding position, orientation, or ranging changes to a UE and / or spatial anchor or objects associated with a spatial anchor. The criteria may comprise thresholds that define the amount of change in position, orientation or ranging that must occur before a notification is generated. The spatial mapping server may receive a response indicating whether the subscription request was successfully processed and established or not. Thereafter, the spatial mapping server may receive UE and / or spatial anchor notifications from the location management server. The notifications may comprise position, orientation or ranging updates for UEs and / or spatial anchors applicable to a spatial map.

[0200] Step 6: Based on UE and / or spatial anchor information received from location management server(s), the spatial mapping server may use this information to create and update a spatial map as described by the hereinafter methods.

[0201] As shown in Figure 20, a spatial mapping server may interface with one or more group management servers in the system to perform group management operations for UEs and / or spatial anchors associated with spatial maps. Note, this may be in addition to or instead of interfacing to a 3GPP core network to perform group management operations as described in the aforementioned methods. The spatial mapping server may send one or more requests to group management servers. The spatial mapping server may receive one or more responses from the group management server. In addition, the spatial mapping server may also receivenotifications from a group management server. For example, a spatial mapping server may receive notifications if / when UEs and / or spatial anchors are dynamically added or removed from a group associated with a spatial map (e.g., based on whether or not the UEs and / or spatial anchors reside within the boundary of the spatial map).

[0202] Step 1 : A spatial mapping server may determine that grouping of UEs and / or spatial anchors is desired in order to create and manage a spatial map. This determination may be made autonomously by the spatial mapping server. Alternatively, this determination may be made using information provided by other entities in the system. For example, the spatial mapping server may receive grouping information such as policies or instructions from a VAL server, spatial mapping client, and / or VAL client.

[0203] Step 2: A spatial mapping server may issue one or more requests to a group management server to discover existing groups of UEs and / or spatial anchors applicable to a spatial map. The request may comprise discovery criteria. The discovery criteria may comprise one or more information elements defined in Table 1 such as a spatial map name, type, identifier, location, boundary, and / or precision. The discovery criteria may also comprise information for one or more UEs and / or spatial anchors of interest such as UE and / or spatial anchor names, types, identifiers or locations. In response, the spatial mapping server may receive discovery results from the group management server comprising information of groups of UEs and / or spatial anchors matching the discovery criteria. For example, identifier(s) of groups of UEs and / or spatial anchors residing within the boundary of the spatial map may be returned.

[0204] Step 3: A spatial mapping server may issue a request to a group management server to create a group of one or more UEs and / or spatial anchors associated with a spatial map. For example, UEs and / or spatial anchors currently residing within the boundary of a spatial map. The request may comprise information such as but not limited to one or more elements defined in Table 1. For example, a spatial map boundary, information regarding one or more spatial anchors associated with a spatial map, or a spatial map location. A spatial mapping server may receive a response from a group management server. The response may comprise one or more identifiers for groups of UEs and / or spatial anchors associated with a spatial map. The response may also comprise additional information for the UEs and / or spatial anchors.

[0205] Step 4: A spatial mapping server may issue one or more requests to a group management server to subscribe to receive notifications regarding one or more groups applicableto a spatial map. The request may comprise a group identifier, a group event of interest, and / or a boundary or sub-boundary associated with a group. The group event of interest may comprise information for one or more groups. For example, whether a member a UE or spatial anchor within the boundary of the spatial map has bene added or removed from one or more groups associated with a spatial map. The spatial mapping server may receive a response indicating whether the subscription request was successfully processed and established or not. Thereafter, the spatial mapping server may receive group notifications from the group management server. For example, a notification may be sent to the spatial mapping server if / when a UE and / or spatial anchor is added or removed from a group associated with the spatial map. The notifications may comprise information regarding the group members such as the one or more UEs and / or spatial anchors that are current members of a group since they currently reside in the boundary of the spatial map.

[0206] Step 5: Based on group information which a spatial mapping server receives from a group management server, the spatial mapping server may use this information to create and update a spatial map as described by the hereinafter methods.

[0207] In one example, spatial mapping servers and / or clients may implement spatial mapping context information elements (such as but not limited to those defined in Table 1) as one or more RESTful resources. The RESTful resources may have unique addresses (e.g. URIs, URNs, etc.) and may also have one or more attributes that comprise resource data and / or metadata. These spatial mapping resources may be created, retrieved, discovered, updated, or deleted by VAL clients and servers, as well as by other entities in the system such as but not limited to those shown in Figure 3. Spatial mapping servers and clients may support RESTful APIs based on these resources. These APIs may be based on RESTful protocols such as HTTP and CoAP.

[0208] In another example, spatial mapping servers and / or clients may implement spatial mapping context information elements (such as but not limited to those defined in Table 1) as one or more topics within a topic space of a message broker (e.g., MQTT broker, AMQP broker, etc.). A spatial mapping server and / or client may function as the message broker. Alternatively, the message broker may be hosted external to the spatial mapping server and / or client. For example, by another entity in the system which the spatial mapping server or client may communicate with. A spatial mapping server and / or client may send and / or receive publishand / or subscribe requests to topics within a message broker. The topics may have unique addresses (e.g. topic names, etc.) and also one or more attributes that comprise topic data and / or metadata.

[0209] Figure 21 shows an example of a graphical user interface (GUI) for a spatial map supporting the spatial mapping capabilities proposed herein. A VAL server and / or client may support a spatial map GUI to allow users to interact with a spatial mapping server and / or client. Alternatively, a spatial mapping server and / or client may support a GUI. Via this GUI a user may perform one or more spatial map operations defined herein. For example, a user may use the GUI to initiate a spatial map create request to a spatial mapping server and / or client.

[0210] Figure 22A illustrates one embodiment of an example communications system 100 in which the methods and apparatuses described and claimed herein may be embodied. As shown, the example communications system 100 may comprise wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, 102e, 102f, and / or 102g (which generally or collectively may be referred to as WTRU 102), a radio access network (RAN) 103 / 104 / 105 / 103b / l 04b / l 05b, a core network 106 / 107 / 109, a public switched telephone network (PSTN) 108, the Internet 110, , other networks 112, and V2X server (or ProSe function and server) 113, though it will be appreciated that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102a, 102b, 102c, 102d, 102e, 102f, 102g may be any type of apparatus or device configured to operate and / or communicate in a wireless environment. Although each WTRU 102a, 102b, 102c, 102d, 102e, 102f, 102g is depicted in Figures 22A-22E as a hand-held wireless communications apparatus, it is understood that with the wide variety of examples contemplated for 5G wireless communications, each WTRU may comprise or be embodied in any type of apparatus or device configured to transmit and / or receive wireless signals, including, by way of example only, user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a pager, a cellular telephone, a personal digital assistant (PDA), a smartphone, a laptop, a tablet, a netbook, a notebook computer, a personal computer, a wireless sensor, consumer electronics, a wearable device such as a smart watch or smart clothing, a medical or eHealth device, a robot, industrial equipment, a drone, a vehicle such as a car, truck, train, or airplane, and the like.

[0211] The communications system 100 may also comprise a base station 114a and a base station 114b. Base stations 114a may be any type of device configured to wirelesslyinterface with at least one of the WTRUs 102a, 102b, 102c to facilitate access to one or more communication networks, such as the core network 106 / 107 / 109, the Internet 110, and / or the other networks 112. Base stations 114b may be any type of device configured to wiredly and / or wirelessly interface with at least one of the RRHs (Remote Radio Heads) 118a, 118b, TRPs (Transmission and Reception Points) 119a, 119b, and / or RSUs (Roadside Units) 120a and 120b to facilitate access to one or more communication networks, such as the core network 106 / 107 / 109, the Internet 110, the other networks 112, and / or V2X server (or ProSe function and server) 113. RRHs 118a, 118b may be any type of device configured to wirelessly interface with at least one of the WTRU 102c, to facilitate access to one or more communication networks, such as the core network 106 / 107 / 109, the Internet 110, and / or the other networks 112. TRPs 119a, 119b may be any type of device configured to wirelessly interface with at least one of the WTRU 102d, to facilitate access to one or more communication networks, such as the core network 106 / 107 / 109, the Internet 110, and / or the other networks 112. RSUs 120a and 120b may be any type of device configured to wirelessly interface with at least one of the WTRU 102e or 102f, to facilitate access to one or more communication networks, such as the core network 106 / 107 / 109, the Internet 110, the other networks 112, and / or V2X server (or ProSe function and server) 113. By way of example, the base stations 114a, 114b may be a base transceiver station (BTS), a Node-B, an eNode B, a Home Node B, a Home eNode B, a site controller, an access point (AP), a wireless router, and the like. While the base stations 114a, 114b are each depicted as a single element, it will be appreciated that the base stations 114a, 114b may comprise any number of interconnected base stations and / or network elements.

[0212] The base station 114a may be part of the RAN 103 / 104 / 105, which may also comprise other base stations and / or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), relay nodes, etc. The base station 114b may be part of the RAN 103b / l 04b / l 05b, which may also comprise other base stations and / or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), relay nodes, etc. The base station 114a may be configured to transmit and / or receive wireless signals within a particular geographic region, which may be referred to as a cell (not shown). The base station 114b may be configured to transmit and / or receive wired and / or wireless signals within a particular geographic region, which may be referred to as a cell (not shown). The cell may further be divided into cell sectors. For example, the cell associated withthe base station 114a may be divided into three sectors. Thus, in an embodiment, the base station 114a may comprise three transceivers, e.g., one for each sector of the cell. In an embodiment, the base station 114a may employ multiple-input multiple output (MIMO) technology and, therefore, may utilize multiple transceivers for each sector of the cell.

[0213] The base stations 114a may communicate with one or more of the WTRUs 102a, 102b, 102c over an air interface 115 / 116 / 117, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, cmWave, mmWave, etc.). The air interface 115 / 116 / 117 may be established using any suitable radio access technology (RAT).

[0214] The base stations 114b may communicate with one or more of the RRHs 118a, 118b, TRPs 119a, 119b, and / or RSUs 120a and 120b, over a wired or air interface 115b / l 16b / l 17b, which may be any suitable wired (e.g., cable, optical fiber, etc.) or wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, cmWave, mmWave, etc.). The air interface 115b / 116b / 117b may be established using any suitable radio access technology (RAT).

[0215] The RRHs 118a, 118b, TRPs 119a, 119b and / or RSUs 120a, 120b, may communicate with one or more of the WTRUs 102c, 102d, 102e, 102f over an air interface 115c / l 16c / l 17c, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, cmWave, mmWave, etc.). The air interface 115c / l 16c / l 17c may be established using any suitable radio access technology (RAT).

[0216] The WTRUs 102a, 102b, 102c, 102d, 102e, 102f, and / or 102g may communicate with one another over an air interface 115d / l 16d / l 17d (not shown in the figures), which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light, cmWave, mmWave, etc.). The air interface 115d / l 16d / l 17d may be established using any suitable radio access technology (RAT).

[0217] More specifically, as noted above, the communications system 100 may be a multiple access system and may employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and the like. For example, the base station 114a in the RAN 103 / 104 / 105 and the WTRUs 102a, 102b, 102c, or RRHs 118a, 118b, TRPs 119a, 119b and RSUs 120a, 120b, in the RAN 103b / 104b / 105b and the WTRUs 102c, 102d, 102e, 102f, may implement a radio technology such as Universal Mobile Telecommunications System (UMTS)Terrestrial Radio Access (UTRA), which may establish the air interface 115 / 116 / 1 17 or 115c / l 16c / l 17c respectively using wideband CDMA (WCDMA). WCDMA may comprise communication protocols such as High-Speed Packet Access (HSPA) and / or Evolved HSPA (HSPA+). HSPA may comprise High-Speed Downlink Packet Access (HSDPA) and / or High- Speed Uplink Packet Access (HSUPA).

[0218] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c, or RRHs 118a, 118b, TRPs 119a, 119b, and / or RSUs 120a, 120b, in the RAN 103b / l 04b / l 05b and the WTRUs 102c, 102d, may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may establish the air interface 115 / 116 / 117 or 115c / l 16c / l 17c respectively using Long Term Evolution (LTE) and / or LTE-Advanced (LTE-A). In the future, the air interface 115 / 116 / 117 may implement 3 GPP NR technology. The LTE and LTE-A technology comprises LTE D2D and V2X technologies and interface (such as Sidelink communications, etc.) The 3GPP NR technology comprises NR V2X technologies and interface (such as Sidelink communications, etc.)

[0219] In an embodiment, the base station 114a in the RAN 103 / 104 / 105 and the WTRUs 102a, 102b, 102c, or RRHs 118a, 118b, TRPs 119a, 119b and / or RSUs 120a, 120b, in the RAN 103b / 104b / l 05b and the WTRUs 102c, 102d, 102e, 102f may implement radio technologies such as IEEE 802.16 (e.g., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 IX, CDMA2000 EV-DO, Interim Standard 2000 (IS- 2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), and the like.

[0220] The base station 114c in Figure 22A may be a wireless router, Home Node B, Home eNode B, or access point, for example, and may utilize any suitable RAT for facilitating wireless connectivity in a localized area, such as a place of business, a home, a vehicle, a campus, and the like. In an embodiment, the base station 114c and the WTRUs 102e, may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN). In an embodiment, the base station 114c and the WTRUs 102d, may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). In yet another embodiment, the base station 114c and the WTRUs 102e, may utilize a cellularbased RAT (e g., WCDMA, CDMA2000, GSM, LTE, LTE-A, etc.) to establish a picocell orfemtocell. As illustrated in Figure 22A, the base station 114b may have a direct connection to the Internet 110. Thus, the base station 114c may not be required to access the Internet 110 via the core network 106 / 107 / 109.

[0221] The RAN 103 / 104 / 105 and / or RAN 103b / 104b / 105b may be in communication with the core network 106 / 107 / 109, which may be any type of network configured to provide voice, data, applications, and / or voice over internet protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. For example, the core network 106 / 107 / 109 may provide call control, billing services, mobile location-based services, pre-paid calling, Internet connectivity, video distribution, etc., and / or perform high-level security functions, such as user authentication.

[0222] Although not illustrated in Figure 22A, it will be appreciated that the RAN 103 / 104 / 105 and / or RAN 103b / l 04b / l 05b and / or the core network 106 / 107 / 109 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 103 / 104 / 105 and / or RAN 103b / l 04b / 105b or a different RAT. For example, in addition to being connected to the RAN 103 / 104 / 105 and / or RAN 103b / l 04b / l 05b, which may be utilizing an E-UTRA radio technology, the core network 106 / 107 / 109 may also be in communication with another RAN (not shown) employing a GSM radio technology.

[0223] The core network 106 / 107 / 109 may also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d, 102e to access the PSTN 108, the Internet 110, and / or other networks 112. The PSTN 108 may comprise circuit-switched telephone networks that provide plain old telephone service (POTS). The Internet 110 may comprise a global system of interconnected computer networks and devices that use common communication protocols, such as the transmission control protocol (TCP), user datagram protocol (UDP) and the internet protocol (IP) in the TCP / IP internet protocol suite. The networks 112 may comprise wired or wireless communications networks owned and / or operated by other service providers. For example, the networks 112 may comprise another core network connected to one or more RANs, which may employ the same RAT as the RAN 103 / 104 / 105 and / or RAN 103b / 104b / 105b or a different RAT.

[0224] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communications system 100 may comprise multi-mode capabilities, e.g., the WTRUs 102a, 102b, 102c, 102d, and 102e may comprise multiple transceivers for communicating with different wireless networks overdifferent wireless links. For example, the WTRU 102e illustrated in Figure 22A may be configured to communicate with the base station 114a, which may employ a cellular-based radio technology, and with the base station 114c, which may employ an IEEE 802 radio technology.

[0225] Figure 22B is a block diagram of an example apparatus or device configured for wireless communications in accordance with the embodiments illustrated herein, such as for example, a WTRU 102. As illustrated in Figure 22B, the example WTRU 102 may comprise a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a keypad 113, a display / touchpad / indicators 128, non-removable memory 130, removable memory 132, a power source 134, a global positioning system (GPS) chipset 136, and other peripherals 138. It will be appreciated that the WTRU 102 may comprise any sub-combination of the foregoing elements while remaining consistent with an embodiment. Also, embodiments contemplate that the base stations 114a and 114b, and / or the nodes that base stations 114a and 114b may represent, such as but not limited to transceiver station (BTS), a Node-B, a site controller, an access point (AP), a home node-B, an evolved home node-B (eNodeB), a home evolved node-B (HeNB), a home evolved node-B gateway, and proxy nodes, among others, may comprise some or all of the elements depicted in Figure 22B and described herein.

[0226] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Array (FPGAs) circuits, any other type of integrated circuit (IC), a state machine, and the like. The processor 118 may perform signal coding, data processing, power control, input / output processing, and / or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit / receive element 122. While Figure 22B depicts the processor 118 and the transceiver 120 as separate components, it will be appreciated that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.

[0227] The transmit / receive element 122 may be configured to transmit signals to, or receive signals from, a base station (e.g., the base station 114a) over the air interface 115 / 116 / 117. For example, in an embodiment, the transmit / receive element 122 may be an antenna configured to transmit and / or receive RF signals. In an embodiment, the transmit / receiveelement 122 may be an emitter / detector configured to transmit and / or receive IR, UV, or visible light signals, for example. In yet an embodiment, the transmit / receive element 122 may be configured to transmit and receive both RF and light signals. It will be appreciated that the transmit / receive element 122 may be configured to transmit and / or receive any combination of wireless signals.

[0228] In addition, although the transmit / receive element 122 is depicted in Figure 22B as a single element, the WTRU 102 may comprise any number of transmit / receive elements 122. More specifically, the WTRU 102 may employ MIMO technology. Thus, in an embodiment, the WTRU 102 may comprise two or more transmit / receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 115 / 116 / 117.

[0229] The transceiver 120 may be configured to modulate the signals that are to be transmitted by the transmit / receive element 122 and to demodulate the signals that are received by the transmit / receive element 122. As noted above, the WTRU 102 may have multi-mode capabilities. Thus, the transceiver 120 may comprise multiple transceivers for enabling the WTRU 102 to communicate via multiple RATs, such as UTRA and IEEE 802.11, for example.

[0230] The processor 118 of the WTRU 102 may be coupled to, and may receive user input data from, the speaker / mi crophone 124, the keypad 126, and / or the display / touchpad / indicators 128 (e.g., a liquid crystal display (LCD) display unit or organic light-emitting diode (OLED) display unit). The processor 118 may also output user data to the speaker / microphone 124, the keypad 126, and / or the display / touchpad / indicators 128. In addition, the processor 118 may access information from, and store data in, any type of suitable memory, such as the non-removable memory 130 and / or the removable memory 132. The nonremovable memory 130 may comprise random-access memory (RAM), read-only memory (ROM), a hard disk, or any other type of memory storage device. The removable memory 132 may comprise a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like. In an embodiment, the processor 118 may access information from, and store data in, memory that is not physically located on the WTRU 102, such as on a server or a home computer (not shown).

[0231] The processor 118 may receive power from the power source 134, and may be configured to distribute and / or control the power to the other components in the WTRU 102. The power source 134 may be any suitable device for powering the WTRU 102. For example, thepower source 134 may comprise one or more dry cell bateries, solar cells, fuel cells, and the like.

[0232] The processor 118 may also be coupled to the GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102. In addition to, or in lieu of, the information from the GPS chipset 136, the WTRU 102 may receive location information over the air interface 115 / 116 / 117 from a base station (e.g., base stations 114a, 114b) and / or determine its location based on the timing of the signals being received from two or more nearby base stations. It will be appreciated that the WTRU 102 may acquire location information by way of any suitable location-determination method while remaining consistent with an embodiment.

[0233] The processor 118 may further be coupled to other peripherals 138, which may comprise one or more software and / or hardware modules that provide additional features, functionality and / or wired or wireless connectivity. For example, the peripherals 138 may comprise various sensors such as an accelerometer, biometrics (e.g., finger print) sensors, an e- compass, a satellite transceiver, a digital camera (for photographs or video), a universal serial bus (USB) port or other interconnect interfaces, a vibration device, a television transceiver, a hands free headset, a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, and the like.

[0234] The WTRU 102 may be embodied in other apparatuses or devices, such as a sensor, consumer electronics, a wearable device such as a smart watch or smart clothing, a medical or eHealth device, a robot, industrial equipment, a drone, a vehicle such as a car, truck, train, or airplane. The WTRU 102 may connect to other components, modules, or systems of such apparatuses or devices via one or more interconnect interfaces, such as an interconnect interface that may comprise one of the peripherals 138.

[0235] Figure 22C is a system diagram of the RAN 103 and the core network 106 according to an embodiment. As noted above, the RAN 103 may employ a UTRA radio technology to communicate with the WTRUs 102a, 102b, and 102c over the air interface 115. The RAN 103 may also be in communication with the core network 106. As illustrated in Figure 22C, the RAN 103 may comprise Node-Bs 140a, 140b, 140c, which may each comprise one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 115. The Node-Bs 140a, 140b, 140c may each be associated with a particular cell (not shown)within the RAN 103. The RAN 103 may also comprise RNCs 142a, 142b. It will be appreciated that the RAN 103 may comprise any number of Node-Bs and RNCs while remaining consistent with an embodiment.

[0236] As illustrated in Figure 22C, the Node-Bs 140a, 140b may be in communication with the RNC 142a. Additionally, the Node-B 140c may be in communication with the RNC 142b. The Node-Bs 140a, 140b, 140c may communicate with the respective RNCs 142a, 142b via an lub interface. The RNCs 142a, 142b may be in communication with one another via an lur interface. Each of the RNCs 142a, 142b may be configured to control the respective Node-Bs 140a, 140b, 140c to which it is connected. In addition, each of the RNCs 142a, 142b may be configured to carry out or support other functionality, such as outer loop power control, load control, admission control, packet scheduling, handover control, macro-diversity, security functions, data encryption, and the like.

[0237] The core network 106 illustrated in Figure 22C may comprise a media gateway (MGW) 144, a mobile switching center (MSC) 146, a serving GPRS support node (SGSN) 148, and / or a gateway GPRS support node (GGSN) 150. While each of the foregoing elements are depicted as part of the core network 106, it will be appreciated that any one of these elements may be owned and / or operated by an entity other than the core network operator.

[0238] The RNC 142a in the RAN 103 may be connected to the MSC 146 in the core network 106 via an luCS interface. The MSC 146 may be connected to the MGW 144. The MSC 146 and the MGW 144 may provide the WTRUs 102a, 102b, 102c with access to circuit- switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices.

[0239] The RNC 142a in the RAN 103 may also be connected to the SGSN 148 in the core network 106 via an luPS interface. The SGSN 148 may be connected to the GGSN 150. The SGSN 148 and the GGSN 150 may provide the WTRUs 102a, 102b, 102c with access to packet- switched networks, such as the Internet 110, to facilitate communications between and the WTRUs 102a, 102b, 102c and IP-enabled devices.

[0240] As noted above, the core network 106 may also be connected to the networks 112, which may comprise other wired or wireless networks that are owned and / or operated by other service providers.

[0241] Figure 22D is a system diagram of the RAN 104 and the core network 107 according to an embodiment. As noted above, the RAN 104 may employ an E-UTRA radio technology to communicate with the WTRUs 102a, 102b, and 102c over the air interface 116. The RAN 104 may also be in communication with the core network 107.

[0242] The RAN 104 may comprise eNode-Bs 160a, 160b, 160c, though it will be appreciated that the RAN 104 may comprise any number of eNode-Bs while remaining consistent with an embodiment. The eNode-Bs 160a, 160b, 160c may each comprise one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In an embodiment, the eNode-Bs 160a, 160b, 160c may implement MIMO technology. Thus, the eNode-B 160a, for example, may use multiple antennas to transmit wireless signals to, and receive wireless signals from, the WTRU 102a.

[0243] Each of the eNode-Bs 160a, 160b, and 160c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the uplink and / or downlink, and the like. As illustrated in Figure 22D, the eNode-Bs 160a, 160b, 160c may communicate with one another over an X2 interface.

[0244] The core network 107 illustrated in Figure 22D may comprise a mobility management gateway (MME) 162, a serving gateway 164, and a packet data network (PDN) gateway 166. While each of the foregoing elements are depicted as part of the core network 107, it will be appreciated that any one of these elements may be owned and / or operated by an entity other than the core network operator.

[0245] The MME 162 may be connected to each of the eNode-Bs 160a, 160b, and 160c in the RAN 104 via an SI interface and may serve as a control node. For example, the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, bearer activation / deactivation, selecting a particular serving gateway during an initial attach of the WTRUs 102a, 102b, 102c, and the like. The MME 162 may also provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM or WCDMA.

[0246] The serving gateway 164 may be connected to each of the eNode-Bs 160a, 160b, and 160c in the RAN 104 via the SI interface. The serving gateway 164 may generally route and forward user data packets to / from the WTRUs 102a, 102b, 102c. The serving gateway 164 mayal so perform other functions, such as anchoring user planes during inter-eNode B handovers, triggering paging when downlink data is available for the WTRUs 102a, 102b, 102c, managing and storing contexts of the WTRUs 102a, 102b, 102c, and the like.

[0247] The serving gateway 164 may also be connected to the PDN gateway 166, which may provide the WTRUs 102a, 102b, 102c with access to packet- switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.

[0248] The core network 107 may facilitate communications with other networks. For example, the core network 107 may provide the WTRUs 102a, 102b, 102c with access to circuit- switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices. For example, the core network 107 may comprise, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the core network 107 and the PSTN 108. In addition, the core network 107 may provide the WTRUs 102a, 102b, 102c with access to the networks 112, which may comprise other wired or wireless networks that are owned and / or operated by other service providers.

[0249] Figure 22E is a system diagram of the RAN 105 and the core network 109 according to an embodiment. The RAN 105 may be an access service network (ASN) that employs IEEE 802.16 radio technology to communicate with the WTRUs 102a, 102b, and 102c over the air interface 117. As will be further discussed below, the communication links between the different functional entities of the WTRUs 102a, 102b, 102c, the RAN 105, and the core network 109 may be defined as reference points.

[0250] As illustrated in Figure 22E, the RAN 105 may comprise base stations 180a, 180b, 180c, and an ASN gateway 182, though it will be appreciated that the RAN 105 may comprise any number of base stations and ASN gateways while remaining consistent with an embodiment. The base stations 180a, 180b, 180c may each be associated with a particular cell in the RAN 105 and may comprise one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 117. In an embodiment, the base stations 180a, 180b, 180c may implement MIMO technology. Thus, the base station 180a, for example, may use multiple antennas to transmit wireless signals to, and receive wireless signals from, the WTRU 102a. The base stations 180a, 180b, 180c may also provide mobility management functions, suchas handoff triggering, tunnel establishment, radio resource management, traffic classification, quality of service (QoS) policy enforcement, and the like. The ASN gateway 182 may serve as a traffic aggregation point and may be responsible for paging, caching of subscriber profiles, routing to the core network 109, and the like.

[0251] The air interface 117 between the WTRUs 102a, 102b, 102c and the RAN 105 may be defined as an R1 reference point that implements the IEEE 802.16 specification. In addition, each of the WTRUs 102a, 102b, and 102c may establish a logical interface (not shown) with the core network 109. The logical interface between the WTRUs 102a, 102b, 102c and the core network 109 may be defined as an R2 reference point, which may be used for authentication, authorization, IP host configuration management, and / or mobility management.

[0252] The communication link between each of the base stations 180a, 180b, and 180c may be defined as an R8 reference point that comprises protocols for facilitating WTRU handovers and the transfer of data between base stations. The communication link between the base stations 180a, 180b, 180c and the ASN gateway 182 may be defined as an R6 reference point. The R6 reference point may comprise protocols for facilitating mobility management based on mobility events associated with each of the WTRUs 102a, 102b, 102c.

[0253] As illustrated in Figure 22E, the RAN 105 may be connected to the core network 109. The communication link between the RAN 105 and the core network 109 may defined as an R3 reference point that comprises protocols for facilitating data transfer and mobility management capabilities, for example. The core network 109 may comprise a mobile IP home agent (MIP-HA) 184, an authentication, authorization, accounting (AAA) server 186, and a gateway 188. While each of the foregoing elements are depicted as part of the core network 109, it will be appreciated that any one of these elements may be owned and / or operated by an entity other than the core network operator.

[0254] The MIP-HA may be responsible for IP address management, and may enable the WTRUs 102a, 102b, and 102c to roam between different ASNs and / or different core networks. The MIP-HA 184 may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices. The AAA server 186 may be responsible for user authentication and for supporting user services. The gateway 188 may facilitate interworking with other networks. For example, the gateway 188 may provide the WTRUs 102a, 102b, 102cwith access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices. In addition, the gateway 188 may provide the WTRUs 102a, 102b, 102c with access to the networks 112, which may comprise other wired or wireless networks that are owned and / or operated by other service providers.

[0255] Although not illustrated in Figure 22E, it will be appreciated that the RAN 105 may be connected to other ASNs and the core network 109 may be connected to other core networks. The communication link between the RAN 105 the other ASNs may be defined as an R4 reference point, which may comprise protocols for coordinating the mobility of the WTRUs 102a, 102b, 102c between the RAN 105 and the other ASNs. The communication link between the core network 109 and the other core networks may be defined as an R5 reference, which may comprise protocols for facilitating interworking between home core networks and visited core networks.

[0256] The core network entities described herein and illustrated in Figures 22A, 22C, 22D, and 22E are identified by the names given to those entities in certain existing 3GPP specifications, but it is understood that in the future those entities and functionalities may be identified by other names and certain entities or functions may be combined in future specifications published by 3GPP, including future 3GPP NR specifications. Thus, the particular network entities and functionalities described and illustrated in Figures 22A, 22B, 22C, 22D, and 22E are provided by way of example only, and it is understood that the subject matter disclosed and claimed herein may be embodied or implemented in any similar communication system, whether presently defined or defined in the future.

[0257] Figure 22F is a block diagram of an exemplary computing system 90 in which one or more apparatuses of the communications networks illustrated in Figures 22A, 22C, 22D and 22E may be embodied, such as certain nodes or functional entities in the RAN 103 / 104 / 105, Core Network 106 / 107 / 109, PSTN 108, Internet 110, or Other Networks 112. Computing system 90 may comprise a computer or server and may be controlled primarily by computer readable instructions, which may be in the form of software, wherever, or by whatever means such software is stored or accessed. Such computer readable instructions may be executed within a processor 91, to cause computing system 90 to do work. The processor 91 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signalprocessor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Array (FPGAs) circuits, any other type of integrated circuit (IC), a state machine, and the like. The processor 91 may perform signal coding, data processing, power control, input / output processing, and / or any other functionality that enables the computing system 90 to operate in a communications network. Coprocessor 81 is an optional processor, distinct from main processor 91, that may perform additional functions or assist processor 91. Processor 91 and / or coprocessor 81 may receive, generate, and process data related to the methods and apparatuses disclosed herein.

[0258] In operation, processor 91 fetches, decodes, and executes instructions, and transfers information to and from other resources via the computing system’s main data-transfer path, system bus 80. Such a system bus connects the components in computing system 90 and defines the medium for data exchange. System bus 80 typically comprises data lines for sending data, address lines for sending addresses, and control lines for sending interrupts and for operating the system bus. An example of such a system bus 80 is the PCI (Peripheral Component Interconnect) bus.

[0259] Memories coupled to system bus 80 comprise random access memory (RAM) 82 and read only memory (ROM) 93. Such memories comprise circuitry that allows information to be stored and retrieved. ROMs 93 generally comprise stored data that cannot easily be modified. Data stored in RAM 82 may be read or changed by processor 91 or other hardware devices. Access to RAM 82 and / or ROM 93 may be controlled by memory controller 92. Memory controller 92 may provide an address translation function that translates virtual addresses into physical addresses as instructions are executed. Memory controller 92 may also provide a memory protection function that isolates processes within the system and isolates system processes from user processes. Thus, a program running in a first mode may access only memory mapped by its own process virtual address space; it may not be able to access memory within another process’s virtual address space unless memory sharing between the processes has been set up.

[0260] In addition, computing system 90 may comprise peripherals controller 83 responsible for communicating instructions from processor 91 to peripherals, such as printer 94, keyboard 84, mouse 95, and disk drive 85.

[0261] Display 86, which is controlled by display controller 96, is used to display visual output generated by computing system 90. Such visual output may comprise text, graphics, animated graphics, and video. The visual output may be provided in the form of a graphical user interface (GUI). Display 86 may be implemented with a CRT-based video display, an LCDbased flat-panel display, gas plasma-based flat-panel display, or a touch-panel. Display controller 96 comprises electronic components required to generate a video signal that is sent to display 86.

[0262] Further, computing system 90 may comprise communication circuitry, such as for example a network adapter 97, that may be used to connect computing system 90 to an external communications network, such as the RAN 103 / 104 / 105, Core Network 106 / 107 / 109, PSTN 108, Internet 110, or Other Networks 112 of Figures 22A, 22B, 22C, 22D, and 22E, to enable the computing system 90 to communicate with other nodes or functional entities of those networks. The communication circuitry, alone or in combination with the processor 91, may be used to perform the transmitting and receiving steps of certain apparatuses, nodes, or functional entities described herein.

[0263] Figure 22G illustrates one embodiment of an example communications system 111 in which the methods and apparatuses described and claimed herein may be embodied. As shown, the example communications system 111 may comprise wireless transmit / receive units (WTRUs) A, B, C, D, E, F, a base station, a V2X server, and a RSUs A and B, though it will be appreciated that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. One or several or all WTRUs A, B, C, D, E can be out of range of the network (for example, in the figure out of the cell coverage boundary shown as the dash line). WTRUs A, B, C form a V2X group, among which WTRU A is the group lead and WTRUs B and C are group members. WTRUs A, B, C, D, E, F may communicate over Uu interface or Sidelink (PC5) interface.

[0264] It is understood that any or all of the apparatuses, systems, methods and processes described herein may be embodied in the form of computer executable instructions (e.g., program code) stored on a computer-readable storage medium which instructions, when executed by a processor, such as processors 118 or 91, cause the processor to perform and / or implement the systems, methods and processes described herein. Specifically, any of the steps, operations or functions described herein may be implemented in the form of such computer executable instructions, executing on the processor of an apparatus or computing system configured forwireless and / or wired network communications. Computer readable storage media comprise volatile and nonvolatile, removable and non-removable media implemented in any non-transitory (e.g., tangible or physical) method or technology for storage of information, but such computer readable storage media do not comprise signals. Computer readable storage media comprise, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD- ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other tangible or physical medium which may be used to store the desired information and which may be accessed by a computing system.

Claims

What is claimed is:

1. A method comprising: receiving, by a spatial mapping server and from at least one of a first vertical application layer (VAL) server or a first spatial mapping client, a first request to create a spatial map, wherein the first request comprises an area of interest, an access control policy associated with the spatial map, and one or more requested layers of information associated with the spatial map; creating, based on the first request, the spatial map for the area of interest comprising the one or more requested layers of spatial map information; generating a spatial map identifier associated with the spatial map; sending a response to the at least one first VAL server or first spatial mapping client, the response comprising the spatial map identifier and an indication of at least one of a successful creation of the spatial map or a failure to create the spatial map; receiving, from at least one of a second VAL server or a second spatial mapping client, a second request, wherein the second request comprises spatial map discovery criteria and an identifier of at least one of the second VAL server or the second spatial mapping client; determining, based on the access control policy associated with the spatial map and the identifier of the at least one of the second VAL server or the second spatial mapping client, at least one of a permission to discover the spatial map or a denial of discovery of the spatial map; determining the spatial map matches the spatial map discovery criteria; and sending, to the at least one of the second VAL server or the second spatial mapping client, a second response comprising an indication of the spatial map.

2. The method of claim 1, wherein the spatial map discovery criteria comprises an area of interest.

3. The method of claim 1, wherein the indication of the spatial map comprises the spatial map identifier.

4. The method of claim 1, wherein the creating the spatial map further comprises determining one or more spatial anchors associated with the spatial map.

5. The method of claim 4, wherein determining the one or more spatial anchors associated with the spatial map further comprises: sending, to a spatial anchor server, a request comprising spatial map information associated with the spatial map; and receiving, from the spatial anchor server, a response comprising one or more spatial anchors associated with the spatial map.

6. The method of claim 4, wherein each one of the one or more spatial anchors associated with the spatial map comprise a spatial anchor identifier.

7. The method of claim 4, wherein each one of the one or more spatial anchors associated with the spatial map is associated with a location in the spatial map.

8. The method of claim 1, further comprising: receiving, from a user device associated with the second spatial mapping client, a subscription request associated with the spatial map; sending, to the user device and in response to the subscription request, subscription information associated with the spatial map; and sending, to the user device, one or more notifications associated with the spatial map.

9. An apparatus comprising one or more processors and memory storing instructions which, when executed by the one or more processors, cause the apparatus to: send, to a spatial mapping server and by a spatial mapping client of the apparatus, a first request to create a spatial map, wherein the first request comprises an area of interest, an access control policy associated with the spatial map, and one or more requested layers of information associated with the spatial map; receive a response from the spatial mapping server, the response comprising an identifier associated with the spatial map and an indication of at least one of a successful creation of the spatial map or an indication of a failure to create the spatial map;send, to the spatial mapping server, a second request, wherein the second request comprises spatial map discovery criteria and an identifier of the spatial mapping client of the apparatus; and receive, from the spatial mapping server and based on the spatial map discovery criteria, a second response comprising an indication of the spatial map.

10. The apparatus of claim 9, wherein the spatial map discovery criteria comprises an area of interest.

11. The apparatus of claim 9, wherein the receiving the second response comprises receiving an identifier of a second spatial map matching the spatial map discovery criteria.

12. The apparatus of claim 9, wherein the first request to create the spatial map comprises a request to associate one or more spatial anchors with the spatial map.

13. The apparatus of claim 12, wherein the one or more spatial anchors associated with the spatial map each correspond to a location in the spatial map.

14. The apparatus of claim 9, wherein the instructions, when executed, further cause the apparatus to: send, to the spatial mapping server, a subscription request associated with the spatial map; receive subscription information associated with the spatial map; subscribe, based on the receiving the subscription information, with the spatial map; and receive one or more notifications associated with the spatial map.

15. An apparatus comprising one or more processors and memory storing instructions which, when executed by the one or more processors, cause the apparatus to: receive, by a spatial mapping server and from at least one of a first vertical application layer (VAL) server or a first spatial mapping client, a first request to create a spatial map,wherein the first request comprises an area of interest, an access control policy associated with the spatial map, and one or more requested layers of information associated with the spatial map; create, based on the first request, the spatial map for the area of interest comprising the one or more requested layers of spatial map information; generate a spatial map identifier associated with the spatial map; send a response to the at least one first VAL server or first spatial mapping client, the response comprising the spatial map identifier and an indication of at least one of a successful creation of the spatial map or a failure to create the spatial map; receive, from at least one of a second VAL server or a second spatial mapping client, a second request, wherein the second request comprises spatial map discovery criteria and an identifier of at least one of the second VAL server or the second spatial mapping client; determine, based on the access control policy associated with the spatial map and the identifier of the at least one of the second VAL server or the second spatial mapping client, at least one of a permission to discover the spatial map or a denial of discovery of the spatial map; determine the spatial map matches the spatial map discovery criteria; and send, to the at least one of the second VAL server or the second spatial mapping client, a second response comprising an indication of the spatial map.

16. The apparatus of claim 15, wherein the spatial map discovery criteria comprises an area of interest.

17. The apparatus of claim 15, wherein the indication of the spatial map comprises the spatial map identifier.

18. The apparatus of claim 15, wherein the creating the spatial map further comprises determining one or more spatial anchors associated with the spatial map.

19. The apparatus of claim 18, wherein determining the one or more spatial anchors associated with the spatial map further comprises: sending, to a spatial anchor server, a request comprising spatial map information associated with the spatial map; andreceiving, from the spatial anchor server, a response comprising one or more spatial anchors associated with the spatial map.

20. The apparatus of claim 18, wherein each one of the one or more spatial anchors associated with the spatial map comprise a spatial anchor identifier.

Images