Event opening method and device

Abstract

The present application discloses an event opening method and apparatus, relating to the field of communication technology, for enabling an application-side device to open certain events to a network-side device. The method may include: a first application function entity obtaining first information for instructing the first application function entity to enable an event opening function; enabling the event opening function based on the first information; receiving an event subscription request from the first device for requesting to subscribe to data related to a first event; and sending the data related to the first event to the first device based on the event subscription request, thereby enabling the application-side entity to externally open and obtain data related to a certain event.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of communication technology, and in particular to an event opening method and device. Background Art

[0002] Third Generation Partnership Project (3 rd The fifth generation partnership project (3GPP) system architecture (SA) designed a brand new 5GMS architecture for the fifth generation media streaming (5GMS) service during the protocol version (release 16, Rel-16).

[0003] The 5GMS application function (5GMS AF) in the 5GMS architecture already has preliminary data collection capabilities (such as terminal parameter collection or usage collection), but does not have the function of opening the collected data / information to the required network elements or third parties. That is, in the 5GMS architecture, the 5GMS AF cannot support opening its collected data / information to other network elements or third-party servers. Summary of the Invention

[0004] The embodiments of the present application provide an event opening method and apparatus to enable an application-side device to open events to other devices, such as a network-side device.

[0005] To achieve the above objectives, the embodiments of the present application adopt the following technical solutions.

[0006] In a first aspect, an embodiment of the present application provides an event opening method, the method comprising: a first application function entity obtains first information used to instruct the first application function entity to turn on an event opening function, and turns on the event opening function according to the first information; subsequently, the first application function entity receives an event subscription request from a first device for requesting to subscribe to relevant data of a first event, and sends relevant data of the first event to the first device according to the event subscription request.

[0007] Based on the method described in the first aspect, the first application function entity (such as 5GMS AF) can enable its own event opening function. After collecting / obtaining data, the first application function entity responds to the subscriber's event subscription request and sends / opens the collected / obtained data (or subscription information) to other devices (such as NWDAF, etc.) so that other devices can perform specific network analysis and decision-making based on the data sent by the first application function entity.

[0008] In one possible design, the first information includes an event opening indication and / or an event list; the event list is used to indicate an open event, and the event list includes one or more of an identifier (ID) of the open event and descriptive information of the open event. The event opening function can be explicitly indicated by the event opening indication, or can be implicitly indicated by providing an event list, thereby improving the flexibility of indicating the event opening function.

[0009] In one possible design, open events include one or more of the measurement and collection data of the terminal and the log information of the application server. That is, this application opens multiple types of data / events to network-side devices to expand application scenarios.

[0010] In one possible design, the first application function entity sends relevant data of the first event to the first device, including: when a preset trigger condition is met, the first application function entity sends relevant data of the first event to the first device, and the preset trigger condition includes one or more of the arrival of data cache time, the arrival of subscription reporting cycle, and the receipt of data reported by the target terminal. That is, the report can be triggered based on the arrival of time and / or based on the data reported by a specific terminal to trigger the reporting of data to the network side device, providing multiple optional methods for triggering reporting.

[0011] In one possible design, the data cache time is included in the first information; alternatively, the data cache time is determined based on a subscription reporting period; alternatively, the data cache time is determined based on a first period and a subscription reporting period, where the first period is the time period during which the source of data related to the first event sends data related to the first event to the first application function network element. Based on this design, multiple flexible and effective methods for determining the data cache time are provided.

[0012] In one possible design, the subscription reporting period is determined based on a first period and a second period; wherein the first period is the time period during which the source of the data related to the first event sends the data related to the first event to the first application function network element; and the second period is the time period during which the first device requests the data to be sent. The subscription reporting period is the first period; or, alternatively, the subscription reporting period is the second period. Based on this possible design, the first application function entity can negotiate the subscription reporting period with the subscriber, ensuring that not only the subscriber's subscription requirements are met, but also that complete terminal-side data is received, avoiding the problem of incomplete terminal-reported data due to a period that is too short.

[0013] In one possible design, the method further includes: the first application function entity obtains relevant data of the first event from the local cache. Before caching the data, the method further includes: the first application function entity receives a cache indication, obtains and caches relevant data of the first event according to the cache indication, the first information carries the cache indication, and the cache indication is used to instruct the first application function network element to cache relevant data of an open event, and the open event includes the first event, that is, the first application function entity caches the received data locally, and when the subscriber subscribes, it obtains the data from the local cache and sends it to the subscriber to ensure the continuity and integrity of the data.

[0014] In one possible design, the method also includes: the first application function entity sends an event subscription request to the second device; the first application function entity receives relevant data of the first event from the second device, that is, the data is stored on the second device, and the first application function entity obtains data from the second device to reduce the storage pressure caused by the local cache data of the first application function entity.

[0015] In one possible design, the first application function entity sends relevant data of the first event to the first device, including: the first application function entity sends the relevant data of the first event to the first device according to a first correspondence, where the first correspondence is used to indicate that the network element subscribing to the first event is the first device. The first correspondence includes a correspondence between an identifier of the first device and an ID of the first event; or, the first correspondence includes a correspondence between a subscription ID and an ID of the first event, where the subscription ID is used to indicate that the first device initiates a subscription, so that the first application function entity can find the subscriber according to the first correspondence and send data obtained from other devices to the subscriber.

[0016] In one possible design, the first information includes security authentication information, and the security authentication information is used by the first application function entity to verify whether the first device is legal; the method also includes: when the first application function entity determines that the first device is legal based on the security authentication information, the first application function entity sends a subscription success message to the first device, and the subscription success message is used to indicate that the first device has successfully subscribed to the first event, thereby ensuring the security and legality of the subscription.

[0017] In one possible design, the first application function entity includes a 5GMS AS or a 5GMS AF, which improves the flexibility of the execution entity of the solution and the application scenarios of the solution.

[0018] In a second aspect, the present application provides a communication device, which may be a first application function entity or a chip or system-on-chip in the first application function entity, or a functional module in the first application function entity for implementing the method described in the first aspect or any possible design of the first aspect. The communication device can implement the functions performed by the first application function entity or access network device in the above-mentioned aspects or possible designs, and the functions can be implemented by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above-mentioned functions. For example, the communication device may include: a transceiver unit and a processing unit.

[0019] The transceiver unit is used to obtain first information for instructing the first application function entity to enable an event opening function.

[0020] A processing unit is configured to enable an event opening function according to the first information.

[0021] The transceiver unit is further configured to receive an event subscription request from the first device for requesting to subscribe to data related to the first event, and send the data related to the first event to the first device according to the event subscription request.

[0022] Specifically, the execution actions of each unit of the communication device can refer to the first aspect or any possible design of the first aspect, and will not be repeated here.

[0023] According to a third aspect, a communication device is provided, which may be a first application function entity or a chip or system on chip in the first application function entity. The communication device may implement the functions performed by the first application function entity in the above-mentioned aspects or possible designs, and the functions may be implemented by hardware. In one possible design, the communication device may include: a processor and a communication interface, and the processor and the communication interface may support the communication device to execute the method described in the above-mentioned first aspect or any possible design of the first aspect. In another possible design, the communication device may further include a memory, the memory being used to store computer-executable instructions and data necessary for the communication device. When the communication device is running, the processor executes the computer-executable instructions stored in the memory, so that the communication device executes the event opening method described in the above-mentioned first aspect or any possible design of the first aspect.

[0024] In a fourth aspect, a computer-readable storage medium is provided, which may be a readable non-volatile storage medium. Instructions are stored in the computer-readable storage medium, which, when executed on a computer, enables the computer to execute the event opening method described in the first aspect or any possible design of the first aspect.

[0025] In a fifth aspect, a computer program product comprising instructions is provided, which, when executed on a computer, enables the computer to execute the event opening method described in the first aspect or any possible design of the first aspect.

[0026] In a sixth aspect, a communication device is provided. The communication device may be a first application function entity or a chip or system-on-chip in the first application function entity. The communication device includes one or more processors and one or more memories. The one or more memories are coupled to the one or more processors and are configured to store computer program code. The computer program code includes computer instructions that, when executed by the one or more processors, cause the first application function entity to execute the event opening method described in the first aspect or any possible design of the first aspect.

[0027] Among them, the technical effects brought about by any design method from the second to the sixth aspects can refer to the technical effects brought about by the above-mentioned first aspect or any possible design of the first aspect, and will not be repeated here.

[0028] In a seventh aspect, an embodiment of the present application provides a communication system, which may include: a first application function entity and a first device. The first application function entity may perform signaling interaction with the first device to execute the event opening method described in the first aspect or any possible design of the first aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] Figure 1a A schematic diagram of a 5GMS architecture;

[0030] Figure 1b This is another 5GMS architecture diagram;

[0031] Figure 2 Schematic diagram of downlink media stream transmission in 5GMS architecture;

[0032] Figure 3 A simplified schematic diagram of a system architecture provided in an embodiment of the present application;

[0033] Figure 4 This is a diagram of the 5G network architecture;

[0034] Figure 5 The event opening flow chart provided for this application;

[0035] Figure 6 A schematic diagram of the composition of a communication device provided in an embodiment of the present application;

[0036] Figure 7 A flow chart of an event opening method provided in an embodiment of the present application;

[0037] Figure 8 A flow chart of an event opening method provided in an embodiment of the present application;

[0038] Figure 9 A flow chart of an event opening method provided in an embodiment of the present application;

[0039] Figure 10 A flow chart of an event opening method provided in an embodiment of the present application;

[0040] Figure 11 A schematic diagram of the composition of a communication device 110 provided in an embodiment of the present application. DETAILED DESCRIPTION

