CN116261110B

CN116261110B - SDR data determining method, device and storage medium

Info

Publication number: CN116261110B
Application number: CN202211557613.6A
Authority: CN
Inventors: 宋亮亮; 黄晶; 邵四清; 邹兴林; 李世英; 王阳; 吕果香; 陈泽浩; 陈翼鹏; 关天宇
Original assignee: China United Network Communications Group Co Ltd
Current assignee: China United Network Communications Group Co Ltd
Priority date: 2022-12-06
Filing date: 2022-12-06
Publication date: 2024-04-12
Anticipated expiration: 2042-12-06
Also published as: CN116261110A

Abstract

The present invention relates to the field of communications technologies, and in particular, to a method and an apparatus for determining SDR data, and a storage medium, which can determine end-to-end SDR data in a call process. The method comprises the following steps: acquiring target call ticket data; the target call ticket data includes: signaling in the call relay process and user identification in the call relay process; determining a target SDR session detailed record data table associated with user identification in the call relay process; the target SDR session detailed record data table is used for storing call parameters in a target call flow, wherein the target call flow is a target call flow to which target call ticket data belong, and the call parameters comprise at least one of signaling messages and call fields; and updating the call parameters in the target SDR session detailed record data table according to the signaling in the call relay process. The method and the device are used in the determining process of SDR data.

Description

SDR data determining method, device and storage medium

Technical Field

The present application relates to the field of communications technologies, and in particular, to a method and an apparatus for determining SDR data, and a storage medium.

Background

In the related art, a Long Term Evolution Voice-over-terminal Evolution (VoLTE) is a comprehensive end-to-end network, spans multiple fields of radio, EPC (Evolved Packet Core), IP multimedia systems (IP Multimedia Subsystem, IMS), communication satellites (Communication Satellite, CS) and the like, relates to numerous network elements and network interfaces, has complicated network element interactions, has high service implementation difficulty, and has great challenges for operators due to operation and maintenance requirements. Therefore, if the quality of service analysis of the VoLTE network needs to be implemented, the second generation mobile phone communication technology (2-Generation wireless telephone technology, 2G) network, the third generation mobile phone communication technology (3-Generation wireless telephone technology, 3G) network, and the fourth generation mobile phone communication technology (4-Generation wireless telephone technology, 4G) network are mutually matched, which involves multiple network interaction exchanges, and the number of integrated network element interfaces is tens.

For call tracing analysis, call routing analysis, drop reason analysis and delimitation, applications such as voice quality analysis, nuisance call analysis and the like must be realized completely according to session detail (Session Detail Record, SDR) records. The existing signaling monitoring system can only realize call association analysis of a single network and a few scenes, so that interfaces related to SDR data are not comprehensive enough, and the accuracy of the SDR data is lower. Therefore, determining SDR data across multiple types of networks is a current technical problem that is in need of resolution.

Disclosure of Invention

The application provides a method and a device for determining SDR data and a storage medium, which can determine SDR data crossing multiple types of networks.

In order to achieve the above purpose, the present application adopts the following technical scheme:

in a first aspect, the present application provides a method for determining SDR data, the method comprising: acquiring target call ticket data; the target call ticket data includes: signaling in the call relay process and user identification in the call relay process; determining a target SDR session detailed record data table associated with user identification in the call relay process; the target SDR session detailed record data table is used for storing call parameters in a target call flow, wherein the target call flow is a call flow to which target call ticket data belong, and the call parameters comprise at least one of signaling messages and call fields; and updating the call parameters in the target SDR session detailed record data table according to the signaling in the call relay process.

With reference to the first aspect, in a possible implementation manner, determining a target SDR session detailed record data table associated with a user identifier in a call relay process includes: determining whether the target call ticket data is call ticket data of the starting call; if yes, establishing a target SDR session detailed record data table according to the user identification in the call relay process, and generating an association relation between the target SDR session detailed record data table and the user identification in the call relay process; if not, determining a user dynamic table corresponding to the user identification in the call relay process; the user dynamic list comprises user identifications of different relay stages in the target call flow; and determining the SDR data table associated with the user dynamic table as a target SDR session detailed record data table.

With reference to the first aspect, in one possible implementation manner, the establishing a target SDR session detailed record data table according to a user identifier in a call relay process includes: determining the call type of the target call flow; under the condition that the call type of the target call flow is the call initiated by the target operator, a target SDR session detailed record data table is established according to the gateway office configuration table of the target operator; under the condition that the call type of the target call flow is international call, determining whether a calling record of the target call flow exists in a call ticket record of a gateway of the international call; if yes, establishing a target SDR session detailed record data table according to the calling record of the target call flow; if not, a target SDR session detailed record data table is established according to the calling record of the target call flow in the long distance office; determining whether a call record of the target call flow exists in the local office under the condition that the call type of the target call flow is the call flow of the local PSTN public switched telephone network; if yes, establishing a target SDR session detailed record data table according to the call record of the call flow in the local office; if not, the local office is used as a call starting point, a call is initiated to the local office, and a target SDR session detailed record data table is established according to the initiated call; and under the condition that the call type of the target call flow is the call flow initiated by the local access network equipment, establishing a target SDR session detailed record data table according to the ticket data of the interface of the local access network equipment.

With reference to the first aspect, in a possible implementation manner, a type of a network carrying the target call flow is determined; determining user identification of a target call flow in different call relay processes according to the type of the network; and generating a user dynamic table according to the user identification of the call flow in different call relay processes.

With reference to the first aspect, in one possible implementation manner, updating the call parameters in the target SDR session detailed record data table according to signaling in the call relay process further includes: determining whether the target call ticket data is call ticket data of ending the call; if yes, after updating the call parameters in the target SDR session detailed record data table according to the signaling in the call relay process, determining that the updating of the target SDR session detailed record data table is completed.

In a second aspect, the present application provides an apparatus for determining SDR data, the apparatus comprising: a processing unit and an acquisition unit; an acquisition unit for acquiring the target call ticket data; the target call ticket data includes: signaling in the call relay process and user identification in the call relay process; a processing unit, configured to determine a target SDR session detailed record data table associated with a user identifier in a call relay process; the target SDR session detailed record data table is used for storing call parameters in a target call flow, wherein the target call flow is a call flow to which target call ticket data belong, and the call parameters comprise at least one of signaling messages and call fields; and the processing unit is used for updating the call parameters in the target SDR session detailed record data table according to the signaling in the call relay process.

With reference to the second aspect, in one possible implementation manner, the processing unit is specifically configured to: determining whether the target call ticket data is call ticket data of the starting call; if yes, establishing a target SDR session detailed record data table according to the user identification in the call relay process, and generating an association relation between the target SDR session detailed record data table and the user identification in the call relay process; if not, determining a user dynamic table corresponding to the user identification in the call relay process; the user dynamic list comprises user identifications of different relay stages in the target call flow; and determining the SDR data table associated with the user dynamic table as a target SDR session detailed record data table.

With reference to the second aspect, in one possible implementation manner, the processing unit is specifically configured to: determining the call type of the target call flow; under the condition that the call type of the target call flow is the call initiated by the target operator, a target SDR session detailed record data table is established according to the gateway office configuration table of the target operator; under the condition that the call type of the target call flow is international call, determining whether a calling record of the target call flow exists in a call ticket record of a gateway of the international call; if yes, establishing a target SDR session detailed record data table according to the calling record of the target call flow; if not, a target SDR session detailed record data table is established according to the calling record of the target call flow in the long distance office; determining whether a call record of the target call flow exists in the local office under the condition that the call type of the target call flow is the call flow of the local PSTN public switched telephone network; if yes, establishing a target SDR session detailed record data table according to the call record of the call flow in the local office; if not, the local office is used as a call starting point, a call is initiated to the local office, and a target SDR session detailed record data table is established according to the initiated call; and under the condition that the call type of the target call flow is the call flow initiated by the local access network equipment, establishing a target SDR session detailed record data table according to the ticket data of the interface of the local access network equipment.

With reference to the second aspect, in one possible implementation manner, the processing unit is specifically configured to: determining the type of a network carrying the target call flow; determining user identification of a target call flow in different call relay processes according to the type of the network; and generating a user dynamic table according to the user identification of the call flow in different call relay processes.

With reference to the second aspect, in a possible implementation manner, the processing unit is further configured to: determining whether the target call ticket data is call ticket data of ending the call; if yes, after updating the call parameters in the target SDR session detailed record data table according to the signaling in the call relay process, determining that the updating of the target SDR session detailed record data table is completed.

In a third aspect, the present application provides an apparatus for determining SDR data, the apparatus comprising: a processor and a communication interface; the communication interface is coupled to a processor for running a computer program or instructions to implement the method of determining SDR data as described in any one of the possible implementations of the first aspect and the first aspect.

In a fourth aspect, the present application provides a computer readable storage medium having instructions stored therein which, when run on a terminal, cause the terminal to perform a method of determining SDR data as described in any one of the possible implementations of the first aspect and the first aspect.

In this application, the names of the above-mentioned service transmission apparatuses do not constitute limitations on the devices or function modules themselves, and in actual implementation, these devices or function modules may appear under other names. Insofar as the function of each device or function module is similar to the present application, it is within the scope of the claims of the present application and the equivalents thereof.

These and other aspects of the present application will be more readily apparent from the following description.

Based on the technical scheme, the method for determining SDR data provided by the embodiment of the application acquires the signaling in the call relay process and the user identification in the call relay process through the electronic equipment, and then determines the target SDR session detailed record data table according to the target SDR session detailed record data table associated with the user identification in the call relay process according to the user identification in the call relay process, and finally updates the call parameters in the target SDR session detailed record data table according to the signaling in the call relay process.

Drawings

Fig. 1 is a schematic structural diagram of an electronic device provided in the present application;

fig. 2 is a flowchart of a method for determining SDR data provided in the present application;

fig. 3 is a flowchart of another method for determining SDR data provided in the present application;

fig. 4 is a flowchart of another method for determining SDR data provided by the present application;

fig. 5 is a flowchart of another method for determining SDR data provided by the present application;

fig. 6 is a flowchart of another method for determining SDR data provided by the present application;

fig. 7 is a schematic structural diagram of an SDR data determining device provided in the present application;

fig. 8 is a schematic structural diagram of another SDR data determining device provided in the present application.

Detailed Description

The method and apparatus for determining SDR data and the storage medium thereof provided in the embodiments of the present application are described in detail below with reference to the accompanying drawings.

The term "and/or" is herein merely an association relationship describing an associated object, meaning that there may be three relationships, e.g., a and/or B, may represent: a exists alone, A and B exist together, and B exists alone.

The terms "first" and "second" and the like in the description and in the drawings are used for distinguishing between different objects or for distinguishing between different processes of the same object and not for describing a particular sequential order of objects.

Furthermore, references to the terms "comprising" and "having" and any variations thereof in the description of the present application are intended to cover a non-exclusive inclusion. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those listed but may optionally include other steps or elements not listed or inherent to such process, method, article, or apparatus.

It should be noted that, in the embodiments of the present application, words such as "exemplary" or "such as" are used to mean serving as an example, instance, or illustration. Any embodiment or design described herein as "exemplary" or "for example" should not be construed as preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "such as" is intended to present related concepts in a concrete fashion.

Fig. 1 is a schematic structural diagram of an electronic device according to an embodiment of the present application, as shown in fig. 1, where the electronic device 100 includes at least one processor 101, a communication line 102, and at least one communication interface 104, and may further include a memory 103. The processor 101, the memory 103, and the communication interface 104 may be connected through a communication line 102.

The processor 101 may be a central processing unit (central processing unit, CPU), an application specific integrated circuit (application specific integrated circuit, ASIC), or one or more integrated circuits configured to implement embodiments of the present application, such as: one or more digital signal processors (digital signal processor, DSP), or one or more field programmable gate arrays (field programmable gate array, FPGA).

Communication line 102 may include a pathway for communicating information between the aforementioned components.

The communication interface 104, for communicating with other devices or communication networks, may use any transceiver-like device, such as ethernet, radio access network (radio access network, RAN), wireless local area network (wireless local area networks, WLAN), etc.

The memory 103 may be, but is not limited to, a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (random access memory, RAM) or other type of dynamic storage device that can store information and instructions, or an electrically erasable programmable read-only memory (electrically erasable programmable read-only memory, EEPROM), a compact disc read-only memory (compact disc read-only memory) or other optical disc storage, optical disc storage (including compact disc, laser disc, optical disc, digital versatile disc, blu-ray disc, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to include or store desired program code in the form of instructions or data structures and that can be accessed by a computer.

In a possible design, the memory 103 may exist independent of the processor 101, i.e. the memory 103 may be a memory external to the processor 101, where the memory 103 may be connected to the processor 101 through a communication line 102 for storing execution instructions or application program codes, and the execution is controlled by the processor 101 to implement a network quality determining method provided in the embodiments described below. In yet another possible design, the memory 103 may be integrated with the processor 101, i.e., the memory 103 may be an internal memory of the processor 101, e.g., the memory 103 may be a cache, and may be used to temporarily store some data and instruction information, etc.

As one implementation, processor 101 may include one or more CPUs, such as CPU0 and CPU1 in fig. 1. As another implementation, the electronic device 100 may include multiple processors, such as the processor 101 and the processor 107 in fig. 1. As yet another implementation, the electronic device 100 may also include an output device 105 and an input device 106.

From the foregoing description of the embodiments, it will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-described division of functional modules is illustrated, and in practical application, the above-described functional allocation may be implemented by different functional modules according to needs, i.e. the internal structure of the network node is divided into different functional modules to implement all or part of the functions described above. The specific working processes of the above-described system, module and network node may refer to the corresponding processes in the foregoing method embodiments, which are not described herein.

The terms related to the present application are explained below.

1. Call Data Record (CDR) is a file Data transferred inside the communication system, and records information of each original communication Record. The method comprises a series of information including serial numbers, user identifications, calling numbers, called numbers, starting time, ending time, call duration, internet traffic, call properties and the like.

2. Session detail record (Session Detail Record, SDR) in a mobile packet network, a complete Session record message generated after a Session is ended, i.e. a complete interaction from a user createp dprequest to DeletePDP Response will generate 1 SDR.

3. External data representation (External Data Representation, XDR); XDR is a function of the open network computing environment of SunSoft. XDR provides an architecture independent representation data that addresses differences in data byte ordering, data byte size, data representation, and data alignment.

4. SIP (Session initialization Protocol, session initiation protocol) is a multimedia communication protocol formulated by IETF (Internet Engineering Task Force ).

5. BSSAP (Base Station System Application), referred to as the base station system application part, is the application layer protocol on the a interface in gsm.

6. Radio Access Network Application Protocol (RANAP) for connection of RNC to core network, which comprises the GSM system BSSMAP. The main functions of the protocol are: RAB management, transparent transport NAS message flow, paging, security mode control, and location information reporting, among others.

7. SRVCC (Single Radio Voice Call Continuity) is a VoLTE voice service continuity scheme proposed by 3GPP, and is mainly used for solving the problem of how to ensure voice call continuity when a single radio UE moves between an LTE/Pre-LTE network and a 2G/3G CS network, i.e. ensuring smooth handover of the single radio UE between IMS-controlled VoIP voice and CS domain voice.

8. MAP: mobile Application Part (mobile application part), mobile Application Part (MAP) conforms to the SS7 protocol standard.

9. The INAP gateway (Intelligent Network Application Protocol) provides the best choice on the market. It is mainly applied to the following IN nodes: SCP, SDP, and IP.

10. The Diameter protocol is used as the next generation AAA protocol standard by the IETF AAA working group. Diameter (Diameter, meaning that Diameter protocol is an upgraded version of RADIUS protocol) protocols include basic protocol, NAS (network access service) protocol, EAP (extensible authentication) protocol, MIP (mobile IP) protocol, CMS (cipher message syntax) protocol, etc.

11. Block error second ratio (Errored Second Ratio, ESR), the ratio of the number of ESs present at the time available to the total number of seconds for a determined test time.

In the related art, voLTE is a comprehensive end-to-end network, spans multiple fields such as radio and EPC, IMS, CS, and relates to a plurality of network elements and network interfaces, wherein the network elements are intricate and complex in interaction, the service implementation difficulty is high, and the operation and maintenance requirements of the VoLTE bring great challenges to operators. Meanwhile, voLTE opens the way for voice evolution towards mobile broadband, and the voice solution of service control is realized by taking LTE network as service access and IMS network. Therefore, if the quality of service analysis of the VoLTE network needs to be implemented, the 2G network, the 3G network, and the 4G network cooperate with each other, which involves multiple network interaction exchanges, and several tens of network element interfaces are integrated. The deployment application of VoLTE relates to all core network elements, the network transformation amount is far greater than CSFB, a large number of interfaces need to be adapted, the existing network also needs to realize smooth migration, and the service conflict and the processing sequence of the network manager also need to be analyzed and verified.

For call tracing analysis, call routing analysis, drop reason analysis and delimitation, voice quality analysis, nuisance call analysis and other applications must be realized completely according to SDR records. The existing signaling monitoring system can only realize call association analysis of a single network and a few scenes, so that interfaces related to SDR data are not comprehensive enough, and the accuracy of the SDR data is lower.

In order to solve the problems in the prior art, the present application provides a method for determining SDR data as shown in fig. 2. The method comprises the following steps: firstly, signaling in the call relay process and user identification in the call relay process are acquired through electronic equipment, then a target SDR session detailed record data table associated with the user identification in the call relay process is determined, and finally call parameters in the target SDR session detailed record data table are updated according to the signaling in the call relay process. Because the signaling in each relay process in the calling process carries the user identification of the calling user, the user identification can be used for associating the calling data of the same calling process in different types of networks into the same SDR table, and the purpose of determining SDR data of the calling process across multiple networks is realized.

As shown in fig. 2, a method for determining SDR provided in the present application includes the following S201-S203.

S201, the electronic equipment acquires the target call ticket data.

Wherein, the destination call ticket data includes: signaling during call relay and user identification during call relay.

Alternatively, the destination call ticket data may be XDR data, CDR data or backup designated router (back-up designated router, BDR) data. The present disclosure is not limited in this regard.

It should be noted that a call procedure generally includes the following call relay procedure: a call relay process from the calling terminal to the calling terminal access network equipment; a calling relay process from the calling terminal access network equipment to the calling terminal call control center; a call relay process from a calling terminal call control center to core network equipment; a call relay process from the core network equipment to the called terminal call control center; a call relay process from the called terminal call control center to the called terminal access network equipment; the called end accesses the call relay process from the network device to the called terminal. The above call relay process is merely an exemplary illustration and does not constitute a limitation of the call relay process in the present disclosure.

In each relay process, corresponding call ticket data are generated in the network. The target call ticket data may be call ticket data in any of the above call relay processes.

S202, the electronic equipment determines a target SDR session detailed record data table associated with the user identification in the call relay process.

The target SDR session detailed record data table is used for storing call parameters in a target call flow, wherein the target call flow is a target call flow to which target call ticket data belong, and the call parameters comprise at least one of signaling information and call fields.

It should be noted that the user identification in the call ticket data may be different during different call relaying procedures, as well as when making calls in different types of networks. The electronic device can build a mobile user dynamic table. The mobile subscriber dynamic table includes the identities used by subscribers during different call relay procedures. The mobile user dynamic table is associated with an SDR data table corresponding to the call of the user.

The electronic equipment can determine the mobile user dynamic list of the user call through the call relay type of the target call ticket data, the network type of the call and the user identification in the target call ticket data, and further the SDR data list corresponding to the call is displayed according to the mobile user dynamic list.

As an example, user identification of calls made in different types of networks during different call relaying processes includes, but is not limited to: calling number, called number, original called number, user roaming number; temporary mobile subscriber identity (Temporary Mobile Subscriber Identity, TMSI), packet temporary mobile subscriber identity (Packet Temperate Mobile Subs cription Identity, P-TMSI), international mobile subscriber identity (International Mobile Subscriber Identity, IMSI), international mobile equipment identity (International Mobile Equipment Identity, IMEI), MSISDN (Mobile Subscriber International ISDN/PSTN number), packet temporary mobile subscriber identity (P-TMSI),

Mobile station roaming number (Mobile Station Roaming Number, MSRN), etc.; SRVCC relation table field in 4G network: c_msisdn, stn_sr, att-sti, msisdn_capability.

It should be noted that for the VOLTE service, it is necessary to distinguish whether the terminal supports SRVCC (Single Radio Voice Call Continuity). If the SRVCC is supported, the SRVCC process has STN-SR, ATU-STI and other fields for forming a corresponding relation with the MSISDN, at the moment, the SRVCC relation table can be established, and the fields of the SIP related CDR can be backfilled in the table;

alternatively, the electronic device may establish a session_id, ue_ip, c_msisdn, imsi four element correspondence table using a Diameter record with an application id 16777236, 16777238 of the Diameter records.

When new corresponding relation between the session_id and any element of the ue_ip, the c_msisdn and the imsi occurs or new corresponding relation between any element of the ue_ip, the c_msisdn and the imsi and the session_id occurs, deleting the last four-element corresponding relation record and establishing a new four-element corresponding relation record.

The record fields of ue_ip, c_msisdn and imsi are not filled in the records with the application IDs 16777236 and 16777238 in the Diameter record, and backfill processing is performed in real time through a four-element corresponding relation table.

It should be noted that, when the user identifier is a mobile phone number, the mobile phone number field in the target call ticket data may be prefixed or not prefixed. E.g., 86, +86, 0086, area code, 1254708, 60, 1241, etc. (the electronic device may be configured to add other prefixes as well).

At this time, when the mobile user dynamic table is managed, a fuzzy matching method can be adopted for association, for example, number prefix is ignored for association, and the situation that numbers cannot be associated correctly due to prefix is avoided.

S203, the electronic equipment updates the call parameters in the target SDR session detailed record data table according to the signaling in the call relay process.

In one possible implementation, the target SDR session detail record data table is used to backfill the entire end-to-end signaling flow of a call. After the electronic equipment acquires a target call ticket data in the call process, the signaling in the call relay process in the target call ticket data is updated to the target SDR session detail record data table through the SDR data table corresponding to the call by the user identification. Thus, after the electronic device obtains all the target call ticket data in the call process, the signaling in the call relay process in all the target call ticket data can be updated to the target SDR session detailed record data table, so as to form all the end-to-end signaling flow of the call.

It can be understood that the target call ticket data may further include a time of the call relay process, and the electronic device may update signaling in the call relay process in each target call ticket data in the call process to the target SDR session detailed record data table according to the call relay process and the time sequence.

The scheme at least brings the following beneficial effects:

In a possible implementation manner, as shown in fig. 3 in connection with fig. 2, the step S202 of determining, by the electronic device, a target SDR session detailed record data table associated with a user identifier in a call relay process may be specifically implemented by the following steps S301 to S307, which are described in detail below:

s301, the electronic device determines whether the target call ticket data is call ticket data of a starting call.

And S302, if so, the electronic equipment establishes a target SDR session detailed record data table according to the user identification in the call relay process.

In one possible implementation manner, if the target call ticket data is call ticket data of the primary call, the target SDR session detailed record data table of the primary call is established according to the user identification in the call relay process of the primary call.

Illustratively, the SDR session detailed record data table established by the electronic device is shown in table 1 below.

Table 1SDR session detail record data table

S303, the electronic equipment generates an association relation between the target SDR session detailed record data table and the user identification in the call relay process.

In one possible implementation, the electronic device records the data table for the SDR session detail for the target SDR session of the initial call according to the SDR session detail record data table associated with the user dynamic table of the user identification during the call relay of the initial call.

S304, if not, the electronic equipment determines a user dynamic table corresponding to the user identification in the call relay process.

The user dynamic table comprises user identifications of different relay stages in the target call flow.

In one possible implementation manner, if the target call ticket data is not the call ticket data of the first call, it is stated that the SDR data table corresponding to the current target call flow has been established before, and only the user dynamic table corresponding to the user identifier in the current call relay process needs to be determined at this time, and the SDR data table corresponding to the current target call flow is queried according to the user dynamic table.

It can be understood that the user dynamic table stores the user identifier of the user in each relay process, and the electronic device can find the user dynamic table to which the user identifier in the relay process belongs when knowing the user identifier in the relay process.

S305, the electronic equipment determines the SDR session detailed record data table associated with the user dynamic table as a target SDR session detailed record data table.

In a possible implementation manner, after S305, the electronic device may further determine whether the target call ticket data is call ticket data of the ending call, so as to determine whether to end updating of the target SDR session detailed record data table, which specifically includes S306 and S307 below.

S306, the electronic equipment determines whether the target call ticket data is call ticket data of ending the call.

S307, if yes, the electronic device determines that updating of the target SDR session detailed record data table is completed after updating the call parameters in the target SDR session detailed record data table according to the signaling in the call relay process.

In one example, the electronic device determines the target call ticket data as call ticket data for ending the call, and the call end time of all the target call ticket data is added with a specified time interval by the end time of the record initiated by the calling end, wherein the specified time interval defaults to sixty seconds, and is independent of the release time record value of the called end. And if the CDR release time of the called terminal is within the specified time interval, taking the release time value of the floor call of the called terminal. The SDR calling number is taken from the calling number of the calling record of the initiating terminal, and the area code and the country code and the associated translation number can be marked and recorded before the calling number; the called number then records the last called number associated with the call CDR. The record of the route number information added before the called number of the initiating terminal is not covered with the processing.

When SDR is related to the SIP_CC and FN_SIP_CC tables, the minimum session_time in each record of the SIP is preferentially taken as the time for comparison of the association conditions; BSSAP_CC/RANAP_CC takes end_time if it is the call between CS without SIP table, and isup/bicc takes callingrel_ delay, calledrel _delay. The description of start_time+session_time and end_time in all the associated times below applies to this section of description.

And judging whether the call records of the landing terminal are processed or not according to whether the network call route is complete or not and whether the interface records of the SRVCC are complete or not when the SDR finishes processing. In an abnormal situation, the call record end time is prolonged 120S (default value, adjustable) to force the end and the sealing process.

In the above, it is described in detail how the electronic device determines whether or not the target call ticket data is call ticket data for ending the call.

In a possible implementation manner, as shown in fig. 4 in conjunction with fig. 3, in S302, the electronic device establishes the target SDR session detailed record data table according to the user identifier in the call relay process, which may be specifically implemented in the following S401-S409.

S401, the electronic equipment determines the call type of the target call flow.

S402, under the condition that the call type of the target call flow is the call initiated by the target operator, the electronic equipment establishes a target SDR session detailed record data table according to the gateway office configuration table of the target operator.

If the call type of the target call flow is a call initiated by an external network, an inter-network call record initiated by a gateway office of an external network operator is required, and the electronic device generates a target SDR session detailed record data table synthesis process according to the gateway office configuration table provided by the operator.

S403, under the condition that the call type of the target call flow is international call, the electronic equipment determines whether a calling record of the target call flow exists in a ticket record of a gateway of the international call.

S404, if so, the electronic equipment establishes a target SDR session detailed record data table according to the calling record of the target call flow.

And S405, if the target SDR session detail record data table is established by the electronic equipment according to the calling record of the target call flow in the long distance office.

It will be appreciated that the operator must provide configuration tables for international and long distance offices from which to generate a target SDR session detail record data table for international and provincial incoming call records.

S406, in case that the call type of the target call flow is the call flow of the local PSTN public switched telephone network, the electronic equipment determines whether the call record of the target call flow exists in the local office.

S407, if the target SDR session detail record data table is established by the electronic equipment according to the call record of the call flow in the local office.

A local office may be understood as a local office, for example; for a local PSTN public switched telephone network, the electronic device may be according to Q.931/H in front of the local telephone office. 248 signaling generates a target SDR session detail record data table.

And S408, if the target SDR session detail record data table does not exist, the electronic equipment initiates a call to the local office by taking the local office as a call starting point, and establishes the target SDR session detail record data table according to the initiated call.

S409, under the condition that the call type of the target call flow is the call flow initiated by the local access network equipment, the electronic equipment establishes a target SDR session detailed record data table according to the call ticket data of the interface of the local access network equipment.

For example, for voice and video calls initiated by the local access network devices BSC/RNC, NB/NR, the electronic device may generate a target SDR session detail record data table based on the XDR of the A/Iu/S1/N1N2 interface.

In a possible implementation manner, in conjunction with fig. 3, as shown in fig. 5, an embodiment of the disclosure further provides a method for generating a user dynamic table by using an electronic device. The method specifically includes the following S501-S503.

S501, the electronic equipment determines the type of the network carrying the target call flow.

The types of networks for the target call flow include, for example, 2G network users, 3G network users, and 4G network users.

S502, the electronic equipment determines user identification of the target call flow in different call relay processes according to the type of the network.

In one example, when the types of networks are 2G network users and 3G network users, the electronic device determines that the user identities of the target call flow during different call relay procedures are TMSI, P-TMSI, IMSI, IMEI, MSISDN, and MSRN.

In another example, when the network is a 4G network user, a service based on Long Term Evolution (Voice-terminal Evolution, voLTE) used by the 4G network needs to distinguish whether the handset supports SRVCC (Single Radio Voice Call Continuity), and in the SRVCC process, there are fields such as STN-SR, ATU-STI, etc. for forming a corresponding relationship with the MSISDN, an SRVCC relationship table needs to be established for backfilling fields of the SIP-related CDRs. Wherein the SRVCC relationship table field includes: c_msisdn, stn_sr, att-sti, msisdn_capability.

Establishing a four-element corresponding relation table of session_id, ue_ip, c_msisdn and imsi by using Diameter records with application IDs 16777236 and 16777238 in Diameter records; when new corresponding association occurs between any element of the session_id and the ue_ip, the c_msisdn and the imsi or new corresponding relationship occurs between any element of the ue_ip, the c_msisdn and the imsi and the session_id, deleting the last four-element corresponding relationship record and establishing a new four-element corresponding association record; the record fields of ue_ip, c_msisdn and imsi are not filled in the records with the application IDs 16777236 and 16777238 in the Diameter record, and backfill processing is performed in real time through a four-element corresponding relation table.

S503, the electronic equipment generates a user dynamic table according to the user identification of the call flow in different call relay processes.

For one example, the signaling of 2G network users, 3G network users, and 4G network users is backfilled into the user dynamic table.

In the above, details are given on how the electronic device generates the user dynamic table.

In a possible implementation manner, the destination call ticket data may be specifically classified according to the following manner, which is described in detail below.

In the mode 1, the electronic device may classify the destination call ticket data based on the type of the external network from which the call is initiated.

Optionally, the external network type: including domestic gateway offices and international gateway offices. The domestic gateway office comprises gateway offices of different cities; the international gateway office includes international gateway offices of different markets.

The electronic equipment divides the target call ticket data into call ticket data of the domestic gateway office and call ticket data of the international gateway office based on the difference of gateway offices initiated by the call.

Mode 2, the electronic device may further classify the destination call ticket data based on the type of the internal network from which the call is initiated.

Optionally, the internal network types include: PSTN network (including fixed network access network and fixed local network); an interprovincial long distance office, tandem mobile switching center (Tandem Mobile Switching Center, TMSC); a 2G network; a 3G network; a 4G network; 5G network.

The electronic device may divide the different types of target call ticket data based on the different types of networks from which the call originates.

Mode 3, the electronic device may classify the destination call ticket data based on the access network and the core network.

The destination call ticket data in the access network can also be called as originating and landing tables. The electronic device classifies and identifies the call relay procedures performed in the access network according to the 2, 3, 4G network architecture.

The destination call ticket data in the access network comprises data of interfaces such as A, iu, S1 and the like, so that the electronic equipment can more conveniently determine the relevant base table and field assignment information from end to end.

The destination call ticket data in the core network may also be referred to as routing and traffic tables. The electronic equipment divides the call relay process of the core network part into different routes of calls and different mobile management services according to the 2, 3 and 4G network architecture, and the intelligent network service table carries out identification definition so as to determine the relevant core netlist and field assignment information from end to end.

Different routes of the call relate to protocol record processing such as ISUP/BICC/SIP, MGCP, Q.931, H248 and the like; the core network service relates to protocol record processing such as MAP, CAP/INAP, diameter and the like.

It is to be noted that, in a specific implementation, the electronic device may classify the target call ticket data with reference to any one or more of the above-described modes 1 to 3. The present disclosure is not limited in this regard.

In one example, in different types of networks, the underlying table names of the target call ticket data are as follows:

in a VOLTE network, the names of the underlying tables include, but are not limited to, at least one of:

ZC_IMS_DIAMETER_BDR；ZC_RxGx_DIAMETER_BDR；ZC_SIP_CC_BDR；ZC_SV_BDR。

in an IMS network, the names of the underlying tables include, but are not limited to, at least one of:

ZC_FN_IMS_DIAMETER_BDR；ZC_FN_SIP_CC_BDR；ZC_DNS_ENUM_BDR。

In a GSM network, the names of the underlying tables include, but are not limited to, at least one of:

ZC_BICC_BDR；ZC_ISUP_BDR；ZC_SIPI_BDR；ZC_H248_BDR；ZC_MGCP_BDR；ZC_SCCP_BDR；ZC_CAP_BDR；ZC_INAP_BDR；ZC_GBSSAP_CC_BDR；ZC_GBSSAP_MM_BDR；ZC_RANAP_CC_BDR；ZC_RANAP_MM_BDR；ZC_GMAP_CC_BDR；ZC_GMAP_HO_BDR；ZC_MAPplus_BDR；ZC_Q931_BDR。

in a CDMA network, the names of the underlying tables include, but are not limited to, at least one of: zc_a1_cc_ bdr; zc_a1_paging_ bdr; zc_cmap_cc_ bdr; zc_cwin_ bdr.

In an LTE network, the names of the underlying tables include, but are not limited to, at least one of:

ZC_SGSAP_SGS_CDR；ZC_DIAMETER_S6A_BDR；ZC_S1_ERAB_BDR；ZC_S1_HANDOVER_CDR；

ZC_S1_EMM_CDR；ZC_S1_ESM_CDR；ZC_GTPV2C_S5S8_BDR；ZC_GTPV2_S10S11_CDR；

ZC_S1_CONTEXT_BDR。

in a soft-mining network, the names of the underlying tables include, but are not limited to, at least one of:

ZC_UE_MR_BDR；ZC_UU_BDR；ZC_X2_BDR；ZC_Cell_MR_BDR。

it can be understood that the basic table name of the target call ticket data can be extended to other networks, for example, extended to interface corresponding tables such as N1/N2/N3/N4 of a 5G network; the present disclosure is not limited in this regard.

The classification of the target call ticket data under different scenes and the corresponding basic table are described in detail above.

Hereinafter, contents in the SDR data table will be described in detail.

In a possible implementation manner, the target SDR session detailed record data table may specifically include the following contents:

an SDR field of a call service, and an SDR field of a registration service. And an SDR field of a mobility management service.

The field is mainly used for recording information such as signaling flow, call time, call result, voice call quality and the like in the call process.

The SDR field of the registration service is a field related to the processing of the dynamic association table of the registration service record and the mobile user, and is mainly used for ensuring the accuracy of SDR association processing.

The SDR field of the mobility management service is related to the processing of the dynamic association table of the mobile user for the mobility management service record, and is mainly used for ensuring the accuracy of SDR association processing.

The SDR field of the call service will be mainly described in detail below.

In case 1, the electronic device may classify the SDR field of the call service according to the function of the field.

Illustratively, the SDR field of the call service includes, but is not limited to, at least one of the following types of fields:

A. a conventional field; B. an SV class field; C. VOID; D. a first split class field; E. the delimiter field is not switched on; F. an end-to-end delay field; G. a wireless delimitation field; H. a call stage field; I. a drop call delimitation field; J. media analysis field.

It should be noted that the above classification of the SDR field of the call service is only an exemplary illustration. The classification of the SDR field of the call service may be increased, decreased or modified according to the actual requirements, which is not limited in this application.

And 2, the electronic equipment defines a call result field according to the call result.

First, the electronic device defines a call result field (result field), and the call result field definition type value includes: 0 success (answer and ringing); 1 failed (not on); 2, dropped call; 3SRVCC handover failed; 4mos mass difference; 5 others (e.g., timeout no response).

Wherein, the priority of the call result field is respectively as follows: 2,3,4,1,0.

The electronic device then determines the assignment condition for each of the call result fields described above.

For the failed (not connected) call result, if the electronic device does not locate the result by the accumulated experience library and the wireless delimitation mode, the electronic device can delimit according to the first split delimitation mode.

Exemplary, the conditions for first tearing down the delimitation include: reading the fields in the static table ZcSDRNetBound matching static table through the fields of first_error_ protocol, first _error_cause, first_error_cause_type, first_error_msg_direct and first_error_msg in the SDR, matching assigned field delimiter code value (error_bound) and delimit reason (alert_reject).

For the dropped call result, the electronic device can be positioned by wireless delimitation. The wireless delimitation refers to a mode of performing problem delimitation positioning by using soft acquisition data such as MR data.

It is noted that the electronic device determines whether to wirelessly delimit based on whether soft-mining data is collected. When soft data is collected, the electronic device can carry out wireless delimitation on the dropped call, and when soft data is not collected, the electronic device can not carry out wireless delimitation on the dropped call data.

For the call result of the SRVCC handover failure, the electronic device associates msisdn, imsi service request message, ESR, split, TAU (cdr _type 76, 69, 72) of EMM with call, call_imsi (association 69 analyzes drop call, association 72 analyzes SRVCC).

The electronic device associates msisdn, imsi paging, service request message, ESR, split, TAU (cdr _type 78, 4, 76, 69, 72) with the encapsulated/encapsulated_imsi EMM (association 69 analyzes dropped calls, association 72 analyzes SRVCC).

It should be noted that the electronic device may be associated with a 4G network acquisition data interface, and the IMS service is associated with the VoLTE service. Illustratively, the association includes, but is not limited to, at least one of: 1) SIPCC is self-associated; 2) SIPCC is associated with DNS; 3) SIPCC is associated with IMS DIMATER/FN_ IMS DIAMETER; 4) SIPCC is associated with RXGX parent CDR; 5) SIPCC is associated with RXGX single interface CDR; 6) SIPCC is associated with the S1 interface; 7) SIPCC is associated with S5S8, S10S 11; 8) SIPCC is associated with S6A; 9) SIPCC is associated with SV; 10 SIPCC & SV is associated with the incisional A/IUCS ports; 11 SIPCC is associated with MAP_CC.

It will be appreciated that the description in the target SDR session detail record data table is described by way of example, and the manner described above may be adaptively extended to other networks, for example, the extension processing may be performed on associated interface data of a 5G network, which is not limited in this disclosure.

Illustratively, the SDR data table established by the electronic device is shown in table 2 below:

TABLE 2

/>

The electronic device may fill the relevant fields in the target call ticket data into the table 2 by associating the target call ticket data with the table.

In one possible implementation, the field assignment in the target SDR session detail record data table may specifically include the following:

call results and call first split field assignment conditions for target SDR data.

The call result of the target SDR data comprises the following three cases:

in the case a, when talk_time 0 is longer than 0, the call result is successful response; judging the conversation result:

at this time, the call drop assignment condition is: mo_drop_flag-! =default value or mt_drop_flag-! =default;

srvcc handover failure assignment condition: mo_esrvcc_result-! =0, default value or mo_esrvcc_result-! =0, default;

Speech mos bad quality assignment condition: mos_send <3000or mos_rec<3000.

In case b, when talk time of talk_time=0 equals 0 but alerting_time 0 rings longer than 0, the call result is successful connection.

In case c, when talk time of talk_time=0 is equal to 0 and alerting_time=0 ringing time is equal to 0, the call result is a call failure; and the reasons of called test failure, network failure and calling side failure are recorded in a distributed mode.

For call first tear-down class field assignment conditions, the first tear-down class field includes, but is not limited to, the following fields, call=result=0, 1, 2.

Illustratively, the first split class field is assigned as shown in Table 3 below.

TABLE 3 Table 3

It can be understood that the first fault reason is extracted according to the single interface record with the earliest absolute time calculated according to the associated single interface records, and the other first fault fields extract relevant information according to the first fault reason value record.

Exemplary, the first fault protocol and record reference table are shown in table 4 below:

TABLE 4 Table 4

/>

Illustratively, the first fault message includes: BICC/ISUP/SIPI judgment method: rel_loc; CAP/INAP judging method: the ACR applies for a reason of failure of the charging report; MAP judging method: PRN provides roaming number failure cause; SRI routing information failure reasons; a mouth/IUCS mouth judging method: taking first_rel_msg; the SIP judgment method comprises the following steps: taking first_rel_msg; the SV judging method comprises the following steps: taking first_rel_msg; the Diameter judgment method comprises the following steps: taking result_code; the DNS judging method comprises the following steps: empty; s1, judging that the method is empty; EMM first first_ cdr _type-! Time is calculated according to end_time=default value; the first time first_ cdr _type-! Time is calculated according to end_time=default value; ERAB is empty; s11& S5S8 judgment method is cdr _type+1; H248/MGCP judging method: taking first_rel_msg; the SGS judging method comprises the following steps: empty; a1 judgment method comprises the following steps: taking first_rel_msg; CMAP judging method: empty.

Illustratively, the first failure point "edge" includes: "edge" describes whether the fault occurs on the MO side, the MT side, or between offices; more fault reasons and fault edge records can be increased and expanded according to the end-to-end scene requirements; more field assignment processes are adjusted according to the system extension application.

The following is given. The overall process of how the electronic device guarantees the accuracy of SDR data is described in connection with fig. 6:

s601, the electronic equipment acquires target call ticket data.

The specific implementation of S601 is similar to S201 described above, and the specific implementation process of S201 may be referred to, which is not described herein.

S602, if the target call ticket data is call ticket data of the starting call, the electronic equipment establishes a target SDR session detailed record data table according to the user identification in the call relay process.

The specific implementation of S602 is similar to S302 described above, and the specific implementation process may refer to S302, which is not described herein.

S603, if the target call ticket data is not the call ticket data of the starting call, the electronic equipment determines a user dynamic table corresponding to the user identification in the call relay process.

The specific implementation of S603 is similar to that of S202 and S304, and the specific implementation process may refer to S202 and S304, which are not described herein.

S604, the electronic equipment processes the target call ticket data.

The specific implementation of S604 is similar to that of S401 and S409, and the specific implementation process of S401 and S409 may be referred to, which are not described herein.

And S605, the electronic equipment determines that the target call ticket data is call ticket data for ending the call, and the electronic equipment determines that the updating of the target SDR session detailed record data table is completed after updating the call parameters in the target SDR session detailed record data table according to the signaling in the call relay process.

The specific implementation of S605 is similar to S307, and the specific implementation process may refer to S307, which is not described herein.

The embodiment of the application may divide the functional module or the functional unit of the SDR data determining device according to the above method example, for example, each functional module or functional unit may be divided corresponding to each function, or two or more functions may be integrated into one processing module. The integrated modules may be implemented in hardware, or in software functional modules or functional units. The division of the modules or units in the embodiments of the present application is merely a logic function division, and other division manners may be implemented in practice.

As shown in fig. 7, a schematic structural diagram of an apparatus for determining SDR data according to an embodiment of the present application is provided, where the apparatus includes: a processing unit 701 and an acquisition unit 702; an acquiring unit 702, configured to acquire target call ticket data; the target call ticket data includes: signaling in the call relay process and user identification in the call relay process; a processing unit 701, configured to determine a target SDR session detailed record data table associated with a user identifier in a call relay process; the target SDR session detailed record data table is used for storing call parameters in a target call flow, wherein the target call flow is a call flow to which target call ticket data belong, and the call parameters comprise at least one of signaling messages and call fields; and a processing unit 701, configured to update the call parameters in the target SDR session detailed record data table according to the signaling in the call relay process.

Optionally, the processing unit 701 is specifically configured to: determining whether the target call ticket data is call ticket data of the starting call; if yes, establishing a target SDR session detailed record data table according to the user identification in the call relay process, and generating an association relation between the target SDR session detailed record data table and the user identification in the call relay process; if not, determining a user dynamic table corresponding to the user identification in the call relay process; the user dynamic list comprises user identifications of different relay stages in the target call flow; and determining the SDR data table associated with the user dynamic table as a target SDR session detailed record data table.

Optionally, the processing unit 701 is specifically configured to: determining the call type of the target call flow; under the condition that the call type of the target call flow is the call initiated by the target operator, a target SDR session detailed record data table is established according to the gateway office configuration table of the target operator; under the condition that the call type of the target call flow is international call, determining whether a calling record of the target call flow exists in a call ticket record of a gateway of the international call; if yes, establishing a target SDR session detailed record data table according to the calling record of the target call flow; if not, a target SDR session detailed record data table is established according to the calling record of the target call flow in the long distance office; determining whether a call record of the target call flow exists in the local office under the condition that the call type of the target call flow is the local PSTN network call flow; if yes, establishing a target SDR session detailed record data table according to the call record of the call flow in the local office; if not, the local office is used as a call starting point, a call is initiated to the local office, and a target SDR session detailed record data table is established according to the initiated call; and under the condition that the call type of the target call flow is the call flow initiated by the local access network equipment, establishing a target SDR session detailed record data table according to the ticket data of the interface of the local access network equipment.

Optionally, the processing unit 701 is specifically configured to: determining the type of a network carrying the target call flow; determining user identification of a target call flow in different call relay processes according to the type of the network; and generating a user dynamic table according to the user identification of the call flow in different call relay processes.

Optionally, the processing unit 701 is further configured to determine whether the destination call ticket data is call ticket data for ending a call; if yes, after updating the call parameters in the target SDR session detailed record data table according to the signaling in the call relay process, determining that the updating of the target SDR session detailed record data table is completed.

When implemented in hardware, the acquisition unit 702 in the embodiments of the present application may be integrated on a communication interface, and the processing unit 701 may be integrated on a processor. A specific implementation is shown in fig. 8.

Fig. 8 shows still another possible configuration diagram of the SDR data determination device involved in the above-described embodiment. The determining device of SDR data comprises: a processor 802 and a communication interface 803. The processor 802 is configured to control and manage actions of the SDR data determination device, for example, to perform the steps performed by the processing unit 701 described above, and/or to perform other processes of the techniques described herein. The communication interface 803 is used to support communication of the determining device of SDR data with other network entities, for example, to perform the steps performed by the above-described acquisition unit 702. The SDR data determination means may further comprise a memory 801 and a bus 804, the memory 801 being for storing program codes and data of the SDR data determination means.

Wherein the memory 801 may be a memory or the like in the SDR data determination device, which may include a volatile memory such as a random access memory; the memory may also include non-volatile memory, such as read-only memory, flash memory, hard disk or solid state disk; the memory may also comprise a combination of the above types of memories.

The processor 802 described above may be implemented or executed with various exemplary logic blocks, modules, and circuits described in connection with this disclosure. The processor may be a central processing unit, a general purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, a transistor logic device, a hardware component, or any combination thereof. Which may implement or perform the various exemplary logic blocks, modules, and circuits described in connection with this disclosure. The processor may also be a combination that performs the function of a computation, e.g., a combination comprising one or more microprocessors, a combination of a DSP and a microprocessor, etc.

Bus 804 may be an extended industry standard architecture (Extended Industry Standard Architecture, EISA) bus or the like. The bus 804 may be classified as an address bus, a data bus, a control bus, or the like. For ease of illustration, only one thick line is shown in fig. 8, but not only one bus or one type of bus.

From the foregoing description of the embodiments, it will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-described division of functional modules is illustrated, and in practical application, the above-described functional allocation may be implemented by different functional modules according to needs, i.e. the internal structure of the apparatus is divided into different functional modules to implement all or part of the functions described above. The specific working processes of the above-described systems, devices and units may refer to the corresponding processes in the foregoing method embodiments, which are not described herein.

The present application provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of determining SDR data in the method embodiments described above.

The embodiment of the application also provides a computer readable storage medium, wherein instructions are stored in the computer readable storage medium, and when the instructions run on a computer, the computer is caused to execute the method for determining the SDR data in the method flow shown in the method embodiment.

The computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples (a non-exhaustive list) of the computer-readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access Memory (Random Access Memory, RAM), a Read-Only Memory (ROM), an erasable programmable Read-Only Memory (Erasable Programmable Read Only Memory, EPROM), a register, a hard disk, an optical fiber, a portable compact disc Read-Only Memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing, or any other form of computer readable storage medium known in the art. An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an application specific integrated circuit (Application Specific Integrated Circuit, ASIC). In the context of the present application, a computer-readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

Since the determining apparatus, the computer-readable storage medium, and the computer program product of the SDR data in the embodiments of the present invention can be applied to the above-mentioned method, the technical effects that can be obtained by the method can also refer to the above-mentioned method embodiments, and the embodiments of the present invention are not described herein again.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods may be implemented in other ways. For example, the above-described device embodiments are merely illustrative, e.g., the partitioning of elements is merely a logical functional partitioning, and there may be additional partitioning in actual implementation, e.g., multiple elements or components may be combined or integrated into another system, or some features may be omitted, or not implemented. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be through some interface, indirect coupling or communication connection of devices or units, electrical, mechanical, or other form.

The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed over a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

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

The foregoing is merely a specific embodiment of the present application, but the protection scope of the present application is not limited thereto, and any changes or substitutions within the technical scope of the present disclosure should be covered in the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method for determining SDR data, comprising:

acquiring target call ticket data; the target call ticket data includes: signaling in a call relay process and user identification in the call relay process;

determining a target SDR session detailed record data table associated with the user identification in the call relay process; the target SDR session detailed record data table is used for storing call parameters in a target call flow, wherein the target call flow is a call flow to which the target call ticket data belongs, and the call parameters comprise at least one of signaling information and a call field;

Updating call parameters in the target SDR session detailed record data table according to signaling in the call relay process;

the determining the target SDR session detailed record data table associated with the user identification in the call relay process comprises the following steps:

determining whether the target call ticket data is call ticket data of a starting call;

if yes, establishing the target SDR session detailed record data table according to the user identification in the call relay process, and generating an association relation between the target SDR session detailed record data table and the user identification in the call relay process;

if not, determining a user dynamic table corresponding to the user identification in the call relay process; the user dynamic table comprises user identifications of different relay stages in the target call flow;

determining an SDR session detailed record data table associated with the user dynamic table as the target SDR session detailed record data table;

the establishing the target SDR session detailed record data table according to the user identification in the call relay process comprises the following steps:

determining the call type of the target call flow;

under the condition that the call type of the target call flow is a call initiated by a target operator, establishing a target SDR session detailed record data table according to a gateway office configuration table of the target operator;

Determining whether a calling record of the target call flow exists in a ticket record of a gateway of the international call under the condition that the call type of the target call flow is the international call;

if yes, establishing a detailed record data table of the target SDR session according to the calling record of the target call flow;

if not, establishing a detailed record data table of the target SDR session according to the calling record of the target call flow in the long distance office;

determining whether a call record of the target call flow exists in a local office under the condition that the call type of the target call flow is a local PSTN public switched telephone network call flow;

if yes, establishing the target SDR session detailed record data table according to the call record of the call flow in the local office;

if not, the local office is used as a call starting point to initiate a call to the local office, and the target SDR session detailed record data table is established according to the initiated call;

and under the condition that the call type of the target call flow is the call flow initiated by the local access network equipment, establishing the target SDR session detailed record data table according to the call ticket data of the interface of the local access network equipment.

2. The method according to claim 1, wherein the method further comprises:

determining the type of the network carrying the target call flow;

determining user identification of the target call flow in different call relay processes according to the type of the network;

and generating the user dynamic table according to the user identification of the call flow in different call relay processes.

3. The method according to claim 1 or 2, wherein said updating call parameters in said target SDR session detail record data table according to signaling in said call relay procedure, further comprises:

determining whether the target call ticket data is call ticket data for ending the call;

if yes, after updating the call parameters in the target SDR session detailed record data table according to the signaling in the call relay process, determining that the updating of the target SDR session detailed record data table is completed.

4. An apparatus for determining SDR data, said apparatus comprising: a processing unit and an acquisition unit;

the acquisition unit is used for acquiring the target call ticket data; the target call ticket data includes: signaling in a call relay process and user identification in the call relay process;

The processing unit is used for determining a target SDR session detailed record data table associated with the user identification in the call relay process; the target SDR session detailed record data table is used for storing call parameters in a target call flow, wherein the target call flow is a call flow to which the target call ticket data belongs, and the call parameters comprise at least one of signaling information and a call field;

the processing unit is used for updating the call parameters in the target SDR session detailed record data table according to the signaling in the call relay process;

the processing unit is specifically configured to: determining whether the target call ticket data is call ticket data of a starting call;

Determining the SDR data table associated with the user dynamic table as the target SDR session detailed record data table;

the processing unit is specifically configured to: determining the call type of the target call flow;

5. The apparatus according to claim 4, wherein the processing unit is specifically configured to: determining the type of the network carrying the target call flow;

6. The apparatus of claim 4 or 5, wherein the processing unit is further configured to: determining whether the target call ticket data is call ticket data for ending the call;

7. A device for determining SDR data, comprising: a processor and a communication interface; the communication interface being coupled to the processor for running a computer program or instructions to implement a method of determining SDR data as claimed in any of claims 1 to 3.

8. A computer readable storage medium having instructions stored therein, characterized in that when executed by a computer, the computer performs the method of determining SDR data of any of the preceding claims 1-3.