Event subscription method and device, related equipment, storage medium and computer program product
By receiving subscription intents and determining the corresponding events, event subscription based on subscription intent granularity is achieved, solving the problem of poor flexibility in event subscription in existing technologies and realizing efficient and flexible event subscription.
Patent Information
- Application Number
- CN202410876620.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-01
- Publication Date
- 2024-11-22
AI Technical Summary
Existing event subscription methods are based on event granularity processing, which is inflexible and makes it difficult to achieve efficient event subscription, especially in multi-user and multi-network environments.
By receiving subscription intents, determining corresponding events, and subscribing to events through a third function, event subscription based on subscription intent granularity is achieved, which is highly flexible and can adapt to changes in network operators.
It achieves efficient event subscription, can adapt to changes in network operators, does not require frequent synchronization of event identifiers, and supports unified subscription in multi-user and multi-network environments.
Smart Images

Figure CN119012170A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of core network technology, and in particular to an event subscription method, apparatus, related equipment, storage medium and computer program product. Background Art
[0002] Currently, an application function (AF) can subscribe to network events by calling a network exposure function (NEF) to obtain required information or event notifications.
[0003] However, in the related art, event subscription is processed based on event granularity, which is very inflexible and cannot achieve efficient event subscription. Summary of the invention
[0004] To solve related technical problems, the embodiments of the present application provide an event subscription method, apparatus, related equipment, storage medium and computer program product.
[0005] The technical solution of the embodiment of the present application is implemented as follows:
[0006] The embodiment of the present application provides an event subscription method, which is applied to a first function and includes:
[0007] receiving a first request sent by a second function, where the first request is used to request event subscription, and the first request includes first information, where the first information represents one or more subscription intentions;
[0008] Determine second information using the first information, where the second information represents one or more events corresponding to the one or more subscription intents;
[0009] Sending a second request to one or more third functions corresponding to the one or more events, where the third functions are at least used to send event notifications, and the second request is used to request to subscribe to one or more events associated with the third functions in the one or more events;
[0010] receiving event notifications sent by one or more of the third functions;
[0011] The received event notification is sent to the second function.
[0012] In the above solution, the step of using the first information to determine the second information includes:
[0013] The second information is determined by using the first information and the third information, wherein the third information represents a correspondence between one or more subscription intentions and events.
[0014] In the above solution, each event notification sent by the third function includes fourth information, where the fourth information is used to identify an event associated with the event notification, and sending the event notification to the second function includes:
[0015] Determine fifth information by using the fourth information and the third information, wherein the fifth information represents a subscription intent corresponding to an event associated with the event notification, and the third information represents a correspondence between one or more subscription intents and the event;
[0016] The event notification sent to the second function includes the fifth information.
[0017] In the above solution, the first request further includes sixth information, where the sixth information represents one or more users corresponding to each subscription intent of the one or more subscription intents; and the method further includes:
[0018] Determine seventh information by using the first information, the third information and the sixth information, wherein the seventh information is used to identify one or more users corresponding to each of the one or more events, and the third information represents a corresponding relationship between one or more subscription intentions and events;
[0019] The second request includes the seventh information.
[0020] In the above solution, the event notification sent by each third function includes fourth information and eighth information, the fourth information is used to identify the event associated with the event notification, and the eighth information is used to identify one or more users corresponding to the event notification, and the sending of the event notification to the second function includes:
[0021] Using the fourth information and the eighth information, merging all received event notifications to obtain one or more event notifications corresponding to each user; sending the one or more event notifications corresponding to each user to the second function;
[0022] Alternatively, the sending the event notification to the second function includes:
[0023] Each event notification received is sent directly to the second function.
[0024] In the above solution, the first function is at least used for network capability exposure, and / or the second function is at least used for providing application services.
[0025] The embodiment of the present application also provides an event subscription method, which is applied to the second function, including:
[0026] Sending a first request to a first function, where the first request is used to request event subscription, and the first request includes first information, where the first information represents one or more subscription intentions;
[0027] Receive an event notification sent by the first function.
[0028] In the above scheme, the event notification sent by the first function includes fifth information, and the fifth information represents the subscription intention corresponding to the event associated with the event notification.
[0029] In the above solution, the receiving the event notification sent by the first function includes:
[0030] Receive an event notification corresponding to each user sent by the first function;
[0031] or,
[0032] Receive each event notification sent directly by the first function.
[0033] In the above solution, the first function is at least used for network capability exposure, and / or the second function is at least used for providing application services.
[0034] The embodiment of the present application further provides an event subscription method, which is applied to a third function, wherein the third function is at least used to send an event notification, including:
[0035] receiving a second request sent by the first function, the second request being used to request a subscription to one or more events associated with the third function, the second request comprising seventh information, the seventh information being used to identify one or more users corresponding to each of the one or more events;
[0036] The seventh information is used to perform subscription processing on each of the one or more users, and an event notification is sent to the first function.
[0037] In the above scheme, the event notification sent includes the fourth information, or the event notification sent includes the fourth information and the eighth information, the fourth information is used to identify the event associated with the event notification, and the eighth information is used to identify one or more users corresponding to each of the one or more events.
[0038] In the above solution, the first function is at least used for network capability opening.
[0039] The embodiment of the present application further provides a first function, including: a first processor and a first memory for storing a computer program that can be run on the processor,
[0040] Wherein, the first processor is used to execute the steps of any method of the above-mentioned first function side when running the computer program.
[0041] The embodiment of the present application further provides a second function, including: a second processor and a second memory for storing a computer program that can be run on the processor,
[0042] Wherein, when the second processor is used to run the computer program, it executes the steps of any method of the second functional side mentioned above.
[0043] The embodiment of the present application further provides a third function, including: a third processor and a third memory for storing a computer program that can be run on the processor,
[0044] Wherein, the third processor is used to execute the steps of any method of the third functional side when running the computer program.
[0045] An embodiment of the present application also provides a storage medium having a computer program stored thereon, wherein when the computer program is executed by a processor, the computer program implements the steps of any method on the first functional side, or implements the steps of any method on the second functional side, or implements the steps of any method on the third functional side.
[0046] An embodiment of the present application also provides a computer program product, including a computer program, which, when executed by a processor, implements the steps of any method on the first functional side, or implements the steps of any method on the second functional side, or implements the steps of any method on the third functional side.
[0047] The event subscription method, apparatus, related equipment, storage medium and computer program product provided by the embodiment of the present application, the second function sends a first request to the first function, the first request is used to request event subscription, the first request includes first information, the first information represents one or more subscription intentions; the first function receives the first request sent by the second function; the first function uses the first information to determine the second information, the second information represents one or more events corresponding to the one or more subscription intentions; the first function sends a second request to one or more third functions corresponding to the one or more events, the third function is at least used to send event notifications, the second request is used to request subscription to one or more events associated with the third function in the one or more events; the first function receives one or more event notifications sent by the third function; the first function sends the received event notification to the second function; the second function receives the event notification sent by the first function. In the solution provided by the embodiment of the present application, the second function sends one or more subscription intentions to the first function, the first function can determine the corresponding event according to the subscription intention, and subscribe to the event through the third function, so that event subscription based on subscription intention granularity can be realized, with high flexibility, and efficient event subscription can be realized. BRIEF DESCRIPTION OF THE DRAWINGS
[0048] Figure 1 A schematic diagram of a network structure supporting network capability opening in the related technology;
[0049] Figure 2 A schematic diagram of a process of an AF calling a service provided by a NEF to subscribe to an event in a related technology;
[0050] Figure 3 This is a flow chart of the first event subscription method according to an embodiment of the present application;
[0051] Figure 4 This is a flow chart of the second event subscription method according to an embodiment of the present application;
[0052] Figure 5 This is a flow chart of the third event subscription method according to an embodiment of the present application;
[0053] Figure 6 This is a flow chart of the fourth event subscription method according to an embodiment of the present application;
[0054] Figure 7 A flowchart of an event subscription enhancement method for an example application of this application;
[0055] Figure 8 This is a schematic diagram of the structure of the first event subscription device in the embodiment of the present application;
[0056] Fig. 9 This is a schematic diagram of the structure of the second event subscription device in the embodiment of the present application;
[0057] Fig.10 This is a schematic diagram of the structure of the third event subscription device in the embodiment of the present application;
[0058] Fig.11 This is a schematic diagram of the first functional structure of an embodiment of the present application;
[0059] Fig.12 This is a schematic diagram of the second functional structure of the embodiment of the present application;
[0060] Fig.13 This is a schematic diagram of the third functional structure of the embodiment of the present application;
[0061] Fig.14 This is a schematic diagram of the event subscription system structure of an embodiment of the present application. DETAILED DESCRIPTION
[0062] The present application will be further described in detail below through the accompanying drawings and embodiments.
[0063] The fifth generation mobile communication technology (5G) network architecture can support the opening of network capabilities. It can open 5G network data and functions such as user status information, location information, quality of service (QoS) control capabilities, session routing management capabilities, etc. to applications (specific applications may include applications provided by operators, third-party applications (also understood as external applications), etc.) to enable applications to obtain network information and adjust network carrying resources according to actual business needs.
[0064] For example, Figure 1 As shown, AF can call the services provided by NEF through the application programming interface (API), such as transmitting business requirements and configuration information to the 5G network through NEF, and subscribing to the information and / or event notifications required by the application to the 5G network. Specifically, Figure 1 In the 5G 5G network, AF can be an application platform. AF is associated with one or more (one or more can also be understood as at least one) external applications. External applications can interact with one or more related users to provide corresponding functions for users. Network functions (NF) can be specific 5G network elements that provide services for external applications. NEF is a core network element for capability exposure. NEF is used to isolate external applications from 5G networks, thereby providing security isolation based on network capability exposure, as well as adaptation of requirements and services. Specifically, NEF has at least the following functions:
[0065] 1) Receive business requests sent by external applications and authenticate and / or authorize the business requests, where business requests may specifically include service call requirements, data configuration requests, event subscription requests, etc.;
[0066] 2) Selecting a network element corresponding to the service request to provide services for the external application, and converting the interactive information between the external application and the network element providing the service to realize the information transmission between the external application and the network element providing the service;
[0067] 3) Receive event notifications sent by network elements and forward the received event notifications to corresponding external applications.
[0068] In the related technologies, the opening of event subscription notification capability is a very important aspect of 5G capability opening. The opening of event subscription notification capability means that the 5G network can open user status information, location information, session status information and other information in the 5G network to applications through NEF; specifically, applications can obtain the required information from the 5G network through event subscription (which can also be understood as subscription event) in the specific circumstances associated with the event.
[0069] More specifically, if Figure 2 As shown, the process of AF calling the service provided by NEF to subscribe to events (also referred to as subscription process) may specifically include the following steps:
[0070] Step 201: AF sends a request to NEF, where the request is used to request event subscription (which can also be understood as requesting service invocation);
[0071] Here, the request sent by AF to NEF may specifically include a list of event identifiers that need to be subscribed (expressed as Event ID List in English) and a user identifier and / or user group identifier associated with each event. That is, AF tells NEF which events need to be subscribed and which user or user group each event is associated with.
[0072] Exemplarily, the AF may send a request to the NEF via an event exposure subscription / unsubscription request (which may be expressed as Nnef_EventExposure_Subscribe / Unsubscribe Request in English) message.
[0073] Step 202: After receiving the request sent by the AF, the NEF forwards the request to the Unified Data Management (UDM);
[0074] Exemplarily, the NEF may send a request to the UDM through an event exposure subscription / unsubscription request (which may be expressed as Nudm_EventExposure_Subscribe / Unsubscribe Request) message of the UDM.
[0075] Step 203: After receiving the request sent by the NEF, the UDM determines one or more network elements for event notification according to the request, and subscribes to the event for the one or more network elements, and then executes step 204;
[0076] Among them, the one or more network elements may specifically include access and mobility management function (AMF, Access and Mobility Management Function), session management function (SMF, Session Management Function), user plane function (UPF, User Plane Function) and other network elements.
[0077] Specifically, UDM can determine the 5G network element (such as AMF, SMF, etc.) used for event notification for each event identified in the event identification list, and subscribe to the event for the determined 5G network element.
[0078] In the case where the network element used for event notification includes AMF, UDM can send a subscription request to AMF to subscribe to events related to AMF, and receive response information sent by AMF, wherein the response information is used to indicate whether the subscription is successful, thereby completing the event subscription to AMF. Exemplarily, UDM can send a subscription request to AMF via a Namf_EventExposure_Subscribe / Unsubscribe Request message; at the same time, AMF can feedback response information to UDM via a Namf_EventExposure_Subscribe / Unsubscribe Response message;
[0079] In the case where the network element used for event notification includes SMF, UDM can send a subscription request to SMF to subscribe to events related to SMF, and receive response information sent by SMF, wherein the response information is used to indicate whether the subscription is successful, thereby completing event subscription for SMF. Exemplarily, UDM can send a subscription request to SMF via Nsmf_EventExposure_Subscribe / Unsubscribe Request message; at the same time, SMF can feedback response information to UDM via Nsmf_EventExposure_Subscribe / Unsubscribe Response message;
[0080] In the case where the network element used for event notification includes UPF, UDM can send a subscription request to SMF to subscribe to events related to UPF, and SMF interacts with UPF to implement event subscription for UPF. After completing the subscription, SMF sends a response message to UDM, and the response message is used to indicate whether the subscription is successful. Exemplarily, SMF and UPF can interact through N4 Session Modification (English can be expressed as N4 Session Modification) messages and Event Exposure Subscription (English can be expressed as Nupf_EventExposure_Subscribe) messages to implement event subscription for UPF.
[0081] Step 204: UDM sends a response message to NEF to inform NEF of the subscription status of the relevant network element;
[0082] Exemplarily, the UDM may send response information to the NEF via a Nudm_EventExposure_Subscribe / Unsubscribe Response message.
[0083] Step 205: After receiving the response information sent by the UDM, the NEF transmits the response information to the AF;
[0084] Exemplarily, the NEF may send response information to the AF via an NEF event exposure subscription / unsubscription response (Nnef_EventExposure_Subscribe / Unsubscribe Response) message.
[0085] In actual application, after step 205, under certain circumstances (such as when a subscribed event is triggered), the relevant network element can execute steps 206 to 207, thereby realizing the opening of the event subscription notification capability.
[0086] Step 206: The NEF receives the event notification sent by the network element that subscribes to the event, and stores the event notification in a unified data storage (UDR, Unified Data Repository), and then executes step 207;
[0087] Here, NEF can receive event notifications directly sent by network elements such as AMF, SMF, UPF, and UDM. Network elements such as AMF, SMF, and UPF can also send event notification information to UDM, and then UDM forwards the event notification information to NEF.
[0088] Exemplarily, UDM can send event notification to NEF through UDM's event exposure notification (Nudm_EventExposure_Notify) message; AMF can send event notification information to NEF through Namf_EventExposure_Notify message; SMF can send event notification information to NEF through Nsmf_EventExposure_Notify message; UPF can send event notification information to NEF through Nupf_EventExposure_Notify message; at the same time, UDM can store event notification information to UDR through UDR's data management create / update (expressed in English as Nudr_DM_Create / Update) message.
[0089] Step 207: The NEF forwards the received event notification information to the AF.
[0090] Exemplarily, the NEF may send event notification information to the AF via a Nnef_EventExposure_Notify message.
[0091] From the above description, it can be seen that AF can subscribe to events of network elements in the 5G core (5GC, 5G Core) network through NEF and UDM.
[0092] However, in actual application, the solutions in the related art have the following shortcomings:
[0093] 1) With the standardization of the Next Generation Real Time Communication (NG-RTC) and the introduction of the Internet Protocol Multimedia Subsystem (IMS) Data Channel (DC), there may be a scenario where the RTC application platform subscribes to events from both the 5G network and the IMS network. That is, the RTC application platform needs to subscribe to events from both the network elements in the 5G network and the network elements in the IMS network to obtain information such as user location information, user registration status in the 5G network, user registration status in the IMS network, IMS session status, IMSDC status, DC application information, etc. At this time, the NEF needs to be able to split the received event subscription requests according to different networks, and according to the split event subscription requests, subscribe to events to the corresponding network elements (such as UDM, Home Subscriber Server (HSS), IMS Application Server (IMS AS), DC Signaling Function (DCSF)), respectively, but the NEF in the relevant technology does not currently have this capability;
[0094] 2) The solutions in the related art can only implement event subscription based on the granularity of a single user or a single user group. That is, when AF sends a subscription request, it can only subscribe to events related to one user or a predefined user group, but cannot implement unified subscription of events related to any combination of multiple users. This is very inflexible and difficult to implement efficient event subscription.
[0095] 3) The solutions in the related technology can only realize event subscription based on event granularity, that is, external applications need to know the event identifiers used by the 5G network and transparently transmit the event identifiers in the network during the event subscription process. This requires application providers to understand the events of the 5G network and pre-negotiate event identifiers with the 5G network operator. At the same time, when the network operator changes or adds event identifiers, external applications need to frequently synchronize all event identifiers with the network operator to ensure the realization of event subscription. This is very inflexible and difficult to achieve efficient event subscription.
[0096] Based on this, in various embodiments of the present application, the second function (such as AF) sends one or more subscription intents to the first function (such as NEF). The first function can determine the corresponding event based on the subscription intent and subscribe to the event through the third function (such as NF). In this way, event subscription based on the granularity of subscription intent can be realized, which is highly flexible and can achieve efficient event subscription.
[0097] The present application embodiment provides an event subscription method, which is applied to a first function, such as Figure 3 As shown, the method includes:
[0098] Step 301: receiving a first request sent by a second function, where the first request is used to request event subscription, and the first request includes first information, where the first information represents one or more subscription intentions;
[0099] Step 302: using the first information, determining second information, where the second information represents one or more events corresponding to the one or more subscription intentions;
[0100] Step 303: Send a second request to one or more third functions corresponding to the one or more events, where the third function is at least used to send event notifications, and the second request is used to request to subscribe to one or more events associated with the third function in the one or more events;
[0101] Step 304: receiving event notifications sent by one or more third functions;
[0102] Step 305: Send the received event notification to the second function.
[0103] Here, in one embodiment, the first function is at least used for network capability opening, and the first function may include NEF; the second function is at least used for providing application services, and the second function may include AF. Of course, in actual application, the first function and the second function may also include other functions that can realize the corresponding functions, which is not limited in this embodiment of the present application.
[0104] In actual application, when the second function needs to subscribe to an event, the second function can send a first request to the first function, and the first request includes one or more subscription intents, that is, the second function informs the first function which intents need to be subscribed to events; accordingly, in step 301, after the first function receives the first request sent by the second function, it obtains one or more subscription intents for which the second function needs to subscribe to events, and implements event subscription based on subscription intent granularity through subsequent steps, that is, subscribing to one or more events related to subscription intent. In this way, the second function does not need to know the event identifier used by the network operator in advance, but only needs to provide the subscription intent to implement event subscription. Since the subscription intent reflects the purpose of subscribing to events, it is more general than the specific event identifier. Therefore, even if the network operator changes or adds event identifiers, the second function does not need to frequently synchronize all event identifiers with the network operator, so that a more general and flexible event subscription can be implemented. Among them, the first request can also be called an event subscription request or an event notification subscription request; the first request can include one or more subscription intent parameters, each of which is used to represent a subscription intent; exemplarily, the subscription intent can include one or more of the following (one or more can also be understood as at least one):
[0105] IMS session status;
[0106] IMSDC status;
[0107] User 5G network registration status;
[0108] User IMS network registration status.
[0109] In actual application, after receiving the first request, in step 302, the first function can determine which event or events the subscription corresponds to for each subscription intent included in the first request by using the correspondence between the subscription intent and the event.
[0110] Based on this, in one embodiment, the specific implementation of step 302 may include:
[0111] The second information is determined by using the first information and the third information, wherein the third information represents a correspondence between one or more subscription intentions and events.
[0112] Here, the third information can be specifically presented in the form of a table. At the same time, the third information can be predefined (i.e., pre-set) within the first function. The embodiment of the present application does not limit the specific form and acquisition method of the third information.
[0113] The second information may specifically include an event identifier list, where the event identifier list includes one or more event identifiers, and each event identifier is used to identify an event.
[0114] In actual application, the operation of step 302 can also be understood as the first function translating the subscription intent into specific events, and splitting the first request to obtain an event subscription request for each event, so that a subscription can be performed for each event.
[0115] In actual application, after determining the second information, the first function can determine one or more third functions corresponding to the one or more events corresponding to the second information, in combination with the correspondence between the event and the third function providing event notification service. Here, the third function is at least used to send event notifications, that is, the third function is a function that can provide event notification services, such as UDM, HSS, DCSF, IMS AS and other functions, which are not limited in this embodiment of the present application.
[0116] In actual application, when a subscription intent corresponds to multiple events, the multiple events may correspond to the same third function, that is, the event notification service of the multiple events is provided by one third function; or, the multiple events may also correspond to multiple third functions, that is, the event notification service of the multiple events is jointly provided by multiple third functions, and each third function provides event notification service for different events among the multiple events.
[0117] After determining the one or more third functions, in step 303, the first function may send a second request to each of the one or more third functions to subscribe to one or more events associated with the third function, that is, the first function calls the event notification service provided by each third function to implement the event subscription related to the first request; wherein, the second request may include event identifiers of all events associated with the third function in one or more events associated with the first request.
[0118] In actual application, for each third function, after receiving the second request sent by the first function, the third function can use the second request to determine which events need to be subscribed, and perform corresponding configuration to complete the event subscription.
[0119] In actual application, after the event subscription is completed, for each event, the third function can send an event notification of the event to the first function under specific circumstances associated with the event (such as event triggering, periodic notification, etc.), wherein the event notification is notification information at the event granularity, and the event notification can specifically include event identifier, event description and other information; accordingly, in step 304, the first function receives the event notification of the event sent by the third function.
[0120] After step 304, the first function can determine, for each received event notification, the event corresponding to the event notification by using the event identifier contained in the event notification, and then determine the subscription intent corresponding to the event notification in combination with the third information (i.e., the correspondence between the event and the subscription intent). Then, in step 305, the first function can include the subscription intent in the sent event notification, so that the second function can determine which subscription intent the received event notification is associated with without knowing the event identifier.
[0121] Based on this, in one embodiment, the event notification sent by each third function includes fourth information, and the fourth information is used to identify the event associated with the event notification. The specific implementation of step 305 may include:
[0122] Determine fifth information by using the fourth information and the third information, wherein the fifth information represents a subscription intent corresponding to an event associated with the event notification, and the third information represents a correspondence between one or more subscription intents and the event;
[0123] The event notification sent to the second function includes the fifth information.
[0124] Here, in actual application, the fourth information may also be referred to as an event identifier, such as an event ID. The embodiment of the present application does not limit the name of the fourth information.
[0125] In step 305, the first function may use the fifth information to replace the fourth information in the event notification, and send the replaced event notification to the second function. This process may also be understood as the first function translating the event identifier in the event notification into a subscription intent.
[0126] In actual application, the first request sent by the second function can also carry user information corresponding to each subscription intent. That is to say, the first request contains one or more subscription intents at the same time, and which users each subscription intent in the one or more subscription intents corresponds to (which can also be understood as the user range of subscription intents). In this way, the first function can realize unified subscription to events corresponding to any combination of multiple users, further improving flexibility and thus further improving event subscription efficiency.
[0127] Based on this, in one embodiment, the first request further includes sixth information, where the sixth information represents one or more users corresponding to each subscription intent of the one or more subscription intents; the method may further include:
[0128] Determine seventh information by using the first information, the third information and the sixth information, wherein the seventh information is used to identify one or more users corresponding to each of the one or more events, and the third information represents a corresponding relationship between one or more subscription intentions and events;
[0129] The second request includes the seventh information.
[0130] Here, the sixth information may specifically include a list of user identifiers corresponding to each subscription intent, the user identifier list including one or more user identifiers, each user identifier being used to identify a user, wherein specific types of user identifiers may include a user permanent identifier (SUPI, SUbs cription Permanent Identifier), a mobile station international integrated services digital network number (MSISDN, Mobile Station international Integrated Services Digital Network number) or an Internet Protocol Multimedia Public Identity (IMPU, Internet Protocol Multimedia Public Identity), a general public user identifier (GPSI, Generic Public Subs cription Identifier) and other types.
[0131] In actual application, after receiving the first request, the first function can use the first information and the third information (i.e., the correspondence between subscription intent and event) to determine which events each subscription intent contained in the first request corresponds to; at the same time, the first information and the sixth information can be used to determine which users each subscription intent contained in the first request corresponds to; and then the first function can associate the event corresponding to each subscription intent with the user, thereby determining the seventh information, that is, the first function can determine that the user range of each event corresponding to the subscription intent includes one or more users corresponding to the subscription intent.
[0132] After determining the seventh information, in step 303, when the first function sends a second request to the third function, the second request may include the event identifiers of all events associated with the third function, and the user identifier corresponding to each of the events (i.e., the seventh information). Accordingly, after receiving the second request including the seventh information, the third function may use the second request to determine which events need to be subscribed and which users correspond to each event, and perform corresponding configuration to complete the event subscription.
[0133] In actual application, after the event subscription is completed, for each event, the third function can send an event notification of the event to the first function under specific circumstances associated with the event, and include a user identifier corresponding to the event in the event notification, and the user identifier is used to indicate the user corresponding to the event notification; accordingly, in step 304, the first function receives the event notification of the event sent by the third function.
[0134] After step 304, the first function can combine all event notifications received using the user identifier contained in each event notification, and combine all event notifications corresponding to the same user into a new event notification. In this way, in step 305, the first function can send the combined event notification to the second function, so that the second function can obtain all event notifications for the same user at one time, which can simplify the subsequent processing flow.
[0135] Based on this, in one embodiment, the event notification sent by each third function includes fourth information and eighth information, the fourth information is used to identify the event associated with the event notification, and the eighth information is used to identify one or more users corresponding to each of the one or more events. The specific implementation of step 305 may include:
[0136] Using the fourth information and the eighth information, all received event notifications are merged to obtain one or more event notifications corresponding to each user; and one or more event notifications corresponding to each user are sent to the second function.
[0137] Of course, the first function may not perform the above combination processing, and directly send each received event notification to the second function. That is to say, in one embodiment, the specific implementation of step 305 may include:
[0138] Each event notification received is sent directly to the second function.
[0139] Accordingly, the embodiment of the present application also provides an event subscription method, applying the second function, such as Figure 4 As shown, the method includes:
[0140] Step 401: Send a first request to a first function, where the first request is used to request event subscription, and the first request includes first information, where the first information represents one or more subscription intentions;
[0141] Step 402: Receive an event notification sent by the first function.
[0142] Here, in actual application, when the second function needs to subscribe to an event, in step 401, a first request may be sent to the first function, and one or more subscription intents may be included in the first request, that is, the second function informs the first function of which intents need to be related to event subscriptions; accordingly, the first function receives the first request sent by the second function, obtains one or more subscription intents for which the second function needs to subscribe to events, and implements event subscription based on the granularity of subscription intent through subsequent steps, that is, subscribing to one or more events related to the subscription intent. In this way, the second function does not need to know the event identifier used by the network operator in advance, but only needs to provide the subscription intent to implement event subscription. Since the subscription intent reflects the purpose of subscribing to the event, it is more general than a specific event identifier. Therefore, even if the network operator changes or adds event identifiers, the second function does not need to frequently synchronize all event identifiers with the network operator, which is highly flexible, thereby achieving efficient event subscription.
[0143] In actual application, after the first function completes the event subscription, it can receive event notifications sent by one or more functions providing event notification services related to the first request, and forward the received event notifications to the second function; accordingly, in step 402, the second function receives the event notification sent by the first function.
[0144] Specifically, the first function may include a subscription intent corresponding to the event notification in the sent event notification, so that the second function can determine which subscription intent the received event notification is associated with without knowing the event identifier.
[0145] Based on this, in one embodiment, the event notification sent by the first function includes fifth information, and the fifth information represents the subscription intent corresponding to the event associated with the event notification.
[0146] At the same time, the first function can also combine all event notifications received using the user identifier contained in each event notification, combine all event notifications corresponding to the same user into a new event notification, and send the combined event notification to the second function, so that the second function can obtain all event notifications for the same user at one time, which can simplify the subsequent processing process.
[0147] Based on this, in one embodiment, the specific implementation of step 402 may include:
[0148] Receive an event notification corresponding to each user sent by the first function;
[0149] Of course, the first function may not perform the above combination processing, and directly send each received event notification to the second function. That is to say, in one embodiment, the specific implementation of step 402 may include:
[0150] Receive each event notification sent directly by the first function.
[0151] Accordingly, the embodiment of the present application further provides an event subscription method, applying a third function, wherein the third function is at least used to send event notifications, such as Figure 5 As shown, the method includes:
[0152] Step 501: receiving a second request sent by a first function, the second request being used to request a subscription to one or more events associated with a third function, the second request comprising seventh information, the seventh information being used to identify one or more users corresponding to each of the one or more events;
[0153] Step 502: Utilize the seventh information to perform subscription processing on each of the one or more users, and send an event notification to the first function.
[0154] Here, in actual application, the first function may send a second request to the third function to subscribe to one or more events associated with the third function, that is, the first function calls the event notification service provided by each third function, wherein the second request may include the event identifiers of all events associated with the third function, and the user identifier corresponding to each event in all the events (that is, the seventh information); accordingly, in step 501, the third function receives the second request containing the seventh information sent by the first function.
[0155] After receiving the second request including the seventh information, in step 502, the third function can use the second request to determine which events need to be subscribed and which users each event corresponds to, and perform corresponding configuration to complete event subscription.
[0156] In actual application, after the event subscription is completed, for each event, the third function can send an event notification of the event to the first function under specific circumstances associated with the event; wherein the event notification can specifically include an event identifier, or include the event identifier and the user identifier corresponding to the event.
[0157] Based on this, in one embodiment, the event notification sent includes fourth information, or the event notification sent includes fourth information and eighth information, the fourth information is used to identify the event associated with the event notification, and the eighth information is used to identify one or more users corresponding to each of the one or more events.
[0158] Accordingly, the present application embodiment also provides an event subscription method, such as Figure 6 As shown, the method includes:
[0159] Step 601: The second function sends a first request to the first function, where the first request is used to request event subscription, and the first request includes first information, where the first information represents one or more subscription intentions;
[0160] Step 602: The first function receives a first request sent by the second function;
[0161] Step 603: The first function uses the first information to determine second information, where the second information represents one or more events corresponding to the one or more subscription intents;
[0162] Step 604: the first function sends a second request to one or more third functions corresponding to the one or more events, the third functions are at least used to send event notifications, and the second request is used to request to subscribe to one or more events associated with the third function in the one or more events;
[0163] Among them, the first request may include seventh information, and the seventh information is used to identify one or more users corresponding to each of the one or more events; at this time, the third function receives a second request sent by the first function, and the second request is used to request subscription to one or more events associated with the third function, and the second request includes the seventh information; the third function uses the seventh information to perform subscription processing on each of the one or more users.
[0164] Step 605: The first function receives one or more event notifications sent by the third function;
[0165] Step 606: The first function sends the received event notification to the second function;
[0166] Step 607: The second function receives the event notification sent by the first function.
[0167] Here, it should be noted that the specific processing procedures of the first function, the second function, the third function and the terminal have been described in detail above and will not be repeated here.
[0168] In addition, the functions (i.e., the first function, the second function, and the third function) that implement the above operations in the embodiments of the present application may also be referred to as network elements or network functions, etc., and the embodiments of the present application do not limit this.
[0169] In the event subscription method provided by the embodiment of the present application, the second function sends a first request to the first function, the first request is used to request event subscription, the first request includes first information, the first information represents one or more subscription intentions; the first function receives the first request sent by the second function; the first function uses the first information to determine the second information, the second information represents one or more events corresponding to the one or more subscription intentions; the first function sends a second request to one or more third functions corresponding to the one or more events, the third function is at least used to send event notifications, the second request is used to request subscription to one or more events associated with the third function in the one or more events; the first function receives one or more event notifications sent by the third function; the first function sends the received event notification to the second function; the second function receives the event notification sent by the first function. In the scheme provided by the embodiment of the present application, the second function sends one or more subscription intentions to the first function, the first function can determine the corresponding event according to the subscription intention, and subscribe to the event through the third function, so that event subscription based on subscription intention granularity can be realized, with high flexibility, and efficient event subscription can be realized.
[0170] The present application is described in further detail below in conjunction with application examples.
[0171] The process of the event subscription enhancement solution provided by this application example is as follows Figure 7 As shown, the following steps are included:
[0172] Step 701: AF (i.e., the second function) sends a subscription request (i.e., the first request) to NEF (i.e., the first function), wherein the subscription request includes multiple subscription intents (i.e., the first information) and a user list corresponding to each subscription intent (i.e., the sixth information);
[0173] Here, AF can specifically call Nnef_EventExposure_Subscribe service of NEF to subscribe to events, that is, AF sends a subscription request to NEF through Nnef_EventExposure_Subscribe message.
[0174] For example, it is assumed that the subscription request sent by AF carries three subscription intents, namely, Figure 1 、Subscribe Figure 2 、Subscribe Figure 3 , and a user list corresponding to each subscription intent (which can also be understood as a user set or user range), the user list contains the user identifier of the user corresponding to the subscription intent, and the subscription intent may specifically include the following information:
[0175] Subscribe Figure 1: User IMS network status, user list: IMPU1, IMPU2, IMPU3;
[0176] Subscribe Figure 2 : User IMSDC status, user list: IMPU2, IMPU3, IMPU4;
[0177] Subscribe Figure 2 : User 5G network status, user list: GPSI1, GPSI2, GPSI3.
[0178] Step 702: The NEF receives the subscription request, and determines, according to the subscription request, the event corresponding to each subscription intent (i.e., the second information), and the network element providing the event notification service associated with the subscription request;
[0179] Here, step 702 can also be understood as NEF translating the subscription intent into a specific event identifier list, thereby splitting the subscription request according to different event subscription intents.
[0180] The network element providing the event notification service may specifically include UDM, HSS, DCSF, IMS AS, etc.
[0181] Exemplarily, based on the above example, as shown in Table 1, NEF can determine which events each subscription intent corresponds to and the event identifier of each event (such as event ID) according to the correspondence table between subscription intents and predefined subscription intents and events (ie, the third information above).
[0182]
[0183]
[0184] Table 1
[0185] After determining the events corresponding to each subscription intent, NEF can further determine the network element that provides event notification services for each event. Specifically, NEF can determine that the four events with event ID = 1, 2, 3, 4 can be provided with event notification services by DCSF; the four events with event ID = 5, 6, 7 can be provided with event notification services by IMS AS; and the four events with event ID = 8, 9, 10 can be provided with event notification services by UDM.
[0186] Step 703: NEF calls the subscription service of each network element that provides event notification service;
[0187] Specifically, the NEF may send a subscription request (ie, the second request) to each determined network element respectively, wherein the subscription request includes a list of event identifiers that need to be subscribed to for the network element and a corresponding list of user identifiers.
[0188] Exemplarily, based on the above example, NEF may send a subscription request to IMS AS, the subscription request including an event identifier list (event ID=1, 2, 3, 4), and a user identifier list (IMPU1, IMPU2, IMPU3); at the same time, NEF may send a subscription request to DCSF, the subscription request including an event identifier list (event ID=5, 6, 7), and a user identifier list (IMPU2, IMPU3, IMPU4); at the same time, NEF may send a subscription request to UDM, the subscription request including an event identifier list (event ID=8, 9, 10), and a user identifier list (GPSI1, GPSI2, GPSI3).
[0189] Step 704: After receiving the subscription request, the network element providing the event notification service subscribes to the event according to the subscription request;
[0190] Step 705: NEF feeds back response information to AF, where the response information indicates that event subscription is completed;
[0191] Here, NEF may send response information to AF via Nnef_EventExposure_Subscribe response message.
[0192] Step 706: The NEF receives the event notification sent by the network element providing the event notification service;
[0193] Each time notification may carry event information such as event ID, event description, and user ID.
[0194] Step 707: NEF uses all received event notifications to merge all event notifications for the same user into one event notification, and translates the event identifier in the event notification into a subscription intent;
[0195] Exemplarily, based on the above example, as shown in Table 2, NEF can determine the subscription intent corresponding to the received event notification, and then merge all event notifications of the same user into one event notification, and include the subscription intent in the merged event notification. The above process can also be understood as merging event notifications based on users (or user identifiers).
[0196]
[0197] Table 2
[0198] Step 708: NEF sends the merged event notification to AF.
[0199] Here, NEF may specifically call Nnef_EventExposure_Notify service to send event notification, that is, NEF sends event notification to AF through Nnef_EventExposure_Notify message.
[0200] In the solution provided by the application example of this application, AF sends one or more subscription intents to NEF, and NEF can determine the corresponding event according to the subscription intent, and subscribe to the event through Wang Yuan, which provides the event notification service. In this way, by enhancing the event subscription notification of NEF, an efficient event subscription notification mechanism based on intent is realized;
[0201] At the same time, the subscription request carries the subscription intent differentiated by type instead of the specific event identifier, which can achieve more flexible event subscription and thus achieve efficient event subscription;
[0202] At the same time, the subscription request contains a list of user identifiers of one or more users corresponding to each subscription intent to indicate the user scope of the subscription, which can support unified subscription of events related to the combination of any multiple users, thereby realizing efficient event subscription.
[0203] In order to implement the method of the first functional side of the embodiment of the present application, the embodiment of the present application also provides an event subscription device, which is set on the first functional side, such as Figure 8 As shown, the device comprises:
[0204] The first processing unit 801 is configured to receive a first request sent by a second function, the first request being used to request event subscription, the first request including first information, the first information representing one or more subscription intentions; and determine second information using the first information, the second information representing one or more events corresponding to the one or more subscription intentions;
[0205] The subscription unit 802 is used to send a second request to one or more third functions corresponding to the one or more events, where the third function is at least used to send event notifications, and the second request is used to request subscription to one or more events associated with the third function in the one or more events; receive event notifications sent by one or more third functions; and send the received event notifications to the second function.
[0206] In one embodiment, the first processing unit 801 is specifically configured to:
[0207] The second information is determined by using the first information and the third information, wherein the third information represents a correspondence between one or more subscription intentions and events.
[0208] In one embodiment, each event notification sent by the third function includes fourth information, where the fourth information is used to identify an event associated with the event notification, and the subscription unit 802 is specifically used to:
[0209] Determine fifth information by using the fourth information and the third information, wherein the fifth information represents a subscription intent corresponding to an event associated with the event notification, and the third information represents a correspondence between one or more subscription intents and the event;
[0210] The event notification sent to the second function includes the fifth information.
[0211] In one embodiment, the first request further includes sixth information, where the sixth information represents one or more users corresponding to each of the one or more subscription intents; and the first processing unit 801 is further configured to:
[0212] Determine seventh information by using the first information, the third information and the sixth information, wherein the seventh information is used to identify one or more users corresponding to each of the one or more events, and the third information represents a corresponding relationship between one or more subscription intentions and events;
[0213] The second request includes the seventh information.
[0214] In one embodiment, the event notification sent by each third function includes fourth information and eighth information, the fourth information is used to identify the event associated with the event notification, the eighth information is used to identify one or more users corresponding to each of the one or more events, and the subscription unit 802 is specifically used to:
[0215] Using the fourth information and the eighth information, merging all received event notifications to obtain one or more event notifications corresponding to each user; sending the one or more event notifications corresponding to each user to the second function;
[0216] Alternatively, the subscription unit 802 is specifically configured to:
[0217] Each event notification received is sent directly to the second function.
[0218] In actual application, the first processing unit 801 and the subscription unit 802 can be implemented by a processor in the event subscription device in combination with a communication interface.
[0219] In order to implement the method of the second function side of the embodiment of the present application, the embodiment of the present application also provides an event subscription device, which is set on the second function, such as Fig. 9 As shown, the device comprises:
[0220] A first sending unit 901 is configured to send a first request to a first function, where the first request is used to request event subscription, and the first request includes first information, where the first information represents one or more subscription intentions;
[0221] The first receiving unit 902 is used to receive the event notification sent by the first function.
[0222] In one embodiment, the first receiving unit 902 is specifically configured to:
[0223] Receive an event notification corresponding to each user sent by the first function;
[0224] or,
[0225] Receive each event notification sent directly by the first function.
[0226] In actual application, the first sending unit 901 and the first sending unit 901 can be implemented by a processor in the event subscription device in combination with a communication interface.
[0227] In order to implement the method on the third function side of the embodiment of the present application, the embodiment of the present application also provides an event subscription device, which is set on the third function, and the third function is at least used to send event notifications, such as Fig.10 As shown, the device comprises:
[0228] The second receiving unit 1001 is used to receive a second request sent by the first function, where the second request is used to request to subscribe to one or more events associated with the third function, and the second request includes seventh information, where the seventh information is used to identify one or more users corresponding to each of the one or more events;
[0229] The second processing unit 1002 is used to use the seventh information to perform subscription processing on each of the one or more users, and send an event notification to the first function.
[0230] In actual application, the second receiving unit 1001 can be implemented by a communication interface in the event subscription device, and the second processing unit 1002 can be implemented by a processor in the event subscription device in combination with the communication interface.
[0231] It should be noted that: the event subscription device provided in the above embodiment only uses the division of the above program units as an example when performing event subscription. In actual applications, the above processing can be assigned to different program units as needed, that is, the internal structure of the device is divided into different program units to complete all or part of the processing described above. In addition, the event subscription device provided in the above embodiment and the event subscription method embodiment belong to the same concept. The specific implementation process is detailed in the method embodiment and will not be repeated here.
[0232] Based on the hardware implementation of the above program module, and in order to implement the method of the first functional side of the embodiment of the present application, the embodiment of the present application also provides a first function, such as Fig.11 As shown, the first function 1100 includes:
[0233] The first communication interface 1101 is capable of exchanging information with other devices;
[0234] A first processor 1102 is connected to the first communication interface 1101 to implement information interaction with other devices, and is used to execute the method provided by one or more technical solutions of the first functional side when running a computer program;
[0235] A first memory 1103 , on which the computer program is stored.
[0236] Specifically, the first communication interface 1101 is used to receive a first request sent by a second function, the first request is used to request event subscription, the first request includes first information, and the first information represents one or more subscription intentions; send a second request to one or more third functions corresponding to one or more events corresponding to the one or more subscription intentions, the third function is at least used to send event notifications, and the second request is used to request subscription to one or more events associated with the third function in the one or more events; receive one or more event notifications sent by the third function; and send the received event notification to the second function;
[0237] The first processor 1102 is configured to determine second information using the first information, where the second information represents one or more events corresponding to the one or more subscription intents.
[0238] In one embodiment, the first processor 1102 is specifically configured to:
[0239] The second information is determined by using the first information and the third information, wherein the third information represents a correspondence between one or more subscription intentions and events.
[0240] In one embodiment, each event notification sent by the third function includes fourth information, where the fourth information is used to identify an event associated with the event notification, and the first processor 1102 is specifically configured to:
[0241] In combination with the first communication interface 1101, fifth information is determined by using the fourth information and the third information, wherein the fifth information represents a subscription intent corresponding to an event associated with the event notification, and the third information represents a correspondence between one or more subscription intents and an event;
[0242] The event notification sent to the second function includes the fifth information.
[0243] In one embodiment, the first request further includes sixth information, where the sixth information represents one or more users corresponding to each subscription intent of the one or more subscription intents; and the first processor 1102 is further configured to:
[0244] Determine seventh information by using the first information, the third information and the sixth information, wherein the seventh information is used to identify one or more users corresponding to each of the one or more events, and the third information represents a corresponding relationship between one or more subscription intentions and events;
[0245] The second request includes the seventh information.
[0246] In one embodiment, the event notification sent by each third function includes fourth information and eighth information, the fourth information is used to identify the event associated with the event notification, and the eighth information is used to identify one or more users corresponding to each of the one or more events. The first processor 1102 is specifically configured to:
[0247] In combination with the first communication interface 1101, using the fourth information and the eighth information, all received event notifications are merged to obtain one or more event notifications corresponding to each user; and one or more event notifications corresponding to each user are sent to the second function;
[0248] or,
[0249] The first communication interface 1101 is specifically used to directly send each received event notification to the second function.
[0250] It should be noted that the specific processing process of the first processor 1102 and the first communication interface 1101 can be understood by referring to the above method.
[0251] Of course, in actual application, the various components in the first function 1100 are coupled together through the bus system 1104. It can be understood that the bus system 1104 is used to realize the connection and communication between these components. In addition to the data bus, the bus system 1104 also includes a power bus, a control bus, and a status signal bus. However, for the sake of clarity, Fig.11 Various buses are labeled as bus system 1104 .
[0252] The first memory 1103 in the embodiment of the present application is used to store various types of data to support the operation of the first terminal 1100. Examples of such data include: any computer program used to operate on the first terminal 1100.
[0253] The method disclosed in the above embodiment of the present application can be applied to the first processor 1102, or implemented by the first processor 1102. The first processor 1102 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by an integrated logic circuit of hardware or software instructions in the first processor 1102. The above-mentioned first processor 1102 may be a general-purpose processor, a digital signal processor (DSP, Digital Signal Processor), or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. The first processor 1102 can implement or execute the various methods, steps and logic block diagrams disclosed in the embodiments of the present application. A general-purpose processor may be a microprocessor or any conventional processor, etc. In combination with the steps of the method disclosed in the embodiment of the present application, it can be directly embodied as a hardware decoding processor to execute, or it can be executed by a combination of hardware and software modules in the decoding processor. The software module may be located in a storage medium, which is located in the first memory 1103, and the first processor 1102 reads the information in the first memory 1103, and completes the steps of the above method in combination with its hardware.
[0254] In an exemplary embodiment, the first function 1100 can be implemented by one or more application specific integrated circuits (ASIC), DSP, programmable logic device (PLD), complex programmable logic device (CPLD), field programmable gate array (FPGA), general processor, controller, microcontroller (MCU), microprocessor, or other electronic components to execute the aforementioned method.
[0255] Based on the hardware implementation of the above program module, and in order to implement the method of the second functional side of the embodiment of the present application, the embodiment of the present application also provides a second function, such as Fig.12 As shown, the second function 1200 includes:
[0256] The second communication interface 1201 is capable of exchanging information with other devices;
[0257] The second processor 1202 is connected to the second communication interface 1201 to implement information interaction with other devices, and is used to execute the method provided by one or more technical solutions of the second functional side when running the computer program;
[0258] A second memory 1203 , on which the computer program is stored.
[0259] Specifically, the second processor 1202 is configured to:
[0260] In combination with the second communication interface 1201, a first request is sent to a first function, where the first request is used to request event subscription, and the first request includes first information, where the first information represents one or more subscription intentions; and an event notification sent by the first function is received.
[0261] In one embodiment, the second communication interface 1201 is specifically used for:
[0262] Receive an event notification corresponding to each user sent by the first function;
[0263] or,
[0264] Receive each event notification sent directly by the first function.
[0265] It should be noted that the specific processing process of the second processor 1202 and the second communication interface 1201 can be understood by referring to the above method.
[0266] Of course, in actual application, the various components in the second function 1200 are coupled together through the bus system 1204. It can be understood that the bus system 1204 is used to realize the connection and communication between these components. In addition to the data bus, the bus system 1204 also includes a power bus, a control bus, and a status signal bus. However, for the sake of clarity, Fig.12 Various buses are labeled as bus system 1204.
[0267] The second memory 1203 in the embodiment of the present application is used to store various types of data to support the operation of the second function 1200. Examples of such data include: any computer program used to operate on the second function 1200.
[0268] The method disclosed in the above embodiment of the present application can be applied to the second processor 1202, or implemented by the second processor 1202. The second processor 1202 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the hardware integrated logic circuit or software instructions in the second processor 1202. The above-mentioned second processor 1202 may be a general-purpose processor, DSP, or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. The second processor 1202 can implement or execute the various methods, steps and logic block diagrams disclosed in the embodiments of the present application. A general-purpose processor may be a microprocessor or any conventional processor, etc. In combination with the steps of the method disclosed in the embodiment of the present application, it can be directly embodied as a hardware decoding processor to execute, or it can be executed by a combination of hardware and software modules in the decoding processor. The software module may be located in a storage medium, which is located in the second memory 1203, and the second processor 1202 reads the information in the second memory 1203 and completes the steps of the above method in combination with its hardware.
[0269] In an exemplary embodiment, the second function 1200 may be implemented by one or more ASICs, DSPs, PLDs, CPLDs, FPGAs, general purpose processors, controllers, MCUs, Microprocessors, or other electronic components to perform the aforementioned method.
[0270] Based on the hardware implementation of the above program modules, and in order to implement the method of the third functional side of the embodiment of the present application, the embodiment of the present application also provides a third function, such as Fig.13 As shown, the third function 1300 includes:
[0271] The third communication interface 1301 is capable of exchanging information with other devices;
[0272] A third processor 1302 is connected to the third communication interface 1301 to implement information interaction with other devices, and is used to execute the method provided by one or more technical solutions of the third functional side when running a computer program;
[0273] A third memory 1303 , on which the computer program is stored.
[0274] Specifically, the third communication interface 1301 is used to:
[0275] receiving a second request sent by a first function, the second request being used to request a subscription to one or more events associated with a third function, the second request comprising seventh information, the seventh information being used to identify one or more users corresponding to each of the one or more events; and sending an event notification to the first function;
[0276] The third processor 1302 is configured to perform subscription processing on each of the one or more users by using the seventh information.
[0277] It should be noted that the specific processing process of the third processor 1302 and the third communication interface 1301 can be understood by referring to the above method.
[0278] Of course, in actual application, the various components in the third function 1300 are coupled together through the bus system 1304. It can be understood that the bus system 1304 is used to realize the connection and communication between these components. In addition to the data bus, the bus system 1304 also includes a power bus, a control bus, and a status signal bus. However, for the sake of clarity, Fig.13 Various buses are labeled as bus system 1304.
[0279] The third memory 1303 in the embodiment of the present application is used to store various types of data to support the operation of the third function 1300. Examples of such data include: any computer program used to operate on the third function 1300.
[0280] The method disclosed in the above embodiment of the present application can be applied to the third processor 1302, or implemented by the third processor 1302. The third processor 1302 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by an integrated logic circuit of hardware or software instructions in the third processor 1302. The third processor 1302 mentioned above can be a general-purpose processor, a DSP, or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. The third processor 1302 can implement or execute the various methods, steps and logic block diagrams disclosed in the embodiments of the present application. A general-purpose processor can be a microprocessor or any conventional processor, etc. In combination with the steps of the method disclosed in the embodiment of the present application, it can be directly embodied as a hardware decoding processor to execute, or it can be executed by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium, which is located in the third memory 1303. The third processor 1302 reads the information in the third memory 1303 and completes the steps of the above method in combination with its hardware.
[0281] In an exemplary embodiment, the third function 1300 may be implemented by one or more ASICs, DSPs, PLDs, CPLDs, FPGAs, general purpose processors, controllers, MCUs, Microprocessors, or other electronic components to perform the aforementioned method.
[0282] It can be understood that the memory (first memory 1103, second memory 1203, third memory 1303) of the embodiment of the present application can be a volatile memory or a non-volatile memory, and can also include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a magnetic random access memory (FRAM), a ferromagnetic random access memory, a flash memory, a magnetic surface memory, an optical disc, or a compact disc read-only memory (CD-ROM); the magnetic surface memory can be a disk memory or a tape memory. The volatile memory can be a random access memory (RAM), which is used as an external cache.By way of example but not limitation, many forms of RAM are available, such as static random access memory (SRAM), synchronous static random access memory (SSRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), direct memory bus random access memory (DRRAM). The memory described in the embodiments of the present application is intended to include but is not limited to these and any other suitable types of memory.
[0283] In an exemplary embodiment, the embodiment of the present application further provides a storage medium, namely a computer storage medium, specifically a computer-readable storage medium, for example, including a first memory 1103 storing a computer program, the computer program can be executed by the first processor 1102 of the first function 1100 to complete the steps of the first function side method, for example, including a second memory 1203 storing a computer program, the computer program can be executed by the second processor 1202 of the second function 1200 to complete the steps of the second function side method, for example, including a third memory 1303 storing a computer program, the computer program can be executed by the third processor 1302 of the third function 1300 to complete the steps of the third function side method. The computer-readable storage medium can be a memory such as FRAM, ROM, PROM, EPROM, EEPROM, FlashMemory, magnetic surface memory, optical disk, or CD-ROM.
[0284] In an exemplary embodiment, the embodiment of the present application also provides a computer program product, including a computer program, which can be executed by the first processor 1102 of the first function 1100 to complete the steps of the aforementioned first function side method, or, the computer program can be executed by the second processor 1202 of the second function 1200 to complete the steps of the aforementioned second function side method, or, the computer program can be executed by the third processor 1302 of the third function 1300 to complete the steps of the aforementioned third function side method.
[0285] In order to implement the method of the embodiment of the present application, the embodiment of the present application also provides an event subscription system, such as Fig.14 As shown, the system includes: a first function 1401 , a second function 1402 , and one or more third functions 1403 .
[0286] It should be noted here that the specific processing procedures of the first function 1401, the second function 1402, and the third function 1403 have been described in detail above and will not be repeated here.
[0287] It should be noted that: "first", "second", etc. are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.
[0288] In addition, the technical solutions described in the embodiments of the present application can be combined arbitrarily without conflict.
[0289] The above description is only a preferred embodiment of the present application and is not intended to limit the protection scope of the present application.
Claims
1. An event subscription method, characterized in that: Applied to the first function, including: receiving a first request sent by a second function, where the first request is used to request event subscription, and the first request includes first information, where the first information represents one or more subscription intentions; Determine second information using the first information, where the second information represents one or more events corresponding to the one or more subscription intents; Sending a second request to one or more third functions corresponding to the one or more events, where the third functions are at least used to send event notifications, and the second request is used to request to subscribe to one or more events associated with the third functions in the one or more events; receiving event notifications sent by one or more of the third functions; The received event notification is sent to the second function.
2. The method according to claim 1, characterized in that: The using the first information to determine the second information includes: The second information is determined by using the first information and the third information, wherein the third information represents a correspondence between one or more subscription intentions and events.
3. The method according to claim 1, characterized in that Each event notification sent by the third function includes fourth information, where the fourth information is used to identify an event associated with the event notification, and sending the event notification to the second function includes: Determine fifth information by using the fourth information and the third information, wherein the fifth information represents a subscription intent corresponding to an event associated with the event notification, and the third information represents a correspondence between one or more subscription intents and the event; The event notification sent to the second function includes the fifth information.
4. The method according to claim 1, characterized in that The first request further includes sixth information, wherein the sixth information represents one or more users corresponding to each subscription intent of the one or more subscription intents; and the method further includes: Determine seventh information by using the first information, the third information and the sixth information, wherein the seventh information is used to identify one or more users corresponding to each of the one or more events, and the third information represents a corresponding relationship between one or more subscription intentions and events; The second request includes the seventh information.
5. The method according to claim 1, characterized in that The event notification sent by each third function includes fourth information and eighth information, wherein the fourth information is used to identify an event associated with the event notification, and the eighth information is used to identify one or more users corresponding to the event notification, and the sending of the event notification to the second function includes: Using the fourth information and the eighth information, merging all received event notifications to obtain one or more event notifications corresponding to each user; sending the one or more event notifications corresponding to each user to the second function; Alternatively, the sending the event notification to the second function includes: Each event notification received is sent directly to the second function.
6. The method according to any one of claims 1 to 5, characterized in that: The first function is at least used for network capability exposure, and / or the second function is at least used for providing application services.
7. An event subscription method, characterized in that: Applied to the second function, including: Sending a first request to a first function, where the first request is used to request event subscription, and the first request includes first information, where the first information represents one or more subscription intentions; Receive an event notification sent by the first function.
8. The method according to claim 7, characterized in that The event notification sent by the first function includes fifth information, and the fifth information represents a subscription intent corresponding to the event associated with the event notification.
9. The method according to claim 7, characterized in that: The receiving the event notification sent by the first function includes: Receive an event notification corresponding to each user sent by the first function; or, Receive each event notification sent directly by the first function.
10. The method according to any one of claims 7 to 9, characterized in that: The first function is at least used for network capability exposure, and / or the second function is at least used for providing application services.
11. An event subscription method, characterized in that: Applied to a third function, the third function being at least used to send an event notification, including: receiving a second request sent by the first function, the second request being used to request a subscription to one or more events associated with the third function, the second request comprising seventh information, the seventh information being used to identify one or more users corresponding to each of the one or more events; The seventh information is used to perform subscription processing on each of the one or more users, and an event notification is sent to the first function.
12. The method according to claim 11, characterized in that The event notification sent includes fourth information, or the event notification sent includes fourth information and eighth information, wherein the fourth information is used to identify an event associated with the event notification, and the eighth information is used to identify one or more users corresponding to each of the one or more events.
13. The method according to claim 11, characterized in that The first function is at least used for network capability exposure.
14. An event subscription device, characterized in that: Set up in the first function, including: A first processing unit is configured to receive a first request sent by a second function, the first request being used to request event subscription, the first request including first information, the first information representing one or more subscription intentions; and determine second information using the first information, the second information representing one or more events corresponding to the one or more subscription intentions; A subscription unit, used to send a second request to one or more third functions corresponding to the one or more events, wherein the third function is at least used to send event notifications, and the second request is used to request subscription to one or more events associated with the third function in the one or more events; receive event notifications sent by one or more third functions; and send the received event notifications to the second function.
15. An event subscription device, characterized in that: Settings in the second function include: A first sending unit, configured to send a first request to a first function, where the first request is used to request event subscription, and the first request includes first information, where the first information represents one or more subscription intentions; The first receiving unit is used to receive the event notification sent by the first function.
16. An event subscription device, characterized in that: The third function is set to at least send an event notification, including: A second receiving unit is configured to receive a second request sent by the first function, the second request being used to request a subscription to one or more events associated with the third function, the second request comprising seventh information, the seventh information being used to identify one or more users corresponding to each of the one or more events; The second processing unit is used to use the seventh information to perform subscription processing on each of the one or more users and send an event notification to the first function.
17. A first function, characterized in that, include: A first processor and a first communication interface; wherein, The first communication interface is used to receive a first request sent by a second function, the first request is used to request event subscription, the first request includes first information, the first information represents one or more subscription intentions; send a second request to one or more third functions corresponding to one or more events corresponding to the one or more subscription intentions, the third function is at least used to send event notifications, the second request is used to request subscription to one or more events associated with the third function in the one or more events; receive one or more event notifications sent by the third function; and send the received event notifications to the second function; The first processor is used to determine second information using the first information, where the second information represents one or more events corresponding to the one or more subscription intents.
18. A second function, characterized in that, include: A second processor and a second communication interface; wherein, The second communication interface is used to send a first request to the first function, where the first request is used to request event subscription, and the first request includes first information, where the first information represents one or more subscription intentions; And receiving an event notification sent by the first function.
19. A third function, characterized in that, The third function is at least used to send event notifications, including: a third processor and a third communication interface; wherein, The third communication interface is configured to receive a second request sent by the first function, the second request being used to request a subscription to one or more events associated with the third function, the second request comprising seventh information, the seventh information being used to identify one or more users corresponding to each of the one or more events; and send an event notification to the first function; The third processor is used to perform subscription processing on each of the one or more users by using the seventh information.
20. A first function, characterized in that include: a first processor and a first memory for storing a computer program executable on the processor, Wherein, when the first processor is used to run the computer program, the steps of the method described in any one of claims 1 to 6 are executed.
21. A second function, characterized in that: include: a second processor and a second memory for storing a computer program executable on the processor, Wherein, when the second processor is used to run the computer program, the steps of the method described in any one of claims 7 to 10 are executed.
22. A third function, characterized in that, include: a third processor and a third memory for storing a computer program executable on the processor, Wherein, the third processor is used to execute the steps of the method described in any one of claims 11 to 13 when running the computer program.
23. A storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, it implements the steps of the method described in any one of claims 1 to 6, or implements the steps of the method described in any one of claims 7 to 10, or implements the steps of the method described in any one of claims 11 to 13.
24. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, it implements the steps of the method described in any one of claims 1 to 6, or implements the steps of the method described in any one of claims 7 to 10, or implements the steps of the method described in any one of claims 11 to 13.
