Data acquisition methods and apparatuses, and device and readable storage medium

Abstract

Provided are data acquisition methods and apparatuses, and a device and a storage medium, by means of which a first communication device can acquire data corresponding to address information of a session of a terminal device within a historical time. A data acquisition method comprises: a first communication device acquiring first information of a terminal device, the first information being used for indicating address information of a session of the terminal device within a historical time, wherein the session comprises a session of the terminal device reporting data to the first communication device; and the first communication device acquiring data of the terminal device within a first time on the basis of the first information, wherein the first time overlaps with the historical time.

Description

Data acquisition method, device, equipment and readable storage medium

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to Chinese patent application No. 202311056764.8 filed in China on August 21, 2023, the entire contents of which are incorporated herein by reference. Technical Field

[0003] 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

[0004] 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.

[0005] In related technologies, before DCAF obtains data from a terminal device, it assumes that the terminal device's user plane session already exists and has not been released. In other words, the IP address corresponding to the terminal device's user plane session always exists and has not changed. When DCAF needs to obtain data, it can immediately use this session and IP address to obtain data from the corresponding terminal device. However, in some scenarios, when the terminal device's session is released or changed, the IP address assigned to the terminal device is deleted or changed, or even assigned to another terminal device, DCAF cannot correctly obtain the corresponding terminal device's historical data based on the original IP address.

[0006] Summary of the Invention

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

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

[0009] The first communication device obtains 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;

[0010] The first communication device obtains data of the terminal device at a first time based on the first information, where the first time overlaps with the historical time.

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

[0012] 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;

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

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

[0015] 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;

[0016] The consumer device receives 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.

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

[0018] A first acquiring unit 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;

[0019] A second acquiring 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.

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

[0021] an acquiring unit, 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;

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

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

[0024] A sending unit, configured to send 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;

[0025] 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.

[0026] 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.

[0027] 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.

[0028] In a ninth aspect, a chip is provided, comprising a processor, wherein the processor is configured 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.

[0029] In a 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.

[0030] 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. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] FIG1 is a schematic diagram of a communication system applicable to an embodiment of the present application;

[0032] FIG2 is a schematic diagram of a network architecture applicable to an embodiment of the present application;

[0033] FIG3 is a schematic diagram of the process of providing terminal device related data to NWDAF;

[0034] FIG4 is a schematic diagram of a process of obtaining a UE IP address corresponding to a UE ID;

[0035] FIG5 is a schematic diagram of a process in which a UE IP address is released in a communication scenario;

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

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

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

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

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

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

[0042] FIG12 is a schematic diagram of a data acquisition device according to an embodiment of the present application;

[0043] FIG13 is a schematic diagram of another data acquisition device according to an embodiment of the present application;

[0044] FIG14 is a schematic diagram of another data acquisition device according to an embodiment of the present application;

[0045] FIG15 is a schematic diagram of an electronic device according to an embodiment of the present application. DETAILED DESCRIPTION

[0046] The technical solution in this application will be described below with reference to the accompanying drawings.

[0047] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: 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.

[0048] Figure 1 shows a schematic diagram of a communication system according to an embodiment of the present application. Figure 1 includes a terminal device 110, an access network device 120, and a core network device 130. Terminal device 110 is connected to access network device 120, and access network device 120 is connected to core network device 130, enabling terminal device 110 to communicate with core network device 130 through access network device 120.

[0049] 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.

[0050] The terminal device 110 may be a device that provides voice / data connectivity to a user, for example, 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 (PLMNs). For example, the terminal device 110 is used to receive a paging message from the access network device 120.

[0051] 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 using wearable technology for 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 just hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include those that are fully functional, large in size, and can achieve complete or partial functions without relying on smartphones, such as smart watches or smart glasses, as well as those 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 smart bracelets and smart jewelry for vital sign monitoring.

[0052] 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 of human-machine interconnection and object-to-object interconnection.

[0053] 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 (OBUs).

[0054] In the embodiment of the present application, the access network device 120 is a device in a 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 and not a limitation, the access network device 120 may include: a next generation Node B (gNB), a transmission reception point (TRP), an evolved Node B (eNB), a radio network controller (RNC), a Node B (NB), a base station controller (BSC), a base transceiver station (BTS), a home base station (e.g., a home evolved Node B, or a home Node B, HNB), a base band unit (BBU), or a wireless fidelity (Wifi) access point (AP).

[0055] In one network structure, the access network device 120 may include a centralized unit (CU) node, a distributed unit (DU) node, or a radio access network (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.

[0056] 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 can be the cell corresponding to the access network device 120 (for example, a base station). The cell can 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, pico cells, 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.

[0057] The core network device 130 is configured to manage one or more access network devices 120. For example, the core network device 130 is configured to send information used by the access network device 120 to send a paging message. 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).

[0058] It should be understood that Figure 1 exemplarily shows a core network device 130, an access network device 120 and a terminal device 110. In some embodiments, the communication system may include other numbers of core network devices, access network devices or terminal devices, and the embodiments of the present application do not limit this.

[0059] FIG2 is a schematic diagram of a network architecture applicable to an embodiment of the present application. 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.

[0060] The access and mobility management function (AMF) is responsible for access and mobility management functions, including user registration, reachability detection, SMF node selection, and mobility state transition management. The AMF can communicate with the UE through the N1 interface and with the (R)AN through the N2 interface.

[0061] The Session Management Function (SMF) is responsible for session management, and its main functions are to control the establishment, modification, and deletion of sessions, the selection of user plane nodes, etc. The SMF can communicate with the User Plane Function (UPF) through the N4 interface.

[0062] The User Plane Function (UPF) primarily provides user plane support, including packet routing and forwarding, serving as a session anchor, acting as an uplink classifier to support routing traffic to the local data network, and acting as a branching point to support multi-homed PDU sessions. The (R)AN and UPF can communicate over the N3 interface, and UPFs can communicate with each other over the N9 interface.

[0063] 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 service data flow or application-based detection, quality of service (QoS), and flow-based charging control. It also provides policies to the AMF and SMF, such as slice selection policy to the AMF and session management policy to the SMF.

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

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

[0066] The application function (AF) interacts with the 3GPP core network to provide services, affecting traffic routing, policy control, etc.

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

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

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

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

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

[0072] It should be noted that the network architecture in Figure 2 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 the network architecture in Figure 2, but also to other network architectures with the same or similar functions as the network architecture.

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

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

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

[0076] In the embodiments of the present application, the “protocol” may refer to a standard protocol in the communications 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.

[0077] The term "and / or" in this document simply describes a relationship between related objects, indicating that three possible relationships exist. For example, "A and / or B" can mean: A exists alone, A and B exist simultaneously, or B exists alone. Additionally, the character " / " in this document generally indicates that the related objects are in an "or" relationship.

[0078] The terms used in the embodiments of this application are intended only to explain the specific embodiments of this application and are not intended to limit this application. The terms "first," "second," "third," and "fourth," etc. in the specification and claims of this application and the accompanying drawings are used to distinguish different objects, not to describe a specific order. In addition, the terms "including" and "having," and any variations thereof, are intended to cover non-exclusive inclusions.

[0079] It should be understood that the "indication" mentioned in the embodiments of this application can be a direct indication, an indirect indication, or an indication of an association. For example, "A indicates B" 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 between A and B.

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

[0081] 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.

[0082] As a specific example, FIG3 shows a schematic diagram of the process of providing terminal device related data to NWDAF. Here, the terminal device is a UE as an example. As shown in FIG3 , steps 301 to 307 are included.

[0083] 301. NF sends an Nnwdaf analysis subscription request to NWDAF.

[0084] 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.

[0085] 302, NWDAF performs AF Discovery.

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

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

[0088] 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.

[0089] 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 Subscription Identifier, GPSI), etc., without limitation.

[0090] 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.

[0091] 304. AF requests and obtains data from UE.

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

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

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

[0095] 306, NWDAF generates data analysis results.

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

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

[0098] 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.

[0099] In Figure 3, the DCAF collects UE-related data indexed by the UE IP address. That is, in step 304, the UE-related data is uploaded via a user plane session corresponding to the UE IP address, such as a PDU session. However, when the NWDAF collects data from the DCAF, it uses the UE ID as the index, carrying the UE ID in step 303. Therefore, the above process requires the DCAF to map the UE ID to the UE IP address.

[0100] As a specific example, FIG4 shows a schematic diagram of a process of obtaining a UE IP address corresponding to a UE ID. As shown in FIG4 , the process includes steps 400 to 407 .

[0101] 400. AF stores UE IP address.

[0102] 401. The AF sends a UE ID acquisition request to the NEF.

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

[0104] 402. The NEF sends a UE context management (CM) acquisition request to the UDM.

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

[0106] 403: UDM sends a UECM acquisition response to NEF.

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

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

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

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

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

[0112] 406. The NEF sends a UE ID acquisition response to the AF.

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

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

[0115] 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.

[0116] In related technologies, before DCAF obtains data from a terminal device, it assumes that the terminal device's user plane session already exists and has not been released. In other words, the IP address corresponding to the terminal device's user plane session always exists and has not changed. When DCAF needs to obtain data, it can immediately use this session and IP address to obtain data from the corresponding terminal device. However, in some scenarios, when a terminal device's session is released or changed, the IP address assigned to the terminal device is deleted or changed, or even assigned to another terminal device, DCAF cannot correctly obtain the corresponding terminal device's historical data based on the original IP address.

[0117] As a specific example, FIG5 shows an example of a communication process in the above scenario, which may include the following steps 501 to 507:

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

[0119] The UE IP1 address is the session used to upload data, such as the IP address corresponding to the user plane PDU session 1.

[0120] 502, PDU session 1 is released.

[0121] For example, PDU session 1 is released. After PDU session 1 is released, SMF / UPF releases the mapping relationship between UE IP1 address and UE ID, and may allocate the IP1 address to other UEs for use.

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

[0123] 504. DCAF sends a UE IP request to SMF / UPF.

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

[0125] 506, PDU session 2 is established.

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

[0127] 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).

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

[0129] To solve the above technical problems, embodiments of the present application provide a data acquisition method, apparatus, device, and storage medium. By associating address information of a session in which a terminal device reports data to a first communication device with a historical time, the first communication device can acquire data of the terminal device at a first time based on the address information of the session in the historical time, thereby enabling the first communication device to acquire data corresponding to the address information of the session in the historical time. The first time and the historical time overlap.

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

[0131] The technical solutions of the embodiments of the present application are described in detail below:

[0132] FIG6 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. As shown in FIG6 , the data acquisition method 600 may include at least part of the following steps 610 to 620:

[0133] 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.

[0134] For example, 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 terminal devices may be one or more, without limitation.

[0135] 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, which is not limited in this application.

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

[0137] 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 single network slice selection assistance information (S-NSSAI). 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.

[0138] In one implementation, 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.

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

[0140] 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.

[0141] 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 IP address as an example. If a session in the network is not based on an IP address, but is based on another type of address (such as an Ethernet address), the provided method is equally applicable.

[0142] For example, 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.

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

[0144] 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.

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

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

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

[0148] 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 terminal device's session at the historical time, wherein the historical time information is used to indicate the historical time.

[0149] Exemplarily, the second communication device may obtain the IP address of the session and the corresponding historical time information during the process from session establishment to release or after the session is released. By obtaining the historical time information and the IP address of the terminal device's session at the historical time, the IP address of the terminal device's session can be associated with the historical time.

[0150] 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 and the ID of the terminal device are associated.

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

[0152] As an example, when the second communication device is SMF, the SMF can obtain the IP address allocated for the session of the terminal device from itself, or obtain the IP address allocated for the session of the terminal device from UPF. This application does not limit this.

[0153] For example, 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. For example, when NAT is deployed on 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.

[0154] 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.

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

[0156] 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 terminal device establishes the session. The time information T1 may refer to time T1 and may include the time information of the session establishment.

[0157] For example, the time information T1 may be the time when the IP address is assigned to the terminal device, the time when the terminal device obtains the IP address, or the time when the IP address of the terminal device's session is associated with the terminal device's ID, without limitation. In other words, at time T1, the IP address of the terminal device's session is associated with the terminal device's ID.

[0158] As another example, the second communication device may obtain corresponding time information T2 when the terminal device's session is released. Time information T2 may refer to time T2. Time information T2 may include the time information of the session release. That is, at time T2, the association between the terminal device IP address and the terminal device ID is released.

[0159] 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, and 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.

[0160] When the session establishment request includes the first indication information and / or the session corresponds to a special DNN and / or S-NSSAI, the second communication device may determine that the session is for the terminal device to report data to the first communication device. In this case, the second communication device may obtain the historical time information and the IP address corresponding to the historical time information. For example, the second communication device may obtain the IP address of the terminal device's session, the terminal device ID, and the corresponding session establishment time information T1 or session release time information T2.

[0161] After obtaining 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.

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

[0163] 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.

[0164] Specifically, the second communication device can obtain the IP address corresponding to the time of session establishment 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.

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

[0166] In one possible implementation, the first information may further include second indication information, where the second indication information is used to indicate to the first communications device that the session has been established, or to indicate that the IP address in the first information has been allocated. Accordingly, the first communications 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 at which the session was established, or that the IP address in the first information has been allocated.

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

[0168] 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 this application.

[0169] 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.

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

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

[0172] 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.

[0173] 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.

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

[0175] In one possible implementation, the first information may further include third indication information, where the third indication information is used to indicate to the first communications device that the session has been released, or to indicate that the IP address in the first information has been released. Accordingly, the first communications 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 that the IP address in the first information has been released.

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

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

[0178] 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.

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

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

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

[0182] 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 a first time; and the first communication device receives first information from the second communication device, where the first information includes the IP address of the terminal device's session at the first time.

[0183] Specifically, the second communication device may 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 terminal device's session at the first time as the first information to the first communication device. Exemplarily, the IP address of the terminal device's session at the first time may be referred to as the first IP address.

[0184] 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 that the first time spans time periods corresponding to multiple historical times, or that the first time overlaps with time periods corresponding to historical times, and this application does not limit this.

[0185] For example, the time periods corresponding to the first time and the historical time overlap, that is, a portion of the first time belongs to the historical time, and the first time may also include a portion of the time belonging to the current and / or future time. For example, the first time is a time period from the beginning of the previous month to the next two months.

[0186] Optionally, for 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, and this application does not limit this.

[0187] In one possible scenario, the second communication device may store the IP addresses of the terminal device at multiple different historical times, where the IP addresses at different historical times may correspond to sessions of the terminal device at different historical times. Upon receiving the first request message, the second communication device may send the IP address corresponding to the historical time including the first time as the IP address of the terminal device's session at the first time to the first communication device.

[0188] Among them, the IP address of the terminal device's session at the first time can be an IP address of a historical time in which the terminal device's session 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.

[0189] Exemplarily, the first request message may include at least one of the terminal device ID and condition information #2. The terminal device ID and condition information #2 are from the second request message sent by the consumer device to the first communication device. For details about the terminal device ID and condition information #2, see the description of the second request message below.

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

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

[0192] In some embodiments, the first communication device may further 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.

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

[0194] The ID of the terminal device may indicate the target terminal of the subscription, which may refer to one or more specific terminal devices or any terminal device without limitation.

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

[0196] Optionally, the subscription request message may further include an event ID (eventID), 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.

[0197] Therefore, through the above-mentioned interaction process between the 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's 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 was established, or recording the IP address of the terminal device's session corresponding to the time when the session was released, etc., without limitation.

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

[0199] Specifically, the first communication device may obtain address information of the session of the terminal device at a historical time based on the first information, and further obtain data of the terminal device at a first time based on the address information at a historical time.

[0200] 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.

[0201] In some embodiments, the first communications device may pre-store data reported by the terminal device at historical times, and then, based on the first information, obtain the data of the terminal device at the first time from the data reported by the terminal device at historical times. The data reported by the terminal device at historical times is reported via the session described above. In embodiments of the present application, the data reported by the terminal device at historical times may be referred to as first data.

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

[0203] 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.

[0204] Exemplarily, the terminal device may report a data packet including the first data and the IP address to the first communication device. In one 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.

[0205] 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 Network Address Translation (NAT) is deployed on the network, 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.

[0206] 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.

[0207] In some embodiments, after the first communication device receives the first data reported by the terminal device, it can store the first data.

[0208] In a possible implementation, the first communication device may store the first data using the IP address of the terminal device as an index. For example, 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.

[0209] In another possible implementation, the first communication device may further store the first data using the terminal device ID as an index. For example, the first communication device may map the IP address associated with the first data to the terminal device ID based on the stored association between the IP address of the terminal device session and the terminal device ID, and then store the first data using the terminal device ID as an index.

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

[0211] 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 when the first data arrives at the first communication device, and a timestamp when the first communication device stores the first data.

[0212] In some embodiments, the first communication device may 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.

[0213] In one possible implementation, when the first information includes historical time information and the IP address of the terminal device's session at the historical time, the first communications device may obtain the IP address corresponding to the first time information from the IP address of the terminal device's session at the historical time as the first IP address. The first time information is used to indicate the first time. Specifically, the first time can be described above.

[0214] 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 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.

[0215] In another possible implementation, when the first information includes the IP address of the terminal device at the first time of the session (ie, the first IP address), the IP address included in the first information may be directly used as the first IP address.

[0216] In some embodiments, when the first communication device saves data with the IP address as the index (or with the IP address and the terminal device ID as the 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.

[0217] 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 terminal device's session at the first time, and then retrieving the data corresponding to the first IP address in the saved data.

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

[0219] Therefore, by storing the first data using the terminal device ID as an index, the first communication device can retrieve the data corresponding to the terminal device ID at the first time from the stored data when it needs to obtain the data at the first time, thereby obtaining the data of the terminal device at the first time. In this case, the first communication device does not need to obtain the IP address of the terminal device session at the first time, which can help improve the efficiency of data acquisition.

[0220] In some embodiments, the first communications device may also receive a second request message sent by the consumer device, the second request message including the first time information, the second request message being used to obtain data from the terminal device at the first time. Exemplarily, the second request message may also be referred to as a UE data collection request, without limitation. The first communications device may then send a response message to the consumer device, the response message including the data from the terminal device at the first time.

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

[0222] Exemplarily, the consumer device may be a device such as NWDAF, AF, RAN, etc. that has a need to obtain terminal device data, and this application does not limit this.

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

[0224] 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 conditions satisfied by the terminal device.

[0225] For example, the terminal device ID 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.

[0226] Exemplarily, condition information #2 is used to limit the range of terminal devices. Exemplarily, the range can be a regional range, such as Tracking Areas (TAs), cells, or a geographic area (such as a latitude and longitude area). The range can also be a specific location, such as a TA ID, cell ID, or latitude and longitude. 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.

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

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

[0229] 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 the historical time, etc., and then obtain the data of the terminal device at the first time according to the first information.

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

[0231] For example, before sending the second request message to the first communication device, the consumer device may obtain the IP address of the terminal device's session at the first time, and then send the second request message containing the IP address 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 terminal device's session at the first time.

[0232] In one possible scenario, when the NWDAF stores the IP addresses of the terminal device's session at historical times, the consumer device can send a third request message to the NWDAF, requesting the IP address of the terminal device's session at the first time. In response to this third request message, the NWDAF sends the IP address of the terminal device's session at the first time to the consumer device. If the consumer device is the NWDAF itself, the IP address of the terminal device's session at the first time can be obtained from the NWDAF itself through internal operations.

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

[0234] Therefore, by carrying the IP address of the terminal device at the first time in the second request message, the first communications device can obtain the data of the terminal device at the first time based on the IP address of the terminal device at the first time. In this case, the first communications device does not need to search for the IP address of the terminal device at the first time from the IP addresses of the terminal device's previous sessions, thereby improving the efficiency of data acquisition.

[0235] In other embodiments, the terminal device itself can store the terminal device's historical data and IP address at the historical time, for example, using the terminal device's IP address or ID as an index to store the historical data. Optionally, the terminal device can also store the time information corresponding to the data. In this case, the first communication device can request the terminal device for the data corresponding to the first time based on the first information.

[0236] FIG7 is a schematic flow chart of another data acquisition method 700 provided in an embodiment of the present application. The data acquisition method can be executed by the second communication device. As shown in FIG7 , the data acquisition method 700 can include at least part of the following steps 710 and 720:

[0237] 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.

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

[0239] 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.

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

[0241] 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.

[0242] 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 addresses), the provided method is also applicable.

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

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

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

[0246] 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 a first time; and the second communication device determines the IP address of the terminal device's session at the first time as the first information. In other words, the first information may include the IP address of the terminal device's session at the first time.

[0247] As an example, when the second communication device is an 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.

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

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

[0250] 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 terminal device at the time the session is established as the first information. In other words, the first information may include the IP address corresponding to the terminal device at the time the session is established.

[0251] Optionally, the session establishment request message may include first indication information, where 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.

[0252] 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.

[0253] 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.

[0254] Optionally, the first information may further include second indication information; the second indication information is used to indicate to the first communications device that the session has been established, or to indicate that the IP address in the first information has been allocated. Accordingly, the first communications 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 was established, or that the IP address in the first information has been allocated.

[0255] 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 was established. Alternatively, when the first communications 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 was established.

[0256] 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 this application.

[0257] 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.

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

[0259] 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 terminal device at the time of session release as the first information. In other words, the first information may include the IP address corresponding to the terminal device at the time of session release.

[0260] Optionally, the first information may further include third indication information; the third indication information is used to indicate to the first communications device that the session is released, or to indicate that the IP address in the first information is released. Accordingly, the first communications 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 that the IP address in the first information is released.

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

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

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

[0264] 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 terminal device's session 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.

[0265] In some embodiments, the second communication device may also send a subscription request message to a third communication device. The subscription request message is used to obtain the first information of the terminal device. For example, 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 a UPF. In response to the subscription request message, the SMF / UPF may send the first information of the terminal device to the NWDAF.

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

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

[0268] 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.

[0269] 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.

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

[0271] 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.

[0272] At 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. The data of the terminal device at the first time is obtained based on first information of the terminal device, the first information indicating address information of a session of the terminal device at a historical time.

[0273] 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.

[0274] 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.

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

[0276] 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 will not be repeated here.

[0277] Below, several specific examples provided by the embodiments of the present application will be described in conjunction with Figures 9 to 11. Specifically, the following description will be based on an example in which the first communication device is a DCAF, the terminal device is a UE, the session is a PDU session, and the address information is an IP address. In the following embodiments, the terms "IP," "IP address," "UE IP," and "UE IP address" have the same meaning.

[0278] Figure 9 is a schematic flow chart of a data acquisition method provided in an embodiment of the present application. The second communication device is an SMF or UPF, and the consumer device is an NWDAF. The SMF or UPF can send the IP address of the terminal device's session at historical times to the DCAF. The data acquisition method is described below with reference to Figure 9.

[0279] It should be noted that in the embodiment of the present application, when the DCAF communicates with a device within the network (such as an 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 implement conversion between an off-network geographical area and an on-network area, conversion between a UE off-network identity and an on-network identity, conversion between off-network data and on-network time, etc., without limitation.

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

[0281] 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 UE's PDU session at a historical time. Exemplarily, the first information may include the IP address of the terminal device's session at a historical time.

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

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

[0284] 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;

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

[0286] Condition information (filter) #1: Used to limit the scope of the target terminal. The scope can be an area range (such as TAs Cells, or a longitude and latitude geographic area, etc.) or a location (such as a TA ID, cell ID, or a longitude and latitude geographic location, etc.), which is used to indicate that only the IP addresses corresponding to the sessions when the terminals in the area or location report data are obtained; the scope can also be a time range, which is used to indicate that the IP addresses corresponding to the sessions when the terminals report data within a specific time period are obtained.

[0287] Specifically, the subscription request is an example of the subscription request message mentioned above. For details, please refer to the relevant description above.

[0288] 901, PDU session 1 is established.

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

[0290] 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.

[0291] 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.

[0292] Specifically, the PDU session establishment request is an example of the session establishment request mentioned above. For details, please refer to the relevant description above.

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

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

[0295] In some embodiments, the notification message #1 may include the IP address (eg, UE IP1) of the PDU session 1 at a historical time. Exemplarily, the historical time may include the time when the PDU session 1 was established, which is not limited.

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

[0297] 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 was established, which may indicate the time when PDU session 1 was established. As another example, the historical time information may include time information when the IP address of PDU session 1 was allocated, which may indicate the time when the IP address of PDU session 1 was allocated.

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

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

[0300] 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 proactively send the notification message to the DCAF or send the notification message in response to the subscription request in step 900. This is not limited in this 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.

[0301] 903. The DCAF record establishes an association between UE IP1 and UE ID at time T1.

[0302] Specifically, DCAF can obtain the IP address corresponding to the session establishment time of the terminal device's PDU session 1 from notification message #1, such as UE IP1. After receiving notification message #1, DCAF can record that the association relationship between UE IP1 and UE ID is established at time T1.

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

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

[0305] 904. The UE reports UE data to the DCAF.

[0306] Specifically, the UE reports UE data to the DCAF via PDU session 1. For example, 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.

[0307] 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.

[0308] The IP address in the data reported by the UE is generally the UE's private IP address. If the network deploys a NAT mechanism, the UE's private IP address is converted to the UE's public IP address after NAT and then sent to the DCAF.

[0309] 904a, DCAF stores UE data.

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

[0311] In some embodiments, when storing data reported by the UE, the DCAF may also record the timestamp information corresponding to the data. 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 the DCAF, and the timestamp of DCAF storing data.

[0312] In one possible implementation, the DCAF may store 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.

[0313] In another possible implementation, the DCAF may store the data reported by the UE using the UE ID as an index. The UE ID is derived from the association between the UE ID and the UE IP address established by the DCAF in step 903. For example, the DCAF may map the UE IP address to the UE ID based on the association, and further store the data reported by the UE using the UE ID as an index.

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

[0315] 905, PDU session 1 is released.

[0316] 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.

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

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

[0319] 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 was released, which may indicate the time when PDU Session 1 was released. As another example, the historical time information may include time information when the IP address of PDU Session 1 was released, which may indicate the time when the IP address of PDU Session 1 was released.

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

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

[0322] 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 proactively send the notification message to the DCAF or send the notification message in response to the subscription request in step 900. This is not limited in this 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.

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

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

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

[0326] In other embodiments, when the notification message #2 does not include historical time information, the DCAF may determine the time when UE IP1 receives the release of PDU session 1 (eg, the time when notification message #2 is received) as time T2.

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

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

[0329] 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.

[0330] At this point, DCAF can store a large number of historical mappings between UE IP addresses and UE IDs, and also stores a large amount of data reported by UEs. This data is stored either by UE ID, by UE IP, or by both. Optionally, DCAF can also store the time information (such as timestamps) corresponding to the data.

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

[0332] Exemplarily, the NWDAF, as a consumer entity, sends a data collection request message (UE data collection request) to the DCAF. The data collection request message can be used to request data from the UE at a first time. The first time may include one or more historical times. The historical times mentioned above may overlap 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 may overlap with the time period corresponding to one or more historical times in the first information.

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

[0334] 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.

[0335] For example, the UE ID may be SUPI or GPSI. When the UE ID is GPSI, it may be converted into GPSI before being sent to the DCAF.

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

[0337] Exemplarily, the UE data collection request may be an example of the second request message mentioned above. For details, please refer to the relevant description above.

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

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

[0340] 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.

[0341] 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.

[0342] 911. DCAF sends UE historical data to NWDAF.

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

[0344] Therefore, in the embodiment of the present application, the IP address of the PDU session in which the UE reports data is sent to the DCAF via 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. This allows the DCAF to obtain the UE's data at the first time based on the pre-stored IP address of the UE's PDU session at the historical time when the UE needs to obtain data. Therefore, in the embodiment of the present application, the DCAF can obtain the data corresponding to the IP address of the UE's PDU session at the historical time.

[0345] Figure 10 is a schematic flow chart of another data acquisition method provided in an embodiment of the present application. The second communication device is an SMF or UPF, and the consumer device is an NWDAF. The SMF or UPF can locally store the IP addresses of the terminal device's sessions at historical times. This data acquisition method is described below in conjunction with Figure 10.

[0346] It should be noted that in the embodiment of the present application, when the DCAF communicates with a device within the network (such as an 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 implement conversion between an off-network geographical area and an on-network area, conversion between a UE off-network identity and an on-network identity, conversion between off-network data and on-network time, etc., without limitation.

[0347] 1001, PDU session 1 is established.

[0348] Specifically, step 1001 is similar to step 901 in FIG. 9 , and reference may be made to the description in FIG. 9 .

[0349] 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.

[0350] 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).

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

[0352] Exemplarily, the SMF / UPF may obtain and record historical time information T1 and the IP address (eg, 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.

[0353] 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.

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

[0355] 1003. The UE reports UE data to the DCAF.

[0356] Specifically, step 1003 is similar to step 904 in FIG. 9 , and reference may be made to the description in FIG. 9 .

[0357] 1004. DCAF stores UE data.

[0358] Specifically, step 1004 is similar to step 904a in FIG. 9 , and reference may be made to the description in FIG. 9 .

[0359] Different from step 904 in FIG. 9 , since DCAF does not record the association between the UE IP and the UE ID of the UE's PDU session, DCAF cannot store UE data using the UE ID as an index.

[0360] 1005, PDU session 1 is released.

[0361] Specifically, step 1005 is similar to step 905 in FIG. 9 , and reference may be made to the description in FIG. 9 .

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

[0363] Specifically, the SMF / UPF may obtain and record the historical time information T2 and the IP address (eg, 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.

[0364] 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.

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

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

[0367] 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.

[0368] At this point, DCAF stores a large amount of data reported by UEs. This data is stored using the UE IP as an index. Optionally, DCAF can also store the time information corresponding to the data (such as a timestamp).

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

[0370] 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.

[0371] 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 met by the terminal device.

[0372] Specifically, step 1008 is similar to step 909 in FIG. 9 , and reference may be made to the description in FIG. 9 .

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

[0374] 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 .

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

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

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

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

[0379] 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.

[0380] 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.

[0381] It should be noted that the number of UE IP addresses 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 address corresponding to the UE at the first time is the UE IP address for that historical time period; when the first time spans multiple historical time periods, the UE IP address corresponding to the UE at the first time is the multiple UE IP addresses corresponding to those multiple historical time periods; and when the first time overlaps with a historical time period, the UE IP address corresponding to the UE at the first time is the UE IP address corresponding to the overlapping historical time period.

[0382] 1010. DCAF retrieves UE historical data based on UE IP and first time information.

[0383] Specifically, the DCAF may 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.

[0384] 1011. DCAF sends UE historical data to NWDAF.

[0385] Therefore, in an embodiment of the present application, the IP address of the PDU session in which the UE reports data to the DCAF is saved 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. In this way, 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.

[0386] Figure 11 is a schematic flow chart of another data acquisition method provided in an embodiment of the present application. The second communication device is an SMF or UPF. The SMF or UPF can send the IP address of the terminal device's session at a historical time to the NWDAF. This data acquisition method is described below in conjunction with Figure 10.

[0387] It should be noted that in the embodiment of the present application, when the DCAF communicates with a device within the network (such as an 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 implement conversion between an off-network geographical area and an on-network area, conversion between a UE off-network identity and an on-network identity, conversion between off-network data and on-network time, etc., without limitation.

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

[0389] 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 UE's PDU session at a historical time. Specifically, the subscription request can refer to the relevant description in Figure 9, which will not be repeated here.

[0390] 1101, PDU session 1 is established.

[0391] Specifically, step 1101 is similar to step 901 in FIG. 9 , and reference may be made to the corresponding description in FIG. 9 .

[0392] After the SMF / UPF receives the PDU session establishment request from the UE, if it is determined that the established PDU session 1 is for the UE to report data to the DCAF, the SMF / UPF may determine the first information of the UE, which 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.

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

[0394] Specifically, notification message #3 is similar to notification message #1 in step 902 in FIG. 9 . Please refer to the description in FIG. 9 , and no further details will be given here.

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

[0396] Specifically, the process of NWDAF recording the association between UE IP1 and UE ID at time T1 is similar to step 903 in FIG. 9 , and reference may be made to the description in FIG. 9 , which will not be repeated here.

[0397] 1104. The UE reports UE data to the DCAF.

[0398] Specifically, step 1104 is similar to step 904 in FIG. 9 , and reference may be made to the description in FIG. 9 .

[0399] 1104a, DCAF stores UE data.

[0400] Specifically, step 1104a is similar to step 904a in FIG. 9 , and reference may be made to the description in FIG. 9 .

[0401] Different from step 904 in FIG. 9 , DCAF does not record the association between the UE IP and the UE ID of the UE's PDU session, so DCAF cannot store UE data using the UE ID as an index.

[0402] 1105, PDU session 1 is released.

[0403] Specifically, step 1105 is similar to step 905 in FIG. 9 , and reference may be made to the description in FIG. 9 .

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

[0405] Specifically, notification message #4 is similar to notification message #2 in step 906 in FIG. 9 . Please refer to the description in FIG. 9 , and no further details will be given here.

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

[0407] Specifically, the process of establishing the association relationship between UE IP1 and UE ID recorded by NWDAF at time T2 is similar to step 907 in FIG. 9 , and reference may be made to the description in FIG. 9 , which will not be repeated here.

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

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

[0410] 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.

[0411] At this point, DCAF stores a large amount of data reported by UEs. This data is stored using the UE IP as an index. Optionally, DCAF can also store the time information corresponding to the data (such as a timestamp).

[0412] In some embodiments, the consumer device may request the UE data at the first time from the DCAF through steps 1109 , 1109 a , and 1109 b in Method 1 .

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

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

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

[0416] Specifically, the data acquisition request message may refer to the relevant description in FIG. 9 , and the UE IP request and UE IP response may refer to the relevant description in FIG. 10 .

[0417] In some other embodiments, the consumer device may request the UE data at the first time from the DCAF through steps 1109a, 1109b, and 1109 in mode 2.

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

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

[0420] Specifically, for UE IP request and UE IP response, please refer to the relevant description in Figure 10.

[0421] 1109. The consumer device sends a data acquisition request to the DCAF to request the UE's data 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.

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

[0423] 1110. DCAF retrieves UE historical data based on UE IP and first time information.

[0424] 1111. DCAF sends UE historical data to NWDAF.

[0425] Specifically, steps 1110 and 1111 may refer to the relevant description in FIG10 .

[0426] Therefore, in an embodiment of the present application, the IP address of the PDU session in which the UE reports data to the DCAF is sent to the NWDAF through the 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 the NWDAF on demand, so that the 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 the DCAF to obtain the data corresponding to the IP address of the UE's PDU session at the historical time.

[0427] The specific embodiments 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 embodiments. Within the technical concept of the present application, a variety of simple modifications can be made to the technical solution of the present application, and these simple modifications all fall within the scope of protection of the present application. For example, the various specific technical features described in the above specific embodiments can be combined in any suitable manner unless there is any contradiction. In order to avoid unnecessary repetition, the present application will not further explain various possible combinations. For another example, the various different embodiments 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.

[0428] It should also be understood that in the various method embodiments of the present application, the order of the sequence numbers of the above-mentioned processes does not imply the order of execution. 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.

[0429] The method embodiment of the present application is described in detail above. The following describes in detail an apparatus embodiment of the present application in conjunction with Figures 12 to 15.

[0430] FIG12 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. As shown in FIG12 , the data acquisition device 10 may include: a first acquisition unit 11 and a second acquisition unit 12.

[0431] A first acquiring unit 11 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 the first communication device;

[0432] The second acquiring unit 12 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.

[0433] In some embodiments, the first acquiring unit 11 is specifically configured to:

[0434] The first information is acquired from a 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.

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

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

[0437] Time information of session release.

[0438] In some embodiments, the first acquiring unit 11 is specifically configured to:

[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 established.

[0440] 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.

[0441] In some embodiments, the first acquiring unit 11 is specifically configured to:

[0442] 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.

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

[0444] In some embodiments, the first acquiring unit 11 is specifically configured to:

[0445] Sending 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;

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

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

[0448] determining, based on the first information, first address information of the session of the terminal device at the first time;

[0449] Acquire data of the terminal device at the first time according to the first address information.

[0450] In some embodiments, the first information further includes an identifier of the terminal device, and the apparatus 10 further includes a storage unit configured to:

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

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

[0453] Obtain data corresponding to the identifier of the terminal device at the first time.

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

[0455] receiving 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;

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

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

[0458] In some embodiments, the second request message includes 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.

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

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

[0461] Send 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.

[0462] 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.

[0463] 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.

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

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

[0466] It should be understood that the device embodiments and method embodiments may correspond to each other, and similar descriptions may refer to the method embodiments. To avoid repetition, no further description is given here. Specifically, the data acquisition device 10 shown in FIG12 can execute the method embodiment corresponding to FIG6, and the aforementioned and other operations and / or functions of the various modules in the data acquisition device 10 are respectively for implementing the corresponding processes in the method embodiment corresponding to FIG6. For the sake of brevity, no further description is given here.

[0467] FIG13 is a 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. As shown in FIG13 , the data acquisition device 20 may include: an acquisition unit 21 and a sending unit 22.

[0468] 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;

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

[0470] 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.

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

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

[0473] Time information of session release.

[0474] In some embodiments, the acquiring unit 21 is specifically configured to:

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

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

[0477] 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.

[0478] 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.

[0479] In some embodiments, the acquiring unit 21 is specifically configured to:

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

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

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

[0483] In some embodiments, the acquiring unit 21 is specifically configured to:

[0484] receiving 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;

[0485] Address information of the session of the terminal device at the first time is determined as the first information.

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

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

[0488] 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.

[0489] 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.

[0490] It should be understood that the device embodiments and method embodiments may correspond to each other, and similar descriptions may refer to the method embodiments. To avoid repetition, they will not be described in detail here. Specifically, the data acquisition device 20 shown in FIG13 can execute the method embodiment corresponding to FIG7, and the aforementioned and other operations and / or functions of each module in the data acquisition device 20 are respectively for implementing the corresponding processes in the method embodiment corresponding to FIG7. For the sake of brevity, they will not be described in detail here.

[0491] FIG14 is a 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. As shown in FIG14 , the data acquisition device 30 may include: a sending unit 31 and a receiving unit 32.

[0492] A sending unit 31 is configured to send 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;

[0493] 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.

[0494] In some embodiments, the second request message includes 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.

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

[0496] It should be understood that the device embodiments and method embodiments may correspond to each other, and similar descriptions may refer to the method embodiments. To avoid repetition, they will not be described in detail here. Specifically, the data acquisition device 30 shown in FIG14 can execute the method embodiment corresponding to FIG8, and the aforementioned and other operations and / or functions of each module in the data acquisition device 30 are respectively for implementing the corresponding processes in the method embodiment corresponding to FIG8. For the sake of brevity, they will not be described in detail here.

[0497] The video processing device of the embodiment of the present application is described above from the perspective of functional modules in conjunction with the accompanying drawings. It should be understood that the functional module can be implemented in the form of hardware, can be implemented by instructions in the form of software, 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 being executed by a hardware encoding processor, or can be executed by a combination of hardware and software modules in the encoding processor. Optionally, the software module can be located in a mature storage medium in the art 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 the memory, and the processor reads the information in the memory and completes the steps in the above method embodiment in conjunction with its hardware.

[0498] Figure 15 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.

[0499] As shown in FIG15 , the electronic device 30 may include:

[0500] The memory 31 and the processor 32 are configured to store computer programs 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.

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

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

[0503] 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.

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

[0505] Volatile memory and / or non-volatile memory. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. 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).

[0506] 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 implement the method provided by the present application. The one or more modules may be a series of computer program instruction segments capable of implementing specific functions, and the instruction segments are used to describe the execution process of the computer program in the electronic device.

[0507] As shown in FIG15 , the electronic device 30 may further include:

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

[0509] The processor 32 can control the transceiver 33 to communicate with other devices. Specifically, it can send information or data to other devices or 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.

[0510] 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.

[0511] 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.

[0512] The present application also provides a computer storage medium having a computer program stored thereon, which, when executed by a computer, enables the computer to perform the method of the above-mentioned method embodiment. In other words, the present application also provides a computer program product containing instructions, which, when executed by a computer, enables the computer to perform the method of the above-mentioned method embodiment.

[0513] 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 device. 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 one website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. 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 integrated. 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 (DVD)), or a semiconductor medium (e.g., a solid state drive (SSD)).

[0514] Those skilled 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 beyond the scope of this application.

[0515] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the modules is merely a logical function division. In actual implementation, there may be other division methods, 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.

[0516] Modules described as separate components may or may not be physically separate, and components displayed as modules may or may not be physical modules, i.e., they may be located in one place or distributed across multiple network elements. Some or all of the modules may be selected based on actual needs to achieve the purpose of the present embodiment. For example, the functional modules in the various embodiments 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 a single module.

[0517] The above content is merely a specific implementation of the embodiments of the present application, but the scope of protection of the embodiments of the present application is not limited thereto. Any person skilled in the art who can easily conceive of changes or substitutions within the technical scope disclosed in the embodiments of the present application should be included in the scope of protection of the embodiments of the present application. Therefore, the scope of protection of the embodiments of the present application should be based on the scope of protection of the claims.

Claims

1. A data acquisition method, comprising: 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, wherein: 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, wherein: 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, wherein: 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, wherein: 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, wherein: 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, wherein: 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, wherein: 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, wherein: 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, wherein: 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, wherein: 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, further comprising: 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, wherein: 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, wherein: 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, further comprising: 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, wherein: 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, wherein: 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, wherein: The first communication device comprises a data acquisition application function DCAF.

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

20. A data acquisition method, comprising: 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, 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.

22. The method according to claim 21, wherein: 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, wherein: 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, wherein: 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, wherein: 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 of claim 20, wherein: 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, wherein: 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 of claim 20, wherein: 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, wherein: The first information also includes an identification of the terminal device.

30. The method according to any one of claims 21 to 27, further comprising: 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, wherein: 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, comprising: 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 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.

33. The method of claim 32, wherein: 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 of claim 32, wherein: The second request message includes address information of the session of the terminal device at the first time.

35. A data acquisition device, comprising: 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, comprising: 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, comprising: 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 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.

38. A communication device comprising: 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 for storing a computer program, wherein the computer program causes 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