Service enabled architecture layer (SEAL) method, device and computer equipment

Abstract

The invention provides a method, a device and computer equipment for a service enabled architecture layer (SEAL), and provides the method, the device and the computer equipment for the SEAL. A request for network connection status information (also referred to as a detection event subscription request for the network connection status information) is received at a network resource management server in the SEAL 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 indicating an amount of time elapsed after the detection event subscription request is sent. And not sending the requested network connection state information after the timeout duration. Based on the detected event subscription request for the network connection status information, the network connection status information for 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 state information response message comprises the network connection state information of the target VAL UE.

Description

Incorporation by reference

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

[0002]

[0014] Embodiments described herein generally relate to a service enablement layer for supporting vertical applications running over wireless networks. Background Art

[0003] The background description provided herein is intended to generally present the context of this application. The work of the currently named inventors described in this background section, as well as aspects of the description that may not constitute prior art at the time of filing, are not admitted, either explicitly or implicitly, to be prior art for this application.

[0004] Wireless communication systems are designed with advanced built-in capabilities to support enterprise sectors or vertical industries, such as healthcare, automotive, smart factories, and mission-critical communications. Vertical application standards are being developed to enable the rapid deployment of vertical services based on the public services provided by wireless networks. A vertical sector can be an industry or group of companies that produce similar products or services. Vertical applications can provide services or functions that are useful in a specific vertical sector. Summary of the Invention

[0005] Aspects of the present application provide a method for a service enabler architecture layer (SEAL). The method may include receiving a detection event subscription request from a vertical application layer (VAL) server at a network resource management server in the SEAL, wherein the detection event subscription request includes an identifier of a VAL user equipment (UE) served by the VAL server. Based on the detection event subscription request, a detection event notification of the VAL UE is received from a wireless network system. A notification detection event message is sent from the network resource management server in the SEAL to the VAL server, wherein the notification detection event message includes the identifier of the target VAL UE and an event that has occurred for the VAL UE.

[0006] Aspects of the present application provide a non-volatile computer-readable medium having instructions stored therein. When executed by a processor, these instructions can cause the processor to perform the above SEAL method.

[0007] Aspects of the present application provide a SEAL device. The device may include a receiving module for receiving, at a network resource management server in the SEAL, a detection event subscription request from a vertical application layer (VAL) server, the detection event subscription request including an identifier of a VAL user equipment (UE) served by the VAL server; an acquiring module for receiving, from a wireless network system, a detection event notification of the VAL UE, in response to the detection event subscription request; and a sending module for sending a detection event notification message from the network resource management server in the SEAL to the VAL server, the detection event notification message including an identifier of the target VAL UE and an event that has occurred for the VAL UE. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] Other features, properties, and various advantages of the disclosed subject matter will become more apparent from the following detailed description and accompanying drawings, in which:

[0009] Figure 1 It shows a general online functional model of an embodiment of the present application;

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

[0011] Figure 3 The event subscription and notification methods of some embodiments of the present application are shown;

[0012] Figure 4 The following describes a method for detecting a network connection state according to some embodiments of the present application.

[0013] Figure 5 The network detection method according to an embodiment of the present application is shown;

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

[0015] Figure 7 is a schematic diagram of a computer system according to an embodiment. DETAILED DESCRIPTION

[0016] I. Service enabling layer for vertical applications

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

[0018] The embodiments of the present application implement a service enabling layer for supporting vertical applications (or vertical industries (verticals)). In the present application, 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) used by multiple vertical applications to accelerate the development and deployment of vertical applications. For example, commonly needed auxiliary services may 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 a vertical application may be optional. A vertical application may decide to use any subset of SEAL services.

[0019] 2. Generic Functional Model for SEAL Services

[0020] In some embodiments, the SEAL functional model can be organized into a general SEAL service functional model and multiple specific SEAL service functional models. The general SEAL service functional model can be used as a reference model for specific SEAL service functional models. The general 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.

[0021] Figure 1A general online functional model (100) of an embodiment of the present application 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 entity may belong to the VAL (101). The SEAL client and the SEAL server entity may belong to the SEAL (102). The VAL client (111) and the SEAL client (112) may be included in the 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 follows Figure 1 shown coupled together.

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

[0023] SEAL (102) provides various services to VAL (101). One or more SEAL clients communicate with one or more SEAL servers via 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 via the SEAL-C reference point (131) (corresponding to the SEAL-C interface). One or more VAL servers communicate with one or more SEAL servers via one or more SEAL-S reference points (corresponding to the SEAL-S interface). One or more SEAL servers (122) can communicate with the underlying 3GPP network system (140) using the corresponding 3GPP interface (135) specified by the 3GPP network system.

[0024] For a specific service (eg, location management service), a specific SEAL client and a specific SEAL server as well as their specific SEAL-UU reference point and a specific network interface of the 3GPP network system may form or belong to a specific online functional model.

[0025] In some embodiments, to support distributed SEAL server deployment, the SEAL server can be connected to the server through the so-called SEAL-E reference point ( Figure 1A SEAL server can interact with another SEAL server for the same SEAL service via a so-called SEAL-X reference point ( Figure 1 The SEAL server can interact with the VAL user database to store and retrieve user profile data through the VAL-UDB reference point.

[0026] 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 between the vertical application and one or more SEAL clients (112). The VAL server (121) (e.g., a V2X application server) may provide server-side functionality corresponding to the vertical application.

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

[0028] 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.

[0029] exist Figure 1In an example, a VAL user database (not shown) may include user profile data 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.

[0030] In some embodiments, the interaction between the VAL client (111) and the VAL server (121) related to the VAL (101) support functionality is supported by the VAL-UU reference point (134). In one example, the 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 the VAL clients of two UEs related to the VAL support functionality may be supported by the VAL-PC5 reference point (not shown). For example, the reference point may be an instance of the PC5 reference point as described in 3GPP TS 23.303.

[0031] In some embodiments, the interaction between a SEAL client (112) and a 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 a specific SEAL service capability 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 a specific SEAL service capability model.

[0032] 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 to which the SEAL-C (131) corresponds may be specified in a specific SEAL service function model.

[0033] 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 function model.

[0034] In some embodiments, interactions between SEAL servers of the same type (eg, providing the same type of SEAL service) 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 function model.

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

[0036] The reference point VAL-UDB exists between the VAL user database and the SEAL server. The reference point VAL-USB may 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.

[0037] 3. Logo

[0038] In various embodiments, different identities 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 identity (user ID) to an identity management server in SEAL (102) during the user authentication process to provide a means for the identity management client to authenticate to the VAL service. Typically, because identity management is a conventional SEAL service, the identity management server uses a set of credentials (e.g., biometric information, secureID, username / password) that may not be bound to a single VAL service. The user credentials uniquely identify the VAL user to the identity management server. As an example, the specific security and authentication mechanisms required for using user IDs are specified in 3GPP TS 33.434.

[0039] In some embodiments, the VAL user ID is a unique identifier within the VAL service, used to identify a 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 via the VAL UE. The VAL user ID also indicates the VAL service provider with which the VAL user has a VAL service agreement. The VAL user may have a VAL service agreement with the VAL service provider and therefore has obtained a unique VAL user ID that corresponds one-to-one with the VAL service provider. The VAL user ID can be used to access the SEAL service.

[0040] 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 TS102 894-2. The VAL UE ID is used to address the VAL UE to send VAL messages.

[0041] In some embodiments, the VAL service ID is a unique identifier representing a 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 a VAL service ID, which identifies the VAL application that provides the VAL service. The VAL service ID can be used for policy mapping, QoS processing for VAL communications, and VAL message distribution. For example, the identifier of a 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.

[0042] In some embodiments, a VAL group ID is a unique identifier within a VAL service that represents a group of VAL users or a group of VAL UEs according to the VAL service. The 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.

[0043] 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.

[0044] 4. Application of functional models in deployment

[0045] In various embodiments, the SEAL architecture described above can support deployment of SEAL services within and / or outside of a public land mobile network (PLMN). The SEAL architecture can also support centralized and distributed deployment of vertical applications. Mobile network operators (MNOs) can adopt a suitable deployment model that suits their business needs.

[0046] The deployment model may involve multiple entities, such as a VAL user, a VAL service provider, a SEAL provider, and a PLMN operator. For example, in one 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. A SEAL server may also interact with another SEAL server deployed in a different PLMN operator domain that provides the same SEAL service, using the SEAL-E interface.

[0047] Multiple business relationships may exist between the various entities involved in a deployment. Based on service-specific agreements, VAL users belong 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, SEAL service provider, and home PLMN operator may also belong to the same organization. If the VAL service provider and home PLMN operator do not belong to the same organization, they may have a service agreement.

[0048] 5. SEAL-based V2X vertical applications

[0049] 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. Typically, a SEAL client does not proactively initiate a process. In order for the SEAL client to initiate a process, the V2X vertical application needs to provide the SEAL client with trigger information and parameters related to the process.

[0050] For example, 3GPP TS 23.286 defines the V2X application-level functional model. As defined, the V2X application enabler (VAE) layer provides VAE functionality to the V2X application-specific layer. The VAE layer utilizes SEAL services. A VAE client can act as a VAL client, interacting with a SEAL client in accordance with the SEAL architecture. A VAE server can act as a VAL server, interacting with a SEAL server in accordance with the SEAL architecture.

[0051] The V2X application layer can provide group joining policies and group leaders for 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. Before a V2X UE begins receiving V2X services from the V2X application layer, the VAE client and VAE server can use the SEAL configuration management service to provide configuration information to the V2X UE. Once the V2X UE has already received V2X services from the V2X application layer, the VAE client and VAE server can also use the SEAL configuration management service to provide configuration updates to the V2X UE.

[0052] The VAE client and 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 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 VAE server can use the SEAL network resource management service to establish and modify bearers and switch between different types of bearers.

[0053] The VAE server can also use the SEAL API to utilize SEAL services to enable various V2X application features or services. For example, to create a V2X application group, the VAE server can call the Create service operation of the Group Management API over the GM-S reference point. The Group Management Server can then create a Group Document and notify the VAE server of the newly created group information.

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

[0055] II. Network Resource Management Services

[0056] 1. Functional model of network resource management

[0057] Figure 2 The functional model (200) of the network resource management SEAL service of some embodiments of the present application is shown. The functional model (200) can be based on Figure 1The general functional model (100) shown in FIG. The functional 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 functional model (200) may further include a 3GPP network system (240).

[0058] In some embodiments, the network resource management client (212) communicates with the network resource management server (222) via 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) via a reference point (231) represented by NRM-C. The VAL server (221) communicates with the network resource management server (222) via a reference point (232) represented by NRM-S. The VAL client (211) communicates with the VAL server (221) via a reference point (234) represented by VAL-UU. The VAL UE (210) can communicate with the 3GPP network system (240) via a UU interface (not shown) specified in the 3GPP standard, for example.

[0059] In some embodiments, the network resource management server (222) can 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) can 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).

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

