CN113573282B - Subscription data providing/acquiring method, providing/acquiring device and interactive system - Google Patents
Subscription data providing/acquiring method, providing/acquiring device and interactive system Download PDFInfo
- Publication number
- CN113573282B CN113573282B CN202010353912.2A CN202010353912A CN113573282B CN 113573282 B CN113573282 B CN 113573282B CN 202010353912 A CN202010353912 A CN 202010353912A CN 113573282 B CN113573282 B CN 113573282B
- Authority
- CN
- China
- Prior art keywords
- subscription
- network entity
- request
- requesting network
- information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/60—Subscription-based services using application servers or record carriers, e.g. SIM application toolkits
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/50—Service provisioning or reconfiguring
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The disclosure relates to a subscription data providing/acquiring method, a subscription data providing/acquiring device and an interaction system, and relates to the technical field of communication. The providing method comprises the following steps: generating a historical subscription list according to the historical event subscription information; in response to receiving a current subscription request sent by a second requesting network entity, judging whether matched historical event subscription information exists in a historical subscription list; sending a subscription response to the second requesting network entity, wherein the subscription response is generated according to the judgment result and is used for informing the second requesting network entity whether the matched first requesting network entity can provide corresponding subscription data; and determining whether the second requesting network entity supports obtaining subscription data from the matched first requesting network entity according to whether a re-subscription request returned by the second requesting network entity is received or not, wherein the re-subscription request is returned under the condition that the local configuration of the matched first requesting network entity and the local configuration of the second requesting network entity conflict.
Description
Technical Field
The present disclosure relates to the field of communications technologies, and in particular, to a method for providing subscription data, a method for acquiring subscription data, a device for providing subscription data, an interactive system for subscription data, and a non-volatile computer-readable storage medium.
Background
An NWDAF (Network Data analysis Function) entity is introduced into the 5G system and is used for Network Data analysis. For example, the NWDAF entity may collect data from NF (Network Function) entities of the 5G core Network to generate the analysis result. The analysis result is used for assisting the NF entity which puts forward the analysis requirement to select a relevant strategy.
In the related art, the NWDAF entity performs data acquisition separately for each network analysis requirement.
Disclosure of Invention
The inventors of the present disclosure found that the following problems exist in the above-described related art: the same data with different requirements are repeatedly collected, so that the network transmission efficiency is reduced.
In view of this, the present disclosure provides a technical solution for providing subscription data, which can improve network transmission efficiency.
According to some embodiments of the present disclosure, there is provided a method of providing subscription data, including: generating a history subscription list according to the relevant information of each first request network entity initiating each history subscription request and the history event subscription information corresponding to each history subscription request; in response to receiving a current subscription request sent by a second requesting network entity, judging whether historical event subscription information matched with current event subscription information in the current subscription request exists in the historical subscription list; sending a subscription response to the second requesting network entity, wherein the subscription response is generated according to a judgment result and is used for notifying the second requesting network entity whether a matched first requesting network entity can provide corresponding subscription data or not, and the matched first requesting network entity is a first requesting network entity corresponding to the matched historical event subscription information in the historical subscription list; and determining whether the second requesting network entity supports obtaining the subscription data from the matched first requesting network entity according to whether a re-subscription request returned by the second requesting network entity is received or not, wherein the re-subscription request is returned under the condition that the local configuration of the matched first requesting network entity and the second requesting network entity conflicts.
In some embodiments, the providing method further comprises: and determining whether to add the second requesting network entity into the historical subscription list according to whether a re-subscription request returned by the second requesting network entity is received.
In some embodiments, the local configuration is a candidate network entity list, the candidate network entity list comprising information about each candidate entity; and the re-subscription request is returned under the condition that the matched first requesting network entity is different from the candidate entities.
In some embodiments, the determining whether to add the second requesting network entity to the historical subscription list according to whether a re-subscription request returned by the second requesting network entity is received comprises: in response to receiving a unsubscribe request returned by the second requesting network entity, sending cancellation confirmation information to the second requesting network entity; and in response to receiving a re-subscription request returned by the second requesting network entity, adding the second requesting network entity to the historical subscription list.
In some embodiments, the determining whether there is historical event subscription information in the historical subscription list that matches current event subscription information in the current subscription request includes: judging whether the current subscription request contains an indication identifier for indicating whether the second requesting network entity supports obtaining the subscription data from each first requesting network entity; under the condition that the indication mark is not included, the judgment result is that the matched historical event subscription information does not exist; and searching the matched historical event subscription information in the historical subscription list under the condition of containing the indication identifier.
In some embodiments, said sending a subscription response to said second requesting network entity comprises: sending a first subscription response to the second requesting network entity in the presence of the matched historical event subscription information, the first subscription response including relevant information of the matched first requesting network entity; and sending a second subscription response to the second requesting network entity in the absence of the matching historical event subscription information, wherein the second subscription response is used for notifying the second requesting network entity that the subscription is successful.
In some embodiments, the event subscription information comprises an identification of the respective event and related parameters; the related information comprises the identity and address information of the corresponding network entity.
In some embodiments, the address information includes an address of a public network associated with the corresponding network entity and a private network identifier of the corresponding network entity.
In some embodiments, the providing method further comprises: under the condition that the matched historical event subscription information does not exist in the judgment result, the related information of the second request network entity and the current event subscription information are stored in the historical subscription list after being bound; in response to an event occurring, determining a second requesting network entity that has subscribed to the event as a current network entity; judging whether the current network entity exists in the history subscription list or not; under the condition that the current network entity exists, informing the current network entity to acquire corresponding subscription data through the first request network entity matched with the event; and sending the corresponding subscription data to the current network entity under the condition that the current network entity does not exist.
According to other embodiments of the present disclosure, there is provided a method for acquiring subscription data, including: sending a current subscription request to a source network entity, wherein the current subscription request comprises current event subscription information; receiving a subscription response returned by the source network entity, wherein the subscription response is used for indicating whether a matched history request network entity capable of providing subscription data exists; determining whether to acquire the corresponding subscription data from the matched history request network entity according to the subscription response; returning a re-subscription request to the source network entity in case the matched history request network entity conflicts with a local configuration.
In some embodiments, the local configuration is a candidate network entity list, the candidate network entity list comprising information about each candidate entity; and the re-subscription request is returned under the condition that the matched first requesting network entity is different from the candidate entities.
In some embodiments, said returning a re-subscription request to said source network entity comprises: returning a unsubscribe request to the source network entity if the matched history request network entity conflicts with the local configuration; and in response to receiving the cancellation confirmation information returned by the source network entity, returning the re-subscription request to the source network entity.
In some embodiments, the sending the current subscription request to the source network entity comprises: and under the condition of supporting to acquire the corresponding subscription data from a history request network entity, sending a current subscription request containing an indication identifier to the source network entity, wherein the indication identifier is used for indicating the source network entity to judge whether the matched history event subscription information exists.
In some embodiments, the obtaining method further includes: responding to the occurrence of an event corresponding to the current subscription request, and receiving a data acquisition notification sent by the source network entity; and acquiring the corresponding subscription data from the matched history request network entity according to the data acquisition notice.
According to still further embodiments of the present disclosure, there is provided a subscription data providing apparatus including: the generating unit is used for generating a history subscription list according to the relevant information of each first request network entity initiating each history subscription request and the history event subscription information corresponding to each history subscription request; a determining unit, configured to determine, in response to receiving a current subscription request sent by a second requesting network entity, whether historical event subscription information matching current event subscription information in the current subscription request exists in the historical subscription list; a sending unit, configured to send a subscription response to the second requesting network entity, where the subscription response is generated according to a determination result, and is used to notify the second requesting network entity whether there is a matching first requesting network entity that can provide corresponding subscription data, where the matching first requesting network entity is a first requesting network entity corresponding to the matching historical event subscription information in the historical subscription list; a determining unit, configured to determine whether the second requesting network entity supports obtaining the subscription data from the matched first requesting network entity according to whether a re-subscription request returned by the second requesting network entity is received, where the re-subscription request is returned when a local configuration of the matched first requesting network entity and the second requesting network entity conflicts.
In some embodiments, the determining unit determines whether to add the second requesting network entity to the historical subscription list according to whether a re-subscription request returned by the second requesting network entity is received.
In some embodiments, the local configuration is a candidate network entity list, the candidate network entity list comprising information about each candidate entity; and the re-subscription request is returned under the condition that the matched first requesting network entity is different from the candidate entities.
In some embodiments, the determining unit sends cancellation determination information to the second requesting network entity in response to receiving a request for unsubscribing returned by the second requesting network entity; and in response to receiving a re-subscription request returned by the second requesting network entity, adding the second requesting network entity to the historical subscription list.
In some embodiments, the determining unit determines whether the current subscription request includes an indication identifier, which is used to indicate whether the second requesting network entity supports obtaining the subscription data from each first requesting network entity; under the condition that the indication mark is not included, the judgment result is that the matched historical event subscription information does not exist; and searching the matched historical event subscription information in the historical subscription list under the condition of containing the indication identifier.
In some embodiments, the sending unit sends a first subscription response to the second requesting network entity in case that the matched historical event subscription information exists, the first subscription response including relevant information of the matched first requesting network entity; and sending a second subscription response to the second requesting network entity in the absence of the matching historical event subscription information, wherein the second subscription response is used for notifying the second requesting network entity that the subscription is successful.
In some embodiments, the event subscription information comprises an identification of the respective event and related parameters; the related information comprises the identity and address information of the corresponding network entity.
In some embodiments, the address information includes an address of a public network associated with the corresponding network entity and a private network identifier of the corresponding network entity.
In some embodiments, the providing apparatus further includes a storage unit, configured to store, in the history subscription list, the relevant information of the second requesting network entity after being bound with the current event subscription information, when the determination result is that the matched history event subscription information does not exist.
In some embodiments, the determining unit determines, as the current network entity, a second requesting network entity that has subscribed to the event in response to the event occurring; the judging unit judges whether the current network entity exists in the history subscription list or not; the sending unit notifies the current network entity to acquire corresponding subscription data through the first request network entity matched with the event under the condition that the current network entity exists; the sending unit sends the corresponding subscription data to the current network entity under the condition that the current network entity does not exist.
According to still other embodiments of the present disclosure, an apparatus for acquiring subscription data is provided, including: a sending unit, configured to send a current subscription request to a source network entity, where the current subscription request includes current event subscription information, and return a re-subscription request to the source network entity when a matched history request network entity conflicts with a local configuration; a receiving unit, configured to receive a subscription response returned by the source network entity, where the subscription response is used to indicate whether there is a history requesting network entity capable of providing the matching of subscription data; a determining unit, configured to determine whether to acquire the corresponding subscription data from the matched history request network entity according to the subscription response.
In some embodiments, the local configuration is a candidate network entity list, the candidate network entity list comprising information about each candidate entity; and the re-subscription request is returned under the condition that the matched first requesting network entity is different from the candidate entities.
In some embodiments, the sending unit returns the re-subscription request to the source network entity in response to receiving cancellation determination information returned by the source network entity.
In some embodiments, the sending unit, in a case that the obtaining of the corresponding subscription data from the history request network entity is supported, sends a current subscription request including an indication identifier to the source network entity, where the indication identifier is used to indicate the source network entity to determine whether the matched history event subscription information exists.
In some embodiments, the receiving unit receives a data acquisition notification sent by the source network entity in response to an event corresponding to the current subscription request; and acquiring the corresponding subscription data from the matched history request network entity according to the data acquisition notice.
According to still further embodiments of the present disclosure, there is provided a subscription data providing apparatus including: a memory; and a processor coupled to the memory, the processor configured to perform the method of providing subscription data in any of the above embodiments based on instructions stored in the memory device.
According to still other embodiments of the present disclosure, there is provided an apparatus for acquiring subscription data, including: a memory; and a processor coupled to the memory, the processor configured to execute the method for obtaining subscription data in any of the above embodiments based on instructions stored in the memory device.
According to still further embodiments of the present disclosure, there is provided a computer-readable storage medium on which a computer program is stored, the program, when executed by a processor, implementing a providing method of subscription data or an acquiring method of subscription data in any of the above embodiments.
According to still further embodiments of the present disclosure, there is provided an interactive system for subscribing to data, including: a subscription data providing device configured to execute the subscription data providing method in any one of the embodiments; and the subscription data acquisition device is used for executing the subscription data acquisition method in any embodiment.
In the above embodiment, it is determined whether there is another network entity capable of providing subscription data for the network entity initiating the subscription request according to the generated historical subscription list, so that the network entity may obtain the subscription data through the other network entity. In this way, repeated collection of data can be avoided, thereby reducing network transmission efficiency.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments of the disclosure and together with the description, serve to explain the principles of the disclosure.
The present disclosure may be more clearly understood from the following detailed description taken in conjunction with the accompanying drawings, in which:
fig. 1 illustrates a flow diagram of some embodiments of a method of providing subscription data of the present disclosure;
FIG. 2 illustrates a flow diagram of further embodiments of a method of providing subscription data of the present disclosure;
FIG. 3 illustrates a flow diagram of yet further embodiments of subscription data provisioning methods of the present disclosure;
fig. 4 illustrates a block diagram of some embodiments of a subscription data providing apparatus of the present disclosure;
fig. 5 illustrates a block diagram of some embodiments of an acquisition apparatus of subscription data of the present disclosure;
fig. 6 illustrates a block diagram of some embodiments of a providing or obtaining device of subscription data of the present disclosure;
FIG. 7 illustrates a block diagram of further embodiments of a subscription data providing or obtaining apparatus of the present disclosure;
fig. 8 illustrates a block diagram of some embodiments of an interactive system to subscribe to data of the present disclosure.
Detailed Description
Various exemplary embodiments of the present disclosure will now be described in detail with reference to the accompanying drawings. It should be noted that: the relative arrangement of the components and steps, the numerical expressions, and numerical values set forth in these embodiments do not limit the scope of the present disclosure unless specifically stated otherwise.
Meanwhile, it should be understood that the sizes of the respective portions shown in the drawings are not drawn in an actual proportional relationship for the convenience of description.
The following description of at least one exemplary embodiment is merely illustrative in nature and is in no way intended to limit the disclosure, its application, or uses.
Techniques, methods, and apparatus known to one of ordinary skill in the relevant art may not be discussed in detail but are intended to be part of the specification where appropriate.
In all examples shown and discussed herein, any particular value should be construed as merely illustrative, and not limiting. Thus, other examples of the exemplary embodiments may have different values.
It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, further discussion thereof is not required in subsequent figures.
As previously described, the 5G system is capable of deploying multiple NWDAF entities simultaneously. In this case, different NWDAF entities may collect the same data according to the analysis request received by themselves; furthermore, it is also possible for the same NWDAF entity to collect the same data multiple times for different analysis requirements (e.g., different analytical IDs).
In view of the above technical problems, the present disclosure provides a technical solution, which can prevent an SNF (source NF) entity from repeatedly sending the same data content to a plurality of NWDAF entities, thereby improving network transmission efficiency. The plurality of NWDAF entities may be a plurality of CNF (consumer NF) entities that subscribe to the same data content.
For example, the technical solutions of the present disclosure can be realized by the following embodiments.
Fig. 1 illustrates a flow diagram of some embodiments of a method of providing subscription data of the present disclosure.
As shown in fig. 1, the method includes: step 110, generating a history subscription list; step 120, judging whether matched historical event subscription information exists; step 130, sending a subscription response; and step 140, determining whether data acquisition from the first requesting network entity is supported.
In step 110, a history subscription list is generated according to the related information of each first requesting network entity initiating each history subscription request and the history event subscription information corresponding to each history subscription request. Therefore, the same data can be prevented from being repeatedly acquired according to the historical subscription list, and the transmission efficiency is improved. For example, the subscription data may be event data corresponding to an event subscription request.
In some embodiments, in response to the subscription request sent by each CNF entity, the SNF entity directly provides the corresponding subscription data to the CNF entities. For example, each CNF entity subscribes to an Event Exposure service (Event Exposure) to the SNF entity.
The SNF entity may determine these CNF entities as HCNF (historical consumption subscription function) entities, i.e. the first requesting network entity. The SNF entity may store the subscription request corresponding to each HCNF as a history subscription record, where each history subscription record forms an IDIL (Index Data Index List), that is, a history subscription List.
In some embodiments, the event subscription information contains an identification of the respective event and related parameters. The related information comprises the identity and address information of the corresponding network entity. For example, the address information includes an address of a public network associated with the corresponding network entity and a private network identifier of the corresponding network entity.
In some embodiments, the Event subscription information may include an Event ID (identification of the Event) and its corresponding Event Filter information (correlation parameter) as a retrieval item. For example, Event ID is an interested Area, and corresponding Event Filter information may be TAI (Tracking Area Identity), etc.; event ID is Access type, and corresponding Event Filter information can be AN (Access Network ) type; event ID is a location description and the corresponding Event Filter information may be TAI.
In some embodiments, an Event ID and Event Filter information may be used as a search term, and an HCNF entity subscribed to the same Event ID and Event Filter information may be recorded under the same search term, thereby forming an IDIL. For example, each search term in the IDIL contains information about at least one HCNF entity. The information related to the HCNF entity may include ID and address information of the HCNF.
In some embodiments, the address information of the network in which the HCNF and the SNF are not located in the same area may be: notification Target Address (+ Notification correction ID). The Notification Target Address may be a gateway Address of a public Network where the HCNF is located, or an Address of an NEF (Network Exposure Function) entity;
the Notification correction ID is the ID of the private network of HCNF.
In step 120, in response to receiving the current subscription request sent by the second requesting network entity, it is determined whether there is historical event subscription information in the historical subscription list that matches the current event subscription information in the current subscription request.
In some embodiments, a CCNF (current CNF) entity wants a certain Event Exposure service to subscribe to the SNF. The second requesting network entity (CCNF) sends a current subscription request to the source network entity (SNF), the current subscription request including current event subscription information.
In some embodiments, the second requesting network entity sends the current subscription request including the indication identifier to the source network entity in support of obtaining the corresponding subscription data from the historical requesting network entity. The indication mark is used for indicating the source network entity to judge whether the matched historical event subscription information exists. In this way, the source network entity can avoid unnecessary matching processing, thereby improving transmission efficiency.
The source network entity judges whether the current subscription request contains an indication identifier, which is used for indicating whether the second requesting network entity supports obtaining the subscription data from each first requesting network entity.
For example, when the indication identifier is not included, the determination result is that there is no matching historical event subscription information; and in the case of containing the indication identifier, searching the history subscription list for the matched history event subscription information.
In some embodiments, if the CCNF entity identifies in the subscription request that it supports the indirect indexing function (acquires subscription data from the HCNF entity), the SNF entity detects the information retrieval items (Event ID, Event Filter information) in the IDIL one by one whether they are the same as the Event ID, Event Filter information in the subscription request of the CCNF entity.
In some embodiments, if the same search term is detected, the SNF entity sends information about the HCNF entity corresponding to the search term in the IDIL to the CCNF entity. For example, it can be sent to the CCNF entity through Acknowledge of Event Exposure Subscription.
For example, if the CCNF entity subscribes to the information through the NEF entity, the SNF entity first transmits the relevant information of the HCNF entity to the NEF entity, and then the NEF entity transmits the relevant information of the HCNF entity to the CCNF entity.
In some embodiments, if the same search term is not detected, the SNF entity determines that the CCNF entity initiating the subscription does not support the indirect indexing function. The SNF entity does not add any relevant information of the HCNF entity in Acknowledgege of Event Exposure Subscription, and adds the CCNF and Subscription information (Event ID, Event Filter information) thereof into IDIL.
In some embodiments, if the CCNF entity does not have an identification in the subscription request indicating that it supports indirect indexing functionality, the SNF entity confirms that the CCNF entity does not support indirect data indexing. The SNF entity can treat the subscription as a subscription of a common Event Exposure, and directly provides a subscription poetry sentence for the CCNF entity when a corresponding Event occurs. In this case, the SNF entity adds the CCNF entity and its subscription information to the IDIL. ,
in step 130, a subscription response is sent to the second requesting network entity, and the subscription response is generated according to the determination result and is used to notify the second requesting network entity whether there is a matching first requesting network entity that can provide corresponding subscription data. The matched first request network entity is the first request network entity corresponding to the matched historical event subscription information in the historical subscription list.
In some embodiments, in the absence of matching historical event subscription information, sending subscription failure information as a subscription response to the second requesting network entity.
In some embodiments, the first subscription response is sent to the second requesting network entity in the presence of matching historical event subscription information. The first subscription response includes relevant information matching the first requesting network entity.
In some embodiments, the second subscription response is sent to the second requesting network entity in the absence of matching historical event subscription information. The second subscription response is used to inform the second requesting network entity that the subscription was successful. The second subscription response does not include any information related to the first requesting network entity.
In some embodiments, the second requesting network entity determines whether to obtain the corresponding subscription data from the matching historical requesting network entity based on the subscription response. For example, it may be determined from the subscription response that corresponding subscription data is obtained from the source network entity or that corresponding subscription data is obtained from the matching history requesting network entity.
In step 140, the second requesting network entity supports obtaining subscription data from the matching first requesting network entity according to whether a re-subscription request returned by the second requesting network entity is received. The re-subscription request is returned in case the local configuration of the matching first requesting network entity and the second requesting network entity conflicts. The re-subscription request is a subscription request sent again by the second requesting network entity.
For example, it may also be determined whether to add the second requesting network entity to the historical subscription list according to whether a re-subscription request returned by the second requesting network entity is received.
In some embodiments, in the event that a re-subscription request returned by the second requesting network entity is received, it is determined that the second requesting network entity does not support obtaining corresponding subscription data from the matching historical requesting network entity.
In some embodiments, the local configuration is a candidate network entity list, which includes information about each candidate entity. And the re-subscription request is returned under the condition that the matched first requesting network entity is different from all the candidate entities.
In some embodiments, the CCNF entity obtains, from the subscription response, HCNF entity information capable of providing subscription data returned by the SNF entity. The CCNF entity detects whether the NF entities in the candidate network entity list are matched with the HCNF entity information one by one, thereby determining whether the HCNF entities can be flushed to acquire subscription data.
Fig. 2 illustrates a flow diagram of further embodiments of subscription data provisioning methods of the present disclosure.
As shown in fig. 2, compared with the embodiment in fig. 1, the present embodiment further includes a step 111 of receiving a current subscription request. Step 130 comprises: step 1310, sending a first subscription response; step 1320, send a second subscription response. At step 250, a re-subscription request is received.
In step 111, a current subscription request from a second requesting network entity is received.
In step 120, in response to receiving the current subscription request sent by the second requesting network entity, it is determined whether there is historical event subscription information in the historical subscription list that matches the current event subscription information in the current subscription request. If so, perform step 1310; in the absence, step 1320 is performed.
In step 1310, a first subscription response is sent to the second requesting network entity. The match is successful if the same HCNF entity is present. The SNF entity informs the CCNF entity to acquire the subscription data in an indirect mode. For example, the NF ID list provided by the CCNF entity may contain wildcards. In the case of wildcard matching, the match is also considered successful.
In step 1320, a second subscription response is sent to the second requesting network entity. If the same HCNF entity is not present, the match fails. The SNF entity refuses the CCNF entity to acquire the subscription data in an indirect mode. If the CCNF entity subscribes through the NEF entity, the NEF entity delivers the notification of the SNF entity to the CCNF entity.
In step 250, a re-subscription request returned by the second requesting network entity is received, and the second requesting network entity indicates in the re-subscription request that indirect acquisition of subscription data is not supported (acquisition of subscription data from the first requesting network entity).
For example, in response to receiving a unsubscribe request returned by the second requesting network entity, sending cancellation confirmation information to the second requesting network entity; and in response to receiving a re-subscription request returned by the second requesting network entity, adding the second requesting network entity to the historical subscription list.
In some embodiments, a CCNF entity supporting indirect acquisition of subscription data maintains a preconfigured white list (list of candidate network entities). The white list lists information of other NF entities (HCNF) that may provide subscription data for the CCNF entity.
For example, the operator may pre-configure a cooperative processing network constituted by NWDAF entities (CNFs) capable of joint processing. The NWDAF entity list in the cooperative Network may also be deployed in each NWDAF instance in the Network, or stored in an NRF (Network redundancy Function) entity.
In some embodiments, the second requesting network entity returns a unsubscribe request to the source network entity in the event that the matching history requesting network entity conflicts with the local configuration. In response to receiving the cancellation determination information returned by the source network entity, the second requesting network entity returns a re-subscription request to the source network entity.
For example, if the CCNF entity determines that the HCNF entity provided by the SNF entity is not on the white list, it determines that the subscription information cannot be acquired from the HCNF entity. The CCNF entity may send subscription cancellation information to the SNF entity. After the cancellation request is confirmed, the CCNF entity re-initiates a subscription request, which does not indicate that it supports indirect data acquisition.
Fig. 3 illustrates a flow diagram of further embodiments of subscription data provisioning methods of the present disclosure.
As shown in fig. 3, compared with the embodiment in fig. 1, the present embodiment further includes: step 310, determining a current network entity; step 320, judging whether the history subscription list has a current network entity; step 330, sending data to the requesting network entity; and step 340, notifying the requesting network entity to obtain the data indirectly.
In step 310, in response to an event occurring, a second requesting network entity that has subscribed to the event is determined as a current network entity.
In some embodiments, the SNF entity determines, according to the Event ID and the Event Filter information of the Event, that the second requesting network entity which has subscribed to the corresponding Event is the current network entity. The SNF entity may generate Notify information for the Event ID and the subscription record of the Event Filter.
In step 320, it is determined whether a current network entity exists in the historical subscription list. In the absence, step 330 is performed; where present, step 340 is performed.
In some embodiments, the SNF entity searches for the related information of the network entity matching the current network entity under the search term corresponding to the current occurrence event.
In step 330, the corresponding subscription data is sent to the current network entity. For example, if there is matching related information in the search term (the current network entity does not support indirect acquisition of data), the Notify information sent by the SNF entity to the current network entity contains a complete Event Report (i.e., subscription data).
In step 340, the current network entity is notified to obtain the corresponding subscription data through the first requesting network entity with the event matching. For example, if there is no matching related information under the search term (the current network entity supports indirect acquisition of data), the Event Report part in the Notify information sent by the SNF entity to the current network entity is empty.
In some embodiments, the current network entity receives a data acquisition notification sent by the source network entity in response to an event corresponding to the current subscription request. And the data acquisition notice is generated according to whether the historical event subscription information corresponding to the current subscription request and the related information of the historical request network entity exist in the historical subscription list. Each history requesting network entity in the history subscription list does not support obtaining subscription data from other history requesting network entities.
In some embodiments, the current network entity obtains the corresponding subscription data from the source network entity or the matching history requesting network entity according to the data obtaining notification. For example, after receiving the Notify information that does not include the Event Report (or the Event Report is null), the CCNF entity may obtain the subscription data (Event Report) through the corresponding HCNF entity. For example, the corresponding HCNF entity information may be stored by the CCNF entity itself, or may be provided by the SNF entity.
In some embodiments, the CCNF entity may obtain the Event Report in a centralized manner. For example, Event Report tasks for multiple CCNF entities may be aggregated by a central processing unit (e.g., NEF entity).
The central processing unit can determine whether to retrieve the redundant data (Event Report) according to the actual situation. For example, the central processing unit has retrieved these redundant data from the corresponding HCNF entity, and these redundant data can be provided to multiple CCNF entities at once. In this case, the CCNF entity does not actually need to retrieve these redundant data from the HCNF entity itself, thereby improving transmission efficiency.
In some embodiments, if the subscription of a certain HCNF entity in the IDIL table has expired (the subscription request may include expires information), the SNF entity may remove the information of the HCNF entity from the IDIL list.
Fig. 4 illustrates a block diagram of some embodiments of a device for providing subscription data of the present disclosure.
As shown in fig. 4, the providing apparatus 4 of subscription data includes a generating unit 41, a judging unit 42, a transmitting unit 43, and a determining unit 44.
The generating unit 41 generates a history subscription list according to the related information of each first requesting network entity initiating each history subscription request and the history event subscription information corresponding to each history subscription request.
The determining unit 42 determines whether there is historical event subscription information in the historical subscription list that matches the current event subscription information in the current subscription request, in response to receiving the current subscription request sent by the second requesting network entity.
The sending unit 43 sends a subscription response to the second requesting network entity. And the subscription response is generated according to the judgment result and is used for informing the second requesting network entity whether the matched first requesting network entity can provide corresponding subscription data. The matched first request network entity is the first request network entity corresponding to the matched historical event subscription information in the historical subscription list.
The determining unit 44 determines whether the second requesting network entity supports obtaining the subscription data from the matched first requesting network entity according to whether a re-subscription request returned by the second requesting network entity is received. The re-subscription request is returned in case the local configuration of the matching first requesting network entity and the second requesting network entity conflicts.
In some embodiments, the determining unit 44 determines whether to add the second requesting network entity to the historical subscription list according to whether a re-subscription request returned by the second requesting network entity is received.
In some embodiments, the local configuration is a list of candidate network entities. The list of candidate network entities includes information about each candidate entity. And the re-subscription request is returned under the condition that the matched first requesting network entity is different from all the candidate entities.
In some embodiments, the sending unit 43 sends the unsubscribe determination information to the second requesting network entity in response to receiving the unsubscribe request returned by the second requesting network entity.
In some embodiments, the providing apparatus further comprises a storage unit, in response to receiving a re-subscription request returned by the second requesting network entity, to add the second requesting network entity to the historical subscription list.
In some embodiments, the determining unit 42 determines whether the current subscription request includes an indication identifier for indicating whether the second requesting network entity supports obtaining the subscription data from each first requesting network entity; under the condition that the indication mark is not included, judging that no matched historical event subscription information exists; in the case of containing the indication identifier, the judging unit 42 searches the history subscription list for the matching history event subscription information.
In some embodiments, the sending unit 43 sends the first subscription response to the second requesting network entity in case there is matching historical event subscription information. The first subscription response includes relevant information matching the first requesting network entity; in case there is no matching historical event subscription information, the sending unit 43 sends a second subscription response to the second requesting network entity, where the second subscription response is used to notify the second requesting network entity that the subscription is successful.
In some embodiments, the event subscription information comprises an identification of the respective event and related parameters; the related information comprises the identity and address information of the corresponding network entity.
In some embodiments, the address information comprises an address of a public network associated with the respective network entity and a private network identity of the respective network entity.
In some embodiments, in the case that the determination result is that there is no matching historical event subscription information, the storage unit 45 stores the relevant information of the second requesting network entity in the historical subscription list after binding with the current event subscription information.
In some embodiments, the determining unit 55 determines, as the current network entity, the second requesting network entity that has subscribed to the event in response to the event occurring; the judging unit 42 judges whether a current network entity exists in the history subscription list; the sending unit 43 notifies the current network entity to obtain corresponding subscription data through the first request network entity matched by the event when the current network entity exists; the sending unit 43 sends the corresponding subscription data to the current network entity, if the current network entity does not exist.
Fig. 5 illustrates a block diagram of some embodiments of an acquisition apparatus of subscription data of the present disclosure.
As shown in fig. 5, the acquisition means 5 of subscription data includes a transmission unit 51, a reception unit 52, and a determination unit 53.
The sending unit 51 sends the current subscription request to the source network entity. The current subscription request includes current event subscription information. In case the matching history requests a network entity conflicting with the local configuration, the sending unit 51 returns a re-subscription request to the source network entity.
The receiving unit 52 receives the subscription response returned by the source network entity. The subscription response is used to indicate whether there is a history requesting network entity that can provide a match for the subscription data.
The determining unit 53 determines whether to acquire the corresponding subscription data from the matching history requesting network entity according to the subscription response.
In some embodiments, the local configuration is a list of candidate network entities. The list of candidate network entities includes information about each candidate entity. And the re-subscription request is returned under the condition that the matched first requesting network entity is different from all the candidate entities.
In some embodiments, the sending unit 51 returns a re-subscription request to the source network entity in response to receiving the cancellation determination information returned by the source network entity.
In some embodiments, the sending unit 51 sends the current subscription request containing the indication identifier to the source network entity in case of supporting the acquisition of the corresponding subscription data from the history request network entity. The indication mark is used for indicating the source network entity to judge whether the matched historical event subscription information exists.
In some embodiments, the receiving unit 52 receives a data acquisition notification sent by the source network entity in response to an event occurrence corresponding to the current subscription request; and acquiring corresponding subscription data from the matched history request network entity according to the data acquisition notice.
Fig. 6 illustrates a block diagram of some embodiments of a providing or obtaining device of subscription data of the present disclosure.
As shown in fig. 6, the subscription data providing apparatus 6 of this embodiment includes: a memory 61 and a processor 62 coupled to the memory 61, the processor 62 being configured to execute a method of providing subscription data in any one of the embodiments of the present disclosure based on instructions stored in the memory 61.
In some embodiments, the obtaining device 6 of the subscription data of this embodiment includes: a memory 61 and a processor 62 coupled to the memory 61, the processor 62 being configured to execute the method for obtaining subscription data in any one of the embodiments of the present disclosure based on instructions stored in the memory 61.
The memory 61 may include, for example, a system memory, a fixed nonvolatile storage medium, and the like. The system memory stores, for example, an operating system, an application program, a Boot Loader (Boot Loader), a database, and other programs.
Fig. 7 shows a block diagram of further embodiments of a providing or obtaining device of subscription data of the present disclosure.
As shown in fig. 7, the subscription data providing device 7 of this embodiment includes: a memory 710 and a processor 720 coupled to the memory 710, the processor 720 being configured to execute the method for providing subscription data in any of the above embodiments based on instructions stored in the memory 710.
In some embodiments, the obtaining device 7 of the subscription data of this embodiment includes: a memory 710 and a processor 720 coupled to the memory 710, wherein the processor 720 is configured to execute the method for obtaining subscription data in any of the embodiments based on instructions stored in the memory 710.
The memory 710 may include, for example, system memory, fixed non-volatile storage media, and the like. The system memory stores, for example, an operating system, an application program, a Boot Loader (Boot Loader), and other programs.
As will be appreciated by one skilled in the art, embodiments of the present disclosure may be provided as a method, system, or computer program product. Accordingly, the present disclosure may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present disclosure may take the form of a computer program product embodied on one or more computer-usable non-transitory storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
Fig. 8 illustrates a block diagram of some embodiments of an interactive system to subscribe to data of the present disclosure.
As shown in fig. 8, the interactive system 8 for subscribing to data includes: a subscription data providing device 81 for executing the subscription data providing method in any of the above embodiments; subscription data acquisition means 82 for executing the subscription data acquisition method in any of the above embodiments.
So far, a providing method of subscription data, an acquiring method of subscription data, a providing of subscription data, an acquiring apparatus of subscription data, an interactive system of subscription data, and a non-volatile computer-readable storage medium according to the present disclosure have been described in detail. Some details that are well known in the art have not been described in order to avoid obscuring the concepts of the present disclosure. It will be fully apparent to those skilled in the art from the foregoing description how to practice the presently disclosed embodiments.
The method and system of the present disclosure may be implemented in a number of ways. For example, the methods and systems of the present disclosure may be implemented by software, hardware, firmware, or any combination of software, hardware, and firmware. The above-described order for the steps of the method is for illustration only, and the steps of the method of the present disclosure are not limited to the order specifically described above unless specifically stated otherwise. Further, in some embodiments, the present disclosure may also be embodied as programs recorded in a recording medium, the programs including machine-readable instructions for implementing the methods according to the present disclosure. Thus, the present disclosure also covers a recording medium storing a program for executing the method according to the present disclosure.
Although some specific embodiments of the present disclosure have been described in detail by way of example, it should be understood by those skilled in the art that the foregoing examples are for purposes of illustration only and are not intended to limit the scope of the present disclosure. It will be appreciated by those skilled in the art that modifications may be made to the above embodiments without departing from the scope and spirit of the present disclosure. The scope of the present disclosure is defined by the appended claims.
Claims (20)
1. A method for providing subscription data, comprising:
generating a history subscription list according to the relevant information of each first request network entity initiating each history subscription request and the history event subscription information corresponding to each history subscription request;
in response to receiving a current subscription request sent by a second requesting network entity, judging whether historical event subscription information matched with current event subscription information in the current subscription request exists in the historical subscription list;
sending a subscription response to the second requesting network entity, wherein the subscription response is generated according to a judgment result and is used for notifying the second requesting network entity whether a matched first requesting network entity can provide corresponding subscription data or not, and the matched first requesting network entity is a first requesting network entity corresponding to the matched historical event subscription information in the historical subscription list;
and determining whether the second requesting network entity supports obtaining the subscription data from the matched first requesting network entity according to whether a re-subscription request returned by the second requesting network entity is received, wherein the re-subscription request is returned under the condition that the local configuration of the matched first requesting network entity and the second requesting network entity conflicts.
2. The supply method according to claim 1,
the local configuration is a candidate network entity list, which comprises relevant information of each candidate entity;
and the re-subscription request is returned under the condition that the matched first requesting network entity is different from the candidate entities.
3. The provisioning method of claim 1, wherein the determining whether the second requesting network entity supports obtaining the subscription data from the matching first requesting network entity according to whether a re-subscription request returned by the second requesting network entity is received comprises:
in response to receiving a unsubscribe request returned by the second requesting network entity, sending cancellation confirmation information to the second requesting network entity;
in response to receiving a re-subscription request returned by the second requesting network entity, determining that the second requesting network entity does not support obtaining the subscription data from the matched first requesting network entity.
4. The providing method according to claim 1, wherein the determining whether there is historical event subscription information in the historical subscription list that matches the current event subscription information in the current subscription request comprises:
judging whether the current subscription request contains an indication mark for indicating whether the second requesting network entity supports obtaining the subscription data from each first requesting network entity;
under the condition that the indication mark is not included, the judgment result is that the matched historical event subscription information does not exist;
and searching the matched historical event subscription information in the historical subscription list under the condition of containing the indication identifier.
5. The provisioning method of claim 1, wherein the sending a subscription response to the second requesting network entity comprises:
sending a first subscription response to the second requesting network entity in the presence of the matched historical event subscription information, the first subscription response including relevant information of the matched first requesting network entity;
and sending a second subscription response to the second requesting network entity in the absence of the matching historical event subscription information, wherein the second subscription response is used for notifying the second requesting network entity that the subscription is successful.
6. The supply method according to claim 1,
the event subscription information comprises identification and relevant parameters of corresponding events;
the related information comprises the identity and address information of the corresponding network entity.
7. The supply method according to claim 6,
the address information comprises the address of the public network related to the corresponding network entity and the private network identification of the corresponding network entity.
8. The provision method according to any one of claims 1 to 7, further comprising:
under the condition that the matched historical event subscription information does not exist in the judgment result, the related information of the second request network entity and the current event subscription information are stored in the historical subscription list after being bound;
in response to an event occurring, determining a second requesting network entity that has subscribed to the event as a current network entity;
judging whether the current network entity exists in the history subscription list or not;
under the condition that the current network entity exists, the current network entity is informed to acquire corresponding subscription data through the first request network entity matched with the event;
and sending the corresponding subscription data to the current network entity under the condition that the current network entity does not exist.
9. The provision method according to any one of claims 1 to 7, further comprising:
and determining whether to add the second requesting network entity into the historical subscription list according to whether a re-subscription request returned by the second requesting network entity is received.
10. A method for acquiring subscription data comprises the following steps:
sending a current subscription request to a source network entity, wherein the current subscription request comprises current event subscription information;
receiving a subscription response returned by the source network entity, wherein the subscription response is used for indicating whether a matched history request network entity capable of providing subscription data exists;
determining whether to acquire the corresponding subscription data from the matched history request network entity according to the subscription response;
returning a re-subscription request to the source network entity in case the matched history request network entity conflicts with a local configuration.
11. The acquisition method according to claim 10,
the local configuration is a candidate network entity list, which comprises relevant information of each candidate entity;
and the re-subscription request is returned under the condition that the matched first requesting network entity is different from the candidate entities.
12. The acquisition method of claim 11, wherein the returning a re-subscription request to the source network entity comprises:
returning a unsubscribe request to the source network entity when the matched history request network entity conflicts with the local configuration;
and in response to receiving the cancellation determination information returned by the source network entity, returning the re-subscription request to the source network entity.
13. The acquisition method of claim 10, wherein the sending a current subscription request to a source network entity comprises:
and under the condition of supporting to acquire the corresponding subscription data from a history request network entity, sending a current subscription request containing an indication identifier to the source network entity, wherein the indication identifier is used for indicating the source network entity to judge whether the matched history event subscription information exists.
14. The acquisition method according to any one of claims 10 to 13, further comprising:
responding to the occurrence of an event corresponding to the current subscription request, and receiving a data acquisition notification sent by the source network entity;
and acquiring the corresponding subscription data from the matched history request network entity according to the data acquisition notice.
15. A subscription data providing apparatus, comprising:
a generating unit, configured to generate a history subscription list according to relevant information of each first request network entity initiating each history subscription request and history event subscription information corresponding to each history subscription request;
a determining unit, configured to determine, in response to receiving a current subscription request sent by a second requesting network entity, whether historical event subscription information matching current event subscription information in the current subscription request exists in the historical subscription list;
a sending unit, configured to send a subscription response to the second requesting network entity, where the subscription response is generated according to a determination result, and is used to notify the second requesting network entity whether there is a matching first requesting network entity that can provide corresponding subscription data, where the matching first requesting network entity is a first requesting network entity corresponding to the matching historical event subscription information in the historical subscription list;
a determining unit, configured to determine whether the second requesting network entity supports obtaining the subscription data from the matched first requesting network entity according to whether a re-subscription request returned by the second requesting network entity is received, where the re-subscription request is returned when local configurations of the matched first requesting network entity and the second requesting network entity conflict.
16. An acquisition apparatus of subscription data, comprising:
a sending unit, configured to send a current subscription request to a source network entity, where the current subscription request includes current event subscription information, and return a re-subscription request to the source network entity when a matched history request network entity conflicts with a local configuration;
a receiving unit, configured to receive a subscription response returned by the source network entity, where the subscription response is used to indicate whether there is a history requesting network entity capable of providing the matching of subscription data;
a determining unit, configured to determine whether to acquire the corresponding subscription data from the matched history request network entity according to the subscription response.
17. A subscription data providing apparatus, comprising:
a memory; and
a processor coupled to the memory, the processor configured to perform the method of providing subscription data of any of claims 1-9 based on instructions stored in the memory.
18. An acquisition apparatus of subscription data, comprising:
a memory; and
a processor coupled to the memory, the processor configured to execute the method of obtaining subscription data of any of claims 10-14 based on instructions stored in the memory.
19. An interactive system for subscribing to data, comprising:
a subscription data providing device for executing the subscription data providing method according to any one of claims 1 to 9;
subscription data acquisition means for executing the subscription data acquisition method of any one of claims 10 to 14.
20. A computer-readable storage medium, on which a computer program is stored, which program, when being executed by a processor, carries out the method for providing subscription data according to any one of claims 1 to 9, or carries out the method for acquiring subscription data according to any one of claims 10 to 14.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010353912.2A CN113573282B (en) | 2020-04-29 | 2020-04-29 | Subscription data providing/acquiring method, providing/acquiring device and interactive system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010353912.2A CN113573282B (en) | 2020-04-29 | 2020-04-29 | Subscription data providing/acquiring method, providing/acquiring device and interactive system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113573282A CN113573282A (en) | 2021-10-29 |
| CN113573282B true CN113573282B (en) | 2022-09-16 |
Family
ID=78158297
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010353912.2A Active CN113573282B (en) | 2020-04-29 | 2020-04-29 | Subscription data providing/acquiring method, providing/acquiring device and interactive system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113573282B (en) |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2004071103A2 (en) * | 2003-02-04 | 2004-08-19 | Nokia Corporation | Method and system for authorizing access to user information in a network |
| CN101295311A (en) * | 2008-06-17 | 2008-10-29 | 浙江大学 | Semantic matching algorithm of large scale issuance subscription system |
| CN104036052A (en) * | 2014-07-05 | 2014-09-10 | 中国科学院软件研究所 | Predicate index matching method based on historical experience |
| CN104809028A (en) * | 2015-05-07 | 2015-07-29 | 厦门雅迅网络股份有限公司 | Method for subscribing and pushing data among multiple local processes |
| WO2016126021A1 (en) * | 2015-02-06 | 2016-08-11 | 엘지전자 주식회사 | Method and apparatus for processing request for stopping notification receipt in wireless communication system |
| CN109547221A (en) * | 2017-09-22 | 2019-03-29 | 中兴通讯股份有限公司 | Big data analysis service providing method and device, computer readable storage medium |
| CN110110269A (en) * | 2019-04-09 | 2019-08-09 | 深圳前海微众银行股份有限公司 | A kind of event subscription method and device based on block chain |
| CN110557744A (en) * | 2018-05-31 | 2019-12-10 | 华为技术有限公司 | Method for subscribing event and network function network element |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20030105801A1 (en) * | 2001-11-30 | 2003-06-05 | Telefonaktiebolaget L M Ericsson (Publ) (Signed) | Method, system and agent for connecting event consumers to event producers in a distributed event management system |
-
2020
- 2020-04-29 CN CN202010353912.2A patent/CN113573282B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2004071103A2 (en) * | 2003-02-04 | 2004-08-19 | Nokia Corporation | Method and system for authorizing access to user information in a network |
| CN101295311A (en) * | 2008-06-17 | 2008-10-29 | 浙江大学 | Semantic matching algorithm of large scale issuance subscription system |
| CN104036052A (en) * | 2014-07-05 | 2014-09-10 | 中国科学院软件研究所 | Predicate index matching method based on historical experience |
| WO2016126021A1 (en) * | 2015-02-06 | 2016-08-11 | 엘지전자 주식회사 | Method and apparatus for processing request for stopping notification receipt in wireless communication system |
| CN104809028A (en) * | 2015-05-07 | 2015-07-29 | 厦门雅迅网络股份有限公司 | Method for subscribing and pushing data among multiple local processes |
| CN109547221A (en) * | 2017-09-22 | 2019-03-29 | 中兴通讯股份有限公司 | Big data analysis service providing method and device, computer readable storage medium |
| CN110557744A (en) * | 2018-05-31 | 2019-12-10 | 华为技术有限公司 | Method for subscribing event and network function network element |
| CN110110269A (en) * | 2019-04-09 | 2019-08-09 | 深圳前海微众银行股份有限公司 | A kind of event subscription method and device based on block chain |
Non-Patent Citations (1)
| Title |
|---|
| "S2-2001854 - CR 23.288 adding the monitoring period as an event filter information for data collection";Huawei;《3GPP tsg_sa\wg2_arch》;20200218;全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113573282A (en) | 2021-10-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8069224B2 (en) | Method, equipment and system for resource acquisition | |
| US9535943B2 (en) | Systems and methods for content collection validation | |
| CN103038788A (en) | Provisioning multiple network resources | |
| CN111181784B (en) | Network port state management method, state machine engine device, equipment and medium | |
| JP2014010723A (en) | Retrieval device, retrieval method and program | |
| TW200821863A (en) | Work item event procession | |
| CN112396432B (en) | Interview task generation system, interview task generation method, interview task generation equipment and interview task generation medium | |
| JP6200376B2 (en) | In-vehicle information system and information processing method thereof | |
| CN111526185B (en) | Data downloading method, device, system and storage medium | |
| CN108574718B (en) | Cloud host creation method and device | |
| CN113573282B (en) | Subscription data providing/acquiring method, providing/acquiring device and interactive system | |
| CN113709792A (en) | Data analysis processing method, device, network data analysis function and medium | |
| CN107045466B (en) | Service data auditing method, device and system | |
| CN113573299B (en) | Subscription data providing/acquiring method, providing/acquiring device and interactive system | |
| EP2568682A1 (en) | Method and System for Managing Suspicious Devices in a Network | |
| CN114328502A (en) | Data collection method, device, network equipment and storage medium | |
| US20120166648A1 (en) | Apparatus and method for providing a service through sharing solution providing unit in cloud computing environment | |
| JP2004228721A (en) | Contents display apparatus and method | |
| CN114138371B (en) | Configuration dynamic loading method and device, computer equipment and storage medium | |
| CN104935966A (en) | Method and device for copying classified video information | |
| CN102045206A (en) | Alarm pushing method and device and system thereof | |
| CN105808606B (en) | Searching method and device on mobile equipment | |
| CN114896337A (en) | Data uplink method, system, equipment and computer readable storage medium | |
| CN108038254A (en) | The processing method and system of different type unit in file format transfer process | |
| CN111061543A (en) | Multi-tenant workflow engine service method, device and server |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |