Data acquisition method, device and equipment and readable storage medium

Abstract

The invention provides a data acquisition method and device, equipment and a storage medium. A first communication device can acquire data corresponding to address information of a session of a terminal device in historical time. The data acquisition method comprises: a first communication device acquires first information of a terminal device, the first information being used for indicating address information of a session of the terminal device at historical time, the session comprising a session in which the terminal device reports data to the first communication device; and the first communication equipment acquires data of the terminal equipment at first time according to the first information, and the first time is overlapped with historical time.

Description

Technical Field

[0001] The present application relates to the field of communications, and more specifically, to a method, apparatus, device and readable storage medium for acquiring data. Background Art

[0002] In some communication mechanisms, due to certain needs, such as data analysis needs, data consumers such as the network data analytics function (NWDAF) in the network need to use data agents, such as the data collection application function (DCAF) to request data related to the terminal device. For example, NWDAF obtains data related to the terminal device from DCAF based on the terminal device identifier. DCAF requests and obtains data from the corresponding terminal device. The data is uploaded to DCAF through a user plane session, and the data is indexed by the address of the terminal device, such as the Internet Protocol (IP) address. Therefore, there is a need for DCAF to map the identifier of the terminal device to the address information of the terminal device.

[0003] In the related art, before DCAF obtains data from a terminal device, it is assumed that the user plane session of the terminal device already exists and has not been released, that is, the IP address corresponding to the user plane session of the terminal device has always existed and has not changed. When DCAF has a need to obtain data, it can immediately use the session and IP address to obtain data from the corresponding terminal device. However, there are some scenarios where, when the session of a terminal device is released or changed, the IP address assigned to the terminal device is deleted or changed, or even assigned to other terminal devices for use, DCAF cannot correctly obtain the corresponding terminal device historical data based on the original IP address. Summary of the invention

[0004] The present application provides a data acquisition method, apparatus, device and storage medium, which can enable a first communication device to acquire data corresponding to address information of a session of a terminal device at a historical time.

[0005] In a first aspect, a data acquisition method is provided, comprising:

[0006] The first communication device acquires first information of a terminal device, where the first information is used to indicate address information of a session of the terminal device at a historical time, wherein the session includes a session in which the terminal device reports data to the first communication device;

[0007] The first communication device obtains data of the terminal device at a first time according to the first information, and the first time overlaps with the historical time.

[0008] In a second aspect, a data acquisition method is provided, comprising:

[0009] The second communication device acquires first information of the terminal device, where the first information is used to indicate address information of a session of the terminal device at a historical time, wherein the session includes a session in which the terminal device reports data to the first communication device;

[0010] The second communication device sends the first information to the first communication device.

[0011] A third aspect provides a data acquisition method, comprising:

[0012] The consumer device sends a second request message to the first communication device, where the second request message includes first time information, and the second request message is used to obtain data of the terminal device at the first time;

[0013] The consumer device receives a response message from the first communication device, and the response message includes data of the terminal device at the first time; the data of the terminal device at the first time is obtained based on first information of the terminal device, and the first information is used to indicate address information of the session of the terminal device at a historical time.

[0014] In a fourth aspect, a data acquisition device is provided, comprising:

[0015] A first acquiring unit, configured to acquire first information of a terminal device, wherein the first information is used to indicate address information of a session of the terminal device at a historical time, wherein the session includes a session in which the terminal device reports data to a first communication device;

[0016] A second acquisition unit is configured to acquire data of the terminal device at a first time according to the first information, where the first time overlaps with the historical time.

[0017] In a fifth aspect, a data acquisition device is provided, comprising:

[0018] an acquiring unit, configured to acquire first information of a terminal device, wherein the first information is used to indicate address information of a session of the terminal device at a historical time, wherein the session includes a session in which the terminal device reports data to a first communication device;

[0019] A sending unit, configured to send the first information to the first communication device.

[0020] In a sixth aspect, a data acquisition device is provided, comprising:

[0021] A sending unit, configured to send a second request message to the first communication device, wherein the second request message includes first time information, and the second request message is used to obtain data of the terminal device at the first time;

[0022] A receiving unit is used to receive a response message from the first communication device, the response message including the data of the terminal device at the first time; the data of the terminal device at the first time is obtained based on the first information of the terminal device, and the first information is used to indicate the address information of the session of the terminal device at a historical time.

[0023] In the seventh aspect, a communication device is provided, comprising: a processor and a memory, wherein the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the method provided in any one of the first to third aspects above.

[0024] In an eighth aspect, a computer-readable storage medium is provided for storing a computer program, wherein the computer program enables a computer to execute the method provided in any one of the first to third aspects above.

[0025] In a ninth aspect, a chip is provided, comprising a processor, wherein the processor is used to call and run a computer program from a memory so that the chip executes the method provided in any one of the first to third aspects above.

[0026] In the tenth aspect, a computer program product is provided, comprising a computer program / instruction, which, when executed by a processor, implements the steps of the method provided in any one of the first to third aspects above.

[0027] The embodiment of the present application associates the address information of the session through which the terminal device reports data to the first communication device with the historical time, so that the first communication device can obtain the data of the terminal device at the first time based on the address information of the session of the terminal device at the historical time, thereby enabling the first communication device to obtain the data corresponding to the address information of the session of the terminal device at the historical time. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] Figure 1 is a schematic diagram of a communication system applicable to an embodiment of the present application;

[0029] Figure 2 is a schematic diagram of a network architecture applicable to an embodiment of the present application;

[0030] Figure 3 It is a schematic diagram of the process of providing terminal device related data to NWDAF;

[0031] Figure 4 It is a schematic diagram of the process of obtaining the UE IP address corresponding to the UE ID;

[0032] Figure 5 is a schematic diagram of a process in which a UE IP address is released in a communication scenario;

[0033] Figure 6 is a schematic flow chart of a data acquisition method provided in an embodiment of the present application;

[0034] Figure 7 is a schematic flow chart of another data acquisition method provided in an embodiment of the present application;

[0035] Figure 8 is a schematic flow chart of another data acquisition method provided in an embodiment of the present application;

[0036] Fig. 9 is a schematic flow chart of another data acquisition method provided in an embodiment of the present application;

[0037] Fig.10 is a schematic flow chart of another data acquisition method provided in an embodiment of the present application;

[0038] Fig.11 is a schematic flow chart of another data acquisition method provided in an embodiment of the present application;

[0039] Fig.12 is a schematic diagram of a data acquisition device according to an embodiment of the present application;

[0040] Fig.13 is a schematic diagram of another data acquisition device according to an embodiment of the present application;

[0041] Fig.14 is a schematic diagram of another data acquisition device according to an embodiment of the present application;

[0042] Fig.15 It is a schematic diagram of an electronic device according to an embodiment of the present application. DETAILED DESCRIPTION

[0043] The technical solution in this application will be described below in conjunction with the accompanying drawings.

[0044] The technical solutions of the embodiments of the present application can be applied to various communication systems, for example, global system for mobile communications (GSM) system, code division multiple access (CDMA) system, wideband code division multiple access (WCDMA) system, general packet radio service (GPRS), long term evolution (LTE) system, system architecture evolved (SAE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD), universal mobile telecommunication system (UMTS), worldwide interoperability for microwave access (WiMAX) communication system, fifth generation (5G) system or new radio (NR), and subsequent evolution communication systems.

[0045] Figure 1 A schematic diagram of a communication system according to an embodiment of the present application is shown. Figure 1 The system includes a terminal device 110, an access network device 120 and a core network device 130. The terminal device 110 is connected to the access network device 120, and the access network device 120 is connected to the core network device 130, so that the terminal device 110 can communicate with the core network device 130 through the access network device 120.

[0046] Among them, the terminal device 110 in the embodiment of the present application can also be called: user equipment (UE), mobile station (MS), mobile terminal (MT), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent or user device, etc.

[0047] The terminal device 110 may be a device that provides voice / data connectivity to a user, such as a handheld device or a vehicle-mounted device with a wireless connection function. At present, some examples of terminals are: mobile phones, tablet computers, laptop computers, PDAs, mobile internet devices (MIDs), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in autonomous driving, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, vehicle-mounted devices, wearable devices, terminal devices in 5G networks or evolved public land mobile communication networks (public land mobile For example, the terminal device 110 is used to receive a paging message from the access network device 120.

[0048] As an example and not a limitation, in the embodiments of the present application, wearable devices may also be referred to as wearable smart devices, which are a general term for wearable devices that are intelligently designed and developed by applying wearable technology to daily wear, such as glasses, gloves, watches, clothing, and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothes or accessories. Wearable devices are not only hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include full-featured, large-sized, and independent of smartphones to achieve complete or partial functions, such as smart watches or smart glasses, as well as devices that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various types of smart bracelets and smart jewelry for vital sign monitoring.

[0049] In addition, in the embodiment of the present application, the terminal device 110 can also be a terminal device in the Internet of Things (IoT) system. IoT is an important part of the future development of information technology. Its main technical feature is to connect objects to the network through communication technology, thereby realizing an intelligent network that interconnects people and machines and things.

[0050] The various terminal devices 110 introduced above, if located on a vehicle (eg placed in or installed in a vehicle), can be considered as vehicle-mounted terminal devices, which are also called on-board units (OBU).

[0051] In the embodiment of the present application, the access network device 120 is a device in a radio access network ((radio) access network, (R)AN), or in other words, a RAN node that connects a terminal device to a wireless network, or a device in a next generation radio access network (NG-RAN). For example, as an example but not a limitation, the access network device 120 may include: gNB, transmission reception point (TRP), evolved Node B (eNB), radio network controller (RNC), Node B (NB), base station controller (BSC), base transceiver station (BTS), home base station (e.g., home evolved NodeB, or home Node B, HNB), base band unit (BBU), or wireless fidelity (Wifi) access point (AP), etc.

[0052] In a network structure, the access network device 120 may include a centralized unit (CU) node, a distributed unit (DU) node, or a RAN device including a CU node and a DU node, or a RAN device including a control plane CU node (CU-CP node) and a user plane CU node (CU-UP node) and a DU node.

[0053] The access network device 120 provides services for the cell, and the terminal device 110 communicates with the access network device 120 through the transmission resources used by the cell (for example, frequency domain resources, or spectrum resources). The cell may be a cell corresponding to the access network device 120 (for example, a base station). The cell may belong to a macro base station or a base station corresponding to a small cell. The small cells here may include: metro cells, micro cells, picocells, femto cells, etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.

[0054] The core network device 130 is used to manage one or more access network devices 120. For example, the core network device 130 is used to send information used by the access network device to send a paging message to the access network device 120. For example, the core network device 130 may include at least one of a core access and mobility management function (AMF), a user plane function (UPF) network element, a session management function (SMF) network element, a data network (DN), a unified data repository (UDR), or a unified data management (UDM).

[0055] It should be understood that Figure 1 A core network device 130, an access network device 120 and a terminal device 110 are shown by way of example. In some embodiments, the communication system may include other numbers of core network devices, access network devices or terminal devices, which is not limited in the embodiments of the present application.

[0056] Figure 2 A schematic diagram of a network architecture applicable to an embodiment of the present application is shown. The network architecture is a 5G network architecture diagram defined by the 3rd Generation Partnership Project (3GPP). It should be understood that the network architecture may also include more, fewer or different functional components without limitation.

[0057] Among them, the access and mobility management function (AMF) is responsible for access and mobility management functions, and its main functions include managing user registration, reachability detection, SMF node selection, mobile state transition management, etc. Among them, AMF can communicate with UE through the N1 interface and communicate with (R)AN through the N2 interface.

[0058] The session management function (SMF) is responsible for session management functions, and its main functions are to control the establishment, modification and deletion of sessions, the selection of user plane nodes, etc. Among them, SMF can communicate with UPF through the N4 interface.

[0059] The user plane function (UPF) mainly provides user plane support, and its main functions are packet routing and forwarding, serving as a session anchor, serving as an uplink classifier to support routing service flows to the local data network, serving as a branch point to support multi-homed PDU sessions, etc. (R)AN and UPF can communicate through the N3 interface, and UPFs can communicate with each other through the N9 interface.

[0060] The policy control function (PCF) is responsible for user policy management. Its main function is to serve as a policy decision point, providing rules such as detection based on service data flows or applications, quality of service (QoS), and flow-based charging control. It also provides policies to AMF and SMF, such as slice selection policy to AMF and session management policy to SMF.

[0061] The main function of unified data management (UDM) is to store user data, such as contract information, authentication / authorization information, etc.

[0062] The authentication server function (AUSF) is an authentication and authorization service module responsible for authenticating and authorizing UE access.

[0063] The application function (AF) interacts with the 3GPP core network to provide services to affect service flow routing, policy control, etc.

[0064] AF may include a data collection application function (DCAF) for providing services related to data (such as user data) collection. The DCAF may be a network element deployed by an operator or a network element deployed by a third party, without limitation.

[0065] The network exposure function (NEF) safely exposes the services and capabilities provided by 3GPP network functions, such as opening services and capabilities to third parties, edge computing, AF, etc. It can also convert internal and external information, such as converting information outside 3GPP into information within 3GPP.

[0066] Data network (DN), such as operator services, Internet access or third-party services. DN and UPF can communicate through the N6 interface.

[0067] The network data analytics function (NWDAF) provides network data collection and analysis functions based on technologies such as big data and artificial intelligence.

[0068] The network repository function (NRF) provides network element registration and discovery, enabling network functions (NFs) to discover each other and communicate.

[0069] It should be noted that Figure 2 The network architecture in the example is only an example of a 5G network architecture. With the development of technology, some modules or functions of the network architecture may be optimized. The embodiments of the present application are not only applicable to Figure 2 The network architecture described herein is also applicable to other network architectures with the same or similar functions as this network architecture.

[0070] It should be understood that the device with communication function in the network / system in the embodiment of the present application can be referred to as a communication device. Figure 1 Taking the communication system shown as an example, the communication equipment may include a terminal device 110 with communication functions, an access network device 120 and a core network device 130, etc., which is not limited in the embodiments of the present application.

[0071] It should be understood that the terms "system" and "network" are often used interchangeably herein.

[0072] In the embodiments of the present application, "pre-definition" can be implemented by pre-saving corresponding codes, tables or other methods that can be used to indicate relevant information in a device (for example, including a terminal device and a network device), and the present application does not limit the specific implementation method. For example, pre-definition can refer to what is defined in the protocol.

[0073] In the embodiments of the present application, the “protocol” may refer to a standard protocol in the communication field, for example, it may include an LTE protocol, an NR protocol, and related protocols used in future communication systems, and the present application does not limit this.

[0074] The term "and / or" in this article is only a description of the association relationship of the associated objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship.

[0075] The terms used in the implementation mode of this application are only used to explain the specific embodiments of this application, and are not intended to limit this application. The terms "first", "second", "third" and "fourth" in the specification and claims of this application and the drawings 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.

[0076] It should be understood that the "indication" mentioned in the embodiments of the present application can be a direct indication, an indirect indication, or an indication of an association relationship. For example, A indicates B, which can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association relationship between A and B.

[0077] In the description of the embodiments of the present application, the term "corresponding" may indicate a direct or indirect correspondence between two items, or an association relationship between the two items, or a relationship between indication and being indicated, configuration and being configured, and the like.

[0078] In some communication mechanisms, due to certain requirements, such as data analysis needs, data consumers such as NWDAF in the network need to use data agents such as DCAF to request data related to terminal devices.

[0079] As a specific example, Figure 3 FIG. 1 is a schematic diagram showing a process of providing terminal device related data to NWDAF. The terminal device is UE as an example for explanation. Figure 3 As shown, steps 301 to 307 are included.

[0080] 301, NF sends a Nnwdaf analysis subscription request to NWDAF.

[0081] For example, the NF may send Nnwdaf_AnalyticsSubscription_Subscribe to the NWDAF to provide data analysis results from the NWDAF to the user NF, where the data analysis results need to be generated by the NWDAF based on relevant data of the UE.

[0082] 302, NWDAF performs AF Discovery.

[0083] Specifically, as a data consumer, the NWDAF network element needs to request UE-related data from the AF (specifically, the DCAF). Exemplarily, the NWDAF can query and obtain the corresponding DCAF.

[0084] 303, NWDAF sends a data acquisition request to AF.

[0085] Specifically, the data acquisition request is used to request relevant data of the UE. As an example, the request may be Naf_Event_Exposure_Subscribe.

[0086] Exemplarily, the data acquisition request may carry a UE identifier (ID), such as a user permanent identifier (SUbscription Permanent Identifier, SUPI) or a generic public user identifier (Generic Public Subs cription Identifier, GPSI), etc., without limitation.

[0087] Optionally, when the DCAF is a third-party untrusted AF, the request message is first sent to the NEF, which is then forwarded to the DCAF.

[0088] 304, AF requests and obtains data from UE.

[0089] Specifically, the DCAF requests and obtains data from the corresponding UE, for example, data in the UE application or baseband can be collected to the AF (Data collection from UE application to AF), wherein the data is uploaded to the DCAF through a user plane session, such as a PDU session.

[0090] 305. The AF returns the UE-related data to the NWDAF.

[0091] Exemplarily, the AF may return UE-related data as a response to Naf_Event_Exposure_Subscribe via Naf_Event_Exposure_Notify.

[0092] 306, NWDAF generates data analysis results.

[0093] Specifically, NWDAF can use UE-related data to complete its own data analysis task requirements.

[0094] 307, NWDAF sends Nnwdaf analysis subscription notification to NF.

[0095] For example, NWDAF may send Nnwdaf_AnalyticsSubscription_Notify to NF as a response to Nnwdaf_AnalyticsSubscription_Subscribe, providing data analysis results from NWDAF to user NF.

[0096] exist Figure 3 In the example, the DCAF collects UE-related data with the UE IP address as the index, that is, the UE-related data is uploaded through the user plane session corresponding to the UE IP address, such as the PDU session, in step 304. When the NWDAF collects data from the DCAF, it uses the UE ID as the index, that is, it carries the UE ID in step 303. Therefore, in the above process, there is a requirement that the DCAF needs to map the UE ID to the UE IP address.

[0097] As a specific example, Figure 4 A schematic diagram showing the process of obtaining the UE IP address corresponding to the UE ID is shown. Figure 4 As shown, steps 400 to 407 are included.

[0098] 400. AF stores UE IP address.

[0099] 401. AF sends a UE ID acquisition request to NEF.

[0100] Exemplarily, the UE ID acquisition request may be: Nnef_UEid_Get_Request.

[0101] 402. NEF sends a UE context management CM acquisition request to UDM.

[0102] Exemplarily, the UECM acquisition request may be: Nudm_UECM_Get_Request.

[0103] 403, UDM sends a UECM acquisition response to NEF.

[0104] Exemplarily, the UECM get response may be: Nudm_UECM_Get_Response.

[0105] 404, NEF sends an event subscription request to SMF to request UE ID.

[0106] Exemplarily, the event subscription request may be: Nsmf_Event_Exposure_Subsribe.

[0107] 405, SMF sends an event subscription notification to NEF, which includes UE ID.

[0108] Exemplarily, the event subscription notification may be: Nsmf_Event_Exposure_Notify.

[0109] 406. NEF sends a UE ID acquisition response to AF.

[0110] Exemplarily, the UE ID acquisition response may be: Nnef_UEid_Get_Response.

[0111] 407, AF correlates UE data collection and NWDAF request (AF correlates UE data collection and NWDAF request).

[0112] Among them, through steps 401 to 403, DCAF queries the SMF corresponding to the UE through NEF and UDM; through steps 404 to 406, DCAF requests and obtains the UE IP address corresponding to the UE ID from the SMF.

[0113] In the related art, before DCAF obtains data from a terminal device, it is assumed that the user plane session of the terminal device already exists and has not been released, that is, the IP address corresponding to the user plane session of the terminal device has always existed and has not changed. When DCAF has a need to obtain data, it can immediately use the session and IP address to obtain data from the corresponding terminal device. However, there are some scenarios where, when the session of a terminal device is released or changed, the IP address assigned to the terminal device is deleted or changed, or even assigned to other terminal devices for use, DCAF cannot correctly obtain the corresponding terminal device historical data based on the original IP address.

[0114] As a specific example, Figure 5An example of a communication process in the above scenario is shown, which may include the following steps 501 to 507:

[0115] 501, UE sends a data report to DCAF, which includes UE IP1 address, timestamp, event ID / data type information, etc.

[0116] Among them, the UE IP1 address is the session used for uploading data, such as the IP address corresponding to the user plane PDU session 1.

[0117] 502, PDU session 1 is released.

[0118] Exemplarily, PDU session 1 is released. After PDU session 1 is released, SMF / UPF will release the mapping relationship between UE IP1 address and UE ID, and may allocate the IP1 address to other UEs for use.

[0119] 503, NWDAF sends a UE data acquisition request to DCAF.

[0120] 504, DCAF sends UE IP request to SMF / UPF.

[0121] Optionally, 505, SMF / UPF sends a UE IP response to DCAF, where the UE IP address is null (NA).

[0122] 506, PDU session 2 is established.

[0123] Optionally, 507, SMF / UPF sends a UE IP response to DCAF, which includes a UE IP2 address, wherein the UE IP2 address is an IP address corresponding to the newly established user plane PDU session 2.

[0124] Specifically, after PDU session 1 is released, if DCAF has a data acquisition request and obtains the UE IP address from the network (such as SMF / UPF), then according to the relevant technical process, the network either returns empty (corresponding to step 505) or returns the UE IP2 address corresponding to the newly established PDU session (such as PDU session 2) (corresponding to step 507).

[0125] If the UE IP response is empty, DCAF cannot obtain any data; if the UE IP response is a new IP address, such as UE IP2 address, DCAF can only return the real-time data corresponding to UE IP2 address. In either case, DCAF does not know the IP address corresponding to the UE at historical time, so DCAF cannot obtain the historical data corresponding to UE IP 1 address at historical time.

[0126] In order to solve the above technical problems, the embodiments of the present application provide a data acquisition method, apparatus, device and storage medium, which associates the address information of the session in which the terminal device reports data to the first communication device with the historical time, so that the first communication device can obtain the data of the terminal device at the first time according to the address information of the session of the terminal device at the historical time, so that the first communication device obtains the data corresponding to the address information of the session of the terminal device at the historical time. Wherein, the first time overlaps with the historical time.

[0127] It should be noted that the embodiments of the present application do not limit the type of session, for example, it can be a user plane session, or a data plane session, etc.; the embodiments of the present application do not limit the type of address information of the session, for example, it can include an IP address, or an Ethernet address, etc.

[0128] The technical solution of the embodiment of the present application will be described in detail below:

[0129] Figure 6 6 is a schematic flow chart of a data acquisition method 600 provided in an embodiment of the present application. The data acquisition method 600 may be executed by a first communication device. Figure 6 As shown, the data acquisition method 600 may include at least part of the following steps 610 to 620:

[0130] 610. The first communication device obtains first information of the terminal device, where the first information is used to indicate address information of a session of the terminal device at a historical time.

[0131] Exemplarily, the first communication device may include but is not limited to a DCAF, and the terminal device may be a terminal device that reports data to the first communication device, such as a UE. The number of the terminal devices may be one or more, and is not limited.

[0132] The session includes a session in which the terminal device reports data to the first communication device. In other words, the session is used when the terminal device reports data to the first communication device, or the session is used for the first communication device to collect user data, or the session is used for the first communication device to collect terminal device related data, and this application does not limit this.

[0133] Exemplarily, a session may include a user plane session, or other types of sessions, such as a data plane session, etc., without limitation.

[0134] Optionally, in an embodiment of the present application, the session of the terminal device may correspond to a special data network name (Data Network Name, DNN) and / or a single network slice selection assistance information (Single Network Slice Selection Assistance information, S-NSSAI). Among them, the special DNN and / or S-NSSAI may be a network deployed specifically for collecting user data. Optionally, the session may also be referred to as a specific session, which is not limited in this application.

[0135] In one implementation manner, the session involved in the embodiment of the present application refers to a session in which a terminal device reports data to a first communication device, that is, a specific session.

[0136] The address information of the session of the terminal device at the historical time may refer to the address information allocated by the network to the session of the terminal device at the historical time. Since the address information corresponding to the session of the terminal device may change over time, by associating the address information of the session of the terminal device with the historical time, the address information of the session of the terminal device at different historical times can be obtained.

[0137] It should be noted that, in the embodiment of the present application, the address information of the session of the terminal device refers to the address information corresponding to the session of the terminal device, that is, the address information assigned to the terminal device for the session.

[0138] Exemplarily, the address information may include an IP address, an Ethernet address, or other types of address information, without limitation. For example, if a session in the network is based on an IP address, the address information is an IP address; if a session in the network is based on an Ethernet type, the address information is an Ethernet address. It should be understood that some embodiments of the present application are described using the address information as an IP address as an example. If a session in the network is not based on an IP address, but is based on other types of addresses (such as Ethernet type addresses), the provided method is equally applicable.

[0139] Exemplarily, a terminal device may correspond to one or more IP addresses at different historical times, wherein the IP addresses at different historical times may correspond to different sessions of the terminal device.

[0140] In one implementation, the historical time may be a time point or a time period, which is not limited in this application.

[0141] In one implementation, the historical time may include the time when the network allocates the IP address to the terminal device, and / or the time when the IP address is released, which is not limited in this application.

[0142] Exemplarily, the historical time associated with the IP address of a session of the terminal device may include any time point or time period in the process from establishment to release of the session, which is not limited in the present application.

[0143] In one implementation, the historical time associated with the IP address of a session of the terminal device may be the period from the establishment to the release of the session, which is not limited in the present application.

[0144] In some embodiments, step 610 may be implemented as follows:

[0145] The first communication device obtains first information from the second communication device, wherein the first information includes historical time information and address information of the session of the terminal device at the historical time, wherein the historical time information is used to indicate the historical time.

[0146] Exemplarily, the second communication device can obtain the IP address of the session and the corresponding historical time information during the process of establishing and releasing the session or after the session is released. By obtaining the historical time information and the IP address of the session of the terminal device at the historical time, the IP address of the session of the terminal device can be associated with the historical time.

[0147] Optionally, the second communication device may also associate the ID of the terminal device, the IP address of the session of the terminal device, and the historical time information, so that the historical time information may indicate the time when the IP address of the session of the terminal device is associated with the ID of the terminal device.

[0148] Exemplarily, the second communication device may be at least one of SMF, UPF or NWDAF.

[0149] As an example, when the second communication device is SMF, the SMF can obtain the IP address assigned to the session of the terminal device from itself, or obtain the IP address assigned to the session of the terminal device from UPF, which is not limited in this application.

[0150] Exemplarily, the IP address of the terminal device can be a private IP address of the terminal device or a public IP address of the terminal device, without limitation. Exemplarily, when NAT is deployed in the network, the IP address of the terminal device is generally the public IP address of the terminal device, otherwise, the IP address of the terminal device is generally the private IP address of the terminal device.

[0151] Exemplarily, the ID of the terminal device may be the SUPI or GPSI of the terminal device, or other unique identifier of the terminal device, which is not limited in this application.

[0152] Optionally, the historical time information may include time information of session establishment and / or time information of session release. The time information of session establishment is the time information when the IP address is allocated, and the time information of session release is the time information when the IP address is released. The time information of session establishment can be understood as the time when the session is established, and the time information of session release can be understood as the time when the session is released.

[0153] As an example, the second communication device may obtain the IP address of the session and the ID of the terminal device, as well as the corresponding time information T1 when the session of the terminal device is established (setup / establishment). The time information T1 may refer to the moment T1. The time information T1 may include the time information of the session establishment.

[0154] Exemplarily, the time information T1 may be the time when the IP address is allocated to the terminal device, or the time when the terminal device obtains the IP address, or the time when the IP address of the session of the terminal device is associated with the ID of the terminal device, without limitation. That is, at time T1, the IP address of the session of the terminal device is associated with the ID of the terminal device.

[0155] As another example, the second communication device may obtain the corresponding time information T2 when the session of the terminal device is released. The time information T2 may refer to the time T2. The time information T2 may include the time information of the session release. That is, at the time T2, the IP address of the terminal device and the ID of the terminal device are released from the association.

[0156] Optionally, the second communication device may also receive a session establishment request from the terminal device, where the session establishment request includes first indication information, such as a specific session indication, where the first indication information is used to indicate that the session requested to be established is used for the terminal device to report data to the first communication device.

[0157] When the session establishment request includes the first indication information, and / or the session corresponds to the special DNN and / or S-NSSAI, the second communication device can determine that the session is used for the terminal device to report data to the first communication device, and the second communication device can obtain the historical time information and the IP address corresponding to the historical time information. Exemplarily, the second communication device can obtain the IP address of the session of the terminal device, the ID of the terminal device, and the corresponding session establishment time information T1 or session release time information T2.

[0158] After acquiring the IP address and historical time information of the session of the terminal device at a historical time, the second communication device sends the IP address and historical time information as the first information to the first communication device.

[0159] In some embodiments, step 610 may also be implemented as follows:

[0160] The first communication device obtains first information from the second communication device, where the first information includes an IP address corresponding to the terminal device at the time when the session is established.

[0161] Specifically, the second communication device can obtain the IP address corresponding to the time when the session for the terminal device to report data to the first communication device is established, and send the IP address as the first information to the first communication device. Correspondingly, the first communication device receives the IP address.

[0162] Exemplarily, the second communication device may be SMF or UPF, etc., without limitation.

[0163] In a possible implementation, the first information may further include second indication information, and the second indication information is used to indicate to the first communication device that the session is established, or to indicate that the IP address in the first information is allocated. Accordingly, the first communication device may determine, based on the second indication information, that the IP address in the first information is the IP address corresponding to the time when the session is established, or determine that the IP address in the first information is allocated.

[0164] In another possible implementation, when the first information does not include the second indication information, the protocol may predefine the IP address in the first information as the IP address corresponding to the time when the session is established. Alternatively, when the first communication device first receives the IP address in the first information, it may determine that the IP address is the IP address corresponding to the time when the session is established.

[0165] Optionally, the first information may further include time information of session establishment. Exemplarily, the time information of session establishment may be the time information T1 mentioned above, which is not limited in the present application.

[0166] Optionally, when the first information does not include the time information of session establishment, the first communication device may determine the time of receiving the first information as the time of session establishment. Correspondingly, the first communication device may record the time information of session establishment.

[0167] Optionally, the time information of session establishment here may also be referred to as historical time information, without limitation.

[0168] In some embodiments, step 610 may also be implemented as follows:

[0169] The first communication device obtains the first information from the second communication device, where the first information includes an IP address corresponding to the terminal device at the time when the session is released.

[0170] Specifically, the second communication device can obtain the IP address corresponding to the time when the session for the terminal device to report data to the first communication device is released, and send the IP address as the first information to the first communication device. Correspondingly, the first communication device receives the IP address.

[0171] Exemplarily, the second communication device may be SMF or UPF, etc., without limitation.

[0172] In a possible implementation, the first information may further include third indication information, and the third indication information is used to indicate to the first communication device that the session is released, or to indicate that the IP address in the first information is released. Accordingly, the first communication device may determine, based on the third indication information, that the IP address in the first information is the IP address corresponding to the time of session release, or determine that the IP address in the first information is released.

[0173] In another possible implementation, when the first information does not include the third indication information, the protocol may predefine the IP address in the first information as the IP address corresponding to the time of session release. Alternatively, when the first communication device receives the IP address in the first information for the second time, it may determine that the IP address is the IP address corresponding to the time of session release.

[0174] Optionally, the first information may further include time information of session release. Exemplarily, the time information of session release may be the time information T2 mentioned above, which is not limited in the present application.

[0175] Optionally, when the first information does not include the time information of the session release, the first communication device may determine the time of receiving the first information as the time of the session release. Correspondingly, the first communication device may record the time information of the session release.

[0176] Optionally, the time information of session release here may also be referred to as historical time information, without limitation.

[0177] In some possible implementations, the second communication device may actively send the first information to the first communication device when determining that a session is established / released for the terminal device to report data to the first communication device, or may send the first information to the first communication device as a response to a subscription request message of the first communication device.

[0178] In some embodiments, step 610 may also be implemented as follows:

[0179] The first communication device sends a first request message to the second communication device, the first request message including first time information, wherein the first time information is used to indicate a first time; and the first communication device receives first information from the second communication device, the first information including the IP address of the session of the terminal device at the first time.

[0180] Specifically, the second communication device can obtain the IP address corresponding to the first time information, and in response to the first request message sent by the first communication device, send the IP address of the session of the terminal device at the first time as the first information to the first communication device. Exemplarily, the IP address of the session of the terminal device at the first time can be called the first IP address.

[0181] Wherein, the first time overlaps with the historical time. Exemplarily, the first time overlaps with the historical time, which may mean that the first time falls within the time period corresponding to the historical time, or the first time spans the time periods corresponding to multiple historical times, or the first time overlaps with the time periods corresponding to the historical time, and this application does not limit this.

[0182] Exemplarily, the time periods corresponding to the first time and the historical time overlap, that is, part of the first time belongs to the historical time, and part of the first time may also belong to the current and / or future time. For example, the first time is a time period from last month to the next 2 months.

[0183] Optionally, for the data belonging to the current and / or future time in the first time of the terminal device, the corresponding data can be obtained according to the IP address of the instant session of the terminal device, which is not limited in this application.

[0184] In one possible scenario, the second communication device may save the IP addresses of the terminal device at multiple different historical times, wherein the IP addresses at different historical times may correspond to the sessions of the terminal device at different historical times. When the second communication device receives the first request message, it may send the IP address corresponding to the historical time including the first time as the IP address of the session of the terminal device at the first time to the first communication device.

[0185] Among them, the IP address of the session of the terminal device at the first time can be an IP address of a historical time where the session of the terminal device falls at the first time, or multiple IP addresses corresponding to multiple historical times spanned by the first time, or an IP address corresponding to the overlapping part of the historical time with the first time.

[0186] Exemplarily, the first request message may include at least one of the ID of the terminal device and condition information #2. The ID of the terminal device and condition information #2 are from the second request message sent by the consumer device to the first communication device. Specifically, the ID of the terminal device and condition information #2 can refer to the description of the second request message below.

[0187] Exemplarily, the second communication device may be SMF, UPF or NWDAF, etc., without limitation.

[0188] As an example, when the second communication device is NWDAF, NWDAF can obtain the IP address of the session of the terminal device at the historical time from SMF / UPF. Optionally, NWDAF can send a subscription request message to SMF / UPF to obtain the IP address of the session of the terminal device at the historical time. Optionally, NWDAF can also obtain historical time information from SMF / UPF.

[0189] In some embodiments, the first communication device may also send a subscription request message to the second communication device to obtain the first information of the terminal device. In response to the subscription request message, the second communication device may send the first information to the first communication device when obtaining the first information.

[0190] Optionally, the subscription request message may include at least one of the ID of the terminal device and condition information #1.

[0191] The ID of the terminal device may indicate the subscribed target terminal, which may refer to one or some specific terminal devices or any terminal device without limitation.

[0192] Among them, condition information #1 is used to limit the scope of the object terminal. Exemplarily, the scope can be an area scope, such as Tracking Areas (TAs), cells, or a geographical area (such as a latitude and longitude area), etc. The scope can also be a specific location, such as a TA ID, a cell ID or longitude and latitude. Optionally, the scope can also be a time range. By setting condition information #1, it can be instructed that the second communication device only obtains the IP address of the session when the terminal device in the corresponding area or position reports data, or it can be instructed to obtain only the IP address of the session when the terminal device in a certain specific time period reports data.

[0193] Optionally, the subscription request message may also include an event ID (eventID), which is specifically used to indicate that the requested event / data is the IP address of the corresponding session returned when the terminal device reports data to the first communication device. The event ID may also be referred to as data type information.

[0194] Therefore, through the interaction process between the above-mentioned first communication device and the second communication device, the first communication device can obtain and record the IP address of the terminal device's session that reports data to the first communication device at a historical time, such as obtaining and recording the association between the IP address of the terminal device session and the ID of the terminal device in the time period from T1 to T2, or recording the IP address of the terminal device's session at the first time, or recording the IP address of the terminal device's session corresponding to the time when the session is established, or recording the IP address of the terminal device's session corresponding to the time when the session is released, etc., without limitation.

[0195] 620. The first communication device obtains data of the terminal device at the first time according to the first information.

[0196] Specifically, the first communication device may obtain address information of a session of the terminal device at a historical time according to the first information, and further obtain data of the terminal device at the first time according to the address information at the historical time.

[0197] Therefore, the embodiment of the present application associates the address information of the session in which the terminal device reports data to the first communication device with the historical time, so that the first communication device can obtain the data of the terminal device at the first time based on the address information of the session of the terminal device at the historical time, thereby enabling the first communication device to obtain the data corresponding to the address information of the session of the terminal device at the historical time.

[0198] In some embodiments, the first communication device may pre-store data reported by the terminal device at a historical time, and then may obtain the data of the terminal device at the first time from the data reported by the terminal device at a historical time according to the first information. The data reported by the terminal device at a historical time is reported through the session described above. In the embodiment of the present application, the data reported by the terminal device at a historical time may be referred to as the first data.

[0199] Exemplarily, the first data is associated with the IP address of the corresponding session. For example, the terminal device reports the first data #1 to the first communication device through session #1 at the first historical time, and the first data #1 is associated with the IP address #1 of session #1. For another example, the terminal device reports the first data #2 to the first communication device through session #2 at the second historical time, and the first data #2 is associated with the IP address #2 of session #2.

[0200] Optionally, the terminal device may send the first data and the associated IP address to the first communication device through the session. Correspondingly, the first communication device receives the first data and the associated IP address through the session.

[0201] Exemplarily, the terminal device may report a data packet including the first data and the IP address to the first communication device. In a possible implementation, the data packet may be in a message format, wherein the first data may be included in a payload of the data packet, and the IP address may be included in a message header of the data packet, which is not limited in this application.

[0202] Exemplarily, the IP address sent by the terminal device to the first communication device may be a private IP address of the terminal device. Optionally, when the network deploys Network Address Translation (NAT), the private IP address is converted to the public IP address of the terminal device after NAT and then sent to the first communication device.

[0203] Optionally, the terminal device may also send a timestamp of the first data to the first communication device. In one possible implementation, the timestamp may be carried in a data packet (such as a payload) containing the first data, which is not limited in this application. Exemplarily, the timestamp may include at least one of a sampling timestamp of the first data and a reporting timestamp of the first data.

[0204] In some embodiments, after the first communication device receives the first data reported by the terminal device, the first data may be stored.

[0205] In a possible implementation, the first communication device may store the first data using the IP address of the terminal device as an index. Exemplarily, the IP address may be an IP address carried in a data packet reported by the terminal device and received by the first communication device.

[0206] In another possible implementation, the first communication device may also save the first data using the ID of the terminal device as an index. Exemplarily, the first communication device may map the IP address associated with the first data to the ID of the terminal device based on the association relationship between the IP address of the session of the terminal device saved and the ID of the terminal device, and then save the first data using the ID of the terminal device as an index.

[0207] In another possible implementation, the first communication device may also save the first data by using both the IP address and the ID of the terminal device as indexes.

[0208] Optionally, when the first communication device stores the first data, it may also store a timestamp of the first data. Exemplarily, the timestamp may include at least one of a sampling timestamp of the first data, a reporting timestamp of the first data, a timestamp of the first data arriving at the first communication device, and a timestamp of the first communication device storing the first data.

[0209] In some embodiments, the first communication device can determine the first IP address of the session of the terminal device at the first time based on the first information, and then obtain the data of the terminal device at the first time based on the first IP address.

[0210] In a possible implementation, when the first information includes historical time information and an IP address of a session of a terminal device at a historical time, the first communication device may obtain an IP address corresponding to the first time information from the IP address of the session of the terminal device at a historical time as the first IP address. The first time information is used to indicate the first time. Specifically, the first time may refer to the description above.

[0211] Exemplarily, the historical time information included in the first information may indicate multiple historical time periods, then the IP address corresponding to the historical time period in which the first time falls is the first IP address, or the multiple IP addresses corresponding to the multiple historical time periods spanned by the first time are the first IP address, or the IP address corresponding to the overlapping part of the historical time period with the first time is the first IP address.

[0212] Another possible implementation manner is that when the first information includes the IP address of the first time of the session of the terminal device (ie, the first IP address), the IP address included in the first information can be directly used as the first IP address.

[0213] In some embodiments, when the first communication device saves data using the IP address as an index (or using the IP address and the terminal device ID together as an index), the data corresponding to the first IP address can be retrieved from the data as the data of the terminal device at the first time.

[0214] Therefore, when the first communication device has a need to obtain data at the first time, it can obtain the data of the terminal device at the first time by obtaining the first IP address of the session of the terminal device at the first time, and then retrieving the data corresponding to the first IP address from the saved data.

[0215] In some embodiments, when the first communication device saves data with the ID of the terminal device (or with the IP address and the ID of the terminal device together) as an index, the first communication device can obtain the data corresponding to the ID of the terminal device at the first time. Exemplarily, the first communication device can retrieve the data corresponding to the ID of the terminal device at the first time from the stored data.

[0216] Therefore, by using the ID of the terminal device as an index to save the first data, the first communication device can retrieve the data corresponding to the ID of the terminal device at the first time from the saved data when there is a need to obtain the data at the first time, thereby obtaining the data of the terminal device at the first time. At this time, the first communication device does not need to obtain the IP address of the session of the terminal device at the first time, which can help improve the efficiency of data acquisition.

[0217] In some embodiments, the first communication device may also receive a second request message sent by the consumer device, the second request message including the first time information, and the second request message is used to obtain the data of the terminal device at the first time. Exemplarily, the second request message may also be referred to as a data acquisition request (UE data collection request), without limitation. Then, the first communication device may send a response message to the consumer device, the response message including the data of the terminal device at the first time.

[0218] For example, the first time may refer to the description above.

[0219] Exemplarily, the consumer device may be, for example, NWDAF, AF, RAN, or other device that has a need to obtain terminal device data, and this application does not limit this.

[0220] As some examples, the second request message can be used to request data of a terminal device in a historical time period, or for data of a terminal device in multiple historical time periods, or for requesting data of multiple terminal devices in one or more historical time periods respectively, without limitation.

[0221] In a possible implementation, the second request message may include at least one of the ID of the terminal device and condition information #2, where the condition information #2 is used to indicate the condition satisfied by the terminal device.

[0222] Exemplarily, the ID of the terminal device here may be SUPI or GPSI, without limitation. In one implementation, when the terminal device identifier of the second terminal device is SUPI, it may be converted into GPSI before being sent to the first communication device.

[0223] Exemplarily, condition information #2 is used to limit the range of the terminal device. Exemplarily, the range can be a regional range, such as Tracking Areas (TAs), cells, or a geographical area (such as a latitude and longitude area), etc. The range can also be a specific location, such as a TA ID, a cell ID, or longitude and latitude. By setting condition information #2, the first communication device can be requested to return the data of the terminal device in the corresponding area or location at the first time.

[0224] Optionally, the first communication device may obtain a terminal device ID list (list) of at least one terminal device that meets the condition according to condition information #2.

[0225] Optionally, when the second request message includes condition information #2, the first request message may not include the ID of the terminal device.

[0226] Therefore, after the first communication device obtains the second request message, it can obtain the first time information and the ID of the terminal device according to the second request message, and thus obtain the first information according to the first time information and the ID of the terminal device, such as the IP address of the corresponding terminal device at the first time, or the IP address at a historical time, etc., and then obtain the data of the terminal device at the first time according to the first information.

[0227] In another possible implementation, the second request message may include the IP address of the session of the terminal device at the first time.

[0228] Exemplarily, before sending the second request message to the first communication device, the consumer device may obtain the IP address of the session of the terminal device at the first time, and then carry the IP address in the second request message and send it to the first communication device to request the data corresponding to the IP address. The data corresponding to the IP address is the data of the session of the terminal device at the first time.

[0229] In one possible scenario, when NWDAF saves the IP address of the session of the terminal device at a historical time, the consumer device may send a third request message to NWDAF to request the IP address of the session of the terminal device at the first time. In response to the third request message, NWDAF sends the IP address of the session of the terminal device at the first time to the consumer device. When the consumer device is the NWDAF device itself, the IP address of the session of the terminal device at the first time may be obtained from itself through internal operations.

[0230] Here, the third request message has a similar function to the first request message mentioned above, and both are used to request the IP address of the session of the terminal device at the first time. Please refer to the relevant description of the first request message, which will not be repeated here.

[0231] Therefore, by carrying the IP address of the terminal device at the first time in the second request message, the first communication device can obtain the data of the terminal device at the first time according to the IP address of the terminal device at the first time. At this time, the first communication device does not need to search the IP address of the terminal device at the first time from the IP addresses of the historical time of the session, which can help improve the efficiency of data acquisition.

[0232] In other embodiments, the terminal device itself can store the data of the terminal device at historical time and the IP address of the historical time, such as saving the data of historical time with the IP address or ID of the terminal device as the index. Optionally, the terminal device can also save the time information corresponding to the data. At this time, the first communication device can request the terminal device for the data corresponding to the terminal device at the first time according to the first information.

[0233] Figure 7 Schematic flow chart of another data acquisition method 700 provided in an embodiment of the present application. The data acquisition method may be executed by a second communication device. Figure 7 As shown, the data acquisition method 700 may include at least part of the following steps 710 and 720:

[0234] 710. The second communication device obtains first information of the terminal device, where the first information is used to indicate address information of a session of the terminal device at a historical time, wherein the session includes a session in which the terminal device reports data to the first communication device.

[0235] 720. The second communication device sends first information to the first communication device.

[0236] Exemplarily, the first communication device may include but is not limited to a DCAF, and the terminal device may be a terminal device that reports data to the first communication device.

[0237] Exemplarily, the second communication device may include but is not limited to SMF, UPF or NWDAF, etc.

[0238] In some embodiments, the first information may include historical time information and address information of the session of the terminal device at the historical time, wherein the historical time information is used to indicate the historical time.

[0239] It should be understood that some embodiments of the present application are described using the IP address as an example of address information. If the session in the network is not based on the IP address but on other types of addresses (such as Ethernet type addresses), the provided method is also applicable.

[0240] Optionally, the historical time information may include time information of session establishment and / or time information of session release.

[0241] As an example, when the second communication device is an SMF or UPF, the second communication device itself can obtain the IP address of the session of the terminal device at a historical time as the first information, and send the first information to the first communication device. Optionally, the first information may also include historical time information. Exemplarily, the second communication device may obtain the first information during the process of session establishment or session release or after the session is released.

[0242] In some embodiments, step 710 may be specifically implemented as follows:

[0243] The second communication device receives a first request message from the first communication device, the first request message including first time information; the first time information is used to indicate the first time; and the second communication device determines the IP address of the session of the terminal device at the first time as the first information. That is, the first information may include the IP address of the session of the terminal device at the first time.

[0244] As an example, when the second communication device is SMF / UPF, the second communication device itself can obtain the IP address of the terminal device's session at a historical time, and when receiving a first request message from the first communication device, obtain the IP address of the first time from the IP address of the terminal device's session at a historical time according to the first time information, and send it to the first communication device as the first information.

[0245] As another example, when the second communication device is NWDAF, the second communication device can obtain the IP address of the terminal device's session at the historical time from SMF / UPF. When NWDAF receives the first request message from the first communication device, it can obtain the IP address of the first time from the IP address of the terminal device's session at the historical time according to the first time information, and send it to the first communication device as the first information.

[0246] In some embodiments, step 710 may be specifically implemented as follows:

[0247] The second communication device receives a session establishment request message from the terminal device, the session establishment request message being used to establish a session in which the terminal device reports data to the first communication device; and the second communication device determines the IP address corresponding to the time when the terminal device establishes the session as the first information. That is, the first information may include the IP address corresponding to the time when the terminal device establishes the session.

[0248] Optionally, the session establishment request message may include first indication information, and the first indication information is used to indicate that the established session is used for the terminal device to report data to the first communication device. In other words, the first indication information is used to indicate the establishment of a session for the terminal device to report data to the first communication device.

[0249] When the session establishment request message includes the first indication information, the second communication device may determine that the session establishment request is used to request establishment of a session for the terminal device to report data to the first communication device.

[0250] In other embodiments, when the session corresponds to a specific DNN and / or S-NSSAI, the second communication device may also determine that the session is a session for the terminal device to report data to the first communication device, which is not limited in this application.

[0251] Optionally, the first information may also include second indication information; the second indication information is used to indicate to the first communication device that the session is established, or to indicate that the IP address in the first information is allocated. Accordingly, the first communication device may determine, based on the second indication information, that the IP address in the first information is the IP address corresponding to the time when the session is established, or that the IP address in the first information is allocated.

[0252] When the first information does not include the second indication information, the protocol may predefine the IP address in the first information as the IP address corresponding to the time when the session is established. Alternatively, when the first communication device first receives the IP address in the first information, it may determine that the IP address is the IP address corresponding to the time when the session is established.

[0253] Optionally, the first information may further include time information of session establishment. Exemplarily, the time information of session establishment may be the time information T1 mentioned above, which is not limited in the present application.

[0254] Optionally, when the first information does not include time information of session establishment, the first communication device may determine the time of receiving the first information as the time of session establishment.

[0255] In some embodiments, step 710 may be specifically implemented as follows:

[0256] The second communication device receives a session release request message from the terminal device, the session release request being used to release the session in which the terminal device reports data to the first communication device; and the second communication device determines the IP address corresponding to the time when the terminal device releases the session as the first information. That is, the first information may include the IP address corresponding to the time when the terminal device releases the session.

[0257] Optionally, the first information may further include third indication information; the third indication information is used to indicate to the first communication device that the session is released, or to indicate that the IP address in the first information is released. Accordingly, the first communication device may determine, based on the third indication information, that the IP address in the first information is the IP address corresponding to the time of session release, or determine that the IP address in the first information is released.

[0258] When the first information does not include the third indication information, the protocol may predefine the IP address in the first information as the IP address corresponding to the time of session release. Alternatively, when the first communication device receives the IP address in the first information for the second time, it may determine that the IP address is the IP address corresponding to the time of session release.

[0259] Optionally, the first information may further include time information of session release. Exemplarily, the time information of session release may be the time information T2 mentioned above, which is not limited in the present application.

[0260] Optionally, when the first information does not include time information of session release, the first communication device may determine the time of receiving the first information as the time of session release.

[0261] In some embodiments, the second communication device may also receive a subscription request message from the first communication device, the subscription request message being used to obtain the first information of the terminal device. In response to the subscription request message, the second communication device may send the IP address of the session of the terminal device at the historical time as the first information to the first communication device. Exemplarily, in this embodiment, the second communication device includes but is not limited to an SMF or a UPF.

[0262] In some embodiments, the second communication device may also send a subscription request message to the third communication device, where the subscription request message is used to obtain the first information of the terminal device. Exemplarily, in this embodiment, when the second communication device may be an NWDAF, the third communication device may include but is not limited to an SMF or an UPF. In response to the subscription request message, the SMF / UPF may send the first information of the terminal device to the NWDAF.

[0263] In some embodiments, the subscription request message may include an ID or condition information of the target terminal device, where the condition information is used to indicate a condition satisfied by the target terminal device.

[0264] In some embodiments, the first information also includes an ID of the terminal device.

[0265] It should be understood that the content in the data acquisition method 700 corresponds to all or part of the content in the data acquisition method 600. Similar descriptions can refer to the embodiment of the method 600. To avoid repetition, they are not repeated here.

[0266] Therefore, the embodiment of the present application associates the address information of the session in which the terminal device reports data to the first communication device with the historical time, so that the first communication device can obtain the data of the terminal device at the first time based on the address information of the session of the terminal device at the historical time, thereby enabling the first communication device to obtain the data corresponding to the address information of the session of the terminal device at the historical time.

[0267] Figure 8 800 is a schematic flow chart of another data acquisition method 800 provided in an embodiment of the present application. The data acquisition method 800 may be executed by a consumer device. Figure 8 As shown, the data acquisition method 800 may include at least part of the following steps 810 and 820:

[0268] 810. The consumer device sends a second request message to the first communication device. The second request message includes first time information. The second request message is used to obtain data of the terminal device at the first time.

[0269] 820. The consumer device receives a response message from the first communication device, the response message including data of the terminal device at a first time, wherein the data of the terminal device at the first time is obtained according to first information of the terminal device, the first information being used to indicate address information of a session of the terminal device at a historical time.

[0270] Therefore, the embodiment of the present application associates the address information of the session in which the terminal device reports data to the first communication device with the historical time, so that the first communication device can obtain the data of the terminal device at the first time based on the address information of the session of the terminal device at the historical time, thereby enabling the first communication device to obtain the data corresponding to the address information of the session of the terminal device at the historical time.

[0271] In some embodiments, the second request message may include an identifier of the terminal device or first condition information, where the first condition information is used to indicate a condition satisfied by the terminal device.

[0272] In some embodiments, the second request message includes address information of the session of the terminal device at the first time.

[0273] It should be understood that the content in data acquisition method 800 corresponds to all or part of the content in data acquisition method 600 or data acquisition method 700. Similar descriptions can refer to the embodiments of method 600 or method 700. To avoid repetition, they are not repeated here.

[0274] Next, we will combine Figures 9 to 11 Several specific examples provided in the embodiments of the present application are described. Specifically, the following description will be given by taking the first communication device as a DCAF, the terminal device as a UE, the session as a PDU session, and the address information as an IP address as an example. In the following embodiments, the IP, IP address, UE IP, UE IP address, etc. described have the same meaning.

[0275] Fig. 9 A schematic flow chart of a data acquisition method provided in an embodiment of the present application. The second communication device is SMF or UPF, and the consumer device is NWDAF. The SMF or UPF can send the IP address of the session of the terminal device at the historical time to DCAF. Fig. 9 The data acquisition method is described.

[0276] It should be noted that in the embodiment of the present application, when the DCAF communicates with a device in the network (such as SMF / UPF), if the DCAF is an untrusted AF, it may need to be transferred or converted through the NEF. For example, the NEF can realize the conversion of the geographical area outside the network and the area inside the network, the conversion of the UE network outside the network identity or the network inside the network identity, the conversion of the data outside the network and the time inside the network, etc., without limitation.

[0277] Optionally, 900, DCAF sends a subscription request to SMF / UPF.

[0278] Specifically, the DACF sends a subscription request to the SMF / UPF to obtain the first information of the UE, where the first information is used to indicate the IP address of the PDU session of the UE at a historical time. Exemplarily, the first information may include the IP address of the session of the terminal device at a historical time.

[0279] Exemplarily, the session may be a user plane PDU session, which is not limited in the present application. For convenience, the following description will be based on the example of a PDU session.

[0280] Exemplarily, the subscription request may include at least one of the following information:

[0281] Event ID or data type information: used to indicate that the subscribed event or data is the IP address corresponding to the session used by the terminal device to report data to DCAF;

[0282] Target UE information: used to indicate the target UE of the subscription, which can be one or some specific UEs (such as UE ID) or any UE (i.e. any UE);

[0283] Condition information (filter) #1: used to limit the scope of the object terminal. The scope can be an area scope (such as TAsCells, or a longitude and latitude geographic area, etc.) or a location (such as TA ID, cell ID, or a longitude and latitude geographic location, etc.), used to indicate that only the IP address corresponding to the session when the terminal in the area or location reports data is obtained; the range can also be a time range, used to indicate that the IP address corresponding to the session when the terminal reports data within a specific time period is obtained.

[0284] Specifically, the subscription request is an example of the subscription request message mentioned above, and details may refer to the relevant description mentioned above.

[0285] 901, PDU session 1 is established.

[0286] Specifically, the UE may initiate a process of establishing a PDU session 1, where the PDU session is used by the UE to report data to the DCAF.

[0287] Optionally, the PDU session 1 may correspond to a special DNN and / or S-NSSAI, where the DNN and / or S-NSSAI is deployed in the network specifically for collecting user data.

[0288] Optionally, when the UE sends a PDU session establishment request to the SMF / UPF, it may carry first indication information for indicating that the PDU session requested to be established (such as PDU session 1) is used for the terminal device to report data to the DCAF. Exemplarily, the first indication information may be used to indicate to the SMF / UPF that the PDU session 1 requested to be established is used for the terminal device to report data to the DCAF. The first indication information may also be referred to as specific PDU session indication information.

[0289] Specifically, the PDU session establishment request is an example of the session establishment request mentioned above, and details may refer to the relevant description mentioned above.

[0290] After the SMF / UPF receives the PDU session establishment request from the UE, if it is determined that the established PDU session 1 is used for the UE to report data to the DCAF, the SMF / UPF may send the first information of the UE to the DCAF, and the first information may indicate the IP address of the UE's PDU session 1 at the historical time. Exemplarily, the first information may be carried in notification message #1 and / or notification message #2.

[0291] 902, SMF / UPF sends notification message #1 to DCAF.

[0292] In some embodiments, the notification message #1 may include the IP address (such as UEIP1) of the PDU session 1 at a historical time. Exemplarily, the historical time may include the time when the PDU session 1 was established, without limitation.

[0293] The IP address may be the UE private IP address or the UE public IP address, without limitation. When NAT is deployed in the network, the IP address here is generally the UE public IP address, otherwise the IP address is generally the UE private IP address. Before the SMF / UPF sends the UE public IP address to the DCAF, the SMF can obtain the UE's public IP address from itself, or obtain the UE's public IP address from the UPF.

[0294] Optionally, notification message #1 may also include historical time information. As an example, the historical time information may include time information (such as time information T1) when PDU session 1 is established, which may indicate the time when PDU session 1 is established. As another example, the historical time information may include time information when the IP address of PDU session 1 is allocated, which may indicate the time when the IP address of PDU session 1 is allocated.

[0295] Optionally, notification message #1 may also include second indication information, used to indicate to DCAF that PDU session 1 is established.

[0296] Optionally, the notification message #1 may also include a UE ID, where the UE ID may be a UE SUPI or a GPSI, without limitation.

[0297] It should be noted that the SMF / UPF may send a notification message #1 to the DCAF when determining that a specific PDU session is established. The SMF / UPF may actively send the notification message to the DCAF or send the notification message as a response to the subscription request in step 900. This is not limited in the present application. The SMF / UPF may include specific PDU session indication information in the PDU session establishment request, or determine that a specific PDU session is established when the PDU session corresponds to a specific DNN and / or S-NSSAI.

[0298] 903, DCAF records the establishment of an association relationship between UE IP1 and UE ID at time T1.

[0299] Specifically, DCAF can obtain the IP address corresponding to the session establishment time of PDU session 1 of the terminal device from notification message #1, such as UE IP1. After receiving notification message #1, DCAF can record that UE IP1 and UE ID are associated at time T1.

[0300] In some embodiments, the time information T1 may be obtained from the notification message #1.

[0301] In other embodiments, when the notification message #1 does not include historical time information, the DCAF may determine the time when UE IP1 corresponding to the time when PDU session 1 is established (such as the time when notification message #1 is received) is received as time T1.

[0302] 904. UE reports UE data to DCAF.

[0303] Specifically, the UE reports UE data to the DCAF via PDU session 1. Exemplarily, the UE may report the following specific data types to the DCAF, and these data may be reported to the DCAF via a specific PDU session (such as PDU session 1) in the embodiment of the present application.

[0304] Exemplarily, the data reported by the UE may include data and a UE IP address (such as UE IP 1). Optionally, the data reported by the UE may also include a timestamp. Exemplarily, the UE may report a data packet to the DCAF, including the reported data.

[0305] The IP address in the data reported by the UE is generally the private IP address of the UE. If the network is deployed with a NAT mechanism, the private IP address of the UE is converted to the public IP address of the UE after NAT, and then sent to the DCAF.

[0306] 904a, DCAF stores UE data.

[0307] Specifically, after receiving the data reported by the UE, the DCAF may store the data reported by the UE.

[0308] In some embodiments, when storing data reported by UE, DCAF may also record the timestamp information corresponding to the data, and the timestamp may include at least one of the following information: the timestamp of UE data sampling, the timestamp of UE data reporting, the timestamp of data arriving at DCAF, and the timestamp of DCAF storing data.

[0309] In a possible implementation, the DCAF may store the data reported by the UE using the UE IP address as an index, wherein the UE IP address is the IP address carried in the data reported by the UE received by the DCAF.

[0310] In another possible implementation, DCAF may store the data reported by the UE with the UE ID as an index. The UEID comes from the association between the UE ID and the UE IP established by DCAF in step 903. Exemplarily, DCAF may map the UE IP to the UE ID based on the association, and further store the data reported by the UE with the UE ID as an index.

[0311] In another possible implementation, DCAF may store the data reported by the UE using both the UE IP and the UE ID as indexes.

[0312] 905, PDU session 1 is released.

[0313] Specifically, the UE may initiate the release of PDU session 1, for example, by sending a PDU session release request message to the SMF / UPF, where the PDU session release request message is used to request the release of PDU session #1. In response to the PDU session release request message, the SMF / UPF releases PDU session 1.

[0314] 906. SMF / UPF sends notification message #2 to DCAF.

[0315] In some embodiments, the notification message #2 may include the IP address (such as UEIP1) of the PDU session 1 at a historical time. Exemplarily, the historical time may include the time when the PDU session 1 is released, which is not limited.

[0316] Optionally, notification message #2 may also include historical time information. As an example, the historical time information may include time information (such as time information T2) when PDU session 2 is released, which may indicate the time when PDU session 1 is released. As another example, the historical time information may include time information when the IP address of PDU session 1 is released, which may indicate the time when the IP address of PDU session 1 is released.

[0317] Optionally, notification message #2 may also include third indication information, used to indicate to DCAF that PDU session 1 is released.

[0318] Optionally, the notification message #2 may also include a UE ID, where the UE ID may be a UE SUPI or a GPSI, without limitation.

[0319] It should be noted that the SMF / UPF may send a notification message #2 to the DCAF when determining that a specific PDU session is released. The SMF / UPF may actively send the notification message to the DCAF or send the notification message as a response to the subscription request in step 900. This is not limited in the present application. The SMF / UPF may include specific PDU session indication information in the PDU session release request, or determine that the specific PDU session is released when the PDU session corresponds to a specific DNN and / or S-NSSAI.

[0320] 907, DCAF records the release association between UE IP1 and UE ID at time T2.

[0321] Specifically, DCAF can obtain the IP address corresponding to the session release time of PDU session 1 of the terminal device from notification message #2, such as UE IP1. After receiving notification message #2, DCAF can record that the association relationship between UE IP1 and UE ID is released at time T2.

[0322] In some embodiments, the time information T2 may be obtained from the notification message #2.

[0323] In other embodiments, when notification message #2 does not include historical time information, DCAF may determine the time when UE IP1 corresponding to the time when PDU session 1 is released (such as the time when notification message #2 is received) as time T2.

[0324] Through the above steps 903 and 907, DCAF can learn and record that there is an association relationship between UE IP1 and UE ID in the time period from T1 to T2.

[0325] 908, PDU session 2 is established and released (repeating 901 and 907).

[0326] Specifically, the establishment and data reporting process of other PDU sessions of the UE, or the establishment and data reporting process of PDU sessions of other UEs are similar to the above steps 901 to 907.

[0327] At this point, DCAF can save a large number of historical mappings between UE IP addresses and UE IDs, and DCAF stores a large amount of data reported by UEs. These data are saved with UE ID as the index, or with UE IP as the index, or with both UE ID and UE IP as the index. Optionally, DCAF can also save the time information (such as timestamp) corresponding to the data.

[0328] 909, NWDAF sends a data acquisition request message to DCAF.

[0329] Exemplarily, NWDAF, as a consumer entity, sends a data collection request message (UE data collection request) to DCAF, and the data collection request message can be used to request the data of UE at the first time. The first time may include one or more historical times. The historical time mentioned above overlaps with the first time, for example, the first time may fall within the time period corresponding to the historical time in the first information, or the first time may span the time period corresponding to multiple historical times in the first information, or the first time overlaps with the time period corresponding to one or more historical times in the first information.

[0330] The data acquisition request message may include first time information, where the first time information is used to indicate the first time.

[0331] Optionally, the data acquisition request message may include UE ID and / or condition information #2, where condition information #2 is used to indicate the conditions met by the terminal device.

[0332] Exemplarily, the UE ID may be SUPI or GPSI. When the UE ID is GPSI, it may be converted into GPSI first and then sent to the DCAF.

[0333] Exemplarily, condition information #2 can be used to limit the range of UEs, which can be an area range (such as TAsCells, or a longitude and latitude geographic area, etc.) or a location (such as TA ID, cell ID or longitude and latitude geographic location, etc.), used to indicate that only the reported data of the terminal in the area or location is obtained. Accordingly, DCAF can obtain the corresponding UE ID (such as UE ID list) according to condition information #2.

[0334] Exemplarily, the UE data collection request may be an example of the second request message mentioned above, and details may refer to the relevant descriptions mentioned above.

[0335] 910. DCAF retrieves UE historical data according to UE ID and first time information.

[0336] Specifically, the DCAF can obtain the historical time period corresponding to the UE ID and the first time information according to the data acquisition request message, and then retrieve the UE historical data, that is, the data of the UE at the first time, from the data reported by the UE according to the UE ID and the historical time period. The historical time period is an example of the first time.

[0337] In one implementation, if DCAF stores data with UE ID as index (or UE ID and UE IP as index), DCAF can directly retrieve UE historical data from the stored data according to the UE ID and time information obtained in the data acquisition request.

[0338] In another implementation, if DCAF stores data with UE IP as the index (or UE ID and UE IP as the index together), DCAF can first map the UE ID obtained according to the data acquisition request to the UE IP based on the correspondence between the UE ID and the UE IP in the historical time period, and then retrieve the UE historical data from the stored data based on the UE IP.

[0339] 911, DCAF sends UE historical data to NWDAF.

[0340] Exemplarily, the DCAF may send the UE history data to the NWDAF as a response to the data acquisition request in step 909 .

[0341] Therefore, the embodiment of the present application sends the IP address of the PDU session in which the UE reports data to the DCAF through the SMF / UPF, so that the DCAF records the IP address of the PDU session in which the UE reports data at the historical time, so that when there is a demand for the UE to obtain data at the first time, the DCAF can obtain the data of the UE at the first time according to the pre-stored IP address of the UE's PDU session at the historical time. Therefore, the embodiment of the present application can enable the DCAF to obtain the data corresponding to the IP address of the UE's PDU session at the historical time.

[0342] Fig.10 A schematic flow chart of another data acquisition method provided by an embodiment of the present application. The second communication device is SMF or UPF, and the consumer device is NWDAF. The SMF or UPF can locally save the IP address of the session of the terminal device at the historical time. Fig.10 The data acquisition method is described.

[0343] It should be noted that in the embodiment of the present application, when the DCAF communicates with a device in the network (such as SMF / UPF), if the DCAF is an untrusted AF, it may need to be transferred or converted through the NEF. For example, the NEF can realize the conversion of the geographical area outside the network and the area inside the network, the conversion of the UE network outside the network identity or the network inside the network identity, the conversion of the data outside the network and the time inside the network, etc., without limitation.

[0344] 1001, PDU session 1 is established.

[0345] Specifically, step 1001 and Fig. 9 Similar to step 901, you can refer to Fig. 9 Description in .

[0346] After SMF / UPF receives the PDU session establishment request from the UE, if it is determined that the established PDU session 1 is used for the UE to report data to DCAF, the SMF / UPF can determine the first information of the terminal device, and the first information can indicate the IP address of the UE's PDU session 1 at a historical time.

[0347] Exemplarily, the first information may include the IP address of the UE's PDU session 1 at a historical time. Optionally, the first information may also include historical time information. The historical time information may include the time information of the PDU session establishment (such as time T1) and / or the time information of the PDU session release (such as time T2).

[0348] 1002, SMF / UPF records the association between UE IP1 and UE ID at time T1.

[0349] Exemplarily, the SMF / UPF may obtain and record the historical time information T1 and the IP address (such as UE IP1) of the PDU session 1 at the historical time T1. The historical time includes the time when the PDU session 1 is established.

[0350] As an example, the historical time information may include time information (such as time information T1) when PDU session 1 is established, which may indicate the time when PDU session 1 is established. As another example, the historical time information may include time information when the IP address of PDU session 1 is allocated, which may indicate the time when the IP address of PDU session 1 is allocated.

[0351] Optionally, the SMF / UPF may also record the UE ID, where the UE ID may be the UE SUPI or GPSI, without limitation.

[0352] 1003. UE reports UE data to DCAF.

[0353] Specifically, step 1003 and Fig. 9 Step 904 is similar to Fig. 9 Description in .

[0354] 1004, DCAF stores UE data.

[0355] Specifically, step 1004 and Fig. 9 Step 904a is similar to that in Fig. 9 Description in .

[0356] and Fig. 9 The difference in step 904 is that since DCAF does not record the association between the UE IP and UE ID of the UE's PDU session, DCAF cannot store UE data with UE ID as the index.

[0357] 1005, PDU session 1 is released.

[0358] Specifically, step 1005 and Fig. 9 Step 905 is similar to Fig. 9 Description in .

[0359] 1006. DCAF records the release association between UE IP1 and UE ID at time T2.

[0360] Specifically, the SMF / UPF may obtain and record the historical time information T2 and the IP address (such as UE IP1) of the PDU session 1 at the historical time T2. The historical time includes the time when the PDU session 1 is released.

[0361] As an example, the historical time information may include time information (such as time information T2) when PDU session 1 is released, which may indicate the time when PDU session 1 is released. As another example, the historical time information may include time information when the IP address of PDU session 1 is released, which may indicate the time when the IP address of PDU session 1 is released.

[0362] After the above steps 1002 and 1006, SMF / UPF can learn and record that there is an association between UE IP1 and UE ID in the time period from T1 to T2. The UE IP address stored in SMF can be a private network IP address or a public network IP address of the UE, without limitation.

[0363] 1007, PDU session 2 is established and released (repeating 1001 and 1006).

[0364] Specifically, the establishment and data reporting process of other PDU sessions of the UE, or the establishment and data reporting process of PDU sessions of other UEs are similar to the above steps 1001 to 1006.

[0365] So far, DCAF stores a large amount of data reported by UE. These data are saved with UE IP as index. Optionally, DCAF can also save the time information (such as timestamp) corresponding to the data.

[0366] 1008. NWDAF sends a data acquisition request message to DCAF.

[0367] The data acquisition request message is used to request data from the UE at a first time, and may include first time information for indicating the first time.

[0368] Optionally, the data acquisition request message may also include UE ID and / or condition information #2, where condition information #2 is used to indicate the conditions satisfied by the terminal device.

[0369] Specifically, step 1008 and Fig. 9 Similar to step 909, you can refer to Fig. 9 Description in .

[0370] 1009a, DCAF sends UE IP request to SMF / UPF.

[0371] The UE IP request is used to request the IP address of the UE's PDU session at the first time, and the UE IP request includes first time information for indicating the first time. The first time information may come from the data acquisition request message in step 1008 .

[0372] Optionally, the UE IP request may also include UE ID and / or condition information #2, where condition information #2 is used to indicate the condition satisfied by the terminal device. UE ID and / or condition information #2 may also come from the data acquisition request message in step 1008.

[0373] As an example, when the data acquisition request message in step 1008 includes condition information #2, DCAF can obtain the corresponding UE ID list according to the condition information #2. In step 1009a, the UE IP request can carry the UEID list to request the IP address of the corresponding UE session at the first time.

[0374] As another example, when the data acquisition request message in step 1008 includes condition information #2, the UE IP request in step 1009a may carry the condition information #2 to request the IP address of the UE session that meets condition information #2 at the first time.

[0375] 1009b, SMF / UPF sends UE IP response to DCAF.

[0376] Specifically, the SMF / UPF maps the UE IP corresponding to the UE ID indicated in the UE IP request at the first time based on the stored association between the UE IP, UE ID and time, and returns the UE IP to the DACF in the UE IP response.

[0377] In some embodiments, when the UE IP request in step 1009a can carry the condition information #2, the SMF / UPF can obtain the UE ID list corresponding to the condition information #2, and then map the corresponding UE IP for each UE, and finally carry the UE IP list in the UE IP response and return it to the DCAF.

[0378] It should be noted that the number of UE IPs corresponding to the UE at the first time may be one or more, without limitation. For example, when the first time falls within a historical time period, the UE IP corresponding to the UE at the first time is the UE IP of the historical time period; when the first time spans multiple historical time periods, the UE IP corresponding to the UE at the first time is the multiple UE IPs corresponding to the multiple historical time periods; when the first time overlaps with the historical time period, the UE IP corresponding to the UE at the first time is the UE IP corresponding to the overlapping historical time period.

[0379] 1010. DCAF retrieves UE historical data according to UE IP and first time information.

[0380] Specifically, DCAF can obtain the UE IP corresponding to the UE at the first time according to the UE IP response, and then retrieve the UE historical data, that is, the data of the UE at the first time, from the data reported by the UE according to the UE IP and the first time information.

[0381] 1011, DCAF sends UE historical data to NWDAF.

[0382] Therefore, in the embodiment of the present application, by saving the IP address of the PDU session for which the UE reports data to DCAF on the SMF / UPF, when the DCAF receives the UE's first-time data acquisition request, the DCAF requests the UE's first-time IP address from the SMF / UPF on demand. Thus, the DCAF can obtain the UE's data at the first time based on the IP address of the UE's PDU session at the first time, thereby enabling the DCAF to obtain the data corresponding to the IP address of the UE's PDU session at the historical time.

[0383] Fig.11 A schematic flow chart of another data acquisition method provided in an embodiment of the present application. The second communication device is SMF or UPF. The SMF or UPF can send the IP address of the session of the terminal device at the historical time to the NWDAF. Fig.10 The data acquisition method is described.

[0384] It should be noted that in the embodiment of the present application, when the DCAF communicates with a device in the network (such as SMF / UPF), if the DCAF is an untrusted AF, it may need to be transferred or converted through the NEF. For example, the NEF can realize the conversion of the geographical area outside the network and the area inside the network, the conversion of the UE network outside the network identity or the network inside the network identity, the conversion of the data outside the network and the time inside the network, etc., without limitation.

[0385] Optionally, 1100, NWDAF sends a subscription request to SMF / UPF.

[0386] The subscription request is used to obtain the first information of the terminal device, and the first information is used to indicate the IP address of the PDU session of the UE at a historical time. Fig. 9 The relevant description in will not be repeated here.

[0387] 1101, PDU session 1 is established.

[0388] Specifically, step 1101 and Fig. 9 Similar to step 901, you can refer to Fig. 9 The corresponding description in .

[0389] After the SMF / UPF receives the PDU session establishment request from the UE, if it is determined that the established PDU session 1 is used for the UE to report data to the DCAF, the SMF / UPF may determine the first information of the UE, and the first information may indicate the IP address of the UE's PDU session 1 at a historical time. Exemplarily, the first information may be carried in notification message #3 and / or notification message #4.

[0390] 1102, SMF / UPF sends notification message #3 to NWDAF.

[0391] Specifically, notification message #3 and Fig. 9 The notification message #1 in step 902 is similar to that in step 902. Fig. 9 The description in will not be repeated here.

[0392] 1103, NWDAF records the association between UE IP1 and UE ID at time T1.

[0393] Specifically, NWDAF records the association between UE IP1 and UE ID at time T1. Fig. 9 The process of step 903 is similar, please refer to Fig. 9 The description in will not be repeated here.

[0394] 1104. UE reports UE data to DCAF.

[0395] Specifically, step 1104 and Fig. 9 Step 904 is similar to Fig. 9 Description in .

[0396] 1104a, DCAF stores UE data.

[0397] Specifically, step 1104a and Fig. 9 Step 904a is similar to that in Fig. 9 Description in .

[0398] and Fig. 9 The difference from step 904 is that DCAF does not record the association between the UE IP and UE ID of the UE's PDU session, so DCAF cannot store UE data with UE ID as the index.

[0399] 1105, PDU session 1 is released.

[0400] Specifically, step 1105 and Fig. 9 Step 905 is similar to Fig. 9 Description in .

[0401] 1106. SMF / UPF sends notification message #4 to NWDAF.

[0402] Specifically, notification message #4 and Fig. 9 The notification message #2 in step 906 is similar, see Fig. 9 The description in will not be repeated here.

[0403] 1107, NWDAF records the release association between UE IP1 and UE ID at time T2.

[0404] Specifically, NWDAF records the association between UE IP1 and UE ID at time T2. Fig. 9 The process of step 907 is similar, please refer to Fig. 9 The description in will not be repeated here.

[0405] Through the above steps 1103 and 1107, the NWDAF can learn and record that there is an association relationship between the UE IP1 and the UEID in the time period from T1 to T2.

[0406] 1108, PDU session 2 is established and released (repeating 1101 and 1107).

[0407] Specifically, the establishment and data reporting process of other PDU sessions of the UE, or the establishment and data reporting process of PDU sessions of other UEs are similar to the above steps 1101 to 1107.

[0408] So far, DCAF stores a large amount of data reported by UE. These data are saved with UE IP as index. Optionally, DCAF can also save the time information (such as timestamp) corresponding to the data.

[0409] In some embodiments, the consumer equipment may request the DCAF for the UE data at the first time through steps 1109 , 1109 a , and 1109 b in method 1 .

[0410] 1109. The consumer device sends a data acquisition request message to the DCAF.

[0411] 1109a, DCAF sends a UE IP request to NWDAF.

[0412] 1109b, NWDAF sends a UE IP response to DCAF.

[0413] For details, please refer to Fig. 9 For the relevant descriptions in UE IP request and UE IP response, please refer to Fig.10 Related description in .

[0414] In some other embodiments, the consumer equipment may request the DCAF for the UE data at the first time through steps 1109a, 1109b, and 1109 in method 2.

[0415] 1109a, the consumer device sends a UE IP request to the NWDAF.

[0416] 1109b, the NWDAF sends a UE IP response to the consumer device.

[0417] For details, please refer to UE IP request and UE IP response. Fig.10 Related description in .

[0418] 1109, the consumer device sends a data acquisition request to the DCAF to request the data of the UE at the first time. The data acquisition request includes the UE IP and the first time information. The UE IP is obtained through the UE IP response.

[0419] It should be noted that, when the consumer device is the NWDAF itself, steps 1109a and 1109b in method 2 belong to the internal operations of the NWDAF and can be omitted.

[0420] 1110. DCAF retrieves UE historical data according to UE IP and first time information.

[0421] 1111, DCAF sends UE historical data to NWDAF.

[0422] Specifically, steps 1110 and 1111 can refer to Fig.10 Related description in .

[0423] Therefore, in an embodiment of the present application, the IP address of the PDU session in which the UE reports data to DCAF is sent to NWDAF through SMF / UPF. When there is a request for obtaining data at the first time from the UE, the IP address of the UE at the first time is requested from NWDAF on demand. Thus, DCAF can obtain the data of the UE at the first time based on the IP address of the UE's PDU session at the first time, thereby enabling DCAF to obtain the data corresponding to the IP address of the UE's PDU session at the historical time.

[0424] The specific implementation modes of the present application are described in detail above in conjunction with the accompanying drawings. However, the present application is not limited to the specific details in the above implementation modes. Within the technical concept of the present application, the technical solution of the present application can be subjected to a variety of simple modifications, and these simple modifications all belong to the protection scope of the present application. For example, the various specific technical features described in the above specific implementation modes can be combined in any suitable manner without contradiction. In order to avoid unnecessary repetition, the present application will not further explain various possible combinations. For another example, the various different implementation modes of the present application can also be arbitrarily combined, and as long as they do not violate the ideas of the present application, they should also be regarded as the contents disclosed in the present application.

[0425] It should also be understood that in the various method embodiments of the present application, the size of the sequence number of the above-mentioned processes does not mean the order of execution, and the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application. It should be understood that these sequence numbers can be interchanged where appropriate, so that the embodiments of the present application described can be implemented in an order other than those shown or described.

[0426] The above describes the method embodiment of the present application in detail. Figures 12 to 15 , describe in detail the device embodiments of the present application.

[0427] Fig.12 1 is a schematic diagram of the structure of a data acquisition device 10 provided in an embodiment of the present application. The data acquisition device 10 is, for example, the first communication device mentioned above. Fig.12 As shown, the data acquisition device 10 may include: a first acquisition unit 11 and a second acquisition unit 12 .

[0428] A first acquiring unit 11 is used to acquire first information of a terminal device, where the first information is used to indicate address information of a session of the terminal device at a historical time, wherein the session includes a session in which the terminal device reports data to the first communication device;

[0429] The second acquisition unit 12 is used to acquire data of the terminal device at a first time according to the first information, where the first time overlaps with the historical time.

[0430] In some embodiments, the first acquiring unit 11 is specifically used for:

[0431] The first information is acquired from a second communication device, wherein the first information includes historical time information and address information of the session of the terminal device at the historical time, wherein the historical time information is used to indicate the historical time.

[0432] In some embodiments, the historical time information includes:

[0433] Time information of establishment of the session; and / or

[0434] The time information of the session release.

[0435] In some embodiments, the first acquiring unit 11 is specifically used for:

[0436] The first information is acquired from the second communication device, where the first information includes address information corresponding to the terminal device at the time when the session is established.

[0437] In some embodiments, the first information also includes second indication information; wherein the second indication information is used to indicate to the first communication device that the session is established.

[0438] In some embodiments, the first acquiring unit 11 is specifically used for:

[0439] The first information is acquired from the second communication device, where the first information includes address information corresponding to the terminal device at the time when the session is released.

[0440] In some embodiments, the first information also includes third indication information; wherein the third indication information is used to indicate to the first communication device that the session is released.

[0441] In some embodiments, the first acquiring unit 11 is specifically used for:

[0442] Sending a first request message to a second communication device, where the first request message includes first time information, wherein the first time information is used to indicate the first time;

[0443] The first information is received from the second communication device, wherein the first information includes address information of the session of the terminal device at the first time.

[0444] In some embodiments, the second acquiring unit 12 is specifically configured to:

[0445] Determining, according to the first information, first address information of the session of the terminal device at the first time;

[0446] The data of the terminal device at the first time is obtained according to the first address information.

[0447] In some embodiments, the first information further includes an identification of the terminal device, and the apparatus 10 further includes a storage unit for:

[0448] The data of the terminal device is saved using the identifier of the terminal device as an index.

[0449] In some embodiments, the second acquiring unit 12 is specifically configured to:

[0450] Acquire data corresponding to the identifier of the terminal device at the first time.

[0451] In some embodiments, the apparatus 10 further includes a receiving unit, configured to:

[0452] receiving a second request message sent by a consumer device, wherein the second request message includes first time information, and the second request message is used to obtain data of the terminal device at the first time;

[0453] The device 10 further includes a sending unit, configured to:

[0454] A response message is sent to the consumer device, where the response message includes data of the terminal device at the first time.

[0455] In some embodiments, the second request message includes an identifier of the terminal device or first condition information, and the first condition information is used to indicate a condition satisfied by the terminal device.

[0456] In some embodiments, the second request message includes address information of the session of the terminal device at the first time.

[0457] In some embodiments, the apparatus 10 further includes a sending unit, configured to:

[0458] A subscription request message is sent to the second communication device, where the subscription request message is used to obtain the first information of the terminal device.

[0459] In some embodiments, the subscription request message includes an identifier of the terminal device or second condition information, where the second condition information is used to indicate a condition satisfied by the terminal device.

[0460] In some embodiments, the second communication device includes a session management function SMF or a user plane function UPF or a network data analysis function NWDAF.

[0461] In some embodiments, the first communication device comprises a data acquisition application function DCAF.

[0462] In some embodiments, the address information includes an Internet Protocol (IP) address.

[0463] It should be understood that the device embodiment and the method embodiment may correspond to each other, and similar descriptions may refer to the method embodiment. To avoid repetition, they will not be described here. Specifically, Fig.12 The data acquisition device 10 shown can perform Figure 6The corresponding method embodiments, and the aforementioned and other operations and / or functions of each module in the data acquisition device 10 are respectively to achieve Figure 6 For the sake of brevity, the corresponding processes in the corresponding method embodiments are not repeated here.

[0464] Fig.13 Schematic diagram of the structure of a data acquisition device 20 provided in an embodiment of the present application. The data acquisition device 20 is, for example, the second communication device mentioned above. Fig.13 As shown, the data acquisition device 20 may include: an acquisition unit 21 and a sending unit 22.

[0465] An acquiring unit 21 is configured to acquire first information of a terminal device, where the first information is used to indicate address information of a session of the terminal device at a historical time, wherein the session includes a session in which the terminal device reports data to a first communication device;

[0466] The sending unit 22 is configured to send the first information to the first communication device.

[0467] In some embodiments, the first information includes historical time information and address information of the session of the terminal device at the historical time; wherein the historical time information is used to indicate the historical time.

[0468] In some embodiments, the historical time information includes:

[0469] Time information of establishment of the session; and / or

[0470] The time information of the session release.

[0471] In some embodiments, the acquisition unit 21 is specifically used for:

[0472] receiving a session establishment request message from the terminal device, wherein the session establishment request message is used to establish the session;

[0473] The address information corresponding to the terminal device at the time when the session is established is determined as the first information.

[0474] In some embodiments, the session establishment request message includes first indication information, and the first indication information is used to indicate that the session is used for the terminal device to report data to the first communication device.

[0475] In some embodiments, the first information further includes second indication information, wherein the second indication information is used to indicate to the first communication device that the session is established.

[0476] In some embodiments, the acquisition unit 21 is specifically used for:

[0477] receiving a session release request message from the terminal device, wherein the session release request message is used to release the session;

[0478] The address information corresponding to the terminal device at the time when the session is released is determined as the first information.

[0479] In some embodiments, the first information also includes third indication information, wherein the third indication information is used to indicate to the first communication device that the session is released.

[0480] In some embodiments, the acquisition unit 21 is specifically used for:

[0481] receiving a first request message from the first communication device, wherein the first request message includes first time information; wherein the first time information is used to indicate the first time;

[0482] The address information of the session of the terminal device at the first time is determined as the first information.

[0483] In some embodiments, the first information also includes an identification of the terminal device.

[0484] In some embodiments, the apparatus 20 further includes a receiving unit, configured to:

[0485] A subscription request message is received from the first communication device, where the subscription request message is used to obtain the first information of the terminal device.

[0486] In some embodiments, the subscription request message includes an identifier of the terminal device or second condition information, where the second condition information is used to indicate a condition satisfied by the terminal device.

[0487] It should be understood that the device embodiment and the method embodiment may correspond to each other, and similar descriptions may refer to the method embodiment. To avoid repetition, they will not be described here. Specifically, Fig.13 The data acquisition device 20 shown can perform Figure 7 The corresponding method embodiments, and the aforementioned and other operations and / or functions of each module in the data acquisition device 20 are respectively to achieve Figure 7 For the sake of brevity, the corresponding processes in the corresponding method embodiments are not repeated here.

[0488] Fig.14 Schematic diagram of the structure of a data acquisition device 30 provided in an embodiment of the present application. The data acquisition device 30 is, for example, the consumer device mentioned above. Fig.14 As shown, the data acquisition device 30 may include: a sending unit 31 and a receiving unit 32 .

[0489] A sending unit 31 is configured to send a second request message to a first communication device, where the second request message includes first time information, and the second request message is used to obtain data of the terminal device at the first time;

[0490] The receiving unit 32 is used to receive a response message from the first communication device, and the response message includes the data of the terminal device at the first time; the data of the terminal device at the first time is obtained based on the first information of the terminal device, and the first information is used to indicate the address information of the session of the terminal device at a historical time.

[0491] In some embodiments, the second request message includes an identifier of the terminal device or first condition information, and the first condition information is used to indicate a condition satisfied by the terminal device.

[0492] In some embodiments, the second request message includes address information of the session of the terminal device at the first time.

[0493] It should be understood that the device embodiment and the method embodiment may correspond to each other, and similar descriptions may refer to the method embodiment. To avoid repetition, they will not be described here. Specifically, Fig.14 The data acquisition device 30 shown can perform Figure 8 The corresponding method embodiments, and the aforementioned and other operations and / or functions of each module in the data acquisition device 30 are respectively to achieve Figure 8 For the sake of brevity, the corresponding processes in the corresponding method embodiments are not repeated here.

[0494] The video processing device of the embodiment of the present application is described above from the perspective of the functional module in conjunction with the accompanying drawings. It should be understood that the functional module can be implemented in hardware form, can be implemented by instructions in software form, and can also be implemented by a combination of hardware and software modules. Specifically, the steps of the method embodiment in the embodiment of the present application can be completed by the hardware integrated logic circuit and / or software instructions in the processor, and the steps of the method disclosed in the embodiment of the present application can be directly embodied as a hardware encoding processor to execute, or a combination of hardware and software modules in the encoding processor to execute. Optionally, the software module can be located in a mature storage medium in the field such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, an electrically erasable programmable memory, a register, etc. The storage medium is located in a memory, and the processor reads the information in the memory, and completes the steps in the above method embodiment in conjunction with its hardware.

[0495] Fig.15 30 is a schematic block diagram of an electronic device 30 provided in an embodiment of the present application. The electronic device may be the communication device mentioned above, such as a terminal device or a network side device.

[0496] like Fig.15 As shown, the electronic device 30 may include:

[0497] The memory 31 and the processor 32, the memory 31 is used to store the computer program and transmit the program code to the processor 32. In other words, the processor 32 can call and run the computer program from the memory 31 to implement the communication method in the embodiment of the present application.

[0498] For example, the processor 32 may be configured to execute the above method embodiments according to instructions in the computer program.

[0499] In some embodiments of the present application, the processor 32 may include but is not limited to:

[0500] General-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, etc.

[0501] In some embodiments of the present application, the memory 31 includes but is not limited to:

[0502] Volatile memory and / or non-volatile memory. Among them, the non-volatile memory can be read-only memory (ROM), programmable ROM (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM) or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link DRAM (SLDRAM), and direct RAM bus random access memory (DR RAM).

[0503] In some embodiments of the present application, the computer program may be divided into one or more modules, which are stored in the memory 31 and executed by the processor 32 to complete the method provided by the present application. The one or more modules may be a series of computer program instruction segments capable of completing specific functions, and the instruction segments are used to describe the execution process of the computer program in the electronic device.

[0504] like Fig.15 As shown, the electronic device 30 may further include:

[0505] The transceiver 33 may be connected to the processor 32 or the memory 31 .

[0506] The processor 32 may control the transceiver 33 to communicate with other devices, specifically, to send information or data to other devices, or to receive information or data sent by other devices. The transceiver 33 may include a transmitter and a receiver. The transceiver 33 may further include an antenna, and the number of antennas may be one or more.

[0507] It should be understood that the various components in the electronic device are connected via a bus system, wherein the bus system includes not only a data bus but also a power bus, a control bus and a status signal bus.

[0508] According to the method provided in the embodiment of the present application, the embodiment of the present application also provides a communication system, which includes the aforementioned first communication device, second communication device and consumer device. Optionally, the communication system may also include a terminal device.

[0509] The present application also provides a computer storage medium on which a computer program is stored, and when the computer program is executed by a computer, the computer can perform the method of the above method embodiment. In other words, the present application embodiment also provides a computer program product containing instructions, and when the instructions are executed by a computer, the computer can perform the method of the above method embodiment.

[0510] When software is used for implementation, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function according to the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integration. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a digital video disc (digital video disc, DVD)), or a semiconductor medium (e.g., a solid state drive (solid state disk, SSD)), etc.

