Communication method and communication device

Abstract

The present application provides a communication method and a communication device. A session management network element notifies a user plane network element of a processing mode for data associated with a first event while unsubscribing from the first event, wherein the processing mode is: upon receiving the notification, sending the data associated with the first event, or on the basis of event report information from a consumer, sending the data associated with the first event, wherein the event report information is used for indicating a reporting mode for the data associated with the first event; and then on the basis of the first processing mode, the user plane network element sends the data associated with the first event, for example, the user plane network element sends the data to the consumer on the basis of indication information, so that resource waste caused by such processing mode in which the user plane network element always directly discards collected data after being unsubscribed can be avoided.

Description

A communication method and device thereof

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of the People's Republic of China on April 3, 2024, with application number 202410405997.2 and application name “A communication method and device thereof”, the entire contents of which are incorporated by reference into this application; this application claims priority to the Chinese patent application filed with the State Intellectual Property Office of the People's Republic of China on August 16, 2024, with application number 202411136928.2 and application name “A communication method and device thereof”, the entire contents of which are incorporated by reference into this application. Technical Field

[0003] The present application relates to the field of communication technology, and in particular to a communication method and apparatus thereof. Background Art

[0004] Consumers can collect data from various network elements to conduct event analysis. For example, the network data analytics function (NWDAF) acts as a consumer and subscribes to certain data from the user-plane network element to derive service experience analysis results. For example, the subscribed data includes: the number of packet transmission / retransmission times, packet transmission delay, etc. The subscription process includes the following steps: the consumer selects a suitable session management network element, the session management network element selects a suitable user-plane network element, the session management network element sends a subscription message to the user-plane network element, and the user-plane network element sends the data associated with the subscription message to the consumer. If the subscribed user-plane network element can no longer provide the subscription data to the consumer, it is necessary to consider what to do next. Summary of the Invention

[0005] The embodiments of the present application provide a communication method and apparatus thereof, for solving the problem of processing collected data when a user-plane network element can no longer provide subscription data to consumers.

[0006] In the first aspect, the present application provides a communication method, which can be executed by a first user plane network element, or by other devices including the functions of the first user plane network element, or by a chip system (which can also be replaced by a chip) or other functional modules, and the chip system or functional module can realize the functions of the first user plane network element, and the chip system or functional module is, for example, set in the first user plane network element. Take the execution of the method by the first user plane network element as an example for introduction: a first message is received, and the first message includes a first processing method of the first user plane network element for the data associated with the first event; the first processing method is: when the subscription to the first event is terminated and / or the session associated with the first event is released, the data associated with the first event is sent, or when the subscription to the first event is terminated (termination can be replaced by cancellation) and / or the session associated with the first event is released, the data associated with the first event is sent according to the event report information and / or report suggestion information from the consumer, and the event report information is used to indicate the reporting method of the data associated with the first event;

[0007] When the first event subscription is terminated and / or the session associated with the first event is released, data associated with the first event is sent based on the first processing manner.

[0008] In this embodiment, a first processing method is used to instruct the first user-side network element how to send relevant data. That is, when the first event subscription is terminated and / or the session associated with the first event is released (or thereafter), the data that has been collected but not yet reported can be processed according to the first processing method. For example, the first user-side network element sends the data to the consumer according to the indication information, thereby avoiding the waste of resources caused by this processing method of always directly discarding the collected data.

[0009] In a possible implementation, the first message is used to indicate cancellation of subscription to the first event; or, the first message is used to indicate subscription to the first event.

[0010] In a possible implementation, when the first event subscription is terminated and / or the session associated with the first event is released, the method includes:

[0011] receiving information indicating cancellation of subscription to the first event; and / or;

[0012] Information indicating that the session associated with the first event is released, or releasing the session associated with the first event, is received.

[0013] In a possible implementation, the receiving the first message includes: receiving the first message from a session management network element; or receiving the first message from a consumer.

[0014] In one possible implementation, the first user plane network element may further send second information to the consumer, where the second information is used to indicate that the consumer's subscription to the first event has been terminated, so that the consumer can make further decisions based on the termination of the subscription.

[0015] In a possible implementation, the second information is also used to indicate the reason for subscription termination, so that the consumer can make further decisions based on the reason.

[0016] In one possible implementation, after sending the second information to the consumer, the first user-plane network element may further send third information to the session management network element. The third information is used to indicate that the first user-plane network element has notified the consumer that the consumer's subscription to the first event has been terminated. This avoids the session management network element also notifying the consumer.

[0017] In one possible implementation, after sending the data associated with the first event to the consumer, the first user-plane network element may also send fourth information to the session management network element, where the fourth information is used to indicate that the first user-plane network element has sent the data associated with the first event to which the consumer has subscribed to to the consumer.

[0018] On the second aspect, the present application provides a communication method, which can be executed by a first network element, or by other devices including the functions of the first network element, or by a chip system (which can also be replaced by a chip) or other functional modules, and the chip system or functional module can realize the functions of the first network element, and the chip system or functional module is, for example, set in the first network element. Take the execution of the method by the first network element as an example for introduction: the first network element sends a first message to the first user-plane network element, and the first message includes the first processing method of the first user-plane network element for the data associated with the first event; the first processing method is: when the subscription to the first event is terminated (termination can be replaced by cancellation) and / or the session associated with the first event is released, the data associated with the first event is sent, or when the subscription to the first event is terminated and / or the session associated with the first event is released, the data associated with the first event is sent according to the event report information and / or report establishment information from the consumer, and the event report information is used to indicate the reporting method of the data associated with the first event.

[0019] In this embodiment, a first processing method is used to instruct the first user-side network element how to send relevant data. That is, when the first event subscription is terminated and / or the session associated with the first event is released (or thereafter), the data that has been collected but not yet reported can be processed according to the first processing method. For example, the first user-side network element sends the data to the consumer according to the indication information, thereby avoiding the waste of resources caused by this processing method of always directly discarding the collected data.

[0020] In a possible implementation, the first message is used to indicate cancellation of subscription to the first event; or, the first message is used to indicate subscription to the first event.

[0021] In a possible implementation, it also includes: sending information to the first user plane network element to indicate cancellation of subscription to the first event; and / or sending information to the first user plane network element to indicate that the session associated with the first event is released, or releasing the session associated with the first event.

[0022] In a possible implementation manner, the first network element is a session management network element or the consumer.

[0023] In one possible implementation, the first network element is a session management network element, and the first message is used to indicate the cancellation of subscription to the first event. The session management network element may first determine that a first condition is satisfied before sending the first message to the first user plane network element. The first condition is redirecting the first user plane network element to a user plane network element other than the first user plane network element, or the first condition is canceling subscription to the first event, or the first condition is releasing a session associated with the first event. Optionally, the session management network element determines that the first condition is satisfied and generates the first message.

[0024] In one possible implementation, the first network element is a session management network element, and the first message is used to indicate the cancellation of subscription to the first event. The session management network element may receive fifth information from the consumer, and the fifth information is used to indicate a second processing method for related data when the first condition is met. The first processing method is related to the second processing method. The second processing method includes: sending data associated with the first event when the subscription to the first event is terminated and / or the session associated with the first event is released, or sending data associated with the first event based on event report information and / or report suggestion information from the consumer when the subscription to the first event is terminated and / or the session associated with the first event is released, wherein the event report information indicates a reporting method for the data associated with the first event. Furthermore, the session management network element sends the first message to the first user plane network element.

[0025] In one possible implementation, the first network element is a session management network element, which may send sixth information to the consumer, indicating that the consumer's subscription to the first event has been terminated. This allows the consumer to make further decisions based on the termination of the subscription.

[0026] In a possible implementation, the sixth information is also used to indicate the reason for subscription termination, so that the consumer can make further decisions based on the reason.

[0027] In one possible implementation, the first network element is a session management network element. After sending the first message to the first user-plane network element, the session management network element may further receive third information from the first user-plane network element. The third information is used to indicate that the first user-plane network element has notified the consumer that the consumer's subscription to the first event has been terminated. This avoids the session management network element also notifying the consumer.

[0028] In one possible implementation, the first network element is a session management network element. After sending the first message to the first user plane network element, the session management network element can also receive fourth information from the first user plane network element. The fourth information is used to indicate that the first user plane network element has sent the data associated with the first event subscribed by the consumer to the consumer.

[0029] In a third aspect, the present application provides a communication method, which can be executed by a second user plane network element, or by other devices including the functions of the second user plane network element, or by a chip system (which can also be replaced by a chip) or other functional modules, the chip system or functional module can realize the functions of the second user plane network element, and the chip system or functional module is, for example, set in the second user plane network element. Take the execution of the method by the second user plane network element as an example for introduction: the second user plane network element receives data associated with a first event from the session management network element or the first user plane network element, the first event is subscribed to by the consumer, and the first event is associated with the first user plane network element; the second user plane network element can also receive a second message from the session management network element, the second message is used to indicate subscription to a second event; the first event and the second event are associated; the second user plane network element sends the first event-associated data and the second event-associated data to the consumer.

[0030] In this embodiment, data associated with the first event is sent to the consumer via the second user plane network element.

[0031] In a possible implementation, the second user plane network element receives the data associated with the first event from the session management network element, including: receiving the data associated with the first event from the first user plane network element forwarded by the session management network element.

[0032] In a possible implementation manner, the second user plane network element receives the second message from the session management network element, including: receiving the second message from the second management network element forwarded by the first user plane network element.

[0033] In a possible implementation, the data associated with the first event is carried in the second message.

[0034] In one possible implementation, the second message includes first information, and the first information is used to indicate a reporting method for data associated with the second event; the second user-plane network element sends the first event-related data and the second event-related data to the consumer based on the reporting method.

[0035] In one possible implementation, the second user-plane network element sending the data associated with the first event and the data associated with the second event to the consumer includes: aggregating the data associated with the first event and the data associated with the second event to obtain third data; and sending the third data to the consumer. For example, the aggregation is to calculate an average.

[0036] In a fourth aspect, the present application provides a communication method, which can be executed by a session management network element, or by other devices including session management network element functions, or by a chip system (which can also be replaced by a chip) or other functional module, wherein the chip system or functional module can implement the functions of the session management network element, and the chip system or functional module is, for example, provided in the session management network element. This method is described using the execution of the session management network element as an example: the session management network element sends the first message to the first user plane network element, where the first message is used to indicate the cancellation of subscription to the first event; the session management network element receives data associated with the first event from the first user plane network element; and the session management network element sends the data associated with the first event to the second user plane network element.

[0037] In this embodiment, data associated with the first event is transmitted through the session management network element to the second user plane network element and then to the consumer.

[0038] In one possible implementation, the first message includes one or more of the following: first information, information of the second user plane network element, and third information; wherein, the first information is used to indicate a first processing method of the first user plane network element for the data associated with the first event, and the first processing method is: sending the data associated with the first event when the subscription to the first event is canceled and / or the session associated with the first event is released, or sending the data associated with the first event according to the event report information and / or report suggestion information from the consumer when the subscription to the first event is canceled and / or the session associated with the first event is released, and the event report information is used to indicate a reporting method for the data associated with the first event; the information of the second user plane network element is used to indicate that the data associated with the first event is sent to the second user plane network element; the third information is used to indicate that the first user plane network element is redirected to the second user plane network element.

[0039] In a possible implementation, the session management network element may further send a second message to the second user plane network element, where the second message is used to indicate subscription to a second event.

[0040] In a possible implementation, the session management network element sends the second message to the second user plane network element, including: sending the second message to the first user plane network element, so that the first user plane network element forwards the second message to the second user plane network element.

[0041] In a possible implementation, the data associated with the first event is carried in the second message.

[0042] In a fifth aspect, the present application provides a communication method, which can be executed by a session management network element, or by other devices including session management network element functions, or by a chip system (which can also be replaced by a chip) or other functional module. The chip system or functional module can implement the functions of the session management network element. The chip system or functional module is, for example, set in the session management network element. Taking the execution of the method by the session management network element as an example, the following is introduced: the session management network element sends the first message to the first user plane network element; the first message is used to indicate the cancellation of subscription to the first event; the session management network element receives data associated with the first event from the first user plane network element; the session management network element sends a second message to the second user plane network element, the second message is used to indicate the subscription to the second event; the first event and the second event are associated; the session management network element receives data associated with the second event from the second user plane network element; the session management network element aggregates the data associated with the first event and the data associated with the second event to obtain third data; the session management network element sends the third data to the consumer.

[0043] In this embodiment, the session management network element aggregates data from two user plane network elements and then sends the data to the consumer. The aggregation is, for example, to calculate an average value.

[0044] In one possible implementation, the first message includes first information, and the first information is used to indicate a first processing method of the first user-side network element for the data associated with the first event. The first processing method is: sending the data associated with the first event when the subscription to the first event is canceled and / or the session associated with the first event is released, or sending the data associated with the first event based on event report information and / or report suggestion information from the consumer when the subscription to the first event is canceled and / or the session associated with the first event is released. The event report information is used to indicate a reporting method for the data associated with the first event.

[0045] In a possible implementation, the second message includes second information, where the second information is used to indicate a reporting method for data associated with the second event.

[0046] In a sixth aspect, a communication device is provided, which may be the first user-plane network element described in the above aspects. The communication device has the functions of the above-mentioned first user-plane network element. The communication device is, for example, a functional module in a first network device, such as a baseband device or a chip system. Alternatively, the communication device may be the second user-plane network element described in the above aspects. The communication device has the functions of the above-mentioned second user-plane network element. The communication device is, for example, a functional module in a second user-plane network element, such as a baseband device or a chip system. Alternatively, the communication device may be the second session management network element described in the above aspects. The communication device has the functions of the above-mentioned second session management network element. The communication device is, for example, a functional module in a second session management network element, such as a baseband device or a chip system.

[0047] In an optional implementation, the communication device includes a baseband device and a radio frequency device. In another optional implementation, the communication device includes a processing unit (sometimes also referred to as a processing module) and a transceiver unit (sometimes also referred to as a transceiver module). The transceiver unit can implement a sending function and a receiving function. When the transceiver unit implements the sending function, it can be called a sending unit (sometimes also referred to as a sending module). When the transceiver unit implements the receiving function, it can be called a receiving unit (sometimes also referred to as a receiving module). The sending unit and the receiving unit can be the same functional module, which is called a transceiver unit, and the functional module can implement a sending function and a receiving function; or, the sending unit and the receiving unit can be different functional modules, and the transceiver unit is a general term for these functional modules.

[0048] In one possible implementation, the communication device further includes a storage unit (sometimes also referred to as a storage module), and the processing unit is used to couple with the storage unit and execute the program or instructions in the storage unit, enabling the communication device to perform the functions of the first user plane network element described in the above aspects, or perform the functions of the second user plane network element described in the above aspects, or perform the functions of the session management network element described in the above aspects.

[0049] In a seventh aspect, a communication device is provided, comprising an interface circuit and a processor, and optionally, a memory. The memory is configured to store a computer program, and the processor is coupled to the memory and the interface circuit. When the processor reads the computer program or instructions, the communication device executes the method performed by the first user plane network element in each of the aforementioned aspects, or the method performed by the second user plane network element in each of the aforementioned aspects, or the method performed by the session management network element in each of the aforementioned aspects. Exemplarily, the interface circuit is configured to receive a signal from a communication device other than the communication device and transmit it to the processor, or to send a signal from the processor to a communication device other than the communication device. The processor implements the method performed by the first user plane network element in each of the aforementioned aspects, or the method performed by the second user plane network element in each of the aforementioned aspects, or the method performed by the session management network element in each of the aforementioned aspects, through a logic circuit or by executing code instructions.

[0050] In a possible implementation, the communication device is a chip or a chip system.

[0051] In an eighth aspect, a communication device is provided, comprising a processor, and optionally, a memory; the processor and the memory are coupled; the memory is used to store computer programs or instructions; the processor is used to execute part or all of the computer programs or instructions in the memory, and when the part or all of the computer programs or instructions are executed, it is used to implement the function of the first user plane network element in the above-mentioned various aspects, or to implement the function of the second user plane network element in the above-mentioned various aspects, or to implement the function of the session management network element in the above-mentioned various aspects.

[0052] In one possible implementation, the apparatus may further include a transceiver configured to transmit a signal processed by the processor or receive a signal input to the processor. The transceiver may perform the transmitting action or receiving action performed by the first user plane network element in various aspects, or by the second user plane network element in various aspects, or by the session management network element in various aspects.

[0053] In one possible implementation, the processing unit in the fourth and fifth aspects can be implemented by the processor, the storage unit in the fourth and fifth aspects can be implemented by the memory, and the transceiver unit in the fourth and fifth aspects can be implemented by the transceiver.

[0054] In a possible implementation, the communication device is a chip or a chip system.

[0055] In a ninth aspect, a communication system is provided, comprising the first user plane network element of the first aspect and the session management network element of the second aspect; or comprising: the second user plane network element of the third aspect and the session management network element of the fourth aspect. For example, the first user plane network element, the second user plane network element, and the session management network element may be implemented by the communication apparatus described in the sixth aspect.

[0056] In a tenth aspect, a computer-readable storage medium is provided, wherein the computer-readable storage medium is used to store computer programs or instructions, which, when executed, enable the methods in the above-mentioned various aspects to be implemented.

[0057] In an eleventh aspect, a computer program product comprising instructions is provided, which enables the methods in the above aspects to be implemented when the computer program product is run on the computer. BRIEF DESCRIPTION OF THE DRAWINGS

[0058] FIG1a is a schematic diagram of the architecture of a communication system provided by the present application;

[0059] FIG1b is a schematic diagram of the architecture of another communication system provided by the present application;

[0060] FIG2 is a flow chart of an existing method for subscribing to UPF data;

[0061] Figures 3 to 14 are schematic flow charts of a communication method provided by the present application;

[0062] FIG15 is a structural diagram of a communication device provided by the present application;

[0063] FIG16 is a structural diagram of a communication device provided in this application. DETAILED DESCRIPTION

[0064] The technical solution of the present application can be applied to a terrestrial network (TN) or a non-terrestrial network (NTN), such as a satellite network. The technical solution of the present application can be applied to various wireless communication systems, and can be applied to, but not limited to, the fourth generation mobile communication technology (the 4th generation, 4G) system (also known as the long term evolution (LTE) system), the fifth generation mobile communication technology (the 5th generation, 5G) system (also known as the new radio (NR) system), or can also be applied to the next generation mobile communication system or other similar communication systems (such as the sixth generation mobile communication technology (the 6th generation, 6G) system), etc., without specific restrictions. In addition, the technical solution of the present application can be applied to device-to-device (D2D) scenarios, such as NR-D2D scenarios, etc., or can be applied to V2X scenarios, such as NR-V2X scenarios, etc. The technical solution of the present application can also be applied to fields such as intelligent driving, assisted driving, or intelligent connected vehicles, or factory manufacturing scenarios.

[0065] For example, Figure 1a is a schematic diagram of a 5G communication system architecture to which this application may be applied. Specifically, Figure 1a is a schematic diagram of a 5G network architecture based on a service-oriented architecture.

[0066] For example, Figure 1b is a schematic diagram of another 5G communication system architecture to which this application may be applied. Specifically, Figure 1b is a schematic diagram of a 5G architecture based on point-to-point communication. The main difference between Figure 1a and Figure 1b is that the interfaces between the network elements in Figure 1a are service-oriented interfaces, while the interfaces between the network elements in Figure 1b are point-to-point interfaces.

[0067] The 5G network architecture shown in Figures 1a and 1b includes terminal equipment, an access network, and a core network. Optionally, it also includes data network (DN) and application function (AF) network elements. Terminals access the core network through the access network, and the core network communicates with the DN or AF. The following briefly describes the functions of some of these network elements.

[0068] A terminal device (UE), also known as user equipment (UE), is a device with wireless transceiver capabilities that can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; on water (such as ships); or in the air (such as airplanes, balloons, and satellites). The terminal device can be a mobile phone, tablet computer, computer with wireless transceiver capabilities, virtual reality (VR) terminal, augmented reality (AR) terminal, wireless terminal in industrial control, wireless terminal in self-driving, wireless terminal in remote medical, wireless terminal in smart grid, wireless terminal in transportation safety, wireless terminal in smart city, wireless terminal in smart home, etc.

[0069] The (R)AN device in this application is a device that provides wireless communication functions for terminal devices. The (R)AN device is also called an access network device. The RAN equipment in this application includes but is not limited to: the next generation base station (g nodeB, gNB) in 5G, evolved node B (evolved node B, eNB), radio network controller (radio network controller, RNC), node B (node ​​B, NB), base station controller (base station controller, BSC), base transceiver station (base transceiver station, BTS), home base station (for example, home evolved nodeB, or home node B, HNB), baseband unit (baseBand unit, BBU), transmission point (transmitting and receiving point, TRP), transmission point (transmitting point, TP), mobile switching center, etc. In systems using different wireless access technologies, the names of devices with base station functions may vary. For example, in the fifth generation (5G) system, it is called RAN or gNB (5G NodeB); in the LTE system, it is called evolved NodeB (eNB or eNodeB); in the third generation (3G) system, it is called Node B, etc.

[0070] A data network (DN) can deploy a variety of services, providing data and / or voice services to terminal devices. For example, a DN is the private network of a smart factory. Sensors installed in the workshop can be terminal devices. The DN contains sensors and a control server, which provides services to the sensors. Sensors can communicate with the control server, receive instructions from the control server, and transmit collected sensor data to the control server according to the instructions. Another example is a DN that is a company's internal office network. Employees' mobile phones or computers can be terminal devices, allowing them to access information and data resources on the company's internal office network.

[0071] The application network element mainly supports interaction with the 3rd Generation Partnership Project (3GPP) core network to provide services, such as influencing data routing decisions, policy control functions, or providing some third-party services to the network side. In the 5G communication system, the application network element can be an application function (AF) network element. In future communication systems, the application network element can still be an AF network element, or it can have other names, which are not limited in this application.

[0072] The core network may include one or more of the following network elements:

[0073] The access management network element (also known as the mobility management network element) is a control plane network element provided by the operator network, responsible for access control and mobility management of terminal devices accessing the operator network, such as mobile state management, allocation of user temporary identity, authentication and user functions. In the 5G communication system, the access management network element can be an access and mobility management function (AMF) network element. In future communication systems, the access management network element can still be an AMF network element, or it can have other names, which are not limited in this application.

[0074] The session management network element is primarily responsible for session management in mobile networks, such as session establishment, modification, and release. Specific functions include allocating IP addresses to users and selecting user plane network elements that provide message forwarding functions. In 5G communication systems, this session management network element may be a session management function (SMF) network element. In future communication systems, the session management network element may still be an SMF network element, or it may have other names, which are not limited in this application.

[0075] The user plane network element is responsible for forwarding and receiving user data in the terminal device. It can receive user data from the data network and transmit it to the terminal device through the access network device; the user plane network element can also receive user data from the terminal device through the access network device and forward it to the data network. The transmission resources and scheduling functions that provide services to the terminal device in the user plane network element are managed and controlled by the SMF network element. In the 5G communication system, the user plane network element can be a user plane function (UPF) network element. In future communication systems, the user plane network element can still be a UPF network element, or it can have other names, which are not limited in this application.

[0076] The data management network element is used for generating authentication credentials, user identification processing (such as storing and managing user permanent identities), access control, and contract data management. In a 5G communication system, this data management network element can be a unified data management (UDM) network element. In future communication systems, the unified data management can still be a UDM network element, or it can have other names, which are not limited in this application.

[0077] The policy control network element mainly supports providing a unified policy framework to control network behavior, provides policy rules to the control layer network function, and is responsible for obtaining user subscription information related to policy decisions. In the 4G communication system, the policy control network element can be a policy and charging rules function (PCRF) network element. In the 5G communication system, the policy control network element can be a policy control function (PCF) network element. In future communication systems, the policy control network element can still be a PCF network element, or it can have other names, which are not limited in this application.

[0078] The data storage network element is responsible for storing structured data information, including contract information, policy information, and network data or service data defined in a standard format. In a 5G communication system, the data storage network element can be a unified data repository (UDR). In future communication systems, the network open function network element can still be a UDR network element, or it can have other names, which are not limited in this application.

[0079] The network storage network element can be used to provide network element discovery function and provide network element information corresponding to the network element type based on the request of other network elements. NRF also provides network element management services, such as network element registration, update, deregistration, and network element status subscription and push. In the 5G communication system, the network storage network element can be a network repository function (NRF) network element. In future communication systems, the network storage network element can still be an NRF network element, or it can have other names, which are not limited in this application.

[0080] A network exposure function element can be used to securely expose services and capabilities provided by 3GPP network function devices to the outside world. In a 5G communication system, the network exposure function element can be a network exposure function (NEF) element. In future communication systems, the network exposure function element can still be an NEF element, or it can have other names, which are not limited in this application.

[0081] The network slice selection network element can be used to select the appropriate network slice for the service. In the 5G communication system, the network slice selection network element can be a network slice selection function (NSSF) network element. In future communication systems, the network open function network element can still be an NSSF network element, or it can have other names, which are not limited in this application.

[0082] The network data analysis network element can collect data from various network functions (NFs), such as policy control network elements, session management network elements, user plane network elements, access management network elements, and application function network elements (through network capability exposure function network elements), and perform analysis and prediction. In a 5G communication system, the network data analysis network element can be a network data analysis function (NWDAF). In future communication systems, the network data analysis network element can still be an NWDAF network element, or it can have other names, which are not limited in this application.

[0083] It is understood that the above-mentioned network element or function can be a network element in a hardware device, a software function running on dedicated hardware, or a virtualized function instantiated on a platform (e.g., a cloud platform). In one possible implementation, the above-mentioned network element or function can be implemented by a single device, or can be implemented by multiple devices together, or can be a functional module within a single device, which is not specifically limited in the embodiments of the present application.

[0084] As shown in FIG2 , a flowchart of a method for subscribing to UPF data is introduced, including the following steps:

[0085] Step 201: The UPF event consumer (eg, NWDAF) obtains the SMF from the UDM. For example, the UPF event consumer calls the Nudm_UECM_Get service operation and retrieves the appropriate SMF by providing UE ID, DNN, S-NSSAI, and NF type=SMF.

[0086] Step 202: The UDM returns the SMF information, for example, returning a Nudm_UECM_Get response and the corresponding SMF information.

[0087] Step 203: The UPF event consumer sends a subscription message to the SMF to subscribe to the data in the UPF. For example, the UPF event consumer sends a subscription message to the SMF by calling the Nsmf_EventExposure_Subscribe service operation.

[0088] Step 204: SMF selects UPF and sends a subscription message to UPF. For example, SMF should send a subscription message to UPF through N4 session modification of PFCP, or send a subscription message to UPF by calling Nupf_EventExposure service operation.

[0089] Step 205: The UPF feeds back corresponding data to the UPF event consumer. For example, the UPF sends the locally collected UPF data to the UPF event consumer by calling the Nupf_EventExposure_Notify service operation.

[0090] In response to the situation where the subscribed user-plane network element can no longer provide subscription data to consumers, this application proposes multiple data processing methods.

[0091] Below, some terms or concepts in the embodiments of the present application are explained to facilitate understanding by those skilled in the art.

[0092] 1) The consumers of this application may be NWDAF, PCF, NEF, AF, etc.

[0093] 2) When a consumer sends a subscription message to a session management network element, a possible example is: the consumer sends a subscription message to the session management network element by calling the Nsmf_eventExposure_Subscribe service operation. The subscription message is used to indicate subscription to a certain event.

[0094] When a consumer sends a subscription update message to a session management network element, a possible example is that the consumer sends a subscription update message to the session management network element by calling the Nsmf_eventExposure_Subscribe service operation. The subscription update message is used to indicate that a subscription to a certain event is updated.

[0095] When a consumer sends an unsubscribe message to a session management network element, a possible example is that the consumer sends an unsubscribe message to the session management network element by calling the Nsmf_eventExposure_UnSubscribe service operation. The unsubscribe message is used to indicate the cancellation of a subscription to an event.

[0096] When the session management network element sends a subscription message to the user plane network element (eg, the first user plane network element or the second user plane network element), a possible example is that the session management network element sends the subscription message to the user plane network element by calling the Nupf_EventExposure_Subscribe service operation.

[0097] When the session management network element sends a subscription update message to the user plane network element (eg, the first user plane network element or the second user plane network element), a possible example is that the session management network element sends the subscription update message to the user plane network element by calling the Nupf_EventExposure_Subscribe service operation.

[0098] When the session management network element sends an unsubscribe message to the user plane network element (eg, the first user plane network element or the second user plane network element), a possible example is that the session management network element sends the unsubscribe message to the user plane network element by calling the Nupf_EventExposure_UnSubscribe service operation.

[0099] When the session management network element sends a notification (which may be replaced by a notification message) to the consumer or user-plane network element, one possible example is: the session management network element sends a notification to the consumer or user-plane network element by calling the Nsmf_EventExposure_Notify service operation. The notification may include event-related data and other parameters.

[0100] When a user-plane network element sends a notification (which may be replaced by a notification message) to a consumer, a session management network element, or another user-plane network element, one possible example is: the user-plane network element sends a notification to the consumer, the session management network element, or another user-plane network element by calling the Nupf_EventExposure_Notify service operation. The notification may include event-related data and other parameters.

[0101] In order to better describe the embodiments of the present application, the following describes the methods provided by the embodiments of the present application in conjunction with the accompanying drawings. Unless otherwise specified, the steps indicated by dotted lines in the accompanying drawings corresponding to the various embodiments of the present application are all optional steps.

[0102] FIG3 is a schematic diagram of a communication process provided in an embodiment of the present application, including the following steps:

[0103] Step 301: A session management network element sends a first message to a first user plane network element. Correspondingly, the first user plane network element receives the first message from the session management network element.

[0104] The first message is used to instruct cancellation of subscription to a first event.

[0105] The first message includes first information, and the first information is used to indicate a first processing method of the first user-plane network element for the data associated with the first event; the first processing method is: after receiving the first information (which can also be replaced by when the subscription to the first event is terminated and / or the session associated with the first event is released), sending the data associated with the first event, or sending the data associated with the first event according to the event report information and / or report suggestion information from the consumer (for example, specifically when the subscription to the first event is terminated and / or the session associated with the first event is released, sending the data associated with the first event according to the event report information and / or report suggestion information from the consumer).

[0106] The first event can be represented by an event ID, for example. The event reporting information (event reporting information) is sent by the consumer to the session management network element during the subscription process for the first event before step 301, and then sent by the session management network element to the first user plane network element. The event reporting information is used to indicate a reporting method for data associated with the first event. For example, the reporting method includes but is not limited to: periodic reporting, reporting upon reaching a threshold, reporting within a specific time, reporting a specific number of times, etc. In one possible example, the event reporting information includes an event reporting mode, which is used to indicate a reporting method for data associated with the first event. In current technology, event reporting information and / or reporting suggestion information from the consumer is used to report data during the subscription process, and is not used to report data after the subscription is terminated. However, in an embodiment of the present application, after the subscription is terminated, data that has been collected by the first user plane network element but has not yet been reported can also be reported based on the event reporting information.

[0107] Optionally, a condition for unsubscribing from a first event is configured in the session management network element. When the session management network element determines that the first condition is met, it triggers the sending of a first message to the first user plane network element. The first condition is redirecting the first user plane network element to another user plane network element other than the first user plane network element, or the first condition is unsubscribing from the first event. Alternatively, the consumer may notify the session management network element to unsubscribe from the first event.

[0108] Step 302: The first user plane network element sends data associated with the first event based on the first processing method.

[0109] The first processing method introduced above refers to sending the data associated with the first event. Another possible processing method is to discard or not report (not reporting and not sending in this application are interchangeable) the first data associated with the first event.

[0110] The data sent in step 302 refers to data associated with the first event that has been collected by the first user-plane network element and has not yet been reported. In all embodiments of the present application, the first user-plane network element discards, does not send, or sends data associated with the first event, which refers to discarding, not sending, or sending data associated with the first event that has been collected and has not yet been reported.

[0111] In the prior art, upon receiving a subscription cancellation message, a user-plane network element will, by default, discard the relevant data and not send it to the consumer. However, in this embodiment, the subscription cancellation message carries an instruction to instruct the user-plane network element on how to send the relevant data. This means that after a subscription is cancelled, the user-plane network element can process the data that has been collected but not yet reported according to the instruction. For example, the user-plane network element can send the data to the consumer based on the instruction. This avoids the resource waste caused by always discarding the collected data.

[0112] After step 302, the first user plane network element may also inform the session management network element that the data has been processed. For example, the first user plane network element sends fourth information to the session management network element. Accordingly, the session management network element receives fourth information from the first user plane network element. The fourth information is used to indicate that the first user plane network element has sent the data associated with the first event subscribed by the consumer to the consumer, or that the first user plane network element has discarded the data associated with the first event.

[0113] In one possible implementation, the consumer may inform the session management network element of a processing method for data associated with the first event (hereinafter referred to as the second processing method for ease of distinction). Exemplarily, the consumer sends fifth information to the session management network element, and the session management network element accordingly receives the fifth information from the consumer, where the fifth information is used to indicate the second processing method for the data associated with the first event when a first condition is met; the first condition is redirecting the user plane network element, or the first condition is unsubscribing from the first event, or the first event is associated with a PDU session, and the first condition is releasing the PDU session.

[0114] The second processing method is to immediately send the relevant data, send the relevant data, send the relevant data based on the event report information and / or report suggestion information from the consumer, discard the relevant data, not report the relevant data, or send the relevant data when a preset condition is met. The preset condition can be a condition corresponding to the event report information or a new condition different from the event report information.

[0115] When the first condition is to redirect the user plane network element, this processing method is not targeted at a certain user plane network element or a certain event, but only targeted at the condition of redirecting the user plane network element.

[0116] When the first condition is to cancel the subscription to the first event, the processing method is not for a certain user-side network element, but for the condition of canceling the subscription to the first event. At this time, the second processing method is described in another way: the second processing method includes: immediately sending (or sending) the data associated with the first event, or sending the data associated with the first event according to the event report information and / or report suggestion information from the consumer (the event report information is used to indicate the reporting method of the data associated with the first event), or discarding the data associated with the first event, or not reporting the data associated with the first event.

[0117] The first processing mode sent by the session management network element to the first user plane network element in step 301 is related to the second processing mode obtained by the session management network element from the consumer. For example, the second processing mode indicates discarding the relevant data, and the first processing mode also indicates discarding the data associated with the first event; for another example, the second processing mode indicates sending the data associated with the first event immediately, and the first processing mode indicates sending the data associated with the first event after receiving the message indicating the cancellation of subscription to the first event. Of course, there may also be a situation where the first processing mode is unrelated to the second processing mode. For example, the second processing mode indicates sending (or sending) the relevant data immediately, and the first processing mode indicates sending the data associated with the first event based on the event report information and / or report suggestion information from the consumer. The fifth information can be carried in the subscription message (Nsmf_EventExposure_Subscribe) sent by the consumer to the session management network element, and of course it can also be carried in other messages different from the subscription message.

[0118] After step 301 (i.e., cancelling the subscription to the first event), the consumer may be informed of the cancellation of the subscription to the first event so that the consumer can determine whether to continue with the new subscription based on their own circumstances. This notification may be made by the session management network element or by the first user plane network element, as described below:

[0119] Example 1: The first user-plane network element notifies the consumer that the subscription to the first event has been terminated.

[0120] Exemplarily, the first user-plane network element sends second information to the consumer, and the consumer receives the second information accordingly; the second information is used to indicate that the consumer's subscription to the first event has been terminated. Optionally, the second information is further used to indicate a reason for the subscription termination, such as UPF relocation.

[0121] Optionally, after sending the second information to the consumer, the first user-plane network element may also notify the session management network element of the situation. Exemplarily, the first user-plane network element sends third information to the session management network element, and the session management network element receives the third information in response; the third information is used to indicate that the first user-plane network element has notified the consumer that the consumer's subscription to the first event has been terminated.

[0122] Exemplarily, before the session management network element subscribes to the first event from the first user plane network element, the consumer sends a subscription message a (the a here is only for the convenience of description and does not limit the subscription message) to the session management network element to subscribe to the first event; the session management network element sends the subscription message a to the first user plane network element; the first user plane network element notifies the consumer that the consumer's subscription to the first event has been terminated. One possible implementation method is: the first user plane network element indicates to the consumer: the subscription to the subscription message a has been terminated. This implementation method can be applied to all embodiments of the present application: the first user plane network element indicates to the consumer that the subscription to the first event has been terminated.

[0123] Example 2: The session management network element informs the consumer that the subscription to the first event has been terminated.

[0124] Exemplarily, the session management network element sends sixth information to the consumer, and the consumer receives the sixth information accordingly; the sixth information is used to indicate that the consumer's subscription to the first event has been terminated. Optionally, the sixth information is used to indicate a reason for the subscription termination, such as UPF relocation.

[0125] Optionally, after sending the sixth information to the consumer, the session management network element may also inform the first user plane network element of the situation. Exemplarily, the session management network element sends an indication message to the first user plane network element, indicating that the session management plane network element has notified the consumer that the consumer's subscription to the first event has been terminated.

[0126] Exemplarily, before the session management network element subscribes to the first event from the first user-side network element, the consumer sends a subscription message a (the a here is only for the convenience of description and does not limit the subscription message) to the session management network element to subscribe to the first event; the session management network element notifies the consumer that the consumer's subscription to the first event has been terminated. One possible implementation method is: the session management network element indicates to the consumer: the subscription to the subscription message a has been terminated. This implementation method can be applied to all embodiments of the present application: the session management network element indicates to the consumer that the subscription to the first event has been terminated.

[0127] In conjunction with FIG3 and the relevant content of Example 1 (the first user-side network element notifies the consumer that the subscription to the first event has been terminated), as shown in FIG4, a flow chart of a communication method is introduced, comprising the following steps:

[0128] Step 401: The consumer sends a subscription message to the session management network element. In response, the session management network element receives the subscription message, which is used to indicate subscription to a first event. For example, the consumer sends the subscription message to the session management network element by calling the Nsmf_eventExposure_Subscribe service operation.

[0129] Subscription messages can include one or more of the following:

[0130] Event reporting information, where the event reporting information is used to indicate a reporting method for data associated with the first event. For example, the reporting method includes, but is not limited to, periodic reporting, reporting upon reaching a threshold, reporting within a specific time period, reporting a specific number of times, etc. In one possible example, the event reporting information includes an event reporting mode, where the event reporting mode is used to indicate a reporting method for data associated with the first event.

[0131] Notification target address (i.e., the address of the UPF event consumer) and notification association information. The consumer will carry the notification association identifier in the subscription message. Subsequently, the session management network element or the first user plane network element will also carry the notification association information in the notification message sent to the consumer, which is used by the consumer to associate the subscription message with the notification message.

[0132] UPF event open service indication and the target UPF event ID to subscribe to. For example, event ID = quality of service (QoS) monitoring means subscribing to QoS monitoring related information, such as uplink packet delay, downlink packet delay, etc.

[0133] Event Filter Information: such as S-NSSAI, DNN, DNAI, UPF Id, flow description of the target data flow (e.g., application Id), AoI, SSID / BSSID, etc.

[0134] Target of event reporting: i.e. UE identity. This can be the identity of a single UE (e.g. subscription permanent identity (SUPI)), the identity of a UE group, or any UE.

[0135] Reporting suggestion information. Reporting suggestion information includes report urgency and reporting time information. Report urgency is used to indicate whether the event can be reported late, and reporting time information is used to indicate the deadline for event reporting. For example, if report urgency indicates that the event can be reported late and reporting time information is set to 100s, this means that the UPF needs to report data related to the event within 100s after detecting the requested event trigger.

[0136] Target Subscription information: such as measurement type and granularity of requested information.

[0137] Relocation reporting indication or reporting indication (corresponding to the fifth information described above, it should be noted that relocation reporting indication or reporting indication is only a name for the indication information. The function of the indication information is to indicate a second processing method for the data associated with the first event when the first condition is met. The name of the indication information can also be replaced with other names without affecting the function of the indication information). The relocation reporting indication or reporting indication is used to indicate a second processing method for the data associated with the first event when the first condition is met. The second processing method includes: sending the relevant data immediately, sending the relevant data, sending the relevant data according to the event report information and / or report suggestion information from the consumer, discarding the relevant data, not reporting the relevant data, or sending the relevant data when a preset condition is met. The preset condition can refer to the condition corresponding to the event report information, or it can refer to a new condition different from the event report information. The event report information is used to indicate the reporting method of the data associated with the first event, or discarding the data associated with the first event. The event report information is used to indicate the reporting method of the data associated with the first event. For example, the reporting method includes but is not limited to: periodic reporting, reporting when a threshold is reached, reporting within a specific time, reporting a specific number of times, etc. In a possible example, the event report information includes an event reporting mode (event reporting mode), where the event reporting mode is used to indicate a reporting method for data associated with the first event.

[0138] Step 402: The session management network element sends a subscription message to the first user plane network element. In response, the first user plane network element receives the subscription message, which is used to indicate subscription to the first event. For example, the session management network element sends the subscription message to the first user plane network element by calling the Nupf_EventExposure_Subscribe service operation.

[0139] The parameters included in the subscription message of step 402 are derived from the parameters included in the subscription message of step 401 and will not be described in detail here.

[0140] Step 403: The first user plane network element sends a notification to the consumer. Correspondingly, the consumer receives the notification from the first user plane network element; the notification includes data associated with the first event.

[0141] For example, the first user plane network element sends a notification to the consumer by calling the Nupf_EventExposure_Notify service operation.

[0142] Optionally, the first user plane network element may send data associated with the first event according to the reporting suggestion information and / or event report information in step 402.

[0143] The first user-plane network element can send the notification to the consumer directly or indirectly through the session management network element. For example, if the session management network element indicates the notification target address to the first user-plane network element in step 402, and the notification target address is the consumer's address, the first user-plane network element can send the notification to the consumer directly; if the session management network element does not indicate the notification target address in step 402, or the session management network element indicates the notification target address, and the notification target address is the address of the session management network element, the first user-plane network element sends the notification to the session management network element, and the session management network element then sends the notification to the consumer. For example, the first user-plane network element sends the notification to the session management network element by calling the Nupf_EventExposure_Notify service operation or through the N4 session modification message, and the session management network element then sends the notification to the consumer through the Nsmf_EventExposure_Notify service operation. In the embodiments of the present application, the steps involving the user-plane network element (e.g., the first user-plane network element, the second user-plane network element, etc.) directly sending the notification to the consumer can all be applied to the method of indirect notification through the session management network element.

[0144] It is understandable that step 403 is the reporting of data during the subscription process. If no data is generated, step 403 does not need to be executed.

[0145] Step 404: The session management network element determines that the first condition is met.

[0146] For example, the first condition is a trigger condition for user plane network element redirection, or canceling subscription to the first event.

[0147] The triggering conditions for user plane network element redirection include but are not limited to one or more of the following:

[0148] UE mobility: The session management network element determines that the UE moves out of the service area of ​​the first user plane network element. This situation is applicable to the scenario where the first event is associated with the UE.

[0149] Load balancing: The session management network element determines that the load on the first user plane network element is too high and selects a new user plane network element to provide services for the current business.

[0150] Service experience change: Based on the consumer's service experience analysis, the session management network element determines that the current user plane path (UP path) cannot meet the service experience requirements and determines to select a new user plane network element.

[0151] Steps 401 to 404 are applicable in all subsequent embodiments.

[0152] Step 405: The session management network element sends a cancel subscription message to the first user plane network element. Correspondingly, the first user plane network element receives the cancel subscription message from the session management network element; the cancel subscription message is used to indicate the cancellation of subscription to the first event.