[0041] Third Generation Partnership Project (3 rd The 3GPP system architecture (SA) designed a new 5GMS architecture for the fifth generation media streaming (5GMS) service during the protocol release 16 (Rel-16). In one possible design, the 5GMS architecture is as follows: Figure 1a As shown, it can include: terminal (can be called user equipment (UE)), data network (datanetwork, DN). The 5GMS architecture can be used with mobile communication networks (such as the fifth generation (5G) th In the fusion scenario, the 5GMS architecture can also include network equipment.

[0042] Figure 1a In the present invention, the terminal may include a 5GMS application (or a 5GMS-aware application) (or a terminal application / UE application) and a 5GMS client (5GMS client). The 5GMS client may include a media session handler (MSH) and a media stream handler (MP). The media stream handler corresponds to the downlink media stream service sent from the DN side to the terminal side. The media stream handler may also be called a media player (MP). The network device may include a control plane network element and / or a user plane network element in the 5G system, such as Figure 1aAs shown, the network equipment may include a network exposure function (NEF), a policy control function (PCF), a 5GMS application function (5GMS AF) and other network elements (not shown in the figure). DN may include a 5GMS application server (5GMS AS) and a 5GMS application provider (5GMS application provider) (which may be referred to as a 5GMS application provider or an application service provider (ASP)). It should be understood that the 5GMS AS and the 5GMS AF may be deployed independently or integrated together without limitation. In addition, the devices involving 5GMS functions on the terminal side and the DN side may be referred to as 5GMS devices, and the 5GMS AS and 5GMS application providers in the DN may be collectively referred to as application servers.

[0043] Figure 1a 5GMS devices in the system can communicate with each other through a point-to-point interface (also known as an exposed application interference (exposed API) or M interface (abbreviated as M)). Figure 1a As shown, Figure 1a M1 is the interface between 5GMS AF and 5GMS application provider. M2 is the interface between 5GMS AS and 5GMS application provider. M3 is the interface between 5GMS AS and 5GMS AF. M4 is the interface between 5GMS AS and the media stream processing function on the terminal side. M5 is the interface between 5GMS AF and the media session processing function on the terminal side. M6 is the interface between the media session processing function and the media stream processing function. M7 is the interface between the media stream processing function and the media session processing function. M8 is the interface between the 5GMS application provider and the 5GMS application. Figure 1a The DN-side devices in the embodiment can communicate with each other through the next generation (N) interface (or simply interface N). For example, N33 is the interface between the 5GMS AF and NEF, and N5 is the interface between the 5GMS AF and PCF. Of course, the communication interfaces between the devices can also have other names, which are not limited in this application.

[0044] In another possible design, the method described in the embodiment of the present application is not limited to application to Figure 1aThe 5GMS architecture shown can also correspond to a general data collection and reporting network architecture. In this case, the 5GMS client can also be just a data collection client on the terminal side, which is used to collect data on the UE side. For example, Figure 1b The corresponding general data collection and reporting architecture is shown. Figure 1a As shown, the general data collection and reporting architecture may include: a terminal, a data collection AF (data collection AF) and a DN. The terminal includes a UE application and a direct data collection client (direct data collection client), and the DN may include an application service provider (ASP) and an AS. Figure 1b The application provider in the 5GMS can be called a 5GMS application provider, which can include: provisioning AF, data collection client and event subscription AF. The data collection AF can be connected to the network side equipment through the N interface, such as the network repository function (NRF), network exposure function (NEF), and network data analysis function (NWDAF). The data collection AF is connected to the terminal and DN side equipment through the R interface (such as R1, R2, etc.).

[0045] Below Figure 1a as well as Figure 1b The functions of the terminal, AF, and DN side devices in the system are introduced as follows:

[0046] The terminal in this application can be called user equipment (UE), or terminal equipment, and can be a device with wireless transceiver function. The terminal can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; it can also be deployed on the water surface (such as ships, etc.); it can also be deployed in the air (for example, on airplanes, balloons and satellites, etc.). The user equipment can also be called a terminal, which can be a mobile phone, a tablet computer (pad), a computer with wireless transceiver function, a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in smart city, a wireless terminal in smart home, etc.

[0047] The 5GMS application deployed in the terminal can be considered as a terminal-side application (application, app); 5GMS applications can be deployed by application service providers themselves. The content of 5GMS applications can be provided by 5GMS application providers.

[0048] The media session processing function (such as MSH) is used to interact with the 5GMS AF to realize the creation, control and transmission of media sessions. The media session processing function can also open relevant application programming interfaces (APIs) for upper-layer 5GMS applications to call.

[0049] The media stream processing function (such as MP) is mainly used for media stream transmission, encoding, decoding and playback (for downlink services) between the 5GMS AS and provides an API interface for upper-layer 5GMS applications and MSH.

[0050] 5GMS application providers are mainly content provision servers for 5GMS applications, such as Tencent, YouTube and other application providers. 5GMS application providers are used to provide and activate media service features for the media service.

[0051] 5GMS AF itself is also a type of AF defined by 3GPP. 5GMS AF is designed to enable information interaction between external servers and 3GPP networks, such as capability exposure or parameter provision. This 5GMS AF is an AF dedicated to media streaming services. Figure 1b In the architecture shown, the 5GMS AF can be a data collection AF, which has the function of collecting UE-side data and opening it to the outside world.

[0052] 5GMS AS can be deployed and managed by a mobile network operator (MNO), or provided by an external third-party application. 5GMS AS acts as a media streaming application server, similar to a content delivery network (CDN). Figure 1b In the architecture shown, the 5GMS AS may be an AS, which may be connected to the data collection AF via an R4 interface.

[0053] by Figure 1a Take the 5GMS network architecture shown as an example. Figure 2 It is a 5G media stream architecture for downlink (DL) media stream services. It is an application scenario where the UE selects a media stream to play through live or on-demand mode. In this application scenario, the media stream processing function can be a media player (such as MP). The 5GMS terminal side may include many sub-functions, such as Figure 2 As shown, the media session processing function (such as MSH) side will support many sub-module functions, such as the media session processing function can include the core function sub-module, the metrics collection and reporting sub-module, the consumption collection and reporting sub-module, and the network assistance and QoS adjustment sub-module. Figure 2 In the application scenario of the downlink media stream service shown, the interface M may be referred to as a downlink interface. For example, M1 may be replaced by M1d, and M2 may be replaced by M2d, etc., which are not listed one by one.

[0054] The functions of each sub-module are introduced below: Core function sub-module: implements the core functions of session establishment, management, and control. Parameter collection and reporting sub-module: configures parameter collection and reporting on the terminal side, thereby realizing parameter collection and reporting on the terminal side. Usage collection and reporting sub-module: collects and configures usage information of media streaming services on the terminal side, and reports it to 5GMS AF based on the configuration information. Network assistance and QoS adjustment sub-module: interacts with the network through 5GMS AF or directly interacts with access network equipment (such as radio access network (RAN)), and requests corresponding policy adjustments (such as quality of service (QoS) adjustment) and network assistance from the network side.

[0055] The media stream processing module or media player MP side will act as a media access terminal (such as a dynamic adaptive streaming over HTTP (DASH) terminal), performing sub-functional modules such as media data decryption, usage policy and logging, digital rights management (DRM) client, media data decoding, and media display and rendering.

[0056] Specifically, the 5GMS application provider will create a service provisioning session and send relevant features, such as parameter collection and reporting features, to the 5GMS AF. The 5GMS AF determines the service access information (SAI) based on the feature information sent by the 5GMS application provider and returns the SAI or its index to the 5GMS application provider. When the user starts to access the media streaming service, the UE obtains the SAI through the M8 or M5 interface and configures and executes according to the features in the SAI. For example, the 5GMS terminal will configure the features according to the corresponding sub-functions in the obtained SAI.

[0057] Taking the parameter collection and reporting function as an example, first, the 5GMS application provider will create a service activation session and send relevant feature information, such as parameter collection and reporting features, to the 5GMS AF. The 5GMS AF determines the SAI based on the feature information sent by the 5GMS application provider and returns the SAI or its index to the 5GMS application provider. Subsequently, when the user starts to access the media streaming service, the UE obtains the SAI through the M8 or M5 interface and configures and executes tasks based on the features in the SAI. For example, the 5GMS terminal will collect and report the parameters according to the obtained SAI. The MSH configures the MP to collect data based on the SAI and reports the collected data information to the 5GMS AF through the M5 interface based on the SAI.

[0058] As can be seen from the above, the 5GMS AF in the 5GMS architecture already has preliminary data collection capabilities (such as UE parameter collection or usage collection), but does not have the function of opening the collected data / information to the required network elements or third parties. That is, in the 5GMS architecture, the 5GMS AF cannot support the opening of its collected data / information to other network elements or third-party servers.

[0059] To solve the above technical problems, an embodiment of the present application provides an event opening method, which may include: a first application function entity obtaining first information for instructing the first application function entity to open an event opening function, opening the event opening function according to the first information, receiving an event subscription request from a first device for requesting to subscribe to relevant data of a first event, sending relevant data of the first event to the first device according to the event subscription request, and realizing that the application-side entity opens relevant data of a certain event to the outside world. In this way, the application-side device (such as 5GMS AF) opens UE-side data and / or the application-side device (such as 5GMS AF and / or 5GMS AS) its own data to the outside world to network-side devices or third-party devices, etc.

[0060] The technical solutions in the embodiments of the present application are described below in conjunction with the drawings in the embodiments of the present application.

[0061] The event opening method provided in the embodiment of the present application can be applied to Figure 3 The communication system shown in Figure 3 As shown, the communication system may include a terminal, a first application function entity, and a first device. Optionally, it may also include a second device, a second application function entity, etc. The first application function entity and the second application function entity may be located in a DN.

[0062] in, Figure 3The terminal in the specification can be called terminal equipment (terminal equipment) or user equipment (user equipment, UE) or mobile station (mobile station, MS) or mobile terminal (mobile terminal, MT) etc. Figure 3 The terminal in the communication network can be a mobile phone, a tablet computer or a computer with wireless transceiver function, and can also be a virtual reality (VR) terminal, augmented reality (AR) terminal, wireless terminal in industrial control, wireless terminal in unmanned driving, wireless terminal in telemedicine, wireless terminal in smart grid, wireless terminal in smart city, smart home, car terminal, etc.

[0063] DN can be an operator network that provides data transmission services to users, such as an operator network that provides IP multimedia services (IMS) to users. An application server can be deployed in the DN, and the application server can provide data transmission services to users. The first application function entity can be a 5GMS AF or a functional module in the 5GMS AF. Alternatively, the first application function entity can be a 5GMS AS or a functional module in the 5GMS AS. The second application function entity can be a 5GMS application provider / 5GMS application server / 5GMS application provider, etc.

[0064] The first device may be a network device (PCF or NEF, etc.) The second device may be other application function entities, etc.

[0065] It should be noted that Figure 3 This is just an example architecture diagram. Figure 3 In addition to the functional units shown in , the system may also include other functional network elements, such as: operation, administration and maintenance (OAM) network elements, etc., which are not limited in the embodiments of the present application. Figure 3 The names of the devices in the Figure 3 In addition to the names shown, each device can also be named other names, such as replacing them with network element names with the same or similar functions, without restriction.

[0066] in, Figure 3The system shown can be a third generation partnership project (3GPP) communication system, such as a fourth generation (4G) communication system, a long term evolution (LTE) system, a fifth generation (5G) communication system or a new radio (NR) system, a next generation communication system, etc., or a non-3GPP communication system without restriction.

[0067] by Figure 3 The communication system shown is Figure 4 As an example, the 5G communication system shown in FIG. Figure 4 As shown, the UE can be Figure 1a or Figure 1b The terminal shown includes Figure 1a or Figure 1b The module in the terminal, DN is Figure 1a or Figure 1b Data networks in Figure 1a or Figure 1b The first application function entity may correspond to the modules included in the data network. Figure 4 The AF in the DN can be deployed in or outside the DN. The first device may include Figure 4 The second application function entity may be the NWDAF, NEF, NRF, policy control function (PCF), unified data manager (UDM), authentication server function (AUSF), access and mobility management function (AMF), session management function (SMF), or service control point (SCP), user plane function (UPF), etc. The second application function entity may be the 5GMS application provider or Figure 4 The second device may be an application server in the AF or DN or any device in the NWDAF, NEF, NRF, PCF, UDM, etc.

[0068] Optionally, the first application function entity in the embodiment of the present application may also be referred to as a communication device, which may be a general-purpose device or a dedicated device, and the embodiment of the present application does not specifically limit this. Optionally, the relevant functions of the first application function entity in the embodiment of the present application may be implemented by one device, or may be implemented by multiple devices together, or may be implemented by one or more functional modules within a device, and the embodiment of the present application does not specifically limit this. It is understandable that the above functions may be network elements in a hardware device, or software functions running on dedicated hardware, or a combination of hardware and software, or virtualization functions instantiated on a platform (e.g., a cloud platform).

[0069] exist Figure 4 In the architecture shown, Figure 5 As shown, the 5GMS AF can be configured to cache data and enable capability exposure. The 5GMS AF caches UE-side data, making the corresponding data available to other network elements or third-party entities when a subscriber subscribes. Alternatively, the 5GMS AF can be configured to enable capability exposure, allowing the 5GMS application provider to store UE-side data. When a subscriber subscribes to the 5GMS AF, the 5GMS AF obtains the data from the 5GMS application provider and reports it to the subscriber.

[0070] In the specific implementation, Figure 3 Each device shown, such as the first session management function network element, the mobility management network element, etc., can adopt Figure 6 The structure shown, or including Figure 6 Parts shown. Figure 6 This is a schematic diagram of the composition of a communication device 600 provided in an embodiment of the present application. The communication device 600 may include a processor 601 and a memory 604. Furthermore, the communication device 600 may also include a communication line 602 and a communication interface 603. The processor 601, the memory 604, and the communication interface 603 may be connected via the communication line 602.

[0071] Processor 601 may be a central processing unit (CPU), a general-purpose processor, a network processor (NP), a digital signal processor (DSP), a microprocessor, a microcontroller, a programmable logic device (PLD), or any combination thereof. Processor 601 may also be other devices with processing capabilities, such as circuits, devices, or software modules, without limitation.

[0072] The communication line 602 is used to transmit information between the components included in the communication device 600.

[0073] Communication interface 603 is used to communicate with other devices or other communication networks. Such other communication networks may be Ethernet, radio access networks (RAN), wireless local area networks (WLAN), etc. Communication interface 603 may be a module, circuit, transceiver, or any other device capable of communication.

[0074] The memory 604 is used to store instructions, where the instructions may be computer programs.

[0075] The memory 604 may be a read-only memory (ROM) or other type of static storage device that can store static information and / or instructions, or a random access memory (RAM) or other type of dynamic storage device that can store information and / or instructions, or an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compact disc, laser disc, optical disc, digital versatile disc, Blu-ray disc), magnetic disk storage media, or other magnetic storage devices, without limitation.

[0076] It should be noted that the memory 604 can exist independently of the processor 601 or can be integrated with the processor 601. The memory 604 can be used to store instructions, program codes, or some data. The memory 604 can be located inside the communication device 600 or outside the communication device 600, without limitation.

[0077] Processor 601 is configured to execute instructions stored in memory 604 to implement the event opening method provided in the following embodiments of the present application. For example, when communication device 600 is a first application function entity or a chip or system on a chip in the first application function entity, processor 601 executes instructions stored in memory 604 to implement the steps performed by the first application function entity in the following embodiments of the present application.

[0078] In one example, the processor 601 may include one or more CPUs, such as Figure 6 CPU0 and CPU1 in.

[0079] As an optional implementation, the communication device 600 includes multiple processors, for example, Figure 6 In addition to the processor 601, a processor 607 may also be included.

[0080] As an optional implementation, the communication apparatus 600 further includes an output device 605 and an input device 606. For example, the input device 606 is a keyboard, a mouse, a microphone, a joystick, and the like, and the output device 605 is a display screen, a speaker, and the like.

[0081] It should be noted that the communication device 600 can be a desktop computer, a portable computer, a network server, a mobile phone, a tablet computer, a wireless terminal, an embedded device, a chip system or a computer with a plurality of CPUs. Figure 6 In addition, Figure 6 The structure shown in the figure does not constitute a limitation on the communication device, except Figure 6 In addition to the components shown, the communication device may include more or fewer components than shown, or combine certain components, or arrange the components differently.

[0082] In the embodiment of the present application, the chip system can be composed of chips, or can include chips and other discrete devices.

[0083] In addition, the actions and terms involved in the various embodiments of this application can refer to each other without limitation. The message names or parameter names in the messages exchanged between the various devices in the embodiments of this application are only examples, and other names can also be used in specific implementations without limitation.

[0084] In the embodiment of the present application, the chip system can be composed of chips, or can include chips and other discrete devices.

[0085] The following combination Figure 3 The communication system shown in the figure describes the event opening method provided in the embodiment of the present application. Each network element in the following embodiment may have Figure 6illustrative components, no further details are given. It should be noted that the actions, terms, etc. involved in the various embodiments of the present application can refer to each other without limitation. The message names or parameter names in the messages exchanged between the various devices in the embodiment of the present application are only an example, and other names can also be used in the specific implementation without limitation. For example: the determination in the embodiment of the present application can also be understood as creation (create) or generation (generate), the "include" in the embodiment of the present application can also be understood as "carry" or "include", etc., the "report" in the embodiment of the present application can also be understood as "send" or "transmit" or "open" or "notify", etc., the "subscription reporting period" in the embodiment of the present application can also be understood as "reporting period", etc., which are uniformly explained here, and the embodiment of the present application does not make specific limitations on this.

[0086] Figure 7 An event opening method provided in the embodiment of the present application is as follows: Figure 7 As shown, this may include:

[0087] S701: The first application function entity obtains first information.

[0088] Among them, the first application function entity can be Figure 3 5GMS AF or 5GMS AS in, or Figure 3 The functional modules or chips in the 5GMS AF, or the functional modules or chips in the 5GMS AS are shown.

[0089] The first information may be used to instruct the first application function entity to enable an event opening function. In one possible design, the first information may include an event opening indication and / or an event list. The event opening indication may indicate enabling the event opening function and is an explicit indication. For example, the event opening indication may be a binary bit number, where a binary bit "0" indicates enabling the event opening function and a binary bit "1" indicates not enabling the event opening function, or a binary bit "1" indicates enabling the event opening function and a binary bit "0" indicates not enabling the event opening function.

[0090] In an embodiment of the present application, the event list may include one or more of an identifier of an open event and descriptive information of an open event. An open event may refer to an event that can be opened to the outside by the first application function entity, such as one or more of the measurement collection data of the terminal and the log information of the application server. Opening to the outside may refer to obtaining relevant data of a certain event and reporting the obtained relevant data of the event to other devices. The identifier (ID) of the open event can be used to identify the event that can be opened to the outside by the first application function entity, and the identifiers of different events are different. The descriptive information of the open event can be used to describe the event that can be opened to the outside by the first application function entity, and the descriptive information of the open event may include one or more of the event type of the open event, the ID of the open event, the start open time / end open time of the open event, the open cycle, the user-side parameters of the open event, etc.

[0091] Optionally, in addition to the event opening indication and / or opening event, the first information may also include other information, for example, the first information may also include one or more of application identity information, security authentication information, and data cache time.

[0092] In an embodiment of the present application, security authentication information can be used to authenticate the legitimacy of a device that subscribes to a certain event that can be opened to the outside world from the first application function entity, so that after the authentication is successful, the relevant data can be opened to the outside world to the device. The security authentication information may include the identifier of the device allowed to subscribe, and / or the authorization certificate, etc. If the device that initiates the subscription to the first application function entity is included in the devices indicated by the identifier of the device allowed to subscribe, it means that the device that initiates the subscription is legal. And / or, if a device carries an authorization certificate in the event subscription request initiated by the device to the first application function entity, and if the authorization certificate is the same as the authorization certificate included in the security authentication information, it means that the device is legal. For example, taking the case where the security authentication information includes the identifier of the device allowed to subscribe and the first application function entity is 5GMS AF, the security authentication information includes {device 1, device 2}. If device 3 initiates an event subscription request to 5GMS AF, it is found that device 3 is not legal based on the security authentication information, and the event subscription request is rejected. If device 2 initiates an event subscription request to 5GMS AF, it is found that device 2 is legal based on the security authentication information. In response to the event subscription request of device 2, the relevant data of the subscribed event is reported / opened / sent to device 2.

[0093] In an embodiment of the present application, the data cache time may refer to the time during which the relevant data of an open event is cached on the application side (such as in a 5GMS AF or a 5GMS application provider). The time may be a time period. The time period may be represented by a start time and a cache duration, or may be represented by an end time and a cache duration, or may be used to identify the start time and the end time, without limitation. For example, the cache time for the relevant data of an open event may be {start time, 9:00 am, cache duration is 1 hour}, or {cache duration is 1 hour, end time is 10:00 am}, or {start time is 9:00 am, end time is 10:00 am}.

[0094] Exemplarily, the first application function entity may receive the first information from the second application function entity. For example, the second application function entity may be a 5GMS application provider, and the 5GMS application provider may send the first information to the first application function entity during a provisioning session establishment process.

[0095] For example, in the process of creating a service activation session initiated by the 5GMS application provider to the 5GMS AF, the 5GMS application provider activates key features related to the corresponding 5GMS service to the first application function entity, such as dynamic policy adjustment, parameter / usage collection and reporting, network assistance, etc. Optionally, the 5GMS application provider can send the first information to the first application function entity while activating the key features related to the corresponding 5GMS service to the first application function entity.

[0096] It should be understood that the event opening function described in this application can be understood as the function of enabling the first application function entity to provide data to the outside, such as enabling the first application function entity to provide the collected terminal side data, usage data, log information and other data information to the network device (such as PCF or NEF or NWDAF, etc.) or other application function entities (such as 5GMS application provider or 5GMS AS).

[0097] S702: The first application function entity enables the event opening function according to the first information.

[0098] Among them, the first application function entity turning on the event opening function according to the first information can be understood as the first information being a trigger condition. After receiving the first information, the first application function entity turns on the event opening function according to the instruction of the first information.

[0099] Specifically, when the first information includes an event list, enabling the event exposure function by the first application function entity may include the first application function entity saving the event list, obtaining relevant data of the event indicated by the event list, and reporting the relevant data of the event (or subscription information) to the subscriber in response to the subscriber's event subscription request. After the first application function entity enables the event exposure function, the first application function entity may have data collection capabilities and data reporting capabilities (or the ability to expose the collected data to the outside world).

[0100] Furthermore, the first application function entity can also configure resources on demand (such as configuring the M2 interface between the 5GMS application provider and the 5GMS AS, and the M4 interface between the media stream processing function and the 5GMS AS), and report the service activation results and the address information of the 5GMS AS to the 5GMS application provider, so that the 5GMS application provider can provide the service content to the 5GMS AS through the M2 interface between the 5GMS application provider and the 5GMS AS based on the address information of the 5GMS AS.

[0101] Furthermore, after the first application function entity enables its own event opening function, the method may further include the following subscription process described in S703-S704:

[0102] S703: The first device sends an event subscription request to the first application function entity. Correspondingly, the first application function entity receives the event subscription request.

[0103] The first device may be a network device or other application function entity, such as an NEF, PCF, NWDAF, or other network device. Alternatively, the first device may be a third-party entity, a 5G MSAS, or a 5GMS application provider. It should be understood that the first device in this application may be referred to as a subscriber.

[0104] In an embodiment of the present application, an event subscription request can be used to request subscription to a certain event, such as subscribing to a first event (or referred to as a target event or subscription target, etc.), and the first event can be included in the events indicated by the above event list. Specifically, the event subscription request may include the ID of the first event and / or the description information of the first event. Optionally, the event subscription request may also include one or more of a subscription reporting period (i.e., the time period for the first application function entity to report subscription information), a preset trigger condition, a time period for the first device to request reporting of subscription information (which may be referred to as the second period in this application), subscriber identity information, application information, and security authentication information.

[0105] In an embodiment of the present application, the ID of the first event and / or the description information of the first event indicate the target event to which the subscriber (such as the first device) subscribes. The second period may be the time period for the first device to request reporting, that is, the time period during which the first device expects / requests the first application function entity to report relevant data of the event is the second period. The second period is the time period for reporting subscription information expected by the first device. The preset trigger condition defines the trigger condition for the first application function entity to send relevant data of the subscribed target event (or called subscription information) to the subscriber. For example, the preset trigger condition may include one or more of the conditions such as receiving / obtaining data reported by the target terminal, arrival of the data cache time, arrival of the subscription reporting period, or other event triggering. The target terminal can be set as needed without restriction. Once the data reported by the target terminal to the application-side entity is received, the data reported by the target terminal is opened to the first device.

[0106] In an embodiment of the present application, the data cache time may be included in the first information. Alternatively, the data cache time may be determined based on other parameters. In one example, the data cache time is determined based on the subscription reporting period, which is included in the event subscription request. For example, the data cache time may be equal to or greater than the subscription reporting period. Alternatively, the data cache time may be determined based on the subscription reporting period and the first period. For example, the data cache time may be equal to or greater than max{subscription reporting period, first period}, meaning that the data cache time may be equal to or greater than the longest period between the subscription reporting period and the first period.

[0107] In the embodiment of the present application, the first period may be the time period during which the source end of the data related to the first event (or the device that generates / collects the data related to the first event) sends the data related to the first event to the application-side device (such as the first application function entity). For example, taking the first event as the measurement collection of the terminal as an example, the first period may be the time period during which the terminal reports the measurement collection data to the first application function entity. Taking the first event as the recording of log information as an example, the first period may be the time period during which the application server reports the collected log information to the first application function entity.

[0108] In an embodiment of the present application, the subscription reporting period may be the time period during which the first application function entity notifies the first device of the relevant data of the acquired event, that is, the time period during which the first application function entity sends an event notification to the subscriber. For example, taking the measurement collection of the terminal as an example, the subscription reporting period may be the time period during which the first application function entity reports the measurement collection data of the terminal to the network side device (such as NEF or PCF, etc.). The subscription reporting period is indicated to the first application function entity by the first device in the event subscription request, and may also be determined based on the first period and the second period. Exemplarily, the subscription reporting period may be determined based on the first period and the second period, including: the subscription reporting period may be equal to the first period. Taking the measurement collection of the terminal as an example, the time period during which the terminal reports to the first application function entity is the same as the time period during which the first application function entity reports the measurement collection data of the terminal to the first device. Alternatively, the subscription reporting period may be equal to the second period, that is, the first application function entity reports the relevant data of the event subscribed by the first device (or subscription information) according to the first device's wishes and the time period desired by the first device.

[0109] It should be understood that the "when A" and "in the case of A" mentioned in this application are equivalent concepts, and both are understood as taking A as a trigger condition for something to happen. For example, "when the preset trigger condition is met" and "in the case of the preset trigger condition being met" are equivalent concepts, and both are trigger conditions for event reporting.

[0110] Exemplarily, when the first device wishes to subscribe to relevant data of the first event (or called relevant information), the first device queries the NRF for a device that can provide relevant data of the first event. For example, the NRF stores the correspondence between the event identifier and / or the event description information and the identifier of the device providing relevant data of the first event (such as the first application function entity). The first device sends a query request carrying the ID of the first event and / or the description information of the first event to the NRF. The NRF receives the query request and returns, based on the query request and the correspondence between the local storage, the identifier of the first application function entity that can provide / open relevant data of the first event to the outside world to the first device, so that the first device sends an event subscription request to the first application function entity based on the identifier of the first application function entity.

[0111] Optionally, the first device queries the NRF for a source end (such as a terminal or application server) that can provide relevant data of the first event, and notifies the first application function entity of the source end that provides the relevant data of the first event, so that the first application function entity obtains the relevant data of the first event from the source end. Furthermore, the NRF can also provide the identifier of the application to the first device, so that the first device notifies the first application function entity of the identifier of the application, so that the first application function entity obtains the relevant data of which applications on the terminal side.

[0112] Optionally, when the first information carries security authentication information, the first application function entity can also authenticate the legitimacy of the first device based on the security authentication information, and after the first device passes the security authentication, the first application function entity returns a subscription success message to the first device.

[0113] S704: The first application function entity sends relevant data of the first event to the first device according to the event subscription request.

[0114] It should be understood that the data related to the first event described in this application may be referred to as subscription information. The first application function entity sending the data related to the first event to the first device according to the event subscription request may include: obtaining the data related to the first event in response to the event subscription request, and sending the data related to the first event to the first device.

[0115] In one possible design, the first application function entity may cache relevant data of the first event. The first application function entity may respond to the event subscription request. When a preset trigger condition is met, the first application function entity determines to obtain relevant data of the first event from the local cache and sends the relevant data of the first event to the first device. In an embodiment of the present application, the first application function entity may send the relevant data of the first event to the first device after obtaining the relevant data of the first event from the local cache, or the first application function entity may send the relevant data of the first event to the first device according to the subscription reporting period.

[0116] Exemplarily, the first application function entity may receive a cache indication and cache data related to the first event according to the cache indication. The cache indication may be carried in the first information and may be used to instruct the first application function entity to cache data related to the first event, or the cache indication may be used to instruct the first application function entity to cache data, which may be data related to all events indicated by an event list, where the events indicated by the event list include the first event; the data may be all data reported by the terminal, all log information on the application side, etc., or may be the result of processing data reported by the terminal or application server.

[0117] Optionally, while caching the relevant data of the first event, the first application function entity may also send the obtained relevant data of the first event to other devices, such as sending the relevant data of the first event to a 5GMS application provider or a network quality of experience (QoE) server.

[0118] For example, assuming that the first application function entity is 5GMS AF, and the first event is the measurement and collection data of the terminal, 5GMSAF collects and reports (or opens to the outside world) the measurement and collection data of the terminal, which may include: the 5GMS application provider initiates the service activation session establishment process, and sends the characteristic information related to the 5GMS service, such as the characteristic information of the terminal measurement and collection data and the reporting data to the 5GMS AF, and the 5GMS AF determines the SAI based on the characteristic information sent by the 5GMS application provider, and returns the SAI or the index of the SAI to the 5GMS application provider. Subsequently, when the user accesses the media streaming service through the terminal, the terminal is triggered to obtain the SAI through the M8 or M5 interface, and the terminal (such as the MSH in the terminal) performs relevant configurations for measurement data collection according to the characteristic information in the obtained SAI, and performs measurement collection tasks (such as QoE measurement collection, etc.). The terminal sends a measurement report (or data report or measurement result) carrying the measurement collection data to the 5GMS AF according to the relevant configuration information in the SAI. The 5GMS AF receives the measurement report, obtains the measurement collection data therefrom, and saves / caches the obtained measurement collection data locally, and sends it to the subscriber when a subscriber (such as the first device described in this application) requests it.

[0119] Specifically, the possible design can refer to the following Figure 8 As described in the illustrated embodiment.

[0120] In another possible design, the relevant data of the first event or the relevant data of all events indicated by the event list are cached on devices other than the first application function entity, such as cached on a second device. The second device may be a 5GMS application provider. After receiving the event subscription request, the first application function entity may send an event subscription request to the second device on behalf of the subscriber. The second device may respond to the event subscription request. When the preset trigger condition is met, the second device determines to return the relevant data of the first event to the first application function entity, and then obtains the relevant data of the first event from the local cache, and returns the relevant data of the first event to the first application function entity, so that the first application function entity reports the relevant data of the first event from the second device to the first device.

[0121] Specifically, after the first application function entity or the first device or the second device obtains the relevant data of the first event, it can be cached, stored, or saved locally, depending on the implementation and is not limited in the examples of this application. Taking the first application function entity as an example, the first application function entity can locally cache the relevant data received for the first event. Subsequently, after the first application function entity obtains the relevant data of the first event from the local cache, it sends the relevant data of the first event to the first device. Alternatively, the first application function entity can obtain the relevant data of the first event from the local cache and send it to the first device according to the subscription reporting period.

[0122] Specifically, the method for determining the data cache time in this possible design is as described above and will not be elaborated on here.

[0123] For example, assuming that the first application function entity is 5GMS AF, the first event is the measurement and collection data of the terminal, and the second device is the 5GMS application provider, the 5GMS AF collects and reports (or opens to the outside world) the measurement and collection data of the terminal, which may include: the 5GMS application provider initiates the service activation session establishment process, and sends the characteristic information related to the 5GMS service, such as the characteristic information of the terminal measurement and collection data and the reporting data to the 5GMS AF, and the 5GMS AF determines the SAI based on the characteristic information sent by the 5GMS application provider, and returns the SAI or the index of the SAI to the 5GMS application provider. Subsequently, when the user accesses the media streaming service through the terminal, the terminal is triggered to obtain the SAI through the M8 or M5 interface, and the terminal (such as the MSH in the terminal) performs relevant configurations for measurement data collection according to the characteristic information in the obtained SAI, and performs measurement collection tasks (such as QoE measurement collection, etc.). The terminal sends a measurement report (or data report or measurement result) carrying the measurement collection data to the 5GMS AF according to the relevant configuration information in the SAI. The 5GMS AF receives the measurement report, obtains the measurement collection data from it and sends it to the 5GMS application provider or QoE server for storage. The 5GMS application provider or QoE server saves / caches the measurement collection data of the terminal locally. When a subscriber (such as the first device in this application) requests it, the 5GMS application provider returns the subscribed data to the 5GMS AF, and the 5GMS AF notifies the subscriber.

[0124] Specifically, the possible design can refer to the following Figure 9 As described in the illustrated embodiment.

[0125] based on Figure 7In the method, the first application function entity (such as 5GMS AF) can enable its own event opening function. After collecting / obtaining data, the first application function entity responds to the subscriber's event subscription request and sends / opens the collected / obtained data (or subscription information) to other devices (such as NWDAF, etc.), so that other devices can perform specific network analysis and decision-making based on the data reported by the first application function entity.

[0126] It is assumed that the first application function entity is 5GMS AF, the first device is NWDAF, the terminal is UE, the UE includes 5GMS perception application, MSH, MP, and the second application function entity is 5GMS application provider. Figure 8 The steps shown are Figure 7 The following process is introduced: 5GMS AF opens the external opening function, 5GMS AF locally stores the data collected and reported by the UE, and after the NWDAF initiates an event subscription request, it opens the terminal's measurement collection data or processed data to the NWDAF according to the open event requirements of the event subscription request. For example, Figure 5 As shown, the data is cached by 5GMS AF and made available to subscribers.

[0127] Figure 8 An event opening method is provided for the embodiment of the present application, such as Figure 8 As shown, this may include:

[0128] S801. The 5GMS application provider initiates a service provisioning session creation process to the 5GMS AF. For example, the 5GMS application provider sends a provisioning session to the 5GMS AF.

[0129] The service activation session creation process may refer to the existing technology and will not be described in detail.

[0130] It should be understood that the 5GMS application provider described in this application can be understood as a 5GMS application providing device, which is a device managed by an application service provider and is used to provide application content.

[0131] S802. In the service activation session creation process, the 5GMS application provider sends 5GMS feature information to the 5GMS AF. Correspondingly, the 5GMS AF receives the feature information.

[0132] The characteristic information may be used to indicate key characteristics related to 5GMS services, such as dynamic policy adjustment (used to adjust the network policy of the terminal, such as adjusting the QoS corresponding to the current service, etc.), parameter / usage collection and reporting (such as QoE reporting, etc.), network assistance (such as querying the network side for current network status information), etc. Optionally, the characteristic information may also include first information, which may include an event open indication and / or an event list, and may also include one or more of security authentication information, data cache time, cache indication, etc.

[0133] Specifically, the description of the first information and the parameters included in the first information is as described in S701 and will not be repeated here.

[0134] Further optionally, the 5GMS AF generates SAI configuration information related to the 5GMS service based on the received characteristic information, and the SAI configuration information is used to instruct the 5GMS client to perform relevant function configuration according to the SAI configuration information. Optionally, one SAI is assigned an index. The SAI index corresponds to the SAI.

[0135] S803.5 The GMS AF enables the event opening function according to the first information, and determines, according to the first information, to cache or store the corresponding terminal measurement and collection data when the terminal measurement and collection data is subsequently sent.

[0136] S804. Optionally, the 5GMS AF performs resource configuration on the 5GMS AS, that is, performs resource configuration on the M2 and M4 interfaces of the 5GMS AS. Specifically, the resource configuration process may refer to the existing technology and will not be described in detail.

[0137] S805.5GMS AF returns the service activation result and the address information of 5GMS AS to the 5GMS application provider.

[0138] The service activation result may carry SAI or an SAI index, etc.

[0139] The address information of the 5GMS AS may include the address of the M2 interface between the 5GMS AS and the 5GMS application provider, which is used by the 5GMS application provider to inject content into the 5GMS AS.

[0140] S806. When the UE starts a 5GMS application (such as on-demand or live broadcast of a media stream), the UE obtains the SAI, configures the client to collect parameters according to the parameter collection and reporting configuration of the SAI, and reports the parameter collection results according to the configuration information.

[0141] It should be understood that the UE obtaining SAI and performing corresponding data collection configuration and reporting based on SAI described in this application may refer to the MSH in the UE obtaining SAI and performing corresponding data collection configuration and reporting of measurement collection data results based on the parameter collection and reporting configuration in the SAI.

[0142] In one example, if during the service activation process, the 5GMS AF sends the index information of the SAI configuration to the 5GMS application provider, then the 5GMS application in the UE obtains the SAI index from the 5GMS application provider through the service notification message, and the 5GMS perception application in the UE sends the obtained SAI index to the MSH, and the MSH sends the SAI index to the 5GMS AF. The 5GMSAF returns the SAI to the MSH based on the received SAI index, thereby ensuring that the MSH obtains the SAI configuration information.

[0143] In another example, if during the service activation process, the 5GMS AF sends the complete SAI configuration information to the 5GMS application provider, then the 5GMS application in the UE directly obtains the SAI from the 5GMS application provider through the service notification message of the application layer, and sends the obtained SAI configuration to the MSH in the UE.

[0144] S807. The MSH in the UE performs UE-side data collection tasks based on the parameter collection and reporting configuration information obtained in the SAI configuration. For example, it performs UE-side QoE measurement and data collection tasks, and measures and collects relevant parameters based on the specific data collected in the configuration.

[0145] S808. The MSH in the UE measures and collects the corresponding parameters according to the parameter collection and reporting configuration information in the SAI configuration, and sends the data report (or parameter measurement report) carrying the measurement data collected by the client to the 5GMS AF side according to the reporting requirements in the configuration, such as periodic reporting or event-triggered reporting. In response, the 5GMS AF receives the data report carrying the measurement data.

[0146] Furthermore, the 5GMS AF caches or stores the measurement collection data in the data report locally based on the first information.

[0147] Optionally, according to the data cache time in the first information, the measurement collection data in the data packet is cached locally for the data cache time.

[0148] S809. Taking NWDAF as the subscriber as an example, NWDAF sends an event subscription request to 5GMS AF. Correspondingly, 5GMS AF receives the event subscription request.

[0149] Among them, Figure 7In the illustrated embodiment, the event subscription request can be used to subscribe to data related to a certain event, such as subscribing to measurement data collected by a terminal, etc. The event subscription request can carry one or more of a subscription reporting period, a second period, a preset trigger condition, and the like.

[0150] Optionally, the 5GMS AF can verify the legitimacy and validity of the NWDAF based on the security authentication information carried by the first information. If the NWDAF passes the security authentication and is legal; and if the event subscribed by the NWDAF is included in the measurement collection data of the UE or can be obtained based on the measurement collection data of the UE, then the event subscription request of the NWDAF is considered valid; then the 5GMS AF will return a subscription success message to the NWDAF, such as returning an acknowledgment message (ACK) to the NWDAF.

[0151] S810.5GMS AF determines the data cache time and continuously caches the data reported by the UE within the data cache time.

[0152] It should be understood that the data reported by the UE in this application may refer to the measurement and collection data of the UE, such as QoE measurement data.

[0153] Exemplarily, the 5GMS AF can determine the data cache time based on the time period for UE data reporting in the SAI (referred to as the first period in this application), such as the data cache time being greater than or equal to the time period for UE data reporting, to ensure that when a subscriber subscribes to data on the UE side, the AF side has the corresponding data cached. Alternatively, the data cache time is determined by the ASP and carried in the first information to indicate to the 5GMS AF; or the 5GMS AF determines the data cache time based on the subscription reporting period and / or the second period carried in the event subscription request, such as the data cache time being equal to the subscription reporting period or equal to the second period.

[0154] S811.5GMS AF caches the data received from the UE and sends the data reported by the UE to other devices, such as sending the data reported by the UE to the QoE server or the 5GMS application provider.

[0155] S812. When the reporting trigger conditions in the event subscription request sent by the subscriber (e.g., NWDAF) are met, such as when the subscription reporting period has arrived, the 5GMS AF reports the requested UE-side data to the NWDAF based on the locally cached UE measurement and collection data in accordance with the event subscription request. Accordingly, the NWDAF receives the UE-side data exposed by the 5GMS AF. Specifically, the UE-side data may be the locally cached UE measurement and collection data, or it may be data processed based on the UE measurement and collection data.

[0156] based on Figure 8 In the method shown, 5GMS AF enables its own external opening function, collects and caches the data reported by the UE, and opens the locally cached subscription information to other network elements (such as NWDAF) when subscribing.

[0157] Figure 8 In the method shown, the 5GMS AF caches the data and opens it to other network elements (such as NWDAF). Alternatively, other devices can cache the data, and the 5GMS AF acts as a subscription proxy entity. When other network elements or entities initiate a subscription to the 5GMS AF, the 5GMS AF can subscribe to other devices that cache or store UE-side data on behalf of the subscriber and obtain the data and indirectly open it to the subscriber, such as Figure 5 As shown, the 5GMS application provider caches or stores the data, and the 5GMS AF obtains the data from the 5GMS application provider and opens it to subscribers.

[0158] It is assumed that the first application function entity is 5GMS AF, the first device is NWDAF, the terminal is UE, the UE includes 5GMS perception application, MSH, MP, and the second application function entity is 5GMS application provider. Figure 9 The steps shown describe the process in which the 5GMS application provider stores the measurement data collected on the UE side, the 5GMS AF subscribes to the 5GMS application provider on behalf of the subscriber to obtain the data and opens it to the subscriber. Figure 9 An event opening method is provided for the embodiment of the present application, such as Figure 9 As shown, this may include:

[0159] S901. The 5GMS application provider initiates a service provisioning session creation process to the 5GMS AF. For example, the 5GMS application provider sends a provisioning session to the 5GMS AF.

[0160] Among them, S901 is the same as S801 and will not be described in detail.

[0161] S902. In the service activation session creation process, the 5GMS application provider sends feature information to the 5GMS AF. In response, the 5GMS AF receives the feature information.

[0162] Among them, S902 is the same as S802 and is not described in detail.

[0163] S903.5GMS AF enables the event opening function according to the first information.

[0164] S904. Optionally, the 5GMS AF performs resource configuration on the 5GMS AS, that is, performs resource configuration on the M2 and M4 interfaces of the 5GMS AS. Specifically, the resource configuration process may refer to the existing technology and will not be described in detail.

[0165] S905.5GMS AF returns the service activation result and the address information of 5GMS AS to the 5GMS application provider.

[0166] The service activation result may carry SAI or an SAI index, etc.

[0167] The address information of the 5GMS AS may include the address of the M2 interface between the 5GMS AS and the 5GMS application provider, which is used by the subsequent application provider to inject service content into the 5GMS AS, such as the 5GMS application provider injecting streaming media content into the 5GMS AS.

[0168] S906. When the UE starts a 5GMS application (for example, starting a video-on-demand or live broadcast of a media stream), the UE obtains the SAI, configures the client to collect parameters according to the parameter collection and reporting configuration in the SAI configuration information, and reports the parameter collection results according to the configuration information.

[0169] Among them, S906 is the same as S806 and is not described in detail.

[0170] S907. The MSH in the UE performs UE-side data collection tasks based on the parameter collection and reporting configuration information obtained in the SAI configuration, such as performing UE-side QoE measurement and data collection tasks, and measuring and collecting relevant parameters based on the specific data collected in the configuration.

[0171] S908. The MSH in the UE measures and collects the corresponding parameters according to the parameter collection and reporting configuration information in the SAI configuration, and sends the data report (or parameter measurement report) containing the measurement data collected by the client to the 5GMS AF according to the reporting requirements in the configuration, such as periodic reporting or event-triggered reporting. In response, the 5GMS AF receives the data report containing the measurement data.

[0172] S909. The 5GMS AF sends the measurement and collection data reported by the UE to the QoE server, such as the 5GMS application provider. Correspondingly, the 5GMS application provider receives and stores the measurement and collection data reported by the UE.

[0173] S910. Taking NWDAF as the subscriber as an example, NWDAF sends an event subscription request to 5GMS AF. Correspondingly, 5GMS AF receives the event subscription request from NWDAF. At this time, for 5GMS AF, the subscriber is NWDAF.

[0174] Among them, Figure 7 In the illustrated embodiment, an event subscription request can be used to subscribe to data related to a particular event, such as subscribing to measurement and collection data of a terminal or subscribing to data that can be processed based on the measurement and collection data of the terminal. The event subscription request can carry one or more of a subscription reporting period, a second period, a preset trigger condition, and the like.

[0175] S911.5GMS AF saves the first correspondence.

[0176] The first correspondence may include a correspondence between the identifier of the first device and the ID of the first event; or, the first correspondence may include a correspondence between a subscription ID and the ID of the first event, where the subscription ID is used to indicate that the first device initiated the subscription, that is, the subscription ID can be used to indicate which subscriber initiated the subscription to the relevant data of the first event. Based on the first correspondence, the 5GMS AF can notify the first device of the subscription notification information from the 5GMS application provider. The identifier of the first device can be used to identify the first device, where the first device can be an NWDAF.

[0177] Optionally, the 5GMS AF may verify the legitimacy of the NWDAF based on the security authentication information carried in the first information. If the NWDAF passes the security authentication and is legal, the 5GMS AF sends an event subscription request to the 5GMS application provider on behalf of the NWDAF, and the 5GMS AF saves the first corresponding relationship.

[0178] S912. The 5GMS AF sends an event subscription request to the 5GMS application provider. In response, the 5GMS application provider receives the event subscription request. At this point, for the 5GMS application provider, the subscriber is the 5GMS AF.

[0179] It should be understood that although the subscribers change for different receivers, the subscription information requested by the event subscription request remains unchanged, and the subscription is still to the relevant data of the first event.

[0180] Optionally, the triggering conditions of the event subscription request may change. For example, when NWDAF initiates an event subscription request to 5GMS AF, the subscription reporting period included is 20 minutes. When 5GMS AF subscribes to the 5GMS application provider on behalf of NWDAF, the defined subscription reporting period can be changed to 18 minutes.

[0181] S913. The 5GMS application provider determines whether the subscription event initiated by the 5GMS AF to the 5GMS application provider is valid and determines whether the corresponding event can be monitored.

[0182] Specifically, the 5GMS application provider determines whether the subscription event from the 5GMS AF is included in the UE's measurement collection data based on the measurement collection data from the UE. If included, it is determined that the subscription event initiated by the 5GMS AF to the 5GMS application provider is valid and the event can be monitored. Alternatively, if the 5GMS application provider determines that the event requested to be subscribed by the 5GMS AF can be obtained from the UE's measurement collection data, it is determined that the subscription event initiated by the 5GMS AF to the 5GMS application provider is valid and the event can be monitored.

[0183] S914. If the subscription event initiated by the 5GMS AF to the 5GMS application provider is determined to be valid, the 5GMS application provider replies with a subscription success message to the 5GMS AF. Otherwise, if the event is determined to be invalid, the 5GMS application provider replies with a subscription failure message to the 5GMS AF.

[0184] S915.5: The GMS AF sends the subscription result to the NWDAF according to the first correspondence stored in S911.

[0185] The subscription result may include a subscription success message or a subscription failure message.

[0186] S916. The MSH in the UE performs relevant parameter measurement and collection according to the parameter collection and reporting configuration in the SAI configuration, and sends a data report carrying the measurement and collection data to the 5GMS AF according to the configuration. In response, the 5GMS AF receives the data report carrying the measurement and collection data.

[0187] S917.5GMS AF sends the data received from the UE to other devices, such as the QoE server or 5GMS application provider. Correspondingly, the 5GMS application provider receives and stores the UE data (or the measurement data collected by the UE).

[0188] S918.5GMS application provider determines that the preset trigger condition is met, such as the trigger condition in the event subscription request sent by 5GMS AF instead of NWDAF has been met. Specifically, the subscription reporting period timer in the event subscription request has timed out or the event trigger condition is the arrival of measurement collection data reported by the UE.

[0189] S919. The 5GMS application provider sends the requested subscription data to the 5GMS AF based on the subscription event in the event subscription request and the locally cached UE measurement data. In response, the 5GMS AF receives the subscribed UE-side data.

[0190] S920. The 5GMS AF sends the subscribed UE-side data in the event subscription request to the NWDAF. Correspondingly, the NWDAF receives the subscribed UE-side data sent by the 5GMS AF.

[0191] based on Figure 9 In the method shown, 5GMS AF enables its own external opening function, collects data reported by UE and sends it to 5GMS application provider, which then notifies the subscription information for the event subscription request. The existing service activation process is enhanced, with 5GMS application provider providing capability exposure configuration information to enable 5GMS AF to send event subscription request messages from subscribing network elements or entities to 5GMS application provider after completing security authentication of the subscribed network element or entity. 5GMS application provider then provides application subscription message notification. 5GMS AF acts only as a proxy entity, responsible for opening the data stored locally by the 5GMS application provider to other network elements (such as NWDAF) that initiate subscriptions.

[0192] In the embodiment of the present application, a subscription parameter negotiation mechanism is also provided, such as the negotiation of subscription reporting period of subscription information. The subscription parameter negotiation mechanism can be applied to the above Figure 7-Figure 9 In any of the schemes shown. The subscription parameter negotiation mechanism can make the subscription reporting period of the subscription information consistent with the terminal side data collection subscription reporting period by mutually negotiating the subscription reporting period, or use the terminal side data collection result reporting as the trigger condition for the subscription information reporting, so that after the data is reported to the first application function entity (such as 5GMS AF), it is sent to the QoE server or 5GMS application provider at the same time, and the subscription trigger condition is met, and the subscribed event is notified to the subscriber based on the measurement and collection data on the UE side.

[0193] Specifically, the subscription parameter negotiation mechanism may include the first application function entity and the subscriber (which may be referred to as the first device in this application) negotiating the subscription reporting period or subscription notification period of the subscription information through signaling interaction, so that the subscription reporting period is determined according to the first period and the second period, for example, the subscription reporting period may be the first period or the subscription reporting period is the second period, etc. Alternatively, the two parties negotiate to report the terminal-side data collection result as a trigger condition for reporting the subscription information, that is, reporting the terminal-side data collection result as one of the above-mentioned preset trigger conditions, and receiving the terminal-side data collection result means opening the subscription event to the first device.

[0194] It is assumed that the first application function entity is 5GMS AF, the first device is NWDAF, the terminal is UE, the UE includes 5GMS perception application, MSH, MP, and the second application function entity is 5GMS application provider. Figure 10 The steps shown introduce the subscription parameter negotiation mechanism described in this application.

[0195] Figure 10 An event opening method is provided for the embodiment of the present application, such as Figure 10 As shown, this may include:

[0196] S1001. The 5GMS application provider initiates a service provisioning session creation process to the 5GMS AF. For example, the 5GMS application provider sends a provisioning session to the 5GMS AF.

[0197] Among them, S1001 is the same as S801 and will not be described in detail.

[0198] S1002. In the service activation session creation process, the 5GMS application provider sends feature information to the 5GMS AF. In response, the 5GMS AF receives the feature information.

[0199] Among them, S1002 is the same as S802 and will not be described in detail.

[0200] S1003.5 The GMS AF enables an event opening function according to the first information, and determines, according to the first information, to cache or store the corresponding terminal measurement and collection data when the terminal device subsequently sends the measurement and collection data.

[0201] S1004. Optionally, the 5GMS AF performs resource configuration on the 5GMS AS, that is, performs resource configuration on the M2 and M4 interfaces of the 5GMS AS. Specifically, the resource configuration process may refer to the existing technology and will not be described in detail.

[0202] S1005.5GMS AF returns the service activation result and the address information of 5GMS AS to the 5GMS application provider.

[0203] The service activation result may carry SAI or an SAI index, etc.

[0204] The address information of the 5GMS AS may include the address of the M2 interface between the 5GMS AS and the 5GMS application provider, which is used by the 5GMS application provider to inject content into the 5GMS AS.

[0205] S1006. The UE has 5GMS service requirements (such as on-demand or live broadcast of a media stream), the UE obtains the SAI, and performs corresponding data collection, configuration, and reporting based on the SAI.

[0206] Among them, S1006 is the same as S806 and is not described in detail.

[0207] S1007. The MSH in the UE performs UE-side data collection tasks based on the acquired SAI, such as performing UE-side QoE measurement and data collection tasks.

[0208] S1008. The MSH in the UE measures and collects relevant parameters according to the specific measurement and collection data in the parameter collection and reporting configuration information within the SAI configuration, and sends a data report carrying the measurement and collection data to the 5GMS AF according to the reporting configuration. In response, the 5GMS AF receives the data report carrying the measurement and collection data.

[0209] S1009. The 5GMS AF sends the data reported by the UE to the QoE server, such as the 5GMS application provider. In response, the 5GMS application provider receives and stores the measurement data reported by the UE.

[0210] S1010. Taking NWDAF as the subscriber as an example, NWDAF sends an event subscription request to 5GMS AF. Correspondingly, 5GMS AF receives the event subscription request. At this time, for 5GMS AF, the subscriber is NWDAF.

[0211] Among them, Figure 7 In the illustrated embodiment, the event subscription request can be used to subscribe to data related to a certain event, such as subscribing to measurement data collected by a terminal, etc. The event subscription request can carry one or more of a subscription reporting period, a second period, a preset trigger condition, and the like.

[0212] S1011.5GMS AF determines the legitimacy and validity of the subscription event initiated by NWDAF and determines whether the corresponding event can be monitored.

[0213] Optionally, the 5GMS AF may verify the legitimacy of the NWDAF based on the security authentication information carried in the first information, and determine the validity of the subscription event initiated by the NWDAF, that is, whether the subscribed event is included in the measurement and collection data of the UE or whether it can be obtained based on the measurement and collection data of the UE. If the NWDAF passes the security authentication and is legitimate, and the initiated subscription event is valid, the 5GMS AF further saves the first corresponding relationship.

[0214] The first correspondence may include a correspondence between the identifier of the first device and the ID of the first event; or, the first correspondence may include a correspondence between a subscription ID and the ID of the first event, where the subscription ID is used to indicate that the first device initiated the subscription, i.e., the subscription ID can be used to indicate which subscriber initiated the subscription for data related to the first event. The identifier of the first device may be used to identify the first device, where the first device may be an NWDAF.

[0215] S1012.5GMS AF determines the subscription reporting cycle.

[0216] Exemplarily, the 5GMS AF can determine the subscription reporting period based on the UE side data reporting period (such as the first period described in this application) and the period requested by the subscriber to report (such as the second period), and set the subscription reporting period to the first period, or set the subscription reporting period to the second period.

[0217] S1013. Optionally, if the 5GMS AF determines that the subscription reporting period is inconsistent with the reporting period requested by the subscriber (such as the second period), the 5GMS AF returns a subscription failure message, which carries the failure reason, the recommended subscription reporting period or the triggering event.

[0218] Among them, the recommended subscription reporting period can be consistent with the UE-side data collection and reporting period, that is, the recommended reporting period is the first period. Alternatively, the trigger condition is set to event triggering, that is, the UE-side reported data is used as the trigger condition. If the subscriber can accept the subscription reporting period and / or trigger condition recommended by the 5GMS AF, it will subscribe again, indicating acceptance of the subscription reporting period and / or trigger condition recommended by the 5GMS AF. At this point, the subscription parameter negotiation between the 5GMS AF and the NWDAF is completed. It should be understood that in the embodiment of the present application, the subscriber can also indicate acceptance of the subscription reporting period and / or trigger condition recommended by the 5GMS AF in other forms, and the specific form is not limited.

[0219] S1014. After the 5GMS AF receives the event subscription request initiated again by the NWDAF and the subscription parameter negotiation is completed, the 5GMS AF sends a subscription success message to the NWDAF.

[0220] S1015. The MSH in the UE measures and collects relevant parameters based on the specific measurement and collection data in the parameter collection and reporting configuration information within the SAI configuration, and sends a data report carrying the measurement and collection data to the 5GMS AF based on the reporting configuration. In response, the 5GMS AF receives the data report carrying the measurement and collection data.

[0221] S1016.5GMS AF sends the data received from the UE to other devices, such as sending the data reported by the UE to the QoE server or 5GMS application provider.

[0222] S1017.5 The GMS AF determines that a preset trigger condition of the subscriber is met, such as expiration of a subscription reporting period timer, or an event trigger condition is arrival of measurement collection data reported by the UE.

[0223] S1018. The 5GMS AF sends the UE-side data requested / subscribed in the event subscription request to the NWDAF. Correspondingly, the NWDAF receives the subscribed UE-side data reported by the 5GMS AF.

[0224] based on Figure 10 In the method shown, 5GMS AF enables its own external openness function, collects and caches the data reported by the UE, and reports the locally cached subscription information to other network elements (such as NWDAF) when subscribing. The existing service activation process is enhanced to enable 5GMS AF to negotiate subscription parameters after completing security authentication of the subscription network element or entity, align the reporting period with the period requested by the subscriber, or use data reporting events as subscription trigger conditions. Subsequently, 5GMSAF receives the data collection and reporting results from the UE side and sends a notification message to the subscriber.

[0225] The above mainly introduces the solution provided by the embodiment of the present application from the perspective of interaction between various network elements. Accordingly, the embodiment of the present application also provides a communication device, which can be the first application function entity in the above embodiment, or a device including the first application function entity, or a component that can be used for the first application function entity. It can be understood that, in order to implement the above functions, the communication device includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should easily realize that, in combination with the units and algorithm steps of the various examples described in the embodiments disclosed herein, the present 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 by computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0226] In the embodiment of the present application, the first application function entity can be divided into functional modules according to the above method example. For example, each functional module can be divided according to each function, or two or more functions can be integrated into one processing module. The above integrated modules can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of modules in the embodiment of the present application is schematic and is only a logical functional division. In actual implementation, there may be other division methods.

