Communication method and apparatus

Abstract

This application provides a communication method and apparatus. The method, applicable to data plane network elements, includes: receiving a first request message for requesting subscription to a first event, the first request message carrying at least one of the following: a notification method, a buffer duration, or descriptive information corresponding to an event consuming node. The notification method indicates whether the sender of the first request message is an event consuming node, and the buffer duration indicates the storage duration of context information corresponding to the first event; executing an event query process based on the first request message; and executing an event notification process based on the first request message. By implementing the event subscription and notification process through data plane network elements, and storing subscription / notification-related context information within the data plane network elements, event subscription and notification can be completed even if the subscription network element / event consuming node is stateless.

Description

Technical Field

[0001] This application relates to the field of communications, and particularly to communication methods and apparatus in the field of communications. Background Technology

[0002] In wireless communication, when there are event dependencies between network elements, event reporting triggered by events can be achieved through a subscription / notification mechanism. For example, a Session Management Function (SMF) network element / Policy Control Function (PCF) network element subscribes to a Terminal Location Change event from an Access and Mobility Management Function (AMF) network element and performs subsequent actions based on the event. For instance, the SMF network element selects the nearest User Plane Function (UPF) network element as the new User Plane anchor point based on the terminal's location; or the PCF network element adjusts the Quality of Service (QoS) parameters and charging policies for Protocol Data Unit (PDU) sessions based on the terminal's location.

[0003] In the existing network architecture, network elements can store context. The subscription / notification mechanism relies on the notification uniform resource identifier (URI) and correlation identifier (Correlation ID) to associate subscriptions with notifications. The notification URI indicates the target address / endpoint / subscriber / subscribing network element to receive the notification. This allows the event source node to send a notification message to the corresponding address based on the notification URI after an event occurs. However, a notification URI may be shared by multiple events. Therefore, for different subscription events, a corresponding correlation identifier can be assigned to each event. When a subscribing network element receives a notification message, it will know which event occurred and which event's context it needs to associate with. For example, network element A initiates a subscription event for user A's session A. When the notification message for the subscription event returns, network element A can modify the associated session based on the correlation identifier.

[0004] However, in a stateless architecture (i.e., network elements may release their context), it may be impossible to assign a notification URI / association identifier. This is because assigning a notification URI / association identifier to a subscription event usually requires the network element to maintain the context so that the subscription event and the notification URI / association identifier can be associated. If the network element releases the context, there is no way to maintain the association between the subscription event and the notification URI / association identifier. Therefore, the above subscription / notification mechanism cannot be implemented. Summary of the Invention

[0005] This application provides a communication method and apparatus to enable subscription and notification in a stateless architecture.

[0006] In a first aspect, this application provides a communication method that can be applied to data plane network elements, such as the data plane network element itself, or components in the data plane network element (such as processors, chips, chip systems, etc.), or logic modules or software capable of implementing all or part of the functions of the data plane network element. This application does not limit the application in this regard.

[0007] For example, the method includes: receiving a first request message for requesting subscription to a first event, the first request message carrying at least one of the following: notification method, cache duration, or description information corresponding to an event consuming node, wherein the notification method is used to indicate whether the sender of the first request message is an event consuming node, and the cache duration is used to indicate the storage duration of context information corresponding to the first event; performing an event query process based on the first request message; and performing an event notification process based on the first request message.

[0008] In the above scheme, the event subscription and notification process is implemented through data plane network elements. The data plane network elements can store the context information related to subscription / notification. In this way, even if the subscription network element / event consumer node is stateless, the event subscription and notification can still be completed.

[0009] In conjunction with the first aspect, in possible implementations of the first aspect, the first request message may further carry at least one of the following: context identification information, the identifier of the first event, the event description information corresponding to the first event, the notification type of the first event, or the notification address corresponding to the first event.

[0010] In conjunction with the first aspect, in a possible implementation of the first aspect, the above-mentioned execution of the event query process based on the first request message includes: performing context addressing based on the first request message to obtain a report of the first event; and performing an event notification process based on the first request message, including: sending a first response message to the event consumer node, wherein the first response message carries a report of the first event; or, determining, based on the cache duration, to return a report of the first event via an independent message.

[0011] In the above scheme, the event consumption node can obtain the report of the first event from the data plane network element. For example, when the sender of the first request message is the event consumption node, the data plane stores the report of the first event, and the first event supports directly returning the event report in the response message, the data plane network element can directly carry the report of the first event in the response message of the subscription request. In this way, it is beneficial to shorten the latency of obtaining the report of the first event.

[0012] In conjunction with the first aspect, in a possible implementation of the first aspect, the above-mentioned event notification process based on the first request message includes: sending a first message to a task-centric function (TCF) network element, the first message being used by the TCF network element to select an event consumer node; receiving a second request message from the event consumer node, the second request message being used to request a report of the first event; and sending a second response message to the event consumer node, the second response message carrying a report of the first event.

[0013] In the above scheme, the event consumption node can be selected through the TCF network element, thereby triggering the event consumption node to obtain the report of the first event from the data plane network element, thus realizing the event notification process for stateless network elements (such as event consumption nodes).

[0014] In conjunction with the first aspect, in a possible implementation of the first aspect, the above-mentioned execution of the event query process based on the first request message includes: receiving a context update request from the event source node, the context update request being used to request an update of context information, the context update request carrying a report of the first event.

[0015] The above event query process can be applied, for example, to scenarios where the first event is one that is reported / notified by default without subscription. After receiving the first request message, if the first event is one that is reported / notified by default without subscription, the data plane network element can obtain the report of the first event based on the above process. This facilitates the event consumer node to obtain the report from the data plane network element, thereby realizing the notification process for stateless network elements (such as event consumer nodes).

[0016] Optionally, before receiving the context update request from the event source node, the method further includes: receiving a third request message from the event source node, the third request message being used to request the acquisition of context information; and sending a third response message to the event source node, the third response message carrying the event subscription list corresponding to the first event.

[0017] In conjunction with the first aspect, in a possible implementation of the first aspect, the above-mentioned execution of the event query process based on the first request message includes: sending a subscription request based on the first request message, the subscription request being used to request subscription to the first event from the event source node; and receiving a second message from the event source node, the second message carrying a report and notification association identifier of the first event.

[0018] The above event query process can be applied, for example, to scenarios where the first event requires subscription to return a notification. After the data plane network element receives the first request message, if the first event is an event that is reported / notified by default without subscription, the subscription and notification process can be completed through the data plane network element.

[0019] Optionally, the aforementioned data plane network element is a data management function (DMF) network element, and the aforementioned receiving of the second message from the event source node includes: directly receiving the second message from the event source node; or, receiving the second message from the event source node forwarded by the data storage function (DSF) network element.

[0020] In conjunction with the first aspect, in a possible implementation of the first aspect, the aforementioned data plane network element is a DMF network element, and the aforementioned method further includes: assigning a notification association identifier to the first event and storing the subscription context information in the DSF network element; or, calling the DSF network element to perform the assignment of the notification association identifier and updating the subscription context information in the DSF network element based on the notification association identifier, wherein the aforementioned subscription context information includes one or more of the following: notification association identifier, description information corresponding to the event consumer node, or context identifier information corresponding to the first event.

[0021] Secondly, this application provides another communication method that can be applied to data plane network elements, such as the data plane network element itself, or components in the data plane network element (such as processors, chips, chip systems, etc.), or logic modules or software that can implement all or part of the functions of the data plane network element. This application does not limit the application in this regard.

[0022] For example, the method includes: receiving a fourth request message, the fourth request message being used to request the allocation of a notification association identifier for a first event; sending a fourth response message, the fourth response message carrying a notification association identifier corresponding to the first event; and receiving a notification message from a TCF network element or an event source node, the notification message carrying a report and notification association identifier for the first event.

[0023] In the above scheme, the data plane network element can perform the allocation of notification association identifier, thereby facilitating the completion of the event subscription and notification process based on this notification association identifier. Furthermore, the data plane network element can receive event notification messages to trigger the event notification process, providing a subscription and notification process for stateless network elements (such as event consumer nodes).

[0024] In conjunction with the second aspect, in possible implementations of the second aspect, receiving the fourth request message as described above includes: receiving a fourth request message from a subscribing network element; or, receiving a fourth request message from a TCF network element.

[0025] In conjunction with the second aspect, in possible implementations of the second aspect, the above method further includes: recording subscription context information, which includes one or more of the following: notification association identifier, description information corresponding to the event consumption node, and context identifier information corresponding to the first event.

[0026] By recording subscription context information, the subscription event and notification association identifier can be associated, which facilitates subsequent subscription and notification processes.

[0027] In conjunction with the second aspect, in a possible implementation of the second aspect, the above method further includes: sending a first message to the TCF network element, the first message being used by the TCF network element to select an event consumer node; receiving a second request message from the event consumer node, the second request message being used to request a report of the first event; and sending a second response message to the event consumer node, the second response message carrying the report of the first event. The above scheme provides a detailed process for event notification to facilitate event notification.

[0028] In conjunction with the second aspect, in a possible implementation of the second aspect, the aforementioned data plane network element is a DMF network element, and the aforementioned method further includes: assigning a notification association identifier to the first event and storing the subscription context information in the DSF network element; or, calling the DSF network element to perform the assignment of the notification association identifier and updating the subscription context information in the DSF network element based on the notification association identifier, wherein the aforementioned subscription context information includes one or more of the following: notification association identifier, description information corresponding to the event consumer node, and context identifier information corresponding to the first event.

[0029] Optionally, receiving notification messages from TCF network elements or event source nodes includes: directly receiving notification messages from TCF network elements or event source nodes; or receiving notification messages from TCF network elements or event source nodes that have been forwarded by DSF network elements.

[0030] Thirdly, this application provides another communication method that can be applied to TCF network elements, such as the TCF network element itself, or components in the TCF network element (such as processors, chips, chip systems, etc.), or logic modules or software that can implement all or part of the functions of the TCF network element. This application does not limit the application in this regard.

[0031] For example, the method includes: receiving a subscription request for subscribing to a first event from an event source node; and sending a third message to the event source node for subscribing to the first event from the event source node, the third message carrying a notification association identifier.

[0032] In the above scheme, the TCF network element acts as a subscriber to forward subscription requests, thereby facilitating the completion of the subscription process.

[0033] In conjunction with the third aspect, in the possible implementations of the third aspect, the subscription request mentioned above carries one or more of the following: the notification type of the first event, the event description information corresponding to the first event, the notification association identifier, or the description information corresponding to the event consumption node.

[0034] In conjunction with the third aspect, among the possible implementations of the third aspect, the above method further includes: receiving a notification message, which carries a report and notification association identifier for the first event; and sending the notification message or notification association identifier to the event consumer node.

[0035] In the above scheme, the TCF network element receives the event notification and directly returns the event notification or a notification association identifier to the event consumer node. The direct return of the event notification by the TCF network element to the event consumer node helps reduce the latency for the event consumer node to obtain the event report. The return of the notification association identifier by the TCF network element to the event consumer node facilitates the event consumer node's retrieval of the event report based on this identifier, which is applicable, for example, to scenarios with large amounts of event report information or relatively low real-time requirements.

[0036] In conjunction with the third aspect, in possible implementations of the third aspect, the above method further includes: receiving a first message from the data plane network element, the first message being used by the TCF network element to select an event consumer node; and sending a notification association identifier to the event consumer node.

[0037] In the above scheme, the TCF network element can receive the first message initiated by the data plane network element, so that the TCF network element can select the event consumption node and trigger the subsequent event notification process.

[0038] Fourthly, this application provides another communication method that can be applied to signaling distribution function (SDF) network elements, such as the SDF network element itself, or components in the SDF network element (such as processors, chips, chip systems, etc.), or logic modules or software capable of implementing all or part of the SDF network element functions. This application does not limit the application in this regard.

[0039] For example, the method includes: receiving a fourth request message, the fourth request message being used to assign a notification association identifier to a first event; receiving a notification message from a TCF network element or an event source node, the notification message carrying a report and notification association identifier of the first event; and sending a first message to the TCF network element, the first message being used by the TCF network element to select an event consumer node.

[0040] In the above scheme, the SDF network element can perform the actions of the data plane network element. For example, the SDF network element can also assign a notification association identifier, which facilitates the completion of the subscription process based on this. The SDF network element can also receive event notifications, trigger the TCF network element to initiate the first message, and thus complete the subsequent event notification process.

[0041] Fifthly, this application provides a communication apparatus for executing the methods in the first to fourth aspects and any possible implementations of the first to fourth aspects described above. Specifically, the communication apparatus includes a module for executing the methods in any possible implementations of the first to fourth aspects described above.

[0042] In a sixth aspect, this application provides another communication device, including a processor coupled to a memory, which can be used to execute instructions in the memory to implement the methods in the first to fourth aspects and any possible implementation of the first to fourth aspects.

[0043] Optionally, the communication device further includes a memory. Optionally, the communication device further includes a communication interface, to which the processor is coupled.

[0044] In one implementation, the aforementioned communication interface can be a transceiver, or an input / output interface.

[0045] In another implementation, the aforementioned communication interface can be an input / output interface.

[0046] In a seventh aspect, this application provides a processor, including: an input circuit, an output circuit, and a processing circuit. The processing circuit is configured to receive signals through the input circuit and transmit signals through the output circuit, causing the processor to execute the methods described in the first to fourth aspects and any possible implementation thereof.

[0047] In the specific implementation process, the processor can be a chip, the input circuit can be an input pin, the output circuit can be an output pin, and the processing circuit can be a transistor, gate circuit, flip-flop, and various logic circuits. The input signal received by the input circuit can be received and input by, for example, but not limited to, a receiver, and the signal output by the output circuit can be, for example, but not limited to, output to a transmitter and transmitted by the transmitter. Furthermore, the input circuit and the output circuit can be the same circuit, which is used as the input circuit and the output circuit at different times. This application does not limit the specific implementation method of the processor and various circuits.

[0048] Eighthly, this application provides a communication device including a processor and a memory. The processor is used to read instructions stored in the memory, receive signals via a receiver, and transmit signals via a transmitter to execute the methods in the first to fourth aspects and any possible implementations of the first to fourth aspects described above.

[0049] Optionally, the processor may be one or more, and the memory may be one or more.

[0050] Optionally, the memory may be integrated with the processor, or the memory may be separated from the processor.

[0051] In the specific implementation process, the memory can be a non-transitory memory, such as read-only memory (ROM), which can be integrated with the processor on the same chip or set on different chips. This application does not limit the type of memory or the way the memory and processor are set.

[0052] It should be understood that related data interaction processes, such as sending messages, can be seen as a process of the processor outputting messages, and receiving messages can be seen as a process of the processor receiving input messages. Specifically, the processed output data can be output to the transmitter, and the input data received by the processor can come from the receiver. Here, the transmitter and receiver can be collectively referred to as a transceiver.

[0053] The communication device in the eighth aspect above can be a chip. The processor can be implemented in hardware or software. When implemented in hardware, the processor can be a logic circuit, integrated circuit, etc. When implemented in software, the processor can be a general-purpose processor that reads software code stored in memory. The memory can be integrated into the processor or located outside the processor and exist independently.

[0054] Ninthly, this application provides a computer program product comprising: a computer program (also referred to as code or instructions) that, when executed, causes a computer to perform the methods described in the first to fourth aspects and any possible implementation thereof.

[0055] In a tenth aspect, this application provides a computer-readable storage medium storing a computer program (also referred to as code or instructions) that, when run on a computer, causes the computer to perform the methods described in the first to fourth aspects and any possible implementation thereof.

[0056] It should be understood that the fifth to tenth aspects of this application correspond to the technical solutions of the first to fourth aspects of this application, and the beneficial effects obtained by each aspect and the corresponding feasible implementation are similar, and will not be repeated here. Attached Figure Description

[0057] Figure 1 This is a schematic diagram of an existing network architecture;

[0058] Figure 2 This is a diagram illustrating the existing subscription / notification process;

[0059] Figure 3 This is a schematic diagram of the stateless network architecture provided in the embodiments of this application;

[0060] Figure 4 This is a schematic diagram of the data plane architecture provided in an embodiment of this application;

[0061] Figure 5 This is a flowchart illustrating the communication method provided in an embodiment of this application;

[0062] Figure 6 This is a detailed flowchart illustrating the communication method provided in the embodiments of this application;

[0063] Figure 7 This is a flowchart illustrating another communication method provided in an embodiment of this application;

[0064] Figure 8 This is a flowchart illustrating another communication method provided in an embodiment of this application;

[0065] Figure 9 This is another detailed flowchart illustrating the communication method provided in the embodiments of this application;

[0066] Figure 10 This is another detailed flowchart illustrating the communication method provided in the embodiments of this application;

[0067] Figure 11This is a schematic diagram of the interaction process within the data plane provided in the embodiments of this application;

[0068] Figure 12 This is a schematic block diagram of a communication device provided in an embodiment of this application;

[0069] Figure 13 This is a schematic block diagram of another communication device provided in the embodiments of this application. Detailed Implementation

[0070] The technical solutions of this application can be applied to various communication systems, such as Long Term Evolution (LTE) systems, 5th generation (5G) systems, new radio (NR) systems, or future communication systems. This application does not limit the scope of these systems.

[0071] The following is a combination of... Figure 1 A detailed explanation of the 5G network architecture is provided.

[0072] Figure 1 This is a schematic diagram of an existing network architecture.

[0073] like Figure 1 As shown, this network architecture includes user equipment (UE) (also referred to as a terminal, terminal equipment, or user terminal, etc.), access network (AN), and core network (CN). Figure 1 (Not shown in the image) and data network (DN), etc. The AN can be used to implement wireless physical layer functions, resource scheduling and wireless resource management, wireless access control, and mobility management; the CN can include management devices and gateway devices. The management devices are mainly used for terminal device registration, security authentication, mobility management, and location management, while the gateway devices are mainly used to establish channels with the terminal devices and forward data packets between the terminal devices and the external data network on these channels; the DN can include network devices (such as servers, routers, etc.), and the data network is mainly used to provide various data services to the terminal devices.

[0074] Understandable Figure 1For example, it could be a 5G network architecture based on service-oriented interfaces in a non-roaming scenario, where the AN in this 5G network architecture can be a radio access network (RAN). The RAN can include at least one RAN node, such as a wireless relay device and / or a wireless backhaul device. The UE can connect to the RAN node wirelessly. The RAN node connects to the CN wirelessly or via a wired connection. The CN device in the CN and the RAN node in the RAN can be different physical devices, or they can be the same physical device integrating CN logical functions and RAN logical functions.

[0075] In this 5G network architecture, the CN can include multiple functional network elements such as UPF (abbreviated as UPF in the figure, and the network elements mentioned below are similar and will not be listed again below), AMF, SMF, network exposure function (NEF) network elements, PCF network elements, unified data management (UDM) network elements, application function (AF) network elements, and unified data repository (UDR).

[0076] In this application, network element may also be referred to as functional network element, functional unit, microservice / service, network function (NF), instance, functional entity, or entity, etc., and this application does not limit it in this way.

[0077] The functions of each of the above network elements will be described in detail below.

[0078] 1. Application Filtering (AF) Element: Responsible for passing application layer requirements to the network layer, such as, but not limited to, QoS requirements or user state event subscriptions. AF elements can be third-party functional entities. When interacting with the core network, they can also undergo authorization processing via the Network Filtering (NEF). For example, an AF element can directly send a request message to a NEF element. The NEF element determines whether the AF element is authorized to send the request message. If the verification is successful, it forwards the request message to the corresponding PCF or UDM element. AF elements can also be application services deployed by operators, such as Internet Protocol Multimedia Subsystem (IMS) voice call services.

[0079] 2. UDM network element: It can be responsible for user identity processing, user access authorization, registration and mobility management, contract management, SMS management, etc.

[0080] 3. UDR network element: mainly used to implement the storage and retrieval functions of data types such as contract data, policy data, and application data.

[0081] 4. PCF Network Element: Primarily responsible for policy control such as billing, QoS bandwidth guarantee, mobility management, and UE policy decision-making at the session and service flow levels. In this network architecture, the PCF network elements connected to the AMF and SMF network elements correspond to the AM PCF (PCF for access and mobility control) and SM PCF (PCF for session management) network elements, respectively. In actual deployment scenarios, the AM PCF and SM PCF network elements may or may not be the same PCF entity; this application does not impose any restrictions on this.

[0082] 5. SMF network element: mainly responsible for session management, execution of control policies issued by PCF network element, selection of UPF network element, UE IP address management and allocation, etc.

[0083] 6. AMF (Active Mobile Component) element: Primarily responsible for mobility management, access authentication / authorization, etc. In addition, the AMF element is also responsible for transmitting user policies between the UE and the PCF (Programmable Component) element.

[0084] 7. UPF network element: As an interface with the data network, it is used for user plane data forwarding, session / flow-based billing statistics, bandwidth limiting, etc.

[0085] It should be noted that these network elements can work independently or be combined to implement certain functions, such as access control and mobility management functions for terminal devices, including access authentication, security encryption, and location registration, as well as session management functions such as the establishment, release, and modification of user plane transmission paths.

[0086] One example is the user registration process, which mainly includes: the UE sending a registration request to the AMF network element via the AN; the AMF network element obtaining subscription data from a specific UDM network element based on the user identifier; and the UDM network element obtaining the actual subscription data from the UDR network element upon receiving the request. In addition, the AMF network element can also initiate a user policy control establishment (UE policycontrol_create) request and an access management policy control establishment (AM policycontrol_create) request to the PCF network element. The user policy control establishment request is used to obtain policy information related to the UE (such as QoS requirements, charging policies, application priorities, etc.), while the access management policy control establishment request is used to obtain policy information related to access management (such as potentially involving access control, network selection, etc.). During this process, the PCF network element returns access management-related policies to the AMF network element, and then, via the AMF network element, returns UE-related policy information to the UE.

[0087] Another example is that the session establishment process mainly includes: the UE sending a session establishment request to the AMF network element through the RAN; the AMF network element selecting an SMF network element to provide services for the session, saving the mapping between SMF network elements and PDU sessions, and sending the session establishment request to the SMF network element; the SMF network element selecting the appropriate UPF network element for the UE, establishing a user plane transmission path, and allocating an IP address for it. During this process, the SMF network element will also initiate a policy control session establishment request to the PCF network element to establish a policy control session between the SMF and PCF network elements. During the policy control session establishment process, the SMF network element will save the mapping between the policy control session and the PDU session. In addition, the AF network element can also establish an AF session with the PCF network element, where the PCF network element binds / associates / maps the AF session with the policy control session.

[0088] The interfaces and functions between the above network elements will be described in detail below.

[0089] In the 5G core network, various functional units can communicate with each other through the next-generation (NG) interface, specifically including:

[0090] NG Interface 1 (N1 for short): The interface between the UE and the AMF network element, which can be used to send QoS control rules to the UE, for example.

[0091] NG Interface 2 (N2 for short): The interface between AN / RAN equipment and AMF network elements, for example, it can be used to transmit control plane signaling.

[0092] NG Interface 3 (N3 for short): The interface between RAN equipment and UPF network elements, for example, it can be used to transmit user plane data.

[0093] NG Interface 4 (N4 for short): The interface between UPF network elements and SMF network elements. For example, it can be used to transmit information between the control plane and the user plane, including but not limited to: the distribution of forwarding rules, QoS control rules, traffic statistics rules, etc. from the control plane to the user plane, as well as the reporting of information from the user plane.

[0094] NG Interface 5 (N5 for short): The interface between AF network elements and PCF network elements, which can be used for sending application service requests and reporting network events.

[0095] NG Interface 6 (N6 for short): The interface between UPF network elements and DN network elements, for example, it can be used for exchanging user plane data.

[0096] NG Interface 7 (N7 for short): The interface between PCF network elements and SMF network elements. For example, it can be used to issue PDU session granularity and service data flow granularity control policies.

[0097] NG Interface 8 (N8 for short): The interface between AMF network elements and UDM network elements. For example, it can be used by AMF network elements to obtain access and mobility management related subscription data and authentication data from UDM network elements, and by AMF network elements to register UE current mobility management related information with UDM network elements.

[0098] NG Interface 10 (N10 for short): The interface between SMF network element and UDM network element. For example, it can be used for SMF network element to obtain session management related subscription data from UDM network element, and for SMF network element to register UE current session related information with UDM network element.

[0099] NG Interface 11 (N11 for short): The interface between AMF network elements and SMF network elements. For example, it can be used to transmit PDU session tunnel information between RAN and UPF network elements, transmit control messages sent to UE, and transmit radio resource control messages sent to RAN.

[0100] NG Interface 15 (N15 for short): The interface between PCF network elements and AMF network elements, which can be used, for example, to issue UE policies and access control related policies.

[0101] NG Interface 35 (N35 for short): The interface between UDM network elements and UDR network elements. For example, it can be used by UDM network elements to obtain user subscription data from UDR network elements.

[0102] NG Interface 36 (N36 for short): The interface between PCF network elements and UDR network elements. For example, it can be used by PCF network elements to obtain policy-related subscription data and application data from UDR network elements.

[0103] NG Interface 52 (N52 for short): The interface between UDM network elements and NEF network elements. For example, it can be used by NEF network elements to open network capabilities to third-party application functions. For example, third-party application functions can subscribe to the reachability events of all users in a specific group (such as user online, user offline, or status change) through NEF network elements to UDM network elements.

[0104] NG Interface 9 (N9 for short): An interface between different UPF instances, used to support packet forwarding and traffic management to facilitate data transfer between different UPF instances.

[0105] Furthermore, NEF network elements have direct interfaces with AMF and SMF network elements. The interface between NEF and AMF network elements is N29, which can be used, for example, for NEF network elements to directly subscribe to relevant network events and update user configuration information from AMF network elements. The interface between NEF and SMF network elements is N51 (not shown in the diagram above for simplicity), which can be used, for example, to update application configuration data on SMF / UPF network elements, such as the packet flow description (PFD) information corresponding to the application. The interfaces between each network element are not listed here in detail.

[0106] It should be noted that, Figure 1 This is just an example architecture diagram, except... Figure 1 In addition to the functional units shown, the network architecture may also include other functional units, which are not limited in this application.

[0107] In existing network architectures (such as...) Figure 1 In the network architecture shown, network elements can store context, and the subscription / notification mechanism relies on notification URIs and association identifiers to associate subscriptions with notifications. The notification URI can indicate the target address / endpoint / subscriber / subscribing network element to receive the notification, allowing the network element to determine when an event has occurred and send a notification message to the corresponding address based on the notification URI. However, a notification URI may be shared by multiple events. Therefore, for different subscription events, a corresponding association identifier can be assigned to each event. This association identifier is used to associate a specific subscription request with the corresponding notification, ensuring that each notification can be mapped to its corresponding subscription event. In this way, when a subscribing network element receives a notification message, it will know which event has occurred and which event's context it needs to associate with. For example, network element A initiates a subscription event for user A's session A. When the result of the subscription event is returned, network element A can modify the associated session A based on the association identifier.

[0108] Figure 2 This is a diagram illustrating an existing subscription / notification process. Figure 2In the subscription / notification process shown, taking the NEF network element (hereinafter referred to as NEF in the figure) subscribing to an event from the AMF network element (hereinafter referred to as AMF in the figure) as an example, the recipient of the subscription event can include the NEF network element, and can also include other network elements, such as the SMF network element.

[0109] like Figure 2 As shown, the NEF network element sends a subscription request or unsubscribe request to the AMF network element, and the AMF network element receives the subscription request or unsubscribe request accordingly. Further, the AMF network element sends a subscription response or unsubscribe response to the NEF network element, and the NEF network element receives the subscription response or unsubscribe response accordingly. The subscription response may carry a notification URI and associated identifier assigned to the subscription request / subscription event, so that the NEF network element can manage the subscription. The notification URI is used to receive event notification reports returned by the AMF network element. This notification URI can be an address assigned by the NEF network element to receive event notification reports, or it can be an address assigned by the actual subscribing node (such as an AF network element) to receive event notification reports. Optionally, when the NEF network element sends a subscription request to the AMF network element, after the subscribed event occurs or the subscription event is triggered, the AMF network element may send a notification message to the NEF network element. Optionally, the AMF network element can also send the above notification message to another receiver (the event receiver shown in the figure). After receiving the above notification message, the receiver can update the associated subscription event to the event context based on the notification URI and association identifier in the notification message.

[0110] Understandable, Figure 1 In the architecture shown, network elements such as NEF and AMF store context, therefore, in Figure 2 In the example shown, NEF and AMF network elements can maintain the association between subscription events and notification URIs / association identifiers. However, if a network element may release its context, there is no way to maintain the association between subscription events and notification URIs / association identifiers. Therefore, the above subscription / notification mechanism may not be implemented.

[0111] In view of this, this application provides a communication method that can be applied to stateless architectures (as described below). Figure 3 or Figure 4 As shown, the event subscription and notification process is implemented through data plane network elements. The data plane network elements can store the context information related to subscription / notification. In this way, even if the subscription network element / event consumer node is stateless, the event subscription and notification can still be completed.

[0112] Before detailing the method provided in this application, the following section first describes the possible architectural designs of the stateless design described above.

[0113] Figure 3This is a schematic diagram of the stateless network architecture provided in the embodiments of this application.

[0114] like Figure 3 As shown, the network architecture includes UE, RAN, DN, and CN. CN can include UPF, AMF, SMF, PCF, etc., collectively referred to as NF in the diagram. In this application, NF can also be referred to as a microservice / service, for example, each network element defines a microservice / service. Figure 1 The architecture shown differs from the others in that this network architecture also includes a signaling distribution function (SDF) network element and a task-centric function (TCF) network element. The SDF network element can locally maintain signaling routing-related state information to provide signaling offloading functionality to the UE and core network elements. The TCF network element is responsible for performing task orchestration based on request messages and completing the tasks corresponding to the request messages by invoking the service capabilities provided by the NFs. Each NF can obtain context information from the data plane to execute tasks. This TCF network element can be designed to be stateful or stateful for a certain period of time.

[0115] In addition, with Figure 1 The difference from the architecture shown is that the above NF can adopt a stateless design. A stateless design can be understood as the NF not needing to store user / session-related context information locally. It only needs to perform task processing based on task requests and / or context information obtained from the data plane. In other words, the NF will release the context information after the task is completed. For example, the context information can be released immediately after the task is completed, or it can be released some time after the task is completed. This application does not limit this.

[0116] For example, taking the registration process as an example, after receiving the registration request initiated by the UE, the TCF network element can sequentially call the authentication function, mobility service, subscription service, and policy service based on its local state machine logic to complete the relevant processes before returning a registration success indication to the UE. During this process, each NF can perform task processing based solely on the task request initiated by the TCF and the context information obtained from the data plane, and return the processed results to the TCF network element and / or the data plane network element, thereby achieving a stateless design for NFs and avoiding the network implementation complexity caused by the coupling of network element functions.

[0117] Optionally, the large network domain and subnet domain can each deploy networks based on the above architecture. The large network domain can be understood as a large range of IP addresses or a network, which can contain multiple subnet domains. Subnet domains can be regarded as branches or subsets of the large network domain. Subnet domains can be used for specific regions / enterprises, such as a subnet dedicated to enterprise A. This subnet includes TCF network elements, NF network elements, etc. This subnet can also be called a private network. This application does not limit its name.

[0118] against Figure 3 The network architecture allows for the refinement of logical functions on the data plane to achieve the required context storage and event subscription / notification processes. The following will combine... Figure 4 A detailed explanation of the data surface refinement is provided.

[0119] Figure 4 This is a schematic diagram of the data plane architecture provided in the embodiments of this application.

[0120] The core network can be accessed through Figure 4 The architecture shown implements information processing, such as Figure 4 As shown, this architecture can include a data application layer, a signaling distribution layer, a data management layer, a data routing layer, and a data storage layer. The data application layer can include TCF network elements, AF network elements, mobility management (MM) functions / session management (SM) functions, etc. TCF network elements are responsible for task orchestration based on request messages and complete the tasks corresponding to the request messages by calling the service capabilities provided by NFs. Each NF can obtain context information from the data plane to execute tasks. The signaling distribution layer can include SDF network elements, which can be used to implement signaling offloading. In another possible implementation, this architecture may not include SDF network elements, and the signaling offloading function can be implemented by routing management function (RMF) network elements.

[0121] The data management layer, data routing layer, and data storage layer can constitute the data plane. In other words, the data plane can be subdivided into the data management layer, the data routing layer (which is optional), and the data storage layer. The data management layer includes data management function (DMF) network elements, which can be used to maintain context information and support proxy subscription or notification processes based on subscription request / notification messages. The data routing layer can include RMF network elements, which can provide intra-domain / inter-domain routing capabilities to data plane network elements. If multiple RMF network elements exist within a domain or multiple domains exist in the network, routing information can be synchronized through the interconnection interface between RMF network elements. The data storage layer can include data storage function (DSF) network elements, which provide context information storage capabilities. In this application, the DMF, RMF, and DSF network elements can provide services externally as a whole node, or they can provide services internally / externally according to their respective logical functions; this application does not limit this.

[0122] Optionally, the aforementioned context information (such as context information on the DMF / DSF network element side) may include one or more of the following: context identifier information, notification association identifier, event (group) identifier, event source node, event consumer node, or event notification type. The context identifier information may be user-granular, such as a subscription permanent identifier (SUPI) or a general public subscription identifier (GPSI). It may also be a PDU session identifier (PDU sessionID) or a context identifier. These context identifier information are merely examples and should not constitute any limitation on this application. The event source node may be the event monitoring node, and the event consumer node may be the recipient of the event notification message. The event notification type may be one-time, meaning only one notification is sent; it may be continuous, meaning the event consumer node is notified whenever the event occurs; or it may be immediate notification. Immediate notification can be understood as immediately returning the corresponding event notification in the response message when a relevant event report already exists locally.

[0123] The following will combine Figure 5 The communication method provided in this application is described in detail.

[0124] Figure 5 The illustrated embodiments demonstrate the method provided in this application from the perspective of data plane network elements. However, this should not constitute any limitation on the implementation of the method provided in this application. Figure 5In this paper, taking the data plane network element as the execution subject as an example, the communication method of the embodiment of this application will be described in detail.

[0125] It should be understood that the data plane network element can be the data plane network element itself, or it can be replaced by a chip, chip system or processor that supports the data plane network element to implement the communication method, or it can be replaced by a logic module or software that can implement all or part of the data plane network element. This application does not limit this.

[0126] Figure 5 This is a flowchart illustrating the communication method 500 provided in an embodiment of this application. Figure 5 In the illustrated embodiment, the data plane network element may be, for example, Figure 4 The DMF network element shown can also be a whole node composed of DMF network elements, RMF network elements, and DSF network elements. DMF network elements can be used to maintain context information and support the execution of proxy subscription or notification processes based on subscription request / notification messages. In this way, even in a stateless architecture, notification and subscription processes can be implemented through data plane network elements.

[0127] The method 500 includes the following steps:

[0128] In step 510, a first request message is received. The first request message is used to request subscription to a first event. The first request message carries at least one of the following: notification method, cache duration, or description information corresponding to the event consumption node.

[0129] The aforementioned first event can be, for example, a directly respondable event, meaning that the event report can be directly returned in the subscription response. For example, the first event includes, but is not limited to: public land mobile network (PLMN) / access type / access technology, session status, roaming status, or subscription data changes. Access type includes, but is not limited to, cellular network access, wireless fidelity (Wi-Fi) access, or satellite access; access technology includes, but is not limited to, 4th generation (4G), 5G, or new radio (NR).

[0130] The aforementioned first event can also be an event that requires subscription to receive a notification. For example, the first event includes, but is not limited to, UE location (such as cell change, primary rate access (PRA) change, etc.) or application (APP) start / end. The notification may carry a notification association identifier corresponding to the first event. The event consuming node can obtain the event report from the data plane network element based on the notification association identifier. Alternatively, the notification may directly carry the report of the first event; this application does not limit this.

[0131] The aforementioned first event can also be an event that is reported / notified by default without subscription. For example, the first event includes, but is not limited to: UE connection status, PLMN / access technology / access standard change, SUPI / permanent equipment identifier (PEI) association change, or resource allocation event, etc.

[0132] The above notification method is used to indicate whether the sender of the first request message is an event consumer node. This notification method can be, for example, direct notification or indirect notification. Direct notification refers to the subscribing network element, i.e., the event consumer node. For instance, if the event consumer node initiates a subscription request and subsequently receives notifications of the subscribed event, the notification method is direct notification. Indirect notification refers to the subscribing network element not being an event consumer node, or it can be understood as the subscribing network element acting as a proxy for the event consumer node initiating the subscription request. This notification method facilitates the determination of the recipient of the event notification.

[0133] When the notification method is indirect, the first request message mentioned above may also carry description information corresponding to the event consumer node.

[0134] Descriptive information of the event consumer node: Used to select the event consumer node. The descriptive information corresponding to the event consumer node includes, but is not limited to, the network element type of the event consumer node, or the characteristics that the event consumer node meets. These characteristics include, but are not limited to, the functions performed by the event consumer node, the region where the event consumer node is located, or the data network name (DNN) providing services to the event consumer node. For example, a UDM (an example of a subscribing network element) initiates a subscription on behalf of a NEF (an example of an event consumer node), and can indicate in the subscription request that the type of the event consumer node is a network data analytics function (NWDAF) network element. The characteristics that the event consumer node meets may include, for example, its region, its functions, or the DNN providing the services.

[0135] The aforementioned cache duration indicates the storage duration of the context information corresponding to the first event, which can be understood as how long after the network element completes its task will it release the context information. In this application, the network element can release the context information immediately after completing its task (i.e., the cache duration is zero), or it can release the context information after a period of time (i.e., the cache duration is greater than zero). In one possible design, if the first request message carries the event notification address before the cache duration expires, the data plane network element can send an event notification based on the notification address.

[0136] Optionally, the first request message may also carry at least one of the following: context identification information, the identifier of the first event, the event description information corresponding to the first event, the notification address corresponding to the first event, or the notification type of the first event.

[0137] The aforementioned context identification information can be, for example, user-level granularity, such as SUPI or GPSI; PDU session-level granularity, such as PDU session identifier; or context-level granularity, such as context identifier. The granularity of the aforementioned context identification information is merely illustrative and should not constitute any limitation on this application. For example, the aforementioned context identification information can also be divided according to network element granularity, such as core network elements perceiving core network element-level context identifiers, and TCF network elements perceiving TCF-level context identifiers.

[0138] The identifier for the first event mentioned above is used to identify the first event.

[0139] The event description information corresponding to the first event mentioned above is used to describe the first event, such as the type of the first event (e.g., direct response, requiring subscription to return a notification, reporting by default without subscription, etc.), or the filtering conditions corresponding to the first event, such as the reporting threshold, and the object description information corresponding to the event (e.g., PDU session, QoS flow identifier, etc.).

[0140] The notification address corresponding to the first event mentioned above: used to indicate the address for receiving the notification message corresponding to the first event.

[0141] The notification types mentioned above can be: one-time, meaning only one notification is sent; continuous, meaning the event consumer node will be notified whenever the event occurs; or immediate notification, where immediate notification can be understood as the corresponding event notification being returned immediately in the response message when there is already a relevant event report locally.

[0142] The following sections will describe in detail the possible designs (Design 1 to Design 3) for the event query process and the event notification process.

[0143] Design 1: The above-mentioned event query process based on the first request message includes: performing context addressing based on the first request message to obtain the report of the first event; the above-mentioned event notification process based on the first request message includes: sending a first response message to the event consumer node, the first response message carrying the report of the first event; or, determining, based on the cache duration, to return the report of the first event through an independent message.

[0144] In one possible implementation, the data plane network element can perform context addressing based on context identification information. For example, if the data plane network element is a DMF network element, the DMF network element can search for the context information corresponding to the context identification information locally or through the RMF network element to obtain the report of the first event. It can be understood that the context information includes the report of the first event. Exemplarily, the process of the DMF network element searching for context information through the RMF network element includes: the DMF network element can determine the target DSF network element through the RMF network element, and then send a context information retrieval request to the target DSF network element to obtain the context information, thereby obtaining the report of the first event. The context information retrieval request may carry the context identification information.

[0145] Based on the first request message, the data plane network element executes an event notification process. One possible implementation is that when the sender of the first request message is an event consumer node, the data plane stores a report of the first event, and the first event supports directly returning the event report in the response message, the data plane network element can send a first response message. This first response message is used to respond to the first request message. For example, the first event can be an event that supports direct response. In this case, when the sender of the first request message is an event consumer node and the data plane stores a report of the first event, the data plane network element can send a first response message, which carries the report of the first event.

[0146] When the sender of the first request message is not an event consumer node, the data plane network element can send a first message to the TCF network element. This first message is used by the TCF network element to select an event consumer node. Correspondingly, the TCF network element sends the aforementioned first message.

[0147] For example, a data plane network element can send a first message directly or indirectly (via an SDF network element) to a TCF network element so that the TCF network element can select an event consumer node and trigger a subsequent notification process.

[0148] Optionally, the first message may carry at least one of the following: context identifier information, identifier of the first event, event description information corresponding to the first event, description information corresponding to the event consumer node, or notification association identifier.

[0149] Optionally, the aforementioned first message can also be sent by the SDF network element, such as when the SDF network element sends the first message to the TCF network element. This first message is used by the TCF network element to select an event consumption node.

[0150] When the data plane does not store a report of the first event, or when the first event does not support returning the event report directly in the response message, the data plane network element can execute Design 2 or Design 3 as described below.

[0151] Based on the first request message, the data plane network element executes the event notification process. Another possible implementation is that if the cache duration expires (or has expired), the data plane network element returns the report of the first event through a separate message, that is, there is no need to carry the report of the first event in the first response message; if the cache duration has not expired (or has not expired), the data plane network element can carry the report of the first event in the first response message.

[0152] Design 2: Based on the first request message, the aforementioned data plane network element executes an event query process, including: the data plane network element receiving a context update request from the event source node, the context update request being used to request an update of context information, the context update request carrying a report of the first event; the aforementioned data plane network element executing an event notification process based on the first request message, including: the data plane network element sending a first message to the TCF network element, the first message being used by the TCF network element to select an event consumer node; the data plane network element receiving a second request message from the event consumer node, the second request message being used to request the acquisition of a report of the first event; and the data plane network element sending a second response message to the event consumer node, the second response message carrying a report of the first event.

[0153] The above design two can be applied, for example, to scenarios where the first event is an event that is reported / notified by default without subscription. Based on the first request message, the data plane element executes an event query process. One possible implementation is that the event source node sends a context update request to the data plane element. This context update request requests an update to context information and carries the report of the first event. Correspondingly, the data plane element receives the aforementioned context update request.

[0154] Optionally, before the data plane network element receives the aforementioned context update request, the method further includes: the data plane network element receiving a third request message from the event source node, the third request message being used to request the acquisition of context information; and the data plane network element sending a third response message to the event source node, the third response message carrying the event subscription list corresponding to the first event.

[0155] The data plane network element returns the event subscription list corresponding to the first event to the event source node, so that the event source node can provide an event report. The event subscription list may include, but is not limited to, one or more of the following: event type, information about the subscribing network element, triggering conditions, or subscription validity period. The event type specifies the specific type of event being subscribed to, such as user online / offline status, location update, or session management events. The information about the subscribing network element identifies the network function entity subscribing to the first event, such as an AMF network element or an SMF network element. The triggering conditions indicate the conditions under which the event will be triggered or notified, such as a specific user group, geographical location, or service type. The subscription validity period refers to the valid time period after which the subscription will automatically expire.

[0156] As one possible scenario, a TCF network element receives a new process trigger request, sends a service request to the event source node, and the event source node responds to the TCF network element. Further, a data plane network element receives a third request message from the event source node, which requests context information; the data plane network element sends a third response message to the event source node, carrying the event subscription list corresponding to the first event. The event source node then sends a context update request to the data plane network element, requesting an update to the context information, and this context update request carries a report of the first event. Correspondingly, the data plane network element receives the aforementioned context update request.

[0157] Optionally, the third response message also carries a notification association identifier. The data plane network element returns the notification association identifier corresponding to the first event to the event source node, so that the event source node can carry the notification association identifier when providing the event report, thereby enabling the recipient of the event report to identify the corresponding event.

[0158] Based on the first request message, the aforementioned data plane network element executes an event notification process. One possible implementation is that the data plane network element sends a first message to the TCF network element. This first message is used by the TCF network element to select an event consumer node. The first message carries at least one of the following: context identifier information, the identifier of the first event, the event description information corresponding to the first event, the description information corresponding to the event consumer node, or a notification association identifier. This first message facilitates triggering the TCF network element to select an event consumer node, thereby triggering the event consumer node to obtain a report of the first event. For example, the event consumer node sends a second request message to the data plane network element, which requests to obtain a report of the first event; the data plane network element then sends a second response message to the event consumer node, which carries the report of the first event.

[0159] Design 3, based on the first request message, executes the event query process, including: the data plane network element sending a subscription request based on the first request message, which is used to request the event source node to subscribe to the first event; and receiving a second message from the event source node, which carries the report and notification association identifier of the first event. Based on the first request message, the event notification process includes: sending a first message to the TCF network element, which is used by the TCF network element to select an event consumer node; receiving a second request message from the event consumer node, which is used to request to obtain the report of the first event; and sending a second response message to the event consumer node, which carries the report of the first event.

[0160] The above design example can be applied to scenarios where the first event requires subscription to return a notification. Based on the first request message, the event query process is executed. One possible implementation is that the data plane network element sends a subscription request to the TCF network element. This subscription request requests subscription to the first event from the event source node. The subscription request may carry the identifier of the first event and / or a notification association identifier. Correspondingly, the TCF network element receives the subscription request and then sends it to the event source node. Correspondingly, the event source node receives the subscription request and then sends a second message to the data plane network element, carrying the report and notification association identifiers of the first event. Correspondingly, the data plane network element receives the second message. Another possible implementation is that the data plane network element directly sends a subscription request to the event source node, thereby the event source node sends a second message to the data plane network element.

[0161] Based on the first request message, the aforementioned data plane network element executes an event notification process. One possible implementation is that the data plane network element sends a first message to the TCF network element. This first message is used by the TCF network element to select an event consumer node. The first message carries at least one of the following: context identifier information, the identifier of the first event, the event description information corresponding to the first event, the description information corresponding to the event consumer node, or a notification association identifier. This first message facilitates triggering the TCF network element to select an event consumer node, thereby triggering the event consumer node to obtain a report of the first event. For example, the event consumer node sends a second request message to the data plane network element, which requests to obtain a report of the first event; the data plane network element then sends a second response message to the event consumer node, which carries the report of the first event.

[0162] Optionally, the data plane network element is a DMF network element. This data plane network element receives the second message from the event source node. One possible implementation is that the DMF network element directly receives the second message from the event source node. Another possible implementation is that the DMF network element receives the second message from the event source node after it has been forwarded by the DSF network element.

[0163] Optionally, the aforementioned data plane network element is a DMF network element. Figure 5 The method 500 further includes: assigning a notification association identifier to the first event and storing the subscription context information in the DSF network element; or, calling the DSF network element to perform the assignment of the notification association identifier and updating the subscription context information in the DSF network element based on the notification association identifier, wherein the subscription context information includes one or more of the following: notification association identifier, description information corresponding to the event consumer node, or context identifier information corresponding to the first event.

[0164] In one example, the DMF element assigns a notification association identifier to the first event and stores the subscription context information in the DMF element.

[0165] In another example, the DMF network element calls the DSF network element to perform notification association identifier allocation, and updates the subscription context information to the DSF network element based on the notification association identifier.

[0166] Figure 6 This is a detailed flowchart illustrating the communication method provided in the embodiments of this application. The following will be combined with... Figure 6 right Figure 5 The method shown is described in more detail below. Figure 6 The illustrated embodiments demonstrate the method provided in this application from the perspective of device interaction. The specific forms and quantities of the devices shown are merely examples and should not constitute any limitation on the implementation of the method provided in this application. Figure 6 In this paper, taking data plane network elements, TCF network elements, subscription network elements and event source nodes as the main execution entities, the communication method of the embodiments of this application will be described in detail.

[0167] It should be understood that a data plane network element can be the data plane network element itself, or it can be replaced by a chip, chip system, or processor that supports the communication method of the data plane network element, or it can be replaced by a logic module or software that can implement all or part of the data plane network element; a TCF network element can be the TCF network element itself, or it can be replaced by a chip, chip system, or processor that supports the communication method of the TCF network element, or it can be replaced by a logic module or software that can implement all or part of the TCF network element; a subscription network element can be the subscription network element itself, or it can be replaced by a chip, chip system, or processor that supports the communication method of the subscription network element, or it can be replaced by a logic module or software that can implement all or part of the subscription network element, etc., and this application does not make specific limitations in this regard. In addition, an event source node can be a certain network element itself, or it can be replaced by a chip, chip system, or processor that supports the communication method of that network element, or it can be replaced by a logic module or software that can implement all or part of that network element, etc.

[0168] In detail Figure 6 Previously, the following section first discussed... Figure 6 The network elements involved will be explained in detail.

[0169] Subscribing network element: This can be understood as the network element that sends a subscription request. One possibility is that the subscribing network element can be an event consumer node, where the event consumer node is the recipient of the event notification; that is, the party sending the subscription request is also the recipient of the event notification. Another possibility is that the subscribing network element is not an event consumer node, but rather a network element that proxies the event consumer node to subscribe, and the event consumer node receives the event notification.

[0170] Data plane network element: This data plane network element can be, for example, a Figure 4 The DMF network element shown can also be, for example, an integral node composed of DMF network elements, RMF network elements, and DSF network elements. Data plane network elements can be used to maintain context information and support the execution of proxy subscription or notification processes based on subscription request / notification messages.

[0171] TCF Network Element: A TCF network element is responsible for task orchestration based on request messages and completes the tasks corresponding to the request messages by calling the business capabilities provided by NFs. Each NF can obtain context information from the data plane to execute tasks. This TCF network element can be designed to be stateful or stateful for a certain period of time.

[0172] Event source node: This can be understood as the network element that provides event notification for an event (such as the first event described below). When the event source node is not the actual monitoring node of the event, it needs to interact with the actual monitoring node of the event to complete the subscription / notification.

[0173] Figure 6 The described embodiments include the following steps:

[0174] In step 601, the subscribing network element sends a first request message, and correspondingly, the data plane network element receives the first request message, which is used to request subscription to the first event.

[0175] The first request message carries at least one of the following: notification method, cache duration, or description information corresponding to the event consumption node. A more detailed explanation of step 601 can be found in step 510, and will not be repeated here.

[0176] When the subscribing network element is an event consumer node, the data plane stores the report of the first event, and the first event supports directly returning the event report in the response message, the data plane network element can execute process A, namely step 602: the data plane network element sends a first response message to the subscribing network element, and the first response message carries the report of the first event.

[0177] For example, the first event can be an event that supports direct response. When the subscribing network element is an event consumer node and the data plane stores a report of the first event, the data plane network element can send a first response message, which carries the report of the first event.

[0178] Optionally, before executing step 602, the data plane network element may also perform context addressing based on the context identifier information in the first request message to obtain a report of the first event.

[0179] When the subscribing network element is not an event consumer node, the data plane network element can execute step 611: the data plane network element sends a first message to the TCF network element, which is used by the TCF network element to select an event consumer node. Correspondingly, the TCF network element receives the aforementioned first message.

[0180] For example, a data plane network element can send a first message directly or indirectly (via an SDF network element) to a TCF network element so that the TCF network element can select an event consumer node, thereby notifying the event consumer node of the report of the first event or the notification association identifier corresponding to the first event.

[0181] Optionally, the first message may carry at least one of the following: context identifier information, identifier of the first event, event description information corresponding to the first event, description information corresponding to the event consuming node, or notification association identifier. The notification association identifier may be assigned by the data plane network element. For example, after receiving the first request message, the data plane network element assigns a notification association identifier to the first event. This can be done by the DMF network element or by calling the DSF network element to perform the notification association identifier assignment.

[0182] When there is no report of the first event in the data plane network element, or when the first event does not support the direct return of the event report in the response message, the data plane network element can determine whether the first event has been subscribed to before.

[0183] As one possible implementation, when the first event has not been subscribed to before, the data plane element can execute process B or process C; when the first event has been subscribed to before, the data plane element can add one or more of the following to the context information: context identifier information, notification association identifier, event (group) identifier, event source node, event consumer node, or event notification type, so that the event notification can be correctly sent to the event consumer node in the future.

[0184] The above process B is applicable to scenarios where the first event type is an event that is reported / notified by default without subscription, while the above process C is applicable to scenarios where the first event type requires subscription to return a notification. Processes B and C will be described in detail below.

[0185] Process B includes steps 603 to 607.

[0186] In step 603, a new process is triggered. For example, the TCF network element receives a new process trigger request.

[0187] In step 604, the TCF network element sends a service request to the event source node, and the event source node responds to the TCF network element with a service.

[0188] For example, the TCF network element selects an event source node and sends a service request to that event source node to request the event source node to execute a task process. The service request may carry context identification information corresponding to the event source node, so that the event source node can obtain context information from the data plane network element based on this context identification information.

[0189] In step 605, the event source node sends a third request message to the data plane network element, which requests context information. Correspondingly, the data plane network element receives the aforementioned third request message.

[0190] In step 606, the data plane network element sends a third response message to the event source node. Correspondingly, the event source node receives the third response message. The aforementioned third response message responds to the third request message, and carries the event subscription list corresponding to the first event.

[0191] For an explanation of step 606, please refer to [link / reference]. Figure 5 The relevant descriptions will not be repeated here.

[0192] In step 607, the event source node sends a context update request to the data plane network element. The context update request is used to request an update of the context information and carries a report of the first event.

[0193] For example, after receiving the third response message, the event source node sends a context update request to the data plane network element. The context update request is used to request an update of the context information, and the context update request carries a report of the first event.

[0194] An example of process B is that after the data plane network element receives the request message from the subscribing network element, it determines that the first event does not need to be subscribed to and can be automatically reported as long as the event occurs. Then, when the mobility management network element (such as the AMF network element or SMF network element) initiates a service request, the data plane network element carries the event subscription list and an optional notification association identifier in the service response to trigger the mobility management network element to perform event reporting in subsequent message interactions; or, when the mobility management network element initiates a context update request to the data plane during or after the execution of a subtask, the data plane network element determines the event report based on the updated context information and triggers the event notification process (such as steps 611 to 614).

[0195] Optionally, if the data plane network element is unaware of the association between the event and the event report, it can assign a notification association identifier at the event granularity for the event source node to use when performing event reporting. If the data plane network element is aware of the association between the event and the event report, it is not necessary to assign a notification association identifier. After the event source node performs the event report based on the context identifier, the data plane network element matches the event report with the event subscription list, thereby triggering the event notification process (such as steps 611 to 614).

[0196] Process C may include steps 608 to 610.

[0197] In step 608, the data plane network element sends a subscription request to the TCF network element. This subscription request is used to request subscription to the first event from the event source node. Correspondingly, the TCF network element receives the subscription request.

[0198] As one possible implementation, the data plane network element can determine whether it needs to send a subscription request through the TCF network element based on whether the event source node has state (or whether it can store context). For example, if the event source node can store context, the data plane network element can directly send the subscription request to the event source node; if the event source node cannot store context, the data plane network element can send the subscription request to the TCF network element to initiate subscription through the TCF network element (i.e., execute step 608).

[0199] In step 609, the TCF network element sends the aforementioned subscription request to the event source node. Correspondingly, the event source node receives the aforementioned subscription request.

[0200] For example, after receiving a subscription request, the TCF network element sends the subscription request to the event source node to request subscription to the first event.

[0201] For example, a data plane network element initiates a subscription request to a TCF network element to trigger the TCF to execute the event subscription process. The subscription request carries one or more of the following: notification association identifier, context identifier information, identifier of the first event, and event description information or context identifier information corresponding to the first event.

[0202] After receiving the subscription request, the TCF network element can complete the context association / acquisition process based on the context identifier information, perform logical network element (i.e., event source node) selection, and forward the subscription request to the event source node.

[0203] Optionally, the above-described subscription initiated by the TCF network element agent to the event source node is merely an example and should not constitute any limitation on this application. For example, the SDF network element agent can also initiate the subscription to the event source node. For instance, the TCF network element triggers the SDF network element to perform physical network element / service instance selection by providing information such as the target network element / service type (i.e., the network element / service type corresponding to the event source node) and selection conditions, and the SDF network element forwards the subscription request to the target network element / service instance.

[0204] Optionally, when the event source node is not the actual monitoring node of the event, the event source node sends the above subscription request to the actual monitoring node of the event to complete the subscription.

[0205] If the event source node is stateful, it will continue to monitor the first event until the first event occurs and then execute the event reporting notification, as in step 610.

[0206] If the event source node is stateless, but the actual monitoring node is stateful, the event source node will trigger the update of context information to the data plane network element after completing the subscription interaction with the actual monitoring node of the event. This includes updating the event subscription information (notification association identifier, event ID, event description information, etc.) to the data plane context corresponding to the event source node. This will allow the actual monitoring node of the event to continue the event reporting process by selecting the network element instance corresponding to a certain event source node after detecting the relevant event.

[0207] In step 610, the event source node sends a second message to the data plane network element, which carries the report and notification association identifier of the first event. Correspondingly, the data plane network element receives the second message.

[0208] Once the event source node detects the target event (either through self-monitoring or by receiving an event notification report initiated by the actual monitoring node), it can update the event report to the data plane network element based on the notification association identifier. This process can be routed based on the notification association identifier (applicable to scenarios where the event source node is stateless or stateful) and sent to the data plane network element, or it can be updated to the data plane network element based on previously received context identifier information (applicable to scenarios where the event source node is stateful).

[0209] In the above process, event notifications can be directly reported to the DSF network element based on the notification association identifier, and then the DSF network element triggers the DMF network element to execute the notification process. Alternatively, the DMF network element can maintain a state context to receive event notifications initiated by the event source node. Furthermore, the notification association identifier can be a request from the DMF network element to the DSF network element to perform allocation, or the DMF network element can complete the allocation based on DSF network element interactions. Additionally, the event notification process can also be initiated from the SDF network element to the event consumer node, without going through the TCF network element.

[0210] Whether it is process B or process C, the event notification process includes steps 611 to 614.

[0211] In step 611, the data plane network element sends a first message to the TCF network element, which is used by the TCF network element to select an event consumer node. Correspondingly, the TCF network element receives the aforementioned first message.

[0212] In step 612, the TCF network element sends a fourth message to the event consumer node. This fourth message carries a notification association identifier, which is used by the event consumer node to obtain a report of the first event. Correspondingly, the event consumer node receives the aforementioned fourth message.

[0213] Optionally, when the TCF network element is stateful, that is, when the TCF network element stores context information, the TCF network element can also directly send the first event report to the event consumer node.

[0214] In step 613, the event consuming node sends a second request message to the data plane network element, which requests a report of the first event. Correspondingly, the data plane network element receives the second request message.

[0215] In step 614, the data plane network element sends a second response message to the event consumer node, which carries a report of the first event. Correspondingly, the event consumer node receives the second response message.

[0216] Optionally, after the event consumption node obtains the report of the first event, it can also trigger related processes based on the report of the first event, such as updating the UE's policy rules, or adjusting the UPF instance currently selected for the UE, etc., which will not be listed in this application.

[0217] This application also provides a communication method. For the subscription process, the data plane network element assigns a notification association identifier to the first event so that the subscription network element can initiate a subscription request. The subscription request can be forwarded by the TCF network element or initiated directly by the subscription network element to the event source node. For the notification process, the data plane network element receives the notification message and triggers the event notification process, thereby realizing the subscription and notification process for stateless network elements.

[0218] It should be understood that the communication method described below can be applied, for example, to events where the first event requires subscription to return a notification.

[0219] Figure 7 This is a flowchart illustrating another communication method 700 provided in an embodiment of this application. Figure 7 The illustrated embodiments demonstrate the above method from the perspective of data plane network elements. However, this should not constitute any limitation on the implementation of the methods provided in this application. Figure 7 In this paper, taking the data plane network element as the execution subject as an example, the communication method of the embodiment of this application will be described in detail.

[0220] It should be understood that a data plane network element can be the data plane network element itself, or it can be replaced by a chip, chip system, or processor that supports the communication method implemented by the data plane network element. It can also be replaced by a logic module or software that can implement all or part of the data plane network element; this application does not limit this. For a more detailed explanation of data plane network elements, please refer to [link / reference]. Figure 5 This will not be elaborated upon here.

[0221] Figure 7 The method shown mainly involves allocating notification association identifiers to data plane network elements and receiving notification messages to trigger the event notification process. This method 700 includes the following steps:

[0222] In step 710, the data plane network element receives a fourth request message, which is used to request the allocation of a notification association identifier for the first event.

[0223] The notification association identifier mentioned above can be at the event granularity, such as one event associated with one notification association identifier; the notification association identifier can also be at the event group granularity, such as one event group associated with one notification association identifier, and an event group can include multiple events; the notification association identifier can also be at the user / PDU session / QoS flow granularity, which is not limited in this application.

[0224] The data plane network element receives the fourth request message. Implementation method A: The subscribing network element sends the aforementioned fourth request message to the data plane network element. This fourth request message is used to request the allocation of a notification association identifier for the first event. Correspondingly, the data plane network element receives the aforementioned fourth request message. The aforementioned subscribing network element may or may not be an event consumer node; this application does not impose any limitations on this.

[0225] Implementation Method B: The TCF network element sends a fourth request message to the data plane network element. This fourth request message requests the allocation of a notification association identifier for the first event. Correspondingly, the data plane network element receives the aforementioned fourth request message. The aforementioned subscribing network element may or may not be an event consumer node; this application does not limit this. For example, after receiving a subscription request from a subscribing network element (which subscribes through the TCF network element), the TCF network element sends a fourth request message to the data plane network element. This fourth request message requests the allocation of a notification association identifier for the first event. Correspondingly, the data plane network element receives the aforementioned fourth request message.

[0226] Optionally, the fourth request message may carry at least one of the following: an identifier of the first event, or event description information corresponding to the first event. For an explanation of the above parameters, please refer to [link to relevant documentation]. Figure 5 This will not be elaborated upon here.

[0227] For example, the subscribing network element requests the data plane network element to assign a notification association identifier, such as a notification association identifier at the event / event group / user / session / QoS flow granularity, so that the data plane network element can correctly associate the notification message with the corresponding context. The request carries the identifier of the first event and the event description information corresponding to the first event. Optionally, the data plane network element may also directly reuse the context identifier to perform the association.

[0228] In step 720, the data plane network element sends a fourth response message, which carries a notification association identifier corresponding to the first event.

[0229] Corresponding to implementation method A, the data plane network element sends a fourth response message to the subscribing network element, which carries the notification association identifier corresponding to the first event. Correspondingly, the subscribing network element receives the aforementioned fourth response message.

[0230] Corresponding to implementation method B, the data plane network element sends a fourth response message to the TCF network element, which carries a notification association identifier corresponding to the first event. Correspondingly, the TCF network element receives the aforementioned fourth response message. This notification association identifier can, for example, be at the TCF granularity.

[0231] In step 730, the data plane network element receives a notification message from the TCF network element or the event source node, which carries the report of the first event and the notification association identifier.

[0232] One possible implementation is that the event source node sends a notification message to the data plane network element through the TCF network element. For example, after receiving the notification message from the event source node, the TCF network element sends it to the data plane network element, and the data plane network element receives the notification message.

[0233] Another possible implementation is that the event source node directly sends a notification message to the data plane network element, and the data plane network element receives the notification message.

[0234] Optionally, the aforementioned data plane network element is a DMF network element, and the aforementioned receiving notification messages from TCF network elements or event source nodes includes: directly receiving notification messages from TCF network elements or event source nodes; or, receiving notification messages from TCF network elements or event source nodes that have been forwarded by DSF network elements.

[0235] One possible implementation is that the TCF network element or event source node directly sends notification messages to the DMF network element, and correspondingly, the DMF network element directly receives notification messages from the TCF network element or event source node. Another possible implementation is that the TCF network element or event source node forwards notification messages through the DSF network element; that is, the TCF network element or event source node sends notification messages to the DSF network element, and the DSF network element forwards them to the DMF network element.

[0236] Optionally, the above method 700 further includes: the data plane network element recording subscription context information, which includes one or more of the following: notification association identifier, description information corresponding to the event consumption node, and context identifier information corresponding to the first event.

[0237] In one possible implementation, the aforementioned data plane network element is a DMF network element, and the aforementioned method 700 further includes: assigning a notification association identifier to the first event and storing the subscription context information in the DSF network element; or, calling the DSF network element to perform the assignment of the notification association identifier and updating the subscription context information in the DSF network element based on the notification association identifier, wherein the subscription context information includes one or more of the following: notification association identifier, description information corresponding to the event consumer node, and context identifier information corresponding to the first event.

[0238] In one example, the DMF element assigns a notification association identifier to the first event and stores the subscription context information in the DMF element.

[0239] In another example, the DMF network element calls the DSF network element to perform notification association identifier allocation, and updates the subscription context information to the DSF network element based on the notification association identifier.

[0240] Optionally, the above method 700 further includes: the data plane network element sending a first message to the TCF network element, the first message being used by the TCF network element to select the event consumer node; receiving a second request message from the event consumer node, the second request message being used to request to obtain a report of the first event; and sending a second response message to the event consumer node, the second response message carrying a report of the first event.

[0241] One possible implementation is that, after receiving the notification message, the data plane network element sends a first message to the TCF network element. This first message is used by the TCF network element to select an event consumer node. The first message carries at least one of the following: context identifier information, the identifier of the first event, event description information corresponding to the first event, description information corresponding to the event consumer node, or a notification association identifier. This first message facilitates triggering the TCF network element to select an event consumer node, thereby triggering the event consumer node to obtain a report of the first event. For example, the event consumer node sends a second request message to the data plane network element, which requests to obtain a report of the first event; the data plane network element then sends a second response message to the event consumer node, which carries the report of the first event. The second request message may, for example, carry a notification association identifier.

[0242] Figure 8 This is a flowchart illustrating another communication method 800 provided in an embodiment of this application. Figure 8 The illustrated embodiments demonstrate the above method from the perspective of TCF network elements. However, this should not constitute any limitation on the implementation of the method provided in this application. Figure 8 In this paper, taking the TCF network element as the execution subject as an example, the communication method of the embodiment of this application will be described in detail.

[0243] It should be understood that the TCF network element can be the data plane network element itself, or it can be replaced by a chip, chip system or processor that supports the communication method of the TCF network element, or it can be replaced by a logic module or software that can implement all or part of the TCF network element. This application does not limit this.

[0244] Figure 8 The method shown mainly involves the process of TCF network element subscription, and the method 800 includes the following steps:

[0245] In step 810, the TCF network element receives a subscription request, which is used to request to subscribe to the first event from the event source node.

[0246] For example, the TCF network element receives a subscription request from the subscription network element. The subscription request is used to request to subscribe to the first event from the event source node. The aforementioned subscription network element may or may not be an event consumer node, and this application does not limit it in this regard.

[0247] Optionally, the subscription request may include one or more of the following: the notification type of the first event, the event description information corresponding to the first event, and the notification association identifier or the description information corresponding to the event consumer node. For a detailed explanation of the above parameters, please refer to [link to relevant documentation]. Figure 5 This will not be elaborated upon here.

[0248] In step 820, the TCF network element sends a third message to the event source node. This third message is used to request to subscribe to the first event from the event source node. The third message carries a notification association identifier.

[0249] Design A: The subscription request carries a notification association identifier. For example, in the scenario where the subscribing network element triggers the data plane network element to allocate a notification association identifier, after the subscribing network element receives the notification association identifier from the data plane network element, it can send a subscription request to the TCF network element. This subscription request carries the notification association identifier. After receiving the subscription request, the TCF network element sends a subscription request to the event source node to request to subscribe to the first event.

[0250] Design B: The subscription request does not carry a notification association identifier. For example, in the scenario where the TCF network element triggers the data plane network element to allocate a notification association identifier, the subscribing network element sends a subscription request to the TCF network element. After receiving the subscription request, the TCF network element requests the data plane network element to allocate a notification association identifier, thereby obtaining the notification association identifier. Further, the TCF network element sends message A to the event source node. Message A is used to request subscription to the first event, and message A carries the notification association identifier.

[0251] Optionally, the above method 800 further includes: the TCF network element receiving a first message from the data plane network element, the first message being used by the TCF network element to select an event consumer node; and sending a notification association identifier to the event consumer node.

[0252] For example, after receiving the notification message, the data plane network element sends a first message to the TCF network element to request the TCF network element to select an event consumption node. Correspondingly, the data plane network element receives the aforementioned first message. Optionally, the aforementioned first message carries at least one of the following: context identification information, the identifier of the first event, the event description information of the first event, the description information corresponding to the event consumption node, or the notification association identifier.

[0253] Optionally, the above method 800 further includes: the TCF network element receiving a notification message, which carries a report and notification association identifier for the first event; and sending the notification message or notification association identifier to the event consumer node.

[0254] One possible scenario is that the notification message needs to be cached via the data plane. Upon receiving the notification message, the TCF network element caches its content in a context accessible to the event consumer node within the data plane network element (this context is indexed, for example, by a context identifier), or in a separate event notification context (this context is indexed, for example, by a notification association identifier). The TCF network element then triggers a request to the event consumer node, providing the aforementioned index information (such as the notification association identifier) ​​to the event consumer node so that it can retrieve the corresponding event notification and network element context information from the data plane network element. This mechanism can be applied to scenarios where the notification message is large or the real-time requirements are relatively low, such as NWDAF subscription analysis source data.

[0255] Another possible scenario is that, upon receiving the notification message, the TCF network element sends the report and notification association identifier of the first event to the event consumer node. This mechanism can be applied to scenarios with small notification messages or relatively high real-time requirements, and it can save some signaling complexity. The event source node can perform TCF network element discovery and report the notification message to the TCF network element. After receiving the notification message, the TCF network element can select the event consumer node and execute subsequent notification procedures, such as sending the report and notification association identifier of the first event to the event consumer node.

[0256] The following section, in conjunction with the accompanying drawings, will illustrate the device interaction from a device interaction perspective. Figure 7 and Figure 8 The method provided. The specific form and quantity of each device shown are merely examples and should not constitute any limitation on the implementation of the method provided in this application. Figure 9 and Figure 10 In this paper, taking data plane network elements, TCF network elements, event source nodes, etc. as the execution subjects, the communication method of the embodiments of this application will be described in detail.

[0257] It should be understood that a data plane network element can be the data plane network element itself, or it can be replaced by a chip, chip system, or processor that supports the communication method of the data plane network element, or it can be replaced by a logic module or software that can implement all or part of the data plane network element. Similarly, a TCF network element can be the TCF network element itself, or it can be replaced by a chip, chip system, or processor that supports the communication method of the TCF network element, or it can be replaced by a logic module or software that can implement all or part of the TCF network element. Furthermore, an event source node can be a network element itself, or it can be replaced by a chip, chip system, or processor that supports the communication method of that network element, or it can be replaced by a logic module or software that can implement all or part of that network element, etc.

[0258] in addition, Figure 9 The illustrated embodiment describes the detailed process of a subscribing network element requesting the allocation of a notification association identifier from a data plane network element, and then using a TCF network element to handle the subscription and notification. Figure 10 The illustrated embodiment is a detailed process of a TCF network element requesting the allocation of a notification association identifier from a data plane network element, and then subscribing to and notifying the data through a TCF network element proxy.

[0259] Figure 9 This is another detailed flowchart illustrating the communication method provided in the embodiments of this application.

[0260] In step 901, the subscribing network element sends a fourth request message to the data plane network element, which requests the allocation of a notification association identifier for the first event. Correspondingly, the data plane network element receives the aforementioned fourth request message.

[0261] The fourth request message mentioned above may carry the identifier of the first event and / or the event description information corresponding to the first event.

[0262] In step 902, the data plane network element sends a fourth response message to the subscribing network element, which carries a notification association identifier.

[0263] Optionally, the notification association identifier mentioned above can be a notification association identifier at the event / event group / user / session / QoS flow granularity.

[0264] In step 903, the subscribing network element sends a subscription request to the data plane network element, and the subscription request carries the aforementioned notification association identifier.

[0265] Optionally, the subscription request may also include at least one of the following: the identifier of the first event, context identifier information, event description information, notification type, notification method, or description information corresponding to the event consumer node.

[0266] In step 904, the TCF network element sends the aforementioned subscription request to the event source node.

[0267] For example, the TCF network element determines the event source node based on the identifier and event description information of the first event, and initiates a subscription request to the event source node so that the event source node can report the first event to the data plane after detecting the event.

[0268] Optionally, if the event source node is stateful, steps 903 and 904 can be replaced by the subscribing network element sending the above subscription request to the event source node through the SDF network element. For example, the AMF network element (an example of a subscribing network element) directly subscribes to the UE location information (an example of the first event) from the RAN device (an example of an event source node) and instructs the RAN device to report to the data plane network element after the event occurs.

[0269] In step 905, the event source node performs event acquisition.

[0270] If the event source node is not the actual monitoring node of the event, the event source node sends the above subscription request to the actual monitoring node of the event to complete the subscription.

[0271] For example, if the event source node is stateful, it will continue to monitor the first event until the first event occurs and then execute the event reporting notification. If the event source node is stateless, but the actual monitoring node is stateful, the event source node will trigger the updating of context information to the data plane network element after completing the subscription interaction with the actual monitoring node of the event. For example, the event subscription information (notification association identifier, event ID, event description information, etc.) will be updated to the data plane context corresponding to the event source node, so that after the actual monitoring node of the subsequent event detects the relevant event, it can continue to process the event reporting process by selecting the network element instance corresponding to a certain event source node.

[0272] The event source node and the actual monitoring node perform event monitoring, a process that also involves whether the event source node is stateful. For example, when the event source node detects a target event (either through self-monitoring or by receiving an event notification report initiated by the actual monitoring node), it can update the event report to the data plane network element based on the notification association identifier. This process can be routed based on the notification association identifier (applicable to scenarios where the event source node is stateless or stateful) and sent to the data plane network element, or it can be updated to the data plane network element based on previously received context identifier information (applicable to scenarios where the event source node is stateful).

[0273] In step 906, the event source node sends a notification message to the TCF network element. This notification message may carry the report and notification association identifier of the first event. Correspondingly, the TCF network element receives the notification message.

[0274] In step 907, the TCF network element sends the aforementioned notification message to the data plane network element. Correspondingly, the data plane network element receives the aforementioned notification message.

[0275] Optionally, steps 906 and 907 above can be replaced by step 908: the event source node directly sends the above notification message to the data plane network element.

[0276] In step 909, the data plane network element performs event association storage.

[0277] After receiving the notification message, the data plane network element will associate and store the report of the first event with the notification association identifier.

[0278] In step 911, the TCF network element sends a fourth message to the event consumer node. This fourth message carries a notification association identifier, which is used by the event consumer node to obtain a report of the first event. Correspondingly, the event consumer node receives the aforementioned fourth message.

[0279] Based on the description information corresponding to the event consumer node, the TCF network element can send the aforementioned fourth message to the event consumer node after selecting the event consumer node.

[0280] In step 912, the event consuming node sends a second request message to the data plane network element, which requests a report of the first event. Correspondingly, the data plane network element receives the second request message.

[0281] In step 913, the data plane network element sends a second response message to the event consumer node, which carries a report of the first event. Correspondingly, the event consumer node receives the second response message.

[0282] Optionally, after the event consumption node obtains the report of the first event, it can also trigger related processes based on the report of the first event, such as updating the UE's policy rules, or adjusting the UPF instance currently selected for the UE, etc., which will not be listed in this application.

[0283] If the event source node directly reports the notification message to the data plane network element, that is, if step 908 is executed, then the data plane network element also needs to execute step 910: the data plane network element reports the event notification status to the TCF network element, so as to trigger the TCF network element to select and notify the event consumer node.

[0284] Figure 10 This is another detailed flowchart illustrating the communication method provided in the embodiments of this application.

[0285] In step 1001, the subscribing network element sends a subscription request to the TCF network element, and correspondingly, the TCF network element receives the subscription request.

[0286] The subscription request includes at least one of the following: the identifier of the first event, context identifier information, event description information, notification type, notification method, or description information corresponding to the event consumer node.

[0287] If the TCF network element determines that the event can be directly returned in the response message, it can search for the report of the first event based on the context stored locally or in the data plane network element, and return it to the event consumer node in the subscription response message. If the TCF determines that the subscription process needs to be triggered, it can continue to execute the following steps.

[0288] In step 1002, the TCF network element sends a fourth request message to the data plane network element, which requests the allocation of a notification association identifier for the first event. Correspondingly, the data plane network element receives the aforementioned fourth request message.

[0289] The fourth request message mentioned above may carry the identifier of the first event and / or the event description information corresponding to the first event.

[0290] In step 1003, the data plane network element sends a fourth response message to the TCF network element, which carries a notification association identifier.

[0291] Optionally, the notification association identifier mentioned above can be a notification association identifier at the TCF granularity.

[0292] Optionally, the notification association identifier can also be assigned by the SDF network element. For example, the SDF network element receives the fourth request message, performs the assignment of the notification association identifier, and then sends the aforementioned notification association identifier to the TCF network element. It is understood that... Figure 9 In the embodiment shown, the notification association identifier can also be assigned by the SDF network element.

[0293] In step 1004, the TCF network element sends message A to the event source node, which may carry a notification association identifier. Correspondingly, the event source node receives message A.

[0294] The message A above can be used to request subscription to the first event. The message A above may also carry at least one of the following: the identifier of the first event, context identifier information, event description information, notification type, notification method, or description information corresponding to the event consumer node.

[0295] In step 1005, the event source node performs event acquisition. For an explanation of step 1005, please refer to [link to relevant documentation]. Figure 9 The relevant descriptions in the document will not be repeated here.

[0296] In step 1006, the event source node sends a notification message to the TCF network element. This notification message may carry the report and notification association identifier of the first event. Correspondingly, the TCF network element receives the notification message.

[0297] In step 1007, the TCF network element sends the aforementioned notification message to the data plane network element. Correspondingly, the data plane network element receives the aforementioned notification message.

[0298] After receiving the notification message, the data plane network element will associate and store the report of the first event with the notification association identifier.

[0299] Optionally, the SDF network element can also receive the aforementioned notification messages from the TCF network element. Additionally, in Figure 9 In this embodiment, the SDF network element can also receive notification messages from the event source node.

[0300] In step 1008, the TCF network element sends a fourth message to the event consumer node. This fourth message carries a notification association identifier, which is used by the event consumer node to obtain a report of the first event. Correspondingly, the event consumer node receives the aforementioned fourth message.

[0301] Based on the description information corresponding to the event consumer node, the TCF network element can send the aforementioned fourth message to the event consumer node after selecting the event consumer node.

[0302] In step 1009, the event consuming node sends a second request message to the data plane network element, which requests a report of the first event. Correspondingly, the data plane network element receives the second request message.

[0303] In step 1010, the data plane network element sends a second response message to the event consumer node, which carries a report of the first event. Correspondingly, the event consumer node receives the second response message.

[0304] Optionally, steps 1007 to 1010 above can be replaced by step 1011, whereby the TCF network element directly sends a notification message to the event consumer node, and the notification message may carry the report and notification association identifier of the first event.

[0305] Optionally, after the event consumption node obtains the report of the first event, it can also trigger related processes based on the report of the first event, such as updating the UE's policy rules, or adjusting the UPF instance currently selected for the UE, etc., which will not be listed in this application.

[0306] Optionally, before step 1001, the process may further include: if the process is not triggered by a TCF network element, TCF addressing may be performed through a data plane network element / SDF network element, such as AF / NEF addressing the TCF network element that provides services to the UE / session; if the process is triggered by a TCF network element, a request may be directly sent to the TCF service address / TCF identifier carried in the process triggered by the TCF network element.

[0307] As previously mentioned, data plane network elements can be DMF network elements. The following will combine... Figure 11When the data plane network element is a DMF network element, the interaction between the DMF network element and the DSF network element and the RMF network element is described in detail.

[0308] Figure 11 This is a schematic diagram of the interaction process within the data plane provided in the embodiments of this application. Figure 11 The internal interaction flow of the data plane network element shown mainly includes the context creation / update / synchronization process (i.e.) Figure 11 The process shown, X), notifies the associated identifier allocation process (i.e. Figure 11 The process shown is Y), the event notification / acquisition process (i.e. Figure 11 The process shown is Z). The event notification process refers to the internal interaction process within the data plane after the event source node reports a notification message to the data plane network element. The event notification retrieval process refers to the internal interaction process within the data plane after the event consumer node sends a request to the data plane network element to retrieve the event report. The following will discuss... Figure 11 The above processes shown are described in detail.

[0309] Process X includes step 0X, step 1X, and step 2X.

[0310] In step 0X, the DMF network element performs user context creation / update / synchronization.

[0311] In step 1X, the DMF network element performs DSF network element addressing using the routing information maintained by the RMF network element to determine the target DSF network element.

[0312] In step 2X, the DMF network element performs a creation / update / synchronization process on the context in the target DSF network element.

[0313] After the DMF network element determines the target DSF network element, it performs a creation / update / synchronization process on the context in the target DSF network element.

[0314] Process Y includes steps 0Y, 1Y, 2Y, 3Y, 4Y, and 5Y.

[0315] In step 0Y, the DMF network element receives a notification associated identifier allocation request.

[0316] The notification association identifier allocation request (an example of the fourth request message) described above is used to request the allocation of a notification association identifier. This notification association identifier allocation request can, for example, originate from a subscribing network element, such as... Figure 6 The first request message shown or as follows Figure 9 The fourth request message shown above, the aforementioned notification association identifier allocation can also come from a TCF network element, such as... Figure 10 The fourth request message shown is not limited in this application.

[0317] In step 1Y, the DMF network element is assigned a notification association identifier.

[0318] After receiving the notification association identifier allocation request, the DMF network element can perform notification association identifier allocation based on the request, and then execute steps 2Y and 4Y.

[0319] In step 2Y, the DMF network element performs context addressing.

[0320] DMF network elements use the routing information maintained by RMF network elements to perform DSF network element addressing to determine the target DSF network element. Thus, the DMF network element and the target DSF network element complete event association storage.

[0321] In step 4Y, the DMF network element performs event association.

[0322] For example, the DMF network element stores subscription context information in the target DSF network element. The subscription context information includes one or more of the following: notification association identifier, description information corresponding to the event consuming node, or context identifier information corresponding to the first event.

[0323] Optionally, the notification association identifier allocation can also be completed by the DMF network element calling the DSF network element. That is, step 1Y can also be replaced by step 3Y: the DMF network element calls the DSF network element to perform the notification association identifier allocation.

[0324] For example, the DMF network element calls the target DSF network element (which may be based on the one obtained in step 2Y) to allocate a notification association identifier, and updates the subscription context information to the target DSF network element based on the notification association identifier. The subscription context information includes one or more of the following: notification association identifier, description information corresponding to the event consumer node, or context identifier information corresponding to the first event.

[0325] In step 5Y, the DMF network element sends a notification associated identifier allocation response.

[0326] The process Z includes step 0Z, step 1Z, and step 2Z.

[0327] In step 0Z, the DMF network element receives an event notification / acquisition request.

[0328] An event notification request refers to an event source node reporting a notification message to a data plane network element directly or indirectly (through TCF network elements). An event notification retrieval request is used to request the retrieval of an event report.

[0329] Scenario 1: The DMF network element receives a notification message, which may carry an event report and a notification association identifier.

[0330] Scenario 2: The DMF network element receives an event notification retrieval request to request an event report. The event notification retrieval request may carry a notification association identifier.

[0331] In step 1Z, the DMF network element performs event notification storage / retrieval.

[0332] Corresponding to Case 1, the DMF network element performs event notification storage. For example, the DMF network element performs DSF addressing based on the notification association identifier and stores the content of the notification message in the target DSF network element.

[0333] Corresponding to scenario 2, the DMF network element performs event notification retrieval. For example, the DMF network element retrieves event reports from the target DSF network element.

[0334] In step 2Z, the DMF network element sends an event notification / receives a response.

[0335] Corresponding to Case 1, the DMF network element sends an event notification response. For example, the event notification response may carry acknowledgment (ACK) information.

[0336] Corresponding to scenario 2, the DMF network element sends an event notification to obtain a response. For example, this event notification response may include an event report.

[0337] The communication method of the embodiments of this application has been described in detail above. The communication device of the embodiments of this application will be described in detail below. The communication device includes modules or units for performing each part of the above embodiments. The modules or units may be software, hardware, or a combination of software and hardware. The following is only a brief illustrative example of the communication device. For details of the implementation, please refer to the description of the foregoing method embodiments, which will not be repeated below.

[0338] Figure 12 This is a schematic block diagram of a communication device 1200 provided in an embodiment of this application. Figure 12 As shown, the communication device 1200 includes a processing module 1210 and a transceiver module 1220.

[0339] In one possible implementation, the communication device 1200 is used to implement the steps corresponding to the data plane network element in the method 500 described above.

[0340] The transceiver module 1220 is used to receive a first request message, which is used to request subscription to a first event. The first request message carries at least one of the following: notification method, cache duration, or description information corresponding to the event consumer node. The notification method is used to indicate whether the sender of the first request message is an event consumer node, and the cache duration is used to indicate the storage duration of the context information corresponding to the first event. The processing module 1210 is used to execute an event query process based on the first request message. The processing module 1210 is also used to execute an event notification process based on the first request message.

[0341] Optionally, the first request message may further include at least one of the following: context identification information, the identifier of the first event, the event description information corresponding to the first event, the notification type of the first event, or the notification address corresponding to the first event.

[0342] Optionally, the processing module 1210 is specifically used to perform context addressing based on the first request message to obtain a report of the first event; the processing module 1210 is specifically used to send a first response message to the event consumer node, the first response message carrying a report of the first event; or, based on the cache duration, to determine to return a report of the first event through an independent message.

[0343] Optionally, the processing module 1210 is specifically configured to send a first message to the TCF network element, the first message being used by the TCF network element to select an event consumer node; receive a second request message from the event consumer node, the second request message being used to request to obtain a report of the first event; and send a second response message to the event consumer node, the second response message carrying a report of the first event.

[0344] Optionally, the processing module 1210 is specifically configured to receive a context update request from the event source node, the context update request being used to request an update of context information, the context update request carrying a report of the first event.

[0345] Optionally, the transceiver module 1220 is further configured to: receive a third request message from the event source node, the third request message being used to request the acquisition of context information; and send a third response message to the event source node, the third response message carrying the event subscription list corresponding to the first event.

[0346] Optionally, the processing module 1210 is specifically configured to send a subscription request based on the first request message, the subscription request being used to request subscription to the first event from the event source node; and receive a second message from the event source node, the second message carrying a report and notification association identifier of the first event.

[0347] Optionally, the data plane network element is a DMF network element, and the processing module 1210 is specifically used to directly receive the second message from the event source node; or, to receive the second message from the event source node forwarded by the DSF network element.

[0348] Optionally, the aforementioned data plane network element is a DMF network element, and the aforementioned processing module 1210 is further configured to allocate a notification association identifier for the first event and store the subscription context information in the DSF network element; or, call the DSF network element to perform the allocation of the notification association identifier and update the subscription context information in the DSF network element based on the notification association identifier, wherein the aforementioned subscription context information includes one or more of the following: notification association identifier, description information corresponding to the event consumption node, or context identifier information corresponding to the first event.

[0349] In one possible implementation, the communication device 1200 is used to implement the steps corresponding to the data plane network element in the method 700 described above.

[0350] The transceiver module 1220 is used to receive a fourth request message, which requests the allocation of a notification association identifier for the first event; send a fourth response message, which carries the notification association identifier corresponding to the first event; and receive a notification message from a TCF network element or event source node, which carries the report and notification association identifier of the first event.

[0351] Optionally, the transceiver module 1220 is specifically used to receive a fourth request message from a subscribing network element; or, to receive a fourth request message from a TCF network element.

[0352] Optionally, the processing module 1210 is used to record subscription context information, which includes one or more of the following: notification association identifier, description information corresponding to the event consumption node, and context identifier information corresponding to the first event.

[0353] Optionally, the transceiver module 1220 is further configured to send a first message to the TCF network element, the first message being used by the TCF network element to select an event consumer node; receive a second request message from the event consumer node, the second request message being used to request a report of the first event; and send a second response message to the event consumer node, the second response message carrying a report of the first event.

[0354] Optionally, the aforementioned data plane network element is a DMF network element, and the aforementioned processing module 1210 is used to allocate a notification association identifier for the first event and store the subscription context information in the DMF network element; or, call the DMF network element to perform the allocation of the notification association identifier and update the subscription context information in the DMF network element based on the notification association identifier, wherein the aforementioned subscription context information includes one or more of the following: notification association identifier, description information corresponding to the event consumption node, and context identifier information corresponding to the first event.

[0355] Optionally, the transceiver module 1220 is specifically used to directly receive notification messages from TCF network elements or event source nodes; or, to receive notification messages from TCF network elements or event source nodes that have been forwarded by DSF network elements.

[0356] In one possible implementation, the communication device 1200 is used to implement the steps corresponding to the TCF network element in the method 800 described above.

[0357] The transceiver module 1220 is used to receive a subscription request, which is used to request to subscribe to the first event from the event source node; and to send a third message to the event source node, which is used to request to subscribe to the first event from the event source node, and the third message carries a notification association identifier.

[0358] Optionally, the subscription request may include one or more of the following: the notification type of the first event, the event description information corresponding to the first event, the notification association identifier, or the description information corresponding to the event consumption node.

[0359] Optionally, the transceiver module 1220 is also used to receive a notification message, which carries a report of the first event and a notification association identifier; and to send a notification message or a notification association identifier to the event consumer node.

[0360] Optionally, the transceiver module 1220 is further configured to receive a first message from the data plane network element, the first message being used by the TCF network element to select an event consumer node; and to send a notification association identifier to the event consumer node.

[0361] It should be understood that the communication device 1200 here is embodied in the form of a functional module. The term "module" here can refer to application-specific integrated circuits (ASICs), electronic circuits, processors (e.g., shared processors, proprietary processors, or group processors) and memories for executing one or more software or firmware programs, combined logic circuits, and / or other suitable components supporting the described functions. In an alternative example, those skilled in the art will understand that the communication device 1200 can specifically be a data plane network element, TCF network element, event consumer node, or event source node, etc., as described in the above embodiments. The communication device 1200 can be used to execute the various processes and / or steps corresponding to the data plane network element, TCF network element, event consumer node, or event source node, etc., as described in the above method embodiments. To avoid repetition, these will not be elaborated further here.

[0362] The aforementioned communication device 1200 has the function of implementing the corresponding steps executed by the data plane network element, TCF network element, event consumer node, or event source node in the above method; the above functions can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions. In the embodiments of this application, Figure 12 The communication device 1200 in the middle can also be a chip.

[0363] It should be understood that the module division in the embodiments of this application is illustrative and only represents a logical functional division. In actual implementation, there may be other division methods. Furthermore, the functional modules in the various embodiments of this application can be integrated into a single processor, exist as separate physical entities, or be integrated into a single module. The integrated modules described above can be implemented in hardware or as software functional modules.

[0364] Figure 13 This is a schematic block diagram of another communication device 1300 provided in the embodiments of this application.

[0365] The communication device 1300 can be a chip system, or it can be an apparatus configured with a chip system to implement the methods described in the above-described method embodiments. In the embodiments of this application, the chip system can be composed of chips, or it can include chips and other discrete devices.

[0366] like Figure 13 As shown, the communication device 1300 may include a processor 1310, which can be used to execute computer programs or instructions stored in memory to achieve... Figures 5 to 11 The method described in any of the embodiments shown.

[0367] The communication device 1300 also includes a communication interface 1320. The communication interface 1320 can be used to communicate with other devices via a transmission medium, thereby enabling the communication device 1300 to communicate with other devices. The communication interface 1320 can be, for example, a transceiver, interface, pin, bus, circuit, or a device capable of transmitting and receiving functions. The processor 1310 can utilize the communication interface 1320 to input and output data and to implement... Figures 5 to 11 The method described in any of the embodiments shown.

[0368] In one possible implementation, the communication device 1300 further includes at least one memory 1330 for storing program instructions and / or data. The memory 1330 is coupled to the processor 1310. The coupling in this embodiment is an indirect coupling or communication connection between devices, units, or modules, and can be electrical, mechanical, or other forms, used for information exchange between devices, units, or modules. The processor 1310 may operate in conjunction with the memory 1330. The processor 1310 may execute program instructions stored in the memory 1330. At least one of the at least one memory may be included in the processor.

[0369] It should be understood that the coupling in the embodiments of this application is an indirect coupling or communication connection between devices, units, or modules, which can be electrical, mechanical, or other forms, used for information interaction between devices, units, or modules. The processor 1310 may operate in conjunction with the memory 1330. The embodiments of this application do not limit the specific connection medium between the processor 1310, communication interface 1320, and memory 1330. Optionally, the processor 1310, communication interface 1320, and memory 1330 are connected via a bus 1340. The bus 1340 is... Figure 13 The connections between other components are shown in bold lines only and are not intended to be limiting. The bus can be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. The bus can be divided into address bus, data bus, control bus, etc. For ease of illustration, Figure 13 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0370] This application also provides a computer program product, which includes: a computer program (also referred to as code or instructions), which, when run, can achieve... Figures 5 to 11 The method described in any of the embodiments shown.

[0371] This application also provides a computer-readable storage medium storing a computer program (also referred to as code or instructions). When the computer program is executed, it can achieve... Figures 5 to 11 The method described in any of the embodiments shown.

[0372] It should be understood that the processor in the embodiments of this application can be an integrated circuit chip with signal processing capabilities. In implementation, each step of the above method embodiments can be completed by the integrated logic circuits in the processor's hardware or by instructions in software form. The processor can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a microprocessor unit (MPU), a microcontroller unit (MCU), a graphics processing unit (GPU), an artificial intelligence processor (AI processor) or a neural processing unit (NPU), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or a combination of one or more discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly embodied in the execution of a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software module can reside in a mature storage medium in the field, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, or registers. This storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method.

[0373] It should also be understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be a cache, 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), 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 linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM). It should be noted that the memory used in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0374] The terms "unit," "module," etc., used in this specification can be used to refer to computer-related entities, hardware, firmware, combinations of hardware and software, software, or software in execution. In the embodiments of this application, "unit" and "module" have the same meaning and can be used interchangeably.

[0375] Those skilled in the art will recognize that the various illustrative logical blocks and steps described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application. In the several embodiments provided in this application, it should be understood that the disclosed apparatus, devices, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for example, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the shown or discussed mutual couplings or direct couplings or communication connections may be through some interfaces; indirect couplings or communication connections between devices or units may be electrical, mechanical, or other forms.

[0376] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0377] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0378] In the above embodiments, the functions of each functional unit can be implemented entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions (programs). When the computer program instructions (programs) are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., digital video discs, DVDs), or semiconductor media (e.g., solid-state drives, SSDs), etc.

[0379] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the technology, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, ROM, RAM, magnetic disks, or optical disks.

[0380] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A communication method, characterized in that, Applied to data plane network elements, the method includes: Receive a first request message, the first request message is used to request subscription to a first event, the first request message carries at least one of the following: notification method, cache duration or description information corresponding to the event consumer node, the notification method is used to indicate whether the sender of the first request message is an event consumer node, the cache duration is used to indicate the storage duration of the context information corresponding to the first event; Based on the first request message, execute the event query process; Based on the first request message, the event notification process is executed.

2. The method as described in claim 1, characterized in that, The first request message also carries at least one of the following: context identification information, the identifier of the first event, the event description information corresponding to the first event, the notification type of the first event, or the notification address corresponding to the first event.

3. The method as described in claim 1 or 2, characterized in that, The step of executing the event query process based on the first request message includes: Based on the first request message, perform context addressing to obtain a report of the first event; The step of executing the event notification process based on the first request message includes: sending a first response message to the event consumer node, wherein the first response message carries a report of the first event; or, Based on the cache duration, a report is determined to be returned for the first event via a separate message.

4. The method as described in claim 1 or 2, characterized in that, The step of executing the event notification process based on the first request message includes: Send a first message to the TCF network element with task-centric function, the first message being used by the TCF network element to select the event consumption node; Receive a second request message from the event consumer node, the second request message being used to request a report of the first event; A second response message is sent to the event consumer node, the second response message carrying a report of the first event.

5. The method as described in claim 4, characterized in that, The step of executing the event query process based on the first request message includes: Receive a context update request from the event source node, the context update request being used to request an update to the context information, the context update request carrying a report of the first event.

6. The method as described in claim 5, characterized in that, The method further includes: Receive a third request message from the event source node, the third request message being used to request the acquisition of context information; A third response message is sent to the event source node, the third response message carrying the event subscription list corresponding to the first event.

7. The method as described in claim 4, characterized in that, The step of executing the event query process based on the first request message includes: Based on the first request message, a subscription request is sent, the subscription request being used to request the event source node to subscribe to the first event; Receive a second message from the event source node, the second message carrying the report and notification association identifier of the first event.

8. The method according to any one of claims 1 to 7, characterized in that, The data plane network element is a data management function (DMF) network element, and the method further includes: Assign a notification association identifier to the first event and store the subscription context information in the DSF network element; or, The DSF network element is invoked to perform notification association identifier allocation, and subscription context information is updated to the DSF network element based on the notification association identifier. The subscription context information includes one or more of the following: notification association identifier, description information corresponding to the event consumption node, or context identifier information corresponding to the first event.

9. The method as described in claim 7, characterized in that, The data plane network element is a data management function (DMF) network element, and the receiving of the second message from the event source node includes: Directly receive the second message from the event source node; or, Receive the second message from the event source node, which is forwarded by the DSF network element.

10. A communication method, characterized in that, Applied to data plane network elements, the method includes: Receive a fourth request message, the fourth request message being used to request the allocation of a notification association identifier for the first event; Send a fourth response message, which carries a notification association identifier corresponding to the first event; Receive a notification message from a task-centric TCF network element or an event source node, the notification message carrying a report of the first event and the notification association identifier.

11. The method as described in claim 10, characterized in that, The receiving of the fourth request message includes: Receive the fourth request message from the subscribed network element; or, Receive the fourth request message from the TCF network element.

12. The method as described in claim 10 or 11, characterized in that, The method further includes: Record subscription context information, which includes one or more of the following: notification association identifier, description information corresponding to the event consumption node, and context identifier information corresponding to the first event.

13. The method according to any one of claims 10 to 12, characterized in that, The method further includes: Send a first message to the TCF network element, the first message being used by the TCF network element to select an event consumption node; Receive a second request message from the event consumer node, the second request message being used to request a report of the first event; A second response message is sent to the event consumer node, the second response message carrying a report of the first event.

14. The method according to any one of claims 10 to 13, characterized in that, The data plane network element is a data management function (DMF) network element, and the method further includes: Assign a notification association identifier to the first event and store the subscription context information in the DSF network element; or, The DSF network element is invoked to perform notification association identifier allocation, and subscription context information is updated to the DSF network element based on the notification association identifier. The subscription context information includes one or more of the following: notification association identifier, description information corresponding to the event consumption node, and context identifier information corresponding to the first event.

15. The method as described in claim 14, characterized in that, The receiving of notification messages from TCF network elements or event source nodes includes: Directly receive notification messages from TCF network elements or event source nodes; or, Receive notification messages from the TCF network element or event source node that are forwarded by the DSF network element.

16. A communication method, characterized in that, Applied to task-centric TCF network elements, the method includes: Receive a subscription request, the subscription request being used to request subscription to a first event from the event source node; A third message is sent to the event source node. The third message is used to request to subscribe to the first event from the event source node. The third message carries a notification association identifier.

17. The method as described in claim 16, characterized in that, The subscription request carries one or more of the following: the notification type of the first event, the event description information corresponding to the first event, the notification association identifier, or the description information corresponding to the event consumption node.

18. The method as described in claim 16 or 17, characterized in that, The method further includes: Receive a notification message, the notification message carrying a report of the first event and the notification association identifier; Send the notification message or the notification association identifier to the event consumption node.

19. The method as described in claim 16 or 17, characterized in that, The method further includes: Receive a first message from the data plane network element, the first message being used by the TCF network element to select an event consumption node; Send the notification association identifier to the event consumption node.

20. A communication method, characterized in that, The method, applied to the signaling distribution function (SDF) network element, includes: Receive a fourth request message, the fourth request message being used to assign a notification association identifier to the first event; Receive a notification message from a task-centric TCF network element or an event source node, wherein the notification message carries a report of the first event and the notification association identifier; Send a first message to the TCF network element. The first message is used by the TCF network element to select an event consumption node.

21. A communication device, characterized in that, include: Includes a module for performing the method as described in any one of claims 1 to 20.

22. A communication device, characterized in that, include: A processor, when invoked from a computer program in memory, causes the apparatus to perform the method as described in any one of claims 1 to 20.

23. A computer-readable storage medium, characterized in that, Used to store a computer program, the computer program including instructions for implementing the method as described in any one of claims 1 to 20.

24. A computer program product, the computer program product comprising instructions, characterized in that, When the instructions are executed on a computer, the computer causes the computer to perform the method as described in any one of claims 1 to 20.

Images