Indication of user environment context within location-based service architecture

Abstract

A method includes receiving, by a first device, a request from a second device, the request including a query of an environmental context of a first user equipment (UE), where the environmental context indicates an indoor location or an outdoor location. A first device receives, from a second device, first context data related to an environmental context of a first UE. Based on the first context data, the first device estimates an environmental context of the first UE as an indoor location or an outdoor location, and sends a first message to the second device, the first message including the environmental context.

Description

Technical Field

[0001] Various example embodiments generally relate to wireless networks, and more particularly, to an indication of a user's environmental context (indoor / outdoor) within a location-based service architecture. Background Art

[0002] The positioning function of the fifth-generation (5G) system provides the ability to determine the geographical location (and / or speed) of a user equipment (UE) based on measured radio signals. The positioning information can be requested by a client associated with the UE (e.g., an application) and reported to the client associated with the UE, or requested by a client within or attached to the 5G core network and reported to the client of the 5G core network.

[0003] The positioning information can be obtained via the location-based service architecture of the 5G system. This positioning information can be utilized by one or more location-based services. Additionally, some location-based services (e.g., emergency services such as E112 / E911 calls) require very high-accuracy location data context, the accuracy of which is specified by regulatory rules. Summary of the Invention

[0004] In one aspect of the present disclosure, a method includes: receiving, by a first device, a request from a second device, the request including a query for the environmental context of a first user equipment (UE), wherein the environmental context indicates an indoor location or an outdoor location. The first device receives first context data related to the environmental context of the first UE from the second device. Based on the first context data, the first device estimates the environmental context of the first UE as an indoor location or an outdoor location, and sends a first message to the second device, the first message including the environmental context.

[0005] In one aspect of the method, the method further includes: determining the accuracy of the estimated environmental context.

[0006] In one aspect of the method, the first message includes: an indication of the accuracy of the estimated environmental context.

[0007] In one aspect of the method, the request from the second device is an Nlmf_Location_DetermineLocation request message.

[0008] In one aspect of the request, the request includes an environmental context attribute.

[0009] In one aspect of the request, the request includes a location and an environmental attribute.

[0010] In one aspect of the method, the first message is an Nlmf_Location_DetermineLocation response message.

[0011] In one aspect of the method, the first message includes environmental context method usage attributes.

[0012] In one aspect of the method, the first message includes an accuracy attribute.

[0013] In one aspect of the method, the request from the second device is a Namf_Location_ProvidePositioningInfo request message.

[0014] In one aspect of the method, the request includes environmental context attributes.

[0015] In one aspect of the method, the request includes location and environmental attributes.

[0016] In one aspect of the method, the first message is a Namf_Location_ProvidePositioningInfo response message.

[0017] In one aspect of the method, the first message includes environmental context method usage attributes.

[0018] In one aspect of the method, the first message includes an accuracy attribute.

[0019] In one aspect of the method, the first device is a Location Management Function (LMF).

[0020] In one aspect of the method, the first device is an Access and Mobility Management Function (AMF).

[0021] In one aspect of the method, the first device is a Network Data Analytics Function (NWDAF).

[0022] In one aspect of the present disclosure, a device includes: at least one processor, and at least one memory storing instructions that, when executed by the at least one processor, cause the device to perform at least any one of the foregoing methods.

[0023] In one aspect of the present disclosure, a processor-readable medium stores instructions that, when executed by at least one processor of a device, cause the device to perform at least any one of the foregoing methods.

[0024] According to some aspects, the subject matter of the independent claims is provided. Some further aspects are defined in the dependent claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] Some example embodiments will now be described with reference to the accompanying drawings.

[0026] Figure 1Diagram of an example embodiment of a wireless network between a network system and a user equipment (UE) according to one illustrated aspect of the present disclosure;

[0027] Figure 2 Diagram of example components of a network system according to one illustrated aspect of the present disclosure;

[0028] Figure 3 Diagram of an example location-based system according to one illustrated aspect of the present disclosure;

[0029] Figure 4 Is a part of an example location-based system that provides environmental context according to one illustrated aspect of the present disclosure Figure 3 Block diagram of;

[0030] Figure 5 Diagram of an example embodiment of signals and operations between a UE, NG-RAN, AMF, LMF, GMLC, UDM, and a client according to one illustrated aspect of the present disclosure;

[0031] Figure 6 Diagram of an example embodiment of signals and operations between a UE, NG-RAN, AMF, LMF, GMLC / LRF, and a client according to one illustrated aspect of the present disclosure;

[0032] Figure 7A and 7B Diagram of an example embodiment of signals and operations between a UE, NG-RAN, AMF, LMF, VGMLC, HGMLC, UDM, LCS client, NEF, AF, and an NF according to one illustrated aspect of the present disclosure;

[0033] Figure 8 Diagram of an example embodiment of analyzing signals and operations between a consumer and an NWDAF according to one illustrated aspect of the present disclosure; and

[0034] Figure 9 Diagram of an example embodiment of components of a UE or a network device according to one illustrated aspect of the present disclosure. Detailed Description

[0035] In the following description, certain specific details are set forth in order to provide a thorough understanding of the disclosed aspects. However, those skilled in the relevant art will recognize that the aspects may be practiced without one or more of these specific details or with other methods, components, materials, etc. In other instances, well-known structures associated with transmitters, receivers, or transceivers have not been shown or described in detail to avoid unnecessarily obscuring the description of the aspects.

[0036] References to "an aspect" or "aspects" throughout the specification mean that a particular feature, structure, or characteristic associated with that aspect is included in at least one aspect. Thus, the phrases "in one aspect" or "in aspects" that appear in various places throughout the specification do not necessarily all refer to the same aspect. Additionally, the particular features, structures, or characteristics may be combined in any suitable manner in one or more aspects.

[0037] The embodiments described in this disclosure may be implemented in a wireless network device, such as but not limited to devices utilizing Worldwide Interoperability for Microwave Access (WiMAX), Global System for Mobile Communications (GSM, 2G), GSM EDGE Radio Access Network (GERAN), General Packet Radio Service (GRPS), Wideband Code Division Multiple Access (W-CDMA)-based Universal Mobile Telecommunications System (UMTS, 3G), High Speed Packet Access (HSPA), Long Term Evolution (LTE), LTE Advanced, Enhanced LTE (eLTE), 5G New Radio (5G NR), 5G Advanced, 6G (and later), and 802.11ax (Wi-Fi 6), and other wireless network systems. The term "eLTE" herein represents the evolution of LTE connected to the 5G core. LTE is also known as Evolved UMTS Terrestrial Radio Access (EUTRA) or Evolved UMTS Terrestrial Radio Access Network (EUTRAN).

