Perception service method and system, perception function network element, core network and storage medium

Abstract

The present disclosure relates to a sensing service method and system, a sensing function network element, a core network and a storage medium. The method comprises: a sensing function network element receiving a sensing data subscription request sent by an application function server, wherein the sensing data subscription request comprises subscription scene information; the sensing function network element allocating a dedicated scene identifier for the subscription scene information; the sensing function network element determining a sensing capability base station existing in the sensing scene; and the sensing function network element performing a related sensing request operation for the sensing capability base station. The present disclosure can provide a service of subscription pushing of a sensing function network element SF leading related sensing business and sensing service based on a terminal-free and base station sensing capability.

Description

Technical Field

[0001] This disclosure relates to the field of wireless communication, and in particular to a sensing service method and system, a sensing function network element, a core network, and a storage medium. Background Technology

[0002] In the research and standardization of network sensing capabilities, sensing services based on terminalless sensing, i.e., sensing services based on base station sensing capabilities, are a relatively special type of service because no terminal is involved in this type of sensing service. Summary of the Invention

[0003] The inventors discovered through research that while base stations possess the capability to provide sensing services, they cannot, like terminals, open up their configuration information to third-party AF (Application Function) servers. Furthermore, third-party AF servers cannot, like terminals, request a direct connection with the base station by reporting their IDs. Therefore, how to enable the base station to execute sensing requests from third-party sensing service-related application function servers (AF servers) and transmit the data back to the AF server is a challenge in existing research.

[0004] In view of at least one of the above technical problems, this disclosure provides a sensing service method and system, a sensing function network element, a core network and a storage medium, which can provide a subscription and push service for related sensing services and sensing services based on terminalless and base station sensing capabilities, led by the SF (Sensing Function).

[0005] According to one aspect of this disclosure, a sensing service method is provided, comprising:

[0006] The sensing function network element receives a sensing data subscription request sent by the application function server, wherein the sensing data subscription request includes subscription scenario information;

[0007] The sensing function network element assigns a unique scene identifier to the subscribed scene information;

[0008] The sensing function network element determines the sensing capability base stations present in the sensing scenario.

[0009] The sensing function network element performs relevant sensing request operations for the sensing capability base station.

[0010] In some embodiments of this disclosure, the sensing function network element receiving a sensing data subscription request sent by the application function server includes:

[0011] The sensing function network element receives a subscription configuration file sent by the policy control function network element. The subscription configuration file is generated by the policy control function network element based on the subscription request data. The subscription request data is included in the sensing data subscription request sent by the application function server to the policy control function network element through the network open function network element. The subscription request data also includes at least one of the identification information of the application function server and the sensing data type to be subscribed to.

[0012] The sensing function network element receives a registry update request sent by the policy control function network element, wherein the registry update request includes the subscription request data.

[0013] In some embodiments of this disclosure, the sensing function network element assigns a unique scene identifier to the subscribed scene information, including:

[0014] The sensing function network element updates the first subscription registry according to the subscription request data, wherein the first subscription registry is the subscription registry on the sensing function network element side; the first subscription registry includes at least one of the following: the identification information of the application function server, the subscription requirements of the application function server, the recorded base station information with sensing capabilities, and the data types that can be sensed and acquired, wherein the subscription requirements include at least one of the following: subscription scenario information, the binding relationship between scenario identifier and base station identifier, the sensing data type to be subscribed to, the data volume, and the data timeliness.

[0015] In some embodiments of this disclosure, the sensing function network element updating the first subscription registry based on the subscription request data includes:

[0016] Compare the subscription request data with the recorded location information and sensing data type of the sensing-capable base station;

[0017] Create a separate scene identifier for each subscribed scene;

[0018] Bind or update the corresponding base station identifier with sensing capability for each scene identifier, and generate the binding relationship between scene identifier and base station identifier;

[0019] Generate the binding relationship between the scene identifier and the identifier of the sensing function network element.

[0020] In some embodiments of this disclosure, the sensing service method further includes:

[0021] The sensing function network element reports the relevant information of the scene identifier to the policy management function network element for updating the second subscription registry. The relevant information of the scene identifier includes the binding relationship between the scene identifier and the base station identifier, and the binding relationship between the scene identifier and the identifier of the sensing function network element. The second subscription registry is the subscription registry on the policy management function network element side. The first subscription registry includes the identification information of the application function server, the subscription scene information, and the sensing function network elements covered by the subscription scene.

[0022] In some embodiments of this disclosure, the perception service method further includes: after the perception function network element reports the relevant information of the scene identifier to the policy management function network element, it sends a push configuration file request to the policy management function network element;

[0023] The sensing function network element receives a push configuration file issued by the policy management function network element. The push configuration file includes at least one of the following: push time node or time period and push range. In response to the push configuration file request, the policy management function network element issues an updated push configuration file to the sensing function network element and the network open function network element.

[0024] In some embodiments of this disclosure, the sensing service method further includes: the sensing function network element determining whether the data already stored in the sensing function network element includes the sensing data required by the application function server;

[0025] If the data already stored in the sensing function network element includes the sensing data required by the application function server, the sensing data will be pushed to the application function server.

[0026] If the data already stored in the sensing function network element does not include the sensing data required by the application function server, the sensing function network element is triggered to perform the operation of sending a sensing request to the base station for the first time, requesting the base station to obtain the sensing data related to the requirement.

[0027] In some embodiments of this disclosure, the sensing function network element performs a sensing request operation for the sensing capability base station, including:

[0028] The sensing function network element periodically sends sensing requests to the base station according to the requirements in the subscription configuration file, requesting the base station to obtain sensing data related to the requirements;

[0029] After collecting and processing the sensing data, the sensing network element pushes the sensing data to the application function server.

[0030] In some embodiments of this disclosure, pushing the sensed data to the application function server includes:

[0031] The sensing function network element pushes the sensing data to the network open function network element, so that when the network open function network element receives the push configuration file sent by the policy management function network element and the sensing data initiated by the sensing function network element, it pushes the sensing data to the application function server.

[0032] In some embodiments of this disclosure, the sensing function network element periodically sends sensing requests to the base station according to the requirements in the subscription configuration file, requesting the base station to obtain sensing data related to the requirements, including:

[0033] The sensing function network element generates a sensing service trigger table based on the requirements for data timeliness and the time nodes of sensing services in the subscription configuration file. The sensing service trigger table includes the identification information of the application function server and the data collection time nodes or time periods required by the application function server.

[0034] The sensing function network element determines the identification information of the application function server corresponding to a fixed time node or according to a predetermined time period based on the sensing service trigger table, determines the scene identifier based on the identification information of the application function server, and determines the corresponding base station identifier based on the scene identifier.

[0035] The sensing network element sends a sensing request to the base station corresponding to the scenario, requesting the base station to perform sensing operations and obtain sensing data.

[0036] In some embodiments of this disclosure, the sensing function network element collects and processes the sensing data in the following ways:

[0037] After receiving the sensing data reported by the base station, the sensing function network element performs relevant processing on the sensing data, wherein the relevant processing includes at least one of integrity check, sensitive information check, data quality check, data filtering and data compression.

[0038] According to another aspect of this disclosure, a sensing function network element is provided, comprising:

[0039] The request receiving module is configured to receive a sensing data subscription request sent by the application function server from the sensing function network element, wherein the sensing data subscription request includes subscription scenario information;

