CN115550896A - Calling method, device and storage medium - Google Patents
Calling method, device and storage medium Download PDFInfo
- Publication number
- CN115550896A CN115550896A CN202110734101.1A CN202110734101A CN115550896A CN 115550896 A CN115550896 A CN 115550896A CN 202110734101 A CN202110734101 A CN 202110734101A CN 115550896 A CN115550896 A CN 115550896A
- Authority
- CN
- China
- Prior art keywords
- eir
- calling
- request
- call
- state
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 78
- 238000007689 inspection Methods 0.000 claims abstract description 61
- 238000001514 detection method Methods 0.000 claims abstract description 28
- 238000012545 processing Methods 0.000 claims abstract description 14
- 206010048669 Terminal state Diseases 0.000 claims description 20
- 230000008569 process Effects 0.000 claims description 19
- 230000002159 abnormal effect Effects 0.000 claims description 16
- 230000001960 triggered effect Effects 0.000 claims description 16
- 238000004891 communication Methods 0.000 claims description 11
- 229920000767 polyaniline Polymers 0.000 claims description 11
- 230000006855 networking Effects 0.000 abstract description 15
- 238000012795 verification Methods 0.000 description 8
- 230000004044 response Effects 0.000 description 7
- 230000001360 synchronised effect Effects 0.000 description 6
- 238000000605 extraction Methods 0.000 description 4
- 238000007726 management method Methods 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 3
- 230000006870 function Effects 0.000 description 3
- 238000013475 authorization Methods 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 238000010295 mobile communication Methods 0.000 description 2
- 238000012360 testing method Methods 0.000 description 2
- 230000009471 action Effects 0.000 description 1
- 238000013459 approach Methods 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000012508 change request Methods 0.000 description 1
- 238000011156 evaluation Methods 0.000 description 1
- 239000000284 extract Substances 0.000 description 1
- 230000004927 fusion Effects 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 230000002452 interceptive effect Effects 0.000 description 1
- 230000007774 longterm Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000002265 prevention Effects 0.000 description 1
- 230000007723 transport mechanism Effects 0.000 description 1
- 238000013022 venting Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/10—Architectures or entities
- H04L65/1016—IP multimedia subsystem [IMS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/80—Responding to QoS
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/06—Authentication
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/60—Context-dependent security
- H04W12/69—Identity-dependent
- H04W12/71—Hardware identity
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/60—Context-dependent security
- H04W12/69—Identity-dependent
- H04W12/72—Subscriber identity
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/60—Context-dependent security
- H04W12/69—Identity-dependent
- H04W12/75—Temporary identity
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/90—Services for handling of emergency or hazardous situations, e.g. earthquake and tsunami warning systems [ETWS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
- H04W60/06—De-registration or detaching
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Multimedia (AREA)
- Business, Economics & Management (AREA)
- Health & Medical Sciences (AREA)
- Emergency Management (AREA)
- Environmental & Geological Engineering (AREA)
- Public Health (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
The invention provides a calling method used for CSCF, comprising: receiving an initial Invite request; determining mobile terminal identification information carried in the initial Invite request; sending an EIR state inspection request to an EIR, wherein the EIR state inspection request carries the identification information of the mobile terminal; receiving an EIR state inspection result; and executing corresponding operation related to the call according to a preset strategy according to the EIR state checking result. The invention provides a calling method for EIR, comprising the following steps: receiving an EIR state inspection request sent by CSCF; according to a preset inspection rule, acquiring an EIR state inspection result of the identification information of the mobile terminal; the EIR status check result is sent to the CSCF. The invention solves the problem that the mobile terminal is stolen by detecting the state of the mobile terminal through the EIR, can realize normal calling without interference and time delay increase in an asynchronous processing mode, and realizes networking flexibility by decoupling the service network element and the detection device. The invention also provides equipment and a storage medium for realizing the method.
Description
Technical Field
The present invention relates to the field of mobile communications, and in particular, to a calling method, device and storage medium.
Background
The IP Multimedia Subsystem (IMS) is defined by the third Generation Partnership Project (3 gpp), and it is intended to provide conventional circuit-switched services (e.g. voice, messaging services) in the form of IP and to implement all Multimedia services provided to users via this Subsystem. Through the development of recent 20 years, IMS has been widely applied to Voice over Long-Term Evolution (VoLTE), voice over Wireless Fidelity (VoWiFi) and soft switch replacement, and has become the only international standard technology for New Voice over Radio (VoNR) and 5G fusion messages with the booming development of the fifth generation mobile communication system (5G).
With the wide commercial use of VoLTE and VoWiFi, some safety use problems arise in practical applications. In an original Mobile Switching Center (MSC) and a Packet Switching domain (PS) network, an EIR (Equipment Identity Register) is used to implement legal authentication on a Mobile device, mainly a Mobile phone, and access control on an illegal Mobile phone (stolen) or a Mobile device without model authentication can be implemented. The EIR checks the International Mobile Equipment Identity (IMEI) of the Mobile phone to prevent the Mobile phone from being stolen, thereby ensuring the security of the system. In the mobile network, the MSC and the Mobility Management Entity (MME) send the IMEI information of the device to the EIR device, the EIR device compares the received IMEI with the white, black, and gray lists, and sends the result to the MSC and the MME, so that the MSC and the MME determine whether to allow the mobile station device to enter the network.
Disclosure of Invention
The present disclosure provides a calling method, apparatus, and storage medium.
In a first aspect, the present disclosure provides a call method for a CSCF, including:
receiving an initial Invite request;
determining the mobile terminal identification information carried in the initial Invite request;
sending an EIR status check request to an equipment identification register EIR, wherein the EIR status check request carries the identification information of the mobile terminal;
receiving an EIR status check result, wherein the EIR makes the EIR status check result according to the EIR status check request;
and executing corresponding operation related to the call according to a preset strategy according to the EIR state inspection result.
Optionally, the step of sending an EIR status check request to the EIR is performed before the initial filter rule iFC of the caller is triggered.
Optionally, the preset policy includes a first preset rule, and the calling method further includes:
after the iFC detection of a calling party is triggered, triggering a calling flow for a calling request meeting the iFC detection;
and after receiving the EIR state detection result, processing the occurred call flow according to the first preset rule.
Further, the processing of the call flow that has occurred according to the first preset rule includes:
if the EIR state inspection result is that the terminal state is abnormal, sending a call forbidding instruction to the terminal to terminate the occurred call flow;
and if the EIR state inspection result is abnormal in the non-terminal state, maintaining the call flow.
Further, the terminal state exception includes:
the EIR state inspection result is inspection failure, and/or a result code in the EIR state inspection result is blacklist matching.
Optionally, the preset policy includes a second preset rule, and the calling method further includes:
and after receiving the EIR state detection result, carrying out call request iFC triggering operation according to a second preset rule.
Further, the second preset rule includes:
if the EIR state inspection result is that the terminal state is abnormal, a Forbidden message is sent to the terminal sending the initial Invite request;
and if the EIR state inspection result is abnormal in a non-terminal state, triggering the initial Invite call request iFC and putting through a call.
Further, the terminal state exception includes:
the EIR state inspection result is inspection failure, and/or a result code in the EIR state inspection result is blacklist matching.
Optionally, the mobile terminal identification information includes at least one of the following information:
the international mobile equipment identity IMEI, the international mobile subscriber identity IMSI, the public user identity PUI and the like of the mobile terminal.
Optionally, the calling method includes:
setting an EIR status check mark;
if the EIR state inspection flag is set to be negative, triggering a call flow by the iFC of the calling party after receiving the initial Invite request;
if the EIR status check flag is set to be yes, after the initial Invite request is received and before the iFC of the calling party is triggered, the EIR status check request is sent to the EIR, and corresponding operation related to the call is executed according to the EIR status check result and a preset strategy.
Further, the calling method further includes at least one of the following steps:
when the called number is a special service number, triggering a calling process;
when the mobile terminal is accessed in a non-VoLTE mode or a non-VoWiFi mode, a call flow is triggered;
and triggering a calling process when neither the calling request nor the registration information of the mobile terminal carries access network information PANI.
Optionally, the EIR status check request is sent to a routing agent node DRA, and the DRA forwards the EIR status check request to the EIR.
In a second aspect, the present disclosure provides a calling method for EIR, including:
receiving the EIR state inspection request sent by the CSCF, wherein the EIR state inspection request comprises the identification information of the mobile terminal;
according to a preset inspection rule, acquiring an EIR state inspection result of the mobile terminal identification information;
and sending the EIR state inspection result to the CSCF.
Further, the obtaining an EIR status check result of the mobile terminal identification information according to a preset check rule includes:
and checking the international mobile equipment identity IMEI, the international mobile subscriber identity IMSI and the public user identity PUI of the mobile terminal, and generating the EIR state checking result.
In a third aspect, the present disclosure provides a CSCF device comprising a memory, a processor, a program stored on the memory and executable on the processor, and a data bus for enabling a connection communication between the processor and the memory, the program, when executed by the processor, implementing the steps of the call method according to the first aspect.
In a fourth aspect, the present disclosure provides an EIR apparatus comprising a memory, a processor, a program stored on the memory and executable on the processor, and a data bus for enabling connection communication between the processor and the memory, the program, when executed by the processor, implementing the steps of the calling method according to the first aspect.
In a fifth aspect, the present disclosure provides a storage medium for computer readable storage, the storage medium storing one or more programs, the one or more programs being executable by one or more processors to implement the steps of the calling method as described in the first or second aspect.
The calling method provided by the disclosure solves the problems of terminal loss and call theft prevention after the terminal is stolen in the voice core network IMS in the 4G, 5G and WiFi access networks of the 3GPP, and detects the use state of the mobile terminal based on the IMS call when the call is initiated so as to ensure that the reported mobile terminal is not used by an illegal holder; realizing the linkage identification of the terminal, the card and the user; the asynchronous processing of the normal call and EIR inspection flow of the mobile terminal does not interfere the normal call and does not increase the time delay; ensuring the priority put-through of the emergency call; the service network element and the detection device are decoupled, so that the networking flexibility is kept.
Drawings
Fig. 1 is a flowchart of a call method for CSCF according to an embodiment of the present disclosure.
Fig. 2 is a flowchart of a calling method for EIR according to an embodiment of the disclosure.
Fig. 3 is a network architecture of a calling method according to an embodiment of the present disclosure.
Fig. 4 is a flowchart of an EIR test of a calling method according to an embodiment of the present disclosure.
Fig. 5 is a flow chart of asynchronous execution of call and verification provided by an embodiment of the present disclosure.
Fig. 6 is a flowchart of EIR and CSCF decoupling under a DRA networking provided by an embodiment of the present disclosure.
Fig. 7 is a module schematic diagram of an electronic device provided by the present disclosure.
FIG. 8 is a schematic diagram of a computer-storable medium provided by the present disclosure.
Detailed Description
For those skilled in the art to better understand the technical solutions of the present disclosure, the following detailed description is given with reference to the accompanying drawings and specific embodiments.
Example embodiments will be described more fully hereinafter with reference to the accompanying drawings, but which may be embodied in different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.
Embodiments of the present disclosure and features of embodiments may be combined with each other without conflict.
As used herein, the term "and/or" includes any and all combinations of one or more of the associated listed items.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "comprises" and/or "comprising," when used in this specification, … … specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of the relevant art and the present disclosure, and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.
In the mobile network, the MSC and the Mobility Management Entity (MME) send the IMEI information of the device to the EIR device, the EIR device compares the received IMEI with the white, black, and gray lists, and sends the result to the MSC and the MME, so that the MSC and the MME determine whether to allow the mobile station device to enter the network. But this approach does not take into account the following scenario: the calling client of VoLTE and VoWiFi is mainly integrated in the mobile terminal in a Native (Native) mode, the registration in the IMS network is already completed in the normal starting state of the mobile phone, if the registration refreshing period is not available, the access network is switched or is switched off and then started, and the registered state capable of talking is kept. When the mobile terminal is lost or stolen, the user usually reports the loss to the operator, but at this time, if the terminal initiates a call or even international long distance, the call is normally dialed, and the resulting charge part is judged to be borne by the operator in the actual cases of a plurality of items. This situation can also exist in 5G and even 6G networks if no measures are taken to solve it.
In order to solve the problem of safe use of the mobile terminal and avoid loss of operators and customers, the calling method provided by the disclosure is used for preventing the stolen calls from being stolen and the loss of the processing terminal of the voice core network IMS in the 4G and 5G of the 3GPP and the WiFi access network. The use state of the mobile terminal based on the IMS call is detected when the call is initiated, and the terminal, the card and the user are linked to identify the identity, so that the reported mobile terminal is not used by an illegal holder, and the emergency call is preferentially put through. By adopting the asynchronous processing mode of the normal call of the mobile terminal and the EIR inspection process, the normal call is not interfered, the time delay is not increased, and the networking flexibility is also realized by decoupling the service network element and the detection device.
In a first aspect, an embodiment of the present disclosure provides a Call method, which is used for a Call Session Control Function entity (CSCF), and as shown in fig. 1, the determining includes the following steps:
in step S110, an initial Invite (Invite) request is received;
in step S120, the mobile terminal identification information carried in the initial Invite request is determined;
in step S130, an EIR status check request is sent to an equipment identification register EIR, where the EIR status check request carries the mobile terminal identification information;
receiving an EIR status check result, wherein the EIR makes the EIR status check result according to the EIR status check request, in step S140;
in step S150, according to the EIR status check result, a corresponding operation related to the call is executed according to a preset policy.
And the calling S-CSCF receives the Invite request and judges that the Access is VoLTE or VoWiFi according to the content of Access Network information (PANI). IMEI or IMSI information of a mobile terminal initiating a call is extracted from the Invite information, and a calling S-CSCF sends the information to the existing network EIR equipment through an S13 interface.
In this embodiment, the S-CSCF sends the EIR status check Request to the EIR through an Engineering Change Request (ECR), and the EIR sends the EIR status check result to the S-CSCF through an Engineering Change Answer (ECA).
The EIR equipment compares the results through a local black, white and grey list, the comparison result is returned through S13, and the S-CSCF returns the result of the black list, the white list and the grey list according to the EIR and the result code information.
And a policy is preset in the S-CSCF, and a detection result is returned aiming at the EIR to decide whether to allow or prohibit the call of the equipment.
In a mobile network, the MSC and MME may send the IMEI information of the device to the EIR device for verification so that the MSC and MME decide whether to admit the mobile station device to the network. However, the calling clients of VoLTE and VoWiFi cannot confirm the user status in this way. In view of the above theft issue problem, the embodiment of the present disclosure actively sends the identification information of the mobile terminal to the EIR device through the S-CSCF for verification on the call client of the VoLTE and the VoWiFi, and does not need to wait for the registration refresh period, and can detect whether the state of the mobile terminal is abnormal in time, thereby solving the theft issue after the terminal is lost and stolen, and reducing the loss of the operator.
As an alternative embodiment, the step of sending an EIR status check request to the EIR is performed before the initial filter rule iFC of the caller is triggered.
Before the iFC triggers the call flow, an EIR status check request is sent to the EIR. As to whether ifcs are to continue triggering the call flow, there are two options:
one is that the iFC triggers the call flow without waiting for the EIR status check result and proceeds according to the normal call flow. After receiving the EIR status check result, deciding whether to intervene the call flow that has occurred. Since the EIR test and the call flow are processed according to the respective flows, they are called asynchronous flows.
The other is that the iFC does not trigger the call flow and waits for the EIR status check result. After receiving the EIR status check result, it is determined whether the iFC can trigger the call flow. A synchronous flow is referred to as an asynchronous flow, as opposed to an asynchronous flow, because the call flow needs to be terminated until the EIR check result is received before deciding whether to continue the call.
As an optional implementation manner, the preset policy includes a first preset rule, and after the iFC of the calling party is triggered, a call flow is triggered for the call request meeting the iFC detection; and after receiving the EIR state detection result, processing the occurred call flow according to a first preset rule.
The execution of the call flow and the EIR inspection flow can adopt asynchronous flow, after receiving a call request, the S-CSCF can directly trigger iFC detection of a calling party, and the call can be directly initiated if the iFC is satisfied, without waiting for the result of the EIR detection to determine that the call is allowed. The asynchronous execution mode does not interfere the prior call flow, does not increase time delay, and can judge whether the system side needs to initiate call release according to the EIR detection result.
Further, the processing, by the first preset rule, the call flow that has occurred includes: if the EIR state inspection result is that the terminal state is abnormal, sending a call forbidding instruction to the terminal to terminate the occurred call flow; and if the EIR state inspection result is abnormal in the non-terminal state, maintaining the call flow.
Wherein the terminal state exception comprises: the EIR state inspection result is inspection failure, and/or a result code in the EIR state inspection result is blacklist matching.
For the asynchronous flow, the first preset rule for the EIR state detection result is specifically as follows:
EIR check and call adopt asynchronous flow, and S-CSCF executes after receiving ECA:
(1) Receiving an ECA success response, carrying a Result Code in a Result-Code, filling the Equipment-Status AVPs as the following values when the Result-Code is successful, and confirming the execution strategy of the S-CSCF with an operator:
WHITELISTED (0) — does not interfere with the existing process
BLACKLISTED (1) — terminate existing flow, system side S-CSCF initiates call termination
GREYLISTED (2) — without interfering with the existing process
DIAMETER _ ERROR _ EQUIPMENT _ UNKNOWN (5422) — does not interfere with existing flows
(2) Receiving ECA failure response, the Result Code is carried in Result-Code AVP, except DIAMETER _ ERROR _ EQUIPMENT _ UNKNOWN (5422), other failure SIP is processed according to failure, terminating the existing flow, the system side S-CSCF initiates call termination.
As an optional implementation manner, the preset policy includes a second preset rule, and after the EIR state detection result is received, the call request iFC triggering operation is performed according to the second preset rule.
Corresponding to the asynchronous mode, the call flow and EIR check flow can also be executed by adopting synchronous flow, after the S-CSCF receives the call request, the result of EIR detection needs to be waited, then the iFC detection of the calling party is triggered, and the call can be initiated when the iFC is satisfied. The synchronous mode is more strict in the detection of the call, and the result of EIR detection needs to be waited to determine whether the call is allowed or not.
Further, if the EIR state inspection result is that the terminal state is abnormal, a Forbidden message is sent to the terminal sending the initial Invite request; and if the EIR state inspection result is abnormal in the non-terminal state, triggering a call request iFC and releasing the call.
Wherein the terminal state anomaly comprises:
the EIR state inspection result is inspection failure, and/or a result code in the EIR state inspection result is blacklist matching.
For the synchronous flow, the second preset rule for the EIR state detection result is specifically as follows:
the EIR detection and the calling adopt a synchronous flow, and the execution of the S-CSCF after receiving the ECA is realized by the prior I-CSCF:
(1) Receiving an ECA success response, carrying a Result Code in a Result-Code, filling the Equipment-Status AVPs as the following values when the Result-Code is successful, and confirming the execution strategy of the S-CSCF with an operator:
WHITELISTED (0) — allowing put-through
BLACKLITED (1) -INHIBIT
GREYLISTED (2) — allowing venting
DIAMETER _ ERROR _ EQUIPMENT _ UNKNOWN (5422) -permit let-through
The basis for this exception handling is the protocol 3gpp ts22.016, described as follows:
Besides the black and white list,administrations have the possibility to use a grey list.Equipments on the grey list are not barred(unless on the black list or not on the white list),but are tracked by the network(for evaluation or other purposes).
(2) After receiving the ECA failure response, the Result Code is carried in the Result-Code AVP, and other failed SIP is processed according to failure except DIAMETER _ ERROR _ EQUIPMENT _ UNKNOWN (5422).
As an optional implementation manner, the mobile terminal identification information includes at least one of the following information:
the international mobile equipment identity IMEI, the international mobile subscriber identity IMSI and the public user identity PUI of the mobile terminal.
For the originating scenario, the calling S-CSCF needs to support IMEI or IMEI + PUI check of the S13 interface, and the S13 interface needs to carry (IMEI, IMSI) or (IMEI, IMSI, PUI). The extraction method of each field is as follows:
(1) The IMEI extraction method comprises the following steps:
if the Invite request carries information, the Invite request is used for requesting IMEI information in an sip. If the Invite does not exist, the registered IMEI is used (the IMEI needs to be saved during registration), and if the registration does not exist, the information is not filled;
(2) The IMSI extraction method comprises the following steps:
the S-CSCF takes the digital part of the registered PVI, if the user is not registered, the digital part in the HSS PVI information is taken (whether the digital part is a pure digital larger than 13 bits needs to be judged);
when extracting on S-CSCF, IMSI preferentially takes username field in Authorization header field of registration code stream, format as follows: digest username = "716060806302394@ims.mnc006.mcc716.3gppnetwor k.org"; if there is no Authorization header field, take the username in the To field, in the format as follows:
To:<sip:716060803237652@ims.mnc006.mcc716.3gppnetwork.org>;
and if the modes are not obtained, taking the digital part in the PVI information obtained from the HSS SAR.
(3) The PUI extraction method comprises the following steps:
and the PUI information in the From field in the Invite message is taken From the S-CSCF.
The specific filling method in the ECR message is as follows:
<ME-Identity-Check-Request>::=<Diameter Header:324,REQ,PXY,16777252>
<Session-Id>
[DRMP]
[Vendor-Specific-Application-Id]
{Auth-Session-State}
{Origin-Host}
{Origin-Realm}
[Destination-Host]
{Destination-Realm}
{Terminal-Information}
[ User-Name ]// fill in IMSI information
* [ AVP ]// extended AVP, copy From field in Invite message, including PUI information
*[Proxy-Info]
*[Route-Record]
Specific filling modes in the terminal information Attribute Value Pair (AVP) message are as follows:
Terminal-Information::=<AVP header:1401 10415>
[ IMEI ]// filling in IMEI information
[3GPP2-MEID]
[Software-Version]
*[AVP]
The embodiment of the disclosure adds user PUI information verification on the basis that IMEI represents the terminal equipment and IMSI represents the SIM card. The S-CSCF can acquire IMEI, IMSI and PUI as an enhanced checking request, simultaneously carries 3 items of information and sends the information to EIR for checking. The terminal, the card and the user can be linked to identify, and illegal communication is further avoided.
As an alternative embodiment, a flag of the EIR status check is set; if the EIR state inspection flag is set to be negative, triggering a call flow by the iFC of the calling party after receiving the initial Invite request; if the EIR status check flag is set to be yes, after the initial Invite request is received and before the iFC of the calling party is triggered, the EIR status check request is sent to the EIR, and corresponding operation related to the call is executed according to the EIR status check result and a preset strategy.
After the flag of EIR state inspection is set at the S-CSCF side, a corresponding switch can be made at the network management side, and the switch state is used for controlling whether the VoLTE or VoWiFi access needs to execute the authentication of the EIR equipment. When the gateway side switch is turned on, the flag state of the EIR status check at the S-CSCF side is "yes", which indicates that the EIR device authentication needs to be performed before the iFC of the calling party is triggered, regardless of the asynchronous flow or the synchronous flow described above. When the gateway side switch is closed, the flag state of the EIR state check at the S-CSCF side is "NO", which means that the EIR equipment authentication is not executed before the call flow is started, and the processing is still performed by the original flow.
The default state of the flag for EIR status check is "NO". Thus, the method can be compatible with old equipment and equipment which does not support EIR authentication; thus, the method can be compatible with old equipment and equipment which does not support EIR authentication;
it should be noted that in the open state of the switch, there are several special cases to be considered:
when the called number is a special service number, triggering a calling process;
when the mobile terminal is accessed in a non-VoLTE mode or a non-VoWifi mode, triggering a calling process;
and triggering a calling process when the calling request and the registration information of the mobile terminal do not carry access network information PANI.
Specific implementation manners are as follows:
(1) And the calling S-CSCF receives the initial Invite request, judges that the terminal is accessed by VoLTE or VoWiFi according to the calling PANI, and sends an ECR request to the EIR through an S13 interface, wherein the message carries the IMEI. And after the EIR inspection is finished, returning a successful response and carrying black, white and gray information, wherein the black, white and gray strategy is as follows: black-forbidden, white-allowed, gray-allowed;
(2) The calling S-CSCF receives the initial Invite request, and does not perform EIR authentication if the calling PANI is judged that the terminal is accessed in a non-VoLTE or non-VoWiFi mode;
(3) And the calling S-CSCF receives the initial Invite request, the call does not carry PANI, the PANI is taken to be registered, and if the call and the registration do not carry PANI, EIR authentication is not carried out. The typical scenario is that the called number is a special service number, such as: emergency call numbers 110, 119, etc. In addition, a special number specified by local regulations and a special number specified by an operator may be set to be called directly without EIR authentication.
As an optional implementation manner, the EIR status check request is sent to a routing agent node DRA, and the DRA forwards the EIR status check request to the EIR.
A basic scene of a DRA networking mode is that CSCF (including I-CSCF and S-CSCF) is not directly connected with EIR, and the CSCF does not need to pay attention to specific EIR, and the selection and management of the EIR are unified to the DRA. Therefore, the CSCF only needs to select an available DRA, the host name of the EIR is not specified in the message, and the DRA can select an appropriate EIR according to a local policy or the like. The ECR message stuffing method is exemplified as follows:
1) When DRA networking is performed, EIR types and names of adjacent hosts on CSCF network elements need to be configured with host names of DRAs.
2) And when DRA networking is performed, the CSCF acquires an adjacent EIR type Host, and the sent ECR message does not carry Destination-Host AVP and only carries an opposite-end domain name.
The Destination-Host is optional as defined in the protocol 3GPP 27.229. The Destination-Host can be obtained by DRA from the adjacent Host name with the type EIR of the adjacent Host in the adjacent Host.
The message format is exemplified as follows:
<ME-Identity-Check-Request>::=<Diameter Header:324,REQ,PXY,16777252>
<Session-Id>
[DRMP]
[Vendor-Specific-Application-Id]
{Auth-Session-State}
{Origin-Host}
{Origin-Realm}
[Destination-Host]
{Destination-Realm}
{Terminal-Information}
[User-Name]
*[AVP]
*[Proxy-Info]
*[Route-Record]
and the service module such as CSCF does not fill in Destination-Host AVP under the DRA networking.
A system global switch can be newly added, CSCF judges whether the DRA networking is performed or not through the switch, and the switch is defaulted to be closed. When the switch is opened, the DRA networking is considered, and Destination-Host AVP is not filled in the ECR.
And the S-CSCF sends an ECR request to the DRA, and the DRA networking ECR request is sent to the EIR network element. The EIR network element sends an ECA response to the DRA, and the S-CSCF receives the ECA response from the DRA. The S-CSCF and the EIR are not directly connected, one S-CSCF and the EIR do not correspond to each other one by one, and the DRA is used for realizing the decoupling of the S-CSCF and the EIR. The relation between the S-CSCF and the EIR is more flexible due to the scene, the DRA can select the EIR corresponding to the user as the target EIR according to a local strategy or user information of the ECR, and the inspection efficiency is improved.
In addition, the support of DRA protection switching by the S-CSCF can be increased. For example: the S-CSCF is connected to the DRA, the DRA has the protection of the DRA01 and the DRA02, and when the DRA01 is down, the S-CSCF can access the DRA02, so that the EIR state inspection process initiated by the S-CSCF cannot be interrupted, and the protection of the EIR state inspection process is realized.
In a second aspect, an embodiment of the present disclosure provides a calling method for EIR, and as shown in fig. 2, the determining includes the following steps:
in step S160, receiving the EIR status check request sent by the CSCF, where the EIR status check request includes the mobile terminal identification information;
in step S170, an EIR status check result for the mobile terminal identification information is obtained according to a preset check rule;
in step S180, the EIR status check result is sent to the CSCF.
After receiving the Invite request, the calling S-CSCF extracts the identification information of the mobile terminal which initiates the call from the Invite information. And the calling S-CSCF sends an EIR state check request to the EIR through an S13 interface.
The EIR equipment compares the results through a local black-white-grey list, returns the comparison result through S13, and the S-CSCF returns the results of the black list, the white list and the grey list according to the EIR and the result code information.
And a policy is preset in the S-CSCF, and a detection result is returned aiming at the EIR to decide whether to allow or prohibit the call of the equipment.
In a mobile network, the MSC and MME may send the IMEI information of the device to the EIR device for verification so that the MSC and MME decide whether to admit the mobile station device to the network. However, the calling clients of VoLTE and VoWiFi cannot confirm the user status in this way. In view of the above theft issue, the embodiment of the disclosure actively sends the identification information of the mobile terminal to the EIR device through the S-CSCF for verification for the calling client of the VoLTE and the VoWiFi, without waiting for the registration refresh period, and can detect whether the state of the mobile terminal is abnormal in time, thereby solving the problems of loss of the terminal and theft after theft, and reducing the loss of the operator.
Further, the checking the EIR status of the mobile terminal identification information according to the preset checking rule includes:
and checking the international mobile equipment identity IMEI, the international mobile subscriber identity IMSI and the public user identity PUI of the mobile terminal, and generating the EIR state checking result.
In the step, a PUI check is added, an PUI database is added to EIR on the basis of the current IMEI and IMSI databases, an S13 interface (based on 3GPP TS29.272) is expanded to add PUI information, and the EIR check is performed by combining the IMEI, the IMSI and the PUI. As an enhanced check, the embodiment of the present disclosure adds user PUI information verification on the basis that the IMEI represents the terminal device and the IMSI represents the SIM card, so that terminal, card, and user linkage identification can be realized, and further illegal communication is avoided.
It should be noted that the mobile terminal identification information includes, but is not limited to, IMEI, IMSI, PUI, and other mobile terminal identification information that can be used for mobile terminal identification, and also falls within the scope of the present invention.
The methods provided by the first and second aspects of the present disclosure are described below with reference to 3 examples.
Example 1
The embodiment 1 of the present disclosure provides a procedure of a call method of an IMS system. As shown in fig. 4, the process includes the following steps:
step S201: the calling S-CSCF receives an initial Invite request;
step S202: the calling S-CSCF judges whether the terminal is accessed by VoLTE or VoWiFi (whether the judgment is needed or not can be determined by a configuration switch) according to PANI information in the Invite request, and before the calling iFC is triggered, an ECR request is sent to an EIR through an S13 interface, and IMEI and IMSI are carried in the message;
it should be noted that different operators can flexibly set the switch states according to actual needs, thereby realizing flexibility of operator selection.
Step S203: optional step 1, EIR judges that the terminal is currently in a white list through IMEI and IMSI;
step S204: EIR returns ECA with "result code: white list ";
step S205: the S-CSCF receives the result code: the ECA of the white list "performs the trigger of the calling iFC, puts through the call to the subsequent Application Server (AS);
step S206: optional step 2, EIR judges that the terminal is currently in the blacklist through IMEI and IMSI;
step S207: EIR returns ECA with "result code: black list ";
step S208: the S-CSCF receives the result code: the ECA of the blacklist rejects the call and sends a 403Forbidden message to the request terminal;
step S209: optional step 3, EIR judges that the terminal is currently in a grey list through IMEI and IMSI;
step S210: EIR returns ECA with "result code: grey list ";
step S211: the S-CSCF receives the result code: ECA of the grey list carries out calling iFC triggering, and the calling is put through to a subsequent AS;
step S212: optional step 4, EIR judges the terminal as unknown equipment by IMEI and IMSI (code 5422);
step S213: EIR returns ECA with "result code:
DIAMETER_ERROR_EQUIPMENT_UNKNOWN(5422)”;
step S214: the S-CSCF receives the result code:
ECA of DIAMETER _ ERROR _ EQUIPMENT _ UNKNOWN (5422) "performs calling iFC triggering, and puts through the call to the subsequent AS;
step S215: step 5 can be selected, EIR judges the terminal is not more than 4 conditions through IMEI and IMSI;
step S216: EIR returns ECA with "result code: other errors other than 5422 ";
step S217: the S-CSCF receives the result code: other ECA's not being 5422 error' rejects the call and sends 403Forbidden message to the requesting terminal;
example 2
The embodiment 2 of the present disclosure is an exemplary flow for asynchronous execution of call and verification. As shown in fig. 5, the process includes the following steps:
step S301: the calling S-CSCF receives an initial Invite request;
step S302: the calling S-CSCF judges whether the terminal is accessed by VoLTE or VoWiFi (whether the judgment is needed or not can be determined by a configuration switch) according to PANI information in the Invite request, and before the calling iFC is triggered, an ECR request is sent to an EIR through an S13 interface, and IMEI and IMSI are carried in the message;
step S303: the calling S-CSCF normally processes the Invite message and triggers the AS according to the iFC;
step S304: the calling S-CSCF receives the ECA returned by the EIR;
step S305: the calling S-CSCF carries out logic judgment according to the ECA;
step S306: if the terminal state is not abnormal, no action is done, and the current user call flow is not interfered;
step S307: if the terminal state is abnormal, rejecting the call and sending 403Forbidden message to the request terminal;
example 3
The embodiment 3 of the present disclosure provides an EIR and CSCF decoupling process under DRA networking. As shown in fig. 6, the process includes the following steps:
step S401: CSCF receives the Register message of terminal Register request;
step S402: and a system global switch is newly added, the CSCF judges whether the DRA networking is performed or not through the switch, and the switch is defaulted to be closed. When the switch is turned on, the switch is considered to be DRA networking, the CSCF sends an ECR message to the EIR, and the Destination-Host AVP is not filled in the ECR message;
step S403: the DRA selects the EIR corresponding to the user as a target EIR according to a local policy or user information of the ECR, acquires a target EIR Host name from an adjacent Host name of which the adjacent Host type is the EIR in the adjacent Host and fills the target EIR Host name in a Destination-Host AVP in an ECR message;
steps S404, S405: the DRA sends an ECR message to the target EIR, optionally step S404 or S405 to EIR 01 or EIR 02;
steps S406 and S407: the target EIR returns an ECA judgment result, and optional step S406 or S407 is sent by the target EIR;
step S408 DRA forwards ECA message replied by the target EIR to CSCF;
step S409 CSCF proceeds the follow-up process according to the received "result code" in ECA, continues the terminal registration or refuses the terminal registration.
In a third aspect, the disclosed embodiment provides a CSCF device, which is characterized in that the device includes a memory, a processor, a program stored on the memory and executable on the processor, and a data bus for implementing connection communication between the processor and the memory, and the program, when executed by the processor, implements the steps of the calling method according to the first aspect.
In a fourth aspect, an embodiment of the present disclosure provides an EIR apparatus, including a memory, a processor, a program stored on the memory and executable on the processor, and a data bus for implementing connection communication between the processor and the memory, wherein the program, when executed by the processor, implements the steps of the calling method according to the second aspect.
In a fifth aspect, a storage medium for computer readable storage, wherein the storage medium stores one or more programs which are executable by one or more processors to implement the steps of the cross-region communication method according to any one of the first or second aspects.
The calling method provided by the disclosure is used for preventing the stolen calls from being stolen and preventing the loss of the processing terminal of the voice core network IMS in the 4G and 5G of the 3GPP and the WiFi access network. The method is not only suitable for the existing VoLTE and VoWiFi network scenes, but also suitable for the VoNR of the subsequent network such as 5G. The method detects the use state of the IMS call-based mobile terminal when the call is initiated, and the terminal, the card and the user are linked to identify the identity, thereby ensuring that the reported mobile terminal is not used by an illegal owner and realizing the prior release of the emergency call. By adopting the asynchronous processing mode of the normal call of the mobile terminal and the EIR inspection process, the normal call is not interfered, the time delay is not increased, the networking flexibility is realized by the decoupling mode of the service network element and the detection device, and by adopting the mode of service switch control, different operators can flexibly set the switch state according to actual needs, so that the selection flexibility of the operators is realized.
One of ordinary skill in the art will appreciate that all or some of the steps of the methods, systems, functional modules/units in the devices disclosed above may be implemented as software, firmware, hardware, and suitable combinations thereof.
In a hardware implementation, the division between functional modules/units mentioned in the above description does not necessarily correspond to the division of physical components; for example, one physical component may have multiple functions, or one function or step may be performed by several physical components in cooperation. Some or all of the physical components may be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application specific integrated circuit. Such software may be distributed on computer readable media, which may include computer storage media (or non-transitory media) and communication media (or transitory media). The term computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data, as is well known to those of ordinary skill in the art. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital Versatile Disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can accessed by a computer. In addition, communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media as known to those skilled in the art.
The preferred embodiments of the present invention have been described above with reference to the accompanying drawings, and are not to be construed as limiting the scope of the invention. Any modifications, equivalents and improvements which may occur to those skilled in the art without departing from the scope and spirit of the present invention are intended to be within the scope of the claims.
Claims (17)
1. A call method for serving a call session control entity, CSCF, comprising:
receiving an initial Invite request;
determining the mobile terminal identification information carried in the initial Invite request;
sending an EIR status check request to an equipment identification register EIR, wherein the EIR status check request carries the identification information of the mobile terminal;
receiving an EIR status check result, wherein the EIR makes the EIR status check result according to the EIR status check request;
and executing corresponding operation related to the call according to a preset strategy according to the EIR state inspection result.
2. The calling method according to claim 1, wherein the calling method further comprises:
the step of sending an EIR status check request to the EIR is performed before the initial filter rule iFC of the caller is triggered.
3. The calling method according to claim 2, wherein the preset policy includes a first preset rule, the calling method further comprising:
after the iFC detection of a calling party is triggered, triggering a calling flow for a calling request meeting the iFC detection;
and after receiving the EIR state detection result, processing the occurred call flow according to the first preset rule.
4. The calling method according to claim 3, wherein the processing the call flow that has occurred according to the first preset rule comprises:
if the EIR state inspection result is that the terminal state is abnormal, sending a call prohibiting instruction to the mobile terminal to terminate the occurred call flow;
and if the EIR state inspection result is abnormal in the non-terminal state, maintaining the call flow.
5. The calling method according to claim 4, wherein the terminal state exception comprises:
the EIR state inspection result is inspection failure, and/or a result code in the EIR state inspection result is blacklist matching.
6. The calling method according to claim 2, wherein the preset policy includes a second preset rule, the calling method further comprising:
and after receiving the EIR state detection result, carrying out call request iFC triggering operation according to a second preset rule.
7. The calling method according to claim 6, wherein the second preset rule comprises:
if the EIR state inspection result is that the terminal state is abnormal, a Forbidden message is sent to the terminal sending the initial Invite request;
and if the EIR state inspection result is abnormal in a non-terminal state, triggering the initial Invite call request iFC and putting through a call.
8. The calling method of claim 7, wherein the terminal state exception comprises:
the EIR state inspection result is inspection failure, and/or a result code in the EIR state inspection result is blacklist matching.
9. The calling method according to claim 1, wherein the mobile terminal identification information includes at least one of:
the international mobile equipment identity IMEI, the international mobile subscriber identity IMSI, the public user identity PUI and the like of the mobile terminal.
10. The calling method according to any one of claims 1 to 9, comprising:
setting an EIR status check mark;
if the EIR state inspection flag is set to be negative, triggering a call flow by the iFC of the calling party after receiving the initial Invite request;
if the EIR status check flag is set to be yes, after the initial Invite request is received and before the iFC of the calling party is triggered, the EIR status check request is sent to the EIR, and corresponding operation related to the call is executed according to the EIR status check result and a preset strategy.
11. The calling method according to any one of claims 1 to 9, further comprising at least one of:
when the called number is a special service number, triggering a calling process;
when the mobile terminal is accessed in a non-VoLTE mode or a non-VoWiFi mode, a call flow is triggered;
and triggering a calling process when the calling request and the registration information of the mobile terminal do not carry access network information PANI.
12. The calling method according to any one of claims 1 to 9, comprising:
and sending the EIR state inspection request to a routing agent node DRA, and forwarding the EIR state inspection request to the EIR by the DRA.
13. A calling method for an equipment identity register EIR, comprising:
receiving an EIR state inspection request sent by the service call session control entity (CSCF), wherein the EIR state inspection request comprises mobile terminal identification information;
according to a preset inspection rule, obtaining an EIR state inspection result of the mobile terminal identification information;
and sending the EIR state detection result to the CSCF.
14. The calling method according to claim 13, wherein the obtaining an EIR status check result for the mobile terminal identification information according to a preset check rule comprises:
and checking the international mobile equipment identity IMEI, the international mobile subscriber identity IMSI and the public user identity PUI of the mobile terminal, and generating the EIR state checking result.
15. A serving call session control entity, CSCF, device comprising a memory, a processor, a program stored on the memory and executable on the processor, and a data bus for enabling connecting communication between the processor and the memory, the program when executed by the processor implementing the steps of the method of a call according to any of claims 1 to 12.
16. An EIR device, characterized in that it comprises a memory, a processor, a program stored on said memory and executable on said processor, said program when executed by said processor implementing the steps of the method of calling according to any of claims 13-14, and a data bus for implementing a connection communication between said processor and said memory.
17. A storage medium for computer readable storage, wherein the storage medium stores one or more programs executable by one or more processors to implement the steps of the method of calling of any of claims 1-14.
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202110734101.1A CN115550896A (en) | 2021-06-30 | 2021-06-30 | Calling method, device and storage medium |
PCT/CN2022/101066 WO2023274055A1 (en) | 2021-06-30 | 2022-06-24 | Calling method, device and storage medium |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202110734101.1A CN115550896A (en) | 2021-06-30 | 2021-06-30 | Calling method, device and storage medium |
Publications (1)
Publication Number | Publication Date |
---|---|
CN115550896A true CN115550896A (en) | 2022-12-30 |
Family
ID=84690063
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN202110734101.1A Pending CN115550896A (en) | 2021-06-30 | 2021-06-30 | Calling method, device and storage medium |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN115550896A (en) |
WO (1) | WO2023274055A1 (en) |
Family Cites Families (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP4319411B2 (en) * | 2001-03-20 | 2009-08-26 | トムソン ライセンシング | Method of remote diagnosis and set-top box for performing remote diagnosis |
ATE338418T1 (en) * | 2004-06-07 | 2006-09-15 | Cit Alcatel | METHOD AND DEVICE FOR PREVENTING ATTACKS ON A CALL SERVER |
CN102869004A (en) * | 2011-07-05 | 2013-01-09 | 中兴通讯股份有限公司 | Mobile terminal recovery and information protection method and device |
CN106453799B (en) * | 2016-10-25 | 2019-06-04 | 郭铮铮 | Manipulative communications deception recognition methods and system |
-
2021
- 2021-06-30 CN CN202110734101.1A patent/CN115550896A/en active Pending
-
2022
- 2022-06-24 WO PCT/CN2022/101066 patent/WO2023274055A1/en active Application Filing
Also Published As
Publication number | Publication date |
---|---|
WO2023274055A1 (en) | 2023-01-05 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP3662630B1 (en) | Methods, systems, and computer readable media for mobility management entity (mme) authentication for outbound roaming subscribers using diameter edge agent (dea) | |
EP3834450B1 (en) | Methods, systems, and computer readable media for conducting a time distance security countermeasure for outbound roaming subscribers using diameter edge agent | |
US12048037B2 (en) | Methods and devices for establishment of redundant PDU session | |
EP2835027B1 (en) | Call-back to a ue that has made an emergency call in a visited ims network | |
JP5506819B2 (en) | Emergency call handling | |
EP2323332A1 (en) | Controlling a session in a service provisioning system | |
CN104798421A (en) | Method and apparatus for controlling specific service in network congestion state in wireless communication system | |
EP1386510B1 (en) | Method and system for enabling emergency sessions to be established in abnormal cases | |
CN102027766A (en) | Methods, systems for controlling access to voice resources in mobile networks | |
EP2487986A1 (en) | Method, device and system for processing connection of called party | |
CN110324819B (en) | Management method and management server of auxiliary card terminal | |
WO2022018581A1 (en) | Rogue network function re-authorization in a communication network | |
CN108235315B (en) | Wireless VPDN (virtual private network digital network) access method and system with configuration-free terminal | |
JP5381087B2 (en) | Communication system and communication control method | |
WO2023274055A1 (en) | Calling method, device and storage medium | |
US12041200B2 (en) | Emergency call handling in a telecommunications network | |
US9544756B2 (en) | Home communication network determination | |
CN101009700A (en) | Method, application and device for the user state identification in the network | |
KR102440411B1 (en) | Method and apparatus for detecting abnormal roaming request | |
US20230232232A1 (en) | Methods, systems, and computer readable media for providing call intelligence to a signaling firewall in a communications network | |
US11184758B2 (en) | Method and device for managing user service profiles | |
WO2011018029A1 (en) | Method, system and home location register for implementing smoothing of signaling traffic | |
US20230247433A1 (en) | Rogue network function detection and isolation in a communication network | |
WO2014177174A1 (en) | Hplmn indication in roaming architecture for voice over ims with local breakout | |
CN117221287A (en) | Communication method, communication device and computer readable storage medium |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PB01 | Publication | ||
PB01 | Publication | ||
SE01 | Entry into force of request for substantive examination | ||
SE01 | Entry into force of request for substantive examination |