[0038] This disclosure may use the term "serving network device" to refer to a network node or network device (or a part thereof) that serves a UE. As used herein, the terms "sent to", "received from", and "cooperate" (and their variants) include communications that may or may not involve communication through one or more intermediate devices or nodes. The term "acquire" (and its variants) includes acquiring in a first instance or reacquiring after a first instance. The term "connected" may represent a physical connection or a logical connection.

[0039] This disclosure uses 5G NR as an example of a wireless network and may use a smartphone and / or an extended reality headset as an example of a UE. It is intended and should be understood that these examples are merely illustrative and this disclosure is applicable to other wireless networks and user devices.

[0040] Figure 1FIG. is an example of a wireless network between network system 100 and user equipment (UE) 150. Network system 100 may include one or more network nodes 120, one or more servers 110, and / or one or more network devices 130 (e.g., test equipment). Network nodes 120 will be described in more detail below. As used herein, the term "network device" may refer to any component of network system 100, such as server 110, network node 120, network device 130, any of the foregoing components, and / or any other component(s) of network system 100. Examples of network devices include, but are not limited to, devices implementing aspects of 5G NR, etc. This disclosure describes embodiments related to 5G NR and embodiments related to aspects defined by the Third Generation Partnership Project (3GPP). However, it should be envisioned that embodiments related to other wireless network technologies are also included within the scope of this disclosure.

[0041] The following description provides further details of an example of a network node. In a 5G NR network, a gNodeB (also referred to as gNB) may include, for example, a node that provides new radio (NR) user plane and control plane protocol termination to the UE and is connected to the 5G Core (5GC) via the NG interface, e.g., according to 3GPP TS 38.300 V16.6.0 (2021-06), section 3.2, which is hereby incorporated by reference herein.

[0042] The gNB supports various protocol layers, such as layer 1 (L1) - physical layer, layer 2 (L2), and layer 3 (L3).

[0043] Layer 2 (L2) of NR is divided into the following sub-layers: Media Access Control (MAC), Radio Link Control (RLC), Packet Data Convergence Protocol (PDCP), and Service Data Adaptation Protocol (SDAP), where, for example:

[0044] o The physical layer provides a transport channel to the MAC sub-layer;

[0045] o The MAC sub-layer provides a logical channel to the RLC sub-layer;

[0046] o The RLC sub-layer provides an RLC channel to the PDCP sub-layer;

[0047] o The PDCP sub-layer provides a radio bearer to the SDAP sub-layer;

[0048] o The SDAP sub-layer provides a Quality of Service (QoS) flow to the 5GC;

[0049] o Control channels include Broadcast Control Channel (BCCH) and Physical Control Channel (PCCH).

[0050] Layer 3 (L3) includes, for example, Radio Resource Control (RRC), for example, according to 3GPP TS 38.300 V16.6.0 (2021-06), part 6, which is hereby incorporated by reference herein.

[0051] The gNB Central Unit (gNB-CU) includes, for example, a logical node that hosts, for example, the Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP), and Packet Data Convergence Protocol (PDCP) protocols of the gNB or the RRC and PDCP protocols of the en-gNB, and controls the operation of one or more gNB Distributed Units (gNB-DUs). The gNB-CU terminates the F1 interface connected to the gNB-DU. The gNB-CU may also be referred to herein as the CU, Central Unit, Centralized Unit, or Control Unit.

[0052] The gNB Distributed Unit (gNB-DU) includes, for example, a logical node that hosts the Radio Link Control (RLC), Media Access Control (MAC), and Physical (PHY) layers of the gNB or en-gNB, and whose operation is partially controlled by the gNB-CU. One gNB-DU supports one or more cells. One cell is supported by only one gNB-DU. The gNB-DU terminates the F1 interface connected to the gNB-CU. The gNB-DU may also be referred to herein as the DU or Distributed Unit.

[0053] As used herein, the term "network node" may refer to any one of, or any combination of, a gNB, gNB-CU, or gNB-DU. A RAN (Radio Access Network) node or network node (e.g., a gNB, gNB-CU, or gNB-DU) or a part thereof may be implemented using, for example, a device having at least one processor and / or at least one memory having processor-readable instructions ("program") that are configured to support and / or provide and / or process CU- and / or DU-related functions and / or features, and / or at least one protocol (sub) layer of the RAN (Radio Access Network), such as layer 2 and / or layer 3. There may be different functional divisions between the central unit and the distributed unit. Examples of such devices and components will be described below in connection with Figure 9 are described.

[0054] The gNB-CU and gNB-DU parts can be co-located or physically separated, for example. The gNB-DU can even be further divided into two parts, for example, one part includes a processing device and the other part includes antennas. The Central Unit (CU) can also be referred to as a Baseband Unit / Radio Equipment Controller / Cloud RAN / Virtual RAN (BBU / REC / C-RAN / V-RAN), Open RAN (O-RAN), or a part thereof. The Distributed Unit (DU) can also be referred to as a Remote Radio Head / Remote Radio Unit / Radio Equipment / Radio Unit (RRH / RRU / RE / RU), or a part thereof. Hereinafter, in various exemplary embodiments of the present disclosure, a network node that supports at least one of the Central Unit function or the Layer 3 protocol of the Radio Access Network can be, for example, a gNB-CU. Similarly, a network node that supports at least one of the Distributed Unit function or the Layer 2 protocol of the Radio Access Network can be, for example, a gNB-DU.

[0055] The gNB-CU can support one or more gNB-DUs. The gNB-DU can support one or more cells and thus can support a serving cell for a User Equipment (UE) or candidate cells for other processes such as handover, dual connectivity, and / or carrier aggregation.

[0056] The User Equipment (UE) 150 can be or include a wireless or mobile device, a device with a radio interface for interacting with the RAN (Radio Access Network), a smartphone, a vehicle-mounted device, an IoT device, or other types of user equipment such as an M2M device. Such a UE 150 can include: at least one processor; and at least one memory including program code; wherein the at least one memory and the computer program code are configured to, together with the at least one processor, cause the device to perform at least certain operations, such as, for example, an RRC connection with the RAN. Examples of the components of the UE will be described in conjunction with Figure 9 will be described. In an embodiment, the UE 150 can be configured to generate a message to be sent to the RAN via radio (e.g., including a cell ID) (e.g., to reach and communicate with a serving cell). In an embodiment, the UE 150 can generate and send and receive an RRC message containing one or more RRC PDUs (Packet Data Units). Those skilled in the art will understand the RRC protocol and other processes that the UE can perform.

[0057] Continuing to refer to Figure 1, in an example of a 5G NR network, network system 100 provides one or more cells that define the coverage area of network system 100. As described above, network system 100 may include a gNB of a 5G NR network, or may include any other device configured to control radio communications and manage radio resources within a cell. As used herein, the term "resource" may refer to radio resources such as resource blocks (RBs), physical resource blocks (PRBs), radio frames, subframes, time slots, subbands, frequency regions, subcarriers, beams, etc. In an embodiment, network node 120 may be referred to as a base station.

[0058] Figure 1 Examples are provided and only network system 100 and UE 150 are illustrated. Those skilled in the art will understand that network system 100 includes components not shown in FIG. 1, and will understand that other user devices may communicate with network system 100.

[0059] Figure 2 is Figure 1 A block diagram of example components of network system 100. A 5G NR network may be described as an example of network system 100, and it is intended that the aspects described below should also apply to other types of network systems. The network system may operate according to Figure 1 the signals and connections shown such that UE 150 communicates with network system 100 via radio access network 225. Additionally, the network system may be divided into user plane components and functions and control plane components and functions as shown and described herein. Unless otherwise specified, the terms "component", "function", and "service" may be used interchangeably herein, and they may refer to instructions executed by one or more processors and implemented thereby.

[0060] Example functions of the components are described below. The example functions are illustrative only, and it should be understood that additional operations and functions may be performed by the components described herein. Additionally, the connections between components may be virtual connections over service interfaces such that any component may communicate with any other component. In this way, any component may act as a service "producer" for any other component that is a service "consumer" to provide services for network functions.

[0061] For example, core network 210 is described in the control plane of the network system. Core network 210 may include an authentication server function (AUSF) 211, an access and mobility function (AMF) 212, and a session management function (SMF) 213. Core network 210 may also include a network slice selection function (NSSF) 214, a network exposure function (NEF) 215, a network repository function (NRF) 216, and a unified data management function (UDM) 217, which may include a unified data repository (UDR) 224.

[0062] Additional components and functions of the core network 210 may include an application function 218, a policy control function (PCF) 219, a network data analytics function (NWDAF) 220, an analytics data repository function (ADRF) 221, a management data analytics function (MDAF) 222, and an operations and management function (OAM) 223.

[0063] The user plane includes a UE 150, a radio access network (RAN) 225, a user plane function (UPF) 226, and a data network (DN) 227. The RAN 225 may include one or more components described in relation to Figure 1 related descriptions, such as one or more network nodes. However, the RAN 225 may not be limited to such components. The UPF 226 provides connectivity for data sent through the RAN 225. For example, the DN 226 identifies services from service providers, Internet access, and third-party services.

[0064] The AMF 212 handles connection and mobility tasks. The AUSF 211 receives an authentication request from the AMF 212 and interacts with the UDM 217 to authenticate and verify network responses for the determination of successful authentication. The SMF 213 performs packet data unit (PDU) session management and manages the session context with the UPF 226.

[0065] The NSSF 214 may select a network slice instance (NSI) and determine the allowed network slice selection assistance information (NSSAI). This selection and determination are used to configure the AMF 212 to provide services to the UE 150. The NEF 215 ensures access to network services for third parties to create specialized network services. The NRF 216 acts as a repository to store network functions to allow these functions to register and discover each other.

[0066] The UDM 217 generates authentication vectors for use by the AUSF 211 and the ADM 212 and provides user identity handling. The UDM 217 may be connected to the UDR 224, which stores data associated with authentication, applications, etc. The AF 218 provides application services to users (e.g., streaming services, etc.). The PCF 219 provides policy control functions. For example, the PCF 219 may assist in network slicing and mobility management, as well as provide quality of service (QoS) and charging functions.

[0067] The NWDAF 220 collects data (e.g., from the UE 150 and the network system) to perform network analysis and provide insights to the functions that utilize the analysis in service provisioning. The ADRF 221 allows for the storage, retrieval, and removal of consumer data and analytics. The MDAF 222 provides additional data analytics services for network functions. The OAM 223 provides configuration and management processing functions to manage elements in the network or connected to the network (e.g., the UE 150, network nodes, etc.).

[0068] Figure 2 These are merely examples of components of the network system, and variations are considered to be within the scope of the present disclosure. In an embodiment, the network system may include Figure 2 other components not shown herein. In an embodiment, the network system may not include Figure 2 each component shown herein. In an embodiment, the components and connections may be implemented with connections different from those shown in Figure 2 herein. Such and other embodiments are considered to be within the scope of the present disclosure.

[0069] Although further details will be provided below, the positioning function of the 5G system is based on measuring radio signals to provide a determination of the geographical location (and / or speed) of the UE. The positioning information may be requested by a client associated with the UE (e.g., an application / location-based service) or by a client / location-based service within or attached to the core network and reported to that client. In various embodiments, the positioning information may be reported in a format known to those skilled in the art (such as a format for cell-based or geographical coordinates), along with the estimated error (uncertainty) of the UE's positioning and speed and (if available) the positioning method (or a list of methods) used to obtain the positioning estimate.

[0070] In various embodiments, multiple types of environmental context may also be included. For example, context such as whether the user is at home, at work, or in a moving vehicle (e.g., a car or a train) may be considered environmental context. For example, in various embodiments, the indoor location context may indicate whether the user is at home, at work, or in a vehicle based on the user's geographical location.

[0071] In various embodiments, the network (e.g., the RAN or the core network) may request this indication to help optimize its own network functions (e.g., handover to obtain better QoE for video applications and slice selection to switch from a slice with more flexible resources to an elastic slice (allocated more resources / processing to provide good radio coverage)).

[0072] As described above, some location-based services (e.g., emergency services such as E112 / E911 calls) require very high-accuracy location data context, the accuracy of which is specified by regulatory rules. However, a single location technology may be difficult to meet various location requirements in different environments. In various embodiments, the 5G system involves selecting an appropriate location technology according to the environment (indoor or outdoor).