[0227] Figure 11 The structure diagram of a communication device 110 is shown. The communication device 110 can be a first application function entity, or a chip in the first application function entity, or a system on a chip. The communication device 110 can be used to perform the functions of the first application function entity involved in the above embodiment. As an implementation method, Figure 11 The communication device 110 shown includes: a transceiver unit 1101, a processing unit 1102;

[0228] The transceiver unit 1101 is configured to obtain first information for instructing a first application function entity to enable an event opening function.

[0229] The processing unit 1102 is configured to enable an event opening function according to the first information.

[0230] The transceiver unit 1101 is also used to receive an event subscription request from the first device for requesting to subscribe to relevant data of the first event, and send relevant data of the first event to the first device according to the event subscription request, so that the application side entity can open up to the outside world and obtain relevant data of a certain event.

[0231] Specifically, the above Figure 7-10 All relevant contents of each step involved in the method embodiment can be referred to the functional description of the corresponding functional module, and will not be repeated here. Figure 7-10 The method shown in the figure has the functions of the first application function entity in the event opening method, so it can achieve the same effect as the above event opening method. For example, the transceiver unit 1101 supports the communication device 110 to execute S701, S703 and S704, and the processing unit 1102 supports the communication device 110 to execute S702, etc.

[0232] As another possible implementation method, Figure 11The communication device 110 shown includes: a processing module and a communication module. The processing module is used to control and manage the actions of the communication device 110. For example, the processing module can support the communication device 110 to perform control functions, such as executing step 1201. The communication module can integrate the functions of the transceiver unit 1101 and can be used to support the communication device 110 to execute steps 1200 and 1600 and communicate with other network entities, such as Figure 3 The communication device 110 may further include a storage module for storing program codes and data of the communication device 110 .

[0233] Among them, the processing module can be a processor or a controller. It can implement or execute various exemplary logic blocks, modules and circuits described in conjunction with the disclosure of this application. The processor can also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of DSP and microprocessors, etc. The communication module can be a transceiver circuit or a communication interface, etc. The storage module can be a memory. When the processing module is a processor, the communication module is a communication interface, and the storage module is a memory, the communication device 110 involved in the embodiment of the present application can be Figure 6 Communication device 600 is shown.

[0234] The embodiment of the present application provides a communication system, which includes the aforementioned first application function entity and a first device (such as PCF or NWDAF, etc.), wherein the first application function entity executes Figure 7-10 A method for a first application function entity (such as a 5GMS AF) in any of the embodiments shown.

[0235] The present application also provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program. When the computer program is executed by a computer, the computer can implement the above method embodiment. Figure 7-10 The relevant process executed by the first application function entity (such as 5GMS AF) in any of the embodiments shown.

[0236] The present application also provides a computer program product for storing a computer program. When the computer program is executed by a computer, the computer can implement the above method embodiment. Figure 7-10 The relevant process executed by the first application function entity (such as 5GMS AF) in any of the embodiments shown.

[0237] The present application also provides a chip, including a processor. The processor is used to read and run a computer program stored in a memory to execute the corresponding operations and / or processes performed by the first application function entity in the event opening method provided by the present application. Optionally, the chip also includes a memory, which is connected to the processor through a circuit or wire, and the processor is used to read and execute the computer program in the memory. Further optionally, the chip also includes a communication interface, and the processor is connected to the communication interface. The communication interface is used to receive processed data and / or information, and the processor obtains the data and / or information from the communication interface and processes the data and / or information. The communication interface can be an input / output interface, interface circuit, output circuit, input circuit, pin or related circuit on the chip. The processor can also be embodied as a processing circuit or a logic circuit. The above-mentioned chip can also be replaced by a chip system, which will not be repeated here.

