WO2023274055A1 - 呼叫方法、设备和存储介质 - Google Patents

呼叫方法、设备和存储介质 Download PDF

Info

Publication number
WO2023274055A1
WO2023274055A1 PCT/CN2022/101066 CN2022101066W WO2023274055A1 WO 2023274055 A1 WO2023274055 A1 WO 2023274055A1 CN 2022101066 W CN2022101066 W CN 2022101066W WO 2023274055 A1 WO2023274055 A1 WO 2023274055A1
Authority
WO
WIPO (PCT)
Prior art keywords
eir
call
request
inspection
result
Prior art date
Application number
PCT/CN2022/101066
Other languages
English (en)
French (fr)
Inventor
李立平
戴志刚
方琰崴
缪永生
史庭祥
陈亚权
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2023274055A1 publication Critical patent/WO2023274055A1/zh

Links

Images

Classifications

    • 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
    • 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
    • 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

Definitions

  • Embodiments of the present disclosure relate to but are not limited to the field of mobile communications, and in particular, relate to a calling method, device and storage medium.
  • the IP Multimedia Subsystem (IMS, IP Multimedia Subsystem) is formulated by the 3rd Generation Partnership Project (3GPP, 3rd Generation Partnership Project).
  • 3GPP 3rd Generation Partnership Project
  • IMS IP Multimedia Subsystem
  • VoIP Voice over Long-Term Evolution
  • VoIP Voice over Long-Term Evolution
  • VoIP Voice over Wireless Fidelity
  • WiFi Voice over Wireless Fidelity
  • Softswitch replacement With the vigorous development of the fifth-generation mobile communication system (5G), it has become the only international standard technology for voice over new radio (VoNR, Voice over New Radio) and 5G fusion messages.
  • EIR Equipment Identity Register
  • MSC Mobile Switching Center
  • PS Packet Switching domain
  • EIR Equipment Identity Register
  • IMEI International Mobile Equipment Identity
  • MSC and Mobility Management Entity send the IMEI information of the device to the EIR device, and the EIR device compares the received IMEI with the three lists of white, black and gray, and sends the result to To MSC and MME, so that MSC and MME decide whether to allow the mobile station equipment to enter the network.
  • the disclosure provides a calling method, device and storage medium.
  • an embodiment of the present disclosure provides a call method applied to CSCF, including: receiving an initial invite Invite request; determining the mobile terminal identification information carried in the initial Invite request; sending the EIR status to the equipment identification register EIR An inspection request, the EIR status inspection request carrying the mobile terminal identification information; receiving the EIR status inspection result, wherein the EIR makes the EIR status inspection result according to the EIR status inspection request; according to the EIR status Check the result, and perform corresponding call-related operations according to the preset strategy.
  • an embodiment of the present disclosure provides a call method applied to EIR, including: receiving the EIR status inspection request sent by the CSCF, the EIR status inspection request including the mobile terminal identification information; according to Presetting inspection rules to obtain an EIR status inspection result of the mobile terminal identification information; sending the EIR status inspection result to the CSCF.
  • the present disclosure provides a CSCF device, the CSCF device includes a memory, a processor, a program stored in the memory and operable on the processor, and a program for implementing the processor and the The memory is connected to a data bus for communication, and when the program is executed by the processor, the steps of the calling method as described in the first aspect are realized.
  • the present disclosure provides an EIR device, the EIR device includes a memory, a processor, a program stored on the memory and operable on the processor, and used to implement the processor and the The memory is connected to a data bus for communication, and when the program is executed by the processor, the steps of the calling method as described in the first aspect are realized.
  • the present disclosure provides a computer-readable storage, the storage medium stores one or more programs, and the one or more programs can be executed by one or more processors, so as to implement the first aspect or The steps of the calling method described in the second aspect.
  • the call method provided by the present disclosure solves the problem of anti-theft call after the terminal is lost or stolen in the voice core network IMS in the 3GPP 4G, 5G and WiFi access networks, and solves the problem of calling the mobile terminal based on the IMS call when the call is initiated.
  • Use state detection to ensure that the mobile terminal that has been reported lost is not used by illegal holders; realize terminal, card, and user linkage identification; asynchronous processing of normal call of mobile terminal and EIR inspection process, without interfering with normal call and without interference Increase the delay; guarantee the priority release of emergency calls; maintain the flexibility of networking by decoupling service network elements and detection devices.
  • Fig. 1 is a flow chart of a calling method provided by an embodiment of the present disclosure used in a CSCF.
  • Fig. 2 is a flow chart of a call method used in an EIR provided by an embodiment of the present disclosure.
  • Fig. 3 is a network architecture of a calling method provided by an embodiment of the present disclosure.
  • Fig. 4 is a flowchart of a calling method EIR inspection provided by an embodiment of the present disclosure.
  • Fig. 5 is a flowchart of asynchronous execution of call and check provided by an embodiment of the present disclosure.
  • Fig. 6 is a flowchart of the decoupling of EIR and CSCF in DRA networking provided by an embodiment of the present disclosure.
  • Fig. 7 is a schematic diagram of modules of an electronic device provided by the present disclosure.
  • Fig. 8 is a schematic diagram of a computer storage medium provided by the present disclosure.
  • MSC and Mobility Management Entity send the IMEI information of the device to the EIR device, and the EIR device compares the received IMEI with the three lists of white, black and gray, and sends the result to To MSC and MME, so that MSC and MME decide whether to allow the mobile station equipment to enter the network.
  • MME Mobility Management Entity
  • this method does not take into account the following scenarios: VoLTE and VoWiFi call clients are mainly integrated in the mobile terminal in a native way, and the registration in the IMS network has been completed when the mobile phone is turned on normally. If the registration refresh period is not reached, the access network is switched, or the device is turned off and on again, the registered and callable state will remain.
  • the mobile terminal 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 an international call, the call will be dialed normally. As a result, the phone bill has been judged to be borne by the operator in the actual cases of many projects. If no measures are taken to solve this situation, it will also exist in 5G or even 6G networks.
  • the present disclosure provides a call method.
  • the processing terminal of the voice core network IMS in the 3GPP 4G, 5G and WiFi access networks is lost or stolen call anti-theft.
  • Detect the use status of the mobile terminal based on IMS call when the call is initiated and identify the terminal, card, and user linkage to ensure that the mobile terminal that has been reported as lost is not used by an illegal owner, and it also realizes priority release for emergency calls Pass.
  • the normal call is not disturbed and the time delay is not increased, and the networking flexibility is realized by decoupling the service network element and the detection device.
  • an embodiment of the present disclosure provides a calling method for calling a session control function entity (CSCF, Call Session Control Function). As shown in FIG. 1 , the calling method includes the following steps:
  • step S110 an initial invitation (Invite) request is received
  • step S120 determine the mobile terminal identification information carried in the initial Invite request
  • step S130 an EIR status inspection request is sent to the equipment identification register EIR, and the EIR status inspection request carries the identification information of the mobile terminal;
  • step S140 an EIR status inspection result is received, wherein the EIR makes the EIR status inspection result according to the EIR status inspection request;
  • step S150 according to the result of the EIR state inspection, corresponding call-related operations are performed according to a preset strategy.
  • the calling S-CSCF receives the Invite request, and judges that it is a VoLTE or VoWiFi access according to the content of the access network information (PANI, P-Access-Network-Info).
  • the IMEI or IMSI information of the calling mobile terminal is extracted from the Invite information, and the calling S-CSCF sends it to the EIR device on the live network through the S13 interface.
  • the S-CSCF sends the EIR status inspection request to the EIR through an engineering change application (ECR, Engineering Change Request), and the EIR sends the EIR status inspection result through an engineering change response (ECA, Engineering Change Answer). Sent to S-CSCF.
  • ECR engineering change application
  • EA engineering Change Answer
  • the EIR device compares the local black, white and gray lists, returns the comparison result through S13, and the S-CSCF returns blacklist, whitelist, graylist results and result code information according to the EIR.
  • the policy is preset in the S-CSCF, and the detection result returned by the EIR determines whether to allow or prohibit the call of the device.
  • MSC and MME can send the IMEI information of the device to the EIR device for verification, so that MSC and MME can decide whether to allow the mobile station device to enter the network.
  • calling clients of VoLTE and VoWiFi cannot use this method to confirm user status.
  • the embodiments of the present disclosure aim at calling clients of VoLTE and VoWiFi, and actively send mobile terminal identification information to the EIR device for inspection through the S-CSCF, without having to wait for the registration refresh cycle, and can detect in time Whether the state of the mobile terminal is abnormal, solve the problem of the terminal being lost or stolen, and reduce the loss of the operator.
  • the step of sending the EIR status inspection request to the EIR is performed.
  • iFC Before the iFC triggers the call process, it sends an EIR status inspection request to the EIR. As for whether iFC should continue to trigger the call process, there are two options:
  • One option includes: iFC triggers the call flow, does not wait for the result of the EIR status check, and proceeds according to the normal call flow. After receiving the EIR status inspection result, decide whether to interfere with the call flow that has already occurred. Because the EIR inspection and call process are processed according to their own processes, they are called asynchronous processes.
  • Another option includes: the iFC does not trigger the call process, and waits for the result of the EIR status inspection. After receiving the EIR status inspection result, decide whether the iFC can trigger the call process. Because it is necessary to suspend the call process and decide whether to continue the call after receiving the EIR inspection result, the opposite of the asynchronous process is called a synchronous process.
  • the preset policy includes a first preset rule. After the calling party's iFC is triggered, a call process is triggered for a call request that meets the iFC detection; after receiving the EIR state detection result Afterwards, according to the first preset rule, the call flow that has occurred is processed.
  • the call process and the EIR inspection process can be executed in an asynchronous process.
  • the S-CSCF After receiving the call request, the S-CSCF will directly trigger the iFC detection of the calling party. If the iFC is satisfied, the call can be initiated directly without waiting for the result of the EIR detection. Yes allow this call.
  • the asynchronous execution will neither interfere with the existing call process nor increase the time delay, and it can be judged according to the EIR test result whether the call release needs to be initiated by the system side.
  • processing the call flow that has occurred includes: if the result of the EIR state inspection is that the terminal state is abnormal, then sending a call prohibition instruction to the terminal to terminate the call flow that has occurred ; If the EIR state inspection result is not abnormal in the terminal state, then maintain the call flow.
  • the abnormality of the terminal status includes: the EIR status inspection result is an inspection failure, and/or the result code in the EIR status inspection result is a blacklist match.
  • the first preset rule for the EIR state detection result is specifically as follows:
  • the result code is carried in the Result-Code.
  • the Equipment-Status AVPs may be filled with the following values, and the S-CSCF execution strategy is confirmed with the operator:
  • DIAMETER_ERROR_EQUIPMENT_UNKNOWN (5422) - do not interfere with existing process
  • the result code is carried in the Result-Code AVP. Except for DIAMETER_ERROR_EQUIPMENT_UNKNOWN (5422), other SIP failures are handled as failures, and the existing process is terminated.
  • the S-CSCF on the system side initiates call termination.
  • the preset policy includes a second preset rule, and after receiving the EIR state detection result, a call request iFC trigger operation is performed according to the second preset rule.
  • the execution of the call process and the EIR inspection process can also be executed in a synchronous process.
  • the S-CSCF After receiving the call request, the S-CSCF needs to wait for the result of the EIR detection, and then trigger the iFC detection of the calling party. iFC can initiate the call.
  • the synchronous mode has stricter detection on calls, and it needs to wait for the result of EIR detection before deciding whether to allow the call.
  • a prohibition message Forbidden is sent to the terminal that issued the initial Invite request; if the EIR state inspection result is not an abnormal terminal state, then a call request iFC is triggered, and the call.
  • the abnormal state of the terminal includes:
  • the EIR status inspection result is inspection failure, and/or the result code in the EIR status inspection result is a blacklist match.
  • the second preset rule for the EIR state detection result is specifically as follows:
  • the result code is carried in the Result-Code.
  • the Equipment-Status AVPs may be filled with the following values, and the S-CSCF execution strategy is confirmed with the operator:
  • graylists In addition to blacklists and whitelists, it is also possible for management stations to use graylists. Devices on the gray list are not banned from use (unless on the blacklist or not on the whitelist), but are tracked by the network (for evaluation or other purposes), ie: "Besides the black and white list, administrations have the possibility to use a gray list. Equipments on the gray 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)".
  • the result code is carried in the Result-Code AVP. Except for DIAMETER_ERROR_EQUIPMENT_UNKNOWN (5422), other failed SIPs are treated as failures.
  • the mobile terminal identification information includes at least one of the following information:
  • the calling S-CSCF needs to support the 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:
  • the digital part of the PVI information obtained from the HSS SAR is obtained.
  • Terminal-Information:: ⁇ AVP header:1401 10415>
  • the embodiment of the present disclosure adds user PUI information verification on the basis that the IMEI represents the terminal equipment and the IMSI represents the SIM card.
  • S-CSCF can obtain IMEI, IMSI, PUI as an enhanced inspection request, carrying three pieces of information at the same time, and send it to EIR for inspection. It can realize the linkage identification of terminal, card and user, and further avoid illegal calls.
  • the flag of the EIR state inspection is set; if the flag of the EIR state inspection is set to no, after receiving the initial Invite request, the calling process is triggered by the calling iFC; if the flag of the EIR state inspection When set to Yes, after receiving the initial Invite request and before the calling iFC is triggered, the EIR status inspection request is sent to the EIR, and according to the EIR status inspection result, the corresponding , Call-related operations.
  • the corresponding switch After setting the flag of EIR status inspection on the S-CSCF side, the corresponding switch can be made on the network management side, and the switch status controls whether VoLTE or VoWiFi access needs to perform EIR device authentication.
  • the flag state of the EIR status check on the S-CSCF side is "Yes”, which means that before the calling iFC is triggered, whether it is the asynchronous process or the synchronous process described above, EIR needs to be executed.
  • Device authentication When the switch on the network management side is closed, the flag status of the EIR status check on the S-CSCF side is "No", which means that the EIR device authentication is not performed before starting the call process, and the original process is still processed.
  • the default state of the flag for EIR status inspection is "No". In this way, it can be compatible with old equipment and equipment that does not support EIR certification; this can be compatible with old equipment and equipment that does not support EIR certification;
  • the calling S-CSCF receives the initial Invite request, judges that the terminal is VoLTE or VoWiFi access according to the calling PANI, and sends an ECR request to the EIR through the S13 interface, and the message carries the IMEI. After the EIR inspection is completed, a successful response is returned, and it carries black, white and gray information.
  • the black, white and gray strategy is: black-prohibited, white-permitted, gray-permitted;
  • the calling S-CSCF receives the initial Invite request, the call does not carry the PANI, and the registered PANI is taken. If neither the call nor the registration carries the PANI, EIR authentication is not performed.
  • the called number is a special service number, such as: emergency call numbers 110, 119, etc.
  • special numbers specified by local regulations and special numbers specified by operators can also be set to call directly without EIR authentication.
  • the EIR status inspection request is sent to a routing proxy node DRA, and the DRA forwards the EIR status inspection request to the EIR.
  • a basic scenario of the DRA networking mode is that the CSCF (including the I-CSCF and S-CSCF) is not directly connected to the EIR, and the CSCF does not need to pay attention to the specific EIR, and the selection and management of the EIR are unified by the DRA. Therefore, the CSCF only needs to select an available DRA, and the host name of the EIR is not specified in the message, and the DRA can select a suitable EIR according to local policies and other methods.
  • An example of how to fill the ECR message is as follows:
  • the EIR type of the adjacent host and the name of the adjacent host need to be configured with the host name of the DRA.
  • CSCF obtains the adjacent EIR type host, and the ECR message sent does not carry the Destination-Host AVP, but only carries the peer domain name.
  • the definition of Destination-Host in the protocol 3GPP 27.229 is optional.
  • the Destination-Host can be obtained by the DRA from the name of the adjacent host whose adjacent host type is EIR in the adjacent hosts.
  • Service modules such as CSCF do not fill in the Destination-Host AVP in a network with DRA.
  • a system global switch can be added.
  • the CSCF judges whether it is a DRA network through the switch.
  • the switch defaults to "OFF". When this switch is turned on, it is regarded as a DRA network, and the Destination-Host AVP is not filled in the ECR.
  • the S-CSCF sends an ECR request to the DRA, and the ECR request is sent to the EIR network element in the DRA network.
  • the EIR network element sends the ECA response to the DRA, and the S-CSCF receives the ECA response from the DRA.
  • the S-CSCF is not directly connected to the EIR.
  • An S-CSCF is not in one-to-one correspondence with the EIR. Instead, the DRA decouples the S-CSCF from the EIR. This scenario makes the relationship between the S-CSCF and the EIR more flexible.
  • the DRA can select the EIR corresponding to the user as the target EIR according to the local policy or the user information of the ECR to improve the inspection efficiency.
  • S-CSCF is connected to DRA, and DRA is protected by DRA01 and DRA02.
  • DRA01 is down
  • S-CSCF can access DRA02, so that the EIR status inspection process initiated by S-CSCF will not be interrupted, and EIR Status inspection process protection.
  • the embodiment of the present disclosure provides a calling method for EIR, as shown in FIG. 2 , the calling method includes the following steps:
  • step S160 receiving the EIR status inspection request sent by the CSCF, the EIR status inspection request including the mobile terminal identification information;
  • step S170 according to the preset inspection rules, the EIR state inspection result of the identification information of the mobile terminal is obtained;
  • step S180 the EIR status inspection result is sent to the CSCF.
  • the calling S-CSCF After receiving the Invite request, the calling S-CSCF extracts the identification information of the calling mobile terminal from the Invite information. The calling S-CSCF sends an EIR status inspection request to the EIR through the S13 interface.
  • the EIR device compares the local black, white and gray lists, returns the comparison result through S13, and the S-CSCF returns the black list, white list, gray list results and result code information according to the EIR.
  • the policy is preset in the S-CSCF, and the detection result returned by the EIR determines whether to allow or prohibit the call of the device.
  • MSC and MME can send the IMEI information of the device to the EIR device for verification, so that MSC and MME can decide whether to allow the mobile station device to enter the network.
  • calling clients of VoLTE and VoWiFi cannot use this method to confirm user status.
  • the embodiments of the present disclosure aim at calling clients of VoLTE and VoWiFi, and actively send mobile terminal identification information to the EIR device for inspection through the S-CSCF, without having to wait for the registration refresh cycle, and can detect in time Whether the state of the mobile terminal is abnormal, solve the problem of the terminal being lost or stolen, and reduce the loss of the operator.
  • the EIR state inspection result of the mobile terminal identification information includes:
  • EIR increases PUI database on the basis of current IMEI and IMSI database
  • S13 interface expands and increases PUI information
  • EIR inspection is carried out in conjunction with IMEI, IMSI and PUI.
  • the embodiment of the present disclosure adds user PUI information verification on the basis of IMEI representing terminal equipment and IMSI representing SIM card, which can realize terminal, card and user linkage identification, and further avoid illegal calls.
  • the mobile terminal identification information includes but not limited to IMEI, IMSI, PUI, and other mobile terminal identification information that can be used for mobile terminal identification also belongs to the protection scope of the present disclosure.
  • Embodiment 1 of the present disclosure provides a flow of an IMS system calling method. As shown in Figure 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 that the terminal is VoLTE or VoWiFi access according to the PANI information in the Invite request (whether this judgment is required can be determined by the configuration switch), and before the calling iFC is triggered, it sends an ECR request to the EIR through the S13 interface, The message carries IMEI and IMSI;
  • Step S203 optional step 1, the EIR judges that the terminal is currently in the whitelist through the IMEI and IMSI;
  • Step S204 EIR returns ECA with "result code: white list"
  • Step S205 S-CSCF receives the ECA of "result code: white list", triggers the calling iFC, and releases the call to the subsequent application server (AS, Application Server);
  • Step S206 optional step 2, the EIR judges that the terminal is currently in the blacklist through the IMEI and IMSI;
  • Step S207 EIR returns ECA with "result code: blacklist"
  • Step S208 S-CSCF rejects the call after receiving the ECA of "result code: blacklist", and sends a 403 Forbidden message to the requesting terminal;
  • Step S209 optional step 3, EIR judges that the terminal is currently in the gray list through the IMEI and IMSI;
  • Step S210 EIR returns ECA with "result code: gray list"
  • Step S211 S-CSCF receives the ECA of "result code: greylist”, triggers the calling iFC, and releases the call to the subsequent AS;
  • Step S212 optional step 4, EIR judges that the terminal is an unknown device through IMEI and IMSI (code 5422);
  • Step S213 EIR returns ECA with "result code:
  • Step S214 S-CSCF receives "result code:
  • Step S215 optional step 5, EIR judges that the terminal is not in the above 4 situations through IMEI and IMSI;
  • Step S216 EIR returns ECA with "result code: other errors other than 5422";
  • Step S217 S-CSCF rejects the call after receiving the ECA of "result code: other error other than 5422", and sends a 403 Forbidden message to the requesting terminal;
  • Embodiment 2 of the present disclosure is a schematic flow of calling and checking asynchronously. As shown in Figure 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 that the terminal is VoLTE or VoWiFi access according to the PANI information in the Invite request (whether this judgment is required can be determined by the configuration switch), and sends an ECR request to the EIR through the S13 interface before the calling iFC is triggered.
  • the message carries IMEI and IMSI;
  • Step S303 The calling S-CSCF normally processes the Invite message and triggers the AS according to iFC;
  • Step S304 the calling S-CSCF receives the ECA returned by the EIR
  • Step S305 the calling S-CSCF makes a logical judgment according to the ECA
  • Step S306 If the terminal state is not abnormal, then do not take any action, and do not interfere with the call flow of the current user;
  • Step S307 if the terminal state is abnormal, then reject the call, and send a 403 Forbidden message to the requesting terminal;
  • Embodiment 3 of the present disclosure provides a process for decoupling EIR and CSCF in a DRA network. As shown in Figure 6, the process includes the following steps:
  • Step S401 CSCF receives a terminal registration request Register message
  • Step S402 Add a system global switch, and the CSCF judges whether it is a DRA network through the switch, and the switch is "off" by default. When the switch is turned on, it is considered as a DRA network, and 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 the target EIR according to the local policy or the user information of the ECR, and the DRA obtains the target EIR host name from the adjacent host names whose adjacent host type is EIR among the adjacent hosts and fills it in the ECR message Middle Destination-Host AVP;
  • Steps S404, S405 DRA sends an ECR message to the target EIR, optional step S404 or S405 to EIR 01 or EIR 02;
  • Steps S406 and S407 The target EIR returns the ECA judgment result, optional step S406 or S407 is sent by the target EIR;
  • Step S408 DRA forwards the ECA message replied by the target EIR to the CSCF;
  • Step S409 CSCF performs follow-up processing according to the "result code" in the received ECA, and continues terminal registration or rejects terminal registration.
  • an embodiment of the present disclosure provides a CSCF device, the CSCF device includes a memory, a processor, a program stored in the memory and operable on the processor, and a program for implementing the processor A data bus connecting and communicating with the memory, when the program is executed by the processor, implements the steps of the calling method as described in the first aspect.
  • an embodiment of the present disclosure provides an EIR device, the EIR device includes a memory, a processor, a program stored in the memory and operable on the processor, and a program for implementing the processor A data bus connecting and communicating with the memory, when the program is executed by the processor, implements the steps of the calling method as described in the second aspect.
  • a storage medium is used for computer-readable storage, the storage medium stores one or more programs, and the one or more programs can be executed by one or more processors to implement the first The steps of the cross-region communication method described in any one of the aspect or the second aspect.
  • the disclosure provides a call method, which is used to prevent call theft after the processing terminal of the voice core network IMS is lost or stolen in the 3GPP 4G, 5G and WiFi access networks. Not only applicable to existing VoLTE and VoWiFi network scenarios, but also applicable to follow-up networks such as 5G VoNR.
  • the decoupling of the service network element and the detection device also realizes the flexibility of networking, and adopts the service switch control In this way, different operators can flexibly set the switching status according to actual needs, realizing the flexibility of operator selection.
  • 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 composed of several physical components. Components cooperate to execute.
  • 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 .
  • a processor such as a central processing unit, digital signal processor, or microprocessor
  • 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).
  • computer storage media includes both volatile and nonvolatile media implemented in any method or technology for storage of information, such as computer readable instructions, data structures, program modules, or other data. permanent, removable and non-removable media.
  • Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disk (DVD) or other optical disk storage, magnetic cartridges, tape, magnetic disk storage or other magnetic storage devices, or can Any other medium used to store desired information and which can be accessed by a computer.
  • 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 may include any information delivery media .

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

本公开提供一种呼叫方法，应用于CSCF，包括：接收初始邀请Invite请求；确定初始Invite请求中携带的移动终端识别信息；向EIR发送EIR状态检验请求，所述EIR状态检验请求中携带所述移动终端识别信息；接收EIR状态检验结果；根据EIR状态检验结果，按照预设策略执行对应的、与呼叫相关的操作。本公开提供一种呼叫方法，应用于EIR，包括：接收CSCF发送的EIR状态检验请求；根据预设检验规则，得到对移动终端识别信息的EIR状态检验结果；将EIR状态检验结果发送到CSCF。本公开通过EIR对移动终端状态的检测，解决移动终端被盗打的问题，通过异步处理的方式可以实现不干扰正常呼叫且不增加时延，通过业务网元与检测装置解耦实现组网灵活性。本公开还提供实现上述方法的设备、存储介质。

Description

呼叫方法、设备和存储介质
相关申请的交叉引用
本公开要求在2021年6月30日提交国家知识产权局、申请号为202110734101.1、发明名称为“呼叫方法、设备和存储介质”的中国专利申请的优先权，该申请的全部内容通过引用结合在本公开中。
技术领域
本公开的实施例涉及但不限于移动通信领域，尤其涉及一种呼叫方法、设备和存储介质。
背景技术
IP多媒体子系统(IMS，IP Multimedia Subsystem)由第三代合作伙伴计划(3GPP，3rd Generation Partnership Project)制定。一方面，希望通过IP的形式提供传统的电路交换服务(如语音，消息服务)。另一方面，希望通过这个子系统实现向用户提供的所有多媒体服务。经过近20年的发展，IMS已广泛应用于长期演进承载语音(VoLTE，Voice over Long-Term Evolution)，无线保真承载语音(VoWiFi，Voice over Wireless Fidelity)和软交换替代。随着第五代移动通信系统(5G)的蓬勃发展成为新无线承载语音(VoNR，Voice over New Radio)和5G融合消息的唯一国际标准技术。
随着VoLTE和VoWiFi的广泛商用，实际应用中出现了一些安全使用方面的问题。在原有移动交换中心(MSC，Mobile Switching Center)和分组交换域(PS，Packet Switching)网络中，采用EIR(Equipment Identity Register)实现对移动设备，主要是手机的合法认证，可以实现对非法手机(窃取)或者未经型号认证的移动设备的接入控制。EIR通过检查手机的国际移动设备标识(IMEI，International Mobile Equipment Identity)来防范 手机被盗从而保障系统的安全性。在移动现网中，MSC和移动管理实体(MME，Mobility Management Entity)将设备的IMEI信息发给EIR设备，EIR设备将收到的IMEI与白、黑、灰三种名单进行比较，把结果发送给MSC和MME，以便MSC和MME决定是否允许该移动台设备进入网络。
发明内容
本公开提供一种呼叫方法、设备和存储介质。
第一方面，本公开的一个实施例提供一种呼叫方法，应用于CSCF，包括：接收初始邀请Invite请求；确定所述初始Invite请求中携带的移动终端识别信息；向设备识别寄存器EIR发送EIR状态检验请求，所述EIR状态检验请求中携带所述移动终端识别信息；接收EIR状态检验结果，其中，所述EIR根据所述EIR状态检验请求做出所述EIR状态检验结果；根据所述EIR状态检验结果，按照预设策略执行对应的、与呼叫相关的操作。
第二方面，本公开的一个实施例提供一种呼叫方法，应用于EIR，包括：接收所述CSCF发送的所述EIR状态检验请求，所述EIR状态检验请求包括所述移动终端识别信息；根据预设检验规则，得到对所述移动终端识别信息的EIR状态检验结果；将所述EIR状态检验结果发送到所述CSCF。
第三方面，本公开提供一种CSCF设备，所述CSCF设备包括存储器、处理器、存储在所述存储器上并可在所述处理器上运行的程序以及用于实现所述处理器和所述存储器之间的连接通信的数据总线，所述程序被所述处理器执行时实现如第一方面所述的呼叫方法的步骤。
第四方面，本公开提供一种EIR设备，所述EIR设备包括存储器、处理器、存储在所述存储器上并可在所述处理器上运行的程序以及用于实现所述处理器和所述存储器之间的连接通信的数据总线，所述程序被所述处理器执行时实现如第一方面所述的呼叫方法的步骤。
第五方面，本公开提供一种计算机可读存储，所述存储介质存储有一个或者多个程序，所述一个或者多个程序可被一个或者多个处理器执行，以实现如第一方面或第二方面所述的呼叫方法的步骤。
本公开提供的呼叫方法，在3GPP的4G、5G和WiFi接入网络中语音核心网IMS的解决了终端丢失、被盗后的呼叫防盗打问题，对基于IMS呼叫的移动终端在呼叫发起时的使用状态进行检测，以保证已报失的移动终端不被非法持有者使用；实现终端、卡、使用者联动身份识别；移动终端的正常呼叫与EIR检验流程的异步处理，不干扰正常呼叫且不增加时延；保障紧急呼叫的优先放通；业务网元与检测装置解耦的方式保持组网灵活性。
附图说明
图1是本公开实施例提供的一种呼叫方法用于CSCF的流程图。
图2是本公开实施例提供的一种呼叫方法用于EIR的流程图。
图3是本公开实施例提供的一种呼叫方法的网络架构。
图4是本公开实施例提供的一种呼叫方法EIR检验的流程图。
图5是本公开实施例提供的呼叫与检验异步执行的流程图。
图6是本公开实施例提供的DRA组网下EIR与CSCF解耦的流程图。
图7是本公开提供的一种电子设备的模块示意图。
图8是本公开提供的一种计算机可存储介质的示意图。
具体实施方式
为使本领域的技术人员更好地理解本公开的技术方案，下面结合附图及具体实施例进行详细描述。
在下文中将参考附图更充分地描述示例实施例，但是所述示例实施例可以以不同形式来体现且不应当被解释为限于本文阐述的实施例。反之，提供这些实施例的目的在于使本公开透彻和完整，并将使本领域技术人员充分理解本公开的范围。
在不冲突的情况下，本公开各实施例及实施例中的各特征可相互组合。
如本文所使用的，术语“和/或”包括一个或多个相关列举条目的任何和所有组合。
本文所使用的术语仅用于描述特定实施例，且不意欲限制本公开。如本文所使用的，单数形式“一个”和“该”也意欲包括复数形式，除非上下文另外清楚指出。还将理解的是，当本说明书中使用术语“包括”和/或“由……制成”时，指定存在所述特征、整体、步骤、操作、元件和/或组件，但不排除存在或添加一个或多个其它特征、整体、步骤、操作、元件、组件和/或其群组。
除非另外限定，否则本文所用的所有术语(包括技术和科学术语)的含义与本领域普通技术人员通常理解的含义相同。还将理解，诸如那些在常用字典中限定的那些术语应当被解释为具有与其在相关技术以及本公开的背景下的含义一致的含义，且将不解释为具有理想化或过度形式上的含义，除非本文明确如此限定。
在移动现网中，MSC和移动管理实体(MME，Mobility Management Entity)将设备的IMEI信息发给EIR设备，EIR设备将收到的IMEI与白、黑、灰三种名单进行比较，把结果发送给MSC和MME，以便MSC和MME决定是否允许该移动台设备进入网络。但该方式没有考虑到以下场景：VoLTE和VoWiFi的呼叫客户端主要以原生(Native)的方式集成在移动终端中，正常手机开机状态下已经完成了在IMS网络中的注册。如果不到注册刷新周期、接入网络发生切换或者关机再开机，这个已注册可通话的状态将保持。当移动终端丢失或者被盗时，用户通常会向运营商挂失。但这时，如果该终端发起呼叫甚至国际长途，呼叫会被正常拨打。由此导致的话费部分在多个项目的实际案例中都被判定为运营商承担。这种情况如果不采取措施解决，在5G甚至6G网络中同样会存在。
为解决上述移动终端安全使用问题，避免运营商和客户的损失，本公开提供的一种呼叫方法，在3GPP的4G、5G和WiFi接入网络中语音核心 网IMS的处理终端丢失、被盗后的呼叫防盗打。对基于IMS呼叫的移动终端在呼叫发起时的使用状态进行检测，终端、卡、使用者联动身份识别，保证已报失的移动终端不被非法持有者使用的同时也实现了对于紧急呼叫优先放通。通过采用移动终端的正常呼叫与EIR检验流程的异步处理的方式，不干扰正常呼叫且不增加时延，通过业务网元与检测装置解耦的方式还实现了组网灵活性。
第一方面，本公开实施例提供了一种呼叫方法，用于呼叫会话控制功能实体(CSCF，Call Session Control Function)，如图1所示，所述呼叫方法包括如下步骤：
在步骤S110中，接收初始邀请(Invite)请求；
在步骤S120中，确定所述初始Invite请求中携带的移动终端识别信息；
在步骤S130中，向设备识别寄存器EIR发送EIR状态检验请求，所述EIR状态检验请求中携带所述移动终端识别信息；
在步骤S140中，接收EIR状态检验结果，其中，所述EIR根据所述EIR状态检验请求做出所述EIR状态检验结果；
在步骤S150中，根据所述EIR状态检验结果，按照预设策略执行对应的、与呼叫相关的操作。
主叫S-CSCF收到Invite请求，根据接入网信息(PANI，P-Access-Network-Info)内容判断是VoLTE或VoWiFi接入。从Invite信息中提取发起呼叫的移动终端的IMEI或IMSI信息，主叫S-CSCF通过S13接口发给现网EIR设备。
在本实施例中，S-CSCF通过工程变更申请(ECR，Engineering Change Request)将所述EIR状态检验请求发送给EIR，EIR通过工程变更应答(ECA，Engineering Change Answer)将所述EIR状态检验结果发送给S-CSCF。
EIR设备通过本地的黑白灰名单进行比较，将比较结果通过S13返回， S-CSCF根据EIR返回的黑名单、白名单、灰名单结果，以及结果码信息。
在S-CSCF预先设置策略，针对EIR返回检测结果，决定是允许还是禁止设备的呼叫。
在移动现网中，MSC和MME可以将设备的IMEI信息发给EIR设备进行验证，以便MSC和MME决定是否允许该移动台设备进入网络。而VoLTE和VoWiFi的呼叫客户端则无法采用此方式来确认用户状态。鉴于前文所述的被盗打问题，本公开实施例针对VoLTE和VoWiFi的呼叫客户端，通过S-CSCF主动发送移动终端识别信息到EIR设备进行检验，而不必等到注册刷新周期，能够及时检测到移动终端状态是否异常，解决终端丢失、被盗后的被盗打的问题，减少了运营商的损失。
作为一种可选实施方式，在主叫的初始过滤规则iFC被触发之前，执行所述向EIR发送EIR状态检验请求的步骤。
在iFC触发呼叫流程之前，先向EIR发送EIR状态检验请求。至于iFC是否要继续触发呼叫流程，则存在两种选择：
一种选择包括：iFC触发呼叫流程，不等待EIR状态检验结果，按照正常呼叫流程继续进行。等收到EIR状态检验结果之后，再决定是否要干涉已经发生的呼叫流程。因为EIR检验与呼叫流程均按照各自的流程处理，因此称为异步流程。
另一种选择包括：iFC不触发呼叫流程，等待EIR状态检验结果。等收到EIR状态检验结果之后，再决定iFC能否触发呼叫流程。因为需要中止呼叫流程，等收到EIR检验结果之后才决定是否继续呼叫，因此与异步流程相对的，称为同步流程。
作为一种可选实施方式，所述预设策略包括第一预设规则，主叫的iFC被触发后，对满足所述iFC检测的呼叫请求触发呼叫流程；在接收到所述EIR状态检测结果后，根据第一预设规则，对已经发生的呼叫流程进行处理。
呼叫流程与EIR检验流程执行可以采用异步流程执行，S-CSCF收到呼叫请求后，会直接触发主叫的iFC检测，满足iFC的就可以直接发起呼 叫，而不必等待EIR检测的结果之后才决定是允许此呼叫。异步方式执行既不干扰现有呼叫流程，不会增加时延，又可以根据EIR检验结果来进行判断是否需要系统侧发起呼叫释放。
进一步地，所述第一预设规则，对已经发生的呼叫流程进行处理包括：若所述EIR状态检验结果为终端状态异常，则向终端发送禁止呼叫指令，以终止所述已经发生的呼叫流程；若所述EIR状态检验结果非终端状态异常，则维持所述呼叫流程。
其中，所述终端状态异常包括：所述EIR状态检验结果为检验失败、和/或所述EIR状态检验结果中的结果码为黑名单匹配。
对于异步流程中，针对EIR状态检测结果的所述第一预设规则举例具体如下：
EIR检验与呼叫采用异步流程则S-CSCF收到ECA后执行：
(1)收到ECA成功响应，result code在Result-Code中携带，当Result-Code为成功时，Equipment-Status AVPs可能填写为下面值，经与运营商确认S-CSCF的执行策略：
WHITELISTED(0)—不干涉现有流程
BLACKLISTED(1)—终止现有流程，有系统侧S-CSCF发起呼叫终结
GREYLISTED(2)—不干涉现有流程
DIAMETER_ERROR_EQUIPMENT_UNKNOWN(5422)—不干涉现有流程
(2)收到ECA失败响应，result code在Result-Code AVP中携带，除DIAMETER_ERROR_EQUIPMENT_UNKNOWN(5422)外，其他失败SIP按失败处理，终止现有流程，有系统侧S-CSCF发起呼叫终结。
作为一种可选实施方式，所述预设策略包括第二预设规则，在接收到所述EIR状态检测结果后，根据第二预设规则，进行呼叫请求iFC触发操作。
与前文所述的异步方式相对应，呼叫流程与EIR检验流程执行也可以采用同步流程执行，S-CSCF收到呼叫请求后，需要等待EIR检测的结果，然后才触发主叫的iFC检测，满足iFC的就可以发起呼叫。同步方式对呼叫的检测更严格，需要等待EIR检测的结果才决定是否允许此呼叫。
进一步地，若所述EIR状态检验结果为终端状态异常，则向发出所述初始Invite请求的终端发送禁止消息Forbidden；若所述EIR状态检验结果非终端状态异常，则进行呼叫请求iFC触发，放通呼叫。
其中，所述终端状态异常包括：
所述EIR状态检验结果为检验失败、和/或所述EIR状态检验结果中的结果码为黑名单匹配。
对于同步流程中，针对EIR状态检测结果的所述第二预设规则举例具体如下：
EIR检验与呼叫采用同步流程则S-CSCF收到ECA后的执行同现有I-CSCF实现：
(1)收到ECA成功响应，result code在Result-Code中携带，当Result-Code为成功时，Equipment-Status AVPs可能填写为下面值，经与运营商确认S-CSCF的执行策略：
WHITELISTED(0)—允许放通
BLACKLISTED(1)—禁止
GREYLISTED(2)—允许放通
DIAMETER_ERROR_EQUIPMENT_UNKNOWN(5422)—允许放通
此例外处理的依据是协议3GPP TS22.016，描述如下：
除了黑名单和白名单，管理站还有可能使用灰色名单。灰名单上的设备不被禁止使用(除非在黑名单上或不在白名单上)，但被网络追踪(用于评估或其他目的)，即：“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)收到ECA失败响应，result code在Result-Code AVP中携带，除DIAMETER_ERROR_EQUIPMENT_UNKNOWN(5422)外，其他失败SIP按失败处理。
作为一种可选实施方式，所述移动终端识别信息包括以下信息中的至少一项：
所述移动终端的国际移动设备识别码IMEI、国际移动用户识别码IMSI、公共用户标识PUI。
对于始呼场景，主叫S-CSCF需要支持S13接口的IMEI或者IMEI+PUI检查，S13接口需要携带(IMEI，IMSI)或者(IMEI，IMSI，PUI)。各字段提取方法如下：
(1)IMEI的提取方法：
如果Invite请求中携带有，则用Invite请求Contact中sip.instance字段里的IMEI信息；如果Invite没有，则用注册的(注册时需要保存IMEI)，如果注册也没有，该信息不填写；
(2)IMSI的提取方法：
S-CSCF上取注册PVI的数字部分，如果用户未注册，取HSS PVI信息中数字部分(需要判断是否是大于13位纯数字)；
在S-CSCF上提取时，IMSI优先取注册码流的Authorization头域中的username字段，格式如例：Authorization:Digest username＝"716060806302394@ims.mnc006.mcc716.3gppnetwork.org"；如果没有Authorization头域，取To字段里面的username，格式举例如下：
To:<sip:716060803237652@ims.mnc006.mcc716.3gppnetwork.org>；
如果上述方式都未取到，则取从HSS SAR获取到的PVI信息中数字部分。
(3)PUI的提取方法：
在S-CSCF上取Invite消息中From字段中PUI信息。
在ECR消息中的具体填充方式举例如下：
<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]//填写IMSI信息
*[AVP]//扩充AVP，拷贝Invite消息中From字段，含PUI信息
*[Proxy-Info]
*[Route-Record]
在终端信息属性值对(AVP，Attribute Value Pair)消息中的具体填充方式举例如下：
Terminal-Information::＝<AVP header:1401 10415>
[IMEI]//填写IMEI信息
[3GPP2-MEID]
[Software-Version]
*[AVP]
本公开实施例在基于IMEI代表终端设备，IMSI代表SIM卡基础上，增加使用者PUI信息校验。S-CSCF可以获取IMEI、IMSI、PUI，作为增 强的检验请求，同时携带3项信息，发送到EIR进行检验。可以实现终端、卡、使用者联动身份识别，进一步避免非法通话。
作为一种可选实施方式，设置EIR状态检验的标志；若EIR状态检验的标志设置为否时，接收到所述初始Invite请求后，由主叫的iFC触发呼叫流程；若EIR状态检验的标志设置为是时，在接收到所述初始Invite请求后，在主叫的iFC被触发之前，向EIR发送所述EIR状态检验请求，并根据所述EIR状态检验结果，按照预设策略执行对应的、与呼叫相关的操作。
在S-CSCF侧设置EIR状态检验的标志后，就可以在网管侧制作对应的开关，由开关状态来控制VoLTE或VoWiFi接入是否需要执行EIR设备的认证。网管侧开关为打开时，在S-CSCF侧的EIR状态检验的标志状态为“是”，表示在主叫的iFC被触发之前，无论是前文所述的异步流程还是同步流程，都需要执行EIR设备认证。网管侧开关为关闭时，在S-CSCF侧的EIR状态检验的标志状态为“否”，表示在开始呼叫流程之前不执行EIR设备认证，仍以原有的流程进行处理。
EIR状态检验的标志的默认状态为“否”。这样，可以兼容老旧设备，以及不支持进行EIR认证的设备；这样可以兼容老旧设备，以及不支持进行EIR认证的设备；
需要指出的是，在开关打开状态时，有几种特殊情况需要考虑：
当被叫号码为特服号码时，触发呼叫流程；
当所述移动终端为非VoLTE接入或非VoWifi接入时，触发呼叫流程；
当所述移动终端的呼叫的请求和注册信息中均未携带接入网信息PANI时，触发呼叫流程。
具体的实现方式，举例如下：
(1)主叫S-CSCF收到初始Invite请求，根据呼叫PANI判断终端为VoLTE或VoWiFi接入，通过S13接口向EIR发送ECR请求，消息中携带IMEI。EIR检验完成后返回成功响应，并携带黑白灰信息，黑白灰策略为：黑-禁止，白-允许，灰-允许；
(2)主叫S-CSCF收到初始Invite请求，若呼叫PANI被判断终端为非VoLTE或非VoWiFi接入，不进行EIR认证；
(3)主叫S-CSCF收到初始Invite请求，呼叫未携带PANI，取注册PANI，如果呼叫和注册都未携带PANI，不进行EIR认证。典型的场景就是，被叫号码为特服号码，如：紧急呼叫号码110、119等。此外，当地法规指定特殊号码，以及运营商自行指定的特殊号码，也可以被设定为不进行EIR认证，直接呼叫。
作为一种可选实施方式，将所述EIR状态检验请求发送给路由代理节点DRA，由所述DRA向所述EIR转发EIR状态检验请求。
DRA组网方式的一种基本场景是，CSCF(包含I-CSCF和S-CSCF)与EIR不直连，CSCF无需关注具体的EIR，EIR的选择以及管理统一归DRA。因此，CSCF只需要选择可用的DRA，消息中不指定EIR的主机名，DRA可以根据本地策略等方式来选择合适的EIR。ECR消息填充方式举例如下：
1)在DRA组网时，CSCF网元上，邻接主机的EIR类型，邻接主机名称，需要配置DRA的主机名。
2)在DRA组网时，CSCF获取邻接的EIR类型主机，发送的ECR消息中不携带Destination-Host AVP，仅携带对端域名。
Destination-Host在协议3GPP 27.229中的定义为可选。Destination-Host可以由DRA从邻接主机中邻接主机类型为EIR的邻接主机名称中获取。
消息格式举例如下：
<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]
业务模块如CSCF在具备DRA组网下，不填写Destination-Host AVP。
可以新增系统全局开关，CSCF通过开关来判断是否为DRA组网，该开关默认为“关闭”。当该开关打开时，认为是DRA组网，ECR中不填写Destination-Host AVP。
S-CSCF发送ECR请求到DRA，DRA组网ECR请求到EIR网元。EIR网元发送ECA响应到DRA，S-CSCF从DRA收到ECA响应。S-CSCF与EIR之间的不直接相连，一个S-CSCF与EIR不是一一对应，而是由DRA来实现对S-CSCF与EIR的解耦。这种场景使S-CSCF与EIR的关系更加灵活，DRA可以根据本地策略或者ECR的用户信息，选择该用户对应的EIR为目标EIR，提高检验效率。
除此之外，还可以增加S-CSCF对DRA保护切换的支持。例如：S-CSCF连接到DRA，DRA存在DRA01与DRA02的保护，当DRA01发生宕机时，S-CSCF能够访问DRA02，使S-CSCF发起的EIR状态检验流程不会因此而中断，实现对EIR状态检验流程的保护。
第二方面，本公开实施例提供了一种呼叫方法，用于EIR，如图2所示，所述呼叫方法包括如下步骤：
在步骤S160中，接收所述CSCF发送的所述EIR状态检验请求，所述EIR状态检验请求包括所述移动终端识别信息；
在步骤S170中，根据预设检验规则，得到对所述移动终端识别信息的EIR状态检验结果；
在步骤S180中，将所述EIR状态检验结果发送到所述CSCF。
主叫S-CSCF收到Invite请求后，从Invite信息中提取发起呼叫的移动终端的识别信息。主叫S-CSCF通过S13接口，向EIR发送EIR状态检验请求。
EIR设备通过本地的黑白灰名单进行比较，将比较结果通过S13返回，S-CSCF根据EIR返回的黑名单、白名单、灰名单结果，以及结果码信息。
在S-CSCF预先设置策略，针对EIR返回检测结果，决定是允许还是禁止设备的呼叫。
在移动现网中，MSC和MME可以将设备的IMEI信息发给EIR设备进行验证，以便MSC和MME决定是否允许该移动台设备进入网络。而VoLTE和VoWiFi的呼叫客户端则无法采用此方式来确认用户状态。鉴于前文所述的被盗打问题，本公开实施例针对VoLTE和VoWiFi的呼叫客户端，通过S-CSCF主动发送移动终端识别信息到EIR设备进行检验，而不必等到注册刷新周期，能够及时检测到移动终端状态是否异常，解决终端丢失、被盗后的被盗打的问题，减少了运营商的损失。
进一步地，所述根据预设检验规则，对所述移动终端识别信息的EIR状态检验结果，包括：
对所述移动终端的国际移动设备识别码IMEI、国际移动用户识别码IMSI、公共用户标识PUI进行检验，并生成所述EIR状态检验结果。
在此步骤中增加对PUI的检验，EIR在当前IMEI和IMSI数据库的基础上增加PUI数据库，S13接口(基于3GPP TS29.272)扩充增加PUI信息，EIR检验结合IMEI、IMSI和PUI进行。作为增强的检验，本公开实施例在基于IMEI代表终端设备，IMSI代表SIM卡基础上增加使用者PUI信息校验，可以实现终端、卡、使用者联动身份识别，进一步避免非法通 话。
需要指出的是，移动终端识别信息包括但不限于IMEI、IMSI、PUI，能够用于移动终端识别的其他移动终端识别信息，也属于本公开保护的范围。
下面结合3个实施例对本公开第一个方面和第二个方面所提供的方法进行介绍。
实施例1
本公开实施例1提供一种IMS系统呼叫方法的流程。如图4所示，该流程包含以下步骤：
步骤S201：主叫S-CSCF收到初始Invite请求；
步骤S202：主叫S-CSCF根据Invite请求中PANI信息判断终端为VoLTE或VoWiFi接入(是否需要做此判断可由配置开关决定)，在主叫iFC触发之前，通过S13接口向EIR发送ECR请求，消息中携带IMEI和IMSI；
需要指出的是，不同运营商可以根据实际需要灵活设置开关状态，实现了运营商选择的灵活性。
步骤S203：可选步骤1，EIR通过IMEI和IMSI判断出该终端当前在白名单内；
步骤S204：EIR返回ECA带“result code：白名单”；
步骤S205：S-CSCF收到“result code：白名单”的ECA则进行主叫iFC触发，放通呼叫到后续应用服务器(AS，Application Server)；
步骤S206：可选步骤2，EIR通过IMEI和IMSI判断出该终端当前在黑名单内；
步骤S207：EIR返回ECA带“result code：黑名单”；
步骤S208：S-CSCF收到“result code：黑名单”的ECA则拒绝呼叫，向请求终端发送403 Forbidden消息；
步骤S209：可选步骤3，EIR通过IMEI和IMSI判断出该终端当前在灰名单内；
步骤S210：EIR返回ECA带“result code：灰名单”；
步骤S211：S-CSCF收到“result code：灰名单”的ECA则进行主叫iFC触发，放通呼叫到后续AS；
步骤S212：可选步骤4，EIR通过IMEI和IMSI判断出该终端为未知设备(代码5422)；
步骤S213：EIR返回ECA带“result code：
DIAMETER_ERROR_EQUIPMENT_UNKNOWN(5422)”；
步骤S214：S-CSCF收到“result code：
DIAMETER_ERROR_EQUIPMENT_UNKNOWN(5422)”的ECA则进行主叫iFC触发，放通呼叫到后续AS；
步骤S215：可选步骤5，EIR通过IMEI和IMSI判断出该终端非以上4种情况；
步骤S216：EIR返回ECA带“result code：非5422的其它错误”；
步骤S217：S-CSCF收到“result code：非5422的其它错误”的ECA则拒绝呼叫，向请求终端发送403 Forbidden消息；
实施例2
本公开实施例2为呼叫与检验异步执行示意流程。如图5所示，该流程包含以下步骤：
步骤S301：主叫S-CSCF收到初始Invite请求；
步骤S302：主叫S-CSCF根据Invite请求中PANI信息判断终端为VoLTE或VoWiFi接入(是否需要做此判断可由配置开关决定)，在主叫iFC触发之前，通过S13接口向EIR发送ECR请求，消息中携带IMEI和IMSI；
步骤S303：主叫S-CSCF正常处理Invite消息根据iFC触发AS；
步骤S304：主叫S-CSCF收到EIR返回的ECA；
步骤S305：主叫S-CSCF根据ECA进行逻辑判断；
步骤S306：终端状态非异常，则不做任何动作，不干扰当前用户呼叫流程；
步骤S307：终端状态异常，则拒绝呼叫，向请求终端发送403 Forbidden消息；
实施例3
本公开实施例3提供一种DRA组网下EIR与CSCF解耦流程。如图6所示，该流程包含以下步骤：
步骤S401：CSCF收到终端注册请求Register消息；
步骤S402：新增系统全局开关，CSCF通过该开关来判断是否为DRA组网，该开关默认为“关闭”。当该开关打开时，认为是DRA组网，CSCF发送ECR消息给EIR，ECR消息中不填写Destination-Host AVP；
步骤S403：DRA根据本地策略或者ECR的用户信息，选择该用户对应的EIR为目标EIR，DRA从邻接主机中邻接主机类型为EIR的邻接主机名称中获取目标EIR主机名称并将其填写在ECR消息中Destination-Host AVP；
步骤S404、S405：DRA发送ECR消息到目标EIR，可选步骤S404或者S405到EIR 01或者EIR 02；
步骤S406、S407：目标EIR返回ECA判断结果，可选步骤S406或者S407由目标EIR发出；
步骤S408 DRA转发目标EIR回复的ECA消息给CSCF；
步骤S409 CSCF根据收到的ECA中“result code”进行后续处理，继续终端注册或者拒绝终端注册。
第三方面，本公开实施例提供了一种CSCF设备，所述CSCF设备包括存储器、处理器、存储在所述存储器上并可在所述处理器上运行的程序 以及用于实现所述处理器和所述存储器之间的连接通信的数据总线，所述程序被所述处理器执行时实现如第一方面所述的呼叫方法的步骤。
第四方面，本公开实施例提供了一种EIR设备，所述EIR设备包括存储器、处理器、存储在所述存储器上并可在所述处理器上运行的程序以及用于实现所述处理器和所述存储器之间的连接通信的数据总线，所述程序被所述处理器执行时实现如第二方面所述的呼叫方法的步骤。
第五方面，一种存储介质，用于计算机可读存储，所述存储介质存储有一个或者多个程序，所述一个或者多个程序可被一个或者多个处理器执行，以实现如第一方面或第二方面中任一项所述的跨区域通信方法的步骤。
本公开提供的一种呼叫方法，在3GPP的4G、5G和WiFi接入网络中语音核心网IMS的处理终端丢失、被盗后的呼叫防盗打。不仅适用于现有VoLTE，VoWiFi网络场景，还适用于后续网络如5G的VoNR。对基于IMS呼叫的移动终端在呼叫发起时的使用状态进行检测，终端、卡、使用者联动身份识别，保证已报失的移动终端不被非法持有者使用的同时也实现了对于紧急呼叫优先放通。通过采用移动终端的正常呼叫与EIR检验流程的异步处理的方式，不干扰正常呼叫且不增加时延，通过业务网元与检测装置解耦的方式还实现了组网灵活性，采用业务开关控制的方式，不同运营商可以根据实际需要灵活设置开关状态，实现了运营商选择灵活性。
本领域普通技术人员可以理解，上文中所公开方法中的全部或某些步骤、系统、设备中的功能模块/单元可以被实施为软件、固件、硬件及其适当的组合。
在硬件实施方式中，在以上描述中提及的功能模块/单元之间的划分不一定对应于物理组件的划分；例如，一个物理组件可以具有多个功能，或者一个功能或步骤可以由若干物理组件合作执行。某些物理组件或所有物理组件可以被实施为由处理器，如中央处理器、数字信号处理器或微处理器执行的软件，或者被实施为硬件，或者被实施为集成电路，如专用集成电路。这样的软件可以分布在计算机可读介质上，计算机可读介质可以包 括计算机存储介质(或非暂时性介质)和通信介质(或暂时性介质)。如本领域普通技术人员公知的，术语计算机存储介质包括在用于存储信息(诸如计算机可读指令、数据结构、程序模块或其他数据)的任何方法或技术中实施的易失性和非易失性、可移除和不可移除介质。计算机存储介质包括但不限于RAM、ROM、EEPROM、闪存或其他存储器技术、CD-ROM、数字多功能盘(DVD)或其他光盘存储、磁盒、磁带、磁盘存储或其他磁存储装置、或者可以用于存储期望的信息并且可以被计算机访问的任何其他的介质。此外，本领域普通技术人员公知的是，通信介质通常包含计算机可读指令、数据结构、程序模块或者诸如载波或其他传输机制之类的调制数据信号中的其他数据，并且可包括任何信息递送介质。
以上参照附图说明了本公开的优选实施例，并非因此局限本公开的权利范围。本领域技术人员不脱离本公开的范围和实质内所作的任何修改、等同替换和改进，均应在本公开的权利范围之内。

Claims (17)

  1. 一种呼叫方法，应用于服务呼叫会话控制实体CSCF，包括：
    接收初始邀请Invite请求；
    确定所述初始Invite请求中携带的移动终端识别信息；
    向设备识别寄存器EIR发送EIR状态检验请求，所述EIR状态检验请求中携带所述移动终端识别信息；
    接收EIR状态检验结果，其中，所述EIR根据所述EIR状态检验请求做出所述EIR状态检验结果；
    根据所述EIR状态检验结果，按照预设策略执行对应的、与呼叫相关的操作。
  2. 根据权利要求1所述的呼叫方法，其中，所述呼叫方法还包括：
    在主叫的初始过滤规则iFC被触发之前，向所述EIR发送所述EIR状态检验请求。
  3. 根据权利要求2所述的呼叫方法，其中，所述预设策略包括第一预设规则，所述呼叫方法还包括：
    主叫的iFC检测被触发后，对满足所述iFC检测的呼叫请求触发呼叫流程；
    在接收到所述EIR状态检测结果后，根据所述第一预设规则，对已经发生的呼叫流程进行处理。
  4. 根据权利要求3所述的呼叫方法，其中，所述根据所述第一预设规则，对已经发生的呼叫流程进行处理包括：
    响应于所述EIR状态检验结果为终端状态异常，则向所述移动终端发送禁止呼叫指令，以终止所述已经发生的呼叫流程；
    响应于所述EIR状态检验结果非终端状态异常，则维持所述呼叫流程。
  5. 根据权利要求4所述的呼叫方法，其中，所述终端状态异常包括：
    所述EIR状态检验结果为检验失败、和/或所述EIR状态检验结果中的结果码为黑名单匹配。
  6. 根据权利要求2所述的呼叫方法，其中，所述预设策略包括第二预设规则，所述呼叫方法还包括：
    在接收到所述EIR状态检测结果后，根据第二预设规则，进行呼叫请求iFC触发操作。
  7. 根据权利要求6所述的呼叫方法，其中，所述第二预设规则包括：
    响应于所述EIR状态检验结果为终端状态异常，则向发出所述初始Invite请求的终端发送禁止消息Forbidden；
    响应于所述EIR状态检验结果非终端状态异常，则进行所述初始Invite呼叫请求iFC触发，放通呼叫。
  8. 根据权利要求7所述的呼叫方法，其中，所述终端状态异常包括：
    所述EIR状态检验结果为检验失败、和/或所述EIR状态检验结果中的结果码为黑名单匹配。
  9. 根据权利要求1所述的呼叫方法，其中，所述移动终端识别信息包括以下信息中的至少一项：
    所述移动终端的国际移动设备识别码IMEI、国际移动用户识别码IMSI、公共用户标识PUI等。
  10. 根据权利要求1至9中任意一项所述的呼叫方法，还包括：
    设置EIR状态检验的标志；
    响应于EIR状态检验的标志设置为“否”，接收到所述初始Invite请求后，由主叫的iFC触发呼叫流程；
    响应于EIR状态检验的标志设置为“是”，在接收到所述初始Invite请求后，在主叫的iFC被触发之前，向EIR发送所述EIR状态检验请求，并根据所述EIR状态检验结果，按照预设策略执行对应的、与呼叫相关的操作。
  11. 根据权利要求1至9中任意一项所述的呼叫方法，还包括以下步骤中的至少一者：
    当被叫号码为特服号码时，触发呼叫流程；
    当所述移动终端为非VoLTE接入或非VoWiFi接入时，触发呼叫流程；
    当所述移动终端的呼叫的请求和注册信息中均未携带接入网信息PANI时，触发呼叫流程。
  12. 根据权利要求1至9中任意一项所述的呼叫方法，还包括：
    将所述EIR状态检验请求发送给路由代理节点DRA，由所述DRA向所述EIR转发EIR状态检验请求。
  13. 一种呼叫方法，应用于EIR，包括：
    接收所述CSCF发送的所述EIR状态检验请求，所述EIR状态检验请求包括所述移动终端识别信息；
    根据预设检验规则，得到对所述移动终端识别信息的EIR状态检验结果；
    将所述EIR状态检验结果发送到所述CSCF。
  14. 根据权利要求13所述的呼叫方法，其中，所述根据预设检验规则，得到对所述移动终端识别信息的EIR状态检验结果，包括：
    对所述移动终端的国际移动设备识别码IMEI、国际移动用户识别码IMSI、公共用户标识PUI进行检验，并生成所述EIR状态检验结果。
  15. 一种CSCF设备，其中，所述CSCF设备包括存储器、处理器、存储在所述存储器上并可在所述处理器上运行的程序以及用于实现所述处理器和所述存储器之间的连接通信的数据总线，所述程序被所述处理器执行时实现如权利要求1-12任一项所述的呼叫的方法的步骤。
  16. 一种EIR设备，其中，所述EIR设备包括存储器、处理器、存储在所述存储器上并可在所述处理器上运行的程序以及用于实现所述处理器和所述存储器之间的连接通信的数据总线，所述程序被所述处理器执行时实现如权利要求13-14任一项所述的呼叫的方法的步骤。
  17. 一种计算机可读存储，其中，所述存储介质存储有一个或者多个程序，所述一个或者多个程序可被一个或者多个处理器执行，以实现权利要求1至14中任一项所述的呼叫的方法的步骤。
PCT/CN2022/101066 2021-06-30 2022-06-24 呼叫方法、设备和存储介质 WO2023274055A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110734101.1 2021-06-30
CN202110734101.1A CN115550896A (zh) 2021-06-30 2021-06-30 呼叫方法、设备和存储介质

Publications (1)

Publication Number Publication Date
WO2023274055A1 true WO2023274055A1 (zh) 2023-01-05

Family

ID=84690063

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/101066 WO2023274055A1 (zh) 2021-06-30 2022-06-24 呼叫方法、设备和存储介质

Country Status (2)

Country Link
CN (1) CN115550896A (zh)
WO (1) WO2023274055A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2004537186A (ja) * 2001-03-20 2004-12-09 トムソン　ライセンシング　ソシエテ　アノニム 遠隔診断の方法およびシステム
EP1605661A1 (en) * 2004-06-07 2005-12-14 Alcatel Method and device for preventing attacks on a call server
CN102869004A (zh) * 2011-07-05 2013-01-09 中兴通讯股份有限公司 移动终端寻回及信息保护的方法及装置
CN106453799A (zh) * 2016-10-25 2017-02-22 北京动石科技有限公司 伪装通信识别方法和系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2004537186A (ja) * 2001-03-20 2004-12-09 トムソン　ライセンシング　ソシエテ　アノニム 遠隔診断の方法およびシステム
EP1605661A1 (en) * 2004-06-07 2005-12-14 Alcatel Method and device for preventing attacks on a call server
CN102869004A (zh) * 2011-07-05 2013-01-09 中兴通讯股份有限公司 移动终端寻回及信息保护的方法及装置
CN106453799A (zh) * 2016-10-25 2017-02-22 北京动石科技有限公司 伪装通信识别方法和系统

