WO2021135950A1 - 数据管理方法及***、关联子***和计算机可读介质 - Google Patents

数据管理方法及***、关联子***和计算机可读介质 Download PDF

Info

Publication number
WO2021135950A1
WO2021135950A1 PCT/CN2020/136933 CN2020136933W WO2021135950A1 WO 2021135950 A1 WO2021135950 A1 WO 2021135950A1 CN 2020136933 W CN2020136933 W CN 2020136933W WO 2021135950 A1 WO2021135950 A1 WO 2021135950A1
Authority
WO
WIPO (PCT)
Prior art keywords
user
log
plane information
data
data management
Prior art date
Application number
PCT/CN2020/136933
Other languages
English (en)
French (fr)
Inventor
连超
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to EP20911202.8A priority Critical patent/EP4084415A4/en
Publication of WO2021135950A1 publication Critical patent/WO2021135950A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/06—Generation of reports
    • H04L43/062—Generation of reports related to network traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/04—Processing captured monitoring data, e.g. for logfile generation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/02—Capturing of monitoring data
    • H04L43/026—Capturing of monitoring data using flow identification
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/08—Testing, supervising or monitoring using real traffic

Definitions

  • the present disclosure relates to the field of communication technology, and in particular to a data management method, an associated subsystem, a computer-readable medium, and a data management system.
  • IP traceability is of great significance to national security, especially in anti-terrorism and criminal record tracing.
  • IP traceability solutions for 2G, 3G and 4G networks.
  • traffic consumption is more, the network topology is more complex, and IP traceability is more important.
  • data volume and terminal number of 5G blowout, and the corresponding big data analysis needs also need to be met.
  • 5G networks are quite different from previous network deployments.
  • the control plane and the user plane are completely separated; at the same time, 5G networks mostly adopt virtualized deployment and collect information through the hardware level.
  • the networking is complicated, difficult, and less feasible, and For network elements deployed in a composite manner, the signaling of the corresponding interface cannot be collected.
  • the present disclosure aims to solve one of the above technical problems at least to a certain extent, and proposes a data management method, an associated subsystem, a computer-readable medium, and a data management system.
  • embodiments of the present disclosure provide a data management method, including: obtaining user control plane information collected by a session management function entity; obtaining user data plane information collected by a user plane function entity; The user control plane information and the user data plane information are associated and merged to generate a user traffic log.
  • the embodiments of the present disclosure provide an associated subsystem, including: one or more processors; a storage device for storing one or more programs; when the one or more programs are used by the one or more A plurality of processors execute, so that the one or more processors implement the data management method as described in the foregoing embodiment.
  • embodiments of the present disclosure provide a computer-readable medium on which a computer program is stored, and when the program is executed by a processor, the steps in the data management method described in the above-mentioned embodiments are implemented.
  • embodiments of the present disclosure provide a data management system, including: a session management function entity, a plurality of user plane function entities, a plurality of network address translators corresponding to the plurality of user plane function entities one-to-one, and There are multiple associated subsystems in one-to-one correspondence with multiple user plane functional entities; wherein, the associated subsystem adopts the associated subsystem as described in the above-mentioned embodiment.
  • FIG. 1 is a flowchart of a data management method provided by an embodiment of the disclosure
  • FIG. 3 is a flowchart of yet another data management method provided by an embodiment of the disclosure.
  • FIG. 4 is a flowchart of yet another data management method provided by an embodiment of the disclosure.
  • FIG. 5 is a flowchart of yet another data management method provided by an embodiment of the present disclosure.
  • FIG. 6 is a flowchart of yet another data management method provided by an embodiment of the disclosure.
  • FIG. 7 is a schematic structural diagram of a data management system provided by an embodiment of the disclosure.
  • FIG. 8 is a schematic structural diagram of a system architecture applicable to the data management method provided by an embodiment of the present disclosure.
  • the data management method provided by the present disclosure can be used to generate IP records based on the corresponding information of the control plane and the user plane, and can meet the requirements of corresponding IP traceability and data analysis.
  • FIG. 1 is a flowchart of a data management method provided by an embodiment of the disclosure. As shown in Figure 1, the method includes:
  • Step S1 Obtain user control plane information collected by a session management function entity (Session Management Function, SMF for short).
  • Session Management Function Session Management Function
  • user control plane information includes: session management function entity identification and other protocol data unit session information, International Mobile Subscriber Identity (IMSI), mobile subscriber number (Mobile Subscriber International ISDN/PSTN number) , MSISDN for short) and International Mobile Equipment Identity (IMEI for short) and other user identity information, location information, billing information, and policy information.
  • IMSI International Mobile Subscriber Identity
  • IMEI International Mobile Equipment Identity
  • step S1 the step of obtaining user control plane information collected by the session management function entity, specifically includes:
  • the session management function entity sends the user control plane information to the closest associated subsystem. After that, multiple associated subsystems share the user control plane information, reducing the amount of network information and remote transmission.
  • the use of the soft acquisition interface can avoid the network complexity introduced by virtualization.
  • the soft acquisition interface directly uses the internal data of the network element, and the information contained in the network element itself is more comprehensive.
  • the customized soft acquisition interface has simple encoding and decoding, and no additional network storage is required.
  • Device (Network Attached Storage, NAS for short) decryption does not require complicated protocol stack association, and an effective control plane and user plane association can be completed in accordance with a simple corresponding association method.
  • step S1 the step of obtaining user control plane information collected by the session management function entity, specifically includes:
  • the user control plane information collected by the session management function entity is obtained.
  • the protocol data unit session process includes: a protocol data unit session creation process, a protocol data unit session modification process, and a protocol data unit session release process.
  • the user control plane information is obtained from the session management functional entity based on the protocol data unit session process, that is, the user control plane information is obtained in the protocol data unit session creation process, the protocol data unit session modification process, and the protocol data unit session release process.
  • the user control plane information when the user control plane information carries the creation process identifier, it means that the protocol data unit session creation process is in progress. At this time, the data area is created and the corresponding information is stored in the data area; when the user control plane information carries When the process identifier is modified, it means that the protocol data unit session modification process is in progress, and the data area is updated at this time; when the user control plane information carries the release process identifier, it means that the protocol data unit session release process is in progress, and the data is released at this time Area.
  • Step S2 Obtain user data plane information collected by a user plane function entity (User Plane Function, UPF for short).
  • a user plane function entity User Plane Function, UPF for short.
  • the user data plane information includes: traffic information and deep packet inspection (Deep Packet Inspection, DPI for short) information.
  • DPI deep packet inspection
  • the in-depth packet inspection information includes: session management function entity identification and other protocol data unit session information, quintuple information, time information, application layer protocol, uniform resource locator (URL), application type, etc. .
  • step S2 the step of obtaining user data plane information collected by the user plane function entity, specifically includes:
  • the user data plane information reported by the user plane functional entity is received through the soft acquisition interface configured by the user plane functional entity.
  • Step S3 Associate and merge the user control plane information and the user data plane information to generate a user traffic log.
  • the user traffic log is the user IP record.
  • FIG. 2 is a flowchart of another data management method provided by an embodiment of the disclosure. As shown in Figure 2, the method is an implementation based on the method shown in Figure 1. Specifically, the method not only includes step S1 and step S2, but also includes step S301 and step S4, and step S301 is a specific implementation of step S3. Only step S301 and step S4 will be described in detail below.
  • Step S3 the step of associating and merging user control plane information and user data plane information to generate a user traffic log includes:
  • Step S301 Backfill the user control plane information into the user data plane information to obtain a user traffic log.
  • the user control plane information is backfilled into the user data plane information, that is, the protocol data unit session information, user identity information, location information, billing information, and policy information are backfilled into the user data plane information to obtain the user Traffic log.
  • step S301 it further includes:
  • Step S4 Create a first index according to the session management function entity identifier, and store user traffic logs according to the first index.
  • the session management function entity identifier is embodied in the form of "SMF-SEID" and "SMF-IP", and each information transmitted by the session management function entity and the user plane function entity will carry the session management function entity identifier.
  • the embodiments of the present disclosure provide a data management method, which can obtain the control plane related information collected by the session management function entity without using the information of the N4 interface between the session management function entity and the user plane function entity.
  • User-plane related information collected by the user-plane functional entity realizes the correlation between the control plane and user-plane information; the generated user traffic log can be used for corresponding IP traceability and data analysis; the use of multiple related subsystems that share control plane information effectively reduces business Complexity and information redundancy.
  • FIG. 3 is a flowchart of yet another data management method provided by an embodiment of the disclosure. As shown in Fig. 3, the method is a specific alternative implementation based on the method shown in Fig. 1. Specifically, the method not only includes steps S1 to S3, but also includes steps S5 and S6. Only step S5 and step S6 will be described in detail below.
  • Step S5 Obtain a network address translation log collected by a network address translation (Network Address Translation, NAT) device corresponding to the user plane functional entity.
  • a network address translation Network Address Translation, NAT
  • the network address translation log includes: private network source IP, private network source port number (Port), public network source IP, public network source port number, and related protocols.
  • step S1 to step S3 can be executed before step S5, or step S1 to step S3 are executed after S5, or Steps S1 to S3 are executed synchronously with S5, which all belong to the protection scope of the present disclosure.
  • step S3 and step S5 it further includes:
  • Step S6 Associate and merge the user traffic log and the network address translation log to generate a detailed IP log.
  • the IP detailed log is finally stored in the database, which can be used for more comprehensive user information traceability, private network source and destination IP traceability, public network source IP traceability, and location information traceability.
  • Fig. 4 is a flowchart of yet another data management method provided by an embodiment of the present disclosure. As shown in FIG. 4, the method is a specific optional implementation based on the method shown in FIG. 3. Specifically, the method not only includes steps S1 to S5, but also includes steps S601 and S7, and step S601 is a specific implementation of step S6. Only step S601 and step S7 will be described in detail below.
  • Step S6 the steps of associating and merging the user traffic log and the network address translation log to generate a detailed IP log include:
  • Step S601 Backfill the network address translation log into the user traffic log to obtain a detailed IP log.
  • backfilling the network address translation log into the user traffic log means backfilling the public network source IP, public network source port number, and related protocols into the user traffic log to obtain a detailed IP log.
  • step S601 it further includes:
  • Step S7 Create a second index according to the private network source IP, the private network source port number and the preset protocol, and store the detailed IP log according to the second index.
  • the preset protocols include: Transmission Control Protocol (TCP), User Datagram Protocol (UDP), Internet Protocol (IP) and network control Message Protocol (Internet Control Message Protocol, ICMP for short), etc.
  • Fig. 5 is a flowchart of yet another data management method provided by an embodiment of the present disclosure. As shown in FIG. 5, the method is a specific optional implementation based on the method shown in FIG. 4. Specifically, the method not only includes steps S1 to S7, but also includes steps S8 and S9. Only step S8 and step S9 will be described in detail below.
  • step S7 it also includes:
  • Step S8 Perform aggregation analysis on the stored IP detailed logs to obtain a first aggregation analysis result.
  • the first aggregate analysis result is only for the locally stored IP detailed log, although it includes the full latitude, it is local.
  • Step S9 Perform aggregation analysis again according to the first aggregation analysis result obtained by itself and the first aggregation analysis result sent by other correlation subsystems to obtain the second aggregation analysis result.
  • the second aggregation analysis result is a global analysis result obtained on the basis of the first aggregation analysis result.
  • Fig. 6 is a flowchart of yet another data management method provided by an embodiment of the present disclosure. As shown in FIG. 6, this method is a specific optional implementation based on the method shown in FIG. 4. Specifically, the method not only includes steps S1 to S7, but also includes steps S10 to S12. Only steps S10 to S12 will be described in detail below.
  • step S7 it also includes:
  • Step S10 In response to the query request, query the detailed IP log stored by itself and other associated subsystems.
  • Step S11 Summarize its own query results and query results of other related subsystems to obtain a query response.
  • Step S12 Feed back the query response to the server.
  • the embodiments of the present disclosure provide a data management method, which can implement corresponding big data analysis based on IP detailed logs and respond to corresponding query requests.
  • the embodiment of the present disclosure also provides a data management system, which includes: a session management function entity, a plurality of user plane function entities, a plurality of network address translators corresponding to the plurality of user plane function entities, and Multiple associated subsystems with one-to-one correspondence between multiple user plane functional entities.
  • the correlation subsystem adopts the correlation subsystem in the above-mentioned embodiment.
  • FIG. 7 is a schematic structural diagram of a data management system provided by an embodiment of the disclosure.
  • the central computer room deploys a session management function entity and other controls
  • user-plane network elements such as user-plane functional entities and network address converters are respectively deployed.
  • associated subsystems are respectively deployed in the three auxiliary computer rooms.
  • the user-plane functional entities and network address converters are deployed.
  • One-to-one corresponding deployment, user plane functional entities and associated subsystems are deployed one-to-one.
  • the session management functional entity sends the user control plane information to the associated subsystem of the first computer room (especially, the data collection module of the associated subsystem), and then the associated subsystem shares the information with the associated subsystems of the second and third computer rooms.
  • User control plane information during this period, the correlation subsystem (data acquisition module) obtains the user data plane information and network address translation log reported by the corresponding user plane functional entity and the network address converter; the correlation subsystem connects the user control plane After the information and user data plane information are associated and merged, a user traffic log is generated. After the user traffic log and the network address translation log are associated and merged, a detailed IP log is generated.
  • the correlation subsystem stores the detailed IP log (especially, the original data storage module of the correlation subsystem), and no longer forwards it, and stores it locally to avoid bandwidth consumption; after storage, the correlation subsystem (
  • the primary aggregation analysis module of the correlation subsystem can perform an aggregation big data analysis to generate the first aggregation analysis result.
  • the analysis is only for the local IP detailed log; after that, the correlation subsystem (In particular, the secondary aggregation analysis module of the correlation subsystem receives the first aggregation analysis results reported by other computer rooms, performs secondary aggregation big data analysis, and generates the second aggregation analysis result, because the first aggregation analysis result is aggregated data , The amount of data is small, and the bandwidth consumption is small.
  • the first aggregate analysis result and the second aggregate analysis result can be applied to operation and maintenance work such as network element bandwidth statistics, packet loss statistics, connection number statistics, user number statistics, and access type statistics.
  • the correlation subsystem of the second computer room can respond to the corresponding query request.
  • the specific process is: the query request is distributed to all the correlation subsystems (original data storage modules) to query itself and others Associate the detailed IP log stored by the subsystem, summarize the query results, obtain the query response, and provide feedback to the Web server.
  • the data transmission of the query process is only carried out between the auxiliary computer rooms, and does not affect the bandwidth between the auxiliary computer rooms of the central computer room, and avoids affecting the transmission of control plane signaling.
  • the query response received by the Web server is the final data set, which realizes the data Minimize the amount.
  • FIG. 8 is a schematic structural diagram of a system architecture applicable to the data management method provided by an embodiment of the present disclosure. As shown in Figure 8, the system architecture is deployed based on the existing 5G architecture. In addition, traceability query requests can also be responded to through the corresponding summary query system.
  • the embodiment of the present disclosure also provides an associated subsystem, including: one or more processors; a storage device for storing one or more programs; when the one or more programs are executed by the one or more processors , So that the one or more processors implement any data management method as in the foregoing embodiments.
  • the embodiments of the present disclosure also provide a computer-readable medium on which a computer program is stored, where the program is executed by a processor to implement the steps in any data management method in the above-mentioned embodiments.
  • the embodiments of the present disclosure provide a data management method, an associated subsystem, a computer-readable medium, and a data management system, which can realize that the corresponding information of the control plane and the user plane is obtained separately, and the traffic log is generated based on the information, thereby avoiding complicated deployment. It meets the needs of IP traceability and big data analysis while meeting the problems of security and network performance.
  • the functional modules/units in the device can be implemented as software, firmware, hardware, and appropriate combinations thereof.
  • the division between functional modules/units mentioned in the above description does not necessarily correspond to the division of physical components; for example, a physical component may have multiple functions, or a function or step may consist of several physical components.
  • the components are executed cooperatively.
  • Some physical components or all physical components can be implemented as software executed by a processor, such as a central processing unit, a digital signal processor, or a microprocessor, or as hardware, or as an integrated circuit, such as an application specific integrated circuit .
  • Such software may be distributed on a computer-readable medium, and the computer-readable medium may include a computer storage medium (or a non-transitory medium) and a communication medium (or a transitory medium).
  • the term computer storage medium includes volatile and non-volatile data implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data). Sexual, removable and non-removable media.
  • Computer storage media include but are not limited to RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, digital versatile disk (DVD) or other optical disk storage, magnetic cassettes, magnetic tapes, magnetic disk storage or other magnetic storage devices, or Any other medium used to store desired information and that can be accessed by a computer.
  • communication media usually contain computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as carrier waves or other transmission mechanisms, and may include any information delivery media. .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Mining & Analysis (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

一种数据管理方法及***、关联子***和计算机可读介质，数据管理方法包括：获取会话管理功能实体采集的用户控制面信息(S1)；获取用户面功能实体采集的用户数据面信息(S2)；将用户控制面信息和用户数据面信息进行关联合并，生成用户流量日志(S3)。

Description

数据管理方法及***、关联子***和计算机可读介质
相关申请的交叉引用
本申请基于申请号为201911398795.5、申请日为2019年12月30日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此引入本申请作为参考。
技术领域
本公开涉及通信技术领域，特别涉及一种数据管理方法、关联子***、计算机可读介质和数据管理***。
背景技术
IP溯源对于国家安全具有重大的意义，尤其是在反恐，追查犯罪记录等方面十分重要。目前针对2G、3G和4G网络已有成熟的IP溯源方案，随着5G的大规模商用，万物互联时代的到来，流量消耗更多，网络拓扑更复杂，IP溯源更加重要。同时，5G的数据量及终端数井喷，相应的大数据分析需求也需要得到满足。
然而，5G网络的部署与之前的网络部署相比有着较大的差异。在5G网络部署中，基于相应的网元，控制面和用户面彻底分离；同时，5G网络多采用虚拟化部署，通过硬件层面进行信息采集，组网复杂，难度高，可行性较低，并且针对复合部署的网元，无法采集到对应接口的信令。
发明内容
本公开旨在至少一定程度上解决上述技术问题之一，提出了一种数据管理方法、关联子***、计算机可读介质和数据管理***。
为实现上述目的，第一方面，本公开实施例提供了一种数据管理方法，包括：获取会话管理功能实体采集的用户控制面信息；获取用户面功能实体采集的用户数据面信息；将所述用户控制面信息和所述用户数据面信息进行关联合并，生成用户流量日志。
第二方面，本公开实施例提供了一种关联子***，包括：一个或多个处理器；存储装置，用于存储一个或多个程序；当所述一个或多个程序被所述一个或多个处理器执行，使得所述一个或多个处理器实现如上述实施例中所述的数据管理方法。
第三方面，本公开实施例提供了一种计算机可读介质，其上存储有计算机程序， 所述程序被处理器执行时实现如上述实施例中所述的数据管理方法中的步骤。
第四方面，本公开实施例提供了一种数据管理***，包括：会话管理功能实体、多个用户面功能实体、与多个所述用户面功能实体一一对应的多个网络地址转换器和与多个所述用户面功能实体一一对应的多个关联子***；其中，所述关联子***采用如上述实施例中所述的关联子***。
附图说明
图1为本公开实施例提供的一种数据管理方法的流程图；
图2为本公开实施例提供的另一种数据管理方法的流程图；
图3为本公开实施例提供的又一种数据管理方法的流程图；
图4为本公开实施例提供的再一种数据管理方法的流程图；
图5为本公开实施例提供的再一种数据管理方法的流程图；
图6为本公开实施例提供的再一种数据管理方法的流程图；
图7为本公开实施例提供的一种数据管理***的结构示意图；
图8为一种适用本公开实施例所提供的数据管理方法的***架构的结构示意图。
具体实施方式
为使本领域的技术人员更好地理解本公开的技术方案，下面结合附图对本公开提供的数据管理方法、关联子***、计算机可读介质和数据管理***进行详细描述。
本公开所提供的数据管理方法可用于根据控制面和用户面相应信息生成IP记录，可满足相应IP溯源和数据分析需求。
图1为本公开实施例提供的一种数据管理方法的流程图。如图1所示，该方法包括：
步骤S1、获取会话管理功能实体(Session Management Function，简称SMF)采集的用户控制面信息。
在一些实施例中，用户控制面信息包括：会话管理功能实体标识等协议数据单元会话信息，国际移动用户识别码(International Mobile Subscriber Identity，简称IMSI)、移动用户号码(Mobile Subscriber International ISDN/PSTN number，简称MSISDN)和国际移动设备识别码(International Mobile Equipment Identity，简称IMEI)等用户身份信息，位置信息，计费信息，以及策略信息等。
在一些实施例中，步骤S1，获取会话管理功能实体采集的用户控制面信息的步骤，具体包括：
通过会话管理功能实体所配置的软采接口从会话管理功能实体处直接获取用户 控制面信息；或者，从其他关联子***处获取该关联子***预先从会话管理功能实体处获得的用户控制面信息。
其中，在一些实施例中，会话管理功能实体会向距离最近的关联子***发送用户控制面信息，此后，多个关联子***共享该用户控制面信息，减少网络信息量和异地传输。
同时，采用软采接口可避免虚拟化引入的组网复杂性，该软采接口直接使用网元内部数据，网元本身包含的信息更全面，定制的软采接口编解码简单，无须网络附加存储装置(Network Attached Storage，简称NAS)解密，无须复杂的协议栈关联，按照简单的对应关联方式即可完成有效的控制面与用户面关联。
在一些实施例中，步骤S1，获取会话管理功能实体采集的用户控制面信息的步骤，具体包括：
基于协议数据单元(Protocol Data Unit，简称PDU)会话流程，获取会话管理功能实体采集的用户控制面信息。
其中，协议数据单元会话流程包括：协议数据单元会话创建流程、协议数据单元会话修改流程和协议数据单元会话释放流程。基于协议数据单元会话流程从会话管理功能实体处获取用户控制面信息，即在协议数据单元会话创建流程、协议数据单元会话修改流程和协议数据单元会话释放流程，都获取用户控制面信息。
在一些实施例中，当用户控制面信息携带创建流程标识时，即代表正在进行协议数据单元会话创建流程，此时创建数据区，并将相应信息存储至该数据区；当用户控制面信息携带修改流程标识时，即代表正在进行协议数据单元会话修改流程，此时更新该数据区；当用户控制面信息携带释放流程标识时，即代表正在进行协议数据单元会话释放流程，此时释放该数据区。
步骤S2、获取用户面功能实体(User Plane Function，简称UPF)采集的用户数据面信息。
在一些实施例中，用户数据面信息包括：流量信息和深度报文检测(Deep Packet Inspection，简称DPI)信息。其中，深度报文检测信息包括：会话管理功能实体标识等协议数据单元会话信息、五元组信息、时间信息、应用层协议、统一资源定位符(Uniform Resource Locator,简称URL)、应用程序类型等。
在一些实施例中，步骤S2，获取用户面功能实体采集的用户数据面信息的步骤，具体包括：
通过用户面功能实体所配置的软采接口接收用户面功能实体上报的用户数据面 信息。
步骤S3、将用户控制面信息和用户数据面信息进行关联合并，生成用户流量日志。
在一些实施例中，用户流量日志即为用户IP记录。
图2为本公开实施例提供的另一种数据管理方法的流程图。如图2所示，该方法为基于图1所示方法的一种实施方案。具体地，该方法不仅包括步骤S1和步骤S2，还包括步骤S301和步骤S4，步骤S301为步骤S3的一种具体实施方式。下面仅对步骤S301和步骤S4进行详细描述。
步骤S3，将用户控制面信息和用户数据面信息进行关联合并，生成用户流量日志的步骤，具体包括：
步骤S301、将用户控制面信息回填至用户数据面信息中，以得到用户流量日志。
其中，将用户控制面信息回填至用户数据面信息中，即是将协议数据单元会话信息、用户身份信息、位置信息、计费信息、以及策略信息等回填至用户数据面信息中，以得到用户流量日志。
在步骤S301之后，还包括：
步骤S4、根据会话管理功能实体标识创建第一索引，根据第一索引存储用户流量日志。
其中，会话管理功能实体标识以“SMF-SEID”和“SMF-IP”等形式进行体现，会话管理功能实体和用户面功能实体传递的各个信息中均会携带该会话管理功能实体标识。
本公开实施例提供了一种数据管理方法，可实现在不使用会话管理功能实体和用户面功能实体之间的N4接口的信息的基础上，获取会话管理功能实体采集的控制面相关信息，获取用户面功能实体采集的用户面相关信息，实现控制面和用户面信息关联；生成用户流量日志可用于相应IP溯源和数据分析；采用多个共享控制面信息的关联子***的方式，有效降低业务复杂度和信息冗余。
图3为本公开实施例提供的又一种数据管理方法的流程图。如图3所示，该方法为基于图1所示方法的一种具体化可选实施方案。具体地，该方法不仅包括步骤S1～步骤S3，还包括步骤S5和步骤S6。下面仅对步骤S5和步骤S6进行详细描述。
步骤S5、获取用户面功能实体对应的网络地址转换(Network Address Translation，简称NAT)器采集的网络地址转换日志。
在一些实施例中，网络地址转换日志包括：私网源IP、私网源端口号(Port)、 公网源IP、公网源端口号和相关协议。
需要说明的是，本公开的技术方案对步骤S1～步骤S3和步骤S5的执行顺序不作限定，即步骤S1～步骤S3可在步骤S5之前执行，或步骤S1～步骤S3在S5后执行，或者步骤S1～步骤S3与S5同步执行，其均属于本公开的保护范围。
在步骤S3和步骤S5之后，还包括：
步骤S6、将用户流量日志与网络地址转换日志进行关联合并，生成IP详细日志。
其中，IP详细日志最终存入数据库中，可用于更全面的用户信息溯源，私网源IP和目的IP溯源，公网源IP溯源，以及位置信息溯源等。
图4为本公开实施例提供的再一种数据管理方法的流程图。如图4所示，该方法为基于图3所示方法的一种具体化可选实施方案。具体地，该方法不仅包括步骤S1～步骤S5，还包括步骤S601和步骤S7，步骤S601为步骤S6的一种具体实施方式。下面仅对步骤S601和步骤S7进行详细描述。
步骤S6，将用户流量日志与网络地址转换日志进行关联合并，生成IP详细日志的步骤，具体包括：
步骤S601、将网络地址转换日志回填至用户流量日志中，以得到IP详细日志。
其中，将网络地址转换日志回填至用户流量日志中，即是将公网源IP、公网源端口号和相关协议回填至用户流量日志中，以得到IP详细日志。
在步骤S601之后，还包括：
步骤S7、根据私网源IP、私网源端口号和预设协议创建第二索引，根据第二索引存储IP详细日志。
其中，一般而言，预设协议包括：传输控制协议(Transmission Control Protocol，简称TCP)、用户数据报协议(User Datagram Protocol，简称UDP)和网际互连协议(Internet Protocol，简称IP)和网络控制报文协议(Internet Control Message Protocol，简称ICMP)等。
图5为本公开实施例提供的再一种数据管理方法的流程图。如图5所示，该方法为基于图4所示方法的一种具体化可选实施方案。具体地，该方法不仅包括步骤S1～步骤S7，还包括步骤S8和步骤S9。下面仅对步骤S8和步骤S9进行详细描述。
在步骤S7之后，还包括：
步骤S8、对所存储的IP详细日志进行聚集分析，得到第一聚集分析结果。
其中，第一聚集分析结果只针对本地存储的IP详细日志，虽包括全量纬度，但具有局域性。
步骤S9、根据自身所得到的第一聚集分析结果和其他关联子***所发送的第一聚集分析结果，再次进行聚集分析，得到第二聚集分析结果。
其中，第二聚集分析结果为在第一聚集分析结果的基础上得到的全局性分析结果。
图6为本公开实施例提供的再一种数据管理方法的流程图。如图6所示，该方法为基于图4所示方法的一种具体化可选实施方案。具体地，该方法不仅包括步骤S1～步骤S7，还包括步骤S10～步骤S12。下面仅对步骤S10～步骤S12进行详细描述。
在步骤S7之后，还包括：
步骤S10、响应于查询请求，查询自身以及其他关联子***所存储的IP详细日志。
步骤S11、将自身的查询结果和其他关联子***的查询结果进行汇总，得到查询响应。
步骤S12、向服务器反馈查询响应。
本公开实施例提供了一种数据管理方法，可实现根据IP详细日志进行相应大数据分析，并对相应查询请求进行响应。
需要说明的是，上述各实施例中不同步骤之间可相互组合以得到的新实施例，该新实施例所对应的技术方案也应属于本公开的保护范围。
本公开实施例还提供了一种数据管理***，该数据管理***包括：会话管理功能实体、多个用户面功能实体、与多个用户面功能实体一一对应的多个网络地址转换器和与多个用户面功能实体一一对应的多个关联子***。其中，关联子***采用如上述实施例中的关联子***。
下面对本公开中的数据管理方法的步骤流程和数据管理***结合实际应用进行详细描述。
图7为本公开实施例提供的一种数据管理***的结构示意图，如图7所示，以一个中心机房和三个附属机房的现有条件为例，在中心机房部署会话管理功能实体等控制面网元，在三个附属机房分别部署用户面功能实体和网络地址转换器等用户面网元，同时，在三个附属机房分别部署关联子***，其中，用户面功能实体与网络地址转换器一一对应部署，用户面功能实体与关联子***一一对应部署。
会话管理功能实体将用户控制面信息发送至第一机房的关联子***(特别地，关联子***的数据采集模块)，之后该关联子***向第二机房和第三机房的关联子系 统共享该用户控制面信息；在此期间，该关联子***(数据采集模块)获取对应的用户面功能实体和网络地址转换器上报的用户数据面信息和网络地址转换日志；该关联子***将用户控制面信息和用户数据面信息进行关联合并后，生成用户流量日志，将用户流量日志和网络地址转换日志进行关联合并后，生成IP详细日志。
此后，该关联子***将IP详细日志进行存储(特别地，存储在关联子***的原始数据存储模块)，并不再转发，在本地存储以避免带宽消耗；进行存储后，该关联子***(特别地，关联子***的一次聚集分析模块)可进行一次聚集大数据分析，生成第一聚集分析结果，同样为了避免带宽消耗，该分析只针对本地的IP详细日志；之后，该关联子***(特别地，关联子***的二次聚集分析模块)接收其他机房上报的第一聚集分析结果，进行二次聚集大数据分析，生成第二聚集分析结果，由于第一聚集分析结果是经过聚集的数据，数据量较小，带宽消耗较小。
其中，第一聚集分析结果和第二聚集分析结果可应用于网元带宽统计、丢包统计、连接数统计、用户数统计和接入类型统计等运维工作。
第二机房的关联子***(特别地，关联子***的溯源查询模块)可响应相应查询请求，具体过程为：将查询请求分发给所有关联子***(原始数据存储模块)，以查询自身以及其他关联子***所存储的IP详细日志，将查询结果进行汇总，得到查询响应，并向Web服务器进行反馈。该查询过程数据传输只在附属机房之间进行，不影响中心机房附属机房之间的带宽，避免影响控制面信令的传输，同时，Web服务器接收到的查询响应为最终的数据集，实现数据量最小化。
需要说明的是，将部署二次聚集分析模块和溯源查询模块部署在不同机房，即是将步骤S8和步骤S9对应流程，以及步骤S10～步骤S12对应流程交予两个不同的关联子***进行实现的情况，仅为本公开实施例中的一种可选实施方案。
图8为一种适用本公开实施例所提供的数据管理方法的***架构的结构示意图。如图8所示，该***架构基于现有5G架构进行相应部署，另外，溯源查询请求同样可通过相应汇总查询***进行响应。
本公开实施例还提供了一种关联子***，包括：一个或多个处理器；存储装置，用于存储一个或多个程序；当该一个或多个程序被该一个或多个处理器执行，使得该一个或多个处理器实现如上述实施例中的任一数据管理方法。
本公开实施例还提供了一种计算机可读介质，其上存储有计算机程序，其中，该程序被处理器执行时实现如上述实施例中的任一数据管理方法中的步骤。
本公开实施例具有以下有益效果：
本公开实施例提供了一种数据管理方法、关联子***、计算机可读介质和数据管理***，可实现通过分别获取控制面和用户面的相应信息，根据这些信息生成流量日志，在规避部署复杂性和网络性能问题的同时，满足IP溯源和大数据分析的需求。
本领域普通技术人员可以理解，上文中所公开方法中的全部或某些步骤、装置中的功能模块/单元可以被实施为软件、固件、硬件及其适当的组合。在硬件实施方式中，在以上描述中提及的功能模块/单元之间的划分不一定对应于物理组件的划分；例如，一个物理组件可以具有多个功能，或者一个功能或步骤可以由若干物理组件合作执行。某些物理组件或所有物理组件可以被实施为由处理器，如中央处理器、数字信号处理器或微处理器执行的软件，或者被实施为硬件，或者被实施为集成电路，如专用集成电路。这样的软件可以分布在计算机可读介质上，计算机可读介质可以包括计算机存储介质(或非暂时性介质)和通信介质(或暂时性介质)。如本领域普通技术人员公知的，术语计算机存储介质包括在用于存储信息(诸如计算机可读指令、数据结构、程序模块或其他数据)的任何方法或技术中实施的易失性和非易失性、可移除和不可移除介质。计算机存储介质包括但不限于RAM、ROM、EEPROM、闪存或其他存储器技术、CD-ROM、数字多功能盘(DVD)或其他光盘存储、磁盒、磁带、磁盘存储或其他磁存储装置、或者可以用于存储期望的信息并且可以被计算机访问的任何其他的介质。此外，本领域普通技术人员公知的是，通信介质通常包含计算机可读指令、数据结构、程序模块或者诸如载波或其他传输机制之类的调制数据信号中的其他数据，并且可包括任何信息递送介质。
本文已经公开了示例实施例，并且虽然采用了具体术语，但它们仅用于并仅应当被解释为一般说明性含义，并且不用于限制的目的。在一些实例中，对本领域技术人员显而易见的是，除非另外明确指出，否则可单独使用与特定实施例相结合描述的特征、特性和/或元素，或可与其他实施例相结合描述的特征、特性和/或元件组合使用。因此，本领域技术人员将理解，在不脱离由所附的权利要求阐明的本公开的范围的情况下，可进行各种形式和细节上的改变。

Claims (13)

  1. 一种数据管理方法，包括：
    获取会话管理功能实体采集的用户控制面信息；
    获取用户面功能实体采集的用户数据面信息；
    将所述用户控制面信息和所述用户数据面信息进行关联合并，生成用户流量日志。
  2. 根据权利要求1所述的数据管理方法，其中，所述将所述用户控制面信息和所述用户数据面信息进行关联合并，生成用户流量日志的步骤，包括：
    将所述用户控制面信息回填至所述用户数据面信息中，以得到所述用户流量日志；
    在所述将所述用户控制面信息和所述用户数据面信息进行关联合并，生成用户流量日志的步骤之后，还包括：
    根据会话管理功能实体标识创建第一索引，根据所述第一索引存储所述用户流量日志。
  3. 根据权利要求1所述的数据管理方法，其中，所述获取会话管理功能实体采集的用户控制面信息的步骤，包括：
    通过所述会话管理功能实体所配置的软采接口从所述会话管理功能实体处直接获取所述用户控制面信息；
    或者，从其他关联子***处获取该关联子***预先从所述会话管理功能实体处获得的所述用户控制面信息。
  4. 根据权利要求1所述的数据管理方法，其中，所述获取会话管理功能实体采集的用户控制面信息的步骤，包括：
    基于协议数据单元会话流程，获取所述用户控制面信息。
  5. 根据权利要求1所述的数据管理方法，其中，所述获取用户面功能实体采集的用户数据面信息的步骤，包括：
    通过所述用户面功能实体所配置的软采接口接收所述用户面功能实体上报的所述用户数据面信息。
  6. 根据权利要求1-5任一所述的数据管理方法，还包括：
    获取所述用户面功能实体对应的网络地址转换器采集的网络地址转换日志；
    在所述将所述用户控制面信息和所述用户数据面信息进行关联合并，生成用户 流量日志的步骤之后，还包括：
    将所述用户流量日志与所述网络地址转换日志进行关联合并，生成IP详细日志。
  7. 根据权利要求6所述的数据管理方法，其中，所述将所述用户流量日志与所述网络地址转换日志进行关联合并，生成IP详细日志的步骤，包括：
    将所述网络地址转换日志回填至所述用户流量日志中，以得到所述IP详细日志；
    在所述将所述用户流量日志与所述网络地址转换日志进行关联合并，生成IP详细日志的步骤之后，还包括：
    根据私网源IP、私网源端口号和预设协议创建第二索引，根据所述第二索引存储所述IP详细日志。
  8. 根据权利要求7所述的数据管理方法，其中，在所述根据所述第二索引存储所述IP详细日志的步骤之后，还包括：
    对所存储的所述IP详细日志进行聚集分析，得到第一聚集分析结果。
  9. 根据权利要求8所述的数据管理方法，其中，在所述对所存储的所述IP详细日志进行聚集分析的步骤之后，还包括：
    根据自身所得到的所述第一聚集分析结果和其他关联子***所发送的第一聚集分析结果，再次进行聚集分析，得到第二聚集分析结果。
  10. 根据权利要求7所述的数据管理方法，其中，在所述根据所述第二索存储所述IP详细日志的步骤之后，还包括：
    响应于查询请求，查询自身以及其他关联子***所存储的所述IP详细日志；
    将自身的查询结果和其他关联子***的查询结果进行汇总，得到查询响应；
    向服务器反馈所述查询响应。
  11. 一种关联子***，包括：
    一个或多个处理器；
    存储装置，用于存储一个或多个程序；
    当所述一个或多个程序被所述一个或多个处理器执行，使得所述一个或多个处理器实现如权利要求1-10中任一所述的数据管理方法。
  12. 一种计算机可读介质，其上存储有计算机程序，其中，所述程序被处理器执行时实现如权利要求1-10中任一所述的数据管理方法中的步骤。
  13. 一种数据管理***，包括：会话管理功能实体、多个用户面功能实体、与多个所述用户面功能实体一一对应的多个网络地址转换器和与多个所述用户面功能实体一一对应的多个关联子***；
    其中，所述关联子***采用如权利要求11中所述的关联子***。
PCT/CN2020/136933 2019-12-30 2020-12-16 数据管理方法及***、关联子***和计算机可读介质 WO2021135950A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP20911202.8A EP4084415A4 (en) 2019-12-30 2020-12-16 DATA MANAGEMENT METHOD AND SYSTEM, ASSOCIATED SUBSYSTEM AND COMPUTER READABLE MEDIA

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201911398795.5 2019-12-30
CN201911398795.5A CN113132170B (zh) 2019-12-30 2019-12-30 数据管理方法及***、关联子***和计算机可读介质

Publications (1)

Publication Number Publication Date
WO2021135950A1 true WO2021135950A1 (zh) 2021-07-08

Family

ID=76687333

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/136933 WO2021135950A1 (zh) 2019-12-30 2020-12-16 数据管理方法及***、关联子***和计算机可读介质

Country Status (3)

Country Link
EP (1) EP4084415A4 (zh)
CN (1) CN113132170B (zh)
WO (1) WO2021135950A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114258052A (zh) * 2022-01-04 2022-03-29 武汉光迅信息技术有限公司 数据关联***、数据关联方法及装置、设备及介质
CN114339719A (zh) * 2021-12-31 2022-04-12 中国联合网络通信集团有限公司 一种dpi数据采集方法及相关装置
CN115996364A (zh) * 2023-03-22 2023-04-21 北京首信科技股份有限公司 一种终端实时溯源定位的方法与设备

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114389792B (zh) * 2022-03-22 2022-06-10 合肥全息网御科技有限公司 一种web日志nat前后关联方法及***

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2219323A1 (en) * 2009-02-16 2010-08-18 NetHawk Oyj Real-time network data analysing system
US20120142335A1 (en) * 2010-12-02 2012-06-07 Chiou Ta-Gang Apparatus and Method for Network Based Wireless Network Test
WO2018231197A1 (en) * 2017-06-13 2018-12-20 Nokia Technologies Oy Conveying non-access stratum messages over ethernet
WO2019201435A1 (en) * 2018-04-18 2019-10-24 Telefonaktiebolaget Lm Ericsson (Publ) Technique for acquiring and correlating session-related information from an internet protocol multimedia subsystem

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150124622A1 (en) * 2013-11-01 2015-05-07 Movik Networks, Inc. Multi-Interface, Multi-Layer State-full Load Balancer For RAN-Analytics Deployments In Multi-Chassis, Cloud And Virtual Server Environments
CN106067880B (zh) * 2016-06-13 2019-05-31 国家计算机网络与信息安全管理中心 一种基于4g网络的ip地址的溯源方法
CN109548092B (zh) * 2017-07-28 2021-04-09 华为技术有限公司 一种激活session的方法、设备及***
CN110048951B (zh) * 2018-01-16 2020-11-27 ***通信有限公司研究院 一种pcf寻址方法及装置、设备、存储介质
WO2019231435A1 (en) * 2018-05-29 2019-12-05 Telefonaktiebolaget Lm Ericsson (Publ) SYSTEMS AND METHODS FOR INVESTIGATING AND ADDRESSING BATTERY LIFE DEGRADATION OF DEVICES, SUCH AS IoT DEVICES, IN A CELLULAR COMMUNICATIONS NETWORK
CN110536481A (zh) * 2019-07-03 2019-12-03 中兴通讯股份有限公司 数据传输链路建立方法、装置以及计算机可读存储介质

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2219323A1 (en) * 2009-02-16 2010-08-18 NetHawk Oyj Real-time network data analysing system
US20120142335A1 (en) * 2010-12-02 2012-06-07 Chiou Ta-Gang Apparatus and Method for Network Based Wireless Network Test
WO2018231197A1 (en) * 2017-06-13 2018-12-20 Nokia Technologies Oy Conveying non-access stratum messages over ethernet
WO2019201435A1 (en) * 2018-04-18 2019-10-24 Telefonaktiebolaget Lm Ericsson (Publ) Technique for acquiring and correlating session-related information from an internet protocol multimedia subsystem

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP4084415A4 *

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114339719A (zh) * 2021-12-31 2022-04-12 中国联合网络通信集团有限公司 一种dpi数据采集方法及相关装置
CN114339719B (zh) * 2021-12-31 2023-05-09 中国联合网络通信集团有限公司 一种dpi数据采集方法及相关装置
CN114258052A (zh) * 2022-01-04 2022-03-29 武汉光迅信息技术有限公司 数据关联***、数据关联方法及装置、设备及介质
CN114258052B (zh) * 2022-01-04 2024-03-15 武汉光迅信息技术有限公司 数据关联***、数据关联方法及装置、设备及介质
CN115996364A (zh) * 2023-03-22 2023-04-21 北京首信科技股份有限公司 一种终端实时溯源定位的方法与设备

Also Published As

Publication number Publication date
CN113132170B (zh) 2024-05-28
EP4084415A1 (en) 2022-11-02
CN113132170A (zh) 2021-07-16
EP4084415A4 (en) 2023-01-25

Similar Documents

Publication Publication Date Title
WO2021135950A1 (zh) 数据管理方法及***、关联子***和计算机可读介质
CN112887433B (zh) 基于quic协议的云端访问边缘服务的方法和***
WO2021207922A1 (zh) 报文传输方法、装置及***
WO2020135575A1 (zh) 一种获取网络拓扑的***、方法和服务器
US10334419B2 (en) Methods, systems, and computer readable media for optimizing machine type communication (MTC) device signaling
WO2014005442A1 (zh) 网络业务访问的方法及***
US10379890B1 (en) Synchronized cache of an operational state of distributed software system
WO2016050109A1 (zh) 一种通信方法、云管理服务器及虚拟交换机
US11723105B2 (en) 5G N3 data plane enrichment using N11 interface in a monitoring system
WO2023056722A1 (zh) 一种分布式防火墙定义方法及***
WO2011140910A1 (zh) 业务处理单元和方法以及业务控制网关和负载均衡方法
US20140337471A1 (en) Migration assist system and migration assist method
WO2017219813A1 (zh) 一种流量处理方法及透明缓存***
CN104065514A (zh) 一种基于netconf中继的家庭网络管理方法
WO2016070633A1 (zh) 上网日志生成方法和装置
WO2019001562A1 (zh) 模型加载方法、装置、存储介质和计算机设备
WO2017190414A1 (zh) 一种wia-pa工业无线网络中移动设备入网认证机制
US10268532B2 (en) Application message processing system, method, and application device
WO2015188331A1 (zh) 转发控制方法、驱动器及sdn网络
WO2018036521A1 (zh) 资源调整方法、装置及***
CN112422395A (zh) 一种数据传输方法、装置、终端设备和存储介质
US20150312146A1 (en) Method and device for hosting application by access node
CN109743585B (zh) 一种监控视频收藏以及收藏夹克隆的方法和装置
WO2012167657A1 (zh) 一种实现事件转发的方法及通用信息模型cim服务器
CN103118115B (zh) 面向云计算用户的虚拟机管理方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20911202

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2020911202

Country of ref document: EP

Effective date: 20220725

NENP Non-entry into the national phase

Ref country code: DE