[0238] The terms "comprises" and "having" and any variations thereof in this application are intended to cover non-exclusive inclusions. For example, a process, method, system, product or apparatus that includes a series of steps or elements is not necessarily limited to those steps or elements expressly listed but may include other steps or elements not expressly listed or inherent to such process, method, product or apparatus.

[0239] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0240] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0241] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0242] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. The purpose of this embodiment can be achieved by selecting some or all of these units based on actual needs.

[0243] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0244] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0245] In addition, the terms "first" and "second" in the specification, claims, and drawings of this application are used to distinguish different objects, rather than to describe a specific order. In addition, the terms "including" and "having," and any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, product, or device that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units that are not listed, or may optionally include other steps or units that are inherent to the process, method, product, or device.

[0246] Although the present application has been described with reference to specific features and embodiments thereof, it is apparent that various modifications and combinations may be made thereto without departing from the spirit and scope of the present application. Accordingly, this specification and the drawings are merely illustrative of the present application as defined by the appended claims and are deemed to cover any and all modifications, variations, combinations or equivalents within the scope of the present application. Obviously, those skilled in the art may make various modifications and variations to the present application without departing from the spirit and scope of the present application. Thus, the present application is intended to include such modifications and variations as fall within the scope of the claims of the present application and their equivalents.

[0247] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any modifications or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in the present invention should be included within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be based on the scope of protection of the claims.

Claims

1. An event opening method, characterized in that: The method comprises: The first application function entity obtains first information; wherein the first information is used to instruct the first application function entity to enable an event opening function, and the first information includes security authentication information, and the security authentication information is used by the first application function entity to verify whether the first device is legitimate; The first application function entity enables an event opening function according to the first information; The first application function entity receives an event subscription request from the first device; wherein the event subscription request is used to request subscription to relevant data of the first event; When the first application function entity determines that the first device is legitimate according to the security authentication information, the first application function entity sends a subscription success message to the first device, where the subscription success message is used to indicate that the first device has successfully subscribed to the first event; The first application function entity sends relevant data of the first event to the first device according to the event subscription request.

2. The method according to claim 1, characterized in that The first information includes an event opening indication and / or an event list; The event list is used to indicate open events, and the event list includes one or more of an identification ID of the open event and description information of the open event.

3. The method according to claim 2, characterized in that The open event includes one or more of measurement and collection data of the terminal and log information of the application server.

4. The method according to any one of claims 1 to 3, characterized in that The first application function entity sending data related to the first event to the first device includes: When the preset trigger conditions are met, the first application function entity sends relevant data of the first event to the first device; wherein the preset trigger conditions include one or more of the data cache time reaching, the subscription reporting cycle reaching, and the data reported by the target terminal being received.

5. The method according to claim 4, characterized in that The data cache time is carried in the first information; or, The data cache time is determined according to the subscription reporting cycle; or, The data cache time is determined according to a first period and the subscription reporting period, where the first period is a time period during which a source end of the relevant data of the first event reports the relevant data of the first event to the first application function entity.

6. The method according to claim 4, characterized in that The subscription reporting period is determined based on a first period and a second period; wherein the first period is the time period during which the source end of the relevant data of the first event reports the relevant data of the first event to the first application function entity; and the second period is the time period during which the first device requests reporting.

7. The method according to claim 6, characterized in that: The subscription reporting period is the first period; or, The subscription reporting period is the second period.

8. The method according to any one of claims 1 to 3, characterized in that The method further comprises: The first application function entity obtains relevant data of the first event from a local cache.

9. The method according to claim 8, characterized in that The method further comprises: The first application function entity receives a cache indication, and according to the cache indication, obtains and caches relevant data of the first event, wherein the first information carries the cache indication, and the cache indication is used to instruct the first application function entity to cache relevant data of an open event, wherein the open event includes the first event.

10. The method according to any one of claims 1 to 3, characterized in that The method further comprises: The first application function entity sends the event subscription request to the second device; The first application function entity receives data related to the first event from the second device.

11. The method according to claim 10, characterized in that The first application function entity sending data related to the first event to the first device includes: The first application function entity sends relevant data of the first event to the first device according to a first corresponding relationship, where the first corresponding relationship is used to indicate that the network element subscribing to the first event is the first device.

12. The method according to claim 11, characterized in that The first corresponding relationship includes a corresponding relationship between the identifier of the first device and the ID of the first event; or, The first corresponding relationship includes a corresponding relationship between a subscription ID and an ID of the first event, wherein the subscription ID is used to indicate that the first device initiates a subscription.

13. The method according to any one of claims 1 to 3, characterized in that The first application function entity includes a fifth-generation media stream application server 5GMS AS or a fifth-generation media stream application function 5GMS AF.

14. A communication system, characterized in that: The communication system includes: a first application function entity and a first device; The first application function entity is configured to obtain first information and enable an event disclosure function based on the first information; wherein the first information is used to instruct the first application function entity to enable the event disclosure function, and the first information includes security authentication information, and the security authentication information is used by the first application function entity to verify whether the first device is legitimate; The first device is configured to send an event subscription request to the first application function entity; wherein the event subscription request is used to request subscription to relevant data of the first event; The first application function entity is further configured to receive the event subscription request, and send relevant data of the first event to the first device according to the event subscription request; The first application function entity is further configured to, if it is determined according to the security authentication information that the first device is legitimate, send a subscription success message to the first device, where the subscription success message is used to indicate that the first device has successfully subscribed to the first event; The first device is further configured to receive data related to the first event.

15. A communication device, characterized in that: The communication device includes a processor and a communication interface, and the processor and the communication interface are used to support the communication device to execute the method according to any one of claims 1 to 13.

16. A computer-readable storage medium, characterized in that in, The computer-readable storage medium stores computer instructions, and when the computer instructions are executed on a computer, the computer is caused to perform the method according to any one of claims 1 to 13.

17. A computer program product, characterized in that in, The computer program product comprises computer instructions, and when the computer instructions are run on a computer, the computer is caused to perform the method according to any one of claims 1 to 13.

18. A chip, characterized in that: The chip includes a processor and a memory, wherein the processor is coupled to the memory. When the processor executes computer program instructions, the method according to any one of claims 1 to 13 is implemented.

Images