CN113498051B - Method for subscribing network event and network function - Google Patents
Method for subscribing network event and network function Download PDFInfo
- Publication number
- CN113498051B CN113498051B CN202010192714.2A CN202010192714A CN113498051B CN 113498051 B CN113498051 B CN 113498051B CN 202010192714 A CN202010192714 A CN 202010192714A CN 113498051 B CN113498051 B CN 113498051B
- Authority
- CN
- China
- Prior art keywords
- event
- network function
- network
- access type
- function entity
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
- H04W8/20—Transfer of user or subscriber data
Landscapes
- Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
The embodiment of the invention discloses a method for subscribing network events and a network function, which are used for judging which management function is selected to subscribe the events. The method comprises the following steps: a first event subscription operation is invoked, the parameters of which include: event identification and access type information; and calling a second event subscription operation of a third network function, wherein the third network function corresponds to the event identifier or the access type information.
Description
Technical Field
The embodiment of the invention relates to the field of communication, in particular to a method for subscribing network events and a network function.
Background
When a user accesses a Network through multiple access networks, such as a Third Generation Partnership Project (3 GPP) macro cellular access Network, and also a Wireless Local Area Network (WLAN), the user may be served by two different management functions, which may include: access and Mobility Management Function (AMF) services and/or Session Management Function (SMF), in which case Unified Data Management (UDM) cannot determine which AMF to select for subscribing to an event, thereby resulting in that event subscription may not be achieved when a user accesses a network through multiple Access networks.
Disclosure of Invention
The embodiment of the invention aims to provide a method for subscribing network events and a network function, which are used for realizing event subscription when a user accesses a network through a plurality of access networks.
In a first aspect, there is provided a method of subscribing to a network event, the method being performed by a first network function, the method comprising: a first event subscription operation is invoked, the parameters of which include: event identification and access type information; and calling a second event subscription operation of a third network function, wherein the third network function corresponds to the event identifier or the access type information.
In a second aspect, there is provided a method of subscribing to a network event, the method being performed by a second network function, the method comprising: invoking a first event subscription operation of a first network function, parameters of the first event subscription operation comprising: event identification or access type information.
In a third aspect, there is provided a method of subscribing to a network event, the method being performed by a third network function, the method comprising: a second event subscription operation is invoked, wherein the second event subscription operation parameters include: event identification or access type information; and sending an event notification when the event matched with the event identification or the access type information occurs.
In a fourth aspect, there is provided a first network function comprising: a first invoking module, configured to invoke a first event subscription operation, where parameters of the first event subscription operation include: event identification and access type information; and the processing module is used for calling a second event subscription operation of a third network function, and the third network function corresponds to the event identifier or the access type information.
In a fifth aspect, there is provided a second network function, the network function comprising: a second invoking module, configured to invoke a first event subscription operation of a first network function, where parameters of the first event subscription operation include: event identification or access type information.
In a sixth aspect, a third network function is provided, the network function comprising: a third invoking module, configured to invoke a second event subscription operation, where the second event subscription operation parameter includes: event identification or access type information; a sending module, configured to send an event notification when an event matching the event identifier or the access type information occurs.
In a seventh aspect, a network function is provided, the terminal device comprising a processor, a memory and a computer program stored on the memory and operable on the processor, the computer program, when executed by the processor, implementing the steps of the method for subscribing to network events according to the first aspect, the second aspect or the third aspect.
In an eighth aspect, there is provided a computer readable storage medium having stored thereon a computer program which, when executed by a processor, carries out the steps of the method of subscribing to network events of the first or second or third aspect.
The method for subscribing the network event and the network function provided by the embodiment of the invention are invoked through a first event subscription operation, and the parameters of the first event subscription operation comprise: event identification and access type information; and calling a second event subscription operation of a third network function, wherein the third network function corresponds to the event identifier or the access type information, so that the UDM can judge which AMF is selected to subscribe the event, and the event subscription is realized.
Drawings
The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:
FIG. 1 is a schematic flow diagram of a method of subscribing to network events according to one embodiment of the present invention;
FIG. 2 is a schematic flow diagram of a method of subscribing to network events according to another embodiment of the present invention;
FIG. 3 is a schematic flow diagram of a method of subscribing to network events according to another embodiment of the present invention;
FIG. 4 is a block diagram of a first network function according to one embodiment of the invention;
FIG. 5 is a block diagram of a second network function according to one embodiment of the invention;
FIG. 6 is a block diagram of a third network function according to one embodiment of the invention;
fig. 7 is a schematic diagram of the structure of a network function according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the technical solutions of the present application will be described in detail and completely with reference to the following specific embodiments of the present application and the accompanying drawings. It should be apparent that the described embodiments are only some of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application. "and/or" in various embodiments of the present specification means at least one of before and after.
It should be understood that the technical solutions of the embodiments of the present invention may be applied to various communication systems, for example: a Long Term Evolution (LTE) System, an LTE Frequency Division Duplex (FDD) System, an LTE Time Division Duplex (TDD) System, a Universal Mobile Telecommunications System (UMTS) or Worldwide Interoperability for Microwave Access (WiMAX) communication System, a 5G System, a New Radio (NR) System, or a subsequently evolved communication System.
In the embodiment of the present invention, the Terminal device may include, but is not limited to, a Mobile Station (MS), a Mobile Terminal (Mobile Terminal), a Mobile phone (Mobile Telephone), a User Equipment (UE), a handset (handset) and a portable device (portable device), a vehicle (vehicle), and the like, and the Terminal device may communicate with one or more core networks through a Radio Access Network (RAN), for example, the Terminal device may be a Mobile phone (or "cellular" phone), a computer with a wireless communication function, and the Terminal device may also be a portable, pocket, handheld, computer built-in, or vehicle-mounted Mobile apparatus.
In the embodiment of the present invention, the network function is a device deployed in a radio access network to provide a wireless communication function for a terminal device. The network function may be a base station, which may include various forms of macro base stations, micro base stations, relay stations, access points, and the like. In systems employing different radio access technologies, the names of devices having a base station function may differ. For example, in an LTE network, called an Evolved Node B (eNB or eNodeB), in a third generation (3 rd generation,3 g) network, called a Node B (Node B), or a network function in a subsequent Evolved communication system, etc., although the words are not limiting.
As shown in fig. 1, an embodiment of the present invention provides a method 100 for subscribing a Network event, where the method may be performed by a Network Function, and the Network Function may be an entity Network device implementing the Network Function, or may be a Network Function, for example, at least one of an AMF, an SMF, a UDM, and a Network Exposure Function (NEF), in other words, the method may be performed by software or hardware installed in the Network Function, and the method includes the following steps:
s122: the second network function invokes a first event subscription operation of the first network function.
In one implementation, this step may include the second network function sending a request to the first network function to invoke the first event subscription operation. The second network function may be, for example, NEF and the first network function may be UDM. This step may include NEF invoking a first event subscription operation of UDM, such as invoking a Nudm _ EventExposure _ Subscribe operation. The parameters of the first event subscription operation include: event identification or access type information.
S112: a first event subscription operation of a first network function is invoked.
In one implementation, this step may include: the first network function receives a request sent by the second network function to invoke the first event subscription operation. A first event subscription operation, e.g., UDM, is invoked. The parameters of the first event subscription operation include: event identification and access type information.
S114: the first network function invokes a second event subscription operation of the third network function.
In one implementation, this step may include: the first network function sends a request to the third network function for invoking the second event subscription operation. The third network function corresponds to the event identifier or the access type information. The UDM invokes event subscription operations of one or more AMFs, such as invoking a Namf _ EventExposure _ Subscribe operation, respectively.
S134: a second event subscription operation of the third network function is invoked.
In one implementation, this step may include: the third network function receives a request sent by the first network function for invoking the second event subscription operation. For example, a second event subscription operation of the AMF is invoked. The second event subscription operating parameters include: event identification or access type information.
In one implementation, the AMF may return the event subscription operation, and the UDM returns the event subscription operation to the NEF upon receipt of the return of the AMF.
S136: the third network function sends an event notification in case an event matching the event identification or the access type information occurs.
In one implementation, the parameters of the second event subscription operation include: the event identification and/or the access type information.
And if the parameter of the second event subscription operation includes an event identifier, the AMF invokes an event notification operation of the AMF, for example, invokes a Namf _ evenexpressure _ Notify operation when an event matching the event identifier occurs, and sends the event notification to the UDM with the event notification receiving address of the UDM as a parameter, and the UDM determines a target event notification corresponding to the access type information from the received event notifications according to the access type information and sends the target event notification to the NEF.
In the case that the parameter of the second event subscription operation includes the access type information, when the AMF has an event, the AMF invokes an event notification operation of the AMF, for example, invokes a Namf _ EventExposure _ Notify operation, sends the event notification to the UDM with the event notification receiving address of the UDM as a parameter, and the UDM determines a target event notification corresponding to the event identifier from the received event notifications according to the event identifier and transmits the target event notification to the NEF.
The parameters of the subscription operation at the second event include: in the case of the event identifier and the access type information, when an event matching the event identifier and the access type information occurs, the AMF invokes an event notification operation of the AMF, for example, invokes a Namf _ EventExposure _ Notify operation, and takes an event notification receiving address of the UDM or an event notification receiving address of the NEF as a parameter, and takes the obtained user-related information as a parameter. Through this call, the network information is transmitted to the NEF.
Therefore, in the method for subscribing to a network event provided by the embodiment of the present invention, a first event subscription operation is invoked, and a parameter of the first event subscription operation includes: event identification and access type information; and calling a second event subscription operation of a third network function, wherein the third network function corresponds to the event identifier or the access type information, so that the UDM can select the AMF corresponding to the event identifier or the access type information to subscribe the event, thereby realizing event subscription.
As shown in fig. 2, an embodiment of the present invention provides a method 200 for subscribing to a network event, which may be performed by a network function, which may be an entity network device implementing the network function, or may be a network function, such as at least one of an AMF, an SMF, a UDM, and a NEF, in other words, the method may be performed by software or hardware installed in the network function, and the method includes the following steps:
s222: the second network function invokes a first event subscription operation of the first network function.
S212: a first event subscription operation of a first network function is invoked.
The above steps S222 and 212 may use the same text descriptions as the steps S122 and S112 in the embodiment of fig. 1, and are not repeated herein.
S213: the first network function determines the information of the network function accessed by the user according to the user identification, and determines the third network function from the information of the network function accessed by the user according to the event identification or the access type information.
In one implementation, the network function accessed by the user is multiple.
In one implementation, the access type information includes: at least one of an access type, a report type, a default type. Among them, the access types are, for example: 3gpp access or non-3 gpp access, reporting type, such as: reporting when corresponding events occur in both accesses, or reporting when corresponding events occur in only one of the two accesses, wherein the type information represents a default type when not carried, such as reporting when corresponding events occur in 3gpp access or reporting when corresponding events occur in only one of the two accesses.
After determining the third network function, returning information indicating that the subscription of the first event is successful to a second network function calling the subscription operation of the first event. And under the condition that the third network function does not exist in the information of the network function accessed by the user, returning failure information representing subscription failure to the second network function invoking the first event subscription operation.
And the second network function receives the information which indicates that the first event is subscribed successfully or the failure information which indicates that the first event is subscribed unsuccessfully and is returned by the first network function.
S214: the first network function invokes a second event subscription operation of the third network function.
S234: a second event subscription operation of a third network function is invoked.
S236: the third network function sends an event notification in case an event matching the event identification or the access type information occurs.
The above steps S214, S234 and S236 may adopt the same text description as the steps S114, S134 and S136 in the embodiment of fig. 1, and are not described herein again.
Therefore, the method for subscribing the network event provided by the embodiment of the invention determines the information of the network function accessed by the user according to the user identification; and determining the third network function from the information of the network function accessed by the user according to the event identifier or the access type information, and enabling the UDM to judge which AMF is selected to subscribe the event when the user accesses the network through a plurality of access networks, thereby realizing the event subscription.
As shown in fig. 3, an embodiment of the present invention provides a method 300 for subscribing to a network event, which may be performed by a network function, which may be a physical network device implementing the network function, or may be at least one of a network function, such as AMF, SMF, UDM, and NEF, in other words, the method may be performed by software or hardware installed in the network function, and the method includes the following steps:
s322: the second network function invokes a first event subscription operation of the first network function.
S312: a first event subscription operation of a first network function is invoked.
The steps S222 and S212 may use the same text descriptions as the steps S122 and S112 in the embodiment of fig. 1, and are not repeated herein.
In an implementation manner, step S313 may be further included after step S312, and the same text description as that in step S213 in the embodiment of fig. 2 is adopted, which is not described herein again.
S314: the first network function invokes a second event subscription operation of the third network function.
The third network function corresponds to the event identifier or the access type information. The UDM invokes event subscription operations of one or more AMFs, such as invoking a Namf _ EventExposure _ Subscribe operation, respectively. The second event subscription operating parameters include: event identification or access type information, and the parameters of the second event subscription operation further include: and (4) identifying the user.
S334: a second event subscription operation of a third network function is invoked.
S336: and sending an event notification when an event matching the access type information, the event identification and the user identification occurs.
When an event matching the access type information, the event identifier, and the user identifier occurs, the AMF invokes an event notification operation of the AMF, for example, invokes a Namf _ EventExposure _ Notify operation, and takes an event notification receiving address of the UDM or an event notification receiving address of the NEF as a parameter, and takes the obtained user-related information as a parameter. Through this call, the network information is transmitted to the NEF.
Therefore, the method for subscribing the network event provided by the embodiment of the invention determines the information of the network function accessed by the user according to the user identification; and determining the third network function from the information of the network function accessed by the user according to the event identifier or the access type information, so that the UDM can judge which AMF is selected to subscribe the event, thereby realizing the event subscription.
Fig. 4 is a schematic structural diagram of a first network function according to an embodiment of the present invention. As shown in fig. 4, the first network function 400 includes: a first calling module 410 and a processing module 420.
The first invoking module 410 is used for invoking a first event subscription operation, and parameters of the first event subscription operation include: event identification and access type information. The processing module 420 is configured to invoke a second event subscription operation of a third network function, where the third network function corresponds to the event identifier or the access type information.
In one implementation, the parameters of the first event subscription operation further include: the processing module 420 is further configured to determine, according to the user identifier, information of a network function accessed by the user before the second event subscription operation for invoking the third network function; and determining the third network function from the information of the network function accessed by the user according to the event identifier or the access type information.
In one implementation, the parameters of the second event subscription operation include: the event identification and/or the access type information.
In one implementation, the parameters of the second event subscription operation further include: the user identification.
In one implementation, the processing module 420 is configured to return information indicating that the subscription of the first event is successful to the second network function that invokes the subscription operation of the first event; or under the condition that the third network function does not exist in the information of the network function accessed by the user, returning failure information representing subscription failure to the second network function invoking the first event subscription operation.
In one implementation, the access type information includes: at least one of an access type, a report type, a default type.
The first network function 400 according to the embodiment of the present invention may refer to a flow corresponding to the first network function execution step in the methods 100 to 300 according to the embodiment of the present invention, and each unit/module and the other operations and/or functions in the first network function 400 are respectively for implementing the flow corresponding to the first network function execution step in the methods 100 to 300, and can achieve the same or equivalent technical effects, and for the sake of brevity, are not described again here.
Fig. 5 is a schematic structural diagram of a second network function according to an embodiment of the present invention. As illustrated in fig. 5, the second network function 500 includes: a second calling module 510.
The second invoking module 510 is configured to invoke a first event subscription operation of the first network function, where parameters of the first event subscription operation include: event identification or access type information.
In one implementation, the second invoking module 510 is further configured to, after the first event subscription operation invoking the first network function, receive information that indicates that the first event subscription is successful or failure information that indicates that the first event subscription is failed, where the information is returned by the first network function.
In one implementation manner, the parameters of the first event subscription operation further include: and (4) identifying the user.
In one implementation, the access type information includes: at least one of an access type, a report type, a default type.
The second network function 500 according to the embodiment of the present invention may refer to a flow corresponding to the second network function execution step in the methods 100 to 300 according to the embodiment of the present invention, and each unit/module and the other operations and/or functions in the second network function 500 are respectively for implementing the flow corresponding to the second network function execution step in the methods 100 to 300, and can achieve the same or equivalent technical effects, and for the sake of brevity, are not described again here.
Fig. 6 is a schematic structural diagram of a third network function according to an embodiment of the present invention. As depicted in fig. 6, the third network function 600 includes: a third calling module 610 and a sending module 620.
The third invoking module 610 is configured to invoke a second event subscription operation, where the second event subscription operation parameters include: event identification or access type information. The sending module 620 is configured to send an event notification when an event matching the event identifier or the access type information occurs.
In an implementation manner, the second event subscription operation further includes a user identifier, and the sending module 620 is configured to send an event notification when an event matching the access type information, the event identifier, and the user identifier occurs.
In one implementation, the access type information includes: at least one of an access type, a report type, a default type.
The third network function 600 according to the embodiment of the present invention may refer to a flow corresponding to the third network function execution step in the methods 100 to 300 according to the embodiments of the present invention, and each unit/module and the other operations and/or functions in the third network function 600 are respectively for implementing the flow corresponding to the third network function execution step in the methods 100 to 300, and can achieve the same or equivalent technical effects, and for brevity, no further description is provided here.
Referring to fig. 7, fig. 7 is a structural diagram of a network function applied in the embodiment of the present invention, which can implement a flow of any one or more network function execution steps in the first, second, or third network functions in the method embodiments 100-300, and achieve the same effect. As shown in fig. 7, the network function 700 includes: a processor 701, a transceiver 702, a memory 703 and a bus interface, wherein:
in this embodiment of the present invention, the network function 700 further includes: a computer program stored on the memory 703 and executable on the processor 701, the computer program when executed by the processor 701 implementing the process of the steps performed by any one or more of the first, second or third network functions of the method embodiments 100-300.
In fig. 7, the bus architecture may include any number of interconnected buses and bridges, with one or more processors, represented by processor 701, and various circuits, represented by memory 703, being linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The transceiver 702 may be a plurality of elements including a transmitter and a receiver that provide a means for communicating with various other apparatus over a transmission medium.
The processor 701 is responsible for managing the bus architecture and general processing, and the memory 703 may store data used by the processor 701 in performing operations.
An embodiment of the present invention further provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the computer program implements a flow of any one or more network function execution steps of the first, second, or third network functions in the foregoing method embodiments 100 to 300, and can achieve the same technical effect, and in order to avoid repetition, details are not described here again. The computer-readable storage medium may be a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrases "comprising a component of' 8230; \8230;" does not exclude the presence of another like element in a process, method, article, or apparatus that comprises the element.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal (such as a mobile phone, a computer, a server, an air conditioner, or a network function) to execute the method according to the embodiments of the present invention.
While the present invention has been described with reference to the embodiments shown in the drawings, the present invention is not limited to the embodiments, which are illustrative and not restrictive, and it will be apparent to those skilled in the art that various changes and modifications can be made therein without departing from the spirit and scope of the invention as defined in the appended claims.
Claims (16)
1. A method of subscribing to network events, the method being performed by a first network function entity, the method comprising:
a first event subscription operation is invoked by the second network function entity, and parameters of the first event subscription operation include: user identification, event identification and access type information;
calling a second event subscription operation of a third network function entity, wherein the third network function entity corresponds to the event identifier or the access type information;
wherein, prior to the invoking of the second event subscription operation of the third network function entity, the method further comprises:
determining the information of the network function accessed by the user according to the user identification;
and determining the third network function entity from the information of the network function accessed by the user according to the event identifier or the access type information.
2. The method of claim 1, wherein the parameters of the second event subscription operation include: the event identification and/or the access type information.
3. The method of claim 2, wherein the parameters of the second event subscription operation further comprise: the user identification.
4. The method of claim 1, wherein the determining the third network function entity from the information of the network function accessed by the user comprises:
after the third network functional entity is determined, returning information representing that the first event subscription is successful to a second network functional entity calling the first event subscription operation; or
And under the condition that the third network function entity does not exist in the information of the network function accessed by the user, returning failure information representing subscription failure to the second network function entity calling the first event subscription operation.
5. The method of claim 1, wherein the access type information comprises: at least one of an access type, a report type, a default type.
6. A method of subscribing to network events, the method being performed by a second network function entity, the method comprising:
invoking a first event subscription operation of a first network function entity, parameters of the first event subscription operation including: user identification, event identification and access type information;
the user identification is used for the first network function entity to determine the information of the network function accessed by the user; the event identification or the access type information is used for the first network function entity to determine a third network function entity from the information of the network function accessed by the user; and the first network function entity calls a second event subscription operation of the third network function entity, and the third network function entity corresponds to the event identifier or the access type information.
7. The method of claim 6, wherein after the invoking the first event subscription operation of the first network function entity, the method further comprises:
and receiving information which is returned by the first network function entity and indicates that the first event is subscribed successfully or failure information which indicates that the first event is subscribed unsuccessfully.
8. The method of claim 6, wherein the access type information comprises: at least one of an access type, a report type, a default type.
9. A method of subscribing to network events, the method being performed by a third network function entity, the method comprising:
a second event subscription operation is invoked by the first network functional entity, and the second event subscription operation parameters include: event identification or access type information;
transmitting an event notification in case that an event matching the event identification or the access type information occurs;
wherein, before the second event subscription operation is invoked by a first network function entity, a first event subscription operation of the first network function entity is invoked by a second network function entity, and parameters of the first event subscription operation include: a user identifier, the event identifier and the access type information; the first network function entity determines the information of the network function accessed by the user according to the user identification; the first network functional entity determines the third network functional entity from the information of the network function accessed by the user according to the event identifier or the access type information; the third network function entity corresponds to the event identifier or the access type information.
10. The method of claim 9, wherein the second event subscription operation further includes the user identifier, and wherein sending an event notification if an event matching the event identifier or the access type information occurs comprises:
and sending an event notification when an event matching the access type information, the event identification and the user identification occurs.
11. The method of claim 9, wherein the access type information comprises: at least one of an access type, a report type, a default type.
12. A first network function entity, comprising:
a first invoking module, configured to invoke a first event subscription operation by a second network function entity, where parameters of the first event subscription operation include: user identification, event identification and access type information;
the processing module is used for calling a second event subscription operation of a third network functional entity, and the third network functional entity corresponds to the event identifier or the access type information;
the processing module is further configured to determine, according to the user identifier, information of a network function accessed by the user before the second event subscription operation for invoking the third network function entity; and determining the third network function entity from the information of the network function accessed by the user according to the event identifier or the access type information.
13. A second network function entity, comprising:
a second invoking module, configured to invoke a first event subscription operation of a first network function entity, where a parameter of the first event subscription operation includes: user identification, event identification and access type information; the user identification is used for the first network function entity to determine the information of the network function accessed by the user; the event identifier or the access type information is used for the first network function entity to determine a third network function entity from the information of the network function accessed by the user; and the first network functional entity calls a second event subscription operation of a third network functional entity, wherein the third network functional entity corresponds to the event identifier or the access type information.
14. A third network function entity, comprising:
a third invoking module, configured to invoke a second event subscription operation by a first network function entity, where the second event subscription operation parameter includes: event identification or access type information;
a sending module, configured to send an event notification when an event matching the event identifier or the access type information occurs;
wherein a first event subscription operation of a first network function entity is invoked by a second network function entity before the second event subscription operation is invoked by the first network function entity, and parameters of the first event subscription operation include: user identification, event identification and access type information; the first network function entity determines the information of the network function accessed by the user according to the user identification; the first network functional entity determines the third network functional entity from the information of the network function accessed by the user according to the event identifier or the access type information; the third network function entity corresponds to the event identifier or the access type information.
15. A network function entity, comprising: a memory, a processor and a computer program stored on the memory and executable on the processor, the computer program, when executed by the processor, implementing the steps of the method of subscribing to network events of any one of claims 1 to 5; or implementing a method of subscribing to network events as claimed in any of claims 6 to 8; or implementing the steps of the method of subscribing to network events of any of claims 9 to 11.
16. A computer-readable storage medium, comprising: a computer program stored on a memory and executable on a processor, the steps of the method of subscribing to network events according to any one of claims 1 to 5 being carried out when executed by the processor; or implementing a method of subscribing to network events as claimed in any of claims 6 to 8; or implementing the steps of a method of subscribing to network events as claimed in any of claims 9 to 11.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010192714.2A CN113498051B (en) | 2020-03-18 | 2020-03-18 | Method for subscribing network event and network function |
| PCT/CN2021/081463 WO2021185303A1 (en) | 2020-03-18 | 2021-03-18 | Method for subscribing to network event and network functions |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010192714.2A CN113498051B (en) | 2020-03-18 | 2020-03-18 | Method for subscribing network event and network function |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113498051A CN113498051A (en) | 2021-10-12 |
| CN113498051B true CN113498051B (en) | 2023-01-03 |
Family
ID=77770133
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010192714.2A Active CN113498051B (en) | 2020-03-18 | 2020-03-18 | Method for subscribing network event and network function |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN113498051B (en) |
| WO (1) | WO2021185303A1 (en) |
Family Cites Families (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070217435A1 (en) * | 2006-03-15 | 2007-09-20 | Crocker Ronald T | Method and apparatus to provide network event messages |
| JP5612036B2 (en) * | 2012-07-31 | 2014-10-22 | 京セラドキュメントソリューションズ株式会社 | Push notification system and provider constituting the same |
| CN110351698B (en) * | 2018-04-04 | 2022-04-05 | 华为技术有限公司 | Event subscription method, device and system |
| CN112188444B (en) * | 2018-04-09 | 2021-08-03 | 华为技术有限公司 | Method and device for subscribing service |
| CN110505591B (en) * | 2018-05-18 | 2022-09-30 | 京东方科技集团股份有限公司 | Subscription service entity, subscription terminal, and information subscription method and system |
| CN110557744B (en) * | 2018-05-31 | 2022-08-19 | 华为技术有限公司 | Method for subscribing event and network function network element |
| CN110650489B (en) * | 2018-06-26 | 2022-02-15 | 华为技术有限公司 | Method and device for managing monitoring events |
| CN110536282B (en) * | 2019-03-28 | 2023-03-21 | 中兴通讯股份有限公司 | Event notification method and device |
-
2020
- 2020-03-18 CN CN202010192714.2A patent/CN113498051B/en active Active
-
2021
- 2021-03-18 WO PCT/CN2021/081463 patent/WO2021185303A1/en active Application Filing
Also Published As
| Publication number | Publication date |
|---|---|
| CN113498051A (en) | 2021-10-12 |
| WO2021185303A1 (en) | 2021-09-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112672383B (en) | Communication method and network device | |
| US20200145843A1 (en) | Method for configuring anr, terminal device, base station, and core network device | |
| EP3668182B1 (en) | Communication method and device | |
| CN102695152A (en) | Mobile communication device and method for requesting emergency bearer services | |
| US11785531B2 (en) | Method and device for transmitting system information | |
| CN109168171B (en) | Configuration information acquisition method, device, equipment and system | |
| CN110049578B (en) | Wireless connection modification method, device and system | |
| CN110392400B (en) | Communication method and related equipment | |
| CN113632512A (en) | Transmitting monitoring event information during mobility procedures | |
| US20230015325A1 (en) | Methods, Network Function Nodes and Computer Readable Media for Event Subscription Management | |
| CN110351683B (en) | Parameter transmission method and device | |
| WO2022206315A1 (en) | Access control method and apparatus for network slice | |
| CN110784912A (en) | Management method of session correspondence and terminal equipment | |
| CN115299168A (en) | Method and apparatus for handover | |
| CN113498051B (en) | Method for subscribing network event and network function | |
| EP4293976A1 (en) | Data analysis method and apparatus, electronic device, and storage medium | |
| CN113254805A (en) | Method and network equipment for inquiring group position | |
| CN113556829B (en) | Method for establishing network connection and electronic equipment | |
| CN114080000B (en) | Network slice determination method and device, core network equipment and terminal | |
| CN111800889B (en) | Method for processing protocol data unit session, terminal equipment and network equipment | |
| AU2018419068A1 (en) | Communication method, network device and terminal device | |
| CN113810956B (en) | Method and device for switching multicast service | |
| CN111836247A (en) | Processing method and device for short-distance discovery service of terminal | |
| US12035411B2 (en) | Methods, network function nodes and computer readable media for event subscription management | |
| CN112689326B (en) | Method, terminal and network side equipment for indicating NSSAI carrying |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |