Methods, apparatuses, and computer devices for a Service Enablement Architecture Layer (SEAL)

Abstract

Methods, apparatuses, and computer devices for providing a service enabler architecture layer (SEAL) are provided. At a network resource management server in the SEAL, a request for network connection status information (also referred to as a detection event subscription request for network connection status information) is received from a vertical application layer (VAL) server. The request for the network connection status information may indicate: a target VAL user equipment (UE), a type of the network connection status information, and a timeout duration, where the timeout duration indicates an amount of time elapsed after the detection event subscription request is sent. The requested network connection status information is not sent after the timeout duration. Based on the detection event subscription request for the network connection status information, the network connection status information of the target VAL UE may be obtained from a wireless network system. A network connection status information response message may be sent from the network resource management server in the SEAL to the VAL server. The network connection status information response message includes the network connection status information of the target VAL UE.

Description

[0001] Incorporation by Reference

[0002] This application claims priority to U.S. Patent Application No. 17 / 499,673, entitled "Network Monitoring in Service Enabler Architecture Layer (SEAL)", filed on October 12, 2021, which claims priority to U.S. Provisional Application No. 63 / 172,052, entitled "A Method for 3GPP UE to Query Network Connection Status When Using SEAL Architecture", filed on April 7, 2021. The entire disclosures of these prior applications are incorporated herein by reference. Technical Field

[0003] The embodiments described in this application generally relate to service enabling layers for supporting vertical applications operating over wireless networks. Background Art

[0004] The background description provided herein is for the purpose of generally presenting the context of this application. Work of the presently named inventors, which is described in the background section herein, and aspects of the description which may not constitute prior art at the time of filing, whether explicitly or implicitly, are not admitted to be prior art to this application.

[0005] Wireless communication systems are designed with advanced built-in capabilities to support enterprise sectors or vertical industries such as healthcare, automotive, smart factories, mission-critical communications, etc. Vertical application standards are under development to enable rapid deployment of vertical services based on common services provided by wireless networks. A vertical domain can be an industry or group of enterprises producing similar products or services. A vertical application can provide services or functions useful in a particular vertical domain. Summary of the Invention

[0006] Aspects of the present application provide a method for a service enabler architecture layer (SEAL). The method may include receiving, at a network resource management server in the SEAL, a request for network connection status information (also referred to as a detection event subscription request for network connection status information) from a vertical application layer (VAL) server. The request for the network connection status information may indicate: a target VAL user equipment (UE), the type of the network connection status information, and a timeout duration, where the timeout duration indicates the amount of time elapsed after the detection event subscription request is sent, and where the requested network connection status information is not sent after the timeout duration. Based on the detection event subscription request for the network connection status information, the network connection status information of the target VAL UE may be obtained from a wireless network system. A network connection status information response message may be sent from the network resource management server in the SEAL to the VAL server. The network connection status information response message includes the network connection status information of the target VAL UE.

[0007] In one embodiment, the network connection status information corresponds to a detection event related to a target UE of interest to the VAL server and is detected in the wireless network system based on predefined conditions. In one embodiment, the network connection status information includes one of the following: connection loss of the target VAL UE and the connection bandwidth of the target VAL UE to the wireless network system.

[0008] In one embodiment, the request for network connection status information includes a subscription to the type of network connection status information. In one embodiment, the subscription indicates the frequency of providing network connection status information from the network resource management server to the VAL server.

[0009] In one embodiment, the network connection status information response message indicates the identity of the target VAL UE and the network connection status information of the target VALUE. In one embodiment, the network connection status information response message further indicates a timestamp corresponding to the network connection status information of the target VALUE.

[0010] The method embodiment may further include: in response to the received request for network connection status information, sending, from the network resource management server in the SEAL to the VAL server, a network connection status information request acceptance message indicating that the request for network connection status information is authorized.

[0011] Aspects of the present application provide a non - volatile computer - readable medium storing instructions which, when executed by a processor, cause the processor to perform the above - described SEAL method.

[0012] Aspects of the present application provide a SEAL device. The device may include circuitry configured to receive, at a network resource management server in SEAL, a request for network connection status information (also referred to as a detection event subscription request for network connection status information) from a vertical application layer (VAL) server. The request for the network connection status information may indicate: a target VAL user equipment (UE), a type of the network connection status information, and a timeout duration, where the timeout duration indicates an amount of time elapsed after the detection event subscription request is sent, and where the requested network connection status information is not sent after the timeout duration. Based on the detection event subscription request for the network connection status information, the network connection status information of the target VALUE may be obtained from a wireless network system. A network connection status information response message including the network connection status information of the target VALUE may be sent from the network resource management server in the SEAL to the VAL server. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] Other 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:

[0014] Figure 1 A general online function model of an embodiment of the present application is shown;

[0015] Figure 2 An exemplary online network resource management function model of some embodiments of the present application is shown;

[0016] Figure 3 An event subscription and notification method of some embodiments of the present application is shown;

[0017] Figure 4 A network connection status detection method of some embodiments of the present application is shown;

[0018] Figure 5 A network detection method of an embodiment of the present application is shown;

[0019] Figure 6 A network detection method according to an embodiment of the present application is shown;

[0020] Figure 7 A schematic diagram of a computer system of an embodiment is shown. Detailed Implementation Manner

[0021] I. Service Enabling Layer for Vertical Applications

[0022] 1. Service Enabler Architecture Layer (SEAL)

[0023] Embodiments of the present application implement a service enabling layer for supporting vertical applications (or vertical industries). In the present application, the service enabling layer can be referred to as the Service Enabler Architecture Layer (SEAL). SEAL can provide a set of common capabilities (or services) used by multiple vertical applications to accelerate the development and deployment of vertical applications. For example, commonly required auxiliary services can be provided in SEAL and shared by multiple vertical applications, rather than developing auxiliary services for each vertical application. The use of all SEAL services by vertical applications can be optional. A vertical application can decide to use any subset of SEAL services.

[0024] 2. Generic Functional Model for SEAL Services

[0025] In some embodiments, the functional model of SEAL can be organized into a generic SEAL service functional model and multiple specific SEAL service functional models. The generic SEAL service functional model can be used as a reference model for specific SEAL service functional models. The generic functional model can include an on-network functional model and an off-network functional model. In various embodiments, the SEAL services provided to support the vertical application layer can include location management, group management, configuration management, identity management, key management, network resource management, etc.

