A method, related equipment and storage medium for service enabling architecture layer
By introducing location management services in the Service Enablement Layer (SEAL), the problem of low efficiency in location management for vertical applications in wireless communication systems is solved, enabling real-time monitoring and rapid deployment of user equipment location information.
Patent Information
- Application Number
- CN202180031198.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2021-10-12
- Filing Date
- 2021-10-14
- Publication Date
- 2024-11-22
- Estimated Expiration
- 2041-10-14
AI Technical Summary
Existing wireless communication systems lack effective location management and information reporting mechanisms when supporting vertical applications, resulting in low efficiency in the rapid deployment and management of vertical applications.
The location management service of the Service Enablement Layer (SEAL) is introduced to realize real-time monitoring and management of the location information of user devices through mechanisms such as location report configuration, event triggering, on-demand location reporting and location information subscription.
It improves the efficiency of location information management for vertical applications, supports rapid deployment and flexible location information acquisition, and meets the customized needs of vertical applications.
Smart Images

Figure CN115486098B_ABST
Abstract
Description
[0001] Incorporation by reference
[0002] This disclosure claims the benefit of priority to U.S. Patent Application No. 17 / 499,601, filed on October 12, 2021, entitled “Location Reporting for Service Enabler Architecture Layer (SEAL)” (which claims the benefit of priority to U.S. Provisional Application No. 63 / 172,050, filed on April 7, 2021, entitled “A Method of Supporting Location Timestamp Reporting for 3GPP SEAL Architecture”). The disclosure of the prior application is incorporated herein by reference in its entirety. Technical Field
[0003] The present disclosure describes embodiments generally directed to a service enablement layer that supports vertical applications running on a wireless network. Background Art
[0004] The background description provided herein is for the purpose of presenting the present disclosure in general. The extent to which the work of the presently named inventors described in this background section and in various aspects of this specification is performed does not indicate that it qualifies as prior art at the time of filing this application, and it is never expressly or impliedly admitted that it is prior art to the present disclosure.
[0005] Wireless communication systems are designed with advanced built-in features to support enterprise sectors or vertical industries such as healthcare, automotive, smart factories, mission-critical communications, etc. Vertical application standards are being developed to enable rapid deployment of vertical services based on the public services provided by wireless networks. A vertical sector can be a business or group of businesses in an industry that produces similar products or services. Vertical applications can provide services or functions that are useful in a specific vertical sector. Summary of the invention
[0006] Aspects of the present disclosure provide a method of a service enabling architecture layer (SEAL). The method may include: receiving a location reporting configuration from a location management server of the SEAL at a first user equipment (UE). The location reporting configuration may indicate at least one location reporting event, and the at least one location reporting event is used to trigger a first location information report from a first location management client at the first UE to the location management server. In response to the occurrence of at least one location reporting event, a first location information report may be sent from the first location management client at the first UE to the location management server. The first location information report may include an identifier of the first UE, an identifier of at least one location reporting event that triggers the first location information report, first location information of the first UE, and a first timestamp corresponding to the first location information of the first UE.
[0007] In one embodiment, the format of the first timestamp corresponding to the first location information of the first UE is one of the following:
[0008] yyyy-month-dayTHH:MM:SS,
[0009] Monday, DD Mon YYYY HH:MM:SS time zone, and
[0010] yyyy-mn-ddTHH:MM:SS.
[0011] An embodiment of the method may further include: receiving a location information request from a location management server of the SEAL; and sending a second location information report to the location management server in response to the received location information request. The second location information report may include the second location information of the first UE and a second timestamp corresponding to the second location information of the first UE.
[0012] An embodiment of the method may further include: sending a location report trigger to a location management server to activate a location reporting process for obtaining third location information of a second location management client of the SEAL at the second UE. A third location information report may be received from the location management server, the third location information report including third location information of the second UE and a third timestamp corresponding to the third location information of the second UE.
[0013] In one embodiment, the type of the first location information identified in the location reporting configuration is one of: an E-UTRA Cell Global Identifier (ECGI), a Multimedia Broadcast Multicast Service Area Identifier (MBMS SAI), and a geographic coordinate.
[0014] An embodiment of the method may further include: sending a location information subscription request including a location information subscription configuration to a location management server. A location information notification may be received from the location management server. The location information notification may include an identifier of the third UE, an identifier of the first UE, an identifier of an event triggering the location information notification, the latest location information of the third UE, and a fourth timestamp associated with the latest location information of the third UE.
[0015] Aspects of the present disclosure may provide another method of a SEAL, which may include: sending a location reporting configuration from a location management server to a first location management client of the SEAL at a first UE. The location reporting configuration may indicate at least one location reporting event, and the at least one location reporting event is used to trigger a first location information report from the first location management client of the SEAL at the first UE to the location management server. A first location information report may be received from the first location management client of the SEAL at the first UE. The first location information report may include an identifier of the first UE, an identifier of at least one location reporting event that triggers the first location information report, first location information of the first UE, and a first timestamp corresponding to the first location information of the first UE. The first location information of the first UE may be stored in a memory.
[0016] Aspects of the present disclosure may provide a non-transitory computer-readable medium storing instructions. When the instructions are executed by a processor, the instructions cause the processor to perform the above method. BRIEF DESCRIPTION OF THE DRAWINGS
[0017] Further features, properties and various advantages of the disclosed subject matter will become more apparent from the following detailed description and the accompanying drawings, in which:
[0018] Figure 1 A general on-network functional model (100) according to one embodiment of the present disclosure is shown.
[0019] Figure 2 An exemplary on-network location management functional model (200) is shown according to some embodiments of the present disclosure.
[0020] Figure 3 An event-triggered location reporting process (300) is shown according to some embodiments of the present disclosure.
[0021] Figure 4 An on-demand location reporting process (400) is shown in accordance with some embodiments of the present disclosure.
[0022] Figure 5 A client-triggered or VAL server-triggered location reporting process (500) is shown according to some embodiments of the present disclosure.
[0023] Figure 6 A location information subscription and notification process (600) is shown according to some embodiments of the present disclosure.
[0024] Figure 7 A location reporting process (700) according to one embodiment of the present disclosure is shown.
[0025] Figure 8 A location reporting process (800) according to one embodiment of the present disclosure is shown.
[0026] Fig. 9 is a schematic diagram of a computer system according to one embodiment. DETAILED DESCRIPTION
[0027] I. Service enabling layer for vertical items
[0028] 1. Service Enablement Architecture Layer (SEAL)
[0029] Embodiments of the present disclosure implement a service enabling layer that supports vertical applications (or vertical items). In the present disclosure, the service enabling layer may be referred to as a service enabling architecture layer (SEAL). SEAL may provide a set of common capabilities (or services) that are used by multiple vertical items to speed up the development and deployment of vertical applications. For example, as an alternative to developing auxiliary services specific to each vertical item, commonly required auxiliary services may be captured into SEAL and shared by multiple vertical applications. It may be optional for a vertical application to use all SEAL services. A vertical application may decide to use any subset of the services from SEAL.
[0030] 2. Generic functional model of SEAL services
[0031] In some embodiments, the SEAL function model can be organized into a general SEAL service function model and a plurality of specific SEAL service function models. The general SEAL service function model can be used as a reference model for a specific SEAL service function model. The general function model can include a function model on the network and a function model outside the network. In various embodiments, the SEAL services provided to support the vertical application layer can include location management, group management, configuration management, identification management, key management, network resource management, etc.
[0032] Figure 1A general network functional model (100) according to an embodiment of the present disclosure is shown. The model (100) may include four types of functional entities: a vertical application layer (VAL) client (111), a VAL server (121), a SEAL client (112), and a SEAL server (122). The number of functional entities of each type in the model (100) may be one or more than one. The VAL client and the VAL server entities may belong to the VAL (101). The SEAL client and the SEAL server entities may belong to the SEAL (102). The VAL client (111) and the SEAL client (112) may be included in a user equipment (UE) (110). The model (100) further includes a wireless network system (140) (e.g., a third generation partnership project (3GPP) network system). These elements may be as shown in FIG. Figure 1 Coupled together as shown.
[0033] In the VAL (101), the VAL client (111) communicates with the VAL server (121) via a VAL-UU reference point (134) corresponding to a VAL-UU interface. In one example, the VAL-UU interface supports a unicast transmission mode and a multicast transmission mode.
[0034] The SEAL (102) provides various services to the VAL (101). The SEAL client communicates with the SEAL server via the SEAL-UU reference point (133) corresponding to the SEAL-UU interface. The SEAL-UU interface supports unicast transmission mode and multicast transmission mode. The SEAL client provides service enabling layer support functions to the VAL client via the SEAL-C reference point (131) (corresponding to the SEAL-C interface). The VAL server communicates with the SEAL server via the SEAL-S reference point (corresponding to a SEAL-S interface). The SEAL server (122) can communicate with the underlying 3GPP network system (140) using the corresponding 3GPP interface (135) specified by the 3GPP network system.
[0035] For a specific service (eg, location management service), a specific SEAL client and a specific SEAL server, their specific SEAL-UU reference points, and a specific network interface of the 3GPP network system may form or belong to a functional model on a specific network.
[0036] In some embodiments, to support distributed SEAL server deployments, SEAL servers may communicate with each other for the same SEAL service through so-called SEAL-E reference points (not in Figure 1 SEAL servers can communicate with other SEAL servers via so-called SEAL-X reference points (not shown in Figure 1The SEAL server can interact with the VAL user database through the VAL-UDB reference point to store and retrieve user profiles.
[0037] In various embodiments, functional entities in a VAL system (e.g., including VAL 101 and SEAL 102) may provide application control and media-specific functions to support one or more VAL services. Figure 1 In an example, a VAL client (111) (e.g., a vehicle-to-everything (V2X) client) may provide client-side functionality corresponding to a vertical application (e.g., a V2X application). The VAL client (111) may support interaction of the vertical application with a SEAL client (112). A VAL server (121) (e.g., a V2X application server) may provide server-side functionality corresponding to the vertical application.
[0038] exist Figure 1 In the example of , the SEAL client (112) may provide client-side functions corresponding to a specific SEAL service (e.g., location management, network resource management, etc.). The SEAL client (112) may support interaction with the VAL client (111). The SEAL client may also support interaction between two UEs and the corresponding SEAL client. The SEAL server (122) may provide server-side functions corresponding to a specific SEAL service. The SEAL server (122) may support interaction with the VAL server (121). The SEAL server may also support interaction with the corresponding SEAL server in a distributed SEAL deployment.
[0039] It should be noted that the functional entities in the model (100) may be implemented in different ways in different embodiments. For example, the functional entities may be implemented in a distributed manner or in a centralized manner. The functional entities may be implemented as software or a combination of software and hardware.
[0040] exist Figure 1 In an example of , a VAL user database (not shown) may contain user profile information associated with a VAL service provided by a VAL service provider. Typically, each VAL service may have a corresponding user database, such as a mission-critical push-to-talk (MCPTT) user database, a mission-critical video (MCVideo) user database, and a mission-critical data (MCData) user database.
[0041] In some embodiments, interactions between the VAL client (111) and the VAL server (121) related to VAL (101) support functions are supported by a VAL-UU reference point (134). In one example, the reference point (134) is an instance of a Uu reference point as described in 3GPP TS 23.401 and 3GPP TS 23.501. In some embodiments, interactions between the VAL clients of two UEs related to VAL support functions may be supported by a VAL-PC5 reference point (not shown). For example, the reference point may be an instance of a PC5 reference point as described in 3GPP TS 23.303.
[0042] In some embodiments, the interaction between the SEAL client (112) and the corresponding SEAL server (122) is supported by the SEAL-UU reference point (133). The specific SEAL service reference point corresponding to SEAL-UU (133) may be specified in the specific SEAL service function model. In some embodiments, the interaction between the SEAL clients of two VAL UEs may be supported by the SEAL-PC5 reference point (not shown). The specific SEAL service reference point corresponding to SEAL-PC5 may be specified in the specific SEAL service function model.
[0043] In some embodiments, the interaction between the VAL client (111) and the SEAL client (112) within the VAL UE (110) is supported by the SEAL-C reference point (131). The specific SEAL service reference point corresponding to the SEAL-C (131) may be specified in a specific SEAL service capability model.
[0044] In some embodiments, the interaction between the VAL server (121) and the SEAL server (132) is supported by the SEAL-S reference point (132). The specific SEAL service reference point corresponding to the SEAL-S (132) may be specified in a specific SEAL service capability model.
[0045] In some embodiments, interactions between SEAL servers of the same type (eg, providing the same type of SEAL services) are supported by a SEAL-E reference point (not shown). The specific SEAL service reference point corresponding to SEAL-E is specified in the specific SEAL service capability model.
[0046] In some embodiments, interactions between different types of SEAL servers may be supported by SEAL-X reference points. Examples of specific reference points corresponding to SEAL-X reference points may include reference point SEAL-X1 between a key management server and a group management server, reference point SEALX-X2 between a group management server and a location management server.
[0047] There is a reference point VAL-UDB between the VAL user database and the SEAL server. The reference point VAL-UDB can be used to store user profile data in a specific VAL user database and to obtain user profiles from a specific VAL user database for further configuration in the UE.
[0048] 3. Logo
[0049] In various embodiments, different identifications may be configured and used in a VAL system developed based on the model (100). In some embodiments, a VAL user may provide a user identification (user ID) to an identification management server in the SEAL (102) during a user authentication transaction to provide a VAL service authentication means to an identification management client. Typically, since identification management is a common SEAL service, an identification management server uses a set of credentials (e.g., biometrics, security ID, username / password) that may not necessarily be bound to a single VAL service. User credentials uniquely identify a VAL user to an identification management server. As an example, specific security and authentication mechanisms required for using a user ID are specified in 3GPP TS 33.434.
[0050] In some embodiments, the VAL user ID is a unique identifier representing a VAL user in a VAL service. For example, the VAL user ID can be a URI. The VAL user ID is used for authentication and authorization purposes to provide VAL services to VAL users through VAL UEs. The VAL user ID also indicates the VAL service provider that has signed a VAL service agreement with the VAL user. The VAL user can sign a VAL service agreement with the VAL service provider, and thus has obtained a unique VAL user ID for each VAL service provider. The VAL user ID can be used to access SEAL services.
[0051] In some embodiments, the VAL UE ID is a unique identifier representing the VAL UE in the VAL service. For example, the VAL UE ID of the V2X service is mapped to the site ID as specified in ETSI TS 102 894-2. The VAL UE ID is used to address the VAL UE to send a VAL message.
[0052] In some embodiments, the VAL service ID is a unique identifier representing a VAL service. The VAL server provides a VAL service list to a VAL user or a VAL UE. Each VAL service is uniquely identified by a VAL service ID, which is an identifier of a VAL application that provides the VAL service. The VAL service ID can be used for policy mapping, QoS processing of VAL communications, and VAL message distribution. For example, an identifier for a V2X service (e.g., an ITS-AID or PSID specified in ETSI TS 102 965 and ISO TS 17419) can be used as a V2X service ID.
[0053] In some embodiments, the VAL group ID is a unique identifier in a VAL service that represents a group of VAL users or VAL UEs according to the VAL service. This group of VAL users may belong to the same or different VAL service providers. The VAL group ID indicates the VAL application server that defines the group.
[0054] In some embodiments, the VAL system ID is a globally unique identifier representing the VAL system. In some embodiments, the VAL stream ID is an identifier used by the VAL server to identify the VAL stream.
[0055] 4. Application of functional models in deployment
[0056] In various embodiments, the SEAL architecture described above can support the deployment of SEAL services deployed inside and / or outside of a public land mobile network (PLMN) network. The SEAL architecture can also support centralized deployment of vertical applications as well as distributed deployment. Mobile network operators (MNOs) can utilize the appropriate deployment model suitable for their business as needed.
[0057] The deployment model may involve multiple entities, such as VAL users, VAL service providers, SEAL providers, and PLMN operators. As an example, in a possible deployment model, a SEAL server may be deployed in a PLMN operator domain, and a vertical application server may be deployed in a VAL service provider domain. A SEAL server may also interact with another SEAL server of the same SEAL service deployed in a different PLMN operator domain using the SEAL-E interface.
[0058] There can be a variety of business relationships between the entities involved in the deployment. VAL users belong to the VAL service provider domain, depending on the service-specific agreement. The VAL service provider and the primary PLMN operator can belong to the same organization. The VAL service provider can enter into a service agreement with the SEAL service provider. It is also possible that the VAL service provider, the SEAL service provider, and the primary PLMN operator belong to the same organization. If the VAL service provider and the primary PLMN operator do not belong to the same organization, the VAL service provider and the primary PLMN operator can enter into a service agreement.
[0059] 5. SEAL-based V2X vertical applications
[0060] In one embodiment, a V2X vertical application is developed based on a SEAL service. SEAL can support multiple SEAL services. Each SEAL service can support multiple processes. Usually, a SEAL client does not initiate a process by itself. In order for a SEAL client to initiate a process, the V2X vertical application needs to provide the SEAL client with parameters and triggers related to the process.
[0061] For example, the V2X application level functional model is defined in 3GPP TS 23.286. As defined, the V2X application enabling (VAE) layer provides VAE capabilities to the V2X application specific layer. The VAE layer uses SEAL services. A VAE client can act as a VAL client that interacts with a SEAL client specified by the SEAL architecture. A VAE server can act as a VAL server that interacts with a SEAL server specified by the SEAL architecture.
[0062] The V2X application layer may provide group join policies and group leadership to each group. The VAE client and VAE server use the SEAL group management service for group management operations. The V2X application layer is responsible for deciding when to create, modify, or delete a group. The VAE client and VAE server may use the SEAL configuration management service to provide configuration to the V2X UE before the V2X UE starts receiving V2X services from the V2X application layer. The VAE client and VAE server may also use the SEAL configuration management service to provide configuration updates to the V2X UE while the V2X UE is receiving V2X services from the V2X application layer.
[0063] VAE clients and VAE servers can use SEAL location management services to manage the location information of V2X UEs and update the location information to the V2X application layer. VAE clients and VAE servers can use SEAL identity management services to authenticate and authorize V2X UEs to use V2X application servers. VAE clients and VAE servers can use SEAL network resource management services to establish different types of bearers, modify different types of bearers, and switch between different types of bearers.
[0064] The VAE server can also use the SEAL API to use the SEAL service to implement different functions or services of the V2X application. For example, to create a group for the V2X application, the VAE server can call the create service operation of the group management API on the GM-S reference point. The group management server can create a group document and notify the VAE server of the newly created group information.
[0065] In various embodiments, multiple vertical applications can use SEAL services at the same time. For example, two vertical applications, V2X and MCPTT, can use SEAL services. The SEAL server can interface with two vertical application servers. In addition, each vertical specific UE may include a SEAL client that provides services to the vertical application client. The two SEAL clients interact with the SEAL server to provide support for the two vertical applications.
[0066] II. Location Management Services
[0067] 1. Functional model for location management
[0068] In various embodiments, the location management of the SEAL service provides location management related capabilities to one or more vertical applications. Location management can be implemented based on a location management functional model. The location management functional model can be based on the above-mentioned general functional model. The location management functional model can include an on-network functional model and an off-network functional model.
[0069] Figure 2 An exemplary network location management functional model (200) according to some embodiments is shown. The model (200) may include a VAL client (211), a VAL server (221), a location management client (212), and a location management server (222). These functional entities may be as follows: Figure 2 Coupled together as shown.
[0070] The VAL client (211) and the VAL server (221) belong to the VAL (201). The location management client (212) and the location management server (222) belong to the SEAL (202). The VAL client (211) and the location management client (212) may be included in the UE (210). The model (200) may also include a wireless working system (240) (e.g., a 3GPP network system), which provides a communication path for the UE (210) to communicate with the VAL server (221) and the location management server (222). It should be noted that in the model (200), there may be multiple VAL clients instead of the VAL client (211), and the multiple VAL clients use the location management SEAL service provided by the location management client (212) and the location management server (222). Furthermore, in the model (200), there may be multiple VAL servers instead of the VAL server (221), and the multiple VAL servers use the location management SEAL service provided by the location management client (212) and the location management server (222).
[0071] In some embodiments, the location management client (212) communicates with the location management server (222) via the LM-UU reference point (233). The location management client (222) provides support for location management functions to the VAL client (211) via the LM-C reference point (231). The VAL server (221) communicates with the location management server (222) via the LM-S reference point (232). The VAL client (211) communicates with the VAL server (221) via the VAL-UU reference point (234).
[0072] In some embodiments, the location management server (222) communicates with the underlying wireless communication system (240) to obtain location information through an interface (235) (e.g., a T8 interface). In one example, the location management server (222) communicates with a service capability exposure function (SCEF) through a T8 interface (235) to obtain location information from an underlying 3GPP network system. In one example, the location management server (222) may use another interface to obtain location information from a location server (LCS) of a 4G system. In one example, the location management server (222) may obtain location information from a 3GPP network system (240) through a Le interface.
[0073] In the out-of-network location management functional model, the VAL clients of the VALs distributed in different UEs can communicate with each other via the VAL-PC5 reference point. The location management clients of the SEALs distributed in different UEs can communicate with each other via the LM-PC5 reference point.
[0074] In some embodiments, the location management client (212) interacts with the VAL client (211) to perform location management functions. The location management client (212) also interacts with the location management server (222). The location management client (212) also supports interaction between two UEs and corresponding location management clients.
[0075] In some embodiments, the location management server (222) receives and stores user location information, and provides the user location information to the VAL server (221). The location management server (222) can also obtain location information provided by the PLMN operator of the 3GPP network system (240) through, for example, the T8 interface (235). The location management server (222) also supports interaction with a corresponding location management server in a distributed SEAL deployment.
[0076] The VAL client (211) and the VAL server (221) can be respectively Figure 1 The VAL client (111) and VAI server (121) in the example of FIG. 1 function in a similar manner.
[0077] In some embodiments, the interaction between the location management client (212) and the location management server (222) related to the location management function is supported by the LM-UU reference point (233). In one example, the reference point (233) uses the Uu reference point as described in 3GPP TS 23.401 and 3GPP TS 23.501. The LM-Uu reference point (333) provides the location management server (222) with a means to receive location information reports from the location management client (212).
[0078] In some embodiments, the interaction between location management clients in different VAL UEs related to location management functions is supported by the LM-PC5 reference point. In one example, the reference point uses the PC5 reference point as described in 3GPP TS 23.303. In some embodiments, the interaction between the VAL client (211) and the location management client (212) in the VAL UE (210) related to location management functions is supported by the LM-C reference point (231).
[0079] In some embodiments, interactions between the VAL server (221) and the location management client (222) related to location management functions are supported by the LM-S reference point (232). In one example, the reference point (232) uses an instance of the CAPIF-2 reference point as specified in 3GPP TS 23.222. For example, the LM-S reference point (232) is used by the VAL server (221) to request and receive location information from the location management server (222).
[0080] In some embodiments, the interaction between location management servers in a distributed deployment and related to location management functions is supported by the LM-E reference point. In some embodiments, the T8 interface (235) supports the interaction between the location management server (222) and the SCEF specified in 3GPP TS 23.682. Functions related to location management of T8 are supported by the location management server (222).
[0081] 2. Example of location management process
[0082] 2.1 Event-triggered location reporting process
[0083] Figure 3 An event-triggered location reporting process (300) according to some embodiments of the present disclosure is shown. The process (300) may be performed by a location management client (301) and a location management server (302). The process (300) may start at (S310).
[0084] At (S310), the location management client (301) may send a location reporting configuration request message to the location management server (302) to obtain the location reporting configuration.
[0085] At (S320), the location management server (302) may send a location reporting configuration response message to the location management client (301) in response to receiving the location reporting configuration request message. The location reporting configuration response message may include a location reporting configuration. The location reporting configuration may be an initial configuration or an update to a previous configuration. The location reporting configuration may indicate the type of location information expected by the location management server (302) and what events will trigger the sending of location information to the location management server (302).
[0086] In some embodiments, the decision to report location information may be triggered at the location management client (301) by various conditions or events, such as: receiving a location reporting configuration, initial registration with a wireless network, driving distance, elapsed time, cell change, MBMS SAI change, MBMS session change, leaving a specific MBMS bearer service area, PLMN change, call initiation, emergency, or other types of events. In one embodiment, the location reporting configuration may further indicate a minimum time between consecutive reports. In one embodiment, the location reporting configuration may further indicate whether a timestamp for the location information report is required.
[0087] In some embodiments, the location report configuration response message may be sent to a specific location management client (e.g., location management client (301)) via a unicast bearer, or may be sent as a group message via an MBMS bearer to simultaneously update the location report configurations of multiple location management clients. In one example, if a multicast transmission mode is used, the MBMS bearer used is activated by the location management server.
[0088] In some embodiments, the location management client (301) stores or updates the location reporting event triggering configuration in response to receiving the location reporting configuration. In one example, the location reporting configuration information may become part of the user profile. In this scenario, there is no need to send a location information configuration response message. In some embodiments, different location reporting criteria may be provided for different location management clients.
[0089] At (S330), the location management client (301) may detect that a configured location reporting event occurs, thereby triggering a location information report.
[0090] At (S340), the location management client (301) may send a location information report to the location management server (302). The location information report may include location information identified by the location management server (302) and available to the location management client (301).
[0091] In one embodiment, the location information report may include one or more of the following information elements: (1) An identifier of a VAL user or VAL UE corresponding to the location management client (301). For example, the VAL UE includes the location management client (301). The VAL user uses the services of the location management client (301) through the VAL client above the location management client (301). (2) An identifier of an event that triggers the transmission of the location information report. (3) Location information of the VAL UE when the event that triggers the transmission of the location information report occurs. (4) Optionally, a timestamp of the location information report. For example, the timestamp may indicate the time when the event that triggers the transmission of the location information report occurs. Alternatively, the timestamp may indicate a time corresponding to the location of the VAL UE indicated by the location information report. In one example, when the location report configuration indicates that a timestamp of the location information report is included, the timestamp may be included in the location information report.
[0092] In one example, the location information report from the location management client (301) to the location management server (302) may include all or part of the information shown in Table 1.
[0093] Table 1
[0094]
[0095] In Table 1, "M" indicates "Mandatory" and "O" indicates "Optional".
[0096] In some embodiments, the timestamp in the location information report may use one of a variety of different time formats, such as ISO 8610 (e.g., yyyy-month-day THH:MM:SS), RFC 1123 (e.g., Monday, DD-Mon YYYY HH:MM:SS time zone), Coordinated Universal Time (UTC: yyyy-mn-dd THH:MM:SS), etc.
[0097] In some embodiments, the location information report may include at least one of multiple different types of location information, such as E-UTRA Cell Global Identifier (ECGI), Multimedia Broadcast Multicast Service Area Identity (MBMS SAI), geographic coordinates, and other types of location information.
[0098] At (S350), when receiving the location information report, the location management server (302) may store the information included in the location information report in a local memory. For example, the location management server (302) may update the location of the reporting location management client (301). If the location management server (302) does not have the location information of the reporting location management client (301) before, the location management server (302) may only store the reported location information of the location management client (301).
[0099] 2.2 On-demand position reporting process
[0100] Figure 4 An on-demand location reporting process (400) according to some embodiments of the present disclosure is shown. The process (400) may be performed by a location management server (401) and a location management client (402). In some embodiments, during the process (400), the location management server (401) may request UE location information at any time by sending a location information request to the location management client (402), which may trigger the location management client (403) to immediately send a location report.
[0101] At (S410), based on configuration such as a periodic location information reporting timer or a location information request from another entity (eg, another location management client or a VAL server), the location management server (401) may determine to immediately initiate a location information request.
[0102] At (S420), the location management server (401) sends a location information request to the location management client (402). For example, the location information request may include an identification of a VAL user or VAL UE and specify what type of location information is requested for the VAL user or VAL UE.
[0103] At (S430), optionally, at the location management client (402), the VAL user or VAL UE may be notified and request permission from the VAL user or VAL UE to share their location. The VAL user may accept or deny the request. In some embodiments, the location may be shared automatically without further user input.
[0104] At (S440), the location management client (402) responds to the location management server (401) with a location information report that includes location information identified by the location management server 401 and available to the location management client (402). In some embodiments, the location information report of (S440) may be similar to the location information report of (S340). For example, the location information report of (S440) may include the location information of the location management client (402) and a timestamp associated with the location indicated by the location information. The location information report of (S440) may or may not indicate a triggering event for the location information report.
[0105] At (S450), when receiving the location information report, the location management server (401) may update the location of the reporting location management client (402). In one example, if the location management server (401) does not have the location information of the reporting location management client (402) before, the location management server (401) may only store the reported location information of the location management client (402).
[0106] 2.3 Client-triggered or VAL server-triggered location reporting process
[0107] Figure 5A client-triggered or VAL server-triggered location reporting process (500) according to some embodiments of the present disclosure is shown. The process (500) may be performed by a first location management client (501A) or a VAL server (501B), a location management server (502), and a second location management client (503). In some embodiments, during the process (500), the first location management client (501A) or the VAL server (501B) may initiate a request for location information of a VAL user or VAL UE corresponding to the second location management client (503). In response, the location management server (502) may obtain the requested location information and report it to the first location management client (501A) or the VAL server (501B).
[0108] At (S510), the first location management client (501A) (e.g., corresponding to an authorized VAL user or VAL UE) or the VAL server (501B) sends a location reporting trigger to the location management server (502) to activate a location reporting process, which allows the user to obtain location information of the second location management client (503).
[0109] At (S520), the location management server (502) may check whether the first location management client (501A) or the VAL server (501B) is authorized to send a location report trigger. Subsequently, according to the information specified by the location report trigger, the location management server (502) may initiate an on-demand location reporting process or an event-triggered location reporting process to request the location information of the second location management client (503).
[0110] At (S530), once the location information of the second location management client (503) is available at the location management server (502), a location information report may be sent to the first location management client (501A) or the VAL server (501B). In some embodiments, the location information report of (S530) may be similar to the location information report of (S340). For example, the location information report of (S530) may include the location information of the location management client (503) and a timestamp associated with the location indicated by the location information. The location information report of (S530) may or may not indicate a triggering event for the location information report.
[0111] In one embodiment, before the first location management client (501A) can request location information from the location management server (502), the first location management client (501A) can perform a registration process to register with the location management server (502). For example, the first location management client (501A) can send a timestamp request to the location management server (502) to request that a timestamp be added to the location information report from the location management server (502). Afterwards, each of the location information response messages from the location management server (502) will include a timestamp in response to a corresponding location query from the first location management client (501A).
[0112] In one embodiment, for the location information query from the VAL server (501B) to the location management server (502), there is no registration process between the VAL server (501B) and the location management server (502). The location management server (502) can optionally send a response with a timestamp to the VAL server (501B).
[0113] 2.4 Location Information Subscription and Notification Process
[0114] Figure 6 A location information subscription and notification process (600) according to some embodiments of the present disclosure is shown. The process (600) may be performed by a VAL server (601), a location management server (602), a location management client (603), and a 3GPP core network (604). During the process (600), the VAL server (601) may subscribe to the location management server (602) for location information of a VAL user or VAL UE corresponding to the location management client (603). The location management server (602) may provide location information notifications to the VAL server (601) based on the subscription configuration. As an alternative to the VAL server (601), other entities (e.g., a location management client) may use the process (600) to subscribe to location information corresponding to the location management client (603), and receive location information notifications from the location management server (602) accordingly.
[0115] At (S610), the VAL server (601) may send a location information subscription request to the location management server (602) to subscribe to the location information of one or more VAL users or VAL UEs. Each VAL user or VAL UE may correspond to a location management client. In the following steps, the location information of the VAL user or VAL UE corresponding to the location management client (603) is subscribed and reported as an example. The location information subscription request may indicate what type of location information is required, a set of events for triggering a location report from the location management client (603), an interval for regularly providing location information notifications, etc. The location information subscription request may indicate that location information (referred to as supplementary location information) is required from the 3GPP core network (604).
[0116] At (S620), the location management server (602) receives the latest location information of the VAL UE corresponding to the location management client (603) according to the location reporting process. For example, the location reporting process can be an event-triggered location reporting process (e.g., process (300)) or an on-demand location reporting process (e.g., process (400) triggered by a periodic location reporting timer configured based on the location information subscription request at S610). Before receiving the latest location information of the VAL UE, the location management server (602) can communicate with the location management client (603) to configure the location report. For example, as performed in process (300), some events can be configured in the location management client (603) to trigger the location report.
[0117] At (S630), the location management server (602) may optionally receive the location information of the VAL UE from the 3GPP core network (604). For example, if the indication of the supplementary location information is included in the subscription request of S610, the UE location information may be obtained from the 3GPP core network (604).
[0118] At (S640), based on the location information subscription configuration (e.g., periodic location information reporting timer) provided by the location information subscription request at (S610), the location management server (602) may determine to report the latest user location information of the location management client (603) to the VAL server (601). For example, the location management server (602) may determine the location information of the VAL UE received in steps (S620) and / or (S630), the location information including the supplemental location information (if indicated by the location information subscription request).
[0119] At (S650), the location management server (602) sends a location information notification including the latest location information of one or more VAL users or VAL UEs to the VAL server (601) (or to a location management client that has previously performed a subscription to the location management server (602)).
[0120] In some embodiments, the location information notification may include one or more of the following information elements: (1) a list of VAL users or VAL UEs, of which location information is to be notified. (2) an identifier of a VAL user or VAL UE that subscribes to a location corresponding to the location management client (603). (3) an identifier of an event that triggers the transmission of the location information notification, or an identifier of an event that triggers the location management client (603) to send a location information report at (S620). (4) location information of the VAL user or VAL UE, of which location information is to be notified, for example, the location information includes the latest location information corresponding to the location management client (603). (5) a timestamp of the location report. In one example, a timestamp corresponding to the latest location indicated by the location information corresponding to the location management client (603) is included. In one example, the timestamp corresponds to the latest location of each VAL user or VAL UE, and the timestamp is included, of which the location information of each VAL user or VAL UE is to be notified. In one example, a timestamp corresponding to the time when the location information notification was generated is included.
[0121] In some embodiments, the location information notification from the location management server (602) to the VAL server (601) may include all or part of the information flows shown in Table 2.
[0122] Table 2
[0123]
[0124]
[0125] In some embodiments, the VAL server (601) may further share the location information in the location information notification with a group or another VAL user or VAL UE.
[0126] III. Exemplary Position Reporting Process
[0127] Figure 7 A location reporting process (700) according to one embodiment of the present disclosure is shown. The process (700) may be performed by a location management client of SEAL. The process (700) may start from (S701) and proceed to (S710).
[0128] At (S710), a location reporting configuration may be received at the UE from a location management server of the SEAL. The location reporting configuration may indicate at least one location reporting event, the at least one location reporting event being used to trigger a location information report from a location management client at the UE to the location management server.
[0129] At (S720), a location information report may be sent from a location management client at the UE to a location management server in response to at least one location reporting event occurring. In one example, the location information report may include an identification of the UE, an identification of at least one location reporting event that triggers the location information report, location information of the UE, and a timestamp corresponding to the location information of the UE. In one example, the type of location information is identified in a location reporting configuration.
[0130] In one example, the format of the timestamp corresponding to the location information of the UE is based on one of: ISO 8610, RFC 1123, and Coordinated Universal Time (UTC). In one example, the type of the location information is one of: E-UTRA Cell Global Identifier (ECGI), Multimedia Broadcast Multicast Service Service Area Identity (MBMS SAI), and geographic coordinates. The process (700) may proceed to (S799) and end at (S799).
[0131] Figure 8 A location reporting process (800) according to one embodiment of the present disclosure is shown. The process (800) may be performed by a location management server of SEAL. The process (800) may start from (S801) and proceed to (S810).
[0132] At (S810), a location reporting configuration may be sent to a location management client of the SEAL at the UE. The location reporting configuration may indicate at least one location reporting event, the at least one location reporting event being used to trigger a location information report from the location management client of the SEAL at the UE to a location management server.
[0133] At (S820), a first location information report may be received from a location management client of the SEAL at the UE. The first location information report may include an identification of the UE, an identification of at least one location reporting event that triggers the location information report, location information of the UE, and a timestamp corresponding to the location information of the UE. In one example, the type of location information is identified in a location reporting configuration.
[0134] In one example, the format of the timestamp corresponding to the location information of the UE is based on one of the following: ISO 8610, RFC 1123, and Coordinated Universal Time (UTC). In one example, the type of the location information is one of the following: E-UTRA Cell Global Identifier (ECGI), Multimedia Broadcast Multicast Service Service Area Identity (MBMS SAI), and geographic coordinates.
[0135] At (S830), the location information of the UE may be stored in a memory at the location management server. The process (800) may proceed to (S899) and end at (S899).
[0136] IV. Computer System
[0137] The above technology can be implemented as computer software that uses computer-readable instructions and is physically stored in one or more computer-readable media. The computer software can be encoded using any suitable machine code or computer language, which can be subjected to assembly, compilation, linking or similar mechanisms to create a code including instructions, which can be directly executed by one or more computer central processing units (CPUs), graphics processing units (GPUs), etc., or executed through interpretation, microcode execution, etc.
[0138] The instructions may be executed on various types of computers or components thereof, including, for example, personal computers, tablet computers, servers, smart phones, gaming devices, Internet of Things devices, and the like.
[0139] Fig. 9 A computer system (900) suitable for implementing certain embodiments of the disclosed subject matter is shown. Fig. 9 The components of the computer system (900) shown are exemplary in nature and are not intended to suggest any limitation on the scope of use or functionality of computer software implementing embodiments of the present disclosure. Neither should the configuration of components be interpreted as having any dependency or requirement relating to any one or combination of components shown in the exemplary embodiment of the computer system (900).
[0140] The computer system (900) may include certain human-machine interface input devices. Such human-machine interface input devices may be responsive to input from one or more human users through, for example, tactile input (e.g., keystrokes, swipes, data glove movements), audio input (e.g., voice, clapping), visual input (e.g., gestures), olfactory input (not depicted). Human-machine interface devices may also be used to capture certain media that are not necessarily directly related to human conscious input, such as audio (e.g., voice, music, ambient sounds), images (e.g., scanned images, captured images obtained from a still image camera), and videos (e.g., two-dimensional video, three-dimensional video including stereoscopic video).
[0141] The human-machine interface input device may include one or more of the following (only one of each is shown): keyboard (901), mouse (902), touchpad (903), touch screen (910), data gloves (not shown), joystick (905), microphone (906), scanner (907), camera (908).
[0142] The computer system (900) may also include certain human-computer interface output devices. Such human-computer interface output devices may stimulate one or more human user senses through, for example, tactile output, sound, light, and smell / taste. Such human-computer interface output devices may include tactile output devices (e.g., tactile feedback of a touch screen (910), a data glove (not shown), or a joystick (905), but may also be a tactile feedback device that is not an input device), audio output devices (e.g., speakers (909), headphones (not depicted)), visual output devices (e.g., screens (910) including CRT screens, LCD screens, plasma screens, OLED screens, each with or without touch screen input capabilities, each with or without tactile feedback capabilities, some of which are capable of outputting two-dimensional visual outputs or outputs in more than three dimensions through devices such as stereoscopic image output, virtual reality glasses (not depicted), holographic displays and smoke boxes (not depicted), and printers (not depicted).
[0143] The computer system (900) may also include human-accessible storage devices and their associated media, such as optical media including CD / DVD ROM / RW (920) with CD / DVD etc. media (921), thumb drives (922), removable hard drives or solid-state drives (923), traditional magnetic media such as tapes and floppy disks (not depicted), dedicated ROM / ASIC / PLD based devices such as security dongles (not depicted), and the like.
[0144] Those skilled in the art should also understand that the term "computer-readable media" used in connection with the presently disclosed subject matter does not encompass transmission media, carrier waves, or other transitory signals.
[0145] The computer system (900) may also include an interface (954) to one or more communication networks (955). The network may be, for example, a wireless network, a wired network, an optical network. The network may further be a local network, a wide area network, a metropolitan area network, a vehicle and industrial network, a real-time network, a delay-tolerant network, etc. Examples of networks include local area networks such as Ethernet, wireless LANs, cellular networks including GSM, 3G, 4G, 5G, LTE, etc., television wired or wireless wide area digital networks including cable television, satellite television, and terrestrial broadcast television, vehicle and industrial networks including CANBus, etc. Some networks typically require an external network interface adapter attached to some common data port or peripheral bus (949) (e.g., a USB port of the computer system (900)); as described below, other network interfaces are typically integrated into the kernel of the computer system (900) by attaching to the system bus (e.g., connected to an Ethernet interface in a PC computer system or connected to a cellular network interface in a smartphone computer system). The computer system (900) can use any of these networks to communicate with other entities. Such communications may be one-way receive only (e.g., broadcast television), one-way send only (e.g., CANBus connected to certain CANBus devices), or bidirectional, for example, using a LAN or WAN digital network to connect to other computer systems. As described above, certain protocols and protocol stacks may be used on each of those networks and network interfaces.
[0146] The above-mentioned human interface device, human-accessible storage device, and network interface may be attached to the kernel (940) of the computer system (900).
[0147] The kernel (940) may include one or more central processing units (CPUs) (941), graphics processing units (GPUs) (942), dedicated programmable processing units in the form of field programmable gate arrays (FPGAs) (943), hardware accelerators (944) for certain tasks, graphics adapters (950), and the like. These devices, as well as read-only memory (ROM) (945), random access memory (946), internal mass storage (947) such as internal non-user accessible hard drives, SSDs, and the like, may be connected via a system bus (948). In some computer systems, the system bus (948) may be accessed in the form of one or more physical plugs to enable expansion by additional CPUs, GPUs, and the like. Peripheral devices may be attached directly to the kernel's system bus (948) or to the kernel's system bus (948) via a peripheral bus (949). In one example, a screen (910) may be connected to a graphics adapter (950). The architecture of the peripheral bus includes PCI, USB, and the like.
[0148] The CPU (941), GPU (942), FPGA (943), and accelerator (944) may execute certain instructions, which may be combined to form the above-mentioned computer code. The computer code may be stored in ROM (945) or RAM (946). Transitional data may also be stored in RAM (946), while permanent data may be stored, for example, in internal mass storage (947). Fast storage and retrieval to any storage device may be performed by using a cache, which may be closely associated with one or more CPUs (941), GPUs (942), mass storage (947), ROM (945), RAM (946), etc.
[0149] The computer readable medium may have thereon computer codes for performing various computer-implemented operations. The medium and computer codes may be those specially designed and constructed for the purposes of the present disclosure, or the medium and computer codes may be of a type well known and available to those skilled in the art of computer software.
[0150] As an example, and not a limitation, a computer system having an architecture (900), particularly a kernel (940), may provide functionality due to one or more processors (including CPUs, GPUs, FPGAs, accelerators, etc.) executing software contained in one or more tangible computer-readable media. Such computer-readable media may be media associated with user-accessible mass storage as described above, as well as memories of certain non-temporary kernels (940), such as kernel internal mass storage (947) or ROM (945). Software implementing various embodiments of the present disclosure may be stored in such devices and executed by the kernel (940). Depending on specific needs, the computer-readable medium may include one or more storage devices or chips. The software may cause the kernel (940), particularly the processors therein (including CPUs, GPUs, FPGAs, etc.), to perform specific processes or specific parts of specific processes described herein, including defining data structures stored in RAM (946) and modifying such data structures according to processes defined by the software. Additionally or alternatively, the computer system may provide functionality due to logic hardwired or otherwise embodied in circuitry (e.g., accelerator (944)) that may replace software or operate in conjunction with software to perform specific processes or specific portions of specific processes described herein. Where appropriate, references to portions of software may include logic and vice versa. Where appropriate, references to portions of computer-readable media may include circuitry (e.g., integrated circuits (ICs)) storing software for execution, circuitry embodying logic for execution, or both. The present disclosure includes any suitable combination of hardware and software.
[0151] Although the present disclosure has described multiple exemplary embodiments, there are modifications, permutations, and various replacement equivalents that fall within the scope of the present disclosure. Therefore, it should be understood that those skilled in the art will be able to design many systems and methods that, although not explicitly shown or described herein, embody the principles of the present disclosure and therefore fall within the spirit and scope of the present disclosure.
Claims
1. A method for SEAL of a service enabling architecture layer, characterized in that: The method comprises: Receiving, at a first user equipment UE, a location reporting configuration from a location management server of the SEAL, the location reporting configuration indicating at least one location reporting event, the at least one location reporting event being used to trigger a first location information report from a first location management client at the first UE to the location management server; and In response to the at least one location reporting event occurring, sending the first location information report from the first location management client at the first UE to the location management server, the first location information report comprising: an identifier of the first UE, an identification of the at least one location reporting event that triggers the first location information report, first location information of the first UE, and a first timestamp corresponding to first location information of the first UE; sending a location information subscription request including a location information subscription configuration to the location management server, the location information subscription configuration including a periodic location information reporting timer, the location information subscription request configured to indicate a desired location information type, a set of location reporting events, and an interval for periodically providing location information notifications, the set of location reporting events being used to trigger location reporting from the first location management client; and Receive a location information notification from the location management server, the location information notification comprising: an identity of a third UE, an identifier of the first UE, an identifier of the event that triggered the location information notification, The latest location information of the third UE, and A fourth timestamp associated with the latest location information of the third UE.
2. The method according to claim 1, characterized in that The format of the first timestamp corresponding to the first location information of the first UE is one of the following: yyyy-month-dayTHH:MM:SS, Monday, DD Mon YYYY HH:MM:SS time zone, and yyyy-mn-ddTHH:MM:SS.
3. The method according to claim 1 or 2, characterized in that: The method further comprises: receiving a location information request from a location management server of the SEAL; and In response to the received location information request, a second location information report is sent to the location management server, the second location information report including the second location information of the first UE and a second timestamp corresponding to the second location information of the first UE.
4. The method according to claim 1 or 2, characterized in that: The method further comprises: sending a location report trigger to the location management server to activate a location reporting procedure for obtaining third location information of a second location management client of the SEAL at a second UE; and A third location information report is received from the location management server, wherein the third location information report includes third location information of the second UE and a third timestamp corresponding to the third location information of the second UE.
5. The method according to claim 1 or 2, characterized in that: The type of the first location information identified in the location reporting configuration is one of the following: E-UTRA cell global identifier ECGI, Multimedia Broadcast Multicast Service Area Identity MBMS SAI, and Geographic coordinates.
6. A method for SEAL of a service enabling architecture layer, characterized in that: The method comprises: Sending a location reporting configuration from a location management server to a first location management client of the SEAL at a first user equipment UE, the location reporting configuration indicating at least one location reporting event, the at least one location reporting event being used to trigger a first location information report from the first location management client of the SEAL at the first UE to the location management server; The first location information report is received from a first location management client of the SEAL at the first UE, the first location information report comprising: an identifier of the first UE, an identification of the at least one location reporting event that triggers the first location information report, first location information of the first UE, and a first timestamp corresponding to first location information of the first UE; and storing the first location information of the first UE in a memory; receiving, from a third location management client of the SEAL at a third UE and one of the second VAL server, a location information subscription request including a location information subscription configuration, the location information subscription configuration including a periodic location information reporting timer, the location information subscription request being configured to indicate a desired location information type, a set of location reporting events, and an interval for periodically providing location information notifications, the set of location reporting events being used to trigger a location report from the first location management client; In response to triggering a location information notification according to the location information subscription configuration, determining latest location information of one or more UEs including the first UE; and Sending the location information notification to one of the third location management client of the SEAL at the third UE and the second VAL server, the location information notification comprising: an identifier of the first UE, When receiving the location information subscription request from the third UE, the identifier of the third UE, an identifier of the event that triggered the location information notification, the latest location information of the first UE, and A fourth timestamp associated with the latest location information of the first UE.
7. The method according to claim 6, characterized in that The format of the first timestamp corresponding to the first location information of the first UE is one of the following: yyyy-month-dayTHH:MM:SS, Monday, DD Mon YYYY HH:MM:SS time zone, and yyyy-mn-ddTHH:MM:SS.
8. The method according to claim 6 or 7, characterized in that: The method further comprises: sending a location information request to a first location management client of the SEAL at the first UE; receiving a second location information report from a first location management client of the SEAL at the first UE, the second location information report comprising second location information of the first UE and a second timestamp corresponding to the second location information of the first UE; and The second location information of the first UE is stored in the memory.
9. The method according to claim 6 or 7, characterized in that: The method further comprises: receiving a location reporting trigger from a second location management client of the SEAL or a first vertical application layer VAL server at a second UE; In response to receiving the location report trigger, initiating a location reporting process to obtain third location information of the first UE; and A third location information report is sent to the second location management client of the SEAL or the first VAL server at the second UE, the third location information report including the third location information of the first UE and a third timestamp corresponding to the third location information of the first UE.
10. The method according to claim 6 or 7, wherein: The type of the first location information identified in the location reporting configuration is one of the following: E-UTRA cell global identifier ECGI, Multimedia Broadcast Multicast Service Area Identity MBMS SAI, and Geographic coordinates.
11. A user equipment UE, comprising: a memory for storing instructions; as well as A processor configured to execute the instructions to perform the method according to any one of claims 1-5.
12. A location management server, comprising: a memory for storing instructions; as well as A processor configured to execute the instructions to perform the method according to any one of claims 6-10.
13. A non-transitory computer-readable medium storing instructions, which, when executed by a processor, cause the processor to perform the method according to any one of claims 1 to 5 or the method according to any one of claims 6 to 10.