[0511] Those of ordinary skill in the art will appreciate that the modules 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 to be beyond the scope of this application.

[0512] In the several embodiments provided in the present 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 only schematic. For example, the division of the module is only a logical function division. There may be other division methods in actual implementation, such as multiple modules 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 modules, which can be electrical, mechanical or other forms.

[0513] The modules described as separate components may or may not be physically separated, and the components displayed as modules may or may not be physical modules, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this embodiment. For example, each functional module in each embodiment of the present application may be integrated into a processing module, or each module may exist physically separately, or two or more modules may be integrated into one module.

[0514] The above contents are only specific implementation methods of the embodiments of the present application, but the protection scope of the embodiments of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or replacements within the technical scope disclosed in the embodiments of the present application, which should be included in the protection scope of the embodiments of the present application. Therefore, the protection scope of the embodiments of the present application should be based on the protection scope of the claims.

Claims

1. A data acquisition method, characterized in that: include: The first communication device acquires first information of a terminal device, where the first information is used to indicate address information of a session of the terminal device at a historical time, wherein the session includes a session in which the terminal device reports data to the first communication device; The first communication device obtains data of the terminal device at a first time according to the first information, and the first time overlaps with the historical time.

2. The method according to claim 1, characterized in that The first communication device acquires first information of the terminal device, including: The first communication device obtains the first information from the second communication device, where the first information includes historical time information and address information of the session of the terminal device at the historical time, wherein the historical time information is used to indicate the historical time.

3. The method according to claim 2, characterized in that The historical time information includes: Time information of establishment of the session; and / or The time information of the session release.

4. The method according to claim 1, characterized in that The first communication device acquires first information of the terminal device, including: The first communication device obtains the first information from the second communication device, where the first information includes address information corresponding to the terminal device at the time when the session is established.

5. The method according to claim 4, characterized in that The first information also includes second indication information; wherein the second indication information is used to indicate to the first communication device that the session is established.

6. The method according to claim 1, characterized in that The first communication device acquires first information of the terminal device, including: The first communication device obtains the first information from the second communication device, where the first information includes address information corresponding to the terminal device at the time when the session is released.

7. The method according to claim 6, characterized in that The first information also includes third indication information; wherein the third indication information is used to indicate to the first communication device that the session is released.

8. The method according to claim 1, characterized in that The first communication device acquires first information of the terminal device, including: The first communication device sends a first request message to the second communication device, where the first request message includes first time information, wherein the first time information is used to indicate the first time; The first communication device receives the first information from the second communication device, where the first information includes address information of the session of the terminal device at the first time.

9. The method according to any one of claims 1 to 8, characterized in that: The first communication device acquires data of the terminal device at the first time according to the first information, including: The first communication device determines, according to the first information, first address information of the session of the terminal device at the first time; The first communication device obtains data of the terminal device at the first time according to the first address information.

10. The method according to any one of claims 1 to 7, characterized in that: The first information further includes an identification of the terminal device, and the method further includes: The first communication device stores the data of the terminal device using the identifier of the terminal device as an index.

11. The method according to claim 10, characterized in that The first communication device acquires data of the terminal device at the first time according to the first information, including: The first communication device obtains data corresponding to the identifier of the terminal device at the first time.

12. The method according to any one of claims 1 to 11, characterized in that: The method further comprises: The first communication device receives a second request message sent by a consumer device, where the second request message includes first time information, and the second request message is used to obtain data of the terminal device at the first time; The first communication device sends a response message to the consumer device, where the response message includes data of the terminal device at the first time.

13. The method according to claim 12, characterized in that The second request message includes the identifier of the terminal device or first condition information, where the first condition information is used to indicate a condition satisfied by the terminal device.

14. The method according to claim 12, characterized in that The second request message includes address information of the session of the terminal device at the first time.

15. The method according to claim 2 or 3, characterized in that: Also includes: The first communication device sends a subscription request message to the second communication device, where the subscription request message is used to obtain the first information of the terminal device.

16. The method according to claim 15, characterized in that The subscription request message includes the identifier of the terminal device or second condition information, where the second condition information is used to indicate a condition satisfied by the terminal device.

17. The method according to any one of claims 2 to 8, characterized in that: The second communication device includes a session management function SMF or a user plane function UPF or a network data analysis function NWDAF.

18. The method according to any one of claims 1 to 17, characterized in that: The first communication device comprises a data acquisition application function DCAF.

19. The method according to any one of claims 1 to 18, characterized in that: The address information includes an Internet Protocol (IP) address.

20. A data acquisition method, characterized in that: include: The second communication device acquires first information of the terminal device, where the first information is used to indicate address information of a session of the terminal device at a historical time, wherein the session includes a session in which the terminal device reports data to the first communication device; The second communication device sends the first information to the first communication device.

21. The method according to claim 20, characterized in that The first information includes historical time information and address information of the session of the terminal device at the historical time; wherein the historical time information is used to indicate the historical time.

22. The method according to claim 21, characterized in that The historical time information includes: Time information of establishment of the session; and / or The time information of the session release.

23. The method according to claim 20, characterized in that The second communication device acquires first information of the terminal device, including: The second communication device receives a session establishment request message from the terminal device, where the session establishment request message is used to establish the session; The second communication device determines the address information corresponding to the terminal device at the time when the session is established as the first information.

24. The method according to claim 23, characterized in that The session establishment request message includes first indication information, where the first indication information is used to indicate that the session is used for the terminal device to report data to the first communication device.

25. The method according to claim 23 or 24, characterized in that The first information also includes second indication information, wherein the second indication information is used to indicate to the first communication device that the session is established.

26. The method according to claim 20, characterized in that The second communication device acquires first information of the terminal device, including: The second communication device receives a session release request message from the terminal device, where the session release request message is used to release the session; The second communication device determines the address information corresponding to the terminal device at the time when the session is released as the first information.

27. The method according to claim 26, characterized in that The first information also includes third indication information, wherein the third indication information is used to indicate to the first communication device that the session is released.

28. The method according to claim 20, characterized in that The second communication device acquires first information of the terminal device, including: The second communication device receives a first request message from the first communication device, where the first request message includes first time information; wherein the first time information is used to indicate the first time; The second communication device determines address information of the session of the terminal device at the first time as the first information.

29. The method according to any one of claims 20 to 28, characterized in that: The first information also includes an identification of the terminal device.

30. The method according to any one of claims 21 to 27, characterized in that: Also includes: The second communication device receives a subscription request message from the first communication device, where the subscription request message is used to obtain the first information of the terminal device.

31. The method according to claim 30, characterized in that The subscription request message includes the identifier of the terminal device or second condition information, where the second condition information is used to indicate a condition satisfied by the terminal device.

32. A data acquisition method, characterized in that: include: The consumer device sends a second request message to the first communication device, where the second request message includes first time information, and the second request message is used to obtain data of the terminal device at the first time; The consumer device receives a response message from the first communication device, the response message including data of the terminal device at the first time; The data of the terminal device at the first time is acquired according to the first information of the terminal device, where the first information is used to indicate the address information of the session of the terminal device at a historical time.

33. The method according to claim 32, characterized in that The second request message includes the identifier of the terminal device or first condition information, where the first condition information is used to indicate a condition satisfied by the terminal device.

34. The method according to claim 32, characterized in that The second request message includes address information of the session of the terminal device at the first time.

35. A data acquisition device, characterized in that: include: A first acquiring unit, configured to acquire first information of a terminal device, wherein the first information is used to indicate address information of a session of the terminal device at a historical time, wherein the session includes a session in which the terminal device reports data to a first communication device; A second acquisition unit is configured to acquire data of the terminal device at a first time according to the first information, where the first time overlaps with the historical time.

36. A data acquisition device, characterized in that: include: an acquiring unit, configured to acquire first information of a terminal device, wherein the first information is used to indicate address information of a session of the terminal device at a historical time, wherein the session includes a session in which the terminal device reports data to a first communication device; A sending unit, configured to send the first information to the first communication device.

37. A data acquisition device, characterized in that: include: A sending unit, configured to send a second request message to the first communication device, wherein the second request message includes first time information, and the second request message is used to obtain data of the terminal device at the first time; A receiving unit, configured to receive a response message from the first communication device, wherein the response message includes data of the terminal device at the first time; The data of the terminal device at the first time is acquired according to the first information of the terminal device, where the first information is used to indicate the address information of the session of the terminal device at a historical time.

38. A communication device, characterized in that: include: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory to execute the method described in any one of claims 1 to 19, or the method described in any one of claims 20 to 31, or the method described in any one of claims 32 to 34.

39. A computer-readable storage medium, characterized in that: Used to store a computer program, wherein the computer program enables a computer to execute the method according to any one of claims 1 to 19, or the method according to any one of claims 20 to 31, or the method according to any one of claims 32 to 34.

Images