[0073] Therefore, quickly detecting the indoor / outdoor context may be valuable for location methods, especially if the accuracy of location measurements is crucial and mandatory, depending on the service that requires it. In various embodiments, independent environmental context information is also essential for commercial and internal services or regulatory services that expect to complete to supplement location data.

[0074] For example, having environmental context information may help quickly locate a user if the emergency service also knows whether the user is indoor or outdoor in addition to the location estimate, especially if the latter is not very accurate. Other examples, such as metaverse applications, ultra-reliable and low-latency communication (URLLC) services (such as virtual reality or augmented reality) or automated guided vehicles in industrial environments, can utilize the context in which the user or device is located to automatically determine the method used or adjust visual content.

[0075] As described in more detail below in this document, in various embodiments, the methods and apparatuses in the automation framework provide an accurate indication of the context (e.g., indoor / outdoor) to the location-based service that requests it. In various embodiments, assistance can be provided to a system including location and positioning methods. The apparatus and the system are within the same sub-network of the network infrastructure (CORE or RAN), which greatly limits additional latency. In various embodiments, the location and environmental context calculation can be based on measuring radio signals (e.g., existing 3GPP radio standard data). For example, the context of the target UE can be continuously monitored in the idle mode or during a call.

[0076] As used herein, communication with the radio access network (RAN) can refer to and represent communication with a part of the RAN (e.g., with a network node (e.g., DU and / or CU)) or another part of the RAN. As used herein, communication with the core network can refer to and represent communication with one or more services / applications of the core network (e.g., AMF or another service of the core network).

[0077] As used herein, terms such as "first" and "second" can refer to the first or second instance of a message sent / received by a component (e.g., UE, apparatus, etc.), or the first component or the second component in the sequence of said components. Therefore, these terms are used in a non-limiting manner and can refer to any message, operation, device, component, etc.

[0078] According to the brief description, Figure 3 is a diagram of an exemplary location-based system 300 according to an exemplary aspect of the present disclosure. As Figure 3 shown, various components similar to Figure 1 and Figure 2 can be included. In various embodiments, the system 300 may include a location acquisition function 311, a location management function 312, a Gateway Mobile Location Center (GMLC) 313, and a Location Service (LCS) client 314.

[0079] In various embodiments, the AF and NF may access the LCS service from the GMLC in the same trust domain (e.g., in the same Public Land Mobile Network (PLMN)) using the Ngmlc interface, or use the Namf interface to expose events using location information from the AMF in the same trust domain. The NWDAF may collect UE location information by directly accessing the GMLC. The LCS client may access the LCS service from the GMLC using the Le reference point.

[0080] In various embodiments, the GMLC may be the first node accessed by an external LCS client in the PLMN (e.g., the Le reference point is supported by the GMLC). The AF and NF may access the GMLC directly or via the NEF. After performing authorization for the external LCS client or AF and verifying the target UE privacy, the GMLC forwards the location request to the serving AMF using the Namf interface, or forwards the location request to the GMLC in another PLMN using the Ngmlc interface in the case of a roaming UE.

[0081] As Figure 3 shown, the AMF may access the GMLC and NEF via the Namf interface, access the RAN via the N2 reference point, and access the UE via the N1 reference point. In various embodiments, the AMF performs to support location services including one or more of the following functions (among other functions): initiate a network-induced request and receive and manage location requests from the GMLC or UE; receive and manage event exposure requests for location information from the NEF, and / or select the LMF.

[0082] In various embodiments, the LMF manages the overall coordination and scheduling of resources required for the location of UEs registered to or accessing the 5GCN. The LMF may receive location requests for target or multiple UE location requests from the serving AMF (for the GMLC or for the UE) using the Nlmf interface. Depending on the positioning method selected by the LMF, the positioning of the UE may be estimated by the NG-RAN node, the LMF, or the UE itself.

[0083] For example, in various embodiments, UE-assisted (LMF-based) positioning may include position calculation by network resources based on radio ranging measurements provided by the UE. The UE obtains position measurements and sends the measurement results to another entity for position calculation. The network may broadcast assistance information to the mobile device, which enables the mobile device to obtain appropriate radio ranging measurements.

[0084] In various embodiments, network-based (NG-RAN-assisted) positioning may include the serving PLMN obtaining position measurements of signals sent by the target UE and calculating a position estimate.

[0085] In various embodiments, UE-based positioning may be supported by UE resources based on broadcast position assistance information. The UE obtains position measurements and uses the assistance data provided by the serving PLMN to calculate a position estimate.

[0086] In various embodiments, stand-alone (UE-based) positioning may be supported by UE resources. The UE obtains position measurements and calculates a position estimate without using the assistance data provided by the serving PLMN.

[0087] In various embodiments, the LMF interacts with the UE to exchange position information applicable to various positioning methods and interacts with the NG-RAN for various methods to obtain position information. The LMF may also calculate or verify the final position and any speed estimates and may estimate the achieved accuracy.

[0088] In various embodiments, the LMF may support one or more of the following: UE position estimation for a given area; for one or more UEs (with two available positioning versions (UE or NG-RAN / LMF)), the LMF may decide whether to perform positioning estimation based on UE conditions; determination of indoor or outdoor for UE position estimation; and / or sending the UE position estimate to the AMF or directly to the GMLC for the target UE.

[0089] According to the brief description, Figure 4 is a block diagram of a portion of an example location-based system 400 that provides environmental context Figure 3 in accordance with an exemplary aspect of the present disclosure.

[0090] As Figure 4 shown, in various embodiments, a context detection system (CDS) that operates / cooperates with a system including positioning and location methods may detect environmental context (e.g., indoor or outdoor location).

[0091] In various embodiments, the CDS may be located in the NWDAF. However, the CDS may be located elsewhere (e.g., in the LMF or AMF). In various embodiments, the LMF includes a positioning and location system and communicates with the NWDAF and the AMF, which in turn communicate with the GMLC to communicate with location-based service clients (e.g., E911, etc.). The CDS may receive context data assistance (e.g., reference signal received power (RSRP), timing advance (TA), etc.) from the NG-RAN communicating with the UE.

[0092] In various embodiments, the CDS may receive context data assistance from the LMF and the AMF. In various embodiments, the indoor / outdoor environment context and the context method used to determine the environmental context (S*) may be provided to the location-based service client from the CDS via the LMF, the AMF, and the GMLC, respectively. Although various interfaces are shown, other interfaces known to those skilled in the art may be utilized.

[0093] The CDS may be triggered by default to assist in automatically and systematically selecting an appropriate location / location method (e.g., as described above). In various embodiments, an indoor / outdoor indication is sent to the LCS client when one or more conditions are met. For example, in various embodiments, when the LCS service requests this indication and the service is authorized to obtain the indication for location-based services. In various embodiments, there are one or more usage categories of location services (e.g., commercial LCS, internal LCS, emergency LCS, and lawful interception LCS).

[0094] In various embodiments, the CDS may be provided with radio measurements, while the location / location system may receive various types of location information (including radio measurements). These two systems may be linked using a closed-loop interface including two interfaces (e.g., Int1 and Int2). In various embodiments, Int1 conveys estimated context information (indoor / outdoor) to the location-based service and the location positioning system, while Int2 conveys the estimated coordinates of the target user to the CDS.

[0095] In various embodiments, the CDS may include a module that includes indoor / outdoor detection using machine learning (ML) / dynamic learning (DL) methods. In various embodiments, the ML / DL methods may be combined with a user behavior optimizer that implements user environment detection (UED), such as indoor / outdoor detection (IOD). The model may detect the user environment by processing standard 3GPP radio measurements (e.g., RSRP, reference signal received quality (RSRQ), TA, and channel quality indicator (CQI)). In various embodiments, radio metadata such as cell ID and timestamp may be utilized.

[0096] In various embodiments, a module including a convex hull-based data classification method may be included in a CDS. As an input, a convex hull algorithm takes a set of points as input, represented as coordinates (x, y) in a 2D plane. Computational geometry algorithms may be used to find the smallest convex polygon enclosing a given set of points in the 2D plane, and the outermost points forming the convex shape may be identified.

[0097] According to the brief description, Figure 5 is a diagram of an example embodiment of signals and operations among a UE, NG-RAN, AMF, LMF, GMLC, UDM, and a client according to an exemplary aspect of the present disclosure. In various embodiments, Figure 5 the components shown in may correspond to similar components described above in Figure 1 , 2 , 3, and 4. The following paragraphs will describe various signals and operations. It will be understood that the described signals may have associated operations, and the described operations may have associated signals. In various embodiments, Figure 5 the signals and operations shown in may be utilized by a regulatory location service.

[0098] At operation 501, an external client (e.g., an LCS client) sends an LCS service request message to the GMLC, and the GMLC receives the LCS service request message. In various embodiments, the LCS service request message includes environmental context attributes as well as location and environmental attributes.

[0099] At operation 502, the GMLC sends a Nudm_UECM_GetRequest message to the UDM, and the UDM receives the Nudm_UECM_GetRequest message. In response to the Nudm_UECM_GetRequest message, at operation 503, the UDM sends a Nudm_UECM_GetResponse message to the GMLC, and the GMLC receives the Nudm_UECM_GetResponse message.

[0100] At operation 504, the GMLC sends a Namf_Location_ProvidePositiongInfo request message including environmental context as well as location and environmental attributes to the AMF, and the AMF receives the Namf_Location_ProvidePositiongInfo request message.

[0101] At operation 505, a network-triggered service request occurs, and at operation 506, the AMF performs LMF selection. At operation 507, the AMF sends an Nlmf_Location_DetermineLocationRequest message to the LMF, including the context of the environment and location and environmental attributes, and the LMF receives the Nlmf_Location_DetermineLocationRequest message.

[0102] At operation 508, UE positioning is determined. At operation 509, the LMF sends an Nlmf_Location_DetermineLocationResponse message to the AMF, including an environmental indication (e.g., indoor or outdoor), the use of the environmental context method, and the accuracy (cAccuracy) attribute, and the AMF receives the Nlmf_Location_DetermineLocationResponse message.

[0103] At operation 510, the AMF sends a Namf_Location_ProvidePositioningInfo response message to the GMLC, and the GMLC receives the Namf_Location_ProvidePositioningInfo response message. In various embodiments, the Namf_Location_ProvidePositioningInfo response message includes an environmental indication (e.g., indoor or outdoor), the use of the environmental context method, and the accuracy (cAccuracy) attribute.

[0104] At operation 511, the GMLC sends an LCS service response message to the external client, including an environmental context indication (e.g., indoor or outdoor), the use of the environmental context method, and the accuracy (cAccuracy), and the external client receives the LCS service response message.

[0105] Figure 5 The operations are merely illustrative, and variations are considered to be within the scope of the present disclosure. In an embodiment, the operations may include Figure 5 other operations not shown in Figure 5 In an embodiment, the operations may not include Figure 5 each operation shown in Figure 5 In an embodiment, the operations may be implemented in an order different from the order shown in

[0106] According to the brief description,Figure 6 This is a diagram of an exemplary embodiment of signals and operations among a UE, NG-RAN, AMF, LMF, GMLC / LRF, and a client according to an exemplary aspect of the present disclosure. In various embodiments, Figure 6 the components shown in Figure 1 、 2 、3, and 4 may correspond to similar components described above in Figure 6 The signals and operations shown in

[0107] At operation 601, a trigger occurs for the AMF to initiate a 5GC network-induced location request (5GC-NI-LR). At operation 602, the AMF sends an Nlmf_Location_DetermineLocation request message to the LMF, and the LMF receives the Nlmf_Location_DetermineLocation request message. In various embodiments, the Nlmf_Location_DetermineLocation request message includes environmental context attributes, as well as location and environmental attributes.

[0108] At operation 603, the UE location is determined. At operation 604, the LMF sends an Nlmf_Location_DetermineLocation response message to the AMF, and the AMF receives the Nlmf_Location_DetermineLocation response message. In various embodiments, the Nlmf_Location_DetermineLocation request message includes an environmental indication (e.g., indoor or outdoor) and an environmental context method usage attribute.

[0109] At operation 605, the AMF sends a Namf_Location_EventNotify message to the GMLC / LRF, and the GMLC / LRF receives the Namf_Location_EventNotify message. In various embodiments, the Namf_Location_EventNotify message includes an environmental indication (e.g., indoor or outdoor), the environmental context method used, and an accuracy attribute.

[0110] At operation 606, the GMLC / LRF sends a location information message to an external client, and the external client receives the location information message. In various embodiments, the location information message includes an environmental indication (e.g., indoor or outdoor), the environmental context method used, and an accuracy attribute.