[0026] Figure 1Shows a general online function model (100) of an embodiment of the present application. 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 each type of functional entity in the model (100) may be one or more than one. The VAL client and VAL server entities may belong to the VAL (101). The SEAL client and 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 radio network system (140) (such as a 3rd Generation Partnership Project (3GPP) network system). These elements may be coupled together as Figure 1 shown.

[0027] In the VAL (101), the VAL client (111) communicates with the VAL server (121) through a VAL-UU reference point (134) corresponding to the VAL-UU interface. In one example, the VAL-UU interface supports unicast and multicast transmission modes.

[0028] The SEAL (102) provides various services to the VAL (101). One or more SEAL clients communicate with one or more SEAL servers through one or more SEAL-UU reference points (133) corresponding to the SEAL-UU interface. The SEAL-UU interface supports unicast and multicast transmission modes. One or more SEAL clients provide service enabling layer support functions to one or more VAL clients through a SEAL-C reference point (131) (corresponding to the SEAL-C interface). One or more VAL servers communicate with one or more SEAL servers through one or more SEAL-S reference points (corresponding to the SEAL-S interface). One or more SEAL servers (122) may communicate with the underlying 3GPP network system (140) using corresponding 3GPP interfaces (135) specified by the 3GPP network system.

[0029] For a specific service (such as a location management service), a specific SEAL client and a specific SEAL server and their specific SEAL-UU reference points and a specific network interface of the 3GPP network system may form a specific online function model or belong to a specific online function model.

[0030] In some embodiments, to support distributed SEAL server deployment, the SEAL server may pass through a so-called SEAL-E reference point ( Figure 1interact with another SEAL server for the same SEAL service (not shown in the figure). The SEAL server can interact with another SEAL server for inter-service communication through a so-called SEAL-X reference point ( Figure 1 not shown in the figure). The SEAL server can interact with the VAL user database for storing and retrieving user description data through the VAL-UDB reference point.

[0031] In various embodiments, the functional entities in the VAL system (e.g., including VAL 101 and SEAL 102) can provide application control and media-specific functions to support one or more VAL services. In Figure 1 the example, the VAL client (111) (e.g., a vehicle-to-everything (V2X) client) can provide client-side functions corresponding to a vertical application (e.g., a V2X application). The VAL client (111) can support the interaction between the vertical application and one or more SEAL clients (112). The VAL server (121) (e.g., a V2X application server) can provide server-side functions corresponding to the vertical application.

[0032] In Figure 1 the example, the SEAL client (112) can provide client-side functions corresponding to a specific SEAL service (e.g., location management, network resource management, etc.). The SEAL client (112) can support the interaction between one or more VAL clients (111). The SEAL client can also support the interaction between the corresponding SEAL clients in two UEs. The SEAL server (122) can provide server-side functions corresponding to a specific SEAL service. The SEAL server (122) can support the interaction between one or more VAL servers (121). The SEAL server can also support the interaction with the corresponding SEAL server in a distributed SEAL deployment.

[0033] Note that in different embodiments, each functional entity in the model (100) can be implemented in various ways. For example, each functional entity can be implemented in a distributed manner or a centralized manner. Each functional entity can be implemented as software or a combination of software and hardware.

[0034] In Figure 1In an example, a VAL user database (not shown) may include user profile data associated with VAL services provided by a VAL service provider. Generally, 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.

[0035] In some embodiments, the interaction between a VAL client (111) and a VAL server (121) related to the VAL (101) support function is supported by a VAL-UU reference point (134). In one example, this reference point (134) is an instance of the Uu reference point as described in 3GPP TS 23.401 and 3GPP TS 23.501. In some embodiments, the interaction between VAL clients of two UEs related to the VAL support function may be supported by a VAL-PC5 reference point (not shown). For example, this reference point may be an instance of the PC5 reference point as described in 3GPP TS 23.303.

[0036] In some embodiments, the interaction between a SEAL client (112) and a corresponding SEAL server (122) is supported by a SEAL-UU reference point (133). The specific SEAL service reference point corresponding to SEAL-UU (133) may be specified in a specific SEAL service function model. In some embodiments, the interaction between SEAL clients of two VAL UEs may be supported by a SEAL-PC5 reference point (not shown). The specific SEAL service reference point corresponding to SEAL-PC5 may be specified in a specific SEAL service function model.

[0037] In some embodiments, the interaction between one or more VAL clients (111) and one or more SEAL clients (112) within a VAL UE (110) is supported by a SEAL-C reference point (131). The specific SEAL service reference point corresponding to SEAL-C (131) may be specified in a specific SEAL service function model.

[0038] In some embodiments, the interaction between a VAL server (121) and a SEAL server (132) is supported by a SEAL-S reference point (132). The specific SEAL service reference point corresponding to SEAL-S (132) may be specified in a specific SEAL service function model.

[0039] In some embodiments, the interaction between SEAL servers of the same type (e.g., providing the same type of SEAL service) is supported by a SEAL-E reference point (not shown). The specific SEAL service reference point corresponding to SEAL-E is specified in a specific SEAL service function model.

[0040] In some embodiments, the interaction between different types of SEAL servers can be supported by a SEAL-X reference point. Examples of specific reference points corresponding to the SEAL-X reference point can include the reference point SEAL-X1 between the key management server and the group management server, and the reference point SEAL-X2 between the group management server and the location management server.

[0041] The reference point VAL-UDB exists between the VAL user database and the SEAL server. The reference point VAL-USB can be used to store user profile data in a specific VAL user database and obtain user profiles from a specific VAL user database for further configuration in the UE.

[0042] 3. Identification

[0043] In various embodiments, different identifications can be configured and used in the VAL system developed based on the model (100). In some embodiments, a VAL user can provide a user identification (user ID) to the identification management server in the SEAL (102) during the user authentication process to provide a way for VAL service authentication to the identification management client. Generally, since identification management is a conventional SEAL service, the identification management server uses a set of credentials (e.g., biometric information, secureID, username / password) that may not have to be bound to a single VAL service. The user credentials uniquely identify the VAL user to the identification management server. As an example, specific security and authentication mechanisms required for using the user ID are specified in 3GPP TS 33.434.

[0044] In some embodiments, the VAL user ID is a unique identification within the VAL service and is used to represent the VAL user. 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 the VAL user through the VAL UE. The VAL user ID also indicates the VAL service provider that has a VAL service agreement with the VAL user. The VAL user can enter into a VAL service agreement with the VAL service provider and thus has obtained a unique VAL user ID corresponding to the VAL service provider one by one. The VAL user ID can be used to access SEAL services.

[0045] In some embodiments, the VAL UE ID is a unique identifier within the VAL service, representing the VAL UE. For example, the VAL UE ID of the V2X service is mapped to the base station ID specified in ETSI TS 102 894-2. The VAL UE ID is used to address the VAL UE to send VAL messages.

[0046] In some embodiments, the VAL service ID is a unique identifier representing the VAL service. The VAL server provides a list of VAL services to each VAL user or each VAL UE. Each VAL service is uniquely identified by the VAL service ID, which is the identifier of the VAL application that provides the VAL service. The VAL service ID can be used for policy mapping, QoS handling of VAL communication, and VAL message distribution. For example, the identifier of the V2X service, such as the ITS-AID or PSID specified in ETSI TS 102 965 and ISO TS 17419, can be used as the V2X service ID.

[0047] In some embodiments, the VAL group ID is a unique identifier within the VAL service that represents a group of VAL users or a group of VAL UEs according to the VAL service. This group of VAL users can belong to the same or different VAL service providers. The VAL group ID indicates the VAL application server that defines the group.

[0048] In some embodiments, the VAL system ID is a globally unique identifier representing the VAL system. In some embodiments, the VAL flow ID is the identifier used by the VAL server to identify the VAL flow.

[0049] 4. Application of the Functional Model in Deployment

[0050] In various embodiments, the SEAL architecture described above can support deployment modes within and / or outside the public land mobile network (PLMN) network. The SEAL architecture can also support centralized deployment and distributed deployment of vertical applications. The mobile network operator (MNO) can adopt a suitable deployment model according to its needs for its business.

[0051] Deploying the model may involve multiple entities, such as VAL users, VAL service providers, SEAL providers, and PLMN operators. For example, in a possible deployment model, one or more SEAL servers may be deployed within the PLMN operator domain, and vertical application servers may be deployed within the VAL service provider domain. The SEAL server may also use the SEAL-E interface to interact with another SEAL server that provides the same SEAL service and is deployed in a different PLMN operator domain.

[0052] There may be multiple business relationships among the multiple entities involved in the deployment. Based on the service-specific protocol, the VAL user belongs to the VAL service provider domain. The VAL service provider and the home PLMN operator may belong to the same organization. The VAL service provider may have a service agreement with the SEAL service provider. The VAL service provider, the SEAL service provider, and the home PLMN operator may also belong to the same organization. When the VAL service provider and the home PLMN operator do not belong to the same organization, they may have a service agreement.

[0053] 5. SEAL-based V2X Vertical Application

[0054] In one embodiment, a V2X vertical application is developed based on the SEAL service. SEAL can support multiple SEAL services. Each SEAL service can support multiple processes. Generally, the SEAL client does not initiate a process actively. To enable the SEAL client to start a process, the V2X vertical application needs to provide the SEAL client with trigger information and parameters related to the process.

[0055] For example, the V2X application-level function model is defined in 3GPP TS 23.286. As defined, the V2X application enabler (VAE) layer provides VAE functions for the V2X application-specific layer. The VAE layer uses the SEAL service. The VAE client can act as a VAL client to interact with the SEAL client in the manner specified by the SEAL architecture. The VAE server can act as a VAL server to interact with the SEAL server in the manner specified by the SEAL architecture.

[0056] The V2X application layer can provide a group joining policy and a group leader for each group. The VAE client and the 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. Before the V2X UE starts receiving V2X services from the V2X application layer, the VAE client and the VAE server can use the SEAL configuration management service to provide configuration information to the V2X UE. When the V2X UE has received V2X services from the V2X application layer, the VAE client and the VAE server can also use the SEAL configuration management service to provide configuration updates to the V2X UE.

[0057] The VAE client and the VAE server can use the SEAL location management service to manage the location information of the V2X UE and update the location information to the V2X application layer. The VAE client and the VAE server can use the SEAL identity management service to authenticate and authorize the V2X UE to use the V2X application server. The VAE client and the VAE server can use the SEAL network resource management service to establish, modify bearers, and switch between different types of bearers.

[0058] The VAE server can also use the SEAL API to use the SEAL services to enable 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 at 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.

[0059] In various embodiments, multiple vertical applications can use the SEAL services simultaneously. For example, two vertical applications, V2X and MCPTT, can use the SEAL services. The SEAL server can establish a connection between the two vertical application servers. In addition, each vertical dedicated UE can 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.

[0060] II. Network Resource Management Service

[0061] 1. Functional Model of Network Resource Management

[0062] Figure 2 Shows the functional model (200) of the network resource management SEAL service in some embodiments of the present application. The functional model (200) can be based on Figure 1The general function model (100) shown in [figure]. The function model (200) may include a VAL client (211), a VAL server (221), a network resource management client (212), and a network resource management server (222). The VAL client (211) and the VAL server (221) may be included in the VAL (201). The network resource management client (212) and the network resource management server (222) may be included in the SEAL (202). The VAL client (211) and the network resource management client (212) may be in the VAL UE (210). In addition, the function model (200) may further include a 3GPP network system (240).

[0063] In some embodiments, the network resource management client (212) communicates with the network resource management server (222) through a reference point (233) represented by NRM-UU. "NRM" stands for "network resource management". The network resource management client (212) provides support for network resource management functions to the VAL client (211) through a reference point (231) represented by NRM-C. The VAL server (221) communicates with the network resource management server (222) through a reference point (232) represented by NRM-S. The VAL client (211) communicates with the VAL server (221) through a reference point (234) represented by VAL-UU. The VAL UE (210) may communicate with the 3GPP network system (240) through, for example, a UU interface (not shown) specified in the 3GPP standard.

[0064] In some embodiments, the network resource management server (222) may communicate with the 3GPP network system (240) through one or more interfaces to utilize various services provided by the 3GPP network system (240). In one example, the network resource management server (222) may communicate with the Broadcast Multicast Service Center (BM-SC) in the 3GPP network system (240) through the MB2-C reference point (235A) or the xMB-C reference point (235B) to obtain and control multicast resources from the underlying 3GPP network system (240). In one example, the network resource management server (222) communicates with the Policy and Charging Rules Function (PCRF) in the 3GPP network (240) through the Rx reference point (235C), or communicates with the Policy Control Function (PCF) in the 3GPP network system (240) through the N5 reference point (235D) to control unicast resources from the underlying 3GPP network system (240).

[0065] In one example, the network resource management server (222) communicates with the service capability exposure function (SCEF) through the T8 reference point (235E), or communicates with the network exposure function (NEF) through the N33 reference point (235F) to perform an event monitoring procedure from the underlying 3GPP network system (240). In one example, the network resource management server (222) interacts with the NEF through the N33 reference point (235F) to obtain QoS detection information from the 3GPP network system (240). Examples of the above functions and reference points can be referred to the relevant 3GPP standards.

[0066] In some embodiments, there may be multiple VAL clients and multiple VAL servers in the VAL UE 210. These functional entities can utilize the network resource management services provided by the network resource management client (212) and the network resource management server (222). In addition, in some embodiments, other types of (standardized or non-standardized) network systems outside the 3GPP network system (240) can be used in the VAL system implementing the functional model (200). For example, instead of the 3GPP network system (240), these various types of network systems can provide a wireless connection to the VAL UE for communicating with the VAL server or the network resource management server (222), or expose the service capabilities of the above SEAL (202) and VAL (201).

[0067] Contrary to Figure 2 the online model (200) shown in, the offline functional model of the network resource management SEAL service may include a first UE and a second UE. These two UEs can communicate through the PC5 reference point or the PC5 interface. For example, each UE may include one or more VAL clients in the VAL. The VAL clients of the first UE and the second UE can communicate through the VAL-PC5 reference point. Each UE may include a network resource management client. The network resource management clients of the first UE and the second UE can communicate through the NRM-PC5 reference point.

[0068] In some embodiments, the network resource management client (212) acts as an application client for managing network resources. The network resource management client (212) interacts with the network resource management server (222). The network resource management server (222) provides management of 3GPP system network resources (such as unicast, multicast) and detection event notifications to support the VAL application. The network resource management server (222) also supports interaction with the corresponding network resource management servers in the distributed SEAL deployment. In one embodiment, the role of the network resource management server is assumed by the VAL server in the deployment manner. At this time, the VAL server executes the network resource management process instead of the network resource management server.

[0069] In some embodiments, the interaction related to the network resource management function between the network resource management client (212) and the network resource management server (222) is supported by the NRM-UU reference point. This reference point utilizes the Uu reference point described in 3GPP TS 23.401 and 3GPP TS 23.501. In some embodiments, the interaction related to the network resource management function between the network resource management clients in different VAL UEs is supported by the NRM-PC5 reference point. This reference point utilizes the PC5 reference point described in 3GPP TS23.303.

[0070] In some embodiments, the interaction related to the network resource management function between the VAL server (221) and the network resource management server (222) is supported by the NRM-S reference point. This reference point can be an instance of the CAPIF-2 reference point specified in 3GPP TS 23.222. In some embodiments, the interaction related to the network resource management function between the network resource management servers in the distributed deployment is supported by the NRM-E reference point.

[0071] In some embodiments, the reference point MB2-C supports the control plane interaction between the network resource management server (222) and the BM-SC, and is specified by 3GPP TS 29.468. In some embodiments, the reference point xMB-C supports the control plane interaction between the network resource management server (222) and the BM-SC, and is specified by 3GPP TS26.348. In some embodiments, the reference point Rx supports the interaction between the network resource management server (222) and the PCRF, and is specified by 3GPP TS 29.214.

[0072] In some embodiments, the reference point N5 supports the interaction between the network resource management server (222) and the PCF, such as the interaction specified in 3GPP TS 23.501. In some embodiments, the reference point N33 supports the interaction between the network resource management server (222) and the NEF, such as the interaction specified in 3GPP TS 23.501. In some embodiments, the reference point T8 supports the interaction between the location management server (222) and the SCEF, such as the interaction specified in 3GPP TS 23.682.

[0073] 2. Exemplary Network Connection Status Detection Process

[0074] 2.1 Event Detection

[0075] In some embodiments, an event detection scheme is used to provide a network connection status detection service, which is part of the network resource management SEAL service. For example, the VAL server can use the network resource management server to detect events related to the VAL UEs served by the VAL server. Based on the detection event subscription request of the VAL server, the network resource management server can subscribe to multiple core network services of the underlying radio access network system to obtain the required events related to the multiple VALUEs served by the VAL server. Then, the network resource management server can report the obtained events to the VAL server.

[0076] In some embodiments, in order to detect and report detection events related to the VAL UE from the 3GPP core network, the network resource management server can use the detection event process specified in 3GPP TS 23.502. In order to detect and report analysis events related to the VAL UE, the network resource management server can use related processes such as those specified in 3GPP TS 23.288.

[0077] Figure 3 An event subscription and notification method (300) of some embodiments of the present application is shown. The method (300) can be executed between the 5G core network (301), the network resource management server (302), and the VAL server (303). During the method (300), the VAL server (303) subscribes to the service of the network resource management server (302) to detect events related to one or more VAL UEs (not shown) served by the VAL server (303). Based on the VAL server request, the network resource management server (302) consumes relevant core network services to receive events related to the VAL UE. The method (300) can start from (S310).

[0078] At (S310), the VAL server (303) sends a detection event subscription request to the network resource management server (302) to request the network resource management server (302) to detect events related to the VAL UE according to the subscription request.

[0079] The detection event subscription request may include information related to events of interest to the VAL server. In some embodiments, the detection event subscription request may include one or more of the following information elements. (1) A list of VAL users or VAL UEs for which event detection is requested. (2) A list of detection events and / or analysis events of interest to the VAL server. In one embodiment, for each VAL user or VAL UE in the listed VAL users or VAL UEs, a list of detection events and / or analysis events is provided. In one embodiment, a common list of detection events and / or analysis events is provided for the listed VAL users or VAL UEs. (3) The timeout duration for sending the subscription response from the network resource management server (302) to the VAL server (303). In one example, when no detection event subscription response is received at the VAL server (303) within the timeout duration starting from when the event detection event subscription request is sent, the VAL server (303) may consider the subscription request to have failed or been rejected. In one example, the timeout duration is used to specify a period after which the requested detection event subscription ends.

[0080] In some embodiments, the detection event subscription request may include the information listed in Table 1 below.

[0081] Table 1

[0082]

[0083]

[0084] In Table 1, "M" represents "mandatory" and "O" represents "optional".

[0085] At (S320), the network resource management server (302) may check whether the VAL server (303) is authorized to initiate a detection event subscription request. If authorized, the network resource management server (302) may respond to the VAL server (303) with a detection event subscription response message indicating a successful subscription status. The detection event subscription response message may include relevant subscription information to confirm the detection event subscription. If not authorized, the network resource management server (302) may respond with a detection event subscription response message indicating that the subscription request has been rejected.

[0086] In some embodiments, the detection event subscription response may include the information listed in Table 2 below.

[0087] Table 2

[0088] Information element Status Description Subscription status M Indicates the subscription result.

[0089] At (S330), based on the event of interest information in the event detection subscription request message at (S310), the network resource management server (302) may subscribe to UE detection events and / or UE analysis events from the 5G core network (301) for a set of UEs (VAL UEs) listed in the detection event subscription request.

[0090] Examples of detection events may include connection loss, UE reachability, location reporting, roaming status, communication failures, the number of UEs present in a geographical area, etc. Examples of analysis events may include UE mobility analysis, UE communication analysis, expected UE behavior parameters related to network data analysis, abnormal behavior related to network data analysis, etc.

[0091] In some embodiments, the network resource management server (302) performs the subscription of UE detection events based on the procedures specified in 3GPP TS 23.502. For example, the network exposure function may be employed to support the external exposure of network function capabilities. The external exposure may be classified into detection capabilities, provisioning capabilities, policy / charging capabilities, network status reporting capabilities, and analysis reporting capabilities. The detection capabilities are used to detect specific events of UEs in the 5G system and make such detection event information available for external exposure through the NEF. For example, ways are provided for configuring specific events, event detection, and reporting events to the requesting party. A list of detection events and related detection criteria is specified in 3GPP 23.502.

[0092] In some embodiments, the network resource management server (302) performs the subscription of UE analysis events. The subscription may be performed based on the procedures specified in 3GPP TS 23.288. For example, one or more network data analytics functions (NWDAF) may be employed to support data collection based on the subscription of events provided by the data consumer (e.g., the network resource management server (302)). The analysis information may be statistical information or prediction information of past events.

[0093] Using the 5G core network (301) as Figure 3 An example, in some embodiments, other types of wireless or wired network systems may be used to support the network resource management server (302) in detecting related events.

[0094] At (S340), the 5G core network (301) may send the subscribed events of the UE in the UE detection event notification to the network resource management server (302) according to the detection event subscription at (S330). Correspondingly, the network resource management server (302) receives the UE detection event notification from the 5G core network (301).

[0095] At (S350), the network resource management server (302) may notify the VAL server (303) of the events related to the VAL UE in the notification detection event message. In one embodiment, when multiple events need to be notified, the network resource management server (302) may merge these notifications and send them to the VAL server (303).

[0096] In some embodiments, the notification detection event message may include one or more of the following information elements. (1) A list of events and one or more related VAL UEs. Each entry in the list may include (i) the VAL UE related to the event, and (ii) a list of detection events and / or analysis events related to the corresponding VAL UE. (2) Optionally, a timestamp corresponding to each of the listed detection events and analysis events.

[0097] In some embodiments, the timestamp in the notification detection event message may be in one of several different time formats, such as ISO 8610 (e.g., yyyy - Month - DayTHH: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.

[0098] In some embodiments, the notification detection event message may include the information listed in Table 3 below.

[0099] Table 3

[0100]

[0101] The method (300) may terminate after (S350).

[0102] In some embodiments, an application programming interface (API) is used for the method (300) of detection event subscription and notification. The API is called an event detection API. In one example, the event detection API defines two API operations: the subscribe - detection - event API operation for subscribing to detection events, and the notify - detection - event API operation for notifying the VAL server of the detection events related to one or more VAL UEs.

[0103] For example, the VAL server (303) may be a user of the subscription-detection-event API operation. Corresponding to (S310) and (S320) of the method (300), the information elements in the detection event subscription request can be used as the input of the subscription-detection-event API operation, and the information elements in the detection event subscription response can be used as the output of the subscription-detection-event API operation.

[0104] In another example, the VAL server (303) may be a consumer of the notification-detection-event API operation. Corresponding to (S350) of the method (300), the information elements in the notification detection event message can be used as the input of the notification-detection-event API operation.

[0105] 2.2 Network Connection Status Detection

[0106] In some embodiments, the network resource management client or the VAL server in the VAL system may be configured to provide a network connection status detection function. In some embodiments, the network connection status detection function may be performed in real time. For example, the network connection status of the VAL UE or VAL user of the VAL system can be detected based on the network connection status detection service provided by the network resource management server. For certain VAL services, it may be crucial to always detect the network connection status. For example, losing the connection may have extremely serious consequences for certain vertical services.

[0107] Figure 4 A network connection status detection method (400) of some embodiments of the present application is shown. The method (400) may be executed among the VAL server (403), the network resource management server (402), and the 5G core network (401). The VAL server (403) is used to explain the method (400) Figure 4 In the method (400), the network resource management client in the VAL UE may also be used to execute the method (400) instead of the VAL server (403) to detect the network connection status of other VAL UEs. In addition, other types of wireless or wired networks outside the 3GPP network system may be used to support the method (400).

[0108] In the network connection status detection method (400), the VAL server (403) may send a request for the network connection status information of the target VAL UE to the network resource management server (402). In response, the network resource management server (402) may report the network connection status of the target VAL UE to the VAL server (403) according to the request. The method (400) may start from (S410).

[0109] At (S410), a network connection status information request message can be sent from the VAL server (403) to the network resource management server (402). The network connection status information request (also referred to as a detection event subscription request for network connection status information) can indicate one or more target VAL UEs whose network connection status information is requested. For example, the identification of a VAL UE or a VAL user defined at the VAL can be used to identify the target UE.

[0110] In some embodiments, the network connection status information request can indicate which types of network connection statuses are to be detected. The types of network connection statuses to be detected can include connection loss, connection bandwidth, UE reachability, location reporting, protocol data unit (PDU) session status, etc.

[0111] In some embodiments, the network connection status information request can additionally or optionally indicate how each type of network connection status is to be detected and reported. In some embodiments, the request can include a subscription. In one example, the network connection status information request can indicate the frequency (or pull frequency) at which the network resource management server (402) periodically reports the current status of each network connection status to be detected.

[0112] In one example, the network connection status information can be event-based. The event can be related to bandwidth and / or connection test events. In one embodiment, the event can be time-based, such as in response to a subscribed query or frequency. In some embodiments, the request can indicate a certain condition, and when the condition is triggered, the corresponding network connection status is reported. For example, the condition can be when the VAL UE loses connection, when the VAL UE changes its PDU session, when the UE leaves or enters a certain area, etc. In some embodiments, such network connection status changes can be referred to as events. For example, a set of network connection status events and related trigger or detection conditions can be predefined. A list of such predefined events can be included in the network connection status information request and provided from the VAL server (403) to the network resource management server (402).

[0113] In some embodiments, the network connection status information request can indicate the identification of one or more entities. The one or more entities can include the VAL server (e.g., Figure 4 the VAL server (403) in the example), the identification of a VAL user, and / or a VAL UE. In one embodiment, the one or more entities can include the entity that executes the request. In one embodiment, the one or more entities include the VAL user or VAL UE for which detection (e.g., event detection) is requested.

[0114] In some embodiments, the network connection status information request may further indicate which service is requesting the network connection status information. For example, the VAL server (403) may operate and provide multiple services corresponding to specific vertical applications. In some examples, the information about the service that is requesting the network connection status information may help to address the target service at the VAL server (403).

[0115] In some embodiments, the network connection status information request may further indicate a timeout duration. The timeout duration may be used to send a response from the network resource management server (402) to the VAL server (403). In one example, when no network connection status information request acceptance message is received at the VAL server (403) from the network resource management server (402) within the timeout duration calculated from the time of sending the network connection status information request, the VAL server (403) may consider the request to have failed or been rejected. In one example, the timeout duration specifies a period after which the transmission of the requested network connection status information ends. The network resource management server (402) may stop providing the network status detection report to the VAL server (403).

[0116] In one embodiment, the network connection status information request may include one or more of the following information elements in Table 4.

[0117] Table 4

[0118]

[0119] In one embodiment, if the information element of "requested VAL service" in Table 4 does not exist, the network connection status may be requested for all existing and running VAL services on the client side.

[0120] At (S420), the network resource management server (402) may send a network connection status information request acceptance message to confirm or reject the network connection status information request of the VAL server (403). For example, the network resource management server (402) may check whether the VAL server (403) has the authorization to request the corresponding network connection status. In one example, the authorization may be an authorization dedicated to different types of network connections.

[0121] (S430) and (S440) can be performed in a manner similar to (S330) and (S340) so that the network resource management server (402) obtains network connection status information from the underlying 5G core network (401). Note that the detection event-based subscription and notification operations described herein are merely examples of how SEAL obtains network connection status information from the underlying network system. In various examples, there can be various ways to obtain the desired network connection status information. For example, the network resource management server (402) can query the underlying network system at any time or periodically to obtain the type of network connection status.

[0122] In (S450), a network connection status information response message can be sent from the network resource management server (402) to the VAL server (403) to report the network connection status information of the target VAL UE. For example, a list of VAL UEs can be indicated in the network connection status information response, such as listing the identities of the VAL UEs. The listed VAL UEs can be the complete set or a subset of the target VAL UEs indicated in the network connection status information request of (S410). Network connection status information can be provided for each of the listed VAL UEs.

[0123] In some embodiments, the network connection status information of the target VAL UE in the response message can be the current status of the target VAL UE. For example, the network resource management server (402) can query the underlying 5G core network periodically or in response to a network connection status information request to obtain the information. In some embodiments, the network connection status information of the target VAL UE in the response message can be an event related to the target VAL UE. For example, the event is detected by the underlying 5G core network (401).

[0124] In some embodiments, the network connection status information response message can further include a timestamp, such as a timestamp corresponding to each network connection status information of a specific target VAL UE. For example, for the current network connection status, a timestamp can be provided to indicate the time when the corresponding status information was obtained. For a detected event, a timestamp can be provided to indicate the time when the event occurred or was detected.

[0125] In some embodiments, the network connection status information response message can be sent in response to a network connection status information request message. In some embodiments, the network connection status information response message can be sent periodically based on the indication of the network connection status information request. In some embodiments, when the event indicated in the network connection status information request message is detected or triggered, the network connection status information response message can be sent.

[0126] In one embodiment, the network connection status information response message may include the following information in Table 5.

[0127] Table 5

[0128]

[0129] III. Exemplary Network Detection Process

[0130] Figure 5 The network detection method (500) of an embodiment of the present application is shown. The method (500) may be executed by a network resource management server in SEAL. The method (500) may start at (S501) and proceed to (S510).

[0131] At (S510), a detection event subscription request may be received from a VAL server at the network resource management server in SEAL. The detection event subscription request may include the identity of the VAL UE served by the VAL server, a list of detection and analysis events related to the VAL UE and of interest to the VAL server, and a timeout duration, where the subscription to the requested detection events ends after the timeout duration.

[0132] In some embodiments, in response to the received detection event subscription request, the network resource management server in SEAL may send a detection event subscription response to the VAL server. The detection event subscription response may indicate whether the subscription status is successful or rejected.

[0133] In some embodiments, the network resource management server may subscribe to a list of detection events and analysis events from a wireless network system related to the VAL UE and of interest to the VAL server. When an event in the list of detection events and analysis events occurs in the wireless network system, the network resource management server may receive a VAL UE detection event notification from the wireless network system indicating the event in the list of detection events and analysis events.

[0134] At (S520), a notification detection event message may be sent from the network resource management server in SEAL to the VAL server to notify an event that has occurred for the VAL UE indicated in the detection event subscription request. For example, the notification detection event message may include the identity of the VAL UE served by the VAL server, the event that has occurred for the VAL UE, and a timestamp of the occurrence time corresponding to the notified event. In one embodiment, the format of the timestamp of the occurrence time corresponding to the notified event is according to one of ISO 8610, RFC1123, and Coordinated Universal Time (UTC). The method (500) may proceed to (S599) and terminate at (S599).

[0135] Figure 6 A network connection status query method (600) of some embodiments of the present application is shown. The network resource management server can be configured to execute the method (600) to support the VAL server in detecting the network connection status of one or more target VAL UEs served by the VAL server. The method (600) can start from (S601) and proceed to (S610).

[0136] At (S610), a request for network connection status information can be received from the VAL server at the network resource management server in the SEAL. The request for network connection status information can indicate the target VAL UE, the type of network connection status information, and a timeout duration, where the requested network connection status information is not sent after the timeout duration.

[0137] In some embodiments, the network connection status information corresponds to a detection event related to the target UE. The VAL server is interested in the detection event. The detection event can be detected in the wireless network system based on predefined conditions. In some embodiments, the network connection status information includes one of the following: connection loss of the target VAL UE and connection bandwidth of the target VAL UE to the wireless network system.

[0138] In some embodiments, the request for network connection status information includes a subscription to the type of network connection status information. For example, the subscription indicates the frequency of providing network connection status information from the network resource management server to the VAL server.

[0139] In some embodiments, in response to the received request for network connection status information, the network resource management server in the SEAL can send a network connection status information request acceptance message to the VAL server, indicating that the request for network connection status information is authorized.

[0140] At (S620), the network connection status information of the target VAL UE can be obtained from the wireless network system through a network service open interface based on the request for network connection status information.

[0141] At (S630), the network resource management server in the SEAL can send a network connection status information response message to the VAL server. The network connection status information response message can include the network connection status information of the target VAL UE. In some embodiments, the network connection status information response message can indicate the identity of the target VAL UE and the network connection status information of the target VAL UE. In some embodiments, the network connection status information response message can further indicate a timestamp corresponding to the network connection status information of the target VAL UE. The method (600) can proceed to (S699) and terminate at (S699).

[0142] IV. Computer System

[0143] The above - mentioned technology can be implemented as computer software using computer - readable instructions and physically stored in one or more computer - readable media. The computer software can be encoded using any suitable machine code or computer language, and code can be generated by mechanisms such as assembly, compilation, linking, or the like. The code includes instructions that can be directly executed by one or more computer central processing units (CPUs), graphics processing units (GPUs), etc., or executed through operations such as code interpretation and micro - code execution.

[0144] These instructions can be executed in various types of computers or components, including, for example, personal computers, tablets, servers, smart phones, gaming devices, Internet of Things devices, etc.

[0145] Figure 7 A computer system (700) suitable for implementing certain embodiments of the disclosed subject matter is shown. Figure 7 The components shown for the computer system (700) are exemplary in nature and are not intended to impose any limitations on the scope of use or functionality of the computer software implementing the embodiments of the present application. Nor should the manner of configuring the components be construed as having any dependence on or requirement for any one component or combination of components in the exemplary embodiments of the computer system (700).

[0146] The computer system (700) may include certain human - machine interface input devices. Such human - machine interface input devices can respond to inputs from one or more human users through, for example, tactile inputs (e.g., key presses, swipes, data glove movements), audio inputs (e.g., voice, taps), visual inputs (e.g., gestures), and olfactory inputs (not shown). The human - machine interface devices can 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 sound), images (e.g., scanned images, photographic images obtained from a still - image camera), and video (e.g., two - dimensional video, three - dimensional video including stereoscopic video).

[0147] The human - machine interface input devices can include one or more of the following (only one of each is shown): keyboard (701), mouse (702), touchpad (703), touchscreen (710), data glove (not shown), joystick (705), microphone (706), scanner (707), camera (708).

[0148] The computer system (700) may also include certain human-machine interface output devices. Such human-machine interface output devices can stimulate the senses of one or more human users through, for example, tactile output, sound, light, and smell / taste. Such human-machine interface output devices may include tactile output devices (such as the tactile feedback of a touch screen (710), a data glove (not shown), or a joystick (705), but there may also be tactile feedback devices that do not serve as input devices), audio output devices (such as speakers (709), headphones (not shown)), visual output devices, and printers (not shown), where the visual output devices are, for example, a screen (710), virtual reality glasses (not shown), a holographic display, and a smoke canister (not shown), and the screen (710) includes a cathode ray tube (CRT) screen, a liquid crystal display (LCD) screen, a plasma screen, an organic light-emitting diode (OLED) screen, each with or without touch screen input capabilities, each with or without tactile feedback capabilities, and some of these screens are capable of outputting two-dimensional visual output information or more than three-dimensional output information, for example, through stereoscopic image output.

[0149] The computer system (700) may also include human-accessible storage devices and their associated media, such as optical media (including CD / DVD ROM / RW (720) with CD / DVD), or similar media (721), thumb drives (722), removable hard disk drives, or solid state drives (723), traditional magnetic media (such as tapes and floppy disks (not shown)), devices based on dedicated ROM / ASIC / PLD (such as security dongles (not shown)), etc.

[0150] Those skilled in the art should also understand that the term "computer-readable medium" used in connection with the subject matter of this application does not include a transmission medium, a carrier wave, or other transient signals.

[0151] The computer system (700) may also include an interface (754) connected to one or more communication networks (755). The network may be, for example, a wireless network, a wired network, an optical network. The network may also be a local area network, a wide area network, a metropolitan area network, a vehicle-to-everything network and an industrial network, a real-time network, a delay-tolerant network, etc. Examples of networks include local area networks (such as Ethernet, wireless LAN), cellular networks (including Global System for Mobile Communications (GSM), 3rd Generation Mobile Communication System (3G), 4th Generation Mobile Communication System (4G), 5th Generation Mobile Communication System (5G), Long Term Evolution (LTE), etc.), television cable or wireless wide area digital networks (including cable television, satellite television, and terrestrial broadcast television), vehicle-to-everything networks and industrial networks (including CANBus), etc. Some networks typically require an external network interface adapter that is connected to some general-purpose data port or peripheral bus (749) (such as the Universal Serial Bus (USB) port of the computer system (700)); other networks are typically connected to the system bus and thus integrated into the core of the computer system (700) (such as an Ethernet interface integrated into a personal computer system or a cellular network interface integrated into a smartphone computer system). By using any of these networks, the computer system (700) can communicate with other entities. Such communication may be, for example, one-way, receive-only (such as broadcast TV), one-way transmit-only (such as CANbus to certain CANbus devices), or two-way communication with other computer systems using a local area network or a wide area digital network. Certain protocols and protocol stacks may be used on each of the networks and network interfaces described above.

[0152] The above-mentioned human-machine interface device, human-accessible storage device, and network interface may be connected to the core (740) of the computer system (700).

[0153] The kernel (740) may include one or more central processing units (CPUs) (741), a graphics processing unit (GPU) (742), a dedicated programmable processing unit in the form of a field-programmable gate array (FPGA) (743), a hardware accelerator for specific tasks (744), a graphics adapter (750), etc. These devices, as well as a read-only memory (ROM) (745), a random access memory (746), an internal mass storage (747) (such as an internal non-user-accessible hard disk drive, SSD), etc., may be interconnected via a system bus (748). In some computer systems, the system bus (748) may be accessible in the form of one or more physical plugs, enabling expansion via additional CPUs, GPUs, etc. Peripheral devices may be connected directly or via a peripheral bus (749) to the system bus (748) of the kernel. In one example, a screen (710) may be connected to the graphics adapter (750). The architecture of the peripheral bus includes PCI, USB, etc.

[0154] The CPU (741), GPU (742), FPGA (743), and accelerator (744) may execute certain instructions, and the combination of these instructions may constitute the aforementioned computer code. This computer code may be stored in the ROM (745) or the RAM (746). Intermediate data may also be stored in the RAM (746), while permanent data may be stored in, for example, the internal mass storage (747). Fast storage and retrieval of any memory device may be enabled by using a cache memory, which may be closely associated with one or more CPUs (741), GPUs (742), mass storage devices (747), ROM (745), RAM (746), etc.

[0155] Computer code may be present on a computer-readable medium, and various computer-executed operations may be performed on the computer code. The medium and the computer code may be specially designed and constructed for the purposes of this application, or they may be media and code well-known and available to those skilled in the art of computer software.

[0156] By way of example and not limitation, a computer system having an architecture (700), and in particular a kernel (740), can provide functionality implemented by one or more processors (including CPUs, GPUs, FPGAs, accelerators, etc.) executing software in one or more tangible computer-readable media. Such computer-readable media can be media associated with the user-accessible mass storage as described above, and certain storage of the non-volatile kernel (740), such as the on-kernel mass storage device (747) or ROM (745). The software implementing the various embodiments of the present application can be stored in such devices and executed by the kernel (740). Depending on specific requirements, the computer-readable media can include one or more memory devices or chips. The software can cause the kernel (740), and in particular the processors therein (including CPUs, GPUs, FPGAs, etc.), to execute specific processes or specific parts of specific processes described herein, including defining data structures stored in the RAM (746), and modifying these data structures according to software-defined processes. As a supplement or as an alternative, the computer system can provide the same functionality as logic hardwired in a circuit (e.g., accelerator (744)) or other components, which can operate instead of or together with the software to execute specific processes or specific parts of specific processes described herein. In appropriate cases, references to software can include logic, and vice versa. In appropriate cases, references to computer-readable media can include circuits (e.g., integrated circuits (ICs)) storing software for execution, circuits including logic for execution, or both. The present application encompasses any suitable combination of hardware and software.

[0157] Although the present application has described multiple exemplary embodiments, various changes, permutations, and various alternatives of the embodiments are within the scope of the present application. 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 application and are thus within the spirit and scope of the present application.

Claims

1. A method for a service enabler architecture layer (SEAL), characterized in that, Including: Receiving, at a network resource management server in SEAL, a detection event subscription request for network connection status information from a vertical application layer (VAL) server, the detection event subscription request for the network connection status information indicating: A target VAL user equipment (UE), The type of the network connection status information, A timeout duration, used to indicate the amount of time elapsed after the detection event subscription request is sent, and A pull frequency, used to indicate the frequency of periodically providing the network connection status information; Obtaining, based on the detection event subscription request for the network connection status information, the network connection status information of the target VAL UE from a radio network system according to the pull frequency indicated by the detection event subscription request; Sending, from the network resource management server in the SEAL to the VAL server, a network connection status information response message, the network connection status information response message including the network connection status information of the target VAL UE; and Stopping sending the requested network connection status information after the timeout duration.

2. The method according to claim 1, characterized in that, The network connection status information corresponds to a detection event related to a target VAL UE of interest to the VAL server and is detected in the radio network system based on predefined conditions.

3. The method according to claim 1, wherein The network connection status information includes one of the following: Connection loss of the target VAL UE, and The connection bandwidth of the target VAL UE to the radio network system.

4. The method according to claim 1, characterized in that The detection event subscription request for the network connection status information includes a subscription to the type of the network connection status information.

5. The method according to claim 4, characterized in that The subscription indicates the frequency of periodically providing the network connection status information from the network resource management server to the VAL server.

6. The method according to claim 1, wherein The network connection status information response message indicates: The identifier of the target VAL UE, and The network connection status information of the target VAL UE.

7. The method according to claim 6, characterized in that, The network connection status information response message further indicates a timestamp corresponding to the network connection status information of the target VAL UE.

8. The method according to claim 1, wherein Further including: In response to the received detection event subscription request for the network connection status information, the network resource management server in the SEAL sends a network connection status information request acceptance message to the VAL server, indicating that the detection event subscription request for the network connection status information is authorized.

9. A non - volatile computer - readable medium stores instructions, characterized in that, When executed by a processor, the instructions cause the processor to execute the method according to any one of claims 1-8.

10. A device of a service enabler architecture layer (SEAL), characterized in that, Including: A receiving module, configured to receive, at a network resource management server in SEAL, a detection event subscription request for network connection status information from a vertical application layer (VAL) server, the detection event subscription request for the network connection status information indicating: Target VAL user equipment (UE), the type of the network connection status information, and the timeout duration, which is used to indicate the amount of time elapsed after the detection event subscription request is sent, and the pulling frequency, which is used to indicate the frequency of periodically providing the network connection status information; an obtaining module, configured to obtain the network connection status information of the target VAL UE from a radio network system according to the detection event subscription request for the network connection status information and at the pulling frequency indicated by the detection event subscription request; a sending module, configured to send a network connection status information response message from the network resource management server in the SEAL to the VAL server, where the network connection status information response message includes the network connection status information of the target VAL UE; and a stopping module, configured to stop the device from sending the requested network connection status information after the timeout duration.

11. A computer device, comprising a processor and a memory, wherein instructions are stored in the memory, characterized in that, When executed by the processor, the instruction causes the processor to execute the method according to any one of claims 1-8.

Images