[0061] In some embodiments, there may be multiple VAL clients and multiple VAL servers in the VAL UE 210. These functional entities may 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 other than the 3GPP network system (240) may be used in the VAL system that implements the functional model (200). For example, instead of the 3GPP network system (240), these various types of network systems may provide a wireless connection to the VAL UE for communicating with the VAL server or the network resource management server (222), or open up the service capabilities of the above SEAL (202) and VAL (201).

[0062] and Figure 2 In contrast to the online model (200) shown in FIG, the offline functional model of the network resource management SEAL service may include a first UE and a second UE. The two UEs may communicate via a PC5 reference point or a PC5 interface. For example, each UE may include one or more VAL clients in a VAL. The VAL clients of the first UE and the second UE may communicate via a 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 may communicate via an NRM-PC5 reference point.

[0063] 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 (e.g., unicast, multicast) and detection event notification to support VAL applications. The network resource management server (222) also supports interaction with corresponding network resource management servers in a distributed SEAL deployment. In one embodiment, the role of the network resource management server is assumed by the VAL server in the deployment mode. In this case, the VAL server performs the network resource management process instead of the network resource management server.

[0064] In some embodiments, interactions related to network resource management functions between a network resource management client (212) and a network resource management server (222) are supported by the NRM-UU reference point. This reference point utilizes the Uu reference point as described in 3GPP TS 23.401 and 3GPP TS 23.501. In some embodiments, interactions related to network resource management functions between network resource management clients in different VAL UEs are supported by the NRM-PC5 reference point. This reference point utilizes the PC5 reference point as described in 3GPP TS 23.303.

[0065] In some embodiments, interactions between the VAL server (221) and the network resource management server (222) related to network resource management functions are supported by the NRM-S reference point. This reference point may be an example of the CAPIF-2 reference point as specified in 3GPP TS 23.222. In some embodiments, interactions between network resource management servers in a distributed deployment related to network resource management functions are supported by the NRM-E reference point.

[0066] In some embodiments, the reference point MB2-C supports control plane interactions 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 control plane interactions between the network resource management server (222) and the BM-SC and is specified by 3GPP TS 26.348. In some embodiments, the reference point Rx supports interactions between the network resource management server (222) and the PCRF and is specified by 3GPP TS 29.214.

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

[0068] 2. Example Network Connection Status Detection Process

[0069] 2.1 Event Detection

[0070] In some embodiments, an event detection solution is utilized to provide a network connection status detection service as part of a network resource management (SEAL) service. For example, a VAL server can utilize a network resource management server to detect events related to a VAL UE served by the VAL server. Based on the VAL server's detection event subscription request, the network resource management server can subscribe to multiple core network services of the underlying wireless network system to obtain desired events related to multiple VAL UEs served by the VAL server. The network resource management server can then report the acquired events to the VAL server.

[0071] In some embodiments, to detect and report detection events related to VAL UEs from the 3GPP core network, the network resource management server may use the detection event procedure specified in 3GPP TS 23.502. To detect and report analysis events related to VAL UEs, the network resource management server may use, for example, the relevant procedures specified in 3GPP TS 23.288.

[0072] Figure 3 An event subscription and notification method (300) of some embodiments of the present application is shown. The method (300) can be performed between a 5G core network (301), a network resource management server (302), and a VAL server (303). During the method (300), the VAL server (303) subscribes to the services 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).

[0073] 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.

[0074] 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, a list of detection events and / or analysis events is provided for each of the listed VAL users or VAL UEs. In one embodiment, a common list of detection events and / or analysis events is provided for the listed VAL users or VAL UEs. (3) A timeout period for sending a 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 from the network resource management server (302) at the VAL server (303) within the timeout period 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 period is used to define a period of time after which the requested detection event subscription ends.

[0075] In some embodiments, the detection event subscription request may include the information listed in Table 1 below. Table 1 In Table 1, "M" indicates "Mandatory" and "O" indicates "Optional".

[0076] At (S320), the network resource management server (302) may check whether the VAL server (303) is authorized to initiate the 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 is rejected.

[0077] In some embodiments, the detection event subscription response may include the information listed in Table 2 below. Table 2 Information Elements state describe Subscription Status M Indicates the result of the subscription.

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

[0079] Examples of detection events may include connection loss, UE reachability, location reporting, roaming status, communication failure, 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.

[0080] In some embodiments, the network resource management server (302) performs subscription of UE detection events based on the process specified in 3GPP TS23.502. For example, a network open function can be used to support the external opening of network functional capabilities. External opening can be classified into detection capabilities, provisioning capabilities, policy / billing capabilities, network status reporting capabilities, and analysis reporting capabilities. Detection capabilities are used to detect specific events of UEs in the 5G system and make such detection event information available for external opening through NEF. For example, a method for configuring specific events, event detection, and reporting events to the requested party is provided. A list of detection events and related detection criteria is specified in 3GPP 23.502.

[0081] In some embodiments, the network resource management server (302) performs subscription of UE analysis events. The subscription can be performed based on the process specified in 3GPP TS 23.288. For example, one or more network data analytics functions (NWDAFs) can be used to support data collection based on subscriptions to events provided by data consumers (e.g., the network resource management server (302)). The analysis information can be statistical information or predictive information of past events.

[0082] Using 5G core network (301) as Figure 3 By way of 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 relevant events.

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

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

[0085] 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 associated VAL UEs. Each entry in the list may include (i) the VAL UE associated with the event, and (ii) a list of detection events and / or analysis events associated with the corresponding VAL UE. (2) Optionally, a timestamp corresponding to each of the listed detection events and analysis events.

[0086] In some embodiments, the timestamp in the notification detection event message can be in one of several different time formats, such as ISO 8610 (e.g., yyyy-month-day THH:MM:SS), RFC 1123 (e.g., Monday, DD MonYYYY HH:MM:SS time zone), Coordinated Universal Time (UTC: yyyy-mn-dd THH:MM:SS), etc.

[0087] In some embodiments, the notification detection event message may include the information listed in Table 3 below. Table 3 The method (300) may terminate after (S350).

[0088] In some embodiments, an application programming interface (API) is used in a method (300) for detecting event subscription and notification. The API is referred to as an event detection API. In one example, the event detection API defines two API operations: a subscribe-detection-event API operation for subscribing to a detection event, and a notify-detection-event API operation for notifying a VAL server of a detection event associated with one or more VAL UEs.

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

[0090] In another example, the VAL server (303) may be a user of the Notify-Detect-Event API operation. Corresponding to (S350) of the method (300), the information elements in the Notify-Detect-Event message may be used as input to the Notify-Detect-Event API operation.

[0091] 2.2 Network connection status detection

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

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

[0094] In the network connection status detection method (400), the VAL server (403) may send a request for network connection status information of a 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 at (S410).

[0095] At (S410), a network connection status information request message may 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 request to subscribe to a detection event for network connection status information) may indicate one or more target VAL UEs whose network connection status information is requested. For example, an identifier of a VAL UE or a VAL user defined at the VAL may be used to identify the target UE.

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

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

[0098] In one example, the network connection status information may be event-based. The event may be related to a bandwidth and / or connection test event. In one embodiment, the event may be time-based, such as in response to a subscribed query or frequency. In some embodiments, the request may indicate a condition, and when the condition is triggered, the corresponding network connection status is reported. For example, the condition may 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 may be referred to as events. For example, a set of network connection status events and related triggering or detection conditions may be predefined. Such a list of predefined events may be included in the network connection status information request and provided from the VAL server (403) to the network resource management server (402).

[0099] In some embodiments, the network connection status information request may indicate the identity of one or more entities. The one or more entities may include a VAL server (e.g., Figure 4 In one embodiment, the one or more entities may include an entity that performs a request. In one embodiment, the one or more entities may include a VAL user or a VAL UE for which detection (e.g., event detection) is requested.

[0100] 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 a specific vertical application. In some examples, information about the service requesting the network connection status information may help address the target service at the VAL server (403).

[0101] In some embodiments, the network connection status information request may further indicate a timeout period. The timeout period may be used to send a response from the network resource management server (402) to the VAL server (403). In one example, when the VAL server (403) does not receive a network connection status information request acceptance message from the network resource management server (402) within the timeout period calculated from the time the network connection status information request is sent, the VAL server (403) may consider that the request has failed or been rejected. In one example, the timeout period specifies a period after which the sending 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).

[0102] In one embodiment, the network connection status information request may include one or more of the following information elements in Table 4. Table 4 In one embodiment, if the information element of "requested VAL services" in Table 4 does not exist, the network connection status may be requested for all existing running VAL services on the client side.

[0103] 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 authorization to request the corresponding network connection status. In one example, the authorization may be authorization specifically for different types of network connection status.

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

[0105] At (S450), a network connection status information response message may 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 may be indicated in the network connection status information response, such as a list of VAL UE identifiers. The listed VAL UEs may be a complete set or a subset of the target VAL UEs indicated in the network connection status information request (S410). Network connection status information may be provided for each listed VAL UE.

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

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

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

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

[0110] III. Exemplary Network Detection Process

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

[0112] At (S510), a detection event subscription request may be received from a VAL server at a network resource management server in SEAL. The detection event subscription request may include an identifier of a 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 period after which subscription to the requested detection event is terminated.

[0113] In some embodiments, in response to the received detection event subscription request, the network resource management server in the 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.

[0114] In some embodiments, the network resource management server may subscribe to a list of detection events and analysis events from the wireless network system that are related to the VAL UE and that the VAL server is interested in. 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.

[0115] At (S520), a notification detection event message may be sent from the network resource management server in the SEAL to the VAL server to notify the VAL UE indicated in the detection event subscription request that an event has occurred. For example, the notification detection event message may include an identifier of the VAL UE served by the VAL server, an 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 one of ISO 8610, RFC 1123, and Coordinated Universal Time (UTC). The method (500) may proceed to (S599) and terminate at (S599).

[0116] Figure 6 The network connection status query method (600) of some embodiments of the present application is shown. The network resource management server can be configured to perform the method (600) to support the VAL server to detect 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).

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

[0118] In some embodiments, the network connection status information corresponds to a detection event associated with 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: a connection loss of the target VAL UE and a connection bandwidth of the target VAL UE to the wireless network system.

[0119] In some embodiments, the request for network connection status information includes a subscription to the type of network connection status information, such as indicating the frequency of providing network connection status information from the network resource management server to the VAL server.

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

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

[0122] At (S630), the network resource management server in the SEAL may send a network connection status information response message to the VAL server. The network connection status information response message may include the network connection status information of the target VAL UE. In some embodiments, the network connection status information response message may indicate the identifier 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 may further indicate a timestamp corresponding to the network connection status information of the target VAL UE. The method (600) may proceed to (S699) and terminate at (S699).

[0123] IV. Computer Systems

[0124] The above-described techniques can be implemented as computer software using computer-readable instructions and physically stored on one or more computer-readable media. Computer software can be encoded using any suitable machine code or computer language, and code can be generated using assembly, compilation, linking, or similar mechanisms. The code includes instructions that can be executed directly by one or more computer central processing units (CPUs), graphics processing units (GPUs), etc., or through operations such as code interpretation and microcode execution.

[0125] These instructions can be executed in various types of computers or components, including, for example, personal computers, tablets, servers, smartphones, gaming devices, IoT devices, etc.

[0126] Figure 7 A computer system (700) suitable for implementing certain embodiments of the disclosed subject matter is shown. Figure 7 The components shown for computer system (700) are exemplary in nature and are not intended to limit the scope of use or functionality of computer software implementing embodiments of the present application. The configuration of components should not be interpreted as creating any dependency or requirement on any one component or combination of components in the exemplary embodiment of computer system (700).

[0127] The computer system (700) may include certain human interface input devices. Such human interface input devices may be responsive to input from one or more human users, for example, through tactile input (e.g., keystrokes, swipes, data glove movements), audio input (e.g., voice, taps), visual input (e.g., gestures), or olfactory input (not shown). The human interface devices may also be used to capture certain media that are not necessarily directly associated with conscious human input, such as audio (e.g., voice, music, ambient sounds), images (e.g., scanned images, photographic images obtained from a still camera), and video (e.g., two-dimensional video, three-dimensional video including stereoscopic video).