[0111] At operation 607, the emergency protocol data unit (PDU) session is released. At operation 608, the AMF sends a Namf_Location_EventNotify message to the GMLC / LRF, and the GMLC / LRF receives the Namf_Location_EventNotify message. In various embodiments, the Namf_Location_EventNotify message includes an environment indication (e.g., indoor or outdoor), the environmental context method used, and an accuracy attribute.

[0112] Figure 6 The operations described are merely illustrative, and variations are considered to be within the scope of the present disclosure. In an embodiment, the operations may include Figure 6 other operations not shown in Figure 6 In an embodiment, the operations may not include Figure 6 each operation shown in Figure 6 In an embodiment, the operations may be implemented in an order different from the order shown in

[0113] Such and other embodiments are considered to be within the scope of the present disclosure. Those skilled in the art will understand that although various example components are described as performing various functions, other components may perform Figure 7A and 7B FIGS. Figure 1 and 2 are diagrams of example embodiments of signals and operations between a UE, NG-RAN, AMF, LMF, access GMLC (VGMLC), home GMLC (HGMLC), UDM, LCS client, NEF, AF, and NF according to an illustrative aspect of the present disclosure. In various embodiments, the components shown in FIG. 7 may correspond to similar components described above in Figure 7A and 7B The signals and operations shown in FIGS.

[0114] At operation 701a, the LCS client sends an LCS service request to the HGMLC, and the HGMLC receives the LCS service request. In various embodiments, the LCS service request includes environmental context attributes as well as location and environmental attributes.

[0115] At operation 701b-1, the AF sends an Nnef_EventExposure subscription message to the NEF, and the NEF receives the Nnef_EventExposure subscription message. At operation 701b-2, the NEF sends an Ngmlc_Location_ProvideLocation request message to the HGMLC, and the HGMLC receives the Ngmlc_Location_ProvideLocation request message. In various embodiments, the Ngmlc_Location_ProvideLocation request message includes environmental context attributes as well as location and environmental attributes.

[0116] At operation 701c, the NF sends an Ngmlc_Location_ProvideLocation request message to the HGMLC, and the HGMLC receives the Ngmlc_Location_ProvideLocation request message. In various embodiments, the Ngmlc_Location_ProvideLocation request message includes environmental context attributes as well as location and environmental attributes.

[0117] At operation 702, the HGMLC exchanges an Nudm_SDM_Get message with the UDM, which includes environmental context attributes as well as location and environmental attributes. At operation 703, the HGMLC exchanges an Nudm_UECM_Get message with the UDM.

[0118] At operation 704, the HGMLC sends an Ngmlc_Location_ProvideLocationRequest message to the VGMLC, and the VGMLC receives the Ngmlc_Location_ProvideLocationRequest message. In various embodiments, the Ngmlc_Location_ProvideLocationRequest message includes environmental context attributes as well as location and environmental attributes.

[0119] At operation 705, the VGMLC sends a Namf_Location_ProvidePositioningInfo request message to the AMF, and the AMF receives the Namf_Location_ProvidePositioningInfo request message. In various embodiments, the Namf_Location_ProvidePositioningInfo request message includes environmental context attributes as well as location and environmental attributes.

[0120] At operation 706, a network-triggered service request occurs. At operation 707, the AMF sends a NAS location notification invocation request message to the UE, and the UE receives the NAS location notification invocation request message.

[0121] At operation 708, the UE sends a NAS location notification return result message to the AMF, and the AMF receives the NAS location notification return result message. At operation 709, the AMF and the UDM exchange Nudm_ParameterProvision_Update messages.

[0122] At operation 710, LMF selection occurs. At operation 711, the AMF sends a Nlmf_Location_DetermineLocation request message to the LMF, and the LMF receives the Nlmf_Location_DetermineLocation request message. In various embodiments, the Nlmf_Location_DetermineLocation request message includes environmental context attributes as well as location and environmental attributes.

[0123] At operation 712, UE positioning is determined. At operation 713, the LMF sends a Nlmf_Location_DetermineLocation response message to the AMF, and the AMF receives the Nlmf_Location_DetermineLocation response message. In various embodiments, the Nlmf_Location_DetermineLocation response message includes an environmental indication (e.g., indoor or outdoor), the environmental context method used, and an accuracy attribute.

[0124] At operation 714, the AMF sends a Namf_Location_ProvidePositioningInfo response message to the VGMLC, and the VGMLC receives the Namf_Location_ProvidePositioningInfo response message. In various embodiments, the Namf_Location_ProvidePositioningInfo response message includes an environmental indication (e.g., indoor or outdoor), the environmental context method used, and an accuracy attribute.

[0125] At operation 715, the VGMLC sends a Ngmlc_Location_ProvideLocation response message to the HGMLC, and the HGMLC receives the Ngmlc_Location_ProvideLocation response message. In various embodiments, the Ngmlc_Location_ProvideLocation response message includes: environmental context attributes, and location and environmental attributes.

[0126] Privacy check is performed at operation 716. At operation 717, the HGMLC sends a Ngmlc_Location_ProvideLocation request message to the VGMLC, and the VGMLC receives the Ngmlc_Location_ProvideLocation request message. In various embodiments, the Ngmlc_Location_ProvideLocation request message includes: environmental context attributes, and location and environmental attributes.

[0127] At operation 718, the VGMLC sends a Namf_Location_ProvidePositioningInfo request message to the AMF, and the AMF receives the Namf_Location_ProvidePositioningInfo request message. In various embodiments, the Namf_Location_ProvidePositioningInfo request message includes: environmental context attributes, and location and environmental attributes.

[0128] At operation 719, a network-triggered service request occurs. At operation 720, the AMF sends a NAS location notification invocation request message to the UE, and the UE receives the NAS location notification invocation request message.

[0129] At operation 721, the UE sends a NAS location notification return result message to the AMF, and the AMF receives the NAS location notification return result message.

[0130] At operation 722, the AMF sends a Namf_location_ProvidePositioning response message to the VGMLC, and the VGMLC receives the Namf_location_ProvidePositioning response message. In various embodiments, the Namf_location_ProvidePositioning response message includes an environmental indication (e.g., indoor or outdoor), the environmental context method used, and an accuracy attribute.

[0131] At operation 723, the VGMLC sends a Ngmlc_Location_ProvideLocation response message to the HGMLC, and the HGMLC receives the Ngmlc_Location_ProvideLocation response message. In various embodiments, the Ngmlc_Location_ProvideLocation response message includes an environment indication (e.g., indoor or outdoor), the environmental context method used, and an accuracy attribute.

[0132] At operation 724a, the HGMLC sends an LCS service response message to the LCS client, and the LCS client receives the LCS service response message. In various embodiments, the LCS service response message includes an environment indication (e.g., indoor or outdoor), the environmental context method used, and an accuracy attribute.

[0133] At operation 724b-1, the HGMLC sends a Ngmlc_Location_ProvideLocation response message to the NEF, and the NEF receives the Ngmlc_Location_ProvideLocation response message. In various embodiments, the Ngmlc_Location_ProvideLocation response message includes an environment indication (e.g., indoor or outdoor), the environmental context method used, and an accuracy attribute.

[0134] At operation 724b-2, the NEF sends an Nnef_EventExposure_Notify message or an Nnef_EventExposure_Subscribe response message to the AF, and the AF receives the Nnef_EventExposure_Notify message or the Nnef_EventExposure_Subscribe response message. In various embodiments, the Nnef_EventExposure_Notify message or the Nnef_EventExposure_Subscribe response message includes an environment indication (e.g., indoor or outdoor), the environmental context method used, and an accuracy attribute.

[0135] At operation 724c, the HGMLC sends a Ngmlc_Location_ProvideLocation response message to the NF, and the NF receives the Ngmlc_Location_ProvideLocation response message. In various embodiments, the Ngmlc_Location_ProvideLocation response message includes an environment indication (e.g., indoor or outdoor), the environmental context method used, and an accuracy attribute.

[0136] The operations of FIG. 7 are merely illustrative, and variations are considered to be within the scope of the present disclosure. In an embodiment, the operations may include other operations not shown in FIG. 7. In an embodiment, the operations may not include every operation shown in FIG. 7. In an embodiment, the operations may be implemented in an order different from the order shown in FIG. 7. Such and other embodiments are considered to be within the scope of the present disclosure. Those skilled in the art will understand that although various example components are described as performing various functions, other components may perform those functions described in FIG. 7.

[0137] According to the brief description, Figure 8 is a diagram of an example embodiment that analyzes signals and operations between a consumer and an NWDAF according to an exemplary aspect of the present disclosure. In various embodiments, Figure 8 the components shown in may correspond to similar components described above in Figure 1 、 2 、3, and 4. The following paragraphs will describe various signals and operations. It will be understood that the described signals may have associated operations, and the described operations may have associated signals.

[0138] At operation 800, a machine learning (ML) model is trained for accurate positioning and made available to the NWDAF. At operation 801, an analytics consumer (e.g., a location-based service) sends an Nnwdaf_Analytics_Request / Nnwdaf_AnalyticsSubscription_Subscribe request message to the NWDAF, and the NWDAF receives the Nnwdaf_Analytics_Request / Nnwdaf_AnalyticsSubscription_Subscribe request message. In various embodiments, the Nnwdaf_Analytics_Request / Nnwdaf_AnalyticsSubscription_Subscribe request message may include an analytics ID, a location estimate, LCS assistance data, environmental context attributes, and context assistance data.

[0139] At operation 802, the NWDAF sends an Nnwdaf_Analytics_Request_Response / Nnwdar_AnalyticsSubscription_Notify message to the analytics consumer, and the analytics consumer receives the Nnwdaf_Analytics_Request_Response / Nnwdar_AnalyticsSubscription_Notify message. In various embodiments, the Nnwdaf_Analytics_Request_Response / Nnwdar_AnalyticsSubscription_Notify message includes location accuracy, environmental indication (e.g., indoor or outdoor), the environmental context method used, and accuracy attributes.

[0140] In various embodiments, data (e.g., environmental context data) may be associated with a timestamp.

[0141] Figure 8 The operations are merely illustrative and variations are considered to be within the scope of the present disclosure. In an embodiment, the operations may include Figure 8 other operations not shown in Figure 8 In an embodiment, the operations may not include Figure 8 each operation shown in Figure 8 In an embodiment, the operations may be implemented in an order different from the order shown in

[0142] Such embodiments and other embodiments are considered to be within the scope of the present disclosure. Those skilled in the art will understand that although various example components are described as performing various functions, other components may perform

[0143] Now refer to Figure 9, a block diagram showing example components of a UE or a network device (e.g., a RAN or a core network). The device includes an electronic storage 910, a processor 920, a network interface 940, and a memory 950. The various components can be communicatively coupled to each other. The processor 920 can be any type of processor, such as a single-core central processing unit (CPU), a multi-core CPU, a microprocessor, a digital signal processor (DSP), a system on a chip (SoC), or any other type of processor. The memory 950 can be a volatile type of memory (e.g., RAM) or a non-volatile type of memory (e.g., NAND flash). The memory 950 includes processor-readable instructions that can be executed by the processor 920 to cause the device to perform various operations, including those mentioned herein, such as Figures 5 to 8 operations.

[0144] The electronic storage 910 can be any type of electronic storage for storing data, such as a hard disk drive, a solid-state drive, an optical disk, and / or other non-transitory computer-readable media, as well as other types of electronic memories. The electronic storage 910 stores processor-readable instructions for causing or being configured to cause the device to perform its operations, and also stores data associated with such operations, such as other data including data related to the 5G NR standard. The network interface 940 can implement wireless network technologies, such as 5G NR and / or other wireless network technologies.

[0145] Figure 9 The components shown in are merely examples, but those skilled in the art will understand that the device includes other components not shown and can include any number of the shown components. These and other embodiments are considered to be within the scope of the present disclosure. For example, a transmitter and a receiver are included as components for transmitting and receiving signals.

[0146] Additional embodiments of the present disclosure include the following examples.

[0147] Example 1.1. A device, comprising:

[0148] means for a first device to receive a request from a second device, the request including a query for an environmental context of a first user equipment (UE), wherein the environmental context indicates an indoor location or an outdoor location;

[0149] means for a first device to receive first context data related to the environmental context of the first UE from the second device;

[0150] means for estimating the environmental context of the first UE as an indoor location or an outdoor location based on the first context data; and

[0151] A component for sending a first message from a first device to a second device, the first message including environmental context.

[0152] Example 1.2. The device according to Example 1.1 further includes: a component for determining the accuracy of the estimated environmental context.

[0153] Example 1.3. The device according to Example 1.2, wherein the first message includes an indication of the accuracy of the estimated environmental context.

[0154] Example 1.4. The device according to Example 1.1, wherein the request from the second device is an Nlmf_Location_DetermineLocation request message.

[0155] Example 1.5. The device according to Example 1.4, wherein the request includes environmental context attributes.

[0156] Example 1.6. The device according to any one of Examples 1.4 to 1.5, wherein the request includes location and environmental attributes.

[0157] Example 1.7. The device according to Example 1.1, wherein the first message is an Nlmf_Location_DetermineLocation response message.

[0158] Example 1.8. The device according to Example 1.7, wherein the first message includes environmental context method usage attributes.

[0159] Example 1.9. The device according to any one of Examples 1.7 to 1.8, wherein the first message includes accuracy attributes.

[0160] Example 1.10. The device according to Example 1.1, wherein the request from the second device is a Namf_Location_ProvidePositioningInfo request message.

[0161] Example 1.11. The device according to Example 1.10, wherein the request includes environmental context attributes.

[0162] Example 1.12. The device according to any one of Examples 1.10 to 1.11, wherein the request includes location and environmental attributes.

[0163] Example 1.13. The device according to Example 1.1, wherein the first message is a Namf_Location_ProvidePositioningInfo response message.

[0164] Example 1.14. The device according to Example 1.13, wherein the first message includes environmental context method usage attributes.

[0165] Example 1.15. The apparatus according to any one of Examples 1.13 to 1.14, wherein the first message includes an accuracy attribute.

[0166] Example 1.16. The apparatus according to Example 1.1, wherein the first apparatus is a Location Management Function (LMF).

[0167] Example 1.17. The apparatus according to Example 1.1, wherein the first apparatus is an Access and Mobility Management Function (AMF).

[0168] Example 1.18. The apparatus according to Example 1.1, wherein the first apparatus is a Network Data Analytics Function (NWDAF).

[0169] The embodiments and aspects disclosed herein are examples of the present disclosure and may be embodied in various forms. For example, although some embodiments herein are described as separate embodiments, each embodiment herein may be combined with one or more other embodiments herein. The specific structural and functional details disclosed herein should not be construed as restrictive, but should be construed as a basis for the claims and a representative basis for teaching those skilled in the art to adopt the present disclosure in various ways with almost any appropriate detailed structure. Throughout the description of the drawings, the same reference numerals may refer to similar or identical elements.

[0170] The phrases "in one aspect", "in aspects", "in various aspects", "in some aspects", or "in other aspects" may each refer to one or more aspects among the same or different aspects according to the present disclosure. The phrase "a plurality" may refer to two or more.

[0171] In various embodiments, the terms "first message" and "second message" and any subsequent messages may refer to any messages sent or received in sequence, not necessarily limited to any specific message.

[0172] The phrases "in one embodiment", "in embodiments", "in various embodiments", "in some embodiments", or "in other embodiments" may each refer to one or more embodiments among the same or different embodiments according to the present disclosure. The phrase in the form "A or B" means "(A), (B), or (A and B)". The phrase in the form "at least one of A, B, or C" means "(A); (B); (C); (A and B); (A and C); (B and C); or (A, B, and C)".

[0173] Any method, procedure, algorithm, or code described herein can be converted into, or expressed in, a programming language or a computer program. The terms "programming language" and "computer program" as used herein each include any language used to specify instructions to a computer and include (but are not limited to) the following languages and their derivatives: assembly language, Basic, batch files, BCPL, C, C+, C++, Delphi, Fortran, Java, JavaScript, machine code, operating system command languages, Pascal, Perl, PL1, Python, scripting languages, Visual Basic, meta-languages that specify programs themselves, and all first-generation, second-generation, third-generation, fourth-generation, fifth-generation, or further-generation computer languages. Also included are databases and other data schemas, and any other meta-languages. There is no distinction made between languages that are interpreted, compiled, or use both compilation and interpretation methods. There is no distinction made between compiled and source versions of a program. Thus, a reference to a program, where the programming language may exist in more than one state (such as source, compiled, object, or linked), refers to any and all such states. A reference to a program may cover the actual instructions and / or the intent of those instructions.

[0174] Although aspects of the present disclosure have been shown in the drawings, it is not intended that the present disclosure be limited thereto, as it is intended that the scope of the present disclosure be as broad as allowed in the art and that the specification be read accordingly. Thus, the foregoing description should not be construed as limiting, but should only be taken as illustrative of particular aspects. Those skilled in the art will envision other modifications within the scope and spirit of the appended claims.

Claims

1. A method for communication, comprising: receiving, by a first device, a request from a second device, the request comprising a query for an environmental context of a first user equipment (UE), wherein the environmental context indicates an indoor location or an outdoor location; receiving, by the first device from the second device, first context data related to the environmental context of the first UE; estimating the environmental context of the first UE as an indoor location or an outdoor location based on the first context data; as well as A first message is sent by the first device to the second device, where the first message includes the environmental context.

2. The method according to claim 1, further comprising: An accuracy of the estimate of the environmental context is determined.

3. The method of claim 1, wherein the request from the second device is an Nlmf_Location_DetermineLocation request message.

4. The method of claim 1, wherein the first message is a Nlmf_Location_DetermineLocation response message. The method of claim 1 , wherein the request from the second device is a Namf_Location_ProvidePositioningInfo request message. The method of claim 1 , wherein the first message is a Namf_Location_ProvidePositioningInfo response message.

7. The method of claim 1, wherein the first device is a location management function (LMF).

8. The method of claim 1, wherein the first device is an Access and Mobility Management Function (AMF).

9. An apparatus for communication, comprising: at least one processor; as well as At least one memory stores instructions, which, when executed by the at least one processor, cause the apparatus to at least perform the method according to any one of claims 1 to 18.

10. An apparatus for communication, comprising: at least one processor; as well as at least one memory storing instructions, which, when executed by the at least one processor, cause the apparatus to at least perform: receiving, by a first device, a request from a second device, the request comprising a query for an environmental context of a first user equipment (UE), wherein the environmental context indicates an indoor location or an outdoor location; receiving, by the first device from the second device, first context data related to the environmental context of the first UE; estimating the environmental context of the first UE as an indoor location or an outdoor location based on the first context data; as well as A first message is sent by the first device to the second device, where the first message includes the environmental context.

Images