[0040] The scene identifier allocation module is configured to allocate a unique scene identifier to the subscribed scene information;

[0041] The sensing base station determination module is configured to determine the sensing base stations with sensing capabilities present in the sensing scenario;

[0042] The perception request module is configured to perform relevant perception request operations for the perception capability base station.

[0043] According to another aspect of this disclosure, a sensing function network element is provided, comprising:

[0044] The memory is configured to store instructions;

[0045] The processor is configured to execute the instructions, causing the sensing function network element to perform operations that implement the sensing service method as described in any of the above embodiments.

[0046] According to another aspect of this disclosure, a core network device is provided, including a sensing function network element as described in any of the above embodiments.

[0047] In some embodiments of this disclosure, the core network device further includes:

[0048] The policy control function network element is configured to receive a perception data subscription request sent by the application function server through the network open function network element. The perception data subscription request includes subscription request data, which includes at least one of the following: subscription scenario information, identification information of the application function server, and the type of perception data to be subscribed to. The configuration element generates a subscription configuration file based on the subscription request data. It then determines the perception function network element corresponding to the subscription scenario information based on the correspondence between the scenario information and the perception function network elements. Finally, it sends the subscription request data and the subscription configuration file to the perception function network element corresponding to the subscription scenario information.

[0049] In some embodiments of this disclosure, the core network device further includes:

[0050] The network open function element is configured to push the perception data packet to the corresponding application function server according to the actual requirements of the push configuration file after receiving the push configuration file issued by the policy control function element and the perception data packet sent by the perception function element.

[0051] According to another aspect of this disclosure, a sensing service system is provided, including a core network device as described in any of the above embodiments.

[0052] In some embodiments of this disclosure, the perception service system further includes:

[0053] An application function server is configured to send a sensing data subscription request to a core network device. The sensing data subscription request includes subscription request data, which includes at least one of the following: subscription scenario information, identification information of the application function server, and sensing data type to be subscribed. The scenario is a geographical or spatial range that needs to perform sensing operations based on one or more base stations.

[0054] In some embodiments of this disclosure, the perception service system further includes:

[0055] The sensing-capable base station is configured to perform a sensing operation upon receiving a sensing request from a sensing function network element in the core network equipment, and then upload the received sensing data to the sensing function network element.

[0056] According to another aspect of this disclosure, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores computer instructions that, when executed by a processor, implement the perception service method as described in any of the above embodiments.

[0057] This disclosure can provide a subscription and push service for related sensing services and sensing services based on terminalless and base station sensing capabilities, with the sensing function network element SF leading the relevant sensing services. Attached Figure Description

[0058] To more clearly illustrate the technical solutions in the embodiments of this disclosure or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this disclosure. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0059] Figure 1 This is a schematic diagram of some embodiments of the sensing service method disclosed herein.

[0060] Figure 2 These are schematic diagrams illustrating the design of scenarios and base stations in some embodiments of this disclosure.

[0061] Figure 3 The diagram illustrates some other embodiments of the sensing service method disclosed herein.

[0062] Figure 4 This is a schematic diagram of some embodiments of the sensing function network element of this disclosure.

[0063] Figure 5 This is a schematic diagram of the structure of some other embodiments of the sensing function network element of this disclosure.

[0064] Figure 6 This is a schematic diagram of some embodiments of the core network equipment disclosed herein. Detailed Implementation

[0065] The technical solutions of the embodiments of this disclosure will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this disclosure, and not all embodiments. The following description of at least one exemplary embodiment is merely illustrative and is in no way intended to limit this disclosure or its application or use. All other embodiments obtained by those skilled in the art based on the embodiments of this disclosure without creative effort are within the scope of protection of this disclosure.

[0066] Unless otherwise specifically stated, the relative arrangement, numerical expressions, and values ​​of the components and steps set forth in these embodiments do not limit the scope of this disclosure.

[0067] At the same time, it should be understood that, for ease of description, the dimensions of the various parts shown in the accompanying drawings are not drawn according to actual scale.

[0068] Techniques, methods, and equipment known to those skilled in the art may not be discussed in detail, but where appropriate, such techniques, methods, and equipment should be considered part of the specification.

[0069] In all examples shown and discussed herein, any specific values ​​should be interpreted as merely exemplary and not as limitations. Therefore, other examples of exemplary embodiments may have different values.

[0070] It should be noted that similar labels and letters in the following figures indicate similar items; therefore, once an item is defined in one figure, it does not need to be discussed further in subsequent figures.

[0071] Through research, the inventors discovered that in the research of network sensing capabilities and related technologies and services, in addition to traditional sensing services based on sensing terminals, there is a new type of terminalless sensing service based on base station sensing capabilities. Under this service, precisely because there is no terminal participation, the core network design for this type of service is completely different. Although the base station, as the main body performing sensing operations, is similar to the terminal, considering that the base station's positioning and design basis are completely different from the terminal's for the network itself, its access and management on the network side cannot directly adopt the specifications designed for terminals.

[0072] Meanwhile, many services in related technologies rely on the network side establishing connections and sessions with the terminal or application function (AF) with the terminal before the network side performs related access management and data transmission services. Without terminal participation, the network side does not disclose detailed base station information to third-party AFs, and third-party AFs cannot directly establish sessions with the base station to transmit data. Therefore, how to enable the base station to execute sensing requests sent by third-party sensing service-related application functions (AFs) and transmit the data back to the AFs is a challenge in existing research.

[0073] In addition, due to the extremely large amount of data and numerous third-party application functions (AFs) in related technology sensing services, besides data compression and processing being existing research challenges, how to reasonably arrange and provide different types of sensing services for third-party AFs to avoid excessive network load in short periods is also a challenge in sensing service design.

[0074] In view of at least one of the above technical problems, this disclosure provides a sensing service method and system, a sensing function network element, a core network, and a storage medium. The present disclosure will be described below through specific embodiments.

[0075] Figure 1 These are schematic diagrams illustrating some embodiments of the sensing service method of this disclosure. Preferably, this embodiment can be executed by a sensing function network element, core network device, or sensing service system of this disclosure. Figure 1 As shown, Figure 1 The method of the embodiment may include at least one of steps 100 to 400, wherein:

[0076] Step 100: The sensing function network element receives a sensing data subscription request sent by the application function server, wherein the sensing data subscription request includes subscription scenario information.

[0077] In some embodiments of this disclosure, step 100 may include at least one of steps 110 to 120, wherein:

[0078] Step 110: The sensing function network element receives the subscription configuration file sent by the policy control function network element. The subscription configuration file is generated by the policy control function network element based on the subscription request data. The subscription request data is included in the sensing data subscription request sent by the application function server to the policy control function network element through NEF (Network Exposure Function). The subscription request data also includes at least one of the identification information of the application function server and the sensing data type to be subscribed to.

[0079] In some embodiments of this disclosure, the specific sensing scenario is defined by the sensing service application function server AF. The sensing service application function server AF sends the scenario information to be subscribed and the sensing data type to the sensing function network element SF. After receiving the configuration file of the subscription request, the sensing function network element SF confirms which base stations correspond to the specific subscribed sensing scenario and sensing data type. Then, it sets a unique scenario ID for each sensing scenario, binds all base station IDs corresponding to each scenario with the scenario ID, and updates the subscription configuration file.