[0153] For example, the session management network element sends an unsubscribe message to the first user plane network element by calling the Nupf_EventExposure_UnSubscribe service operation.

[0154] The unsubscribe message includes a last notification indication (corresponding to the first information in step 301. It should be noted that the last notification indication is only a name of the indication information. The function of the indication information is to indicate the first processing mode of the first user-plane network element for the data associated with the first event. The name of the indication information can also be replaced with other names without affecting the function of the indication information). The last notification indication is used to indicate the first processing mode of the first user-plane network element for the data associated with the first event. The first processing mode is: sending the data associated with the first event after receiving the first information, or sending the data associated with the first event based on the event report information and / or report suggestion information from the consumer, or discarding the data associated with the first event, or not reporting the data associated with the first event. The event reporting information is used to indicate the reporting mode of the data associated with the first event. For example, the reporting mode includes but is not limited to periodic reporting, reporting when a threshold is reached, reporting within a specific time, reporting a specific number of times, etc. In one possible example, the event reporting information includes an event reporting mode, and the event reporting mode is used to indicate the reporting mode of the data associated with the first event. Alternatively, the first processing method is: sending the data associated with the first event when the subscription to the first event is canceled and / or the session associated with the first event is released, or sending the data associated with the first event based on the event report information and / or report suggestion information from the consumer when the subscription to the first event is canceled and / or the session associated with the first event is released, and the event report information is used to indicate the reporting method of the data associated with the first event.

[0155] In one possible implementation, the last notification indication in step 405 may also be the relocation reporting indication or reporting indication carried by the consumer when subscribing (step 401), that is, the SMF may only forward the relocation reporting indication or reporting indication brought by the consumer in the subscription.

[0156] In a possible example, the last notification indication is an optional parameter. The session management network element can explicitly indicate the parameter in the unsubscribe message. If the session management network element does not indicate the parameter, the first user plane network element can independently determine how to handle the data associated with the first event, such as discarding the data associated with the first event, or not reporting the data associated with the first event, or sending the data associated with the first event after receiving the unsubscribe message, or sending the data associated with the first event based on the event report information and / or report suggestion information from the consumer, etc.

[0157] In one possible implementation, in step 401, the consumer sends a relocation reporting indication to the session management network element. The specific content of the last notification indication in step 405 may be related to the specific content of the relocation reporting indication in step 401. The association between the first information (last notification indication) and the fifth information (relocation reporting indication) has been introduced above and will not be repeated here. If step 401 does not carry a relocation reporting indication, the session management network element may determine the specific content of the last notification indication in step 405 based on internal logic. The internal logic of the session management network element includes but is not limited to the following:

[0158] For example, the session management network element determines whether it needs to obtain data already collected by the first user plane network element from the first user plane network element. For example, a consumer specifies immediate reporting upon event triggering (which can be indicated by event report information), provided that data is forwarded by the session management network element. When UPF relocation is triggered, the session management network element has not received any data from the first user plane network element, indicating that the event has not yet been triggered and the first user plane network element has not yet started collecting data. Therefore, the session management network element determines that it does not need to obtain data from the first user plane network element and directly cancels the subscription with the first user plane network element. For another example, if the consumer specifies periodic reporting, when UPF relocation is triggered, the session management network element has already received data from the first user plane network element several times, and the next notification time has not yet arrived, indicating that the first user plane network element may have already collected some data within the period. Therefore, the session management network element may determine that it is necessary to request the first user plane network element for the previously collected data during UPF relocation. In this case, the session management network element needs to instruct the first user plane network element to send the previously collected data to the session management network element / consumer.

[0159] Furthermore, the session management network element can determine the target address (e.g., the session management network element or the consumer) for subsequent subscriptions to the second user plane network element based on whether the first user plane network element has data (or, in other words, based on whether it is necessary to obtain data already collected by the first user plane network element from the first user plane network element). For example, if the first user plane network element has data, the target address for notification is the session management network element (e.g., the session management network element needs to perform data aggregation); otherwise, the target address for notification is the consumer. Note that this is merely an example; in practice, if the first user plane network element has data, the target address for notification can also be the consumer.

[0160] For another example, the session management network element determines how to process the data already collected by the first user-plane network element. For example, if the session management network element determines that the ratio of the duration of data collection to the set total duration (the set total duration refers to the duration for which data collection is required) is greater than a set threshold, the collected data needs to be reported. If it is less than or equal to the set threshold, the collected data can be discarded. For example, if a consumer subscribes to a QoS monitoring event within an hour, for example, the average bitrate within an hour, and the session management network element determines that the first user-plane network element has collected data for half an hour, in this case, the collected data needs to be retained, and the data from the second user-plane network element for the next half hour needs to be aggregated to calculate the average bitrate within an hour. At this time, the session management network element needs to instruct the first user-plane network element to send the collected data (either to the session management network element or to the second user-plane network element), and the session management network element or the second user-plane network element will further perform data aggregation. For another example, if a subscription to UserDataUsageMeasures requests a user traffic usage report for three days, and the session management element determines that the first user plane network element has only collected one hour of data, discarding the first user plane network element's data is acceptable. Therefore, the session management element can instruct the first user plane network element to discard the collected data, or instruct the first user plane network element not to report the collected data, or the session management element does not send any special instructions to the first user plane network element. By default, the first user plane network element does not need to send the collected data to the session management element / consumer. For another example, the session management element determines whether the time period during which the data was collected is a critical time period. If so, the data cannot be discarded; if not, the data can be discarded.

[0161] Step 406: The first user-plane network element processes the data associated with the first event (that is, the collected but unsent data), for example, sends, does not send, or discards the data associated with the first event.

[0162] If the session management network element sends a last notification indication to the first user plane network element in step 405, the first user plane network element may process the data associated with the first event (i.e., data that has been collected but not sent) based on the last notification indication. If the last notification indication is not included in step 405, the first user plane network element may independently determine how to handle the data associated with the first event, such as discarding or not reporting the data associated with the first event, sending the data associated with the first event after receiving a subscription cancellation message, or sending the data associated with the first event based on the event report information and / or report suggestion information from the consumer. If the handling method is to send the data associated with the first event, the first UPF may send the data associated with the first event to the session management network element or the consumer.

[0163] After step 405, execute step 407: the first user plane network element sends a notification to the consumer, and accordingly, the consumer receives the notification from the first user plane network element; the notification includes a subscription termination indication (corresponding to the second information in the previous example 1), and the subscription termination indication is used to indicate that the consumer's subscription to the first event has been terminated.

[0164] For example, the first user plane network element sends a notification to the consumer by calling the Nupf_EventExposure_Notify service operation.

[0165] Optionally, the notification also includes: a cause code associated with the subscription termination indication, where the cause code is used to indicate the reason for subscription termination, such as UPF relocation.

[0166] Optionally, the notification also includes: data associated with the first event (referring to data that has been collected but not sent). The first user plane network element may determine whether and when to send the data associated with the first event to the consumer based on the last notification indication from the session management network element or the internal logic of the first user plane network element. This data may be in the same notification as the subscription termination indication or in a different notification.

[0167] Optionally, the unsubscribe message in step 405 also includes an indication information, which is used to instruct the first user plane network element to send a subscription termination indication and an optional cause code to the consumer. In this case, the first user plane network element sends a subscription termination indication and an optional cause code to the consumer based on the indication information.

[0168] There is no restriction on the order of steps 406 and 407. For example, if the data associated with the first event does not need to be sent in step 405, then the order of steps 406 and 407 can be unrestricted; if the data associated with the first event needs to be sent in step 405, then steps 405 and 407 can be carried in the same notification message and before step 406; if the data associated with the first event needs to be sent in step 405, then steps 405 and 407 can also be carried in different notification messages. If they are in different notification messages, there is no restriction on the order of steps 406 and 407.

[0169] Optionally, step 408: the first user plane network element sends a notification to the session management network element, and accordingly, the session management network element receives the notification from the first user plane network element, which includes indication information, and the indication information (corresponding to the third information in the previous example 1) is used to indicate that the first user plane network element has notified the consumer that the consumer's subscription to the first event has been terminated.

[0170] Optionally, after step 406, execute step 409: the first user plane network element sends a notification to the session management network element, and accordingly, the session management network element receives the notification from the first user plane network element, which includes indication information, and the indication information is used to indicate that the first user plane network element has processed the data associated with the first event.

[0171] For example, the indication information is specifically used to indicate that the first user-plane network element has sent the data associated with the first event subscribed by the consumer to the consumer, or that the first user-plane network element has discarded the data associated with the first event. Step 409 is optional. If the first user-plane network element first sends the data associated with the first event to the session management network element, there is no need to send the indication information to the session management network element.

[0172] Step 408 and step 409 may be in the same notification message or in different notification messages. If they are in different notification messages, the order of step 408 and step 409 is not limited.

[0173] Optionally, step 410: the consumer sends a cancel subscription message to the session management network element to indicate the cancellation of subscription to the first event.

[0174] Optionally, step 411a: the consumer may send a subscription update message to the session management network element.

[0175] Optionally, step 411b: the session management network element sends a subscription message to the second user plane network element.

[0176] Optionally, step 411c: the second user plane network element sends a notification message to the consumer to notify the collected data.

[0177] After receiving an indication that the subscription to the first event has been terminated, the consumer can determine whether to continue the subscription based on its own circumstances, for example, whether the collected information is sufficient. If the consumer determines that the current subscription is no longer needed, the consumer sends a cancel subscription message to the session management network element to indicate the cancellation of the subscription to the first event (i.e., step 410). If the consumer needs to update the current subscription, the consumer can send a subscription update message to the session management network element. The subscription update message includes the identifier of the first event and may also include updated subscription parameters, such as event filter information, event report targets, report suggestion information, etc. After receiving the subscription update message, the session management network element selects a new second user plane network element and sends a subscription message (based on the subscription update message) to the second user plane network element. The second user plane network element sends a notification message to the consumer network element to notify the collected data (i.e., steps 411a-411c).

[0178] In conjunction with FIG. 3 and the relevant content of Example 2 (the session management network element notifies the consumer that the subscription to the first event has been terminated), as shown in FIG. 5 , a flow chart of a communication method is further introduced, including the following steps:

[0179] Step 501: The session management network element determines that a first condition is met, for example, the first condition is user plane network element redirection, or unsubscribing from a first event.

[0180] Step 502: The session management network element sends a cancel subscription message to the first user plane network element. Correspondingly, the first user plane network element receives the cancel subscription message from the session management network element; the cancel subscription message is used to indicate the cancellation of subscription to the first event, and the cancel subscription message includes a last notification indication, which is used to indicate the first processing method of the first user plane network element for the data associated with the first event.

[0181] Step 503: The first user-plane network element processes the data associated with the first event (that is, the collected but unsent data), for example, discards or does not report the data associated with the first event, or sends the data associated with the first event to the consumer (see step 503a).

[0182] Steps 501 to 503 may refer to steps 404 to 406 and will not be described in detail. Steps that may be performed before step 501 may refer to steps 401 to 403 and will not be described in detail.

[0183] Optionally, step 504: the first user plane network element sends a notification to the session management network element. Correspondingly, the session management network element receives the notification from the first user plane network element, where the notification includes indication information, and the indication information is used to indicate that the first user plane network element has processed the data associated with the first event.

[0184] For example, the indication information is specifically used to indicate that the first user-plane network element has sent the data associated with the first event subscribed by the consumer to the consumer, or that the first user-plane network element has discarded the data associated with the first event. This step 504 is optional. If the first user-plane network element first sends the data associated with the first event to the session management network element, there is no need to send the indication information to the session management network element.

[0185] After step 502, step 505 is executed: the session management network element sends a notification to the consumer. In response, the consumer receives the notification from the session management network element; the notification includes a subscription termination indication, which is used to indicate that the consumer's subscription to the first event has been terminated.

[0186] Optionally, the notification also includes: a cause code associated with the subscription termination indication, where the cause code is used to indicate the reason for subscription termination, such as UPF relocation.

[0187] The order of step 505 and step 504 is not limited.

[0188] Optionally, step 506: the session management network element sends a notification to the first user plane network element, and accordingly, the first user plane network element receives the notification from the session management network element, where the notification includes indication information, and the indication information is used to indicate that the session management network element has notified the consumer that the consumer's subscription to the first event has been terminated.

[0189] The above-mentioned Figures 3, 4, and 5 describe the carrying of first information / last notification indication in the unsubscribe message. The first information / last notification indication is used to indicate the first processing method of the first user-plane network element for the data associated with the first event (see step 301 in Figure 3, step 405 in Figure 4, and step 502 in Figure 5). In another possible implementation, as shown in Figures 6 and 7, the last notification indication can be carried in the subscription update message. After the subscription update message, the session management network element sends an unsubscribe message to the first user-plane network element. In Figure 6, the first user-plane network element notifies the consumer that the subscription to the first event has been terminated (see step 606), and in Figure 7, the session management network element notifies the consumer that the subscription to the first event has been terminated (see step 706).

[0190] FIG6 shows a flow chart of a possible communication method, including the following steps:

[0191] Step 601: The session management network element determines that a first condition is met, for example, the first condition is user plane network element redirection, or unsubscribing from a first event.

[0192] Step 601 may refer to step 404 and will not be described in detail. Steps that may be performed before step 601 may refer to steps 401 to 403 and will not be described in detail.

[0193] Step 602: The session management network element sends a subscription update message to the first user plane network element. Correspondingly, the first user plane network element receives the subscription update message, where the subscription update message is used to indicate a subscription update for the first event and includes a last notification indication.

[0194] The subscription update message carries a subscription correlation identifier (Subscription Correlation ID). The Subscription Correlation ID is a parameter sent by the first user plane network element to the session management network element after the session management network element sends the subscription message to the first user plane network element. If the subscription is successful, the session management network element includes the parameter in the subscription update message, which is used by the first user plane network element to associate the subscription update message with the previous subscription message.

[0195] Step 603: The first user plane network element processes the data associated with the first event (that is, the data that has been collected but not sent out) based on the last notification indication.

[0196] For example, the data associated with the first event is discarded or not reported, or the data associated with the first event is sent to the consumer (see step 603a).

[0197] Step 604: The first user plane network element sends a notification to the session management network element. Correspondingly, the session management network element receives the notification from the first user plane network element. The notification includes indication information, which is used to indicate that the first user plane network element has processed the data associated with the first event.

[0198] For example, the indication information is specifically used to indicate that the first user-plane network element has sent the data associated with the first event subscribed by the consumer to the consumer, or that the first user-plane network element has discarded the data associated with the first event. Step 604 is optional. If the first user-plane network element first sends the data associated with the first event to the session management network element, there is no need to send the indication information to the session management network element.

[0199] Step 605: The session management network element sends a cancel subscription message to the first user plane network element. Correspondingly, the first user plane network element receives the cancel subscription message, where the cancel subscription message is used to indicate the cancellation of subscription to the first event.

[0200] Step 606: The first user plane network element sends a notification to the consumer. Correspondingly, the consumer receives the notification from the first user plane network element; the notification includes a subscription termination indication, which is used to indicate that the consumer's subscription to the first event has been terminated.

[0201] Optionally, the notification also includes: a cause code associated with the subscription termination indication, where the cause code is used to indicate the reason for subscription termination, such as UPF relocation.

[0202] Optionally, the notification also includes: data associated with the first event (referring to data that has been collected but not sent). The first user plane network element may determine whether and when to send the data associated with the first event to the consumer based on the last notification indication from the session management network element or the internal logic of the first user plane network element. This data may be in the same notification as the subscription termination indication or in a different notification.

[0203] Step 603a and step 606 may be carried in the same notification message or in different notification messages; if they are in the same notification message, the notification message is after step 605 and before step 604.

[0204] Optionally, step 607: the first user plane network element sends a notification to the session management network element, and accordingly, the session management network element receives a notification from the first user plane network element, where the notification includes indication information, and the indication information is used to indicate that the first user plane network element has notified the consumer that the consumer's subscription to the first event has been terminated.

[0205] Step 604 and step 607 may be in the same notification or in different notifications.

[0206] FIG7 is a flow chart illustrating a possible communication method. Steps 701 to 705 refer to steps 601 to 605, step 706 refers to step 505, and step 707 (optional) refers to step 506, and will not be repeated here. Steps that may be performed before step 701 may refer to steps 401 to 403, and will not be described in detail here.

[0207] In the above-mentioned Figures 5 to 7, optionally, the content introduced in step 410 in Figure 4, or the content introduced in steps 411a to 411c in Figure 4, are also included, which are not drawn in the figures.

[0208] For the scenario where the first user plane network element redirects to the second user plane network element, as shown in Figure 8, a flow chart of a communication method is introduced. In this method, after receiving the unsubscribe message, the first user plane network element sends the data associated with the first event to the second user plane network element, which then sends it to the consumer. Figure 8 includes the following steps:

[0209] Step 801: The session management network element sends a first message to the first user plane network element. Correspondingly, the first user plane network element receives the first message; the first message is used to indicate the cancellation of subscription to a first event.

[0210] Optionally, the first message includes first information, and the first information is used to indicate a first processing method of the first user-plane network element for the data associated with the first event, and the first processing method is: sending the data associated with the first event after receiving the first information, or sending the data associated with the first event according to the event report information and / or report suggestion information from the consumer, and the event report information is used to indicate the reporting method of the data associated with the first event, or discarding the data associated with the first event. Alternatively, the first processing method is: sending the data associated with the first event when the subscription to the first event is canceled and / or the session associated with the first event is released, or sending the data associated with the first event according to the event report information and / or report suggestion information from the consumer when the subscription to the first event is canceled and / or the session associated with the first event is released.

[0211] The first message in step 801 indicating cancellation of subscription to the first event may be replaced by: the first message indicating renewal of subscription to the first event. In other words, the session management network element may also indicate the first processing method in the subscription update message and then send an unsubscribe message to the first user plane network element to unsubscribe from the first event.

[0212] Step 802 a: The first user plane network element sends data associated with the first event (i.e., collected but not yet sent) to the second user plane network element directly or indirectly through the session management network element. Alternatively, step 802 b: The first user plane network element sends data associated with the first event (i.e., collected but not yet sent) to the second user plane network element indirectly through the session management network element.

[0213] If the first processing method is notified in step 801, the first user plane network element sends the data associated with the first event to the second user plane network element based on the first processing method. If the first processing method is not notified in step 801, the first user plane network element can independently determine the processing method of the data associated with the first event, such as discarding or not reporting the data associated with the first event, or sending the data associated with the first event after receiving the unsubscribe message, or sending the data associated with the first event based on the event report information and / or report suggestion information from the consumer, etc.

[0214] When the first user-plane network element sends data associated with the first event to the second user-plane network element, the first user-plane network element may send the data associated with the first event directly to the second user-plane network element, or the first user-plane network element may send the data associated with the first event to the second user-plane network element through the session management network element. For example, the first message may also include information about the second user-plane network element, such as an identifier or IP address of the second user-plane network element. The first user-plane network element may send the data associated with the first event to the second user-plane network element based on the information about the second user-plane network element. If the first message does not include information about the second user-plane network element, the first user-plane network element sends the data associated with the first event to the session management network element. For another example, if the first message indicates that the destination address is the session management network element, the first user-plane network element first sends the data associated with the first event to the session management network element. Alternatively, if the first message does not indicate a destination address, the first user-plane network element sends the data associated with the first event to the session management network element by default.

[0215] In step 803 a, the session management network element directly sends a second message to the second user plane network element, and the second user plane network element receives the second message. Alternatively, in step 803 b, the session management network element indirectly sends the second message to the second user plane network element via the first user plane network element, and the second user plane network element receives the second message. The second message indicates a subscription to a second event, and the first event and the second event are associated.

[0216] When the session management network element sends a message for subscribing to the second event to the second user plane network element, the session management network element may send the message directly to the second user plane network element, or the second user plane network element may first send the message for subscribing to the second event to the first user plane network element, and the first user plane network element then sends the message for subscribing to the second event to the second user plane network element. Optionally, the first user plane network element carries the data associated with the first event and the message for subscribing to the second event in a single message and sends it to the second user plane network element.

[0217] Step 804: The second user-plane network element sends the first event-related data and the second event-related data to the consumer.

[0218] In a possible example, the second message in a or b of step 803 includes a reporting method for data associated with the second event, and in step 804, the second user plane network element sends the first event-related data and the second event-related data to the consumer based on the reporting method for data associated with the second event. For example, the second message includes event reporting information associated with the second event, and the event reporting information is used to indicate the reporting method for data associated with the second event. For example, the reporting method includes but is not limited to: periodic reporting, reporting upon reaching a threshold, reporting within a specific time, reporting a specific number of times, etc. In a possible example, the event reporting information includes an event reporting mode, and the event reporting mode is used to indicate the reporting method for data associated with the second event. The data associated with the first event and the data associated with the second event can be sent to the consumer in one notification message, or can be sent to the consumer separately through two different notification messages.

[0219] In a possible example, if the second user-plane network element cannot collect the data associated with the second event, then in step 804, the second user-plane network element only sends the data associated with the first event to the consumer. For example: a consumer requests to obtain the latency information of a certain UE. The first user-plane network element has collected 30 minutes of latency data of the UE during step 801 (i.e., user-plane network element relocation). However, after relocation, the UE no longer transmits data, so the second user-plane network element cannot collect the latency data of the UE. When the reporting method of the data associated with the second event is met (for example, the last reporting time indicated by the reporting time information is reached), the second user-plane network element only needs to send the data associated with the first event to the consumer.

[0220] In one possible example, in step 804, the second user-plane network element may aggregate the data associated with the first event and the data associated with the second event to obtain third data, and send the third data to the consumer. Aggregation may be, for example, calculating an average value. For example, a consumer requests to obtain the average bitrate of the UE within an hour. The first user-plane network element has collected 20 minutes of bitrate data during step 801 (i.e., user-plane network element relocation). After receiving the data associated with the first event, the second user-plane network element collects another 40 minutes of bitrate data. The second user-plane network element then calculates the average bitrate information within the hour based on these two pieces of data.

[0221] In conjunction with the description in FIG8 , the transmission method of the data associated with the first event and the transmission method of the subscription message for subscribing to the second event are described in detail in three cases.

[0222] Case 1: The first user plane NE sends data associated with the first event to the session management NE, which then sends it to the second user plane NE. The session management NE then directly sends a subscription message to the second user plane NE for subscribing to the second event. For details, see Figure 9.

[0223] Case 2: The first user plane network element directly sends data associated with the first event to the second user plane network element, and the session management network element directly sends a subscription message for subscribing to the second event to the second user plane network element. For details, please refer to Figure 10.

[0224] Case 3: The first user plane network element directly sends the data associated with the first event to the second user plane network element. The session management network element first sends a subscription message for subscribing to the second event to the first user plane network element, which then sends the message to the second user plane network element. For details, see Figure 11.

[0225] Case 4: The first user plane network element directly sends the data associated with the first event to the second user plane network element, and the first user plane network element also sends the previously received subscription message to the second user plane network element. In this way, the session management network element does not need to subscribe to the second user plane network element again. For details, please refer to Figure 11.

[0226] As shown in FIG9 , a flow chart of a communication method is introduced, which includes the following steps:

[0227] Step 900: The session management network element determines the user plane network element redirection.

[0228] Step 901: The session management network element sends a cancel subscription message to the first user plane network element. Correspondingly, the first user plane network element receives the cancel subscription message from the session management network element; the cancel subscription message is used to indicate the cancellation of subscription to the first event.

[0229] Optionally, the unsubscribe message includes a last notification indication, where the last notification indication is used to indicate a first processing manner of the first user plane network element on the data associated with the first event.

[0230] Step 900 may refer to step 404, step 901 may refer to step 405, and steps that may be executed before step 901 may refer to steps 401 to 403, which will not be described in detail.

[0231] Optionally, the unsubscribe message in step 901 may be replaced by a subscription update message, which is used to indicate that the subscription to the first event is to be updated. Subsequently, the session management network element sends the unsubscribe message to the first user plane network element to unsubscribe from the first event.

[0232] Step 902: The first user plane network element sends a notification to the session management network element. In response, the session management network element receives the notification, which includes data associated with the first event and optionally includes the start time of the first event.

[0233] If the session management network element sends a last notification indication to the first user plane network element in step 901, the first user plane network element may process the data associated with the first event (i.e., data that has been collected but not sent) based on the last notification indication, such as sending, not sending, or discarding the data associated with the first event. If the last notification indication is not included in step 901, the first user plane network element may independently determine how to process the data associated with the first event, such as discarding, not sending, or sending the data associated with the first event after receiving a subscription cancellation message, or sending the data associated with the first event based on event report information and / or report suggestion information from the consumer. If the processing method is to send the data associated with the first event, as defined in this embodiment, the first UPF may send the data associated with the first event to the session management network element.

[0234] The start time of the first event (event start time) indicates the start time of the first event requested by the consumer detected by the first user-plane network element. For example, the consumer requests the QoS monitoring result of a certain UE, the first event is QoS monitoring (i.e., event ID = QoS monitoring), and the first user-plane network element determines that the UE starts data transmission, thereby triggering QoS monitoring, and the time when QoS monitoring is triggered is the event start time. The start time of the first event can be used to update the reporting suggestion information in the subscription message.

[0235] If the first user plane network element determines that the data associated with the first event has not been collected after receiving the unsubscribe message, the notification sent by the first user plane network element to the session management network element in step 901 does not include the parameter, or the content of the parameter is empty.

[0236] Optionally, the destination address notified in the unsubscribe message of step 901 is information that the session management network element is the session management network element, and the first user-side network element first sends the data associated with the first event to the session management network element. Alternatively, the destination address may not be notified in the unsubscribe message, in which case the data associated with the first event is sent to the session management network element by default.

[0237] Step 903: The session management network element sends a subscription message to the second user plane network element. Correspondingly, the second user plane network element receives the subscription message. The subscription message is used to indicate subscription to the second event. The subscription message includes data associated with the first event received in step 902. The second event is associated with the first event.

[0238] For example, the event IDs of the first event and the second event are the same.

[0239] The session management network element selects a new user plane network element (i.e., the second user plane network element) and sends a subscription message to the second user plane network element. The content of the subscription message is basically the same as the content of the subscription message previously sent to the first user plane network element. The differences include but are not limited to the following: One difference is that if the first user plane network element includes data associated with the first event in the notification of step 902, the session management network element may include data associated with the first event in the subscription message of step 903 (data that the first user plane network element has collected but not sent when UPF redirection occurs). Another difference is that the session management network element may update the reporting suggestion information and include the updated reporting suggestion information in the subscription message of step 903. Of course, it is also possible not to update the reporting suggestion information when subscribing to the first event and directly reuse it.

[0240] If the subscription message sent by the consumer to the session management network element (see step 401) includes reporting suggestion information, the session management network element can determine whether to update and how to update the reporting suggestion information before sending the subscription message to the second user plane network element. For example, the session management network element can determine that the reporting suggestion information provided by the consumer in the subscription message remains unchanged, and send the reporting suggestion information of the subscription message to the second user plane network element in the subscription message of step 903. For another example, the session management network element can update the reporting suggestion information based on the reporting suggestion information provided by the consumer and the event start time provided by the first user plane network element. For example, the reporting suggestion information indicates that the event can be delayed in reporting (indicated by the report urgency parameter), and the last reporting time of the event is 100s (that is, the UPF should report the data within 100s after detecting the event at the latest, and this information is indicated by the reporting time information parameter). The session management network element determines based on the event start time and the current time provided by the first user plane network element that 60s have passed since the first user plane network element detected the occurrence of the event. Therefore, the session management network element can set the reporting time information in the updated reporting suggestion information to 40s and send it to the second user plane network element, instructing the second user plane network element to report the data within 40s.

[0241] For other parameters included in the subscription message in step 903, reference may be made to the introduction in step 402 and will not be described in detail.

[0242] In addition, the session management network element can determine whether it is necessary to subscribe to the second user plane network element. When UPF relocation is triggered, the session management network element determines whether it is necessary to subscribe to the second user plane network element based on the subscription message from the consumer (see step 401). For example, if the consumer requests to report three times, and the session management network element determines that the first user plane network element has already reported three times when the user plane network element redirection occurs, the session management network element does not need to send a subscription message to the second user plane network element and can directly cancel the subscription with the first user plane network element. In other words, step 903 is an optional step. If step 903 is not executed, the data associated with the first event obtained by the session management network element in step 902 can be sent by the session management network element to the consumer (step 906).

[0243] Optionally, step 904: the second user-plane network element aggregates the data associated with the first event and the data associated with the second event to obtain aggregated data.

[0244] Step 905: The second user-plane network element sends the first event-related data and / or the second event-related data to the consumer, or sends aggregated data.

[0245] Step 904 and step 905 may refer to the relevant content of step 804 above, and will not be repeated here.

[0246] As shown in FIG10 , a flow chart of a communication method is introduced, which includes the following steps:

[0247] Step 1000: The session management network element determines the user plane network element redirection.

[0248] Step 1000 is the same as step 900, and may refer to step 404. Steps that may be executed before step 1001 may refer to steps 401 to 403, and will not be described in detail.

[0249] Step 1001: a session management network element sends a cancel subscription message to a first user plane network element. Correspondingly, the first user plane network element receives the cancel subscription message from the session management network element; the cancel subscription message is used to indicate the cancellation of subscription to a first event.

[0250] Optionally, the unsubscribe message includes a last notification indication, which is used to indicate a first processing mode of the first user plane network element for the data associated with the first event. For relevant contents of the last notification indication, please refer to the description in step 405 and will not be repeated here.

[0251] In addition, the unsubscribe message also includes information about the second user plane network element, and optionally, a redirection indication. The information about the second user plane network element, such as an identifier or an IP address, can be used by the first user plane network element to obtain information about the second user plane network element based on the information about the second user plane network element. The redirection indication is used to instruct the first user plane network element to redirect. After receiving the redirection indication, the first user plane network element sends a notification to the second user plane network element. The notification includes data associated with the first event that has been collected in the first user plane network element but has not yet been sent out. Of course, it may also be that the protocol stipulates that the first user plane network element will send the data associated with the first event to the second user plane network element upon receiving a message indicating the cancellation of subscription to the first event and receiving information from the second user plane. In this way, there is no need to carry a redirection indication in the unsubscribe message.

[0252] If the first user plane network element determines that the data associated with the first event has not been collected after receiving the unsubscribe message, there is no need to send the data associated with the first event to the second user network element.

[0253] Optionally, the unsubscribe message in step 1001 may be replaced by a subscription update message, which is used to indicate that the subscription to the first event is to be updated. Subsequently, the session management network element sends the unsubscribe message to the first user plane network element to unsubscribe from the first event.

[0254] Step 1002: The first user plane network element sends a notification to the second user plane network element. Correspondingly, the second user plane network element receives the notification, which includes data associated with the first event.

[0255] Optionally, in step 1002a, the first user plane network element sends an indication to the session management network element. Accordingly, the session management network element receives the indication, which indicates that the first user plane network element has sent data associated with the first event to the second user plane network element. Optionally, the first user plane network element may also send the start time of the first event to the session management network element.

[0256] Step 1003: The session management network element sends a subscription message to the second user plane network element. Correspondingly, the second user plane network element receives the subscription message. The subscription message is used to indicate subscription to a second event, and the second event is associated with the first event. For example, the first event and the second event have the same event ID.

[0257] The difference from step 903 is that step 1003 does not include the data associated with the first event. The rest of the content can refer to step 903 and will not be repeated.

[0258] Optionally, step 1004: the second user-plane network element aggregates the data associated with the first event and the data associated with the second event to obtain aggregated data.

[0259] Step 1005: The second user-plane network element sends the first event-related data and / or the second event-related data to the consumer, or sends aggregated data.

[0260] The contents of step 1004 and step 1005 are the same as those of step 904 and step 905. You may refer to the relevant contents of step 804 above and will not repeat them here.

[0261] As shown in FIG11 , a flow chart of a communication method is introduced, which includes the following steps:

[0262] Step 1100: The session management network element determines the user plane network element redirection.

[0263] Step 1100 is the same as step 900, and may refer to step 404. Steps that may be executed before step 1101 may refer to steps 401 to 403, and will not be described in detail.

[0264] Step 1101: The session management network element sends a cancel subscription message to the first user plane network element. Correspondingly, the first user plane network element receives the cancel subscription message from the session management network element; the cancel subscription message is used to indicate the cancellation of subscription to the first event.

[0265] Optionally, the unsubscribe message includes a last notification indication, which is used to indicate a first processing mode of the first user plane network element for the data associated with the first event. For relevant contents of the last notification indication, please refer to the description in step 405 and will not be repeated here.

[0266] Optionally, the unsubscribe message also includes information about the second user plane network element, and optionally, a redirection indication. The information about the second user plane network element is, for example, an identifier or an IP address. The first user plane network element can obtain information about the second user plane network element based on the information about the second user plane network element. The redirection indication is used to instruct the first user plane network element to redirect. After receiving the redirection indication, the first user plane network element sends a notification to the second user plane network element. The notification includes data associated with the first event that has been collected in the first user plane network element but has not yet been sent out. Of course, it may also be that the protocol stipulates that the first user plane network element will send the data associated with the first event to the second user plane network element after receiving a message for instructing to unsubscribe from the first event and receiving information about the second user plane. In this way, there is no need to carry a redirection indication in the unsubscribe message. If the unsubscribe message does not include information about the second user plane network element, the first user plane network element may also determine a user plane network element (i.e., the second user plane network element) to which the data associated with the first event is sent.

[0267] Optionally, the unsubscribe message may further include a subscription message for the second event. In this way, the session management network element does not need to send a separate subscription message to the second user plane network element. If the unsubscribe message does not include a subscription message for the second event, the first user plane network element may send the subscription message it has received to the second user plane network element.

[0268] If the first user plane network element determines that the data associated with the first event has not been collected after receiving the unsubscribe message, there is no need to send the data associated with the first event to the second user network element.

[0269] Optionally, the unsubscribe message in step 1101 may be replaced by a subscription update message, which is used to indicate that the subscription to the first event is to be updated. Subsequently, the session management network element sends the unsubscribe message to the first user plane network element to unsubscribe from the first event.

[0270] Step 1102: The first user plane network element sends a notification to the second user plane network element. Correspondingly, the second user plane network element receives the notification, which includes data associated with the first event and a subscription message for indicating subscription to the second event.

[0271] The subscription message for instructing subscription to the second event includes reporting suggestion information from the consumer.

[0272] If step 1101 includes a subscription message for the second event, the subscription message used to indicate subscription to the second event in step 1102 comes from step 1101; if step 1101 does not include a subscription message for the second event, the subscription message used to indicate subscription to the second event in step 1102 is determined by the first user plane network element itself. For example, the subscription message for subscribing to the first event sent by the session management network element to the first user plane network element can be sent to the second user plane network element in step 1102 (in this case, the first event and the second event are exactly the same).

[0273] If the unsubscribe message of step 1101 includes information about the second user plane network element, the first user plane network element can obtain information about the second user plane network element based on step 1101; if the unsubscribe message of step 1101 does not include information about the second user plane network element, the first user plane network element can also determine a user plane network element (i.e., the second user plane network element) to which the data associated with the first event is sent.

[0274] Optionally, step 1102a: the first user plane network element sends an indication to the session management network element. Correspondingly, the session management network element receives the indication, which is used to indicate that the first user plane network element has sent data associated with the first event to the second user plane network element.

[0275] Optionally, step 1103: the second user-plane network element aggregates the data associated with the first event and the data associated with the second event to obtain aggregated data.

[0276] Step 1104: The second user-plane network element sends the first event-related data and / or the second event-related data to the consumer, or sends aggregated data.

[0277] The contents of step 1103 and step 1104 are the same as those of step 904 and step 905. You may refer to the relevant contents of step 804 above and will not repeat them here.

[0278] Figures 9 to 11 illustrate how a first user-plane network element directly or indirectly sends data associated with a first event to a second user-plane network element, which then aggregates the data associated with the first event and the data associated with the second event and sends the data to the consumer. In another possible example, as shown in Figure 12, the first user-plane network element sends data associated with the first event to a session management network element, and the second user-plane network element sends data associated with the second event to the session management network element, which then aggregates the data associated with the first event and the data associated with the second event and sends the data to the consumer.

[0279] As shown in FIG12 , a flow chart of a communication method is provided, including the following steps:

[0280] Step 1200: The session management network element determines the user plane network element redirection.

[0281] Step 1201: The session management network element sends a cancel subscription message to the first user plane network element. Correspondingly, the first user plane network element receives the cancel subscription message from the session management network element; the cancel subscription message is used to indicate the cancellation of subscription to the first event.

[0282] Optionally, the unsubscribe message includes a last notification indication, where the last notification indication is used to indicate a first processing manner of the first user plane network element on the data associated with the first event.

[0283] Step 1200 may refer to step 404, step 1201 may refer to step 405, and steps that may be executed before step 1201 may refer to steps 401 to 403, which will not be described in detail.

[0284] In addition, the unsubscribe message in step 1201 may also be updated to a subscription update message, and then the session management network element sends the unsubscribe message to the first user plane network element.

[0285] Optionally, step 1202: the first user plane network element sends a notification to the session management network element. Correspondingly, the session management network element receives the notification, which includes data associated with the first event.

[0286] If the session management network element sends a last notification indication to the first user plane network element in step 1201, the first user plane network element may process the data associated with the first event (i.e., data that has been collected but not sent) based on the last notification indication, such as sending, not sending, or discarding the data associated with the first event. If the last notification indication is not included in step 1201, the first user plane network element may independently determine how to process the data associated with the first event, such as discarding or not reporting the data associated with the first event, sending the data associated with the first event after receiving a subscription cancellation message, or sending the data associated with the first event based on the event report information and / or report suggestion information from the consumer. If the processing method is to send the data associated with the first event, as defined in this embodiment, the first UPF may send the data associated with the first event to the session management network element.

[0287] Step 1203: The session management network element sends a subscription message to the second user plane network element. Correspondingly, the second user plane network element receives the subscription message; the subscription message is used to indicate subscription to the second event.

[0288] The content of the subscription message sent by the session management network element to the second user plane network element is basically the same as the content of the subscription message previously sent to the first user plane network element. Possible differences include: the reporting suggestion information (reporting suggestion information) sent by the session management network element to the first user plane network element in step 402 (reference step) and the reporting suggestion information (reporting suggestion information) in step 1203 may be different. For example, the first user plane network element sends the start time (event start time) of the first event to the session management network element, and the event start time represents the start time of the first event requested by the consumer detected by the first user plane network element. For example, the consumer requests the QoS monitoring result of a certain UE, and the first event is QoS monitoring (i.e., event ID = QoS monitoring). The first user plane network element determines that the UE starts data transmission, thereby triggering QoS monitoring, and the time when QoS monitoring is triggered is the event start time. The session management network element can update the reporting suggestion information based on the reporting suggestion information provided by the consumer and the event start time provided by the first user plane network element. For example, the reporting suggestion information indicates that the event can be delayed in reporting (indicated by the report urgency parameter), and the last reporting time of the event is 100s (that is, the UPF should report the data within 100s after detecting the event at the latest, and this information is indicated by the reporting time information parameter). The session management network element determines based on the event start time and the current time provided by the first user plane network element that 60s have passed since the first user plane network element detected the occurrence of the event. Therefore, the session management network element can set the reporting time information in the updated reporting suggestion information to 40s and send it to the second user plane network element, instructing the second user plane network element to report the data within 40s.

[0289] For other parameters included in the subscription message in step 1203, please refer to the introduction in step 402 and will not be described in detail.

[0290] The order of step 1201 and step 1203 is not limited.

[0291] Step 1204: The second user plane network element sends a notification to the session management network element. Correspondingly, the session management network element receives the notification, which includes data associated with the second event.

[0292] The second user plane network element may send data associated with the second event based on the report suggestion information.

[0293] Optionally, step 1205: the session management network element aggregates the data associated with the first event and the data associated with the second event to obtain aggregated data.

[0294] Step 1206: The session management network element sends the first event-related data and / or the second event-related data to the consumer, or sends aggregated data.

[0295] When a consumer indicates in a subscription message (see step 401) sent to a session management network element that it wishes to report collected data based on event reporting information, the session management network element, upon receiving data associated with a first event from a first user-plane network element, determines whether a reporting condition (e.g., reporting at a specific time) is met. If the reporting condition is not met, the session management network element does not immediately report the data associated with the first event from the first user-plane network element to the consumer, but instead waits until the reporting condition is met before reporting. During the waiting period, if the session management network element receives data associated with a second event from a second user-plane network element, then, if the reporting condition is met, the session management network element aggregates the data associated with the first event and the data associated with the second event, and then notifies the consumer of the aggregated data. The description of the aggregation method in step 804 is omitted for clarity. Alternatively, the session management network element may not aggregate the data associated with the first event and the data associated with the second event, but instead directly send them to the consumer. The session management network element may send the data associated with the first event and the data associated with the second event to the consumer in a single notification message, or may send the data associated with the first event and the data associated with the second event to the consumer via two separate notification messages.

[0296] Furthermore, after step 1206, the session management network element may determine whether it is necessary to update the subscription with the second user plane network element. For example, if the session management network element determines that the second user plane network element can subsequently send notifications directly to the consumer, the session management network element may update the subscription of the second user plane network element and change the notification target address to the consumer. For example, because the session management network element no longer needs to aggregate data associated with the first event and the second event, the second user plane network element may send the notification message directly to the consumer. For another example, if the session management network element determines that it is necessary to update reporting suggestion information, such as when aggregating data associated with the first event and the second event, the second user plane network element is required to report the data within 40 seconds. If the session management network element no longer needs to aggregate the data associated with the first event and the second event, the second user plane network element's reporting deadline is no longer 40 seconds, for example, to 100 seconds. In this case, the session management network element may update the subscription for the second event and send updated reporting suggestion information to the second user plane network element.

[0297] In addition, the session management network element can determine the destination address for notifications when subscribing to the second user plane network element based on whether the first user plane network element has data. For example, if the first user plane network element has data, the notification destination address is the session management network element; otherwise, the second user plane network element's notification destination address is the consumer. In this case, the second user plane network element directly notifies the consumer of the data in step 1204, and steps 1205 and 1206 do not need to be performed.

[0298] The above-mentioned Figures 3, 4, and 5 describe carrying first information in the unsubscribe message, where the first information is used to indicate a first processing manner of the first user-plane network element for the data associated with the first event (see step 301 of Figure 3, step 405 of Figure 4, and step 502 of Figure 5). The above-mentioned Figures 6 and 7 describe carrying first information in the subscription update message.

[0299] Next, an example of carrying the first information in a subscription message is introduced.

[0300] As shown in FIG13 , a flow chart of a communication method is introduced, which includes the following steps:

[0301] Step 1301: The consumer sends a subscription message to the session management network element. In response, the session management network element receives the subscription message, which is used to indicate subscription to the first event. For example, the consumer sends the subscription message to the session management network element by calling the Nsmf_eventExposure_Subscribe service operation.

[0302] Step 1301 may refer to step 401 and will not be repeated here.

[0303] Step 1302: The session management network element sends a third message (subscribe message) to the first user plane network element. Correspondingly, the first user plane network element receives the third message (subscribe message) from the session management network element.

[0304] The third message is used to instruct subscription to the first event.

[0305] The third message includes first information (reporting indication; it should be noted that reporting indication is merely a name for the indication information, which is used to instruct the first user-plane network element to perform a first processing manner on the data associated with the first event. The name of the indication information may also be replaced with another name without affecting the function of the indication information). The first information is used to instruct the first user-plane network element to perform a first processing manner on the data associated with the first event. The first processing manner is at least one of the following (the following numbering is for convenience of description only and does not limit the order or importance of the processing manners):

[0306] 1) When the subscription to the first event is terminated and / or the PDU session associated with the first event is released, the data associated with the first event is sent (e.g., immediately sent). This processing method can be understood as: when the subscription is terminated or the PDU session is released, the data associated with the first event that has been collected by the first user plane network element but has not yet been reported is always reported.

[0307] 2) When the subscription to the first event is terminated and / or the PDU session associated with the first event is released, the data associated with the first event is sent according to the event report information from the consumer. This processing method can be understood as: when the subscription is terminated or the PDU session is released, the data associated with the first event that has been collected by the first user-side network element but not yet reported is reported according to the event report information and / or report establishment information from the consumer. In the current technology, the event report information and / or report suggestion information from the consumer is used to report data during the subscription process, and will not be used to report data after the subscription is terminated. In an embodiment of the present application, after the subscription is terminated, the data that has been collected by the first user-side network element but not yet reported can also be reported according to the event report information.

[0308] 3) When the subscription to the first event is terminated and / or the PDU session associated with the first event is released, and when the set conditions are met, the data associated with the first event is sent. This processing method can be understood as follows: when the subscription is terminated or the PDU session is released, if the preset conditions are met, the data associated with the first event that has been collected but not yet reported is reported; if the first conditions are not met, there is no need to report. For example, the preset conditions include: reaching a specific threshold (for example, the number of transmitted data packets is greater than 1000, or the amount of transmitted data is greater than 100M, etc.), or reaching a specific time (for example, the input of the NWDAF model is the average bit rate within 5 minutes, so if the subscription is terminated, the data collected by the UPF is less than 5 minutes, then there is no need to report; if the data collected by the UPF is greater than 5 minutes, then it is reported), etc. The preset condition reporting can also be reporting based on event report information and / or report suggestion information from the consumer, or canceling the subscription to the first event, or the release of the PDU session associated with the first event.

[0309] 4) When the subscription to the first event is terminated and / or the PDU session associated with the first event is released, discard the data associated with the first event. This processing method can be understood as: when the subscription is terminated or the PDU session is released, the data associated with the first event that has been collected by the first user plane network element but has not yet been reported is not reported and is discarded.

[0310] 5) When the subscription to the first event is terminated and / or the PDU session associated with the first event is released, data associated with the first event is not reported. This processing method can be understood as follows: when the subscription is terminated or the PDU session is released, data associated with the first event that has been collected but not yet reported by the first user plane network element is not reported. It does not indicate whether the first user plane network element discards the data associated with the first event.

[0311] In one possible implementation, the reporting indication in step 1302 may also be the relocation reporting indication or reporting indication carried by the consumer when subscribing (step 1301), that is, the SMF may simply forward the relocation reporting indication or reporting indication brought by the consumer in the subscription.

[0312] Other parameters included in the subscription message of step 1302 may come from the parameters included in the subscription message of step 1301, and will not be described in detail here.

[0313] Optionally, step 1303: the first user plane network element sends a notification to the consumer, and accordingly, the consumer receives the notification from the first user plane network element; the notification includes data associated with the first event.

[0314] For example, the first user plane network element sends a notification to the consumer by calling the Nupf_EventExposure_Notify service operation.

[0315] Optionally, the first user plane network element may send data associated with the first event based on the reporting suggestion information and / or event reporting information in step 1302.

[0316] The specific content of step 1303 can be referred to step 403 and will not be repeated here.

[0317] It is understandable that step 1303 is the reporting of data during the subscription process. If no data is generated, step 1303 does not need to be executed.

[0318] Optionally, step 1304: the session management network element determines that the first condition is met.

[0319] Step 1304 may refer to step 404 and will not be repeated here.

[0320] Optionally, step 1305: the session management network element sends a cancel subscription message to the first user plane network element. Correspondingly, the first user plane network element receives the cancel subscription message from the session management network element; the cancel subscription message is used to indicate the cancellation of subscription to the first event.

[0321] Optionally, step 1306: the session management network element sends instruction information for releasing the PDU session associated with the first event to the first user plane network element.

[0322] Step 1307: The first user-plane network element processes the data associated with the first event (that is, the collected but unsent data) based on the first processing method.

[0323] For example, after the first user plane network element receives the message to cancel subscription to the first event (eg, step 1305 ), it determines that the subscription to the first event is terminated, and then step 1307 may be executed.

[0324] For another example, if the first event is related to a PDU session, and if the PDU session is released (e.g., step 1306), data cannot be collected any further, and the first user plane network element may also execute step 1307. For example, after the first user plane network element receives indication information (e.g., the indication information comes from the session management network element) indicating that the PDU session associated with the first event is released or that the PCU session associated with the first event is released, step 1307 is executed.

[0325] The first user plane network element receives the unsubscribe message or determines that the PDU session corresponding to the data collection is released. The first user plane network element determines how to process the collected but unreported data associated with the first event based on the first information / reporting indication in the subscription message of step 1302. If it is determined based on the first information / reporting indication that the data needs to be sent to the consumer, the first UPF may send the data to the consumer. For example, the first user plane network element sends the data to the consumer by calling the Nupf_EventExposure_Notify service operation.

[0326] The example described in FIG13 differs from the examples described above in the following manner: in which message the first information is sent to the first user-plane network element; the remaining details (e.g., how to notify the consumer that the subscription to the first event has been terminated and how to transmit data) can refer to the examples described above. It is understood that all embodiments of the present application can refer to each other as long as there is no logical conflict.

[0327] Next, an example is introduced in which a user plane network element event consumer sends first information to a first user plane network element.

[0328] FIG14 is a flow chart illustrating a communication method.

[0329] Optionally, step 1400: the consumer determines the first user plane network element.

[0330] A possible scenario is that an analysis consumer (such as AF / NEF) sends an analysis request to a user plane network element event consumer (such as NWDAF), where the analysis request is used to indicate the analysis result of the first UE, and the analysis request includes the IP address of the first UE, and optionally, the data network name (DNN), single network slice selection assistance information (S-NSSAI), area of ​​interest (AoI), application server IP address / fully qualified domain name (FQDN), application ID, data network access identifier DNAI, etc.

[0331] The user plane network element event consumer discovers the first user plane network element serving the first UE through the NRF. For example, the user plane network element event consumer sends the IP address of the first UE and optional information such as the DNN, S-NSSAI, and DNAI to the NRF by calling the Nnrf_NFDiscovery_Request service operation. The NRF discovers the first user plane network element based on the IP address of the first UE and optional information such as the DNN, S-NSSAI, and DNAI. The NRF discovers the first user plane network element based on this information about the first UE. The NRF sends indication information to the user plane network element event consumer by calling the Nnrf_NFDiscovery_Response service operation, indicating the first user plane network element.

[0332] Step 1401: The consumer sends a fourth message to the first user plane network element. Correspondingly, the first user plane network element receives the fourth message.

[0333] The fourth message is used to instruct subscription to the first event.

[0334] For example, the consumer sends the fourth message to the first user plane network element by calling the Nupf_EventExposure_subscribe service operation.

[0335] The fourth message includes the first information / reporting indication. For an introduction to the first information / reporting indication, please refer to the introduction at step 1302, which will not be repeated here.

[0336] The other contents included in the fourth message can refer to the contents sent by the sender to the session management network element in step 401 described above, and will not be repeated here. Optionally, the fourth message does not include a relocation reporting indication (used to indicate the second processing method for the data associated with the first event when the first condition is met).

[0337] Optionally, the identifier of the UE in the target of event reporting is the identifier of the first UE in step 1400 .

[0338] Optionally, step 1402: the first user plane network element sends a notification to the user plane network element event consumer. Correspondingly, the user plane network element event consumer receives the notification from the first user plane network element; the notification includes data associated with the first event.

[0339] For example, the first user plane network element sends a notification to the consumer by calling the Nupf_EventExposure_Notify service operation.

[0340] Optionally, the first user plane network element may send data associated with the first event based on the reporting suggestion information and / or event reporting information in step 1401.

[0341] The specific content of step 1402 can be referred to step 403 and will not be repeated here.

[0342] It is understandable that step 1402 is for reporting data during the subscription process. If no data is generated, step 1402 does not need to be executed.

[0343] Step 1403: The first user-plane network element processes the data associated with the first event (that is, the data that has been collected but not sent out) based on the first processing method.

[0344] For example, after receiving the message to cancel subscription to the first event, the first user plane network element determines that the subscription to the first event is terminated, and then step 1403 may be executed.

[0345] For another example, if the first event is related to a PDU session, and if the PDU session is released, data cannot be collected any further, and the first user-plane network element may also execute step 1403. For example, after the first user-plane network element receives indication information (e.g., from a session management network element) indicating that the PDU session associated with the first event is released or that the PCU session associated with the first event is released, step 1403 is executed.

[0346] Optionally, step 1404: the first user plane network element sends data associated with the first event (that is, data that has been collected but not sent out) to the user plane network element event consumer.

[0347] The first user plane network element determines how to process the collected but unreported data associated with the first event based on the first information / reporting indication in the fourth message of step 1401. If it is determined based on the first information / reporting indication that the data needs to be sent to the consumer, the first UPF may send the data to the consumer. For example, the first user plane network element sends the data to the consumer by calling the Nupf_EventExposure_Notify service operation.

[0348] Further optionally, the first user plane network element may also send subscription termination indication information (subscription termination indication) to the user plane network element event consumer, to indicate that the subscription to the first event has been terminated.

[0349] Further optionally, the first user plane network element may also send a cause code (cause code) of the subscription termination reason to the user plane network element event consumer, such as PDU session release.

[0350] When the user plane network element event consumer (e.g., NWDAF) receives the subscription termination indication and the optional reason code, it is determined that the IP address of the first UE may have changed. Further, optionally, the user plane network element event consumer may then perform the following operations:

[0351] Based on the SUPI / GPSI of the first UE, the new IP address of the first UE (which may be a private UE IP address or a public UE IP address) is retrieved from the UDR. Based on the new IP address of the first UE, the new UPF is discovered through the NRF (of course, the new UPF and the previous UPF may be the same UPF or different UPFs), and an event subscription message is sent to the new UPF based on the new IP address of the first UE.

[0352] A possible scenario is as follows: UE#1's PDU session is established, and the network (e.g., SMF / UPF) assigns a private UE IP address, "IP_a," to UE#1. A consumer (e.g., AF / NEF / NWDAF) wants to subscribe to the UPF data corresponding to UE#1. The consumer first obtains the UE's private IP address, then sends a subscription message to the UPF, using the private IP address to subscribe to the UE's data. UE#1's PDU session is released (e.g., due to UPF relocation), and "IP_a" becomes unavailable for a period of time. After a period of time, when UE#2 establishes a PDU session, "IP_a" may be assigned to UE#2.

[0353] 'IP_a' may be assigned to UE#2, but the Consumer (e.g. AF / NEF / NWDAF) believes that 'IP_a' is still assigned to UE#1. This will cause the consumer to collect data from the UPF based on the wrong UE IP address. The above example can avoid this situation.

[0354] It is understandable that, in order to implement the functions in the above embodiments, the user plane network element and the session management network element include hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should readily appreciate that, in combination with the units and method steps of the various examples described in the embodiments disclosed in this application, this application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in hardware or in a manner driven by computer software depends on the specific application scenario of the technical solution and the conditions under which design constraints take effect.

[0355] Figures 15 and 16 are schematic diagrams of possible communication devices provided in embodiments of the present application. These communication devices can be used to implement the functions of the user plane network element and the session management network element in the above method embodiments, thereby also achieving the beneficial effects of the above method embodiments.

[0356] As shown in FIG. 15 , the communication device 1500 includes a processing unit 1510 and a transceiver unit 1520 .

[0357] For example, the communication device 1500 is configured to implement the functions of the first user plane network element, the second user plane network element, or the session management network element in the method embodiments shown in Figures 3-14 above. The transceiver unit 1520 may execute the receiving and sending actions performed by the first user plane network element, the second user plane network element, or the session management network element in the method embodiments above. The processing unit 1510 may execute other actions, except for the sending and receiving actions, among those performed by the first user plane network element, the second user plane network element, or the session management network element in the method embodiments above.

[0358] Exemplarily, when the communication device 1500 is used to implement the function of the first user plane network element in the method embodiment shown in Figure 3, the transceiver unit 1520 is used to receive the first information and send data associated with the first event. The processing unit 1510 is used to parse the first information and determine the first processing method.

[0359] Exemplarily, when the communication device 1500 is used to implement the function of the session management network element in the method embodiment shown in FIG4 , the transceiver unit 1520 is configured to receive a subscription message from a consumer, send a subscription message to the first user plane network element, and send an unsubscribe message to the first user plane network element. The processing unit 1510 is configured to determine whether a first condition is satisfied.

[0360] A more detailed description of the processing unit 1510 and the transceiver unit 1520 can be directly obtained by referring to the relevant description of the method embodiments shown in Figures 3 to 14, and will not be repeated here. The processing unit 1510 can be implemented by a processor, and the transceiver unit 1520 can be implemented by a transceiver.

[0361] As shown in Figure 16, communication device 1600 includes a processor 1610 and an interface circuit 1620. Processor 1610 and interface circuit 1620 are coupled to each other. It is understood that interface circuit 1620 can be a transceiver or an input / output interface. Optionally, communication device 1600 may also include a memory 1630 for storing instructions executed by processor 1610, or storing input data required by processor 1610 to execute instructions, or storing data generated after processor 1610 executes instructions. Sometimes, interface circuit 1620 can also be understood as part of processor 1610, in which case communication device 1600 includes processor 1610.

[0362] When the communication device 1600 is used to implement the method shown in Figures 3 to 14 above, the processor 1610 is used to implement the functions of the processing unit 1510 above, and the interface circuit 1620 is used to implement the functions of the transceiver unit 1520 above.

[0363] When the above-mentioned communication device is a chip applied to a terminal device, the terminal device chip implements the functions of the terminal device in the above-mentioned method embodiment. When the terminal device chip receives information from the network device, it can be understood that the information is first received by other modules in the terminal device (such as a radio frequency module or antenna) and then sent to the terminal device chip by these modules. When the terminal device chip sends information to the network device, it can be understood that the information is first sent to other modules in the terminal device (such as a radio frequency module or antenna) and then sent to the network device by these modules.

[0364] When the above-mentioned communication device is a chip applied to a network device, the network device chip implements the functions of the network device in the above-mentioned method embodiment. The network device chip receives information from the terminal device, which can be understood as the information being first received by other modules in the network device (such as a radio frequency module or antenna) and then sent to the network device chip by these modules. The network device chip sends information to the terminal device, which can be understood as the information being sent to other modules in the network device (such as a radio frequency module or antenna) and then sent to the terminal device by these modules. The network device module here can be a baseband chip of the network device, or it can be a DU or other module. The DU here can be a DU under the open radio access network O-RAN architecture.

[0365] In the present application, when entity A sends information to entity B, it can be that A sends it directly to B, or that A sends it to B indirectly through other entities. Similarly, when entity B receives information from entity A, it can be that entity B directly receives the information sent by entity A, or that entity B indirectly receives the information sent by entity A through other entities. Entities A and B here can be network devices or terminal devices, or modules within a network device or modules within a terminal device. The sending and receiving of information can be information interaction between a network device and a terminal device, or information interaction between two network devices, such as information interaction between a CU and a DU; the sending and receiving of information can also be information interaction between different modules within a device, such as information interaction between a terminal device chip and other modules of the terminal device, or information interaction between a network device chip and other modules in the network device.

[0366] It is understood that the processor in the embodiments of the present application may be a central processing unit (CPU), or may be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. The general-purpose processor may be a microprocessor or any conventional processor.

[0367] The present application also provides a computer-readable storage medium storing a computer program, which, when executed by a computer, enables the computer to perform the above-mentioned communication method. In other words, the computer program includes instructions for implementing the above-mentioned communication.

[0368] An embodiment of the present application further provides a computer program product, including: computer program code, which, when executed on a computer, enables the computer to execute the communication method provided above.

[0369] An embodiment of the present application further provides a communication system, which includes: a first user-plane network element and a second user-plane network element that execute the above-mentioned communication method.

[0370] The method steps in the embodiments of the present application can be implemented by hardware or by a processor executing software instructions. The software instructions can be composed of corresponding software modules, and the software modules can be stored in a random access memory, a flash memory, a read-only memory, a programmable read-only memory, an erasable programmable read-only memory, an electrically erasable programmable read-only memory, a register, a hard disk, a mobile hard disk, a compact disc read-only memory (CD-ROM) (also known as a read-only optical disc) or any other form of storage medium well known in the art. An exemplary storage medium is coupled to the processor so that the processor can read information from the storage medium and write information to the storage medium. Of course, the storage medium can also be an integral part of the processor. The processor and the storage medium can be located in an ASIC. In addition, the ASIC can be located in a base station or a terminal. Of course, the processor and the storage medium can also be present in a base station or a terminal as discrete components.

[0371] The above embodiments can be implemented in whole or in part using software, hardware, firmware, or any combination thereof. When implemented using software, they can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer programs or instructions. When the computer programs or instructions are loaded and executed on a computer, the processes or functions described in the embodiments of this application are performed in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, a network device, a first control plane network element, a user equipment, or other programmable device. The computer program or instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program or instructions can be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means. The computer-readable storage medium can be any available medium accessible by a computer or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium, such as a floppy disk, hard disk, or magnetic tape; an optical medium, such as a digital video disk; or a semiconductor medium, such as a solid-state drive. The computer-readable storage medium may be a volatile or nonvolatile storage medium, or may include both volatile and nonvolatile types of storage media.

[0372] In the various embodiments of the present application, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.

[0373] In the embodiments of the present application, the number of nouns, unless otherwise specified, means "singular noun or plural noun", that is, "one or more". "At least one" means one or more, and "plural" means two or more. "And / or" describes the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone, where A or B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. For example, A / B means: A or B. "At least one of the following items" or "one or more of them" and other similar expressions refer to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b, or c, or one or more of a, b, or c, means: a, b, c, a and b, a and c, b and c, or a and b and c. Each of a, b, and c can be single or multiple.

[0374] The ordinal numbers "first" and "second" mentioned in the embodiments of this application are used to distinguish multiple objects and are not used to limit the size, content, order, timing, priority, or importance of multiple objects. Moreover, such names do not indicate differences in the content, sender / receiver, transmission order, size, application scenario, priority, or importance of the two pieces of information. In addition, the numbering of the steps in the various embodiments introduced in this application is only for distinguishing different steps and is not used to define the order of the steps.

Claims

1. A communication method, characterized in that: Executed by a first user plane network element or a chip used for the first user plane network element, including: Receive a first message, the first message including an identifier of a first event and first information, the first information being used to indicate a first processing method, by the first user-plane network element, for data associated with the first event; the first processing method being: sending the data associated with the first event or discarding the data associated with the first event when the subscription to the first event is canceled and / or the session associated with the first event is released, or sending the data associated with the first event according to event report information and / or report suggestion information from the consumer when the subscription to the first event is canceled and / or the session associated with the first event is released, the event report information being used to indicate a reporting method for the data associated with the first event; When the first event subscription is cancelled and / or the session associated with the first event is released, data associated with the first event is sent or discarded based on the first information.

2. The method according to claim 1, wherein The data associated with the first event is the data associated with the first event that has been collected by the first user-plane network element and has not yet been sent out.

3. The method according to claim 1 or 2, wherein: Also includes: The first message is used to instruct cancellation of subscription to the first event; or, The first message is used to indicate a subscription to the first event.

4. The method according to any one of claims 1 to 3, wherein When the first event subscription is canceled and / or the session associated with the first event is released, the method includes: receiving information indicating cancellation of subscription to the first event; and / or; Information indicating that the session associated with the first event is released, or releasing the session associated with the first event, is received.

5. The method according to any one of claims 1 to 4, characterized in that The receiving of the first message includes: receiving the first message from the session management network element; or, The first message is received from the consumer.

6. The method according to any one of claims 1 to 5, wherein: Also includes: A notification message is sent to the consumer, where the notification message includes second information, where the second information is used to indicate that the consumer's subscription to the first event has been terminated.

7. The method according to claim 6, wherein The notification message further includes a reason code associated with the second information, where the reason code is used to indicate a reason for subscription termination.

8. The method according to claim 6 or 7, wherein: After sending the second information to the consumer, the method further includes: Sending third information to the session management network element, where the third information is used to indicate that the first user plane network element has notified the consumer that the consumer's subscription to the first event has been terminated.

9. The method according to any one of claims 1 to 8, wherein After sending the data associated with the first event to the consumer, the method further includes: Sending fourth information to the session management network element, where the fourth information is used to indicate that the first user plane network element has sent data associated with the first event subscribed by the consumer to the consumer.

10. A communication method, characterized in that: The method is executed by a first network element or a chip used for the first network element, including: A first message is sent to a first user-plane network element, wherein the first message includes an identifier of a first event and first information, and the first information is used to indicate a first processing method of the first user-plane network element for data associated with the first event; the first processing method is: when the subscription to the first event is canceled and / or the session associated with the first event is released, the data associated with the first event is sent or the data associated with the first event is discarded, or when the subscription to the first event is canceled and / or the session associated with the first event is released, the data associated with the first event is sent according to event report information and / or report suggestion information from the consumer, and the event report information is used to indicate a reporting method for the data associated with the first event.

11. The method according to claim 10, wherein The data associated with the first event is the data associated with the first event that has been collected by the first user-plane network element and has not yet been sent out.

12. The method according to claim 10 or 11, wherein: The first message is used to instruct to cancel subscription to the first event; or, The first message is used to indicate a subscription to the first event.

13. The method according to any one of claims 10 to 12, wherein: Also includes: Sending information for instructing to cancel subscription to the first event to the first user plane network element; and / or Sending information to the first user plane network element indicating that the session associated with the first event is released, or releasing the session associated with the first event.

14. The method according to any one of claims 10 to 13, wherein: The first network element is a session management network element or the consumer.

15. The method according to any one of claims 10 to 14, wherein: The first network element is a session management network element, and further includes: Determine user plane network element redirection; Sending indication information of releasing the protocol data unit (PDU) session associated with the first event to the first user plane network element.

16. The method according to any one of claims 10 to 15, wherein: The first network element is a session management network element, and before sending the first message to the first user plane network element, the method further includes: A second message is received from a consumer, where the second message includes an identifier of the first event and the first information, and the second message is used to indicate a subscription to the first event.

17. The method according to any one of claims 10 to 16, wherein: The first network element is a session management network element, and the first message is used to instruct cancellation of subscription to the first event; Before sending the first message to the first user plane network element, the method further includes: Determine that a first condition is met; the first condition is redirecting the first user plane network element to another user plane network element other than the first user plane network element, or the first condition is unsubscribing from the first event.

18. The method according to any one of claims 10 to 15, wherein: Before sending the first message to the first user plane network element, the method further includes: Receive fifth information from a consumer, the fifth information being used to indicate a second processing method for data associated with the first event when the first condition is met; the first processing method is related to the second processing method; the second processing method includes: sending data associated with the first event when the subscription to the first event is canceled and / or the session associated with the first event is released, or sending data associated with the first event based on event report information and / or report suggestion information from the consumer when the subscription to the first event is canceled and / or the session associated with the first event is released, and the event report information is used to indicate a reporting method for data associated with the first event.

19. The method according to any one of claims 10 to 18, wherein: The first network element is a session management network element, and further includes: Sending sixth information to the consumer, where the sixth information is used to indicate that the consumer's subscription to the first event has been canceled.

20. The method according to claim 19, wherein The sixth information is also used to indicate the reason for subscription termination.

21. The method according to any one of claims 10 to 20, wherein: The first network element is a session management network element, and after sending the first message to the first user plane network element, further includes: Receive third information from the first user plane network element, where the third information is used to indicate that the first user plane network element has notified the consumer that the consumer's subscription to the first event has been canceled.

22. The method according to any one of claims 10 to 21, wherein: The first network element is a session management network element, and after sending the first message to the first user plane network element, further includes: Receive fourth information from the first user plane network element, where the fourth information is used to indicate that the first user plane network element has sent data associated with the first event subscribed by the consumer to the consumer.

23. A communication method, characterized in that: Executed by a second user plane network element or a chip used for the second user plane network element, including: Receiving data associated with a first event from a session management network element or a first user plane network element, where the first event is subscribed to by a consumer and the first event is associated with the first user plane network element; receiving a second message from a session management network element, where the second message is used to indicate a subscription to a second event; and associating the first event with the second event; The first event-related data and the second event-related data are sent to the consumer.

24. The method according to claim 23, wherein Receiving data associated with the first event from the session management network element, including: Receive data associated with a first event from the first user plane network element and forwarded by the session management network element.

25. The method of claim 23, wherein: Receiving a second message from the session management network element includes: Receive a second message from the second management network element forwarded by the first user plane network element.

26. The method according to any one of claims 23 to 25, wherein: The data associated with the first event is carried in the second message.

27. The method according to any one of claims 23 to 26, wherein: The second message includes first information, where the first information is used to indicate a reporting method for data associated with the second event; The sending the first event-related data and the second event-related data to the consumer includes: Based on the reporting method, the first event-related data and the second event-related data are sent to the consumer.

28. The method according to any one of claims 23 to 27, wherein: Sending data associated with the first event and data associated with the second event to the consumer includes: aggregating the data associated with the first event and the data associated with the second event to obtain third data; The third data is sent to the consumer.

29. A communication method, characterized in that: Executed by a session management network element or a chip used for a session management network element, including: Sending the first message to a first user plane network element, where the first message is used to indicate cancellation of subscription to a first event; receiving data associated with the first event from the first user plane network element; Send data associated with the first event to a second user plane network element.

30. The method of claim 29, wherein: The first message includes one or more of the following: first information, second user plane network element information, and third information; Among them, the first information is used to indicate the first processing method of the first user plane network element for the data associated with the first event, and the first processing method is: sending the data associated with the first event when the subscription to the first event is canceled and / or the session associated with the first event is released, or sending the data associated with the first event according to the event report information and / or report suggestion information from the consumer when the subscription to the first event is canceled and / or the session associated with the first event is released, and the event report information is used to indicate the reporting method of the data associated with the first event; the information of the second user plane network element is used to indicate that the data associated with the first event is sent to the second user plane network element; the third information is used to indicate that the first user plane network element is redirected to the second user plane network element.

31. The method according to claim 29 or 30, wherein Also includes: A second message is sent to the second user plane network element, where the second message is used to indicate a subscription to a second event.

32. The method of claim 31, wherein Sending a second message to the second user plane network element includes: The second message is sent to the first user plane network element, so that the first user plane network element forwards the second message to the second user plane network element.

33. The method according to claim 31 or 32, wherein: The data associated with the first event is carried in the second message.

34. A communication method, characterized in that: Executed by a session management network element or a chip used for a session management network element, including: Sending the first message to the first user plane network element; the first message is used to indicate the cancellation of subscription to the first event; receiving data associated with the first event from the first user plane network element; Sending a second message to the second user plane network element, where the second message is used to indicate a subscription to a second event; and associating the first event with the second event; receiving data associated with the second event from the second user plane network element; aggregating the data associated with the first event and the data associated with the second event to obtain third data; The third data is sent to the consumer.

35. The method of claim 34, wherein: The first message includes first information, and the first information is used to indicate a first processing method of the first user-side network element for the data associated with the first event. The first processing method is: sending the data associated with the first event when the subscription to the first event is canceled and / or the session associated with the first event is released, or sending the data associated with the first event based on event report information and / or report suggestion information from the consumer when the subscription to the first event is canceled and / or the session associated with the first event is released. The event report information is used to indicate a reporting method for the data associated with the first event.

36. The method according to claim 34 or 35, wherein: The second message includes second information, where the second information is used to indicate a reporting method for data associated with the second event.

37. A communication device, characterized in that: The method comprises a module for executing the method according to any one of claims 1 to 36.

38. A communication device, characterized in that: comprising a processor coupled to a memory; The memory is used to store computer programs or instructions; The processor is used to execute part or all of the computer programs or instructions in the memory, and when the part or all of the computer programs or instructions are executed, it is used to implement the method according to any one of claims 1 to 36.

39. A communication device, characterized in that: including processor and memory; The memory is used to store computer programs or instructions; The processor is used to execute part or all of the computer programs or instructions in the memory, and when the part or all of the computer programs or instructions are executed, it is used to implement the method according to any one of claims 1 to 36.

40. A chip system, characterized in that: comprising a processor and an interface circuit, wherein the processor is coupled to the memory; The memory is used to store computer programs or instructions; The processor is used to execute part or all of the computer programs or instructions in the memory, and when the part or all of the computer programs or instructions are executed, it is used to implement the method according to any one of claims 1 to 36.

41. A computer-readable storage medium, characterized in that The storage medium stores a computer program or instruction. When the computer program or instruction is executed by the communication device, the method according to any one of claims 1 to 36 is implemented.

42. A computer program product, characterized in that The computer program product comprises: computer instructions, and when the computer instructions are run on a computer, the method according to any one of claims 1 to 36 is implemented.

Images