Communication method and apparatus

Abstract

The present application provides a communication method and an apparatus. The method comprises: receiving from a second network function a subscription request for a first event, where the subscription request comprises subject information corresponding to the first event and an identifier of the first event, and the subject information and / or the identifier of the first event corresponds to network information of the first event; and, after a trigger notification for the first event is acquired, sending the trigger notification to the second network function, where the trigger notification corresponds to the network information. In the present application, the subscription request for the first event that carries the network information allows for subscription to the first event in a specified network.

Description

A communication method and apparatus

[0001] Cross-reference to related applications

[0002] This application claims priority to Chinese Patent Application No. 202411449819.6, filed on October 16, 2024, entitled "A Communication Method and Apparatus", the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application relates to the field of communication technology, and in particular to a communication method and apparatus. Background Technology

[0004] In current mobile networks, the event subscription process involves the event subscriber obtaining the event monitor's identity and the interface information provided by the monitor, while the event monitor maintains the subscriber's identity and the event binding relationships. When an event is triggered, the event monitor sends an event notification to each subscriber based on the binding relationship between the event and the subscriber. The coupling between the event subscriber and the event monitor is strong; therefore, when the event subscriber or event monitor changes, or when mobile network services are upgraded, it's crucial to consider how to maintain the aforementioned information (e.g., interface information, binding relationships, etc.). Summary of the Invention

[0005] This application provides a communication method and apparatus to decouple event subscribers from event monitors, thereby improving the processing efficiency of subscribed events.

[0006] Firstly, this application provides a communication method that can be executed through a first network function used for event subscription management and event notification management. The first network function can be the first network function itself, a component within the first network function (e.g., a processor, chip, or chip system), or a logic module or software implementing all or part of the first network function. This application does not specifically limit the scope of the method.

[0007] The method includes: receiving a subscription request for a first event from a second network function, the subscription request including topic information corresponding to the first event and an identifier of the first event, wherein the topic information and / or the identifier of the first event correspond to network information of the first event; and after obtaining a trigger notification of the first event, sending a trigger notification to the second network function, wherein the trigger notification corresponds to the network information.

[0008] In this application, the second network function (e.g., the event subscription function) can subscribe to a first event in a specified network by sending a subscription request carrying network information to the first network function. Furthermore, using the first network function to manage event subscription and event notification can improve the efficiency of event processing and decouple the event subscription function from the event monitoring function.

[0009] In one possible approach, the subscription request may also include: first authentication information.

[0010] For example, the first authentication information can be understood as the first event invocation key or invocation token, etc. The second network function carries the first authentication information in the subscription request so that the first network function can authenticate the second network function, thereby reducing the possibility of information leakage caused by network functions that do not have the ability to subscribe to the first event.

[0011] In one possible approach, if the first authentication information matches the second authentication information pre-stored in the first network function, then it is determined that the second network function has the permission to subscribe to the first event, and the second authentication information is used to indicate the identity information of the user of the first event.

[0012] Specifically, when the first network function is also used for authenticating the identity of event users (event subscribers or event monitors), the first network function can compare the pre-stored second authentication information with the first authentication information to determine whether the second network function has the authority to subscribe to the first event, thereby reducing the possibility of information leakage caused by network functions that do not have the authority to subscribe to the first event.

[0013] In one possible approach, a first authentication request message is sent to a third network function. The first authentication request message includes first authentication information and is used to request the third network function to authenticate whether the second network function has the permission to subscribe to the first event. A first authentication result is received from the third network function. Based on the first authentication result, it is determined whether the second network function has the permission to subscribe to the first event.

[0014] The third network function is used to authenticate the identity of the user of the event. The first network function authenticates the identity of the second network function by sending a first authentication request message to the third network function. This can improve the real-time performance of data processing and save the processing resources of the first network function in a stateless manner (without storing the context related to the first event).

[0015] In one possible approach, the first authentication request message may also include: subject information, and / or, an identifier of the first event.

[0016] When a third network function stores authentication information indicating the identity information of multiple users for multiple different events, and / or when the first authentication information cannot be parsed to reveal the associated event information, the third network function can clearly identify the specific event associated with the first authentication information and the network information corresponding to that specific event when the first authentication request message includes subject information and / or the identifier of the first event. Based on the identifier of the first event, the third network function can select the second authentication information corresponding to the user of the first event from the stored authentication information of the user's identity information for multiple different events, and compare the second authentication information corresponding to the user of the first event with the first authentication information, thereby improving the authentication efficiency of the second network function. Furthermore, different networks may include the same first event. When the subject information corresponds to the network information of the first event, including the subject information in the first authentication request message facilitates the third network function in selecting the second authentication information corresponding to the user of the first event in the specified network from the stored authentication information based on the network information.

[0017] In one possible approach, the first network function receives an event trigger notification from the fifth network function. The trigger notification includes topic information corresponding to the first event and an identifier of the first event, wherein the topic information and / or the identifier of the first event correspond to the network information of the first event.

[0018] In this application, the fifth network function detects the triggering of the first event and sends an event triggering notification to the first network function. Based on this, the first network function can respond to the processing of the event triggering notification in a timely manner. When the triggering notification includes the topic information corresponding to the first event and the identifier of the first event, the first network function can clearly identify which specific event in which network the triggering notification corresponds to, so as to perform the corresponding processing.

[0019] In one possible approach, the notification may also include third-party authentication information.

[0020] For example, the third authentication information can be understood as the first event call key or call token, etc. The fifth network function carries the third authentication information in the trigger notification so that the first network function can authenticate the identity of the fifth network function, thereby reducing the possibility of information leakage caused by the network function that does not have the ability to monitor the first event.

[0021] In one possible approach, if the third authentication information matches the second authentication information pre-stored in the first network function, then it is determined that the fifth network function has the authority to monitor the first event, and the second authentication information is used to indicate the identity information of the user of the first event.

[0022] In this application, when the first network function is also used for authenticating the identity of event users (event subscribers or event monitors), the first network function can compare the pre-stored second authentication information with the third authentication information to determine whether the fifth network function has the authority to monitor the first event, thereby reducing the possibility of information leakage caused by network functions that do not have the authority to monitor the first event.

[0023] In one possible approach, a second authentication request message is sent to a third network function, the second authentication request message including third authentication information, the second authentication request message being used to request the third network function to authenticate whether the fifth network function has the authority to monitor the first event; a second authentication result is received from the third network function; and the authority to monitor the first event is determined based on the second authentication result.

[0024] The third network function is used to authenticate the identity of the user involved in the event. The first network function authenticates the identity of the fifth network function by sending a second authentication request message to the third network function. This can improve the real-time performance of data processing and save processing resources of the first network function in a stateless manner (without storing the context related to the first event).

[0025] In one possible approach, the second authentication request message may also include: subject information, and / or, an identifier of the first event.

[0026] When the third network function stores authentication information indicating the identity information of multiple users for multiple different events, and / or the second authentication information cannot be parsed to obtain the associated event information, when the second authentication request message includes subject information and / or the identifier of the first event, the third network function can clearly identify the specific event associated with the first authentication information and the network information corresponding to that specific event. Based on the identifier of the first event, the third network function can select the second authentication information corresponding to the user of the first event from the stored authentication information of the identity information of users for multiple different events, and compare the second authentication information corresponding to the user of the first event with the third authentication information, thereby improving the authentication efficiency of the fifth network function. Furthermore, different networks may include the same first event. When the subject information corresponds to the network information of the first event, including the subject information in the second authentication request message facilitates the third network function in selecting the second authentication information corresponding to the user of the first event in the specified network from the stored authentication information based on the network information.

[0027] In one possible approach, before receiving a subscription request for a first event from a second network function, an event registration request message is received from a fourth network function, the event registration request message including: subject information of the first event and identifier of the first event; an event registration response message is sent to the fourth network function, the event registration response message including: registration result and second authentication information.

[0028] Based on this, the first network function can clearly define the context information of the first event and assign second authentication information to indicate the identity information of the user of the first event.

[0029] In one alternative, the fourth network function is one or more of the following: capability open network function, service control function, service orchestration function, access network service management function, core network service management function, mobile network operation and maintenance management system, or a fifth network function, the fifth network function being used to monitor the first event.

[0030] Various network functions can register with the primary network function after acquiring event configuration information, making them suitable for different scenarios. Among these, service control and service orchestration are network functions that may exist in future mobile networks. Compared to existing network services that only interact between network functions that have already deployed services, the introduction of service control and service orchestration functions allows for event registration and subscription for services before the services are deployed on the network functions involved, thus reducing dependence on network functions. For different services, the event-related registration and subscription processes can be configured more flexibly.

[0031] In one possible approach, the event registration request message may also include: the handling rules for the first event.

[0032] Based on this, the first network function can clearly define the execution conditions and execution operations of the first event.

[0033] In one possible manner, the subject information includes one or more of the following: user information of the first event, or business information of the first event.

[0034] The application scope or monitoring target of the first event can be clearly defined based on the user information or business information of the first event.

[0035] In one possible approach, network information includes one or more of the following: public land mobile network (PLMN) information, network slice information, non-public network (NPN) information, and subnet information.

[0036] Based on this, the first network function can clearly identify the specific network information of the second network function calling the first event.

[0037] In one possible manner, the topic information and / or the identifier of the first event corresponding to the network information of the first event includes one of the following: the topic information indicates network information; or, the identifier of the first event indicates network information; or, both the topic information and the identifier of the first event indicate network information.

[0038] When the subscription to the first event can be provided in different networks, the first event can be invoked in a specific network based on topic information and / or the identifier of the first event, and the network information for invoking the first event can be specified for the function of the second network.

[0039] Secondly, this application provides a communication method that can be executed through a second network function used to subscribe to a first event. The second network function can be the second network function itself, a component within the second network function (e.g., a processor, chip, or chip system), or a logic module or software implementing all or part of the second network function. This application does not specifically limit the scope here. The method includes:

[0040] Send a subscription request for a first event to a first network function. The subscription request includes topic information corresponding to the first event and an identifier of the first event, wherein the topic information and / or the identifier of the first event correspond to network information of the first event; receive a trigger notification for the first event from the first network function, wherein the trigger notification corresponds to network information.

[0041] In one possible approach, the subscription request may also include: the rules for handling the first event.

[0042] In one possible manner, the subject information includes one or more of the following: user information of the first event, or business information of the first event.

[0043] In one possible manner, network information includes one or more of the following: PLMN information, network slice information, NPN information, and subnet information.

[0044] In one possible manner, the topic information and / or the identifier of the first event corresponding to the network information of the first event includes one of the following: the topic information indicates network information; or, the identifier of the first event indicates network information; or, both the topic information and the identifier of the first event indicate network information.

[0045] Thirdly, this application provides a communication method that can be executed through a third network function used to authenticate the identity of an event user. This third network function can be the third network function itself, a component within the third network function (e.g., a processor, chip, or chip system), or a logical module or software implementing all or part of the third network function. This application does not specifically limit the scope here. The method includes:

[0046] Receive an event registration request message from the fourth network function. The event registration request message includes: the topic information of the first event and the identifier of the first event, wherein the topic information and / or the identifier of the first event correspond to the network information of the first event; the first event is any one of the subscribed events; send an event registration response message to the fourth network function. The event registration response message includes: the registration result and the second authentication information, which is used to indicate the identity information of the user of the first event.

[0047] Based on this, the third network function can record the information corresponding to the first event and assign second authentication information to indicate the identity information of the user of the first event, which can be used by other network functions to subscribe to and notify the first event.

[0048] In one possible approach, first configuration information is sent to the subscription network function of the first event, the first configuration information including: topic information, the identifier of the first event, and second authentication information; and / or, second configuration information is sent to the monitoring network function of the first event, the second configuration information including: topic information, the identifier of the first event, and second authentication information.

[0049] Based on this, subscribers to the first event can clearly identify the events they can subscribe to, and monitors of the first event can clearly identify the events they can monitor.

[0050] In one possible approach, the first configuration information may further include: a subscription instruction for the first event, and / or, a processing rule for the first event; the second configuration information may further include: a monitoring instruction for the first event, and / or, a processing rule for the first event.

[0051] When the first configuration information includes a subscription instruction for the first event, the subscription network function for the first event can explicitly perform the processing related to the subscription of the first event. When the first configuration information includes processing rules for the first event, the subscription network function for the first event can specify the specific processing granularity of the first event. When the second configuration information includes a monitoring instruction for the first event, the monitoring network function for the first event can explicitly perform the processing related to the monitoring of the first event. When the second configuration information includes processing rules for the first event, the monitoring network function for the first event can specify the specific processing granularity of the first event.

[0052] In one possible approach, a first authentication request message is received from a first network function. The first authentication request message includes first authentication information. The first authentication request message is used to request a third network function to authenticate whether a second network function has the permission to subscribe to a first event. The second network function is used to subscribe to the first event. A first authentication result is determined based on the first authentication information and the second authentication information. The first authentication result is then sent to the first network function.

[0053] In one possible approach, a second authentication request message is received from a first network function. The second authentication request message includes third authentication information. The second authentication request message is used to request the third network function to authenticate whether the fifth network function has the authority to monitor the first event. The fifth network function is used to monitor the first event. A second authentication result is determined based on the first authentication information and the second authentication information. The second authentication result is then sent to the first network function.

[0054] In one possible manner, the first authentication request message includes: subject information of the first event, and / or, the identifier of the first event.

[0055] In one possible approach, the second authentication request message may also include: subject information, and / or, an identifier of the first event.

[0056] In one possible approach, the event registration request message may also include the processing rules for the first event.

[0057] In one possible approach, the registration response message may also include: information about a first network function used for event subscription and event notification management.

[0058] Since multiple first network functions may be deployed in the network, the registration response message may optionally include information about the first network function.

[0059] In one possible manner, the subject information includes one or more of the following: user information of the first event, or business information of the first event.

[0060] In one possible manner, the fourth network function is one or more of the following: capability open network function, service control function, service orchestration function, access network service management function, core network service management function, mobile network operation and maintenance management system, or a fifth network function, the fifth network function being used to monitor the first event.

[0061] In one possible manner, network information includes one or more of the following: PLMN information, network slice information, NPN information, and subnet information.

[0062] In one possible manner, the topic information and / or the identifier of the first event corresponding to the network information of the first event includes one of the following: the topic information indicates network information; or, the identifier of the first event indicates network information; or, both the topic information and the identifier of the first event indicate network information.

[0063] Fourthly, this application provides a communication method that can be executed through a fourth network function. This fourth network function can be the fourth network function itself, a component within the fourth network function (e.g., a processor, chip, or chip system), or a logic module or software implementing all or part of the fourth network function. This application does not specifically limit the scope here. The method includes:

[0064] Send an event registration request message, which includes: the topic information of the first event and the identifier of the first event, wherein the topic information and / or the identifier of the first event correspond to the network information of the first event, and the first event is any one of the subscribed events; receive an event registration response message, which includes: the registration result and the second authentication information, which is used to indicate the identity information of the user of the first event.

[0065] In one possible approach, the event registration request message may also include the processing rules for the first event.

[0066] In one possible approach, the registration response message may also include: information about a first network function used for event subscription and event notification management.

[0067] In one possible manner, the subject information includes one or more of the following: user information of the first event, or business information of the first event.

[0068] In one possible manner, the fourth network function is one or more of the following: capability open network function, service control function, service orchestration function, access network service management function, core network service management function, mobile network operation and maintenance management system, or a fifth network function, the fifth network function being used to monitor the first event.

[0069] In one possible manner, network information includes one or more of the following: PLMN information, network slice information, NPN information, and subnet information.

[0070] In one possible manner, the topic information and / or the identifier of the first event corresponding to the network information of the first event includes one of the following: the topic information indicates network information; or, the identifier of the first event indicates network information; or, both the topic information and the identifier of the first event indicate network information.

[0071] Fifthly, embodiments of this application provide a communication device, which may include a first network function, a second network function, a third network function, a fourth network function, and a fifth network function. The communication device is equipped with the functions described in the first to fourth aspects. For example, the communication device includes modules, units, or means that perform the steps involved in the first to fourth aspects. These functions, units, or means can be implemented by software, hardware, or hardware executing corresponding software.

[0072] In one possible design, the communication device includes a processing unit and a transceiver unit. The transceiver unit can be used to send and receive signals to enable communication between the communication device and other devices. For example, the transceiver unit can be used to receive subscription requests for a first event. The processing unit can be used to perform some internal operations of the communication device. The transceiver unit can be called an input / output unit, a communication unit, etc., and can be a transceiver; the processing unit can be a processor. When the communication device is a module (e.g., a chip) in a communication device, the transceiver unit can be an input / output interface, input / output circuit, or input / output pins, etc., and can also be called an interface, communication interface, or interface circuit, etc.; the processing unit can be a processor, processing circuit, or logic circuit, etc.

[0073] In another possible design, the communication device includes a processor and may further include a transceiver for transmitting and receiving signals. The processor executes program instructions to perform the methods in any of the possible designs or implementations of the first to fourth aspects described above. The communication device may also include one or more memories coupled to the processor. The memories may store necessary computer programs or instructions for implementing the functions involved in the first to fourth aspects described above. The processor can execute the computer programs or instructions stored in the memory, and when the computer programs or instructions are executed, the communication device performs the methods in any of the possible designs or implementations of the first to fourth aspects described above.

[0074] In another possible design, the communication device includes a processor that can be coupled to a memory. The memory can store necessary computer programs or instructions for implementing the functions described in the first to fourth aspects above. The processor can execute the computer programs or instructions stored in the memory, causing the communication device to implement the methods in any possible design or implementation of the first to fourth aspects above when the computer programs or instructions are executed.

[0075] In another possible design, the communication device includes a processor and an interface circuit, wherein the processor is used to communicate with other devices through the interface circuit and to perform the methods in any possible design or implementation of the first to fourth aspects described above.

[0076] In one possible design, the communication device is a chip or chip system.

[0077] Understandably, in the fifth aspect above, 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. Furthermore, there can be one or more processors, and one or more memories. The memory can be integrated with the processor, or the memory and processor can be separate. In specific implementations, the memory can be integrated with the processor on the same chip, or it can be set on different chips. This application does not limit the type of memory or the arrangement of the memory and processor.

[0078] Sixthly, embodiments of this application provide a communication system including the aforementioned first network function, second network function, third network function, fourth network function, and fifth network function. The first network function executes the method in the first aspect, the second network function executes the method in the second aspect, the third network function executes the method in the third aspect, and the fourth network function executes the method in the fourth aspect. Furthermore, it should be noted that each aspect may involve processes executed interactively by multiple devices or network elements; the corresponding processes are not executed by a single device or network element, but primarily through the interaction of corresponding devices or network elements. This will not be elaborated upon here. For example, in the first aspect, the first network function receives a subscription request for a first event from the second network function, provided that the second network function sends a subscription request for the first event to the first network function. This will not be further elaborated upon here.

[0079] In a seventh aspect, this application provides a chip system including a processor and potentially a memory, for implementing the methods described in the first to fourth aspects above. The chip system may be composed of chips or may include chips and other discrete devices.

[0080] Eighthly, this application also provides a computer-readable storage medium storing computer-readable instructions that, when executed on a computer, cause the computer to perform the methods described in the first to fourth aspects.

[0081] Ninthly, this application provides a computer program product comprising a computer program or instructions, which, when run on a computer, causes the computer to perform the methods of the embodiments of the first to fourth aspects described above. Attached Figure Description

[0082] Figure 1 shows a schematic diagram of a communication system provided in an embodiment of this application;

[0083] Figure 2 shows a schematic diagram of an event management function provided in an embodiment of this application;

[0084] Figure 3 illustrates an event subscription diagram;

[0085] Figure 4 illustrates an event subscription process according to an embodiment of this application;

[0086] Figure 5 illustrates a schematic diagram of an event subscription process provided in an embodiment of this application;

[0087] Figure 6 illustrates a schematic diagram of an event subscription process provided in an embodiment of this application;

[0088] Figure 7 illustrates a schematic diagram of an event subscription process provided in an embodiment of this application;

[0089] Figure 8 illustrates an event subscription process according to an embodiment of this application;

[0090] Figure 9 shows a schematic diagram of the communication device provided in an embodiment of this application;

[0091] Figure 10 shows a schematic diagram of the communication device provided in an embodiment of this application;

[0092] Figure 11 shows a schematic diagram of the structure of the communication device provided in an embodiment of this application. Detailed Implementation

[0093] To make the objectives, technical solutions, and advantages of this application clearer, a further detailed description of this application will be provided below in conjunction with the accompanying drawings. The specific operational methods in the method embodiments can also be applied to the device embodiments or system embodiments. In the description of this application, unless otherwise stated, "multiple" means two or more. Therefore, implementations of the device and method can be referred to mutually, and repeated details will not be repeated.

[0094] To address the challenges of wireless broadband technology and maintain the leading edge of the 3rd Generation Partnership Project (3GPP) network, the 3GPP standards group developed the 5G standard. thThis architecture supports not only radio access technologies defined by the 3GPP standards group (such as Long Term Evolution (LTE) and 5G Radio Access Network (RAN)) to access the 5G core network (CN), but also supports access to the core network using non-3GPP access technologies through non-3GPP interworking functions (N3IWF) or next-generation packet data gateways (ngPDG).

[0095] Figure 1 illustrates a schematic diagram of a mobile communication network architecture, which includes a terminal (Figure 1 uses user equipment (UE) as an example), access network equipment (Figure 1 uses (R)AN equipment as an example), access and mobility management functions (Figure 1 uses access and mobility management function (AMF) as an example), session management functions (Figure 1 uses session management function (SMF) as an example), user plane functions (Figure 1 uses user plane function (UPF) as an example), policy control functions (Figure 1 uses policy control function (PCF) as an example), network repository functions (Figure 1 uses network repository function (NRF) as an example), unified data management functions (Figure 1 uses unified data management (UDM) as an example), authentication service functions (Figure 1 uses authentication server function (AUSF) as an example), and network exposure functions (Figure 1 uses NEF network exposure). The mobile communication network architecture includes, for example, the application function (AF), and the data network (DN) connecting to the operator's network. The terminal can access the wireless network through the access node at its current location. The terminal can send service data to and receive service data from the data network through access network equipment and user plane functions. Optionally, this mobile communication network architecture also includes event registration and event management functions.

[0096] A terminal can be a device capable of receiving scheduling and instruction information from access network equipment, providing voice and / or data connectivity to users, or a handheld device with wireless connectivity, or other processing devices connected to a wireless modem. Terminal devices can communicate with one or more core networks or the Internet via the RAN. For example, a terminal device can be a portable, pocket-sized, handheld, computer-embedded, or vehicle-mounted mobile device. Terminal devices can also be referred to as subscriber units (SS), subscriber stations (MS), mobile stations (MS), remote stations (AP), access points (AP), remote terminals, access terminals, user agents, customer premises equipment (CPE), terminals, user experience units (UEs), mobile terminals (MTs), etc. Terminal devices can also be wearable devices. Terminal devices can also be devices in next-generation communication systems. For example, terminal devices in 5G networks or terminal devices in future PLMN networks, terminal devices in New Radio (NR) communication systems, etc.Currently, terminal devices can include: mobile phones, tablets, laptops, PDAs, customer-premises equipment (CPE), point-of-sale (POS) machines, light user equipment (UE), reduced capability UE (REDCAP UE), mobile internet devices (MID), wearable devices (e.g., smartwatches, smart bracelets, pedometers), in-vehicle equipment (e.g., cars, bicycles, electric vehicles, airplanes, ships, trains, high-speed trains), virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, smart home devices (e.g., refrigerators, televisions, air conditioners, electricity meters), smart robots, workshop equipment, wireless terminals in self-driving vehicles, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, and smart city devices. Wireless terminals in a city, or wireless terminals in a smart home, or flying devices (e.g., intelligent robots, hot air balloons, drones, airplanes), etc. Terminals can also be other devices with terminal functions; for example, a terminal device can also be a device that performs terminal functions in D2D communication. Figure 1 illustrates this using the UE as the terminal.

[0097] Access network equipment is an entity on the network side used to transmit or receive signals. Examples include transmission reception points (TRPs) and gNBs. Network equipment can be access points (APs) in wireless local area networks (WLANs), evolved Node Bs (eNBs or eNodeBs) in LTE, relay stations or access points, or network equipment in vehicular devices, wearable devices, and 5G networks, or network equipment in future PLMNs, or gNodeBs / gNBs in NR systems. In some deployments, a gNB may include a central unit (CU) and a distributed unit (DU). The CU implements some of the gNB's functions, and the DU implements some of the gNB's functions. For example, the CU is responsible for handling non-real-time protocols and services. For example, it implements radio resource control (RRC), service data adaptation protocol (SDAP) functions, and packet data convergence protocol (PDCP) layer functions. The DU is responsible for handling physical layer protocols and real-time services. For example, it can implement the functions of the radio link control (RLC) layer, medium access control (MAC) layer, and physical (PHY) layer. The gNB can also include an active antenna unit (AAU). The AAU implements some physical layer processing functions, radio frequency processing, and related functions of the active antenna. Since the information from the RRC layer ultimately becomes information from the PHY layer, or is derived from information from the PHY layer, in this architecture, higher-layer signaling (e.g., RRC layer signaling) can also be considered as being sent by the DU, or by the DU and AAU. It is understood that the network device can be one or more of the following: CU node, DU node, and AAU node. Furthermore, the CU can be a network device in the RAN, or a network device in the core network (CN); this application does not limit this. Additionally, in the embodiments of this application, the network device provides services to a cell, and the terminal device communicates with the network device through the transmission resources (e.g., frequency domain resources, or spectrum resources) used by the cell. This cell can be the cell corresponding to the network device (e.g., a base station). A cell can belong to a macro base station or to a base station corresponding to a small cell.For example, small cells may include: metro cells, micro cells, pico cells, femto cells, etc. Because small cells have small coverage areas and low transmission power, they can provide high-speed data transmission services. Furthermore, in other possible cases, the network device can be other devices that provide wireless communication functions for terminal devices. The embodiments of this application do not limit the specific technology or device form used in the network device. For example, in an open radio access network (ORAN) system, a CU can also be called an O-CU (open CU), a DU can also be called an O-DU, a CU-CP can also be called an O-CU-CP, a CU-UP can also be called an O-CU-UP, and a radio unit (RU) can also be called an O-RU. For ease of description, this application uses CU, CU-CP, CU-UP, DU, and RU as examples. Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software and hardware modules. Figure 1 uses (R)AN as an example of an access network device to illustrate this.

[0098] Access and Mobility Management (AMF) functions are primarily used for terminal attachment, mobility management, and tracking area update procedures in mobile networks. In 5G communication systems, AMF can be used. In future communication systems, AMF may still be called AMF, or it may have other names; this application is not limiting. Figure 1 illustrates this using AMF as an example.

[0099] Session management functions are primarily used for session management in mobile networks, such as session creation, modification, and release. Specific functions include assigning Internet Protocol (IP) addresses to terminals and selecting user plane functions that provide packet forwarding capabilities. In 5G communication systems, the session management function can be an SMF (Multicast / Broadcast-Session Management Function). In future communication systems, the session management function may still be called an SMF, or it may have other names; this application is not limited to these. This application also involves a multicast / broadcast session management network element, which can be a multicast / broadcast-session management function (MB-SMF), primarily used for session management in mobile networks, such as session creation, modification, and release. Figure 1 illustrates this using an SMF as an example.

[0100] User plane functions (UPFs) are primarily used for processing user packets, such as forwarding and billing. In 5G communication systems, UPFs can be used. In future communication systems, UPFs may still be used, or they may have other names; this application is not limited to these. Figure 1 illustrates this using UPFs as an example.

[0101] Policy control functions include policy control functions, billing policy control functions, and quality of service (QoS) control. In 5G communication systems, the policy control function can be PCF (Policy Control Function). In future communication systems, the policy control function can still be PCF, or it can have other names; this application is not limited to these. Figure 1 illustrates this using PCF as an example.

[0102] The network repository function is primarily used to provide registration and discovery of network functions or the services provided by network functions. In 5G communication systems, the network repository function can be an NRF (Network Function Repository). In future communication systems, the network repository function may still be an NRF, or it may have other names; this application is not limited to any particular name. Figure 1 illustrates this using an NRF as an example.

[0103] The unified data management function is mainly used to manage the subscription information of terminals. In 5G communication systems, the unified data management function can be UDM. In future communication systems, the unified data management function can still be a UDM function, or it can have other names. This application is not limited to this.

[0104] The authentication service function is mainly used for secure authentication of terminals. In 5G communication systems, the authentication service function can be AUSF. In future communication systems, the authentication service function can still be called AUSF, or it can have other names; this application is not limited to any particular name.

[0105] Network capability exposure (NEF) allows for the controlled exposure of certain network functions to applications. In 5G communication systems, NEF may be used. In future communication systems, NEF may still be used, or it may have other names; this application does not limit this.

[0106] Application functions can provide various application service data to the control plane functions of the operator's communication network, or obtain network data and control information from the control plane functions of the communication network. In 5G communication systems, application functions may be AF (Application Function). In future communication systems, application functions may still be AF, or they may have other names; this application is not limited to these.

[0107] Data networks are primarily used to provide data transmission services to terminals. Data networks can be private networks, such as local area networks (LANs), public data networks (PDNs), such as the Internet, or dedicated networks deployed by carriers, such as configured IP multimedia core network subsystems (IMS) services.

[0108] The event registration function is mainly used to provide event registration services for other network functions or third parties, such as the event registration function (ERF) in Figure 1.

[0109] The event management function is primarily used to provide event subscription and notification services for other network functions, such as the event management function (EMF) in Figure 1. The event management function can include event control and event execution functions. The event control function receives event subscriptions from the event subscription network function and configures the corresponding forwarding rules for the event to the event execution function. The event monitoring network function can send event trigger notifications to the event execution function, which then forwards the event to the corresponding event subscription network function based on the forwarding configuration information. In practical applications, the event control function can correspond to multiple event execution functions. Taking Figure 2 as an example, event management function 1 includes event control function 1 and two event execution functions. Event control function 1 is communicatively connected to event execution function 1 and event execution function 2, respectively. This communication connection can be a wireless or wired communication connection, which is not specifically limited here.

[0110] Event registration and event management functions can be implemented as independent network functions or integrated into existing network functions as units within those functions. For example, the EMF can be co-located with the NEF or a service communication proxy (SCP), or integrated as a logical function of the NEF or SCP. Similarly, the ERF can be co-located with the NRF, or integrated as a logical function of the NRF.

[0111] Furthermore, the event registration function can be combined with event registration, but this application does not specifically limit this.

[0112] In Figure 1, Nausf, Npcf, Nudm, Naf, Namf, Nsmf, Nnef, Nnrf, Nerf, and Nemf are the service-based interfaces (SBIs) provided by AUSF, PCF, UDM, AF, AMF, SMF, NEF, NRF, ERF, and EMF, respectively, used to invoke the corresponding service-based operations. N1, N2, N3, N4, N6, and N9 are interface sequence numbers, and their meanings are as follows:

[0113] 1) N1: The interface between the AMF and the terminal, which can be used to transmit non-access stratum (NAS) signaling (such as QoS rules from the AMF) to the terminal.

[0114] 2) N2: The interface between the AMF and the access network equipment, which can be used to transmit radio bearer control information from the core network side to the access network equipment.

[0115] 3) N3: The interface between the access network device and the UPF, mainly used to transmit uplink and downlink user plane data between the access network device and the UPF.

[0116] 4) N4: The interface between SMF and UPF, which can be used to transmit information between the control plane and the user plane, including the distribution of forwarding rules, QoS rules, traffic statistics rules, etc. from the control plane to the user plane, as well as the reporting of information from the user plane.

[0117] 5) N6: The interface between UPF and DN, used to transmit uplink and downlink user data streams between UPF and DN.

[0118] 6) N9: User plane interface between UPF network elements, used to transmit uplink and downlink user data streams between UPF network elements.

[0119] In the architecture shown in Figure 1, the various network functional elements are connected via a service-oriented bus and interact through service-oriented interfaces. The advantages of a service-oriented bus include improved network flexibility, openness, scalability, and intelligence, enabling support for diverse service scenarios and requirements. The service-oriented bus can be used to transmit various types of data and signaling. For example, it can be used to transmit latency-sensitive real-time signaling (e.g., service-oriented interface call signaling between network functional elements), latency-sensitive real-time data (e.g., real-time AI inference data), and non-real-time data (e.g., offline AI training data). Furthermore, when transmitting this data or signaling, the service-oriented bus couples the data or signaling together; that is, the service-oriented bus can simultaneously transmit real-time signaling, real-time data, and non-real-time data.

[0120] It is understood that the aforementioned network element or function can be a network component in a hardware device, a software function running on dedicated hardware, or a virtualized function instantiated on a platform (e.g., a cloud platform). Optionally, the aforementioned network element or function can be implemented by one device, multiple devices working together, or a functional module within a single device; this application embodiment does not specifically limit this.

[0121] The session management network element and user plane network element in this application can be the SMF and UPF shown in Figure 1, or they can be network elements with the functions of the aforementioned SMF and UPF in future communication networks. This application does not limit them in this regard.

[0122] The functions in the embodiments of this application may also be referred to as network elements, network functions, functional entities, devices, etc. For example, access and mobility management functions may also be referred to as access and mobility management network elements, or access and mobility management network functions, or access and mobility management functional entities, etc. The names of each function are not limited in this application. Those skilled in the art can replace the names of the above functions with other names to perform the same function, and all such replacements are within the scope of protection of this application.

[0123] As shown in Figure 3(a), in an existing 5G network, Network Function 2 (i.e., the event subscriber) can subscribe to events monitored by Network Function 1 (i.e., the event monitor), carrying an event identifier (Event ID) with the subscription request. The ID represents the identifier. The event feedback also includes address information (such as the address information of Network Function 1) and a correlation ID. Based on the request from Network Function 2, Network Function 1 can record the event identifier and Network Function 2 information in its locally maintained user or service context. When the event corresponding to the event identifier is triggered (occurs), Network Function 1 sends a notification message to Network Function 2 based on the Network Function 2 information corresponding to the event identifier in the context, carrying the event identifier and the corresponding event information with the notification message.

[0124] As shown in Figure 3(b), network function 2 (event subscriber) can also send event subscription requests to network function 1 (event monitor) through other network functions, such as AF1 subscribing to events through NEF. AF1 sends an event subscription request to NEF, and NEF selects the corresponding network function 2 (NF2) (such as NF 2 for event monitoring) based on the events subscribed to by AF1 and sends the event subscription request to that NF2. Here, AF1 is the event subscriber relative to NEF, and NEF is the event subscriber relative to NF2. When the subscribed event is triggered, NF2 sends a notification to NEF, and NEF then sends the corresponding event trigger notification to AF1 based on AF1's subscription. In addition, before NEF sends a subscription request to NF2, it may need to obtain event subscription authorization from UDM, query the NF 2 information that the current terminal is providing services for, or subscribe to events from other NFs through UDM. Therefore, the process of an event subscription may involve interactions between multiple NFs.

[0125] Event monitors need to define separate event subscription interfaces for use by event subscribers. Therefore, for service development, different network functions may require developing corresponding subscription interfaces; for example, in 5G network functions such as AMF, SMF, and UDM all have corresponding EventExposure_Subscribe services. Event subscribers send subscription request messages to event monitors, while event monitors maintain the binding relationships between all subscribers corresponding to an event. When an event is triggered, based on the binding relationships between the event and its subscribers, the event monitor sends event notifications to each subscriber. The coupling between event subscribers and event monitors is very strong. When event subscribers or event monitors change, or when mobile network services are upgraded, it is also necessary to consider how to maintain the aforementioned information (e.g., interface information, binding relationships, etc.).

[0126] Based on this, this application provides a communication method to decouple event subscribers from event monitors, thereby improving the processing efficiency of subscribed events. This method can be implemented through the interaction of a first network function, a second network function, and a fourth network function. The first network function is used for event subscription management and event notification management, such as the event management function described above. The first network function can be the first network function itself, a component within the first network function (e.g., a processor, chip, or chip system), or a logical module or software implementing all or part of the first network function. The second network function is used to subscribe to a first event, where the first event is any one of the subscribed events. The second network function can be the second network function itself, a component within the second network function (e.g., a processor, chip, or chip system), or a logical module or software implementing all or part of the second network function. This application does not specifically limit this. The fourth network function is used to monitor the first event. The fourth network function can be the fourth network function itself, a component within the fourth network function (e.g., a processor, chip, or chip system), or a logical module or software implementing all or part of the fourth network function. This application does not specifically limit this. This application is not specifically limited here.

[0127] This method can be applied to 5G communication systems or future communication systems, and can also be applied to non-terrestrial communication systems; this application does not specifically limit its application. In this application, the number of the first network function, the second network function, and the fourth network function is not specifically limited; each is illustrated using one as an example. Referring to Figure 4, the execution is as follows:

[0128] Step 401: The second network function sends a subscription request for the first event to the first network function. The subscription request includes topic information corresponding to the first event and an identifier for the first event, wherein the topic information and / or the identifier for the first event correspond to network information of the first event. Accordingly, the first network function receives the subscription request.

[0129] In one possible implementation, the second network function can pre-store the correspondence between information of the first network function and network information to determine which first network function to send the subscription request to. For example, first network function 1 has a correspondence 1 with PLMN1, and first network function 2 has a correspondence 2 with PLMN2. If the first event for which the second network function requests subscription occurs in PLMN2, then the second network function can send the subscription request to first network function 2 based on PLMN2 and correspondence 2. The second network function can also determine which first network function to send the subscription request to based on indication information from other network functions (e.g., the network function responsible for unified data management in the core network) (this indication information indicates information of the first network function). For example, the second network function receives indication information from the UDM indicating that first network function 2 corresponds to PLMN2. If the first event for which the second network function requests subscription occurs in PLMN2, then the second network function can send the subscription request to first network function 2 based on PLMN2 and the indication information. The second network function can also receive configuration information for a first event from an event orchestration (or event service) network function. This configuration information includes information about the first network function, and the second network function can specify which first network function to send a subscription request to based on this configuration information. This is merely an illustrative example and not a specific limitation on how the second network function specifies which first network function to send a subscription request to.

[0130] Wherein, the topic information, and / or the identifier of the first event corresponding to the network information of the first event, includes one of the following: the topic information indicates network information; or, the identifier of the first event indicates network information; or, both the topic information and the identifier of the first event indicate network information. For example, the topic information indicating network information can be understood as the topic information including network information. Or, the topic information indicates network information, for example, the topic information is &*, where * corresponds to network information. For example, the identifier of the first event indicating network information can be understood as the identifier of the first event including network information. Or, the identifier of the first event indicates network information, for example, the identifier of the first event is Event1, where Event1 corresponds to network information 1. For example, both the topic information and the identifier of the first event indicating network information can be understood as the topic information including network information, and the identifier of the first event including network information. Or, the topic information indicates network information, and the identifier of the first event indicates network information. Or, the topic information includes network information, and the identifier of the first event indicates network information. Or, the topic information indicates network information, and the identifier of the first event includes network information. This is merely illustrative and not specifically limiting. When subscription to the first event can be provided in different networks, the first event can be invoked in a specific network based on topic information and / or the identifier of the first event, thus clarifying the network information for the second network function to invoke the first event. When both the topic information and the identifier of the first event indicate network information, the first network function can determine the specific network information based on local configuration information or the operator's configuration policy. For example, if the local configuration information of the first network function is such that if the network information indicated by the topic information and the identifier of the first event are different, the network information indicated by the topic information is used as the network information for invoking the first event, then the network information for invoking the first event is determined by referring to the topic information. This is merely an illustrative example and is not intended to be specific or limiting.

[0131] Network information includes one or more of the following: PLMN information (i.e., the main network, such as PLMN identifier, PLMN parameters, etc.), network slice information (such as slice type, slice instance, etc.), NPN information (such as NPN identifier, NPN parameters, etc.), and subnet information. The subnet is a core network subnet deployed in a distributed manner by the operator, which can interact with the main network and invoke its functions to manage terminals. Subnet information can be a subnet identifier or subnet parameters, etc., and is not specifically limited here. For example, network information may include PLMN information and subnet information, or network information may include PLMN information and network slice information, or network information may include PLMN information and NPN information, etc. This is only an illustrative example and does not specifically limit the content of the network information. Based on this, the first network function can clearly define the specific network information of the second network function's invocation of the first event.

[0132] The topic information in the subscription request mentioned above can be referred to as Topic ID, which is used to indicate the application scope of the first event. Topic information may include one or more of the following: user information for the first event (e.g., user identifier, user address, etc.), or service information for the first event (e.g., service identifier (such as session identifier for a connection service, task identifier for an intelligent service, perception session identifier for a perception service, etc.), service parameters (such as session parameters (a combination of slice and / or data network name (DNN)), service type (perception service, computing service, artificial intelligence (AI) service, etc.), and execution entity information corresponding to the first event (such as network element type, network function type, network function instance identifier, etc.)). Optionally, the topic information may only include network information, which may indicate the network information of the first event, or the network information may correspond to an event at the network granularity, indicating a specific load condition or a network event of an accessing user. For example, the topic information Topic1 includes PLMN1, where PLMN1 corresponds to an event with 80% network load, or an event with X accessing users.

[0133] Optionally, the topic information includes network information and user information for the first event. This user information can indicate that the first event belongs to a user under the network corresponding to the network information. For example, if Topic 2 includes subnet 1 and UE1 and UE2, and the first event is a user location information change report, then Topic 2 indicates that UE1 and UE2 report location information changes under subnet 1.

[0134] Optionally, the topic information includes network information and service information of the first event. For example, if topic information Topic3 ​​includes subnet 1 and service 1, and service 1 corresponds to the reporting of user location information changes, then topic information Topic3 ​​including subnet 1 and service 1 indicates that user location change information is reported under subnet 1.

[0135] Optionally, the topic information may also include network information, user information of the first event, and service information of the first event. For example, if Topic 4 includes subnet 1, UE3, and service 1, and service 1 corresponds to the reporting of user location information changes, then Topic 4 including subnet 1, UE3, and service 1 indicates that the location change information of UE3 is reported under subnet 1.

[0136] Alternatively, when the identifier of the first event indicates network information, the subject information may include user information of the first event, or the subject information may include business information of the first event, etc. The specific content included in the subject information is not specifically limited here.

[0137] The identifier of the first event in the aforementioned subscription request can be called an Event ID. This Event ID can be understood with reference to existing standards 3GPP TS23.501 and TS 23.502. For example, an Event ID in the AMF corresponds to a user location report, while an Event ID in the SMF corresponds to a Protocol Data Unit (PDU) session state, QoS report, etc. Furthermore, Event IDs can also be events related to new services involved in future mobile networks, such as compute node load information and task service status.

[0138] The following description, with reference to Table 1, illustrates the correspondence between the subject information, the first event, and the monitoring network function of the first event. In specific applications, other events may also be involved, which will not be elaborated upon here.

[0139] Table 1

[0140] Optionally, the subscription request may also include: first authentication information. The first authentication information can be understood as a first event invocation key or invocation token, etc. The second network function carries the first authentication information in the subscription request so that the first network function can authenticate the second network function, thereby reducing the possibility of information leakage caused by network functions that do not have the ability to subscribe to the first event.

[0141] In one possible approach, if the first authentication information matches the second authentication information pre-stored in the first network function, then it is determined that the second network function has the permission to subscribe to the first event, and the second authentication information is used to indicate the identity information of the user of the first event. For example, the matching of the first authentication information and the second authentication information can be that the first authentication information and the second authentication information are the same, or that the first authentication information is processed to be the same as the second authentication information; this application is not limited to this.

[0142] Specifically, when the first network function is also used for authenticating the identity of event users (event subscribers or event monitors), the first network function can compare the pre-stored second authentication information with the first authentication information to determine whether the second network function has the permission to subscribe to the first event. Here, the first network function can be understood as a network function that combines event management and event registration functions. The second authentication information can be stored in the context of the first event. For example, if the first authentication information is TOKEN1 and the second authentication information is TOKEN2, and the first network function determines that TOKEN1 and TOKEN2 are different, then the second network function does not have the permission to subscribe to the first event. If the first network function determines that TOKEN1 and TOKEN2 are the same, then the second network function has the permission to subscribe to the first event. For example, if the first authentication information is encoded information W and the second authentication information is TOKEN2, and the first network function decodes W to obtain TOKEN1, and the first network function determines that TOKEN1 and TOKEN2 are different, then the second network function does not have the permission to subscribe to the first event. If the first network function determines that TOKEN1 and TOKEN2 are the same, then the second network function is determined to have the permission to subscribe to the first event. This is only an example and is not specifically limited.

[0143] In another alternative approach, the first network function sends a first authentication request message to the third network function. The first authentication request message includes first authentication information and is used to request the third network function to authenticate whether the second network function has the permission to subscribe to the first event. The third network function can determine the first authentication result based on the first authentication information and the second authentication information, and send the first authentication result to the first network function. Accordingly, the first network function receives the first authentication result. The first network function determines whether the second network function has the permission to subscribe to the first event based on the first authentication result.

[0144] For example, the third network function is used to authenticate the identity of the event user, such as the event registration function described above. The first network function authenticates the identity of the second network function by sending a first authentication request message to the third network function. This can improve the real-time performance of data processing and save processing resources of the first network function in a stateless manner (without storing the context related to the first event). For example, if the first authentication information is TOKEN1 and the second authentication information is TOKEN2, if the third network function determines that TOKEN1 and TOKEN2 are different by comparing them, then the first authentication result is that the second network function does not have the permission to subscribe to the first event. If the third network function determines that TOKEN1 and TOKEN2 are the same by comparing them, then the first authentication result is that the second network function has the permission to subscribe to the first event. For example, if the third network function only stores one second authentication information, the third network function can determine whether the second network function has the permission to subscribe to the first event by comparing whether the second authentication information is the same as the first authentication information. For example, if there is a correspondence between the first authentication information and the first event, after receiving the first authentication information, the third network function can parse the first authentication information to know that the first authentication information is associated with the first event. Then, it compares the first authentication information with the authentication information corresponding to the first event (i.e., the second authentication information) stored in its system to determine whether the second network function has the permission to subscribe to the first event. This is only an example and is not specifically limited.

[0145] If the third network function stores authentication information indicating the identity information of multiple users for multiple different events, and / or, the first authentication information cannot be parsed to obtain the associated event information, the first authentication request message may further include: subject information, and / or, an identifier of the first event. Based on this, when the first authentication request message includes subject information and / or the identifier of the first event, the third network function can clearly identify the specific event associated with the first authentication information and the network information corresponding to that specific event. Based on the identifier of the first event, the third network function can select the second authentication information corresponding to the user of the first event from the stored authentication information of the identity information of users for multiple different events, and compare the second authentication information corresponding to the user of the first event with the first authentication information, thereby improving the authentication efficiency of the second network function. Furthermore, different networks may include the same first event. When the subject information corresponds to the network information of the first event, including the subject information in the first authentication request message facilitates the third network function in selecting the second authentication information corresponding to the user of the first event in the specified network from the stored authentication information based on the network information.

[0146] Optionally, the subscription request may also include processing rules for the first event, wherein the processing rules may indicate the execution conditions and operations for the first event. For example, if the first event is a user location information report, the processing rules for the first event may be that the user reports their location when they are in area A, or that the user's location is reported periodically, etc. No specific limitations are imposed here. The processing rules for the first event can be understood as a more granular application scope of the subscription to the first event (or subscription rules). For example, if the topic information and the identifier of the first event indicate a user location information report, the processing rules for the first event may be that the user reports their location when they are in area A. This is merely an illustrative example and is not specifically limited.

[0147] Step 402: The first network function obtains the trigger notification of the first event.

[0148] In one possible approach, a first network function may receive an event trigger notification from a fifth network function. The trigger notification includes topic information corresponding to a first event and an identifier for the first event. The topic information and / or the identifier for the first event correspond to network information for the first event. The fifth network function monitors the first event. Upon detecting the triggering of the first event, the fifth network function sends an event trigger notification to the first network function. Based on this, the first network function can respond promptly to the event trigger notification. Furthermore, when the trigger notification includes the topic information and the identifier for the first event, the first network function can clearly identify which specific event in which network the trigger notification corresponds to, in order to perform the corresponding processing. In another possible approach, other network functions (e.g., NEF, etc.) may forward the trigger notification to the first network function after receiving it. The specific method of obtaining the trigger notification is not limited here.

[0149] Optionally, the trigger notification may also include third authentication information. This third authentication information can be understood as the first event invocation key or invocation token, etc. The fifth network function carries this third authentication information in the trigger notification so that the first network function can authenticate the fifth network function, reducing the possibility of information leakage caused by network functions that do not have the capability to monitor the first event.

[0150] In one possible approach, if the third authentication information matches the second authentication information pre-stored in the first network function, then it is determined that the fifth network function has the authority to monitor the first event, and the second authentication information is used to indicate the identity information of the user of the first event.

[0151] When the first network function is also used for authenticating the identity of event users (event subscribers or event monitors), it can compare the pre-stored second authentication information with the third authentication information to determine whether the fifth network function has the authority to monitor the first event. Here, the first network function can be understood as a network function combining event management and event registration functions. The third authentication information can be stored in the context of the first event. For example, if the third authentication information is TOKEN3 and the second authentication information is TOKEN2, and the first network function determines that TOKEN3 and TOKEN2 are different, then the fifth network function does not have the authority to monitor the first event. If the first network function determines that TOKEN3 and TOKEN2 are the same, then the fifth network function has the authority to monitor the first event. This is only an illustrative example and is not specifically limited.

[0152] In another alternative approach, the first network function sends a second authentication request message to the third network function. The second authentication request message includes third authentication information and is used to request the third network function to authenticate whether the fifth network function has the authority to monitor the first event. The third network function can determine a second authentication result based on the third and second authentication information and send the second authentication result to the first network function. Accordingly, the first network function receives the second authentication result. The first network function determines whether the fifth network function has the authority to monitor the first event based on the second authentication result.

[0153] The third network function is used to authenticate the identity of the event user, such as the event registration function described above. The first network function authenticates the identity of the fifth network function by sending a second authentication request message to the third network function. This improves the real-time performance of data processing and saves processing resources of the first network function in a stateless manner (without storing the context related to the first event). For example, if the third authentication information is TOKEN3 and the second authentication information is TOKEN2, if the third network function determines that TOKEN3 and TOKEN2 are different, it determines that the fifth network function does not have the permission to monitor the first event. If the third network function determines that TOKEN3 and TOKEN2 are the same, it determines that the fifth network function has the permission to monitor the first event. For example, if the third network function only stores one second authentication information, it can determine whether the fifth network function has the permission to monitor the first event by comparing whether the second authentication information matches the third authentication information. For example, if there is a correspondence between the third authentication information and the first event, after receiving the third authentication information, the third network function can parse the third authentication information to know that the third authentication information is associated with the first event. Then, it compares the third authentication information with the authentication information corresponding to the first event (i.e., the second authentication information) stored in its system to determine whether the fifth network function has the authority to monitor the first event. This is only an example and is not specifically limited.

[0154] If the third network function stores authentication information indicating the identity information of multiple users for multiple different events, and / or, the third authentication information cannot be parsed to obtain the associated event information, the second authentication request message may further include: subject information, and / or, an identifier of the first event. Based on this, when the second authentication request message includes subject information and / or the identifier of the first event, the third network function can clearly identify the specific event associated with the first authentication information and the network information corresponding to that specific event. Based on the identifier of the first event, the third network function can select the second authentication information corresponding to the user of the first event from the stored authentication information of the identity information of users for multiple different events, and compare the second authentication information corresponding to the user of the first event with the third authentication information, thereby improving the authentication efficiency of the fifth network function. Furthermore, different networks may include the same first event. When the subject information corresponds to the network information of the first event, including the subject information in the second authentication request message facilitates the third network function in selecting the second authentication information corresponding to the user of the first event in the specified network from the stored authentication information based on the network information.

[0155] Optionally, the notification trigger also includes the processing rules for the first event. This can be understood by referring to the description in step 401 above, and will not be repeated here.

[0156] This application does not limit the execution order of the above steps 401 and 402. They can be executed simultaneously. Step 401 can be executed first and then step 402, or step 402 can be executed first and then step 401.

[0157] Step 403: The first network function sends a trigger notification to the second network function, and the trigger notification corresponds to the network information.

[0158] The network information corresponding to the trigger notification can be understood as the trigger notification under the corresponding network in the second network function subscription request. For example, if the second network function requests to subscribe to the first event in PLMN1, it will only send the notification to the second network function if the trigger notification obtained by the first network function is from PLMN1; otherwise, it will not send the notification to the second network function if the trigger notification obtained by the first network function is from PLMN2. Based on this, it can be guaranteed that the event subscription function subscribes to events triggered under the same network.

[0159] In this application, the event subscription function can subscribe to a first event in a specified network by sending a subscription request for a first event carrying network information to the first network function. In addition, the first network function manages event subscription and event notification, which can improve the efficiency of event subscription processing and decouple the event subscription function from the event monitoring function.

[0160] In an optional embodiment, the first network function is further used for authenticating the identity of event users (event subscribers or event monitors). Before performing steps 401 and / or 402, the first network function may receive an event registration request message from the fourth network function. The event registration request message includes: the topic information of the first event and the identifier of the first event. The first network function sends an event registration response message to the fourth network function. The event registration response message includes: registration result (registration successful or registration failed (optionally carrying a reason for failure, such as the current network does not support the registration of the event, the current event does not meet the user's subscription requirements, the identity verification of the registrant (i.e., the fourth network function) fails, etc.)) and second authentication information. Based on this, the first network function can clarify the context information of the first event and assign the second authentication information to indicate the identity information of the user of the first event. Optionally, the event registration request message also includes the processing rules of the first event so that the first network function can clarify the specific processing requirements of the first event. Subsequently, after the first network function receives a subscription request for the first event or a trigger notification of the first event, the first network function can authenticate the identities of the first network function and the fifth network function based on the registration result and the second authentication information.

[0161] The fourth network function can be one or more of the following: a capability open network function (e.g., NEF), a service control function, a service orchestration function, an access network service management function (e.g., access network AI function), a core network service management function (e.g., core network session management function), a mobile network operation and maintenance management system (e.g., operation administration and maintenance (OAM)), or a fifth network function. The fifth network function is used to monitor the first event and is a network function specific to the first event. Regarding specific application functions, the fifth network function can also be replaced by an event monitoring network function. For example, the service control function is used for the overall coordination of service execution, managing the invocation of network functions (services) involved in the service execution process. During service execution, event subscription and processing between services may be involved. For example, the registration service may involve service calls between AMF, PCF, AUSF, and UDM. The service control configures the process for the AMF and PCF services involved in the registration process. That is, when the AMF receives the UE's registration request, it sends a subscription or policy request to the UDM or PCF, and this request action is configured by the service control for the AMF. In the provision of such services, the network function itself does not have the ability to call other network function services; instead, this needs to be configured by the service control function. In this case, the service control function possesses end-to-end process control capabilities for the service. Therefore, during the execution of certain services, some network functions need to subscribe to certain events of other network functions, such as the UDM subscribing to the AMF for UE location information, as mentioned above. For example, the service orchestration function is used for orchestrating service calls to network functions related to the service. Similar to the service control function, during orchestration, the service orchestration function can logically complete the service call logic configuration between network functions, thereby pre-registering the event subscriptions involved. Unlike the service control function, the service orchestration function can be understood as a design-state pre-event registration; that is, after service orchestration is completed, instantiation may not have occurred yet, while service control is generally a runtime event registration, meaning that the instantiation of the network function has already been completed.

[0162] When the fourth network function is a capability open network function, service control function, service orchestration function, access network service management function, core network service management function, or mobile network operation and maintenance management system, the fourth network function may send first configuration information to the subscribing network function of the first event. The first configuration information includes: topic information, the identifier of the first event, and second authentication information; and / or,

[0163] The monitoring network function of the first event sends second configuration information, which includes: topic information, the identifier of the first event, and second authentication information. Based on this, subscribers to the first event can specify which events they can subscribe to, and monitors of the first event can specify which events they can monitor. For example, if an AI task requires multiple network functions to complete, network function 1 may need to obtain the task execution status of network functions 2 and 3. In this application, network functions 2 and 3 receive the second configuration information and monitor the event based on the event identifier in the second configuration information. Network function 1 receives the first configuration information. When network function 1 obtains the first configuration information and needs to execute the relevant task, it sends an event subscription request to the first network function. Network functions 2 and 3 send event trigger notifications to the first network function after the monitored event occurs or periodically based on the configuration.

[0164] Optionally, the first configuration information further includes: a subscription instruction for the first event, and / or, processing rules for the first event; the second configuration information further includes: a monitoring instruction for the first event, and / or, processing rules for the first event. When the first configuration information includes a subscription instruction for the first event, the subscription network function for the first event can explicitly perform processing related to the subscription of the first event. When the first configuration information includes processing rules for the first event, the subscription network function for the first event can specify the specific processing granularity of the first event. When the second configuration information includes a monitoring instruction for the first event, the monitoring network function for the first event can explicitly perform processing related to the monitoring of the first event. When the second configuration information includes processing rules for the first event, the monitoring network function for the first event can specify the specific processing granularity of the first event.

[0165] For example, the Network Capability Open Function (NEF) can receive event configuration request messages from third-party application services from the Application Server Attachment (AF). These event configuration request messages can carry the aforementioned first or second configuration information. For example, they carry an application server identifier (such as AF ID) to identify the server, an application identifier (such as APP ID) to identify the application corresponding to the event, and a user identifier (such as a generic public subscription identifier (GPSI), a subscription permanent identifier (SUPI), an internet protocol (IP) address, etc.) to identify the relevant user and the event configuration. The NEF can obtain the corresponding network function (i.e., the subscription network function for subscribing to the event or the monitoring network function for monitoring the event) information based on the event configuration request message. Alternatively, it can infer the network function corresponding to the event from the service information in the topic information (Topic ID) and / or the event identifier (Event ID), such as selecting SMF and / or UPF for connection services.

[0166] For example, service control and service orchestration functions need to select and execute network functions related to a specific business (i.e., subscription network functions that subscribe to the event or monitoring network functions that monitor the event). If an AI task involves multiple network functions such as SMF (connection management), compute control (computation scheduling), and data control (data storage and retrieval, data processing, etc.), then service control and orchestration functions need to send first configuration information or second configuration information to these network functions based on the network function information involved in a specific business.

[0167] For example, the service management functions of the access network and the core network, such as the SMF needing to subscribe to the status of the UE on the RAN device side or the interface air state of the RAN device, can send first configuration information or second configuration information to the RAN device to which the UE is connected or to the RAN device in certain areas. Similarly, if the RAN device side needs to obtain certain information from the core network side, it can also send first configuration information or second configuration information to the corresponding core network function.

[0168] For example, the mobile network operation and maintenance management system is equivalent to the operator's operation and maintenance management function. It can send corresponding event configuration information to the network function based on local operation and maintenance needs or the needs of network tenants, such as the reporting of the number of users in the sub-network, network load status, and other scenarios.

[0169] When the fourth network function is the fifth network function or an event monitoring network function, the first network function can determine which network functions subscribed to the event to provide trigger notifications based on association identification information. The association identification information can be used to indicate the subscription relationship of an event or the context of an event, i.e., the binding relationship between the event ID and the event subscriber. In a communication system, there may be a large number of event subscriptions. By introducing association identification, the subscriber of a specific event or the current state of the event can be quickly located, facilitating event status tracking and execution recording.

[0170] Optionally, the first configuration information and the second configuration information also include second authentication information. The subscribing network function for the first event can store the second authentication information obtained from the first configuration information, so that it can subsequently use this second authentication information to verify the identity of the subscribing network function for the first event through the first network function. The monitoring network function for the first event can also store the second authentication information obtained from the second configuration information, so that it can subsequently use this second authentication information to verify the identity of the monitoring network function for the first event through the first network function. Furthermore, this also prevents network functions from impersonating others to subscribe to or monitor events. For example, network function 1 obtains the second authentication information TOKEN1 related to event 1 from the first configuration information, subscribes to event 1, and uses TOKEN1 to authenticate with the first network function. If the first network function finds a match, the authentication is successful. If network function 2 does not obtain the first configuration information, it randomly generates authentication information TOKEN2, uses TOKEN2 to authenticate with the first network function, and if the first network function finds a mismatch, it rejects the event 1 call. When the identity of the subscribing network function for the first event is trustworthy, the first authentication information in the subscription request becomes the second authentication information. When the identity of the monitoring network function for the first event is trusted, the third authentication information in the aforementioned trigger notification becomes the second authentication information.

[0171] Furthermore, it should be noted that if the first configuration information and the second configuration information do not include the second authentication information, the aforementioned first authentication request message may include the identity identifier of the subscribed network function of the first event, so as to verify the identity of the subscribed network function of the first event through the first network function and ensure that the identity of the subscribed network function of the first event is trustworthy. Similarly, the aforementioned second authentication request message may include the identity identifier of the monitoring network function of the first event, so as to verify the identity of the monitoring network function of the first event through the first network function and ensure that the identity of the monitoring network function of the first event is trustworthy.

[0172] Referring to Figure 5, taking EMF as the first network function, network function 1 as the second network function, network function 2 as the fifth network function, and service orchestration as the fourth network function as an example, the execution is as follows:

[0173] Step 501: The service orchestration function sends an event registration request message to the EMF. The event registration request message includes the subject information of one or more events and the identifier of the events.

[0174] Optionally, the event registration request message may also include the event processing rules. The topic information, event identifier, and event processing rules can be understood with reference to the above description, which will not be repeated here.

[0175] Step 502: EMF sends an event registration response message to the service orchestration function. The event registration response message includes the registration result (success or failure) and the second authentication information corresponding to the event.

[0176] The second authentication information can be understood by referring to the description of step 401 above.

[0177] Step 503A: The service orchestration function sends first configuration information to network function 1. The first configuration information includes the topic information of the event and the identifier of the event.

[0178] Optionally, the first configuration information also includes event processing rules and subscription instructions, which can be understood with reference to the above description and will not be repeated here.

[0179] Optionally, the first configuration information may also include second authentication information.

[0180] Step 503B: The service orchestration function sends second configuration information to network function 2. The second configuration information includes the topic information of the event and the identifier of the event.

[0181] Optionally, the second configuration information also includes event processing rules and monitoring instructions, which can be understood with reference to the above description and will not be repeated here.

[0182] Optionally, the second configuration information may also include second authentication information.

[0183] This application does not specify the execution order of steps 503A and 503B.

[0184] Step 504: Network function 1 sends a subscription request for event 1 to EMF. The subscription request for event 1 includes the topic information corresponding to event 1, the identifier of event 1, and the first authentication information (if network function 1 obtains the second authentication information from step 503A, the subscription request carries the second authentication information, and at this time, the second authentication information matches the first authentication information).

[0185] This includes the topic information corresponding to Event 1, and / or the network information corresponding to the identifier of Event 1. Optional subscription request messages may also include the processing rules for Event 1. The subscription request is not limited here; the description in step 401 above can be used as a reference.

[0186] Step 505: After network function 1 detects that event 1 has occurred, it sends a trigger notification for event 1 to EMF. The trigger notification for event 1 includes the topic information corresponding to event 1, the identifier of event 1, and the third authentication information (if network function 2 obtains the second authentication information from step 503B, the trigger notification carries the second authentication information, and at this time, the second authentication information matches the third authentication information).

[0187] This includes the topic information corresponding to Event 1, and / or the network information corresponding to the identifier of Event 1. Optional trigger notifications may also include the processing rules for Event 1. The trigger notification is not limited here; the description in step 401 above can be used for clarification.

[0188] Step 506A: EMF determines the first authentication result by comparing whether the first authentication information matches the second authentication information.

[0189] Step 506B: EMF determines the second authentication result by comparing whether the third authentication information matches the second authentication information.

[0190] The execution order of steps 506A and 506B is not specified here. The specific processing flow of steps 506A and 506B can be understood by referring to step 401 above, and will not be repeated here.

[0191] If the first authentication result is successful for network function 1 and the second authentication result is successful for network function 2, proceed to step 507.

[0192] Step 507: EMF sends a trigger notification to network function 1.

[0193] Service orchestration is the process of selecting network functions and orchestrating service calls between them for end-to-end service execution. Therefore, service orchestration can select the service call behaviors between network functions involved in the service execution process at the initial stage of service execution (including the event monitoring and notification behaviors of different network service functions during service execution). Based on this, before service execution, service orchestration can send event registration request messages to the EMF based on the event handling needs between network functions involved in the service execution (such as network function 1 and network function 2), and send the event monitoring and subscription configurations to network function 1 and network function 2 respectively, thereby meeting the monitoring and handling needs of relevant events during service execution. Unifying event monitoring, notification, and subscription configuration through service orchestration simplifies the design and implementation of the network functions themselves. Furthermore, developers do not need to develop event handling for each network function involved in each service separately. Additionally, when the mobile network needs to execute a new service, only the network functions involved in the new service need to be orchestrated and configured through service orchestration, without the need for repeated development and adjustment of all network functions. Based on this, the service can be quickly deployed and implemented within the network.

[0194] Referring to Figure 6, taking EMF as the first network function, network function 1 as the second network function, and network function 2 (i.e., the event monitoring network function) as the fourth network function as the fourth network function, let's illustrate this. Assume that network function 2 can monitor event A and executes the following:

[0195] Step 601, create event A.

[0196] For example, event A is the creation of a PDU session.

[0197] Step 602: Network function 2 sends an event registration request message to EMF. The event registration request message includes the subject information of event A and the identifier of event A.

[0198] Optionally, the event registration request message may also include the processing rules for event A. The topic information, event identifier, and event processing rules can be understood with reference to the above description, which will not be repeated here.

[0199] For example, network function 2 is a session management function, and event A is monitoring PDU sessions. The event registration request message may include user information (such as UE identifier and / or UE address) and the identifier of event A (e.g., PDU session identifier). Optionally, the processing rule for event A is to report when the PDU session state changes, or when certain QoS flow parameters cannot meet the requirements, etc. This is only an example and is not specifically limited.

[0200] Step 603: EMF creates context information for event A.

[0201] The context information for event A may include the topic information of event A, the identifier of event A, and the processing rules for event A.

[0202] Step 604: Network function 1 sends a subscription request for event A to EMF. The subscription request for event A includes the topic information corresponding to event A and the identifier of event A.

[0203] Among them, the topic information corresponding to event A, and / or the network information corresponding to the identifier of event A.

[0204] When authenticating the identity of an event subscription network function (i.e., network function 1), the event subscription network function carries authentication information in its subscription request. This authentication information can be assigned by the operator or requested by the event subscription network function from the NRF (for example, the NRF obtains the authentication information when requesting the discovery of the EMF). When receiving a subscription request, the EMF authenticates the identity of the event subscription network function by comparing the authentication information in the subscription request with the authentication information obtained by the EMF. The EMF can obtain the authentication information related to event A based on the operator's configuration or from the NRF.

[0205] Step 605: EMF updates the context information of event A based on the subscription request for event A.

[0206] Step 606: EMF sends a subscription request for event A to network function 2.

[0207] Specifically, the subscription request may include topic information, the identifier of event A, and associated identifiers.

[0208] Multiple event subscription network functions may exist for the same event. Therefore, the subscription action of a specific event subscription network function for a single event can be bound or identified by a unique association identifier and recorded in the event context, as described in step 605 above. Based on this, subsequent network functions that have subscribed to the event (such as network function 1) can carry the association identifier to perform subscription-related updates for event A, such as updates to reporting rules or feedback addresses. Network function 1 can carry the association identifier with its subscription update request, enabling EMF to quickly find the event context corresponding to the event subscription and perform the corresponding subscription update.

[0209] Step 607: When event A is triggered, network function 2 sends a trigger notification of event A to EMF.

[0210] The trigger notification for event A includes the topic information corresponding to event A and the identifier of event A. The topic information corresponding to event A and / or the identifier of event A correspond to the network information of event A. Optional trigger notifications may also include the processing rules for event A.

[0211] Step 608: EMF sends an event notification to network function 1 based on the subscriber information corresponding to the association identifier in the context information of event A.

[0212] Based on this, by introducing association identifiers, it is possible to quickly locate the subscribers of a certain event, or the current state of the event, which facilitates the tracking of the event's state and the recording of its execution.

[0213] In another optional embodiment, regarding data interaction between the first network function and the third network function, before performing steps 401 and / or 402, the third network function may receive an event registration request message from the fourth network function. The event registration request message includes: subject information of the first event and an identifier of the first event, wherein the subject information and / or the identifier of the first event correspond to the network information of the first event. The third network function sends an event registration response message to the fourth network function. The event registration response message includes: a registration result (registration successful or registration failed (optionally carrying a reason for failure, such as authentication failure, request not matching the subscription, event registration unsatisfactory (e.g., outside service range, unable to obtain UE or network status, etc.))) and second authentication information, which indicates the identity information of the user of the first event. Based on this, the third network function can clarify the context information of the first event and allocate the second authentication information to indicate the identity information of the user of the first event. Optionally, the event registration request message also includes processing rules for the first event, so that the third network function can clarify the specific processing requirements of the first event. Since multiple first network functions may be deployed in the network, the registration response message may optionally include information about the first network function, such as the EMF's identifier and address.

[0214] The fourth network function can be understood by referring to the above description and will not be repeated here.

[0215] When the fourth network function is a capability open network function, service control function, service orchestration function, access network service management function, core network service management function, or mobile network operation and maintenance management system, the fourth network function can send first configuration information to the subscription network function of the first event. The first configuration information includes: topic information, the identifier of the first event, and second authentication information; and / or, send second configuration information to the monitoring network function of the first event. The second configuration information includes: topic information, the identifier of the first event, and second authentication information. Based on this, the subscriber of the first event can clearly define the events that can be subscribed to, and the monitor of the first event can clearly define the events that can be monitored. Optionally, the first configuration information also includes: a subscription instruction for the first event, and / or, the processing rules for the first event; the second configuration information also includes: a monitoring instruction for the first event, and / or, the processing rules for the first event. When the first configuration information includes a subscription instruction for the first event, the subscription network function of the first event can clearly define the processing related to the subscription of the first event. When the first configuration information includes the processing rules for the first event, the subscription network function of the first event can clearly define the specific processing granularity of the first event. When the second configuration information includes a monitoring indication for the first event, the network function monitoring the first event can explicitly execute the processing related to the monitoring of the first event. When the second configuration information includes processing rules for the first event, the network function monitoring the first event can specify the specific processing granularity of the first event. Furthermore, the first and second configuration information may also include information about a first network function. This information can be configured locally by the operator's network or obtained from a third network function; no specific limitation is made here. If the information about the first network function configured locally by the operator is different from the information about the first network function obtained from the third network function, the most recently obtained first network function information will be used as the target first network function (i.e., the network function that sends the subscription request from the second network function and the network function that sends the trigger notification from the fifth network function).

[0216] Referring to Figure 7, taking EMF as the first network function, network function 1 as the second network function, network function 2 as the fifth network function, service orchestration function as the fourth network function, and ERF as the third network function as an example, the execution is as follows:

[0217] Step 701: The service orchestration function sends an event registration request message to the ERF. The event registration request message includes the subject information of one or more events and the identifier of the events.

[0218] Optionally, the event registration request message may also include the event processing rules. The topic information, event identifier, and event processing rules can be understood with reference to the above description, which will not be repeated here.

[0219] Step 702: ERF sends an event registration response message to the service orchestration function. The event registration response message includes the registration result (success or failure) and the second authentication information corresponding to the event.

[0220] The second authentication information can be understood by referring to the description of step 401 above. Optionally, the event registration response message includes the EMF's identifier.

[0221] Step 703A: The service orchestration function sends first configuration information to network function 1. The first configuration information includes the topic information of the event and the identifier of the event.

[0222] Optionally, the first configuration information also includes event processing rules and subscription instructions, which can be understood with reference to the above description and will not be repeated here.

[0223] Optionally, the first configuration information includes the identifier of the EMF.

[0224] Step 703B: The service orchestration function sends second configuration information to network function 2. The second configuration information includes the topic information of the event and the identifier of the event.

[0225] Optionally, the second configuration information also includes event processing rules and monitoring instructions, which can be understood with reference to the above description and will not be repeated here.

[0226] Optionally, the second configuration information includes the identifier of the EMF.

[0227] This application does not limit the execution order of steps 703A and 703B.

[0228] Step 704: Network function 1 sends a subscription request for event 1 to EMF. The subscription request for event 1 includes the topic information corresponding to event 1, the identifier of event 1, and the first authentication information.

[0229] The message includes the topic information corresponding to event 1, and / or the network information corresponding to the identifier of event 1. Optionally, the subscription request message also includes the processing rules for event 1. The subscription request can be understood with reference to the description in step 401 above; this is not limited to this.

[0230] Step 705: After network function 1 detects that event 1 has occurred, it sends a trigger notification for event 1 to EMF. The trigger notification for event 1 includes the topic information corresponding to event 1, the identifier of event 1, and third authentication information.

[0231] This includes the topic information corresponding to Event 1, and / or the network information corresponding to the identifier of Event 1. Optional trigger notifications may also include the processing rules for Event 1. The trigger notification is not limited here; the description in step 401 above can be used for clarification.

[0232] This application does not specifically limit the execution order of steps 704 and 705.

[0233] Step 706A: The EMF sends a first authentication request message to the ERF. The first authentication request message includes first authentication information and is used to request the ERF to authenticate whether network function 1 has the permission to subscribe to the first event.

[0234] Optionally, the first authentication request message may also include the subject information corresponding to event 1, the identifier of event 1, and the processing rules for event 1. This can be understood by referring to the description in step 401 above, and will not be repeated here.

[0235] Step 707A: ERF determines the first authentication result by comparing whether the first authentication information matches the second authentication information.

[0236] Step 706B: The EMF sends a second authentication request message to the ERF. The second authentication request message includes third authentication information. The third authentication request message is used to request the ERF to authenticate whether network function 2 has the authority to monitor the first event.

[0237] Optionally, the second authentication request message may also include the subject information corresponding to event 1, the identifier of event 1, and the processing rules for event 1. This can be understood by referring to the description in step 401 above, and will not be repeated here.

[0238] In step 707B, the ERF determines the second authentication result by comparing whether the third authentication information matches the second authentication information.

[0239] If the first authentication result is successful for network function 1 and the second authentication result is successful for network function 2, proceed to step 708.

[0240] Step 708: EMF sends a trigger notification to network function 1.

[0241] Based on this, the service orchestration function sends event registration request messages to the EMF, simplifying the implementation of network functions and facilitating layered deployment and management. The event registration function only provides event registration services, while the event management service can manage and execute event subscriptions and notifications. Therefore, the number of ERFs can be relatively small, or even only one is needed in the network, while the EMF can be dynamically scaled up or down based on network needs and flexibly deployed based on user locations.

[0242] Referring to Figure 8, taking EMF as the first network function, network function 1 as the second network function, network function 2 (i.e., the event monitoring network function) as the fourth network function, and ERF as the third network function as the third, let's assume that network function 2 can monitor event A and executes as follows:

[0243] Step 801, create event A.

[0244] For example, event A is a monitoring PDU session.

[0245] Step 802: Network function 2 sends an event registration request message to ERF. The event registration request message includes the subject information of event A and the identifier of event A.

[0246] Optionally, the event registration request message may also include the processing rules for event A. The topic information, event identifier, and event processing rules can be understood with reference to the above description, which will not be repeated here.

[0247] For example, network function 2 is a session management function, and event A is monitoring PDU sessions. The event registration request message may include user information (such as UE identifier and / or UE address) and the identifier of event A (e.g., PDU session identifier). Optionally, the processing rule for event A is to report it after a change in the PDU session state. This is only an example and is not specifically limited.

[0248] In addition, the event registration request message can also carry authentication information that allows users to subscribe to the event, such as network information (e.g., PLMN ID, subnetwork identifier, slice identifier, etc.) and network function information (e.g., network function identifier, address, etc.) for subsequent authentication of users of the event service.

[0249] Step 803, ERF creates context information for event A.

[0250] The context information for event A may include the topic information of event A, the identifier of event A, and the processing rules for event A.

[0251] Step 804: Network Function 1 sends a subscription request for Event A to the EMF. The subscription request for Event A includes the topic information corresponding to Event A and the identifier of Event A. In addition, the request message also needs to carry information about Network Function 1, such as the network function identifier and address.

[0252] Among them, the topic information corresponding to event A, and / or the network information corresponding to the identifier of event A.

[0253] Step 805: The EMF sends an authentication request to the ERF based on the subscription request of event A.

[0254] For example, if the EMF obtains information about network function 1 in step 804, the EMF can send an authentication request to the ERF, carrying the subject information and / or the identifier of event A, as well as the information about network function 1, along with the subscription request. The ERF can authenticate the requester's identity based on the operator's local configuration, or based on the network information or network function information carried during event registration in step 802 that allows the use of the event service.

[0255] Step 806: EMF sends a subscription request for event A to network function 1.

[0256] Specifically, the subscription request may include topic information, the identifier of event A, and associated identifiers.

[0257] Step 807: When event A is triggered, network function 1 sends a notification of event A to the EMF.

[0258] The trigger notification for event A includes the topic information corresponding to event A and the identifier of event A. The topic information corresponding to event A and / or the identifier of event A correspond to the network information of event A. Optional trigger notifications may also include the processing rules for event A.

[0259] In step 808, after EMF determines that Network Function 1 is a subscriber with subscription rights based on step 805, it sends an event notification to Network Function 1.

[0260] Based on this, the event monitoring network function sends event registration request messages to the EMF, simplifying the implementation of network functions and facilitating layered deployment and management. The event registration function only provides event registration services, while the event management service can manage and execute event subscriptions and notifications. Therefore, the number of ERFs can be relatively small, or even only one is needed in the network, while the EMF can be dynamically scaled up or down based on network needs and flexibly deployed based on user locations.

[0261] The foregoing primarily describes the solutions provided by the embodiments of this application from the perspective of device interaction. It is understood that, in order to achieve the above functions, each device may include corresponding hardware structures and / or software modules for executing each function. Those skilled in the art should readily recognize that, in conjunction with the units and algorithm steps of the various examples described in the embodiments disclosed herein, the embodiments of this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware 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.

[0262] The embodiments of this application can divide the device into functional units according to the above method examples. For example, each function can be divided into a separate functional unit, or two or more functions can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0263] In the case of using integrated units, FIG9 shows a possible exemplary block diagram of the communication device involved in the embodiments of this application. As shown in FIG9, the communication device 900 may include a processing unit 901 and a transceiver unit 902. The processing unit 901 is used to control and manage the operation of the communication device 900. The transceiver unit 902 is used to support communication between the communication device 900 and other devices. Optionally, the transceiver unit 902 may include a receiving unit and / or a transmitting unit, respectively used to perform receiving and transmitting operations. Optionally, the communication device 900 may also include a storage unit for storing the program code and / or data of the communication device 900. The transceiver unit may be called an input / output unit, a communication unit, etc., and the transceiver unit may be a transceiver; the processing unit may be a processor. When the communication device is a module (e.g., a chip) in a communication device, the transceiver unit may be an input / output interface, an input / output circuit, or an input / output pin, etc., and may also be called an interface, a communication interface, or an interface circuit, etc.; the processing unit may be a processor, a processing circuit, or a logic circuit, etc. For example, the device may be the first network function, the second network function, the third network function, the fourth network function, or the fifth network function described above.

[0264] More detailed descriptions of the processing unit 901 and the transceiver unit 902 can be obtained directly from the relevant descriptions in the above method embodiments, and will not be repeated here.

[0265] Figure 10 shows a communication device 1000 provided in this application. The communication device 1000 can be a chip or a chip system. The communication device can be located in the device involved in any of the above method embodiments, such as a first network function, a second network function, a third network function, a fourth network function, or a fifth network function, to perform the actions corresponding to the device.

[0266] Optionally, a chip system can consist of chips or include chips and other discrete components.

[0267] The communication device 1000 includes a processor 1010.

[0268] The processor 1010 is used to execute the computer program stored in the memory 1020 to implement the operation of each device in any of the above method embodiments.

[0269] Optionally, the communication device 1000 may also include a memory 1020 for storing computer programs.

[0270] Optionally, the memory 1020 and the processor 1010 are coupled. Coupling is an indirect coupling or communication connection between devices, units, or modules, which can be electrical, mechanical, or other forms, for information exchange between devices, units, or modules. Optionally, the memory 1020 and the processor 1010 are integrated together.

[0271] There can be one or more processors 1010 and memory 1020, and there is no limitation.

[0272] Optionally, in practical applications, the communication device 1000 may or may not include a transceiver 1030, as illustrated by the dashed box in the figure. The communication device 1000 can exchange information with other devices through the transceiver 1030. The transceiver 1030 can be a circuit, a bus, a transceiver, or any other device that can be used for information exchange.

[0273] In one possible implementation, the communication device 1000 may be a first network function, a second network function, a third network function, a fourth network function, or a fifth network function, etc., in the above-described methods.

[0274] This application embodiment does not limit the specific connection medium between the transceiver 1030, processor 1010, and memory 1020. In Figure 10, the memory 1020, processor 1010, and transceiver 1030 are connected via a bus, indicated by a thick line. The connection methods between other components are merely illustrative and not intended to be limiting. The bus can be an address bus, data bus, control bus, etc. For ease of illustration, only one thick line is used in Figure 10, but this does not imply only one bus or one type of bus. In this application embodiment, the processor can be a general-purpose processor, digital signal processor, application-specific integrated circuit, field-programmable gate array, or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component, capable of implementing or executing the methods, steps, and logic block diagrams disclosed in this application embodiment. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in this application embodiment can be directly manifested as execution by a hardware processor, or execution by a combination of hardware and software modules within the processor. For example, the processor may include one or more of the following: a central processing unit (CPU), an application-specific integrated circuit (ASIC), a digital signal processor (DSP), a microprocessor unit (MPU), a microcontroller unit (MCU), a graphics processing unit (GPU), a field-programmable gate array (FPGA), an artificial intelligence processor (AI processor), or a neural processing unit (NPU).

[0275] In the embodiments of this application, the memory can be non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD), or it can be volatile memory, such as random-access memory (RAM). The memory can also be any other medium capable of carrying or storing desired program code in the form of instructions or data structures, and accessible by a computer, but is not limited thereto. The memory in the embodiments of this application can also be a circuit or any other device capable of implementing storage functions for storing computer programs, program instructions, and / or data. Exemplarily, the memory can include, but is not limited to, cache, read-only memory (ROM), RAM, synchronous dynamic random access memory (SDRAM), hard disk drive (HDD) or solid-state drive (SSD), erasable programmable read-only memory (EPROM), or compact disc read-only memory (CD-ROM), etc. A memory is any medium capable of carrying or storing desired program code in the form of instructions or data structures, and accessible by a computer, but is not limited thereto. The memory in the embodiments of this application may also be a circuit or any other means capable of implementing storage functions for storing computer programs or instructions, and / or data.

[0276] Based on the above embodiments, referring to FIG11, this application embodiment also provides another communication device 1100, including: interface circuit 1110 and logic circuit 1120; interface circuit 1110 can be understood as input / output interface, which can be used to execute the transmission and reception steps of each device in any of the above method embodiments, and logic circuit 1120 can be used to run code or instructions to execute the methods executed by each device in any of the above embodiments, which will not be described again.

[0277] Based on the above embodiments, this application also provides a computer-readable storage medium storing instructions that, when executed, cause the methods executed by the devices in any of the above method embodiments to be implemented. The computer-readable storage medium may include various media capable of storing program code, such as a USB flash drive, portable hard drive, read-only memory, random access memory, magnetic disk, or optical disk.

[0278] Based on the above embodiments, this application also provides a computer program product containing a computer program or instructions, which, when run on a computer, causes the computer to execute the methods executed by the various devices in any of the above method embodiments.

[0279] Based on the above embodiments, this application provides a communication system that includes the first network function, second network function, third network function, fourth network function, or fifth network function mentioned in any of the above method embodiments, and can be used to execute the methods executed by each device in any of the above method embodiments.

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

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

[0282] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means that implement the functions specified in one or more flowcharts and / or one or more block diagrams.

[0283] These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process, such that the instructions, which execute on the computer or other programmable apparatus, provide steps for implementing the functions specified in one or more flowcharts and / or one or more block diagrams.

Claims

1. A communication method characterized by comprising: Applied to the first network function, including: Receive a subscription request for a first event from a second network function, the subscription request including topic information corresponding to the first event and an identifier of the first event, wherein the topic information and / or the identifier of the first event correspond to the network information of the first event; After receiving the trigger notification of the first event, the trigger notification is sent to the second network function, and the trigger notification corresponds to the network information.

2. The method of claim 1, wherein, The subscription request also includes: first authentication information.

3. The method of claim 2, wherein, The method further includes: If the first authentication information matches the second authentication information pre-stored in the first network function, it is determined that the second network function has the permission to subscribe to the first event, and the second authentication information is used to indicate the identity information of the user of the first event.

4. The method of claim 2, wherein, The method further includes: Send a first authentication request message to the third network function. The first authentication request message includes the first authentication information. The first authentication request message is used to request the third network function to authenticate whether the second network function has the permission to subscribe to the first event. Receive the first authentication result from the third network function; Based on the first authentication result, determine whether the second network function has the permission to subscribe to the first event.

5. The method of claim 4, wherein, The first authentication request message also includes: the topic information, and / or, the identifier of the first event.

6. The method according to any one of claims 1 to 5, characterized in that, The process of obtaining the trigger notification for the first event includes: Receive an event trigger notification from the fifth network function, the trigger notification including topic information corresponding to the first event and the identifier of the first event, wherein the topic information and / or the identifier of the first event correspond to the network information of the first event.

7. The method of claim 6, wherein, The trigger notification also includes third-party authentication information.

8. The method of claim 7, wherein, The method further includes: If the third authentication information matches the second authentication information pre-stored in the first network function, then it is determined that the fifth network function has the authority to monitor the first event, and the second authentication information is used to indicate the identity information of the user of the first event.

9. The method of claim 7, wherein, The method further includes: Send a second authentication request message to the third network function. The second authentication request message includes the third authentication information. The second authentication request message is used to request the third network function to authenticate whether the fifth network function has the authority to monitor the first event. Receive the second authentication result from the third network function; Based on the second authentication result, determine whether the fifth network function has the authority to monitor the first event.

10. The method of claim 9, wherein, The second authentication request message also includes: the topic information, and / or, the identifier of the first event.

11. The method according to claim 3 or 8, characterized in that, Before receiving the subscription request for the first event from the second network function, the method further includes: Receive an event registration request message from the fourth network function, the event registration request message including: the subject information of the first event and the identifier of the first event; Send an event registration response message to the fourth network function, the event registration response message including: registration result and the second authentication information.

12. The method of claim 11, wherein, The event registration request message also includes: the processing rules for the first event.

13. A communication method characterized by comprising: Applied to second network functions, including: Send a subscription request for a first event to a first network function. The subscription request includes topic information corresponding to the first event and an identifier of the first event, wherein the topic information and / or the identifier of the first event correspond to the network information of the first event. Receive a trigger notification for the first event from the first network function, the trigger notification corresponding to the network information.

14. The method of any one of claims 1-13, wherein, The subscription request also includes: the processing rules for the first event.

15. A method of communication, comprising: Applications to third-party network functions include: Receive an event registration request message from a fourth network function, the event registration request message including: topic information of a first event and an identifier of the first event, wherein the topic information and / or the identifier of the first event correspond to the network information of the first event; the first event is any one of the subscribed events; Send an event registration response message to the fourth network function. The event registration response message includes: registration result and second authentication information, the second authentication information being used to indicate the identity information of the user of the first event.

16. The method of claim 15, wherein, Also includes: Send first configuration information to the subscription network function of the first event, the first configuration information including: the topic information, the identifier of the first event, and the second authentication information; and / or, Send second configuration information to the monitoring network function of the first event. The second configuration information includes: the topic information, the identifier of the first event, and the second authentication information.

17. The method of claim 16, wherein, The first configuration information further includes: a subscription indication for the first event, and / or, a processing rule for the first event; the second configuration information further includes: a monitoring indication for the first event, and / or, a processing rule for the first event.

18. The method of any one of claims 15-17, wherein, The method further includes: Receive a first authentication request message from a first network function. The first authentication request message includes first authentication information. The first authentication request message is used to request the third network function to authenticate whether the second network function has the permission to subscribe to the first event. The second network function is used to subscribe to the first event. The first authentication result is determined based on the first authentication information and the second authentication information; Send the first authentication result to the first network function.

19. The method of any one of claims 15-18, wherein, The method further includes: Receive a second authentication request message from a first network function, the second authentication request message including third authentication information, the second authentication request message being used to request the third network function to authenticate whether the fifth network function has the authority to monitor the first event, the fifth network function being used to monitor the first event; The second authentication result is determined based on the first authentication information and the second authentication information; Send the second authentication result to the first network function.

20. The method of claim 18 or 19, wherein, The first authentication request message includes: subject information of the first event, and / or, the identifier of the first event.

21. The method according to claim 19 or 20, characterized in that, The second authentication request message also includes: the topic information, and / or, the identifier of the first event.

22. A method of communication, comprising: Applied to the fourth network function, including: Send an event registration request message, the event registration request message including: topic information of a first event and identifier of a first event, wherein the topic information and / or the identifier of the first event correspond to the network information of the first event, and the first event is any one of the subscribed events; Receive an event registration response message, the event registration response message including: registration result and second authentication information, the second authentication information being used to indicate the identity information of the user of the first event.

23. The method of any one of claims 15-22, wherein, The event registration request message also includes the processing rules for the first event.

24. The method of any one of claims 15-23, wherein, The registration response message also includes: information about the first network function, which is used for event subscription and event notification management.

25. The method of any one of claims 1-23, wherein, The topic information includes one or more of the following: The user information of the first event, or the business information of the first event.

26. The method of any one of claims 11, 15-25, wherein, The fourth network function is one or more of the following: The capability includes open network functions, service control functions, service orchestration functions, access network service management functions, core network service management functions, mobile network operation and maintenance management system, or a fifth network function, wherein the fifth network function is used to monitor the first event.

27. The method of any one of claims 1-26, wherein, The network information includes one or more of the following: Public Land Mobile Network (PLMN) information, network slice information, non-public network (NPN) information, and subnet information.

28. The method of any one of claims 1-27, wherein, The topic information, and / or the network information corresponding to the identifier of the first event, includes one of the following: The topic information indicates the network information; or, The identifier of the first event indicates the network information; or, Both the topic information and the identifier of the first event indicate the network information.

29. A communications device, characterized by include: At least one processor, said processor being coupled to a memory for storing a computer program; The at least one processor is configured to run part or all of the computer program to cause the method of any one of claims 1-28 to be performed.

30. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores instructions that, when executed by a computer, cause the method as described in any one of claims 1-28 to be performed.

31. A computer program product comprising computer programs or instructions, characterized in that, When the computer program or instructions are run on a computer, the method as described in any one of claims 1-28 is performed.

32. A communication system, characterized by Includes the first network function, the second network function, and the third network function. The first network function is used to perform the method as described in any one of claims 1-12, the second network function is used to perform the method as described in claim 13 or 14, the third network function is used to perform the method as described in any one of claims 15-21, and the fourth network function is used to perform the method as described in any one of claims 22-28.

Images