CN117098080A - Network type identification method, device, equipment, storage medium and program product - Google Patents

Abstract

The application discloses a network type identification method, a network type identification device, a network type identification equipment, a network type storage medium and a network type identification program product. The method comprises the following steps: sending a User Data Request (UDR) message of a calling user to a Unified Data Management (UDM) platform, wherein the UDM message comprises identification information of the calling user; receiving a user data response (UDA) message sent by the UDM platform based on the UDR message; and determining the type of the target network where the calling user is located according to the UDA information. According to the embodiment of the application, the network type of the calling user can be identified, so that the problem that the network type cannot be accurately identified in the prior art is solved.

Description

Network type identification method, device, equipment, storage medium and program product

Technical Field

The present application belongs to the field of communication technologies, and in particular, to a network type identification method, device, apparatus, storage medium, and program product.

Background

The caller number display service, i.e. caller number display service, is a basic function of the telephone network, and the wide use of caller number display service brings great convenience to users. With the continuous development of new technologies and the continuous opening of telecommunication markets, users participate in and perform customized services, and rapid development is achieved. However, some lawbreakers utilize vulnerabilities existing in network new technologies or gateway devices to artificially modify calling numbers into social public service numbers such as 110, operator customer service numbers such as 10086 or other user numbers, and perform illegal activities such as harassment, telephone fraud and the like on users. Therefore, effective measures are urgently needed to monitor calling numbers, so as to intercept false calling numbers.

Before intercepting the false calling number, the network type of the calling user needs to be determined, so that the network type identification of the calling user is very important, and an identification mode capable of accurately identifying the network type of the calling user is highly required.

Disclosure of Invention

The embodiment of the application provides a network type identification method, device, equipment, storage medium and program product, which can solve the problem that the network type of a user cannot be identified in the prior art.

In a first aspect, an embodiment of the present application provides a method for identifying a network type, where the method includes:

sending a User Data Request (UDR) message of a calling user to a Unified Data Management (UDM) platform, wherein the UDM message comprises identification information of the calling user;

receiving a user data response (UDA) message sent by the UDM platform based on the UDR message;

and determining the type of the target network where the calling user is located according to the UDA information.

In some embodiments, the determining the network type of the calling subscriber according to the UDA information includes at least one of:

under the condition that a session management function entity SMF host name exists in the UDA message, determining that the calling user is in a 5GC network;

Under the condition that a mobile management entity MME host name exists in the UDA message, determining that the calling user is in an EPC network;

and determining that the calling user is in a CS network under the condition that a mobile switching center MSC number exists in the UDA message.

In some embodiments, after said determining the network type of the calling subscriber from the UDA information, the method further comprises:

and determining whether the calling of the calling user is a false calling according to the virtual calling determination mode corresponding to the target network type.

In some embodiments, the determining, according to the virtual calling determination manner corresponding to the target network type, whether the calling of the calling subscriber is a false calling includes:

inquiring whether the calling user has a quality of service flow QOS flow with 5QI being 1 or not to an SMF through a capability open platform NEF under the condition that the calling user is in a 5GC network, and obtaining a first inquiry result;

determining whether the calling of the calling user is a false calling according to the first query result;

wherein, under the condition that the first query result is that the calling user has a QOS flow with 5QI of 1, determining that the calling of the calling user is not a false calling;

And under the condition that the first query result is that the calling party does not have a QOS stream with 5QI of 1, determining that the calling party of the calling party is a false calling party.

In some embodiments, the determining, according to the virtual calling determination manner corresponding to the target network type, whether the calling of the calling subscriber is a false calling includes:

inquiring whether the calling user has a bearing with the QCI of 1 or not from an MME under the condition that the calling user is in an EPC network, and obtaining a second inquiry result;

determining whether the calling of the calling user is a false calling according to the second query result;

wherein, when the second query result is that the calling user has a bearing with QCI of 1, determining that the calling of the calling user is not a false calling;

and under the condition that the second query result is that the calling user does not have the bearing with the QCI of 1, determining that the calling of the calling user is a false calling.

In some embodiments, the determining, according to the virtual calling determination manner corresponding to the target network type, whether the calling of the calling subscriber is a false calling further includes:

inquiring whether the calling user is in a busy state or not to an MSC through a home location register HLR under the condition that the calling user is in a CS network, and obtaining a third inquiring result;

Determining whether the calling of the calling user is a false calling according to the third query result;

wherein, when the third query result is that the calling party is in a busy state, determining that the calling party of the calling party is not a false calling party;

and under the condition that the third query result is that the calling party is not in a busy state, determining that the calling party of the calling party is not a false calling party.

In some embodiments, after determining whether the caller of the caller is a false caller according to the virtual caller determination manner corresponding to the target network type, the method further includes:

sending first indication information under the condition that the calling of the calling user is false calling, wherein the first indication information is used for indicating to release the calling;

and under the condition that the calling party of the calling party is not a false calling party, sending first indicating information, wherein the second indicating information is used for indicating the continuous calling party.

In a second aspect, an embodiment of the present application further provides a method for identifying a network type, where the method includes:

receiving a UDR message sent by a virtual calling platform, wherein the UDM message comprises identification information of the calling user;

Determining the network type of the calling user according to the UDR message;

generating a UDA message according to the network type of the calling user;

and sending the UDA message to the virtual calling platform.

In some embodiments, said determining the network type of the calling subscriber from said UDR message comprises:

determining whether the calling user has registered AMF information and SMF information according to the identification information of the calling user;

determining that the calling subscriber is in a 5GC network under the condition that the registered AMF information and SMF information exist in the calling subscriber;

under the condition that the calling user does not have the registered AMF information and SMF information, determining whether the IMS corresponding to the calling user is in a subscription registration state or not and whether the T-ADS supports a packet switched PS domain or not according to the identification information of the calling user;

under the condition that the IMS corresponding to the calling user is in a subscription registration state and the T-ADS supports a PS domain, determining that the calling user is in an EPC network;

and determining that the calling user is in a CS network under the condition that the IMS corresponding to the calling user is not in a subscription registration state or the T-ADS does not support a PS domain.

In a third aspect, an embodiment of the present application provides a network type identification apparatus, where the apparatus includes:

the system comprises a sending module, a Unified Data Management (UDM) platform and a receiving module, wherein the sending module is used for sending a User Data Request (UDR) message of a calling user to the UDM platform, and the UDM message comprises identification information of the calling user;

the receiving module is used for receiving a user data response (UDA) message sent by the UDM platform based on the UDR message;

and the determining module is used for determining the type of the target network where the calling user is located according to the UDA information.

In a fourth aspect, an embodiment of the present application provides a network type identification device, where the device includes: a processor and a memory storing computer program instructions;

the processor, when executing the computer program instructions, implements the network type identification method as described above.

In a fifth aspect, embodiments of the present application provide a computer storage medium having stored thereon computer program instructions which, when executed by a processor, implement a method for identifying a network type as above.

In a sixth aspect, embodiments of the present application provide a computer program product comprising computer program instructions which, when executed by a processor, implement a method of identifying a network type as above.

In the application, a virtual calling platform sends a User Data Request (UDR) message to a Unified Data Management (UDM) platform through a calling user according to a calling party; receiving a user data response (UDA) message fed back by the UDM platform; and determining the network type of the calling user according to the UDA information. In this way, the virtual calling platform can determine whether the calling party is in the 5GC network, the EPC network or the CS network, and identify whether the calling party is a false calling party or not in different modes according to different network types of the calling party, so that the accuracy of false calling identification is ensured.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the embodiments of the present application will be briefly described below, and it is obvious that the drawings described below are only some embodiments of the present application, and other drawings may be obtained according to these drawings without inventive effort to a person of ordinary skill in the art.

Fig. 1 is a flow chart of a network type identification method according to an embodiment of the present application;

fig. 2 is a flow chart of a network type identification method according to another embodiment of the present application;

Fig. 3 is a flow chart of a method for identifying a network type according to another embodiment of the present application;

fig. 4 is a flow chart of a network type identification method according to still another embodiment of the present application;

fig. 5 is a flowchart of a network type identification method according to still another embodiment of the present application;

fig. 6 is a flowchart of a network type identification method according to still another embodiment of the present application;

fig. 7 is a flowchart of a method for identifying a network type according to still another embodiment of the present application;

fig. 8 is a flowchart of a network type identification method according to still another embodiment of the present application;

fig. 9 is a schematic structural diagram of a network type identification device according to an embodiment of the present application;

fig. 10 is a flowchart of a method for identifying a network type according to still another embodiment of the present application;

fig. 11 is a schematic hardware structure of a network type identification device according to an embodiment of the present application;

fig. 12 is a schematic structural diagram of a network type identification device according to an embodiment of the present application.

Detailed Description

Features and exemplary embodiments of various aspects of the present application will be described in detail below, and in order to make the objects, technical solutions and advantages of the present application more apparent, the present application will be described in further detail below with reference to the accompanying drawings and the detailed embodiments. It should be understood that the particular embodiments described herein are meant to be illustrative of the application only and not limiting. It will be apparent to one skilled in the art that the present application may be practiced without some of these specific details. The following description of the embodiments is merely intended to provide a better understanding of the application by showing examples of the application.

It is noted that relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises an element.

It should be noted that, without conflict, the embodiments of the present application and features of the embodiments may be combined with each other. The embodiments will be described in detail below with reference to the accompanying drawings.

The caller number display service, i.e. caller number display service, is a basic function of the telephone network, and the wide use of caller number display service brings great convenience to users. With the continuous development of new technologies and the continuous opening of telecommunication markets, users participate in and perform customized services, and rapid development is achieved. However, some lawbreakers utilize vulnerabilities existing in network new technologies or gateway devices to artificially modify calling numbers into social public service numbers such as 110, operator customer service numbers such as 10086 or other user numbers, and perform illegal activities such as harassment, telephone fraud and the like on users. Therefore, effective measures are urgently needed to monitor calling numbers, so as to intercept false calling numbers.

In the related art, for the treatment of false calling, mainly only a network interception scheme is adopted: namely, in the process of a calling user initiating a call, a gateway is triggered to an SCP (service control node), and the SCP sends a user data request UDR message comprising identification information of the calling user to a home subscriber server HSS according to the calling user of the call; receiving user data response UDA message sent by HSS, wherein the UDA message includes information of IP multimedia subsystem IMS corresponding to calling user and information of terminating access domain selection T-ADS; if the IMS subscription and registration corresponding to the calling user are carried out, and the T-ADS supports the PS domain, the calling user is determined to be in the PS domain, the busy and idle state of the calling user is inquired to a Mobility Management Entity (MME), and if the busy and idle state of the calling user is idle, the calling user of the call is determined to be a false calling. Otherwise, determining that the calling user is in the CS domain, inquiring the busy and idle state of the calling user from the HLR, and determining that the calling user is a false calling if the busy and idle state of the calling user is idle.

However, the above method can only recognize that the caller is in the PS domain or the CS domain and detect whether the caller is a false caller in the PS domain or the CS domain. When the network type of the calling user is 5GC, the network type of the calling user cannot be identified, and whether the call of the calling user in the 5GC is a false calling cannot be detected.

Therefore, in the false caller identification process, it is important for the network type identification of the caller, and there is a need for an identification method capable of accurately identifying the network type of the caller.

Specifically, in order to solve the problems in the prior art, embodiments of the present application provide a network type identification method, apparatus, device, storage medium, and program product. The following first describes a network type identification method provided by an embodiment of the present application.

Fig. 1 is a flow chart illustrating a network type identification method according to an embodiment of the present application. The method is applied to a virtual calling platform and comprises the following steps of:

s110, sending a User Data Request (UDR) message of a calling user to a Unified Data Management (UDM) platform, wherein the UDM message comprises identification information of the calling user.

In this embodiment, a User Data request (User Data Request, UDR) message of the calling User may be sent to a Unified Data Management (UDM) platform by a false calling platform, where the UDR message includes identification information of the calling User, and the UDM platform may determine a network type where the calling User is located based on the received identification information of the calling User. Wherein the calling subscriber is a subscriber actively initiating a call.

S120, receiving a user data response UDA message sent by the UDM platform based on the UDR message.

In this embodiment, after determining the network type of the calling User based on the received identification information of the calling User, the UDM platform generates a User Data Answer (UDA) message that matches the network type of the calling User, and sends the UDA message back to the false calling platform. In this way, the virtual calling platform can determine the network type in which the calling subscriber is located based on the received UDA message.

S130, determining the type of the target network where the calling user is located according to the UDA information.

In this embodiment, after the false calling platform receives the UDA message, the network type of the calling user may be determined according to the content in the UDA message. In some embodiments, the network types include a 5G core 5GC network, a 4G core EPC network, and a circuit switched CS network. If the UDA message includes a session management function entity (Session Management Function, SMF) hostname for the caller registration, then it may be determined that the network type of the caller is a 5G core 5GC network; if the hostname of the mobility management entity (Mobility Management Entity, MME) is included in the UDA message, then it may be determined that the network type of the calling subscriber is a 4G core EPC network; if the UDA message includes a mobile switching center (Mobile Switching Center, MSC) number, then the network type of the calling subscriber can be determined to be a circuit switched CS network.

In the application, the virtual calling platform sends a UDR message to the UDM platform according to a calling user and receives a UDA message fed back by the UDM platform; and determining the network type of the calling user according to the UDA information. In this way, the virtual calling platform can determine whether the calling subscriber is in the 5GC network, the EPC network or the CS network, thereby accurately identifying the network type of the calling subscriber.

As an alternative embodiment, referring to fig. 2, in order to accurately determine the network type of the calling subscriber, S130 includes at least one of the following:

s210, under the condition that a session management function entity SMF host name exists in the UDA message, determining that the calling user is in a 5GC network;

s220, under the condition that a mobile management entity MME host name exists in the UDA message, determining that the calling user is in an EPC network;

s230, determining that the calling user is in a CS network under the condition that a mobile switching center MSC number exists in the UDA message.

In this embodiment, when the network types of the calling subscribers are different, the UDA messages generated by the UDM platform are different, and the virtual calling platform can determine the network state of the calling subscriber according to the differences of the UDA messages. If the UDA message carries the SMF host name registered by the calling user, the calling user can be determined to be in a 5GC state; if the UDA message carries the MSC number, then the calling user can be determined to be in the CS network state; if the UDA message carries an MME hostname, then it can be determined that the calling subscriber is in the EPC network state.

As an alternative embodiment, referring to fig. 3, in order to identify the authenticity of the caller, after S130, the method may further include:

s310, determining whether the calling of the calling user is a false calling according to the virtual calling determination mode corresponding to the target network type.

In this embodiment, the determination manners for determining whether the caller is a false caller may be different when the caller is in different network types, for example, the determination manners for determining whether the caller is a virtual caller may be different when the caller is in a CS network, EPC network, and 5GC network states.

As an alternative embodiment, referring to fig. 4, in order to identify the authenticity of the caller in the 5GC network state, S310 may include:

s410, inquiring whether the calling user has a quality of service flow QOS flow with a 5QI of 1 or not to an SMF through a capability open platform NEF under the condition that the calling user is in a 5GC network, and obtaining a first inquiry result;

s420, determining whether the calling of the calling user is a false calling or not according to the first query result;

s430, determining that the calling party is not a false calling party when the first query result is that the calling party has a QOS stream with 5QI of 1;

S440, determining that the calling party is false calling when the first query result is that the calling party does not have the QOS flow with the 5QI of 1.

In this embodiment, the NEF may query the SMF for QOS flows of the calling subscriber, obtain a first query result, and determine, according to the first query result, whether the calling subscriber performs a voice call in the 5GC network. If the calling user performs voice call in the 5GC network, the calling user is not false calling; if the caller is not engaged in a voice call in the 5GC network, this means that the caller of the caller is a false caller.

In some embodiments, if the first query result is that the calling party has a QOS flow with 5QI of 1, it means that the calling party in the 5GC network has a media bearer, further means that the calling party is in a voice call in the 5GC network, so it may be determined that the calling party of the calling party is not a false calling party, otherwise, the calling party of the calling party may be considered as a false calling party.

As an alternative embodiment, referring to fig. 5, in order to identify the authenticity of the caller in the EPC network state, S310 may include:

S510, inquiring whether the calling user has a bearing with QCI of 1 to an MME (mobility management entity) under the condition that the calling user is in an EPC (evolved packet core) network, and obtaining a second inquiring result;

s520, determining whether the calling of the calling user is a false calling or not according to the second query result;

s530, determining that the calling party is not a false calling party when the second query result indicates that the calling party has a bearing with QCI of 1;

s540, determining that the calling party is a false calling party when the second query result is that the calling party does not have the bearing with the QCI of 1.

In this embodiment, whether the calling user has the bearer with QCI of 1 may be queried from the MME to obtain a second query result, and whether the calling user performs voice call in the EPC network may be determined according to the second query result. If the calling party performs voice call in the EPC network, the calling party is not false calling; if the caller is not engaged in a voice call in the EPC network, this means that the caller of the caller is a false caller.

In some embodiments, if the second query result is that the caller has a bearer with QCI of 1, this means that the caller is engaged in a voice call in the EPC network, so it may be determined that the caller of the caller is not a false caller, otherwise the caller of the caller may be considered as a false caller.

As an alternative embodiment, referring to fig. 6, in order to identify the authenticity of the caller in the CS network state, S310 may further include:

s610, inquiring whether the calling user is in a busy state or not to an MSC through a home location register HLR under the condition that the calling user is in a CS network, and obtaining a third inquiring result;

s620, determining whether the calling of the calling user is a false calling or not according to the third query result;

s630, wherein if the third query result is that the calling party is in a busy state, the calling party of the calling party is determined not to be a false calling party;

and S640, determining that the calling party is not a false calling party under the condition that the third query result is that the calling party is not in a busy state.

In this embodiment, the HLR may query the MSC for the status of the calling subscriber, obtain a third query result, and determine, according to the third query result, whether the calling subscriber performs a voice call in the CS network. If the calling user performs voice call in the CS network, the calling of the calling user is not false calling; if the calling party does not make a voice call in the CS network, this means that the calling party of the calling party is a false calling party.

In some embodiments, if the third query result is that the status of the calling party is busy, this means that the calling party is engaged in a voice call in the CS network, so it may be determined that the calling party is not a false calling party, otherwise the calling party may be considered as a false calling party.

As an alternative embodiment, referring to fig. 7, in order to ensure that the call is normal, after S310, the method may further include:

s710, in the case that the calling party of the calling party is a false calling party, sending first indication information, wherein the first indication information is used for indicating to release the calling party;

and S720, sending first indication information for indicating the continued calling party under the condition that the calling party of the calling party is not the false calling party.

In this embodiment, in order to ensure that when the caller of the caller is not a false caller, the caller request can be normally issued; and when the caller of the calling user is a false caller, releasing the caller request. If the false calling platform determines that the calling party of the calling party is the false calling party, sending first indication information to inform a gateway to release the calling party; if the false calling platform determines that the calling party of the calling party is not the false calling party, the false calling platform sends second indication information to inform the gateway to continue the calling party.

Fig. 8 is a flow chart illustrating a network type identification method according to an embodiment of the present application. The method is applied to the UDM platform and comprises the following steps:

s810, receiving UDR information sent by a virtual calling platform;

s820, determining the network type of the calling user according to the UDR message;

s830, generating a UDA message according to the network type of the calling user;

and S840, the UDA message is sent to the virtual calling platform.

In this embodiment, the UDM platform is communicatively connected to the false calling platform, and after receiving the UDR message sent by the false calling platform, the UDM platform determines the network type of the calling user according to the identification information of the calling user in the UDR message. After the network type of the calling user is determined, different UDA messages are generated according to the different network types of the calling user, and the UDA messages are fed back to the virtual calling platform, so that the virtual calling platform determines the network type of the calling user according to the received UDA messages.

In one embodiment, the connection between the local gateway and the false calling platform is shown in fig. 9, the false calling platform is in communication connection with the local gateway, the local gateway is connected to an off-network incoming call, the false calling platform is in communication connection with UDM, NEF, MME, HLR, the NEF is further in communication connection with the SMF, and the HLR is in communication connection with the MSC.

As an alternative embodiment, referring to fig. 10, in order to determine the network type of the calling subscriber through the UDR message, S820 may further include:

s101, determining whether the calling user has registered AMF information and SMF information according to the identification information of the calling user;

s102, determining that the calling user is in a 5GC network under the condition that the registered AMF information and SMF information exist in the calling user;

s103, under the condition that the calling user does not have the registered AMF information and SMF information, determining whether the IMS corresponding to the calling user is in a subscription registration state or not and whether T-ADS supports a packet switched PS domain or not according to the identification information of the calling user;

s104, determining that the calling user is in an EPC network under the condition that the IMS corresponding to the calling user is in a subscription registration state and the T-ADS supports a PS domain;

s105, determining that the calling user is in a CS network under the condition that the IMS corresponding to the calling user is not in a subscription registration state or the T-ADS does not support a PS domain.

In this embodiment, the UDM platform may determine the network type of the calling subscriber from the identification information contained in the received UDR message. In an embodiment, the UDM platform may first determine whether the calling subscriber has the registered AMF information and SMF information according to the identification information in the UDR message, if the calling subscriber has the AMF information and SMF information, it may determine that the calling subscriber is in the 5GC network, if the calling subscriber does not have the AMF information and SMF information, it may further determine the network type of the calling subscriber, that is, query whether the IMS corresponding to the calling subscriber is in a subscription registration state according to the identification information in the UDR message, and query whether the T-ADS supports the PS domain; if the IMS corresponding to the calling subscriber is in a subscription registration state and the T-ADS supports a PS domain, determining that the calling subscriber is in an EPC network; if it appears that the IMS to which the calling subscriber corresponds is not registered for subscription, or that the T-ADS does not support any of the PS domains, then it may be determined that the calling subscriber is in the CS network.

Based on the network type identification method provided by the embodiment, correspondingly, the application further provides a specific implementation mode of the network type identification device. Please refer to the following examples.

Referring first to fig. 11, a network type identification device 110 provided in an embodiment of the present application includes the following modules:

a sending module 111, configured to send a user data request UDR message of a calling user to a unified data management UDM platform, where the UDM message includes identification information of the calling user;

a receiving module 112, configured to receive a user data response UDA message sent by the UDM platform based on a UDR message;

and the determining module 113 is used for determining the type of the target network where the calling user is located according to the UDA information.

The device may send a user data request UDR message to the unified data management UDM platform by a caller according to the caller; receiving a user data response (UDA) message fed back by the UDM platform; and determining the network type of the calling user according to the UDA information, and determining whether the calling of the calling user is a false calling according to a virtual calling determination mode corresponding to the target network type. In this way, the virtual calling platform can determine whether the calling party is in the 5GC network, the EPC network or the CS network, and identify whether the calling party is a false calling party or not in different modes according to different network types of the calling party, so that the accuracy of false calling identification is ensured.

As an implementation manner of the present application, in order to accurately determine the network type of the calling subscriber, the determining module 113 may further include:

a first determining unit, configured to determine that the calling subscriber is in a 5GC network when a session management function entity SMF hostname exists in the UDA message;

a second determining unit, configured to determine that the calling subscriber is in an EPC network when a mobile management entity MME host name exists in the UDA message;

and a third determining unit, configured to determine that the calling subscriber is in a CS network when a mobile switching center MSC number exists in the UDA message.

As an implementation manner of the present application, in order to identify the authenticity of the caller, the determining module 113 may further include:

and the false calling determination unit is used for determining whether the calling of the calling user is a false calling according to the virtual calling determination mode corresponding to the target network type.

As an implementation manner of the present application, in order to identify the authenticity of the caller in the 5GC network state, the false caller determining unit may further include:

the first query unit is used for querying whether the calling user has a quality of service (QOS) flow with a quality of service (QI) of 1 or not to the SMF through the capability open platform NEF under the condition that the calling user is in a 5GC network, so as to obtain a first query result;

And the first analysis unit is used for determining whether the calling party of the calling party is a false calling party according to the first query result, wherein the calling party of the calling party is determined not to be the false calling party under the condition that the first query result is that the calling party has a QOS flow with the 5QI of 1, and the calling party of the calling party is determined to be the false calling party under the condition that the first query result is that the calling party does not have the QOS flow with the 5QI of 1.

As an implementation manner of the present application, in order to identify the authenticity of the caller in the EPC network state, the false caller determining unit may further include:

a second query unit, configured to query, when the calling subscriber is in an EPC network, whether the calling subscriber has a bearer with a QCI of 1, to an MME, to obtain a second query result;

and the second analysis unit is used for determining whether the calling party of the calling party is a false calling according to the second query result, wherein the calling party of the calling party is determined not to be the false calling when the second query result is that the calling party has the bearer with the QCI of 1, and the calling party of the calling party is determined to be the false calling when the second query result is that the calling party does not have the bearer with the QCI of 1.

As an implementation manner of the present application, in order to identify the authenticity of the caller in the CS network state, the false caller determining unit may further include:

a third query unit, configured to query, through a home location register HLR, whether the calling subscriber is busy, to an MSC, to obtain a third query result when the calling subscriber is in a CS network;

and the third analysis unit is used for determining whether the calling party of the calling party is a false calling according to the third query result, wherein the calling party of the calling party is determined not to be the false calling when the third query result is that the calling party is in a busy state, and the calling party of the calling party is determined not to be the false calling when the third query result is that the calling party is not in a busy state.

As an implementation manner of the present application, in order to identify the authenticity of the caller in the CS network state, the false caller determining unit may further include:

the first sending unit is used for sending first indication information when the calling party of the calling party is a false calling party, wherein the first indication information is used for indicating to release the calling party;

And the second sending unit is used for sending the first indicating information when the calling party of the calling party is not a false calling party, and the second indicating information is used for indicating the continuous calling party.

As an implementation manner of the present application, the network type identification device 700 may further include:

the UDR receiving module is used for receiving the UDR message sent by the virtual calling platform;

the type determining module is used for determining the network type of the calling user according to the UDR message;

the generating module is used for generating a UDA message according to the network type of the calling user;

and the feedback module is used for sending the UDA message to the virtual calling platform.

The network type identification device provided in the embodiment of the present application can implement each step in the method embodiments of fig. 1 to 8, and in order to avoid repetition, a description is omitted here.

Fig. 12 is a schematic hardware structure diagram of a network type identification device according to an embodiment of the present application.

The identification device at the network type may comprise a processor 1001 and a memory 1002 storing computer program instructions.

In particular, the processor 1001 described above may include a Central Processing Unit (CPU), or an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), or may be configured as one or more integrated circuits that implement embodiments of the present application.

Memory 1002 may include mass storage for data or instructions. By way of example, and not limitation, memory 1002 may include a Hard Disk Drive (HDD), floppy Disk Drive, flash memory, optical Disk, magneto-optical Disk, magnetic tape, or universal serial bus (Universal Serial Bus, USB) Drive, or a combination of two or more of the foregoing. The memory 1002 may include removable or non-removable (or fixed) media, where appropriate. Memory 1002 may be internal or external to the integrated gateway disaster recovery device, where appropriate. In a particular embodiment, the memory 1002 is a non-volatile solid state memory.

The memory may include Read Only Memory (ROM), random Access Memory (RAM), magnetic disk storage media devices, optical storage media devices, flash memory devices, electrical, optical, or other physical/tangible memory storage devices. Thus, in general, the memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software comprising computer-executable instructions and when the software is executed (e.g., by one or more processors) it is operable to perform the operations described with reference to methods in accordance with aspects of the present disclosure.

The processor 1001 reads and executes the computer program instructions stored in the memory 1002 to implement the network type identification method of any one of the above embodiments.

In one example, the network type identification device may also include a communication interface 1003 and a bus 1010. As shown in fig. 10, the processor 1001, the memory 1002, and the communication interface 1003 are connected to each other by a bus 1010, and perform communication with each other.

The communication interface 1003 is mainly used for implementing communication among the modules, devices, units and/or apparatuses in the embodiment of the application.

Bus 1010 includes hardware, software, or both that couple components of the network type identification device to each other. By way of example, and not limitation, the buses may include an Accelerated Graphics Port (AGP) or other graphics bus, an Enhanced Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), a HyperTransport (HT) interconnect, an Industry Standard Architecture (ISA) bus, an infiniband interconnect, a Low Pin Count (LPC) bus, a memory bus, a micro channel architecture (MCa) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCI-X) bus, a Serial Advanced Technology Attachment (SATA) bus, a video electronics standards association local (VLB) bus, or other suitable bus, or a combination of two or more of the above. Bus 1010 may include one or more buses, where appropriate. Although embodiments of the application have been described and illustrated with respect to a particular bus, the application contemplates any suitable bus or interconnect.

The network type identification device may be based on the above-described embodiments, thereby implementing the network type identification method and apparatus described in connection with fig. 1 to 10.

In addition, in combination with the network type identification method in the above embodiment, the embodiment of the present application may be implemented by providing a computer storage medium. The computer storage medium has stored thereon computer program instructions; the computer program instructions, when executed by the processor, implement the method for identifying a network type according to any one of the above embodiments, and achieve the same technical effects, so that repetition is avoided, and no further description is given here. The computer readable storage medium may include a non-transitory computer readable storage medium, such as Read-Only Memory (ROM), random access Memory (Random Access Memory, RAM), magnetic disk or optical disk, and the like, but is not limited thereto.

In addition, the embodiment of the application also provides a computer program product, which comprises computer program instructions, wherein the computer program instructions can realize the steps and corresponding contents of the embodiment of the method when being executed by a processor.

It should be understood that the application is not limited to the particular arrangements and instrumentality described above and shown in the drawings. For the sake of brevity, a detailed description of known methods is omitted here. In the above embodiments, several specific steps are described and shown as examples. However, the method processes of the present application are not limited to the specific steps described and shown, and those skilled in the art can make various changes, modifications and additions, or change the order between steps, after appreciating the spirit of the present application.

The functional blocks shown in the above block diagrams may be implemented in hardware, software, firmware, or a combination thereof. When implemented in hardware, it may be, for example, an electronic circuit, an Application Specific Integrated Circuit (ASIC), suitable firmware, a plug-in, a function card, or the like. When implemented in software, the elements of the application are the programs or code segments used to perform the required tasks. The program or code segments may be stored in a machine readable medium or transmitted over transmission media or communication links by a data signal carried in a carrier wave. A "machine-readable medium" may include any medium that can store or transfer information. Examples of machine-readable media include electronic circuitry, semiconductor memory devices, ROM, flash memory, erasable ROM (EROM), floppy disks, CD-ROMs, optical disks, hard disks, fiber optic media, radio Frequency (RF) links, and the like. The code segments may be downloaded via computer networks such as the internet, intranets, etc.

It should also be noted that the exemplary embodiments mentioned in this disclosure describe some methods or systems based on a series of steps or devices. However, the present application is not limited to the order of the above-described steps, that is, the steps may be performed in the order mentioned in the embodiments, or may be performed in a different order from the order in the embodiments, or several steps may be performed simultaneously.

Aspects of the present disclosure are described above with reference to flowchart illustrations and/or block diagrams of methods, apparatus and computer program products according to embodiments of the disclosure. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, enable the implementation of the functions/acts specified in the flowchart and/or block diagram block or blocks. Such a processor may be, but is not limited to being, a general purpose processor, a special purpose processor, an application specific processor, or a field programmable logic circuit. It will also be understood that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware which performs the specified functions or acts, or combinations of special purpose hardware and computer instructions.

In the foregoing, only the specific embodiments of the present application are described, and it will be clearly understood by those skilled in the art that, for convenience and brevity of description, the specific working processes of the systems, modules and units described above may refer to the corresponding processes in the foregoing method embodiments, which are not repeated herein. It should be understood that the scope of the present application is not limited thereto, and any equivalent modifications or substitutions can be easily made by those skilled in the art within the technical scope of the present application, and they should be included in the scope of the present application.

Claims (13)

1. A method for identifying a network type, the method being applied to a virtual calling platform, the method comprising:

sending a User Data Request (UDR) message of a calling user to a Unified Data Management (UDM) platform, wherein the UDM message comprises identification information of the calling user;

receiving a user data response (UDA) message sent by the UDM platform based on the UDR message;

and determining the type of the target network where the calling user is located according to the UDA information.

2. The method for identifying a network type according to claim 1, wherein said determining a network type of the calling subscriber from the UDA information comprises at least one of:

under the condition that a session management function entity SMF host name exists in the UDA message, determining that the calling user is in a 5GC network;

under the condition that a mobile management entity MME host name exists in the UDA message, determining that the calling user is in an EPC network;

and determining that the calling user is in a CS network under the condition that a mobile switching center MSC number exists in the UDA message.

3. The method for identifying a network type according to claim 1, wherein after said determining the network type of the calling subscriber based on the UDA information, the method further comprises:

And determining whether the calling of the calling user is a false calling according to the virtual calling determination mode corresponding to the target network type.

4. The method for identifying a network type according to claim 3, wherein the determining whether the caller of the caller is a false caller according to the virtual caller determination method corresponding to the target network type includes:

inquiring whether the calling user has a quality of service flow QOS flow with 5QI being 1 or not to an SMF through a capability open platform NEF under the condition that the calling user is in a 5GC network, and obtaining a first inquiry result;

determining whether the calling of the calling user is a false calling according to the first query result;

wherein, under the condition that the first query result is that the calling user has a QOS flow with 5QI of 1, determining that the calling of the calling user is not a false calling;

and under the condition that the first query result is that the calling party does not have a QOS stream with 5QI of 1, determining that the calling party of the calling party is a false calling party.

5. The method for identifying a network type according to claim 3, wherein the determining whether the caller of the caller is a false caller according to the virtual caller determination method corresponding to the target network type includes:

Inquiring whether the calling user has a bearing with the QCI of 1 or not from an MME under the condition that the calling user is in an EPC network, and obtaining a second inquiry result;

determining whether the calling of the calling user is a false calling according to the second query result;

wherein, when the second query result is that the calling user has a bearing with QCI of 1, determining that the calling of the calling user is not a false calling;

and under the condition that the second query result is that the calling user does not have the bearing with the QCI of 1, determining that the calling of the calling user is a false calling.

6. The method for identifying a network type according to claim 3, wherein the determining whether the caller of the caller is a false caller according to the virtual caller determining manner corresponding to the target network type further comprises:

inquiring whether the calling user is in a busy state or not to an MSC through a home location register HLR under the condition that the calling user is in a CS network, and obtaining a third inquiring result;

determining whether the calling of the calling user is a false calling according to the third query result;

wherein, when the third query result is that the calling party is in a busy state, determining that the calling party of the calling party is not a false calling party;

And under the condition that the third query result is that the calling party is not in a busy state, determining that the calling party of the calling party is not a false calling party.

7. The method for identifying a network type according to claim 3, wherein after determining whether the caller of the caller is a false caller according to the virtual caller determination method corresponding to the target network type, the method further comprises:

sending first indication information under the condition that the calling of the calling user is false calling, wherein the first indication information is used for indicating to release the calling;

and under the condition that the calling party of the calling party is not a false calling party, sending first indicating information, wherein the second indicating information is used for indicating the continuous calling party.

8. A method for identifying a network type, the method being applied to a UDM platform, the method comprising:

receiving a UDR message sent by a virtual calling platform, wherein the UDM message comprises identification information of the calling user;

determining the network type of the calling user according to the UDR message;

generating a UDA message according to the network type of the calling user;

and sending the UDA message to the virtual calling platform.

9. The method for identifying a network type according to claim 8, wherein said determining a network type of a calling subscriber from said UDR message comprises:

determining whether the calling user has registered AMF information and SMF information according to the identification information of the calling user;

determining that the calling subscriber is in a 5GC network under the condition that the registered AMF information and SMF information exist in the calling subscriber;

under the condition that the calling user does not have the registered AMF information and SMF information, determining whether the IMS corresponding to the calling user is in a subscription registration state or not and whether the T-ADS supports a packet switched PS domain or not according to the identification information of the calling user;

under the condition that the IMS corresponding to the calling user is in a subscription registration state and the T-ADS supports a PS domain, determining that the calling user is in an EPC network;

and determining that the calling user is in a CS network under the condition that the IMS corresponding to the calling user is not in a subscription registration state or the T-ADS does not support a PS domain.

10. A network type identification device, the device comprising:

The system comprises a sending module, a Unified Data Management (UDM) platform and a receiving module, wherein the sending module is used for sending a User Data Request (UDR) message of a calling user to the UDM platform, and the UDM message comprises identification information of the calling user;

the receiving module is used for receiving a user data response (UDA) message sent by the UDM platform based on the UDR message;

and the determining module is used for determining the type of the target network where the calling user is located according to the UDA information.

11. A network type identification device, characterized in that the network type identification device comprises: a processor and a memory storing computer program instructions;

the processor, when executing the computer program instructions, implements the network type identification method according to any one of claims 1-9.

12. A computer storage medium having stored thereon computer program instructions which, when executed by a processor, implement the network type identification method of any of claims 1-9.

13. A computer program product, characterized in that it comprises computer program instructions which, when executed by a processor, implement the network type identification method of any one of claims 1-9.