[0128] The human-machine interface input device may include one or more of the following (only one of each is shown): keyboard (701), mouse (702), touchpad (703), touch screen (710), data gloves (not shown), joystick (705), microphone (706), scanner (707), camera (708).

[0129] The computer system (700) may also include certain human-computer interface output devices. Such human-computer interface output devices can 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 (710), a data glove (not shown), or a joystick (705), but there may also be tactile feedback devices that are not used as input devices), audio output devices (e.g., speakers (709), headphones (not shown)), visual output devices, and printers (not shown), wherein visual output devices include screens (710), virtual reality glasses (not shown), holographic displays, and smoke canisters (not shown), and screens (710) include cathode ray tube (CRT) screens, liquid crystal display (LCD) screens, plasma screens, and organic light emitting diode (OLED) screens, 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, such as stereoscopic image output.

[0130] 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 drives or solid-state drives (723), traditional magnetic media (such as magnetic tapes and floppy disks (not shown)), dedicated ROM / ASIC / PLD based devices (such as security dongles (not shown)), etc.

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

[0132] The computer system (700) may further include an interface (754) for connecting to one or more communication networks (755). The network may be, for example, a wireless network, a wired network, or an optical network. The network may also be a local area network, a wide area network, a metropolitan area network, an Internet of Vehicles (IoV) and an industrial network, a real-time network, a delay-tolerant network, etc. Examples of networks include local area networks (e.g., Ethernet, wireless LAN), cellular networks (including Global System for Mobile Communications (GSM), third generation mobile communication systems (3G), fourth generation mobile communication systems (4G), fifth generation mobile communication systems (5G), long term evolution (LTE), etc.), television wired or wireless wide area digital networks (including cable television, satellite television, and terrestrial broadcast television), Internet of Vehicles (IoV) and industrial networks (including CANBus), etc. Some networks typically require an external network interface adapter that is connected to some universal data port or peripheral bus (749) (e.g., a universal serial bus (USB) port of the computer system (700)); other networks are typically integrated into the core of the computer system (700) by connecting to the system bus (e.g., 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 communications can be one-way, receive-only (e.g., broadcast TV), one-way send-only (e.g., CANbus to certain CANbus devices), or two-way communications, such as with other computer systems using a local area network or a wide area digital network. Certain protocols and protocol stacks can be used on each of those networks and network interfaces as described above.

[0133] The aforementioned human interface devices, human-accessible storage devices, and network interfaces may be connected to the kernel (740) of the computer system (700).

[0134] The core (740) may include one or more central processing units (CPUs) (741), graphics processing units (GPUs) (742), specialized programmable processing units in the form of field programmable gate arrays (FPGAs) (743), hardware accelerators (744) for specific tasks, a graphics adapter (750), and the like. These devices, as well as read-only memory (ROM) (745), random access memory (746), internal mass storage (747) (e.g., internal non-user accessible hard drives, SSDs), and the like, 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, allowing expansion with additional CPUs, GPUs, and the like. Peripheral devices may be connected to the core's system bus (748) directly or via a peripheral bus (749). In one example, a screen (710) may be connected to a graphics adapter (750). Peripheral bus architectures include PCI, USB, and the like.

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

[0136] The computer-readable medium may have computer code thereon, and various computer-implemented operations may be performed on the computer code. The medium and computer code may be specially designed and constructed for the purposes of this application, or may be medium and code well known and available to those skilled in the computer software field.

[0137] As an example and not limitation, a computer system having architecture (700), and in particular the 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 user-accessible mass storage as described above, as well as certain storage of the kernel (740) that is non-volatile, such as a kernel internal mass storage device (747) or ROM (745). Software implementing various embodiments of the present application can be stored in such devices and executed by the kernel (740). Depending on specific needs, the computer-readable medium may include one or more memory devices or chips. The software can enable the kernel (740), in particular 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 (746) and modifying these data structures according to software-defined processes. In addition or in lieu thereof, a computer system may provide the same functionality as logic hardwired into circuitry (e.g., accelerator (744)) or other components that may operate in place of or in conjunction with software to perform a particular process or a particular portion of a particular process described herein. Where appropriate, references to software may include logic and vice versa. Where appropriate, references to computer-readable media may include circuitry (e.g., an integrated circuit (IC)) storing the executing software, circuitry including the executing logic, or both. The present application includes any suitable combination of hardware and software.

[0138] Although this application has described a number of exemplary embodiments, various modifications, permutations, and substitutions of the embodiments are within the scope of this application. Therefore, it should be understood that those skilled in the art will be able to devise many systems and methods that, although not explicitly shown or described herein, embody the principles of this application and are therefore within the spirit and scope of this application.

Claims

1. A method for a service enabler architecture layer (SEAL), characterized in that: include: A network resource management server in the SEAL receives a detection event subscription request from a vertical application layer (VAL) server, wherein the detection event subscription request includes an identifier of a VAL user equipment (UE) served by the VAL server; receiving, based on the detection event subscription request, a detection event notification of the VAL UE from a wireless network system; and A notification detection event message is sent from the network resource management server in the SEAL to the VAL server, where the notification detection event message includes an identifier of the target VAL UE and an event that has occurred for the VAL UE.

2. The method according to claim 1, characterized in that The detection event subscription request further includes: a list of events related to the VALUE and of interest to the VAL server; The method further comprises: The network resource management server subscribes to the wireless network system for events in the event list related to the VAL UE; The network resource management server receives a detection event notification of the VAL UE from the wireless network system, where the detection event notification indicates an event in the event list.

3. The method according to claim 1, characterized in that The detection event subscription request further includes a timeout period; The method further comprises: The subscription corresponding to the detection event subscription request is terminated after the timeout period.

4. The method according to claim 1, wherein The notification detection event message includes a list of at least two events that have occurred for the VALUE.

5. The method according to claim 1 or 4, characterized in that The notification detection event message further includes a timestamp of the occurrence time of the event that has occurred for the VAL UE.

6. The method according to claim 1, 2 or 4, characterized in that The event includes at least one of the following: Connection loss, UE reachability, location reporting, roaming status, communication failures, number of UEs present in a geographical area, UE mobility analysis, UE communication analysis, expected UE behavior parameters, abnormal behavior.

7. The method according to claim 1, characterized in that Further including: The network resource management server sends a detection event subscription response to the VAL server, where the detection event subscription response indicates whether the subscription status is successful or rejected.

8. The method according to claim 7, characterized in that Further including: The network resource management server checks whether the VAL server is authorized to initiate a detection event subscription request; The network resource management server sending a detection event subscription response to the VAL server includes: In response to the VAL server being authorized to initiate a detection event subscription request, the network resource management server sends a detection event subscription response message indicating a successful subscription status; In response to the VAL server not being authorized to initiate the detection event subscription request, the network resource management server sends a detection event subscription response message indicating that the subscription request is rejected.

9. A non-volatile computer-readable medium storing instructions, characterized in that: When the instructions are executed by a processor, the processor is caused to perform the method according to any one of claims 1 to 8.

10. A device for a service enabler architecture layer (SEAL), characterized in that: include: A receiving module, configured to receive, at a network resource management server in the SEAL, a detection event subscription request from a vertical application layer (VAL) server, the detection event subscription request including an identifier of a VAL user equipment (UE) served by the VAL server; an acquisition module, configured to receive a detection event notification of the VAL UE from a wireless network system, for the detection event subscription request; and A sending module is configured to send a notification detection event message from the network resource management server in the SEAL to the VAL server, wherein the notification detection event message includes an identifier of the target VAL UE and an event that has occurred for the VAL UE.

11. A computer device comprising a processor and a memory, wherein the memory stores instructions, characterized in that: When the instructions are executed by the processor, the processor is caused to perform the method according to any one of claims 1 to 8.

Images