Also Published As

Publication number Publication date
CN115550896A (zh) 2022-12-30

Similar Documents

Publication Publication Date Title
EP2835027B1 (en) Call-back to a ue that has made an emergency call in a visited ims network
US20220104296A1 (en) Methods and devices for establishment of redundant pdu session
US10893069B2 (en) Diameter edge agent attack detection
CN106717041B (zh) 用于在外地网络中漫游的移动装置的增强的互联网协议多媒体子系统的服务限制和选择控制
US8949950B2 (en) Selection of successive authentication methods
JP2023553496A (ja) 第５世代（５ｇ）通信ネットワークにおいてメッセージ検証を実行するための方法、システムおよびコンピュータ可読媒体
CN112567779A (zh) 用diameter边缘代理为出站漫游订户执行时间距离安全对策的方法、系统和计算机可读介质
JP2024505791A (ja) 予想されるユーザ機器（ＵＥ）挙動パターンに基づいてインターネット・オブ・シングス（ＩｏＴ）デバイスへの５Ｇローミング攻撃を緩和するための方法、システム、およびコンピュータ読取可能媒体
CN115699840A (zh) 用于使用安全边缘保护代理（sepp）来减轻5g漫游安全攻击的方法、系统和计算机可读介质
CN104798421A (zh) 在无线通信系统中在网路拥塞状态下控制特定服务的方法和装置
EP2323332A1 (en) Controlling a session in a service provisioning system
EP2420037A2 (en) Emergency call handling in accordance with authentication procedure in communication network
US10292088B2 (en) Blocked device checking in roaming scenarios
EP2487986B1 (en) Method, device and system for processing connection of called party
WO2020037007A1 (en) Originating caller verification via insertion of an attestation parameter
WO2010127578A1 (zh) 对电信设备安全状态验证的方法、设备和系统
US20230292131A1 (en) Rogue network function re-authorization in a communication network
WO2012159312A1 (zh) 一种多模单待终端在网络注册的方法和装置
CN110324819B (zh) 副卡终端的管理方法和管理服务器
WO2023274055A1 (zh) 呼叫方法、设备和存储介质
US20230247433A1 (en) Rogue network function detection and isolation in a communication network
US11974134B2 (en) Methods, systems, and computer readable media for validating subscriber entities against spoofing attacks in a communications network
EP3972142B1 (en) Policy control function fallback
KR102440411B1 (ko) 비정상 로밍 요청 탐지 방법 및 장치
US20230156122A1 (en) Emergency call handling in a telecommunications network

Legal Events

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

Ref document number: 22831869

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE