Perception service method and system, perception function network element, core network and storage medium
The perception service method and system address the challenge of accessing perception data from base stations by using SF entities to manage and push perception data, enhancing efficiency and reducing network load, enabling effective scene-based perception services for third-party AFs.
Patent Information
- Application Number
- CN202311273201.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-09-28
- Publication Date
- 2025-03-28
- Estimated Expiration
- 2043-09-28
AI Technical Summary
In the context of network-based perception services, the challenge lies in enabling third-party Application Functions (AF) to request and receive perception data from base stations without direct connection establishment, as base stations do not typically share configuration information with third parties, and existing solutions struggle with managing large volumes of data and avoiding network overload.
A perception service method and system where a Sensing Function (SF) net entity receives subscription requests from AF servers, allocates scene identifiers, determines capable base stations, and executes perception requests, enabling push-based services by managing data collection and transmission through a network of SF entities and base stations.
This approach allows for efficient, scene-based perception services by directing data collection and push operations, reducing network load and enabling third-party AFs to access necessary perception data without direct base station connections, thus addressing the limitations of existing technologies.
Smart Images

Figure CN119729874A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to the field of wireless communications, and in particular to a perception service method and system, a perception function network element, a core network and a storage medium. Background Art
[0002] Related technologies In the process of research and standardization of network perception capabilities, the perception service based on non-terminal perception, that is, based on base station perception capabilities, is a relatively special service type, because there is no terminal participation in this type of perception service. Summary of the invention
[0003] The inventors have found through research that: in the related technology, although the base station has the ability to provide perception services, the base station cannot open relevant configuration information to the third-party AF (Application Function) server like the terminal, and the third-party AF server cannot request to establish a direct connection with the base station by reporting an ID like connecting to the terminal. Therefore, how to let the base station execute the perception request sent by the application function server AF related to the third-party perception service and transmit the data back to AF is a difficulty in the existing research.
[0004] In view of at least one of the above technical problems, the present disclosure provides a perception service method and system, a perception function network element, a core network and a storage medium. By directly reporting the scene information that needs to be perceived by AF, it can provide a subscription push service for related perception services and perception services based on terminal-free and base station perception capabilities, with SF (Sensing Function, perception function network element) leading the way.
[0005] According to one aspect of the present disclosure, a sensing service method is provided, including:
[0006] The perception function network element receives a perception data subscription request sent by the application function server, wherein the perception data subscription request includes subscription scenario information;
[0007] The perception function network element allocates an exclusive scenario identifier for the subscription scenario information;
[0008] The perception function network element determines the perception capability base stations existing in the perception scenario;
[0009] The perception function network element executes relevant perception request operations for the perception capability base station.
[0010] In some embodiments of the present disclosure, the receiving, by the perception function network element, a perception data subscription request sent by an application function server includes:
[0011] The perception function network element receives a subscription configuration file sent by the 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 included in the perception data subscription request sent by the application function server to the policy control function network element through the network open function network element, and the subscription request data also includes at least one of identification information of the application function server and the type of perception data to be subscribed;
[0012] The perception function network element receives a registration table update request sent by the policy control function network element, wherein the registration table update request includes the subscription request data.
[0013] In some embodiments of the present disclosure, the perception function network element assigning a dedicated scenario identifier to the subscription scenario information includes:
[0014] The perception function network element updates the first subscription registration table according to the subscription request data, wherein the first subscription registration table is the subscription registration table on the perception function network element side; the first subscription registration table includes the identification information of the application function server, the subscription requirements of the application function server, the recorded base station information with perception capabilities, and at least one of the types of data that can be perceived and obtained, wherein the subscription requirements include subscription scenario information, the binding relationship between the scenario identifier and the base station identifier, the type of perception data that needs to be subscribed, and at least one of the data volume and data timeliness.
[0015] In some embodiments of the present disclosure, the perception function network element updating the first subscription registration table according to the subscription request data includes:
[0016] Comparing the subscription request data with the recorded location information of the base station with sensing capability and the type of sensing data;
[0017] Create a separate scenario ID for each subscription scenario;
[0018] Bind or update the corresponding base station identifier with perception capability for each scene identifier, and generate a binding relationship between the scene identifier and the base station identifier;
[0019] Generate a binding relationship between the scene identifier and the identifier of the perception function network element.
[0020] In some embodiments of the present disclosure, the service perception method further includes:
[0021] The perception function network element reports the relevant information of the scene identifier to the policy management function network element for updating the second subscription registration table, 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 perception function network element. The second subscription registration table is the subscription registration table on the policy management function network element side, and the first subscription registration table includes the identification information of the application function server, the subscription scene information, and the perception function network elements covered by the subscription scene.
[0022] In some embodiments of the present disclosure, the perception service method further includes: after the perception function network element reports the relevant information of the scenario identifier to the policy management function network element, sending a push configuration file request to the policy management function network element;
[0023] The perception function network element receives a push configuration file issued by the policy management function network element, wherein the push configuration file includes at least one of a push time node or time period and a push range. The policy management function network element responds to the push configuration file request and simultaneously issues an updated push configuration file to the perception function network element and the network open function network element.
[0024] In some embodiments of the present disclosure, the perception service method further includes: the perception function network element determines whether the data stored in the perception function network element includes the perception data required by the application function server;
[0025] In the case where the data already stored in the perception function network element includes the perception data required by the application function server, pushing the perception data to the application function server;
[0026] In the case that the data already stored in the perception function network element does not include the perception data required by the application function server, the perception function network element is triggered to execute the operation of sending a perception request to the base station for the first time to request the base station to obtain the perception data related to the requirement.
[0027] In some embodiments of the present disclosure, the sensing function network element performs a sensing request operation on the sensing capability base station, including:
[0028] The sensing function network element periodically sends a sensing request 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 perception data, the perception function network element pushes the perception data to the application function server.
[0030] In some embodiments of the present disclosure, pushing the perception data to the application function server includes:
[0031] The perception function network element pushes the perception data to the network open function network element, so that the network open function network element pushes the perception data to the application function server when receiving the push configuration file sent by the policy management function network element and the perception data initiated by the perception function network element.
[0032] In some embodiments of the present disclosure, the sensing function network element periodically sends a sensing request to the base station according to a requirement in a subscription configuration file, and the requesting the base station to obtain sensing data related to the requirement includes:
[0033] The perception function network element generates a perception service trigger table according to the requirements for data timeliness and time nodes of the perception service in the subscription configuration file, wherein the perception service trigger table includes identification information of the application function server, and a data collection time node or time period required by the application function server;
[0034] The perception function network element determines, according to the perception service trigger table, at a fixed time node or according to a predetermined time period, the identification information of the application function server corresponding to the time, 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;
[0035] The perception function network element sends a perception request to the base station corresponding to the scene, requesting the base station to perform a perception operation and obtain perception data.
[0036] In some embodiments of the present disclosure, the sensing function network element collecting and processing the sensing data includes:
[0037] After receiving the perception data reported by the base station, the perception function network element performs relevant processing on the perception data, wherein the relevant processing includes at least one of integrity check, sensitive information check, data quality check, data screening and data compression.
[0038] According to another aspect of the present disclosure, a perception function network element is provided, including:
[0039] A request receiving module is configured to receive, by a perception function network element, a perception data subscription request sent by an application function server, wherein the perception data subscription request includes subscription scenario information;
[0040] A scene identifier allocation module, configured to allocate an exclusive scene identifier to the subscribed scene information;
[0041] A sensing base station determination module is configured to determine a sensing-capable base station existing in the sensing scene;
[0042] The perception request module is configured to perform relevant perception request operations on the perception capability base station.
[0043] According to another aspect of the present disclosure, a perception function network element is provided, including:
[0044] a memory configured to store instructions;
[0045] The processor is configured to execute the instruction so that the perception function network element performs the operation of implementing the perception service method as described in any of the above embodiments.
[0046] According to another aspect of the present disclosure, a core network device is provided, comprising a perception function network element as described in any of the above embodiments.
[0047] In some embodiments of the present disclosure, the core network device further includes:
[0048] A policy control function network element is configured to receive 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, wherein the perception data subscription request includes subscription request data, and the subscription request data includes subscription scenario information, identification information of the application function server and at least one of the perception data types that need to be subscribed; generate a subscription configuration file according to the subscription request data; determine the perception function network element corresponding to the subscription scenario information according to the correspondence between the protection scenario information and the perception function network element; and send 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 the present disclosure, the core network device further includes:
[0050] The network open function network 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 network element and the perception data packet sent by the perception function network element.
[0051] According to another aspect of the present disclosure, a perception service system is provided, comprising a core network device as described in any of the above embodiments.
[0052] In some embodiments of the present disclosure, the perception service system further includes:
[0053] An application function server is configured to send a perception data subscription request to a core network device, wherein the perception data subscription request includes subscription request data, and the subscription request data includes subscription scenario information, identification information of the application function server and at least one of the types of perception data that need to be subscribed, and the scenario is a geographical scope or spatial scope in which perception operations need to be performed based on a single or multiple base stations.
[0054] In some embodiments of the present disclosure, the perception service system further includes:
[0055] The perception capability base station is configured to perform a perception operation after receiving a perception request from a perception function network element in a core network device, and then upload the received perception data to the perception function network element.
[0056] According to another aspect of the present disclosure, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores computer instructions, and when the instructions are executed by a processor, the perception service method as described in any of the above embodiments is implemented.
[0057] The present disclosure can provide a subscription and push service for related perception services and perception services based on the perception capability of the base station without terminals and led by the perception function network element SF. BRIEF DESCRIPTION OF THE DRAWINGS
[0058] In order to more clearly illustrate the embodiments of the present disclosure or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.
[0059] Figure 1 Schematic diagram of some embodiments of the service perception method disclosed in the present invention.
[0060] Figure 2 The present invention is a schematic diagram of the design of scenes and base stations in some embodiments of the present invention.
[0061] Figure 3 Schematic diagrams of other embodiments of the service perception method disclosed in the present invention.
[0062] Figure 4 The present invention is a schematic diagram of some embodiments of the perception function network element.
[0063] Figure 5 It is a schematic diagram of the structure of other embodiments of the perception function network element disclosed in the present invention.
[0064] Figure 6 The following is a schematic diagram of some embodiments of the core network device disclosed in the present invention. DETAILED DESCRIPTION
[0065] The technical solutions in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the drawings in the embodiments of the present disclosure. Obviously, the described embodiments are only part of the embodiments of the present disclosure, rather than all of the embodiments. The following description of at least one exemplary embodiment is actually only illustrative and is by no means intended to limit the present disclosure and its application or use. Based on the embodiments in the present disclosure, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present disclosure.
[0066] Unless specifically stated otherwise, the relative arrangement of components and steps, the numerical expressions and numerical values set forth in these embodiments do not limit the scope of the present disclosure.
[0067] At the same time, it should be understood that for the convenience of description, the sizes of the various parts shown in the drawings are not drawn according to the actual proportional relationship.
[0068] Technologies, methods, and apparatus known to ordinary technicians in the relevant field may not be discussed in detail, but where appropriate, such technologies, methods, and apparatus should be considered part of the authorization specification.
[0069] In all examples shown and discussed herein, any specific values should be interpreted as merely exemplary and not as limiting. Therefore, other examples of the exemplary embodiments may have different values.
[0070] It should be noted that like reference numerals and letters refer to similar items in the following figures, and therefore, once an item is defined in one figure, it need not be further discussed in subsequent figures.
[0071] The inventors have found through research that in the research of network perception-related technologies and services, in addition to the traditional perception services based on perception terminals, there is also a new type of terminal-free perception service based on base station perception capabilities. In this service, precisely because there is no terminal participation, the core network will design this type of service completely differently. Although the base station is similar to the terminal as the subject of performing perception operations, considering that the base station is completely different from the terminal due to its own positioning and design basis for the network itself, its access and management on the network side cannot directly copy the specifications designed for the terminal.
[0072] At the same time, since many services in related technologies are established by the network side and the terminal or the application function AF and the terminal to establish a connection and session, and then the network side performs related access management and data transmission services. Without the participation of the terminal, the network side will not open the relevant detailed information of the base station to the third-party AF, and the third-party AF cannot directly establish a session with the base station to transmit data. Therefore, how to let the base station execute the perception request sent by the application function AF related to the third-party perception service and transmit the data back to the AF is a difficulty in existing research.
[0073] In addition, due to the extremely large amount of data in related technical perception services and the large number of third-party application functions AF, in addition to the compression and processing of data being the existing research difficulties, how to reasonably arrange and provide different types of perception services for third-party AF to avoid short-term excessive network load is also a difficulty in the design of perception services.
[0074] In view of at least one of the above technical problems, the present disclosure provides a perception service method and system, a perception function network element, a core network and a storage medium. The present disclosure is explained below through specific embodiments.
[0075] Figure 1 Schematic diagram of some embodiments of the perception service method disclosed in the present invention. Preferably, this embodiment can be executed by the perception function network element or core network device of the present invention or the perception service system of the present invention. 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 perception function network element receives a perception data subscription request sent by an application function server, wherein the perception data subscription request includes subscription scenario information.
[0077] In some embodiments of the present disclosure, step 100 may include at least one of steps 110 to 120, wherein:
[0078] Step 110, the perception function network element receives the subscription configuration file sent by the policy control function network element, wherein the subscription configuration file is generated by the policy control function network element based on subscription request data, and the subscription request data is included in the perception data subscription request sent by the application function server to the policy control function network element via NEF (Network Exposure Function), and the subscription request data also includes the identification information of the application function server and at least one of the perception data types that need to be subscribed.
[0079] In some embodiments of the present disclosure, a specific perception scenario is defined by a perception service application function server AF, which sends the scenario information and perception data type that need to be subscribed to to the perception function network element SF. After receiving the configuration file of the subscription request, the perception function network element SF confirms the base stations corresponding to the specific subscribed perception scenarios and perception data types, and then establishes an exclusive scenario ID for each perception scenario. Then, all base station IDs corresponding to each scenario are bound to the scenario ID and updated to the subscription configuration file.
[0080] In some embodiments of the present disclosure, the scene information requested by AF includes: location information of the center of the scene, and the range of the scene (radius or length, width, height, etc.).
[0081] Figure 2 Schematic diagram of the design of scenes and base stations in some embodiments of the present disclosure. Figure 2 As shown, each dotted circle represents a perception scenario defined by an AF based on actual perception service requirements. Since the AF cannot determine whether there will be or which base stations in the scenario have the perception capability to obtain perception data, the AF only needs to report the location information and spatial information of the requested perception scenario and the corresponding perception requirements to the network. The corresponding perception capability base stations in the specific scenario and the perception capabilities they have are determined by the network side.
[0082] Step 120: The perception function network element receives a registration table update request sent by a PCF (Policy Control Function), wherein the registration table update request includes the subscription request data.
[0083] Step 200: The perception function network element allocates an exclusive scenario identifier to the subscription scenario information.
[0084] In some embodiments of the present disclosure, step 200 may include: the perception function network element updates the first subscription registration table according to the subscription request data, wherein the first subscription registration table is a subscription registration table on the perception function network element side; the first subscription registration table includes the identification information of the application function server, the subscription requirements of the application function server, the recorded base station information with perception capabilities, and at least one of the types of data that can be perceptibly obtained, wherein the subscription requirements include subscription scenario information, the binding relationship between the scenario identifier and the base station identifier, the type of perception data that needs to be subscribed, and at least one of the data volume and data timeliness.
[0085] In some embodiments of the present 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 of the base stations with sensing capabilities and the type of sensing data.
[0087] Step 220: Create a separate scenario identifier for each subscription scenario.
[0088] In some embodiments of the present disclosure, each scene, regardless of size, will be assigned a unique scene ID by the SF.
[0089] Step 230: Bind or update the corresponding base station identifier with perception capability for each scene identifier, and generate a binding relationship between the scene identifier and the base station identifier.
[0090] In some embodiments of the present disclosure, each scene ID may include one or more base station IDs, and the allocation of the corresponding base station ID to the scene ID is determined by the SF based on the recorded base stations with perception capabilities and the location information of the base stations.
[0091] In some embodiments of the present disclosure, each base station ID may correspond to one or more scene IDs, and the specific corresponding information is maintained by the SF.
[0092] Step 240: Generate a binding relationship between the scene identifier and the identifier of the perception function network element.
[0093] In some embodiments of the present disclosure, each scenario ID may correspond to one or more AF IDs after being established (if multiple AFs request the same scenario).
[0094] Step 300: The perception function network element determines the perception capability base stations existing in the perception scenario.
[0095] Step 400: The perception function network element performs relevant perception request operations on the perception capability base station.
[0096] In some embodiments of the present disclosure, step 400 may include at least one of steps 410 to 420, wherein:
[0097] Step 410: The sensing function network element periodically sends a sensing request 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 the present disclosure, step 410 may include at least one of steps 411 to 413, wherein:
[0099] Step 411, the perception function network element generates a perception service trigger table according to the requirements for data timeliness and time nodes of the perception service in the subscription configuration file, wherein the perception 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.
[0100] Step 412: The perception function network element determines the identification information of the application function server corresponding to the time at a fixed time node or according to a predetermined time period according to the perception service trigger table, 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.
[0101] Step 413: The perception function network element sends a perception request to the base station corresponding to the scene, requesting the base station to perform a perception operation and obtain perception data.
[0102] Step 420: After collecting and processing the perception data, the perception function network element pushes the perception data to the application function server.
[0103] In some embodiments of the present disclosure, in step 420, the step of collecting and processing the perception data by the perception function network element may include: after receiving the perception data reported by the base station, the perception function network element performs relevant processing on the perception data, wherein the relevant processing includes at least one of integrity check, sensitive information check, data quality check, data screening and data compression.
[0104] In some embodiments of the present disclosure, in step 420, the step of pushing the perception data to the application function server may include: the perception function network element pushes the perception data to the network open function network element, so that the network open function network element pushes the perception data to the application function server when receiving the push configuration file sent by the policy management function network element and the perception data initiated by the perception function network element.
[0105] In some embodiments of the present disclosure, the perception service method may further include: the perception function network element reports the relevant information of the scene identifier to the policy management function network element for updating the second subscription registration table, 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 perception function network element, wherein the second subscription registration table is a subscription registration table on the policy management function network element side, and the first subscription registration table includes the identification information of the application function server, the subscription scenario information, and the perception function network element covered by the subscription scenario.
[0106] In some embodiments of the present disclosure, the perception service method may further include: after the perception function network element reports the 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 a push time node or time period and a push range, and the policy management function network element responds to the push configuration file request and simultaneously issues an updated push configuration file to the perception function network element and the network open function network element.
[0107] In some embodiments of the present disclosure, the perception service method may further include: the perception function network element determines whether the data already stored in the perception function network element includes the perception data required by the application function server; if the data already stored in the perception function network element includes the perception data required by the application function server, the perception data is pushed to the application function server; if the data already stored in the perception function network element does not include the perception data required by the application function server, the perception function network element is triggered to execute the operation of sending a perception request to the base station for the first time, requesting the base station to obtain the perception data related to the requirement.
[0108] The above-mentioned embodiment of the present disclosure provides a subscription push service method of a perception function network element of a base station perception capability.
[0109] The above-mentioned embodiments of the present disclosure belong to the technical field of wireless communication and core network.
[0110] The above embodiment of the present disclosure is a subscription-based push service model designed for the perception capability of the network. Its related services and solutions are deployed in the network perception capability network element, so that the network can provide more diverse related network perception services for application function servers.
[0111] In order to better solve the design and deployment of services without terminal participation, the above embodiments of the present disclosure design a scenario-based design based on base station perception capabilities, and design a subscription push service based on scenarios. The above embodiments of the present disclosure can make the perception service more reasonably deployed by stipulating the perception objects and perception operation executors in the scenario without terminal perception, as well as data collection and push led by the network side.
[0112] Figure 3 Schematic diagram of other embodiments of the perception service method disclosed in the present invention. Preferably, this embodiment can be executed by the core network device disclosed in the present invention or the perception service system disclosed in the present invention. Figure 3 As shown, Figure 3 The method of the embodiment may include at least one of steps 1 to 18, wherein: Figure 3The perception service method of the embodiment may include a subscription registration initiation process and a process for regularly collecting perception data during subscription, wherein:
[0113] Figure 3 The subscription registration initiation process of the embodiment may include at least one step from step 1 to step 9, wherein:
[0114] Step 1: The perception service application function AF requests the network open function NEF to subscribe to the perception scene data, report the scene information of the subscribed perception service (location information of the scene center, length, width, height and other geographical location information of the scene range), report the application function ID (AF ID) and the perception data type to be subscribed. The above information is provided for the creation of the perception service.
[0115] Step 2: The network open function NEF forwards the subscription request to the policy control function network element PCF, which generates a new subscription configuration file and a push configuration file and updates the subscription push registration table on the PCF side.
[0116] Step 3: After completing the above operations, the policy control function network element PCF will send data to the perception function network element SF to update the subscription registration table (first subscription registration table) on the SF side, and at the same time send a new subscription configuration file to SF, and send the subscription scenario information of the subscriber for SF to confirm the specific base station corresponding to each scenario.
[0117] Step 4: After receiving the request from PCF, the perception function network element SF compares the recorded location information of the base stations with perception capabilities and the type of perception data, creates a separate scene ID for each scene, and binds or updates the corresponding base station ID with perception capabilities for each scene ID. Then, the binding information of the generated scene ID and the base station ID and the binding information of the scene ID and the ID of the perception function network element (SF ID) are reported to the policy management function network element PCF to update the subscription registration table (second subscription registration table) on the PCF side.
[0118] Step 5: After reporting the relevant information of the scenario 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 step 6 and step 8, PCF updates the corresponding push configuration file after updating the new scene ID and related corresponding information. After receiving the push configuration file request sent by SF, PCF will send the updated push configuration file to SF and NEF at the same time.
[0120] In some embodiments of the present disclosure, the push configuration file sent to the SF side is saved by the SF, and the SF will keep saving and updating the configuration file before the subscription is cancelled.
[0121] In some embodiments of the present disclosure, the push configuration file sent to NEF will not be saved on the NEF side in consideration of the capabilities of the NEF network element, so the push configuration file on the NEF side is one-time and valid only once, so each subsequent push requires the PCF to send a new push configuration file to the NEF and then the NEF pushes the data.
[0122] Step 7: After receiving the push configuration file, the perception function network element SF checks the existing data, triggers the first data collection, and packages the collected data and sends it to the network open function network element NEF.
[0123] In some embodiments of the present disclosure, step 7 may include: the perception function network element determines whether the data already stored in the perception function network element includes the perception data required by the application function server; if the data already stored in the perception function network element includes the perception data required by the application function server, the perception data is pushed to the application function server through NEF; if the data already stored in the perception function network element does not include the perception data required by the application function server, the first data collection is triggered, triggering the perception function network element to execute the operation of sending a perception request to the base station for the first time, requesting the base station to obtain the perception data related to the requirement, that is, executing the process of regularly collecting perception data during the subscription period of steps 11 to 18 for the first time.
[0124] Step 9: After receiving the first perception data packet and the push configuration file, the network open function NEF pushes the perception data to the corresponding subscriber, that is, the application function AF of this perception service, according to the description of the configuration file.
[0125] Figure 3 The process of periodically collecting perception data during the subscription period of the embodiment may include at least one step from step 11 to step 18, wherein:
[0126] Step 11: Every time a sensing service application function AF initiates a subscription push service registration, the sensing function network element SF will update the stored "sensing service trigger table". The trigger table stores the subscriber ID that needs to execute the sensing service and the relevant data timeliness requirements and time node or time period requirements.
[0127] Step 12, when the trigger table triggers the perception operation according to the time requirements in the table, the perception function network element SF determines the specific scene ID according to the subscriber AF ID corresponding to the time on the trigger table, and sends a perception request to the base station corresponding to this scene according to the matching information in SF.
[0128] Step 13: After receiving a request from the sensing function network element SF, the sensing base station (Sensing Base Station, RAN) with sensing capability performs a sensing operation to obtain sensing data.
[0129] In some embodiments of the present disclosure, Figure 3 As shown, the sensing capability base station performs sensing operations and obtains sensing data from sensing objects (Sensing Objects) or sensing scenes (Sensing Scenarios).
[0130] In some embodiments of the present disclosure, the sensing object may be a sensing target such as a vehicle or a person. The step of acquiring sensing data from the sensing object may include: acquiring sensing data from a sensing target such as a vehicle or a person.
[0131] In some other embodiments of the present disclosure, the step of acquiring the perception data from the perception scene may include acquiring sensing parameters in the sensing scene such as temperature and humidity from the perception scene.
[0132] Step 14: The base station with sensing capability uploads the received sensing data to the SF.
[0133] In step 15 and step 17, after receiving the sensing data reported by the base station, the sensing function network element SF will perform relevant operations and processing (integrity check, sensitive information check, data quality check, data screening, data compression, etc.) on the data and then send the data to NEF. At the same time, SF will also send a request to PCF to prompt that this sensing operation has been completed, report the subscriber (AF ID) corresponding to this sensing operation, and request PCF to send a push file to NEF according to the subscriber information.
[0134] Step 16: After receiving the request, the policy control function network element PCF sends 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 sent by the PCF and the perception data packet sent by the SF, the network open function NEF pushes the perception data packet to the corresponding subscriber according to the actual requirements of the push configuration file.
[0136] Related technologies: The current 3GPP main architecture and services are mainly designed for terminals with active communication capabilities. The above embodiments of the present disclosure are designed for terminal-free scenarios included in new perception services, that is, services based on base station perception capabilities, so that perception services can be performed without terminal participation.
[0137] The above-mentioned embodiments of the present disclosure design a subscription push service design with perception network element as the core, and the perception network element actively provides related services on the premise of meeting the perception service requirements of the third-party AF, thereby avoiding two problems: base station information cannot be opened to the third-party AF and it may be necessary to establish a direct connection and session between the AF and the base station.
[0138] The above embodiments of the present disclosure directly deploy interfaces between the perception function network element SF and the base station (RAN), thereby avoiding the problem that the N1 port cannot be used without a terminal and the base station needs to transmit a large amount of original perception data, which may cause a huge transmission load on the N2 and N3 ports.
[0139] Related technology In the traditional business model, the third-party AF generally provides relevant terminal information or the terminal actively initiates a request and the network side establishes the corresponding connection and session for it. However, in a terminal-free scenario, the third-party AF does not know the information of the base station, and the network does not open the base station information to the AF or establish a connection from the AF to the base station. The above-mentioned embodiment of the present disclosure takes the perception function network element as the core, and directly interacts with the base station through the perception function network element to perform perception operations and collect perception data, so as to meet the needs of the third-party AF as much as possible on the basis of avoiding the disclosure of base station related information, and avoids a large number of session establishment and data transmission.
[0140] Because the third-party AF cannot establish a direct connection with the base station according to the related technology, and in order to avoid congestion between the AF and the network due to a large number of AFs sending requests to the network in a short period of time, the above-mentioned embodiment of the present invention designs a service model based on subscription push of perception function network elements. In this mode, the AF only needs to register, report or update the corresponding requirements, and the network side can provide the AF with relevant data and business services for a long time, thereby avoiding congestion and waste of network resources caused by the AF frequently sending requests to the network due to its own business needs.
[0141] Figure 4 Schematic diagram of some embodiments of the perception function network element disclosed in the present invention. Figure 4 As shown, the perception function network element of the present disclosure may include a request receiving module 41, a scene identification allocation module 42, a perception base station determination module 43 and a perception request module 44, wherein:
[0142] The request receiving module 41 is configured to receive, as a perception function network element, a perception data subscription request sent by an application function server, wherein the perception data subscription request includes subscription scenario information.
[0143] In some embodiments of the present disclosure, the request receiving module 41 can be configured to receive a subscription profile sent by a policy control function network element by a perception function network element, wherein the subscription profile is generated by the policy control function network element based on subscription request data, and the subscription request data is 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, and the subscription request data also includes identification information of the application function server and at least one of the types of perception data that need to be subscribed; 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 scenario identifier allocation module 42 is configured to allocate a dedicated scenario identifier to the subscribed scenario information.
[0145] In some embodiments of the present disclosure, the scenario identifier allocation module 42 can be configured to update a first subscription registration table according to the subscription request data, wherein the first subscription registration table is a subscription registration table on the perception function network element side; the first subscription registration table includes identification information of the application function server, subscription requirements of the application function server, recorded base station information with perception capabilities, and at least one of the types of data that can be perceptibly obtained, wherein the subscription requirements include subscription scenario information, a binding relationship between a scenario identifier and a base station identifier, the type of perception data that needs to be subscribed, data volume, and at least one of data timeliness.
[0146] In some embodiments of the present disclosure, the scenario identifier allocation module 42 can be configured to compare the subscription request data with the recorded location information of the base station with perception capability and the type of perception data when updating the first subscription registration table according to the subscription request data; create a scenario identifier for each subscription scenario separately; bind or update the corresponding base station identifier with perception capability for each scenario identifier, and generate a binding relationship between the scenario identifier and the base station identifier; generate a binding relationship between the scenario identifier and the identifier of the perception function network element.
[0147] The perception base station determination module 43 is configured to determine the perception-capable base stations existing in the perception 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 the present disclosure, the perception request module 44 can be configured to, when performing a perception request operation on the perception capability base station, periodically send a perception request to the base station according to the requirements in the subscription profile, 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 the present disclosure, the perception request module 44 can be configured to perform relevant processing on the perception data after receiving the perception data reported by the base station while collecting and processing the perception data, wherein the relevant processing includes at least one of integrity check, sensitive information check, data quality check, data screening and data compression.
[0151] In some embodiments of the present disclosure, the perception request module 44 can be configured to push the perception data to the network open function network element when the perception data is pushed to the application function server, so that the network open function network element pushes the perception data to the application function server when receiving the push configuration file sent by the policy management function network element and the perception data initiated by the perception function network element.
[0152] In some embodiments of the present disclosure, the perception request module 44 can be configured to generate a perception service trigger table according to the requirements for data timeliness and time nodes of the perception service in the subscription profile, when periodically sending perception requests to the base station according to the requirements in the subscription profile and requesting the base station to obtain perception data related to the requirements, wherein the perception 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; according to the perception service trigger table, at a fixed time node or according to a predetermined time period, determine the identification information of the application function server corresponding to the time, determine the scene identifier according to the identification information of the application function server, and determine the corresponding base station identifier according to the scene identifier; send a perception request to the base station corresponding to the scene, requesting the base station to perform a perception operation and obtain perception data.
[0153] In some embodiments of the present disclosure, the perception function network element may also be configured to report relevant information of the scenario identifier to the policy management function network element for updating a second subscription registration table, wherein the relevant information of the scenario identifier includes a binding relationship between the scenario identifier and the base station identifier, and a binding relationship between the scenario identifier and the identifier of the perception function network element, wherein the second subscription registration table is a subscription registration table on the policy management function network element side, and the first subscription registration table includes identification information of the application function server, subscription scenario information, and perception function network elements covered by the subscription scenario.
[0154] In some embodiments of the present disclosure, the perception function network element can also be configured to send a push configuration file request to the policy management function network element after reporting the relevant information of the scenario 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 a push time node or time period and a push range, and the policy management function network element responds to the push configuration file request and simultaneously issues an updated push configuration file to the perception function network element and the network open function network element.
[0155] In some embodiments of the present disclosure, the perception function network element may also be configured to determine whether the data already stored in the perception function network element includes the perception data required by the application function server; if the data already stored in the perception function network element includes the perception data required by the application function server, push the perception data to the application function server; if the data already stored in the perception function network element does not include the perception data required by the application function server, trigger the perception function network element to execute the operation of sending a perception request to the base station for the first time, requesting the base station to obtain the perception data related to the requirement.
[0156] In some embodiments of the present disclosure, the perception function network element of the present disclosure may also be configured to execute the above embodiments of the present disclosure (for example Figure 1 Example Figure 3 The perception service method described in any one of steps 2 to 7, steps 11 to 12, steps 14 to 15, and step 17 of the embodiment.
[0157] Figure 5 FIG. 1 is a schematic diagram of the structure of some other embodiments of the perception function network element disclosed in the present invention. Figure 5 As shown, the perception function network element includes a memory 51 and a processor 52.
[0158] The memory 51 is used to store instructions. The processor 52 is coupled to the memory 51. The processor 52 is configured to execute the above embodiments of the present disclosure (for example, Figure 1 Example Figure 3 The perception service method described in any one of steps 2 to 7, steps 11 to 12, steps 14 to 15, and step 17 of the embodiment.
[0159] like Figure 5 As shown, the perception function network element further includes a communication interface 53 for information exchange with other devices. At the same time, the perception function network element further includes a bus 54, through which the processor 52, the communication interface 53, and the memory 51 communicate with each other.
[0160] The memory 51 may include a high-speed RAM memory, and may also include a non-volatile memory, such as at least one disk memory. 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] In addition, the processor 52 may be a central processing unit (CPU), or may be an application specific integrated circuit (ASIC), or may be configured to implement one or more integrated circuits of the embodiments of the present disclosure.
[0162] In scenarios where large-scale perception terminals are deployed and there are fixed perception service application functions AF, the service mode of the above embodiments of the present disclosure can be deployed, such as hospitals, schools, storage centers, department stores, large stations, etc. Since the above embodiments of the present disclosure are mainly aimed at perception services without terminal perception, that is, based on the perception capabilities of base stations, relevant service providers of the scenarios, such as hospitals, schools, governments, etc., can subscribe to the perception services of the relevant scenarios and the required perception data from the operator in outdoor and indoor scenarios. The operator performs perception operations on demand through the base stations deployed on the ground to collect perception data and provide customizable perception services for the relevant subscribers.
[0163] The technical effect of the above-mentioned embodiments of the present disclosure is that as the demand for perception services becomes higher and higher in the future, the demand for networks will also become higher and higher. Although a large amount of perception data puts higher requirements on the network load and data processing capabilities on the one hand, it can also bring huge commercial value on the other hand. A large amount of original perception data can enable the network to provide more and richer data services to third-party service providers, thereby significantly increasing the size of the market.
[0164] With the emergence of many new terminal-free scenarios in the future, there will be more and more scenario-based services, and many scenarios will include both terminal services and base station services. The service design and customized scenario-based design proposed in the above embodiments of the present disclosure may be gradually applied to more services in the future as various new businesses emerge.
[0165] Figure 6 The following is a schematic diagram of some embodiments of the core network device disclosed in the present invention. Figure 3 Also provided are schematic diagrams of some embodiments of the core network device of the present disclosure. Figure 3 and Figure 6 As shown, the core network device of the present disclosure may include a perception function network element (SF) 61, wherein:
[0166] The sensing function network element 61 may be any one of the above embodiments (for example Figure 4 or Figure 5 The perception function network element described in the embodiment).
[0167] In some embodiments of the present disclosure, the perception function network element 61 can be configured to be responsible for managing the network-related perception capabilities, and to manage and process the corresponding perception functions, perception operations, and perception data of the base stations with perception capabilities recorded on the network side. In this system, this network element mainly manages the recorded base stations with perception capabilities and the related perception services and perception operations, and collects the related perception data. The perception function network element 61 also has the function of storing the related perception data and performing related processing on it.
[0168] In some embodiments of the present disclosure, the perception function network element 61 can also be configured to maintain a registry for subscription push services, and the contents of the registry mainly include: the registered AF (AF ID), the subscription requirements of the registered AF (scenario information, scenario ID and base station ID, data type, data volume, data timeliness, etc.), the recorded base station information with perception capabilities, and the data type that can be perceived and obtained. Finally, the perception function network element SF also has a perception service trigger table, which is generated according to the requirements for data timeliness and the time node of the perception service in the subscription configuration file. The content of this service trigger table is: subscriber AF ID + data collection time node or time period required by this subscriber. The subsequent data collection and data push is that SF collects relevant perception data and pushes data according to this service trigger table.
[0169] In some embodiments of the present disclosure, the perception function network element SF is designed to be distributedly deployed in the system, that is, there will be multiple sub-perception function network elements SF in the system, which are respectively connected to different single or multiple base stations.
[0170] In some embodiments of the present disclosure, Figure 3 and Figure 6 As shown, the core network device of the present disclosure may include a policy control function network element (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 to the policy control function network element through the network open function network element, wherein the perception data subscription request includes subscription request data, and the subscription request data includes subscription scenario information, identification information of the application function server and at least one of the perception data types that need to be subscribed; generate a subscription configuration file according to the subscription request data; determine the perception function network element corresponding to the subscription scenario information according to the correspondence between the protection scenario information and the perception function network element; and send the subscription request data and the subscription configuration file to the perception function network element corresponding to the subscription scenario information.
[0172] In some embodiments of the present disclosure, the policy control function network element 62 can be configured to be mainly responsible for maintaining a subscription registry and a corresponding subscription configuration file in this system. The contents of the subscription registry are: the AF (AFID) of the registered subscription, the subscribed scene information (location information and scene ID), and the subscribed perception network element (SFID) covered by the subscribed perception scene.
[0173] In some embodiments of the present disclosure, Figure 3 and Figure 6 As shown, the core network device of the present disclosure may include a network open function network element (NEF) 63, wherein:
[0174] The network open function network 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 sent by the policy control function network element and the perception data packet sent by the perception function network element.
[0175] In some embodiments of the present disclosure, the policy control function network element 62 may be configured to forward relevant subscription data, perform relevant integrity and data quality (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 in the present invention are also given. Figure 3 Also provided are schematic diagrams of some embodiments of the perception service system disclosed herein. Figure 3 and Figure 6 As shown, the perception service system disclosed in the present invention may include a core network device as described in any of the above embodiments.
[0177] In some embodiments of the present disclosure, Figure 3 and Figure 6 As shown, the perception service system may further include an application function server (AF) 64, wherein:
[0178] The application function server 64 is configured to send a perception data subscription request to a core network device, wherein the perception data subscription request includes subscription request data, and the subscription request data includes subscription scenario information, identification information of the application function server and at least one of the types of perception data that need to be subscribed, and the scenario is a geographical scope or spatial scope in which perception operations need to be performed based on a single or multiple base stations.
[0179] In some embodiments of the present disclosure, the application function server 64, which in this system is mainly a capability module or server accessed by a third party for perception services, can be configured to obtain relevant perception terminal information and perception data after registering and subscribing to the perception function network element on the core network side, and use the subscribed perception data to deploy related services according to its own business needs.
[0180] In some embodiments of the present disclosure, Figure 3 and Figure 6 As shown, the sensing service system may further include a sensing capability base station (Sensing Base Station, RAN) 65, wherein:
[0181] The sensing capability base station 65 is configured to perform a sensing operation after receiving a sensing request from a sensing function network element in a core network device, and then upload the received sensing data to the sensing function network element.
[0182] In some embodiments of the present disclosure, Figure 3 and Figure 6 As shown, the sensing capability base station 65 performs sensing operations and obtains sensing data from sensing objects (Sensing Objects) or sensing scenes (Sensing Scenarios).
[0183] In some embodiments of the present disclosure, the sensing object may be a sensing target such as a vehicle or a person. The step of acquiring sensing data from the sensing object may include: acquiring sensing data from a sensing target such as a vehicle or a person.
[0184] In some other embodiments of the present disclosure, the step of acquiring the perception data from the perception scene may include acquiring sensing parameters in the sensing scene such as temperature and humidity from the perception scene.
[0185] In some embodiments of the present disclosure, Figure 3 and Figure 6 As shown in FIG. 1 , the sensing function network element SF adds three main interfaces: the interface between SF and the base station (RAN), the interface between SF and the PCF, and the interface between SF and the NEF, among which:
[0186] SF and NEF interface: mainly used to transmit the perception data collected and processed by SF.
[0187] SF and PCF interface: mainly used to transmit the update registry request and configuration file issued by PCF, and also transmit the update registry request and push request sent by SF.
[0188] SF and base station (RAN) interface: mainly used for the base station to transmit raw perception data to the perception function network element SF.
[0189] In some embodiments of the present disclosure, the SF and the base station (RAN) interface is mainly because in the non-terminal perception scenario, the base station performs the perception operation. In the absence of terminal participation, the existing N1 and N2 interfaces will no longer be applicable. Even if the N2 interface is expanded, considering that the amount of perception data is extremely large, it will cause great transmission pressure on the N2 interface. It is a more appropriate solution to create a new interface between the perception function network element and the base station (RAN) for transmitting the original perception data.
[0190] The above-mentioned embodiment of the present disclosure is a perception business service mode designed based on the perception function of the core network.
[0191] The above-mentioned embodiments of the present disclosure are mainly designed for a perception business service mode of a base station with perception capability.
[0192] The above-mentioned embodiments of the present disclosure propose a scenario-based solution, that is, the third-party AF describes the required perception service requirements by reporting the scenario information in which the perception operation needs to be performed.
[0193] In some embodiments of the present disclosure, a scenario is a geographical range or spatial range where a sensing operation needs to be performed based on a single or multiple base stations.
[0194] In some embodiments of the present disclosure, the core network perception function SF is mainly responsible for the management and execution of the subscription push service.
[0195] In some embodiments of the present 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 corresponding information between the perception scene and the sub-perception function network element).
[0196] In some embodiments of the present disclosure, the core network policy control function PCF is mainly responsible for maintaining the configuration files of the base stations with perception capabilities.
[0197] In some embodiments of the present disclosure, the core network policy control function PCF is mainly responsible for maintaining a subscription registry, the contents of which are: the registered subscribed AF (AF ID), the subscribed scene information (location information and scene ID), and the sub-perception network element (SF ID) covered by the subscribed perception scene.
[0198] In some embodiments of the present disclosure, the core network policy control function PCF is mainly responsible for maintaining the push configuration file.
[0199] In some embodiments of the present disclosure, the core network perception function SF protects the registration table of the subscription push service, and the contents of the registration table mainly include: the registered subscribed AF (AF ID), the subscription requirements of the registered subscribed AF (scenario information, scenario ID and base station ID, data type, data volume, data timeliness, etc.), the recorded base station information with perception capability and the data type that can be perceived and obtained.
[0200] In some embodiments of the present disclosure, the perception function network element SF maintains a perception service trigger table, which is generated according to the requirements of the subscription configuration file for data timeliness and the time node of the perception service. The content of this service trigger table is: subscriber AF ID + data collection time node or time period required by this subscriber.
[0201] In some embodiments of the present disclosure, the sensing function network element SF has three interfaces with the base station, the policy control function PCF, and the network capability exposure NEF.
[0202] The above-mentioned embodiments of the present disclosure design a set of process specifications for this subscription push service.
[0203] The present disclosure provides a terminal-free perception service system, in which the application function server AF registers for subscription push services to the policy control function network element PCF and the perception function network element SF through the network open function network element NEF. The information of base stations with perception capabilities will be recorded in the perception function network element SF. At the same time, when the perception service is executed, it will send requests and collect data according to the specific recorded scenarios and base stations. After the perception service application server AF is registered with the perception function network element SF, PCF will synchronously send a specific subscription configuration file to the perception function network element SF. After that, the perception function network element will regularly request the base station side to obtain relevant perception data according to the requirements in the subscription configuration file, and push the collected and processed perception data to the subscriber's perception service application function AF.
[0204] Based on the technical problems of related technologies, the above embodiments of the present disclosure design a service based on terminal-free, base station perception capability, and dominated by the perception network element SF for subscription and push of related perception services and perception services. The above embodiments of the present disclosure, on the basis of setting up a perception function network element on the core network side, deploy a new interface between the perception function network element SF and the base station (RAN), so that the service execution based on the perception capability of the base station can bypass the existing N1, N2, N3 interfaces and functional network elements such as AMF, UPF, SMF, and directly transmit perception data to the perception function network element SF.
[0205] At the same time, the above-mentioned embodiments of the present disclosure convert the terminal-based perception service design into a scenario-based perception service, and perform specialized processing on the scenarios reported by the third-party application function AF. After assigning a separate ID to each scenario, the perception operation and perception service are performed based on each scenario ID. That is, in the traditional mode, the perception function network element SF performs perception operations and perception services based on each perception terminal, but in the scenario-based mode, the perception service based on the base station perception capability does not use a single base station as the unit of the perception service, but performs the perception service based on each unique scenario and all base stations with perception capabilities contained in this scenario. This avoids the problem that the base station information cannot be opened to the third-party AF.
[0206] Finally, in order to avoid the problem of excessive data volume and excessive load caused by establishing a direct connection between AF and the base station and a large number of sessions. The above embodiment of the present disclosure designs a subscription push service mode based on the perception function network element, so that the SF on the network side can grasp the service dominance of some perception services, avoiding the need for the network to directly establish a connection and session between AF and a single base station in a perception scenario without a terminal. At the same time, since SF is on the core network side, it can know the actual load of the network, and actively adjust the data processing and transmission of the perception service according to the actual load of the network, so that the services with lower timeliness or data requirements and higher services can be flexibly fine-tuned.
[0207] According to another aspect of the present disclosure, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores computer instructions, and when the instructions are executed by a processor, any of the above embodiments (for example Figure 1 or Figure 3 The perception service method described in the embodiment).
[0208] In some embodiments of the present disclosure, the computer-readable storage medium may be a non-transitory computer-readable storage medium.
[0209] Those skilled in the art will appreciate that the embodiments of the present disclosure may be provided as methods, devices, or computer program products. Therefore, the present disclosure may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present disclosure may take the form of a computer program product implemented on one or more computer-usable non-transient storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.
[0210] The present disclosure is described with reference to flowcharts and / or block diagrams of methods, devices (systems) and computer program products according to embodiments of the present disclosure. It should be understood that each process and / or block in the flowchart and / or block diagram and the combination of processes and / or blocks in the flowchart and / or block diagram can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.
[0211] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.
[0212] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process in the computer or other programmable device. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.
[0213] The perception function network element, request receiving module, scene identification allocation module, perception base station determination module, perception request module, network open function network element, policy control function network element, core network equipment, perception service system, application function server and perception capability base station described above can be implemented as a general-purpose processor, programmable logic controller (PLC), digital signal processor (DSP), application-specific integrated circuit (ASIC), field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component or any appropriate combination thereof for performing the functions described in this application.
[0214] So far, the present disclosure has been described in detail. In order to avoid obscuring the concept of the present disclosure, some details known in the art are not described. Based on the above description, those skilled in the art can fully understand how to implement the technical solution disclosed here.
[0215] A person skilled in the art will understand that all or part of the steps to implement the above embodiments may be accomplished by hardware, or may be accomplished by instructing the relevant hardware through a program, and the program may be stored in a non-transitory computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a disk or an optical disk, etc.
[0216] The description of the present disclosure is given for the purpose of illustration and description, and is not intended to be exhaustive or to limit the present disclosure to the disclosed form. Many modifications and variations will be apparent to those of ordinary skill in the art. The embodiments are selected and described in order to better illustrate the principles and practical applications of the present disclosure, and to enable those of ordinary skill in the art to understand the present disclosure and thereby design various embodiments with various modifications suitable for specific uses.
Claims
1. A sensing service method, comprising: The perception function network element receives a perception data subscription request sent by the application function server, wherein the perception data subscription request includes subscription scenario information; The perception function network element allocates an exclusive scenario identifier for the subscription scenario information; The perception function network element determines the perception capability base stations existing in the perception scenario; The perception function network element executes relevant perception request operations for the perception capability base station.
2. The sensing service method according to claim 1, wherein: The receiving, by the perception function network element, of a perception data subscription request sent by the application function server includes: The perception function network element receives a subscription configuration file sent by the 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 included in the perception data subscription request sent by the application function server to the policy control function network element through the network open function network element, and the subscription request data also includes at least one of identification information of the application function server and the type of perception data to be subscribed; The perception function network element receives a registration table update request sent by the policy control function network element, wherein the registration table update request includes the subscription request data.
3. The sensing service method according to claim 2, wherein: The sensing function network element allocating a dedicated scenario identifier for the subscription scenario information includes: The perception function network element updates the first subscription registration table according to the subscription request data, wherein the first subscription registration table is the subscription registration table on the perception function network element side; the first subscription registration table includes the identification information of the application function server, the subscription requirements of the application function server, the recorded base station information with perception capabilities, and at least one of the types of data that can be perceived and obtained, wherein the subscription requirements include subscription scenario information, the binding relationship between the scenario identifier and the base station identifier, the type of perception data that needs to be subscribed, and at least one of the data volume and data timeliness.
4. The sensing service method according to claim 3, wherein: The perception function network element updates the first subscription registration table according to the subscription request data, including: Comparing the subscription request data with the recorded location information of the base station with sensing capability and the type of sensing data; Create a separate scenario ID for each subscription scenario; Bind or update the corresponding base station identifier with perception capability for each scene identifier, and generate a binding relationship between the scene identifier and the base station identifier; Generate a binding relationship between the scene identifier and the identifier of the perception function network element.
5. The sensing service method according to claim 4 further comprises: The perception function network element reports the relevant information of the scene identifier to the policy management function network element for updating the second subscription registration table, 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 perception function network element. The second subscription registration table is the subscription registration table on the policy management function network element side, and the first subscription registration table includes the identification information of the application function server, the subscription scene information, and the perception function network elements covered by the subscription scene.
6. The sensing service method according to claim 5, further comprising: After reporting the relevant information of the scenario identifier to the policy management function network element, the perception function network element sends a configuration file push request to the policy management function network element; The perception function network element receives a push configuration file issued by the policy management function network element, wherein the push configuration file includes at least one of a push time node or time period and a push range. The policy management function network element responds to the push configuration file request and simultaneously issues an updated push configuration file to the perception function network element and the network open function network element.
7. The sensing service method according to claim 6, further comprising: The perception function network element determines whether the data stored in the perception function network element includes the perception data required by the application function server; In the case where the data already stored in the perception function network element includes the perception data required by the application function server, pushing the perception data to the application function server; In the case that the data already stored in the perception function network element does not include the perception data required by the application function server, the perception function network element is triggered to execute the operation of sending a perception request to the base station for the first time to request the base station to obtain the perception data related to the requirement.
8. The sensing service method according to any one of claims 1 to 7, wherein: The sensing function network element executing the sensing request operation for the sensing capability base station includes: The sensing function network element periodically sends a sensing request 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; After collecting and processing the perception data, the perception function network element pushes the perception data to the application function server.
9. The sensing service method according to claim 8, wherein: The pushing the perception data to the application function server comprises: The perception function network element pushes the perception data to the network open function network element, so that the network open function network element pushes the perception data to the application function server when receiving the push configuration file sent by the policy management function network element and the perception data initiated by the perception function network element.
10. The sensing service method according to claim 8, wherein: The sensing function network element periodically sends a sensing request to the base station according to the requirements in the subscription configuration file, and the requesting the base station to obtain sensing data related to the requirements includes: The perception function network element generates a perception service trigger table according to the requirements for data timeliness and time nodes of the perception service in the subscription configuration file, wherein the perception service trigger table includes identification information of the application function server, and a data collection time node or time period required by the application function server; The perception function network element determines, according to the perception service trigger table, at a fixed time node or according to a predetermined time period, the identification information of the application function server corresponding to the time, 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 a perception request to the base station corresponding to the scene, requesting the base station to perform a perception operation and obtain perception data.
11. The sensing service method according to claim 8, wherein: The sensing function network element collecting and processing the sensing data includes: After receiving the perception data reported by the base station, the perception function network element performs relevant processing on the perception data, wherein the relevant processing includes at least one of integrity check, sensitive information check, data quality check, data screening and data compression.
12. A perception function network element, comprising: A request receiving module is configured to receive, by a perception function network element, a perception data subscription request sent by an application function server, wherein the perception data subscription request includes subscription scenario information; A scene identifier allocation module, configured to allocate an exclusive scene identifier to the subscribed scene information; A sensing base station determination module is configured to determine a sensing-capable base station existing in the sensing scene; The perception request module is configured to perform relevant perception request operations on the perception capability base station.
13. A perception function network element, comprising: a memory configured to store instructions; The processor is configured to execute the instruction so that the perception function network element performs the operation of implementing the perception service method according to any one of claims 1 to 11.
14. A core network device, comprising the perception function network element as claimed in claim 12 or 13.
15. The core network device according to claim 14, further comprising: A policy control function network element is configured to receive 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, wherein the perception data subscription request includes subscription request data, and the subscription request data includes subscription scenario information, identification information of the application function server and at least one of the perception data types that need to be subscribed; generate a subscription configuration file according to the subscription request data; determine the perception function network element corresponding to the subscription scenario information according to the correspondence between the protection scenario information and the perception function network element; and send the subscription request data and the subscription configuration file to the perception function network element corresponding to the subscription scenario information.
16. The core network device according to claim 14 or 15, further comprising: The network open function network 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 network element and the perception data packet sent by the perception function network element.
17. A perception service system, comprising the core network device as described in any one of claims 14 to 16.
18. The sensing service system according to claim 17, further comprising: An application function server is configured to send a perception data subscription request to a core network device, wherein the perception data subscription request includes subscription request data, and the subscription request data includes subscription scenario information, identification information of the application function server and at least one of the types of perception data that need to be subscribed, and the scenario is a geographical scope or spatial scope in which perception operations need to be performed based on a single or multiple base stations.
19. The sensing service system according to claim 17 or 18, further comprising: The perception capability base station is configured to perform a perception operation after receiving a perception request from a perception function network element in a core network device, and then upload the received perception data to the perception function network element.
20. A computer-readable storage medium, wherein: The computer-readable storage medium stores computer instructions, and when the instructions are executed by a processor, the perception service method as described in any one of claims 1-11 is implemented.
Citation Information
Patent Citations
Perception service processing method, terminal and network side equipment
CN115866635A
Sensing service providing method and apparatus, and communication device and storage medium
WO2023056648A1
Method and apparatus for providing sensing service, communication device, and storage medium
WO2023065090A1
Perception execution method and apparatus, device, and storage medium
WO2023092269A1