[0080] In some embodiments of this disclosure, the scene information requested by AF includes: the location information of the scene center, and the range of the scene (radius or length, width, height, etc.).

[0081] Figure 2 These are schematic diagrams illustrating the design of scenarios and base stations in some embodiments of this disclosure. For example... Figure 2 As shown, each circle in the dashed line represents a sensing scenario defined by the AF (Awareness Controller) based on actual sensing service requirements. Since the AF cannot determine whether or which base stations in the scenario possess sensing capabilities to acquire sensing data, the AF only needs to report the location and spatial information of the requested sensing scenario, along with the corresponding sensing requirements, to the network. The specific sensing base stations within the scenario and the specific sensing capabilities they possess are determined by the network side.

[0082] Step 120: The sensing function network element receives a registry update request sent by the PCF (Policy Control Function), wherein the registry update request includes the subscription request data.

[0083] Step 200: The sensing function network element assigns a unique scene identifier to the subscribed scene information.

[0084] In some embodiments of this disclosure, step 200 may include: the sensing function network element updating the first subscription registry according to the subscription request data, wherein the first subscription registry is the subscription registry on the sensing function network element side; the first subscription registry includes at least one of the following: the identification information of the application function server, the subscription requirements of the application function server, the recorded base station information with sensing capabilities, and the data type that can be sensed and acquired, wherein the subscription requirements include at least one of the following: subscription scenario information, the binding relationship between the scenario identifier and the base station identifier, the sensing data type to be subscribed to, the data volume, and the data timeliness.

[0085] In some embodiments of this disclosure, step 200 may include at least one of steps 210 to 240, wherein:

[0086] Step 210: Compare the subscription request data with the recorded location information and sensing data type of the sensing-capable base station.

[0087] Step 220: Create a separate scene identifier for each subscribed scene.

[0088] In some embodiments of this disclosure, each scene, regardless of size, is assigned a unique scene ID by SF.

[0089] Step 230: Bind or update the corresponding base station identifier with sensing capability for each scene identifier, and generate the binding relationship between scene identifier and base station identifier.

[0090] In some embodiments of this disclosure, each scene ID may include one or more base station IDs. The base station ID corresponding to the scene ID is determined by SF based on the recorded base stations with sensing capabilities and the location information of the base stations.

[0091] In some embodiments of this disclosure, each base station ID may correspond to one or more scenario IDs, and the specific correspondence information is maintained by SF.

[0092] Step 240: Generate the binding relationship between the scene identifier and the identifier of the sensing function network element.

[0093] In some embodiments of this disclosure, each scene ID can correspond to one or more AF IDs after it is established (if multiple AFs request the same scene).

[0094] Step 300: The sensing function network element determines the sensing capability base stations existing in the sensing scenario.

[0095] Step 400: The sensing function network element performs relevant sensing request operations for the sensing capability base station.

[0096] In some embodiments of this disclosure, step 400 may include at least one of steps 410 to 420, wherein:

[0097] Step 410: The sensing function network element periodically sends sensing requests to the base station according to the requirements in the subscription configuration file, requesting the base station to obtain sensing data related to the requirements.

[0098] In some embodiments of this disclosure, step 410 may include at least one of steps 411 to 413, wherein:

[0099] Step 411: The sensing function network element generates a sensing service trigger table according to the requirements for data timeliness and sensing service time nodes in the subscription configuration file. The sensing service trigger table includes the identification information of the application function server and the data collection time nodes or time periods required by the application function server.

[0100] Step 412: The sensing function network element determines the identification information of the application function server corresponding to a fixed time node or according to a predetermined time period based on the sensing service trigger table, determines the scene identifier based on the identification information of the application function server, and determines the corresponding base station identifier based on the scene identifier.

[0101] Step 413: The sensing function network element sends a sensing request to the base station corresponding to the scenario, requesting the base station to perform sensing operations and obtain sensing data.

[0102] Step 420: After collecting and processing the sensing data, the sensing function network element pushes the sensing data to the application function server.

[0103] In some embodiments of this disclosure, step 420, in which the sensing function network element collects and processes the sensing data, may include: after receiving the sensing data reported by the base station, the sensing function network element performs relevant processing on the sensing data, wherein the relevant processing includes at least one of integrity check, sensitive information check, data quality check, data filtering, and data compression.

[0104] In some embodiments of this disclosure, step 420, the step of pushing the sensing data to the application function server, may include: the sensing function network element pushing the sensing data to the network open function network element, so that the network open function network element, upon receiving the push configuration file sent by the policy management function network element and the sensing data initiated by the sensing function network element, pushes the sensing data to the application function server.

[0105] In some embodiments of this disclosure, the sensing service method may further include: a sensing function network element reporting relevant information of a scene identifier to a policy management function network element for updating a second subscription registry, wherein the relevant information of the scene identifier includes the binding relationship between the scene identifier and the base station identifier, and the binding relationship between the scene identifier and the identifier of the sensing function network element, wherein the second subscription registry is a subscription registry on the policy management function network element side, and the first subscription registry includes the identifier information of the application function server, the subscription scene information, and the sensing function network elements covered by the subscription scene.

[0106] In some embodiments of this disclosure, the perception service method may further include: after reporting relevant information of the scene identifier to the policy management function network element, the perception function network element sends a push configuration file request to the policy management function network element; the perception function network element receives the push configuration file issued by the policy management function network element, wherein the push configuration file includes at least one of push time node or time period and push range; and the policy management function network element responds to the push configuration file request by simultaneously issuing an updated push configuration file to the perception function network element and the network open function network element.

[0107] In some embodiments of this disclosure, the sensing service method may further include: a sensing function network element determining whether the data already stored in the sensing function network element includes sensing data required by the application function server; if the data already stored in the sensing function network element includes the sensing data required by the application function server, pushing the sensing data to the application function server; if the data already stored in the sensing function network element does not include the sensing data required by the application function server, triggering the sensing function network element to perform the operation of sending a sensing request to the base station to request the base station to obtain sensing data related to the request for the first time.

[0108] The above embodiments of this disclosure provide a method for subscribing to and pushing services for sensing function network elements with base station sensing capabilities.

[0109] The embodiments disclosed above belong to the field of wireless communication and core network technology.

[0110] The above embodiments disclosed herein are a subscription-based push service model designed for network awareness capabilities. The related services and solutions are deployed within network awareness elements, enabling the network to provide more diverse network awareness services to application function servers.

[0111] To better address the design and deployment of services without terminal participation, the embodiments of this disclosure present a scenario-based design based on base station sensing capabilities, and a scenario-based subscription push service design. By defining the sensing objects and sensing operation executors in terminal-less sensing scenarios, and by implementing data collection and push led by the network side, the embodiments of this disclosure enable more rational deployment of sensing services.

[0112] Figure 3 These are schematic diagrams illustrating other embodiments of the sensing service method of this disclosure. Preferably, this embodiment can be executed by the core network device or the sensing service system of this disclosure. Figure 3 As shown, Figure 3 The method of the embodiment may include at least one of steps 1 to 18, wherein, Figure 3The sensing service method of the embodiment may include a subscription registration initiation process and a process of periodically collecting sensing data during the subscription period, wherein:

[0113] Figure 3 The subscription registration initiation process of this embodiment may include at least one of steps 1 to 9, wherein:

[0114] Step 1: The Application Function (AF) requests the Network Open Function (NEF) to subscribe to sensing scene data, reporting the scene information of the subscribed sensing service (location information of the scene center, geographical location information such as length, width, and height of the scene range), the application function ID (AF ID), and the type of sensing data to be subscribed. This information is provided for the creation of the sensing service.

[0115] Step 2: The Network Open Function (NEF) forwards the subscription request to the Policy Control Function (PCF). The PCF then generates a new subscription configuration file and a push configuration file, and updates the subscription and push registry on the PCF side.

[0116] Step 3: After completing the above operations, the Policy Control Function Network Element (PCF) will send data to the Sensing Function Network Element (SF) to update the subscription registry (first subscription registry) on the SF side. At the same time, it will send a new subscription configuration file to the SF and send the subscription scenario information of the subscriber to the SF for confirmation of the specific base station corresponding to each scenario.

[0117] Step 4: Upon receiving the request from the PCF, the sensing function network element (SF) compares the recorded location information and sensing data types of the base stations with sensing capabilities. It creates a unique scenario ID for each scenario and binds or updates the corresponding base station ID with sensing capabilities for each scenario ID. Then, it reports the binding information between the generated scenario ID and the base station ID, as well as the binding information between the scenario ID and the ID (SF ID) of the sensing function network element, to the policy management function network element (PCF) to update the subscription registry (second subscription registry) on the PCF side.

[0118] Step 5: After reporting the relevant information of the scene ID, the perception function network element SF requests the push configuration file of the subscriber from the policy control function network element PCF.

[0119] In steps 6 and 8, after updating the new scene ID and related information, PCF updates the corresponding push configuration file. After receiving the request for push configuration file from SF, PCF will simultaneously send the updated push configuration file to SF and NEF.

[0120] In some embodiments of this disclosure, the push configuration file sent to the SF side is saved by the SF, and the SF will continue to save and update this configuration file until the subscription is canceled.

[0121] In some embodiments of this disclosure, the push configuration file sent to NEF takes into account the capabilities of NEF network elements and is not stored on the NEF side. Therefore, the push configuration file on the NEF side is one-time and only valid once. So, each subsequent push requires the PCF to send a new push configuration file to NEF and then NEF pushes the data.

[0122] Step 7: After receiving the push configuration file, the sensing function network element SF checks the existing data, then triggers the first data collection, and sends the collected data, processed and packaged, to the network open function network element NEF.

[0123] In some embodiments of this disclosure, step 7 may include: the sensing function network element determining whether the data already stored in the sensing function network element includes the sensing data required by the application function server; if the data already stored in the sensing function network element includes the sensing data required by the application function server, pushing the sensing data to the application function server via NEF; if the data already stored in the sensing function network element does not include the sensing data required by the application function server, triggering the first data collection, triggering the sensing function network element to execute the operation of sending a sensing request to the base station to request the base station to obtain sensing data related to the requirement for the first time, that is, the process of periodically collecting sensing data during the subscription period in steps 11-18 is executed for the first time.

[0124] Step 9: After receiving the initial sensing data packet and push configuration file, the Network Open Function (NEF) pushes the sensing data to the corresponding subscriber according to the description in the configuration file, which is the application function (AF) of this sensing service.

[0125] Figure 3 The process of periodically collecting sensed data during the subscription period in the embodiment may include at least one of steps 11 to 18, wherein:

[0126] Step 11: Each time a Sensing Service Application Function (AF) initiates a subscription push service registration, the Sensing Function Network Element (SF) updates the stored "Sensing Service Trigger Table". The trigger table stores the subscriber IDs that need to execute the Sensing Service, as well as the relevant data timeliness requirements and time nodes or time periods.

[0127] Step 12: When the trigger table triggers the sensing operation according to the time requirements in the table, the sensing function network element SF will determine the specific scene ID according to the subscriber AF ID corresponding to the time in the trigger table, and send a sensing request to the base station corresponding to this scene according to the matching information in the SF.

[0128] Step 13: After receiving a request from the sensing function network element SF, the sensing base station (RAN) performs a sensing operation to acquire sensing data.

[0129] In some embodiments of this disclosure, such as Figure 3 As shown, the sensing base station performs sensing operations to acquire sensing data from sensing objects or sensing scenarios.

[0130] In some embodiments of this disclosure, the sensing object can be a vehicle, a person, or other sensing target. The step of acquiring sensing data from the sensing object may include: acquiring sensing data from the vehicle, person, or other sensing target.

[0131] In some other embodiments of this disclosure, the step of acquiring sensing data from the sensing scene may include acquiring sensing parameters such as temperature and humidity from the sensing scene.

[0132] Step 14: The base station with sensing capabilities uploads the received sensing data to SF.

[0133] In steps 15 and 17, after receiving the sensing data reported by the base station, the sensing function network element (SF) performs relevant operations and processing on the data (integrity check, sensitive information check, data quality check, data filtering, data compression, etc.) and then sends the data to the NEF. Simultaneously, the SF also sends a request to the PCF indicating that the sensing operation has been completed, reports the subscriber (AF ID) corresponding to this sensing operation, and requests the PCF to send the push file to the NEF based on the subscriber information.

[0134] Step 16: After receiving the request, the Policy Control Function Network Element (PCF) will send the push configuration file corresponding to the subscriber (AF ID) to the Network Open Function Network Element (NEF).

[0135] Step 18: After receiving the push configuration file issued by the PCF and the sensing data packet sent by the SF, the Network Open Function (NEF) pushes the sensing data packet to the corresponding subscriber according to the actual requirements of the push configuration file.

[0136] The current 3GPP architecture and services are mainly designed for terminals with active communication capabilities. The above-mentioned embodiments of this disclosure are designed for terminal-free scenarios included in the new sensing services, namely, service design based on base station sensing capabilities, so that sensing services can be carried out without terminal participation.

[0137] The above embodiments of this disclosure design a subscription push service centered on a sensing network element. By having the sensing network element proactively provide relevant services while meeting the sensing service requirements of a third-party AF, the two problems of base station information not being open to third-party AFs and the need to establish a direct connection and session between the AF and the base station are avoided.

[0138] The embodiments disclosed above avoid the problems of N1 port not being usable without a terminal and the large transmission load that the base station needs to transmit a large amount of raw sensing data on N2 and N3 ports by directly deploying interfaces between the sensing function network element SF and the base station (RAN).

[0139] In traditional business models, third-party AFs typically provide relevant terminal information, or the network establishes a connection and session after the terminal initiates a request. However, in scenarios without a terminal, the third-party AF does not know the base station information, and the network will not share base station information with the AF or establish an AF-to-base station connection. The embodiments described in this disclosure use a sensing function network element as the core, directly interacting with the base station to perform sensing operations and collect sensing data. This approach satisfies the needs of third-party AFs as much as possible while avoiding the sharing of base station-related information, and also avoids a large amount of session establishment and data transmission.

[0140] Because third-party AFs cannot establish a direct connection with the base station due to the relevant technologies, and in order to avoid congestion between AFs and the network caused by a large number of AFs sending requests to the network in a short period of time, the above embodiments of this disclosure design a subscription push service mode based on sensing function network elements. In this mode, AFs only need to register, report or update the corresponding requirements, and the network side can provide AFs with relevant data and service services for a long time, thereby avoiding congestion and waste of network resources that may be caused by AFs frequently sending requests to the network due to their own business needs.

[0141] Figure 4 This is a schematic diagram of some embodiments of the sensing function network elements of this disclosure. For example... Figure 4 As shown, the sensing function network element of this disclosure may include a request receiving module 41, a scene identifier allocation module 42, a sensing base station determination module 43, and a sensing request module 44, wherein:

[0142] The request receiving module 41 is configured to receive a sensing data subscription request sent by the application function server from the sensing function network element, wherein the sensing data subscription request includes subscription scenario information.

[0143] In some embodiments of this disclosure, the request receiving module 41 can be configured to receive a subscription configuration file sent by a policy control function network element, wherein the subscription configuration file is generated by the policy control function network element based on subscription request data, the subscription request data being included in a perception data subscription request sent by an application function server to the policy control function network element through a network open function network element, the subscription request data also including at least one of the identification information of the application function server and the perception data type to be subscribed; and to receive a registry update request sent by the policy control function network element, wherein the registry update request includes the subscription request data.

[0144] The scene identifier allocation module 42 is configured to allocate a unique scene identifier to the subscribed scene information.

[0145] In some embodiments of this disclosure, the scene identifier allocation module 42 can be configured to update the first subscription registry according to the subscription request data, wherein the first subscription registry is the subscription registry of the sensing function network element side; the first subscription registry includes at least one of the following: the identification information of the application function server, the subscription requirements of the application function server, the recorded base station information with sensing capabilities, and the data type that can be sensed and acquired, wherein the subscription requirements include at least one of the following: subscription scene information, the binding relationship between scene identifier and base station identifier, the sensing data type to be subscribed, the data volume, and the data timeliness.

[0146] In some embodiments of this disclosure, the scene identifier allocation module 42 can be configured to, when updating the first subscription registry based on the subscription request data, compare the subscription request data with the recorded location information and sensing data type of the sensing-capable base station; create a scene identifier for each subscription scene; bind or update the corresponding sensing-capable base station identifier for each scene identifier, generating a binding relationship between the scene identifier and the base station identifier; and generate a binding relationship between the scene identifier and the identifier of the sensing function network element.

[0147] The sensing base station determination module 43 is configured to determine the sensing capability base stations existing in the sensing scenario.

[0148] The perception request module 44 is configured to perform relevant perception request operations for the perception capability base station.

[0149] In some embodiments of this disclosure, the perception request module 44 can be configured to, when performing a perception request operation on the perception capability base station, periodically send perception requests to the base station according to the requirements in the subscription configuration file, requesting the base station to obtain perception data related to the requirements; after collecting and processing the perception data, push the perception data to the application function server.

[0150] In some embodiments of this disclosure, the sensing request module 44 may be configured to perform relevant processing on the sensing data after receiving the sensing data reported by the base station when the sensing data is collected and processed. The relevant processing includes at least one of integrity check, sensitive information check, data quality check, data filtering, and data compression.

[0151] In some embodiments of this disclosure, the perception request module 44 may be configured to push the perception data to the network open function element when the perception data is pushed to the application function server, so that the network open function element pushes the perception data to the application function server when it receives the push configuration file sent by the policy management function element and the perception data initiated by the perception function element.

[0152] In some embodiments of this disclosure, the sensing request module 44 can be configured to periodically send sensing requests to the base station according to the requirements in the subscription configuration file, requesting the base station to obtain sensing data related to the requirements. The module then generates a sensing service trigger table based on the data timeliness and time node requirements of the sensing service in the subscription configuration file. The sensing service trigger table includes the identification information of the application function server and the data collection time node or time period required by the application function server. Based on the sensing service trigger table, at a fixed time node or according to a predetermined time period, the module determines the identification information of the application function server corresponding to that time, determines a scene identifier based on the identification information of the application function server, determines the corresponding base station identifier based on the scene identifier, and sends a sensing request to the base station corresponding to that scene, requesting the base station to perform a sensing operation and obtain sensing data.

[0153] In some embodiments of this disclosure, the sensing function network element can also be configured to report relevant information of the scene identifier to the policy management function network element for updating the second subscription registry. The relevant information of the scene identifier includes the binding relationship between the scene identifier and the base station identifier, and the binding relationship between the scene identifier and the identifier of the sensing function network element. The second subscription registry is a subscription registry on the policy management function network element side, and the first subscription registry includes the identification information of the application function server, the subscription scene information, and the sensing function network elements covered by the subscription scene.

[0154] In some embodiments of this disclosure, the sensing function network element can also be configured to send a push configuration file request to the policy management function network element after reporting relevant information of the scene identifier to the policy management function network element; receive the push configuration file issued by the policy management function network element, wherein the push configuration file includes at least one of push time node or time period and push range; and the policy management function network element responds to the push configuration file request by simultaneously issuing an updated push configuration file to the sensing function network element and the network open function network element.

[0155] In some embodiments of this disclosure, the sensing function network element may also be configured to determine whether the data already stored in the sensing function network element includes the sensing data required by the application function server; if the data already stored in the sensing function network element includes the sensing data required by the application function server, push the sensing data to the application function server; if the data already stored in the sensing function network element does not include the sensing data required by the application function server, trigger the sensing function network element to perform the operation of sending a sensing request to the base station for the first time, requesting the base station to obtain the sensing data related to the request.

[0156] In some embodiments of this disclosure, the sensing function network element of this disclosure can also be configured to perform the above embodiments of this disclosure (e.g., Figure 1 Implementation examples Figure 3 The perception service method described in any one of steps 2 to 7, 11 to 12, 14 to 15, and 17 of the embodiment.

[0157] Figure 5 The diagram shows the structure of some other embodiments of the sensing function network element of this disclosure. For example... Figure 5 As shown, the sensing function network element includes a memory 51 and a processor 52.

[0158] Memory 51 is used to store instructions, and processor 52 is coupled to memory 51. Processor 52 is configured to execute instructions stored in memory to implement the embodiments of this disclosure described above (e.g., Figure 1 Implementation examples Figure 3 The perception service method described in any one of steps 2 to 7, 11 to 12, 14 to 15, and 17 of the embodiment.

[0159] like Figure 5 As shown, the sensing network element also includes a communication interface 53 for information exchange with other devices. Additionally, the sensing network element includes a bus 54, through which the processor 52, communication interface 53, and memory 51 communicate with each other.

[0160] The memory 51 may include high-speed RAM, and may also include non-volatile memory, such as at least one disk drive. The memory 51 may also be a memory array. The memory 51 may also be divided into blocks, and the blocks may be combined into virtual volumes according to certain rules.

[0161] Furthermore, processor 52 may be a central processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to implement embodiments of the present disclosure.

[0162] In scenarios with large-scale deployment of sensing terminals and fixed sensing service application functions (AF), the service modes of the above embodiments of this disclosure can be deployed, such as in hospitals, schools, warehousing centers, department stores, and large train stations. Since the above embodiments of this disclosure mainly target sensing services without terminal sensing, i.e., sensing services based on base station sensing capabilities, in both outdoor and indoor scenarios, relevant service providers such as hospitals, schools, and government agencies can subscribe to the relevant sensing services and required sensing data from the operator. The operator then uses locally deployed base stations to perform sensing operations on demand, collect sensing data, and provide customizable sensing services to the relevant subscribers.

[0163] The technical effect of the above embodiments disclosed is that: in the future, as the demand for sensing services increases, the demand for networks will also increase. Although a large amount of sensing data places higher demands on the network load and data processing capabilities, it can also bring huge commercial value. A large amount of raw sensing data can enable the network to provide more and richer data services to third-party service providers, thereby significantly increasing the market size.

[0164] With the emergence of many new terminal-free scenarios in the future, scenario-based services will become increasingly common. Many scenarios will simultaneously include both terminal services and base station services. The service designs and customized scenario-based designs proposed in the above embodiments of this disclosure may be gradually applied to more services as various new businesses emerge.

[0165] Figure 6 This is a schematic diagram of some embodiments of the core network equipment disclosed herein. Figure 3 Also provided are schematic diagrams of some embodiments of the core network equipment besides those disclosed herein. For example... Figure 3 and Figure 6 As shown, the core network equipment disclosed herein may include a sensing function network element (SF) 61, wherein:

[0166] The sensing function network element 61 can be any of the embodiments described above (e.g.) Figure 4 or Figure 5 The sensing function network element described in the embodiment).

[0167] In some embodiments of this disclosure, the sensing function network element 61 can be configured to manage network-related sensing capabilities, and to manage and process the corresponding sensing functions, sensing operations, and sensing data of base stations with sensing capabilities registered on the network side. In this system, this network element mainly manages and records the base stations with sensing capabilities, as well as related sensing services and sensing operations, and collects related sensing data. The sensing function network element 61 also has the ability to store related sensing data and process it.

[0168] In some embodiments of this disclosure, the sensing function network element 61 can also be configured to maintain a registry for the subscription push service. The registry content mainly includes: the registered subscribed AF (AF ID), the subscription requirements of the registered subscribed AF (scene information, scene ID and base station ID, data type, data volume, data timeliness, etc.), the recorded base station information with sensing capabilities, and the data types that can be sensed and acquired. Finally, the sensing function network element SF also has a sensing service trigger table. This table is generated based on the requirements for data timeliness and the time nodes of sensing services in the subscription configuration file. The content of this service trigger table is: the subscriber AF ID + the data collection time node or time period required by this subscriber. Subsequent data collection and data push are performed by the SF collecting relevant sensing data and pushing the data according to this service trigger table.

[0169] In some embodiments of this disclosure, the sensing function network element SF is designed to be deployed in a distributed manner in this system, that is, there will be multiple sub-sensing function network elements SF in the system, which are connected to different single or multiple base stations respectively.

[0170] In some embodiments of this disclosure, such as Figure 3 and Figure 6 As shown, the core network equipment disclosed herein may include a policy control function (PCF) 62, wherein:

[0171] The policy control function network element 62 is configured to receive a perception data subscription request sent by the application function server through the network open function network element to the policy control function network element. The perception data subscription request includes subscription request data, which includes at least one of the following: subscription scenario information, identification information of the application function server, and the type of perception data to be subscribed to. The configuration file is generated based on the subscription request data. The perception function network element corresponding to the subscription scenario information is determined based on the correspondence between the scenario information and the perception function network element. The subscription request data and the subscription configuration file are then sent to the perception function network element corresponding to the subscription scenario information.

[0172] In some embodiments of this disclosure, the policy control function network element 62 can be configured to be mainly responsible for maintaining the subscription registry and the corresponding subscription configuration file in this system. The content of the subscription registry includes: the AF (AFID) of the registered subscription, the scene information (location information and scene ID) of the sub-sensing network element (SFID) covered by the subscribed sensing scene.

[0173] In some embodiments of this disclosure, such as Figure 3 and Figure 6 As shown, the core network equipment disclosed herein may include a Network Open Function (NEF) element 63, wherein:

[0174] Network open function element 63 is configured to push the perception data packet to the corresponding application function server according to the actual requirements of the push configuration file after receiving the push configuration file issued by the policy control function element and the perception data packet sent by the perception function element.

[0175] In some embodiments of this disclosure, the policy control function network element 62 can be configured to forward relevant subscription data, perform relevant integrity and quality of service checks on the data, and push the data to the relevant subscription server AF.

[0176] Figure 6 Schematic diagrams of some embodiments of the perception service system disclosed herein are also provided. Figure 3 Also shown are schematic diagrams of some embodiments of the perception service system besides those disclosed herein. For example... Figure 3 and Figure 6 As shown, the perception service system disclosed herein may include the core network equipment as described in any of the above embodiments.

[0177] In some embodiments of this disclosure, such as Figure 3 and Figure 6 As shown, the perception service system may further include an application function server (AF) 64, wherein:

[0178] Application function server 64 is configured to send a sensing data subscription request to core network equipment. The sensing data subscription request includes subscription request data, which includes at least one of the following: subscription scenario information, identification information of the application function server, and sensing data type to be subscribed. The scenario is a geographical or spatial range that needs to perform sensing operations based on one or more base stations.

[0179] In some embodiments of this disclosure, the application function server 64, in this system, is mainly a capability module or server accessed by a third party for the sensing service. It can be configured to register and subscribe to the sensing function network element on the core network side to obtain relevant sensing terminal information and sensing data, and deploy relevant services using the subscribed sensing data according to its own business needs.

[0180] In some embodiments of this disclosure, such as Figure 3 and Figure 6 As shown, the sensing service system may further include a sensing base station (RAN) 65, wherein:

[0181] The sensing base station 65 is configured to perform a sensing operation after receiving a sensing request from a sensing function network element in the core network equipment, and then upload the received sensing data to the sensing function network element.

[0182] In some embodiments of this disclosure, such as Figure 3 and Figure 6 As shown, the sensing capability base station 65 performs sensing operations to acquire sensing data from sensing objects or sensing scenarios.

[0183] In some embodiments of this disclosure, the sensing object can be a vehicle, a person, or other sensing target. The step of acquiring sensing data from the sensing object may include: acquiring sensing data from the vehicle, person, or other sensing target.

[0184] In some other embodiments of this disclosure, the step of acquiring sensing data from the sensing scene may include acquiring sensing parameters such as temperature and humidity from the sensing scene.

[0185] In some embodiments of this disclosure, such as Figure 3 and Figure 6 As shown, the sensing function network element SF has added three main interfaces: the interface between SF and the base station (RAN), the interface between SF and PCF, and the interface between SF and NEF, among which:

[0186] SF and NEF interface: mainly used to transmit sensing data collected and processed by SF.

[0187] SF and PCF interface: mainly used to transmit registry update requests and configuration files issued by PCF, as well as registry update requests and push requests sent by SF.

[0188] SF and base station (RAN) interface: mainly used by the base station to transmit raw sensing data to the sensing function network element SF.

[0189] In some embodiments of this disclosure, the interface between the SF and the base station (RAN) is mainly because in terminal-free sensing scenarios, the base station performs the sensing operation. Without the participation of a terminal, the existing N1 and N2 interfaces will no longer be applicable. Even if the N2 interface is expanded, considering that the amount of sensing data is extremely large, it will put great transmission pressure on the N2 interface. Therefore, it is a more suitable solution to create a new interface between the sensing function network element and the base station (RAN) for transmitting the original sensing data.

[0190] The above embodiments disclosed herein are a sensing service mode designed based on the sensing function of the core network.

[0191] The above embodiments disclosed herein are mainly designed for a sensing service mode for base stations with sensing capabilities.

[0192] The above embodiments of this disclosure propose a scenario-based solution, in which a third-party AF describes the required sensing business needs by reporting scenario information that requires the sensing operation to be performed.

[0193] In some embodiments of this disclosure, the scenario is a geographical or spatial range that requires sensing operations to be performed based on one or more base stations.

[0194] In some embodiments of this disclosure, the core network awareness function (SF) is primarily responsible for the management and execution of the subscription push service.

[0195] In some embodiments of this disclosure, the core network policy control function PCF is mainly responsible for maintaining the correspondence between scene information and perception function SF (Note: Because the perception function network element SF has a distributed deployment scheme, there will actually be multiple sub-perception function network elements. This correspondence is the correspondence information between the perception scene and the sub-perception function network element).

[0196] In some embodiments of this disclosure, the core network policy control function (PCF) is primarily responsible for maintaining the configuration files of sensing-enabled base stations.

[0197] In some embodiments of this disclosure, the core network policy control function PCF is mainly responsible for maintaining the subscription registry. The contents of the subscription registry are: the registered subscribed AF (AF ID), the subscribed scene information (location information and scene ID), and the sub-sensing network elements (SF ID) covered by the subscribed sensing scene.

[0198] In some embodiments of this disclosure, the core network policy control function (PCF) is primarily responsible for maintaining push configuration files.

[0199] In some embodiments of this disclosure, the core network sensing function SF protects the registration registry for the subscription push service. The registry content mainly includes: the registered subscribed AF (AF ID), the subscription requirements of the registered subscribed AF (scene information, scene ID and base station ID, data type, data volume, data timeliness, etc.), the recorded base station information with sensing capabilities, and the data types that can be sensed and obtained.

[0200] In some embodiments of this disclosure, the sensing function network element SF maintains a sensing service trigger table. This table is generated based on the requirements for data timeliness and the time nodes of sensing services in the subscription configuration file. The content of this service trigger table is: subscriber AF ID + the data collection time node or time period required by this subscriber.

[0201] In some embodiments of this disclosure, the sensing function network element SF has three interfaces with the base station, the policy control function PCF, and the network capability openness NEF.

[0202] The above embodiments of this disclosure design a set of process specifications for this subscription push service.

[0203] This disclosure provides a terminalless sensing service system. The Application Function Server (AF) registers and subscribes to push services with the Policy Control Function (PCF) and Sensing Function Network Element (SF) through the Network Open Function (NEF). Information about base stations with sensing capabilities is recorded in the Sensing Function Network Element (SF). Simultaneously, during the execution of the sensing service, requests and data collection are issued based on the specific recorded scenario and base station. After the Sensing Service Application Server (AF) registers with the Sensing Function Network Element (SF), the PCF synchronously sends a specific subscription configuration file to the Sensing Function Network Element (SF). Subsequently, the Sensing Function Network Element (SF) periodically requests relevant sensing data from the base station according to the requirements in the subscription configuration file, collects and processes the sensing data, and then pushes it to the subscribing Sensing Service Application Function Server (AF).

[0204] Based on the technical problems of related technologies, the above embodiments of this disclosure design a service based on terminalless operation and base station sensing capabilities, where the sensing network element (SF) leads the subscription and push of related sensing services. In addition to establishing a sensing function network element on the core network side, the above embodiments of this disclosure deploy a new interface between the sensing function network element (SF) and the base station (RAN), enabling the execution of services based on base station sensing capabilities to bypass existing N1, N2, N3 interfaces and functional network elements such as AMF, UPF, and SMF, and directly transmit sensing data to the sensing function network element (SF).

[0205] Meanwhile, the embodiments disclosed above transform the terminal-based sensing service design into a scenario-based sensing service. The scenarios reported by the third-party application function (AF) are specialized, and a unique ID is assigned to each scenario. Sensing operations and services are then executed based on each scenario ID. In the traditional model, the sensing function network element (SF) executes sensing operations and services based on each sensing terminal. However, in the scenario-based model, the sensing service based on base station sensing capabilities does not use a single base station as the unit of sensing service. Instead, it executes sensing services based on each unique scenario and all sensing-capable base stations within that scenario. This avoids the problem of base station information not being accessible to third-party AFs.

[0206] Finally, to avoid the problem of excessive data volume and load that may result from establishing direct connections between the AF and the base station and a large number of sessions, the above embodiments of this disclosure design a subscription and push service mode based on sensing function network elements. This allows the SF on the network side to have some control over the service of sensing services, avoiding the need for the network to directly establish connections and sessions between the AF and a single base station in sensing scenarios without terminals. At the same time, since the SF is on the core network side, it can know the actual network load and actively adjust the data processing and transmission of sensing services according to the actual network load. This allows for flexible fine-tuning of services with lower timeliness or data requirement levels and services with higher requirements.

[0207] According to another aspect of this disclosure, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores computer instructions that, when executed by a processor, implement any of the embodiments described above (e.g., Figure 1 or Figure 3 The sensing service method described in the embodiment).

[0208] In some embodiments of this disclosure, the computer-readable storage medium may be a non-transitory computer-readable storage medium.

[0209] Those skilled in the art will understand that embodiments of this disclosure can be provided as methods, apparatus, or computer program products. Therefore, this disclosure can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this disclosure can take the form of a computer program product embodied on one or more computer-usable non-transitory storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0210] This disclosure is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this disclosure. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create a machine for implementing the flowchart illustrations. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0211] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0212] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0213] The sensing function network elements, request receiving module, scene identifier allocation module, sensing base station determination module, sensing request module, network open function network elements, policy control function network elements, core network equipment, sensing service system, application function server and sensing capability base station described above can be implemented as general-purpose processors, programmable logic controllers (PLCs), digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components or any suitable combination thereof for performing the functions described in this application.

[0214] This concludes the detailed description of the present disclosure. To avoid obscuring the concept of the disclosure, some details known in the art have not been described. Those skilled in the art will fully understand how to implement the technical solutions disclosed herein based on the above description.

[0215] Those skilled in the art will understand that all or part of the steps of the above embodiments can be implemented by hardware, or by a program instructing the relevant hardware to implement them. The program can be stored in a non-transitory computer-readable storage medium, such as a read-only memory, a disk, or an optical disk.

[0216] The description in this disclosure is provided for illustrative and descriptive purposes only and is not intended to be exhaustive or to limit the disclosure to its forms. Many modifications and variations will be apparent to those skilled in the art. The embodiments were chosen and described in order to better illustrate the principles and practical application of this disclosure and to enable those skilled in the art to understand this disclosure and to design various embodiments with various modifications suitable for a particular purpose.

Claims

1. A method for a perception service, comprising: receiving, by a perception function network element, a perception data subscription request sent by an application function server, wherein the perception data subscription request comprises subscription scenario information; allocating, by the perception function network element, a dedicated scenario identifier for the subscription scenario information; determining, by the perception function network element, a perception-capable base station existing in a perception scenario; performing, by the perception function network element, a related perception request operation for the perception-capable base station; wherein the receiving, by the perception function network element, the perception data subscription request sent by the application function server comprises: receiving, by the perception function network element, a subscription configuration file sent by a policy control function network element, wherein the subscription configuration file is generated by the policy control function network element according to subscription request data, the subscription request data is contained in a perception data subscription request sent by the application function server to the policy control function network element through a network exposure function network element, and the subscription request data further comprises at least one of identifier information of the application function server and a type of perception data to be subscribed; receiving, by the perception function network element, a registry update request sent by the policy control function network element, wherein the registry update request comprises the subscription request data; allocating, by the perception function network element, the dedicated scenario identifier for the subscription scenario information comprises: updating, by the perception function network element, a first subscription registry according to the subscription request data, wherein the first subscription registry is a subscription registry on the side of the perception function network element, and the first subscription registry comprises at least one of the identifier information of the application function server, a subscription requirement of the application function server, recorded information of the perception-capable base station, and a type of perception data that can be sensed.

2. The awareness service method of claim 1, wherein, The updating, by the perception function network element, the first subscription registry according to the subscription request data comprises: comparing the subscription request data with recorded location information of the perception-capable base station and a type of perception data; individually creating a scenario identifier for each subscription scenario; binding or updating a corresponding base station identifier of the perception-capable base station for each scenario identifier, to generate a binding relationship between the scenario identifier and the base station identifier; generating a binding relationship between the scenario identifier and an identifier of the perception function network element. 3.The method according to claim 2, further comprising: reporting, by the perception function network element, related information of the scenario identifier to a policy management function network element, for updating a second subscription registry, wherein the related information of the scenario identifier comprises the binding relationship between the scenario identifier and the base station identifier, the binding relationship between the scenario identifier and the identifier of the perception function network element, and the second subscription registry is a subscription registry on the side of the policy management function network element, and the first subscription registry comprises the identifier information of the application function server, the subscription scenario information, and a perception function network element covered by the subscription scenario. 4.The method according to claim 3, further comprising: The perception function network element sends a push profile request to the policy management function network element after reporting the related information of the scene identification to the policy management function network element; The perception function network element receives the push profile sent by the policy management function network element, wherein the push profile comprises at least one of a push time node or a time period, a push range, and the policy management function network element simultaneously sends the updated push profile to the perception function network element and the network exposure function network element in response to the push profile request.

5. The perception service method of claim 4, further comprising: The perception function network element determines whether the perception data required by the application function server is included in the data already stored in the perception function network element; In the case where the perception data required by the application function server is included in the data already stored in the perception function network element, the perception data is pushed to the application function server; In the case where the perception data required by the application function server is not included in the data already stored in the perception function network element, the perception function network element triggers the first execution of the operation of sending the perception request to the base station to request the base station to obtain the perception data related to the requirement.

6. The perception service method according to any one of claims 1-5, wherein, The operation of sending the perception request by the perception function network element to the base station comprises: The perception function network element periodically sends the perception request to the base station to request the base station to obtain the perception data related to the requirement according to the requirement in the subscription profile; The perception function network element collects and processes the perception data and then pushes the perception data to the application function server.

7. The awareness service method of claim 6, wherein, The operation of pushing the perception data to the application function server comprises: The perception function network element pushes the perception data to the network exposure function network element, so that the network exposure function network element pushes the perception data to the application function server in the case where the push profile sent by the policy management function network element and the perception data triggered by the perception function network element are received. 8.The awareness service method of claim 6, wherein, The operation of periodically sending the perception request by the perception function network element to the base station to request the base station to obtain the perception data related to the requirement according to the requirement in the subscription profile comprises: The perception function network element generates a perception service trigger table according to the requirement for the data time effectiveness and the time node of the perception service in the subscription profile, wherein the perception service trigger table comprises the identification information of the application function server and the data collection time node or time period required by the application function server; The perception function network element determines the identification information of the application function server corresponding to the time according to the perception service trigger table at the fixed time node or according to the predetermined time period, determines the scene identification according to the identification information of the application function server, and determines the corresponding base station identification according to the scene identification; The perception function network element sends the perception request to the base station corresponding to the scene to request the base station to perform the perception operation and obtain the perception data. 9.The awareness service method of claim 6, wherein, The operation of collecting and processing the perception data by the perception function network element comprises: The perception function network element performs the related processing on the perception data after receiving the perception data reported by the base station, wherein the related processing comprises at least one of integrity check, sensitive information check, data quality check, data screening, and data compression.

10. A perception function network element, comprising: a request receiving module configured to receive a perception data subscription request sent by an application function server, wherein the perception data subscription request comprises subscription scenario information; wherein the request receiving module is configured to receive a subscription profile sent by a policy control function network element, the subscription profile being generated by the policy control function network element according to subscription request data, the subscription request data being included in the perception data subscription request sent by the application function server to the policy control function network element through a network exposure function network element, the subscription request data further comprising at least one of identification information of the application function server and a type of perception data to be subscribed; and receive a registry update request sent by the policy control function network element, the registry update request comprising the subscription request data; a scenario identification allocation module configured to allocate a dedicated scenario identification to the subscription scenario information; wherein the scenario identification allocation module is configured to update a first subscription registry according to the subscription request data, the first subscription registry being a subscription registry on the side of the perception function network element; the first subscription registry comprising at least one of the identification information of the application function server, subscription requirements of the application function server, recorded information of a base station with perception capability, and a type of data that can be perceived and acquired; wherein the subscription requirements comprise at least one of a binding relationship between the subscription scenario information, a scenario identification, and a base station identification, a type of perception data to be subscribed, a data volume, and a data timeliness; a perception base station determination module configured to determine a perception capability base station existing in a perception scenario; a perception request module configured to perform a related perception request operation on the perception capability base station.

11. A perception function network element, comprising: a memory configured to store instructions; a processor configured to execute the instructions, so that the perception function network element performs operations for implementing the perception service method according to any one of claims 1-9.

12. A core network device comprising the perception function network element according to claim 10 or 11.

13. The core network device according to claim 12, further comprising: a policy control function network element configured to receive a perception data subscription request sent by an application function server to the policy control function network element through a network exposure function network element, wherein the perception data subscription request comprises subscription request data, the subscription request data comprising at least one of subscription scenario information, identification information of the application function server, and a type of perception data to be subscribed; generate a subscription profile according to the subscription request data; determine a perception function network element corresponding to the subscription scenario information according to a correspondence relationship between the subscription scenario information and the perception function network element; and send the subscription request data and the subscription profile to the perception function network element corresponding to the subscription scenario information.

14. The core network device according to claim 13, further comprising: The network exposure function network element is configured to push the sensing data packet to the corresponding application function server according to actual requirements of the push configuration file after receiving the push configuration file issued by the policy control function network element and the sensing data packet sent by the sensing function network element.

15. A sensing service system comprising the core network device of any one of claims 12 to 14.

16. The sensing service system of claim 15, further comprising: an application function server configured to send a sensing data subscription request to the core network device, wherein the sensing data subscription request comprises subscription request data, and the subscription request data comprises at least one of subscription scenario information, identification information of the application function server, and a type of sensing data that needs to be subscribed, and the scenario is a geographical range or a spatial range based on a single or multiple base stations that needs to perform a sensing operation.

17. The sensing service system of claim 16, further comprising: a sensing capability base station configured to perform a sensing operation after receiving a sensing request from the sensing function network element in the core network device, and then upload the received sensing data to the sensing function network element.

18. A computer readable storage medium, wherein, The computer readable storage medium stores computer instructions, and the instructions are executed by the processor to implement the sensing service method of any one of claims 1-9.

Images