CN117812619A - Data processing method and device - Google Patents

Data processing method and device Download PDF

Info

Publication number
CN117812619A
CN117812619A CN202211214133.XA CN202211214133A CN117812619A CN 117812619 A CN117812619 A CN 117812619A CN 202211214133 A CN202211214133 A CN 202211214133A CN 117812619 A CN117812619 A CN 117812619A
Authority
CN
China
Prior art keywords
message
dra
network element
information
udm
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
Application number
CN202211214133.XA
Other languages
Chinese (zh)
Inventor
孙凡喜
黄泽旭
陈亮
谷柏峰
李志军
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to CN202211214133.XA priority Critical patent/CN117812619A/en
Publication of CN117812619A publication Critical patent/CN117812619A/en
Pending legal-status Critical Current

Links

Landscapes

  • Mobile Radio Communication Systems (AREA)

Abstract

The application provides a data processing method and device, which are used for backing up UE related data in UE registration, so that when a UDM network element fails, the backup data is used for communication, and the disaster tolerance capability of a communication system is improved. The method comprises the following steps: the routing agent node (Diameter Routing Agent, DRA) forwarding to the unified data management (unified data management, UDM) network element a first message that may be used to request user data from the UDM network element, the first message comprising a message sent to the DRA by the first network device during registration of the user device UE; the DRA receives a first response message fed back by the UDM network element, wherein the first response message carries relevant information of the UE; the DRA stores the relevant information of the UE according to the first response message, so that the DRA can inquire the relevant information of the UE from the stored data when the UDM network element fails.

Description

Data processing method and device
Technical Field
The present disclosure relates to the field of communications, and in particular, to a data processing method and apparatus.
Background
In a communication scenario, voice or short message interaction between users, etc. are functions commonly used by users. In a communication system, there may be some devices that fail.
For example, in a fifth generation mobile communication system (5th Generation,5G) voice solution, a 5G core network+new air interface (NR) network serves as an access network for User Equipment (UE) to an IP multimedia subsystem (IP Multimedia Subsystem, IMS) core network. In the communication process, after the calling IMS sends a session initiation protocol (Session initialization Protocol, SIP) call request message to the called IMS network, the called IMS extracts the number information such as MSISDN in the SIP request message, and then obtains the corresponding relation between the MSISDN and the S-CSCF host name by inquiring in the UDM so as to find the S-CSCF network element serving the called UE. However, when the UDM fails, user data is typically imported into the VOLTE network original HSS manually to restore the traffic. The user data is led into the original EPC network HSS one by one, the leading-in efficiency is low, and the voice service is slow to recover.
Disclosure of Invention
The application provides a data processing method and device, which are used for backing up UE related data in UE registration, so that when a UDM network element fails, the backup data is used for communication, and the disaster tolerance capability of a communication system is improved.
In a first aspect, the present application provides a data processing method, including: the routing agent node (Diameter Routing Agent, DRA) forwarding to the unified data management (unified data management, UDM) network element a first message that may be used to request user data from the UDM network element, the first message comprising a message sent to the DRA by the first network device during registration of the user device UE; the DRA receives a first response message fed back by the UDM network element, wherein the first response message carries relevant information of the UE; the DRA stores the relevant information of the UE according to the first response message, so that the DRA can inquire the relevant information of the UE from the stored data when the UDM network element fails.
Therefore, in the embodiment of the present application, during the registration process of the UE, the DRA may save the relevant data of the UE. In the subsequent communication process, if the UDM network element fails completely, the DRA can also extract the related data of the UE from the stored data, so that the service of the UE can be normally executed, the disaster recovery capability of the system is improved, and the user experience is improved.
In one possible implementation, the first network device may include a serving call session control function (S-CSCF) entity, and the UE related information includes information of an IMS and information of the S-CSCF entity to which the UE corresponds.
Therefore, in this embodiment of the present application, the DRA may store information of the S-CSCF entity to which the UE belongs, including information such as a Name or an address, e.g., information such as a Server capability set (Server-Capabilities), a host Name (Server-Name), or an address, so in a subsequent re-registration or call scenario, if the UDM fails, the DRA may read information of the S-CSCF entity to which the UE belongs from the stored data, so as to ensure that the re-registration or call service may be performed normally.
In a possible implementation manner, during the process of re-registering the UE, the DRA receives a user authorization request UAR message from an inquiring-call session control function (I-CSCF) entity corresponding to the UE, where the UAR message is used to request information of an S-CSCF entity from a UDM network element; the DRA determines the fault of the UDM network element; the DRA reads information of the S-CSCF entity from the stored data, wherein the information comprises information such as names or addresses, such as Server capability sets (servers), host names (servers-names) or addresses, and the like, and generates user authorization response UAA information; the DRA feeds back UAA message to the I-CSCF entity.
In the embodiment of the application, the DRA determines that the UDM network element fails in the process of re-registering the UE, and at the moment, the information of the S-CSCF entity to which the UE belongs can be read from the stored data, so that the information of the S-CSCF entity is fed back to the I-CSCF entity. Therefore, in the process of re-registering the UE, the I-CSCF entity can acquire the information of the S-CSCF entity even if the UDM network element fails completely, so as to complete the re-registering process.
In a possible implementation manner, in a process of a call initiated by a UE, the DRA receives a location information request LIR message from an I-CSCF entity corresponding to the UE, where the LIR message is used to request information of an S-CSCF entity from a UDM network element; the DRA determines the fault of the UDM network element; the DRA reads the information of the S-CSCF entity from the stored data and generates a position information response LIA message; the DRA feeds back LIR message to the I-CSCF entity.
In the embodiment of the application, in the process of initiating a call by the UE, after determining that the UDM network element has complete faults, the DRA can read the information of the S-CSCF entity from the stored data, so that the information of the S-CSCF entity is fed back to the I-CSCF entity. Therefore, during the UE call, the I-CSCF entity can obtain the information of the S-CSCF entity to complete the call flow even if the UDM network element fails entirely.
In one possible implementation, the first network device includes an internet protocol Short Message Gateway (internet protocol-Short-Message-Gateway, IP-SM-GW), and the UE related information includes mobile station international ISDN number (Mobile Station international ISDN number, MSISDN) and IP-SM-GW information.
In the embodiment of the application, the DRA can store the information of the MSISDN and the IP-SM-GW so as to inquire the information of the IP-SM-GW based on the MSISDN of the UE when the UDM fails, thereby ensuring that the short message transmission of the UE can be normally carried out.
In one possible implementation, the DRA receives an SRI-FOR-SM (MAP send routing information FOR short message) message from a short message center (Short Message Service Center, SMSC) FOR requesting a network element FOR next hop forwarding from a UDM network element; the DRA determines the fault of the UDM network element; the DRA reads the information of the IP-SM-GW from the stored data and generates an SRI-FOR-SM response message; the DRA sends an SRI-FOR-SM response message to the SMSC.
In the embodiment of the application, in a short message transmission scene of the UE, after determining that the UDM network element has faults, the DRA can read the information of the IP-SM-GW from the stored data so as to ensure that the short message of the UE can be normally transmitted.
In a possible implementation manner, the foregoing determination, by the DRA, that the UDM network element fails may include:
the DRA determines that the feedback of the UDM network element aiming at the heartbeat maintenance message is overtime;
or, after the DRA sends the service message to the UDM network element through the C link, the preset response code is received, where the preset response code is used to indicate that the UDM network element fails, and the C link is a link between two DRAs at the same level, and the preset response code may be a pre-agreed code for identifying the total failure of the UDM network element.
Therefore, in this embodiment of the present application, the DRA may determine whether the UDM network element fails by using a heartbeat maintenance message, and further, the DRA may send a service message to the UDM network element through a C link, and if a specific response code is received, the DRA may determine that the UDM network element fails completely, so as to start a disaster recovery procedure or a failure procedure, and so on.
In a possible implementation manner, the foregoing DRA may save relevant information of the UE according to the first response message, and may include: the DRA sends relevant information of the UE to the third party entity to instruct the third party entity to save the relevant information of the UE in the database.
In the embodiment of the application, a large amount of UE related information can be saved through the third-party entity, which is equivalent to backing up the UE related information in the third-party entity, so that the disaster tolerance capability of the system is improved.
In a second aspect, the present application provides a data processing method, including:
the method comprises the steps that first network equipment sends a first message to a DRA in the process of registering UE, wherein the first message is used for requesting user data from a UDM network element;
the DRA forwards the first message to a Unified Data Management (UDM) network element;
the UDM network element reads the related information of the UE from the local and generates a first response message, wherein the first response message carries the related information of the UE;
the UDM network element sends a first response message to the DRA;
the DRA stores the relevant information of the UE according to the first response message, so that the DRA can inquire the relevant information of the UE from the stored data when the UDM network element fails.
The advantages of the second aspect and any optional embodiments of the second aspect may be referred to in the foregoing first aspect, and are not described herein.
In a possible implementation manner, the first network device includes a serving call session control function S-CSCF entity, and the relevant information of the UE includes information of an IP multimedia subsystem IMS and information of the S-CSCF entity corresponding to the UE.
In one possible embodiment, the method may further include:
the I-CSCF entity sends a user authorization request UAR message to the DRA, wherein the UAR message is used for requesting information of the S-CSCF entity from the UDM network element;
The DRA determines the fault of the UDM network element;
the DRA reads the information of the S-CSCF entity from the stored data and generates a user authorization response UAA message;
the DRA feeds back UAA message to the I-CSCF entity.
In one possible embodiment, the method may further include:
in the process of UE initiating a call, an I-CSCF entity sends a location information request LIR message to a DRA, wherein the LIR message is used for requesting information of an S-CSCF entity to a UDM network element;
the DRA determines the fault of the UDM network element;
the DRA reads the information of the S-CSCF entity from the stored data and generates a position information response LIA message;
the DRA feeds back LIR message to the I-CSCF entity.
In one possible implementation, the first network device comprises an IP short message gateway IP-SM-GW, and the UE-related information comprises information of a mobile station international integrated services digital network number MSISDN and the IP-SM-GW.
In one possible embodiment, the method may further include:
the SMSC sends SRI-FOR-SM information to the DRA, wherein the SRI-FOR-SM information is used FOR requesting a network element forwarded by the next hop to the UDM network element;
the DRA determines the fault of the UDM network element;
the DRA reads the information of the IP-SM-GW from the stored data and generates an SRI-FOR-SM response message;
the DRA sends an SRI-FOR-SM response message to the SMSC.
In a possible implementation manner, the determining, by the DRA, that the UDM network element fails may include: the DRA determines that the feedback of the UDM network element aiming at the heartbeat maintenance message is overtime; or, after the DRA sends the service message to the UDM network element through the C link, the DRA receives a preset response code, wherein the preset response code is used for indicating the fault of the UDM network element, and the C link is a link between the DRA and the UDM network element.
In a possible implementation manner, the foregoing DRA may save relevant information of the UE according to the first response message, and may include: the DRA sends relevant information of the UE to the third party entity to instruct the third party entity to save the relevant information of the UE in the database.
In a third aspect, the present application provides a communication device comprising:
a transceiver module, configured to forward a first message to the UDM network element, where the first message is used to request user data from the UDM network element, and the first message includes a message sent to the DRA by the first network device during the registration of the UE;
the receiving and transmitting module is also used for receiving a first response message fed back by the UDM network element, wherein the first response message carries the relevant information of the UE;
and the processing module is used for storing the relevant information of the UE according to the first response message, and the DRA is used for inquiring the relevant information of the UE from the stored data when the UDM network element fails.
The advantages of the third aspect and any optional embodiments of the third aspect may be referred to in the foregoing description of the first aspect, and are not repeated herein.
In a possible implementation manner, the first network device includes a serving call session control function S-CSCF entity, and the relevant information of the UE includes information of an IP multimedia subsystem IMS and information of the S-CSCF entity corresponding to the UE.
In a possible implementation manner, the transceiver module is further configured to receive a user authorization request UAR message from an I-CSCF entity corresponding to the UE during the process of re-registering the UE, where the UAR message is used to request information of the S-CSCF entity from the UDM;
the receiving and transmitting module is also used for determining the fault of the UDM network element;
the processing module is also used for reading the information of the S-CSCF entity from the stored data and generating a user authorization response (UAA) message;
and the transceiver module is also used for feeding back UAA information to the I-CSCF entity.
In one possible implementation, the transceiver module is further configured to: in the process of a call initiated by UE, the DRA receives a location information request LIR message from an I-CSCF entity corresponding to the UE, wherein the LIR message is used for requesting information of an S-CSCF entity from a UDM network element and determining the fault of the UDM network element;
The processing module is also used for reading the information of the S-CSCF entity from the stored data and generating a location information response LIA message;
and the receiving and transmitting module is also used for feeding back the LIR message to the I-CSCF entity.
In one possible implementation, the first network device comprises an IP short message gateway IP-SM-GW, and the UE-related information comprises information of a mobile station international integrated services digital network number MSISDN and the IP-SM-GW.
In a possible implementation manner, the transceiver module is further configured to receive an SRI-FOR-SM message from the short message center SMSC, where the SRI-FOR-SM message is used to request a network element FOR forwarding a next hop from the UDM network element;
the receiving and transmitting module is also used for determining the fault of the UDM network element;
the processing module is also used FOR reading the information of the IP-SM-GW from the stored data and generating an SRI-FOR-SM response message;
and the transceiver module is also used FOR sending the SRI-FOR-SM response message to the SMSC.
In one possible implementation, the transceiver module is specifically configured to:
the DRA determines that the feedback of the UDM network element aiming at the heartbeat maintenance message is overtime;
or, after the DRA sends the service message to the UDM network element through the C link, the DRA receives a preset response code, wherein the preset response code is used for indicating the fault of the UDM network element, and the C link is a link between two same-level DRAs.
In one possible implementation, the processing module is specifically configured to instruct the transceiver module to send the relevant information of the UE to the third party entity, so as to instruct the third party entity to store the relevant information of the UE in the database.
In a fourth aspect, the present application provides a communication device comprising: a processor, a memory, an input-output device, and a bus; the memory has stored therein computer instructions; the processor, when executing the computer instructions in the memory, stores the computer instructions in the memory; the processor, when executing the computer instructions in the memory, is configured to implement any one of the implementations as in the first aspect.
In a fifth aspect, the present application provides a communication system comprising: routing agent node DRA, first network device, UDM network element;
the DRA is configured to perform steps as performed by the DRA in the second aspect or in any of the alternative embodiments of the second aspect;
the first network device is configured to perform the steps performed by the first network device as in the second aspect or any optional implementation of the second aspect;
the UDM network element is adapted to perform the steps as performed by the UDM network element in the second aspect or in any alternative implementation of the second aspect.
In a sixth aspect, an embodiment of the present application provides a chip system, where the chip system includes a processor and an input/output port, where the processor is configured to implement a processing function related to the data processing method described in the first aspect, and the input/output port is configured to implement a transceiver function related to the data processing method described in the first aspect.
In a possible design, the chip system further comprises a memory for storing program instructions and data for implementing the functions related to the data processing method according to the first aspect.
The chip system can be composed of chips, and can also comprise chips and other discrete devices.
In a seventh aspect, embodiments of the present application provide a computer-readable storage medium. The computer readable storage medium has stored therein computer instructions; the computer instructions, when executed on a computer, cause the computer to perform the data processing method as described in the first aspect or any one of the possible implementations of the first aspect.
In an eighth aspect, embodiments of the present application provide a computer program product. The computer program product comprises a computer program or instructions which, when run on a computer, cause the computer to perform the data processing method as described in the first aspect or any one of the possible implementations of the first aspect.
Drawings
Fig. 1 is a schematic structural diagram of a communication system provided in the present application;
fig. 2 is a schematic structural diagram of another communication system provided in the present application;
FIG. 3 is a schematic flow chart of a data processing method provided in the present application;
FIG. 4 is a flow chart of another data processing method provided in the present application;
FIG. 5 is a flow chart of another data processing method provided in the present application;
FIG. 6 is a flow chart of another data processing method provided in the present application;
FIG. 7 is a flow chart of another data processing method provided in the present application;
fig. 8 is a schematic structural diagram of a communication device provided in the present application;
fig. 9 is a schematic structural diagram of a communication device provided in the present application.
Detailed Description
The embodiment of the application provides a data processing method and a communication processing device, which are used for guaranteeing normal communication of UE (user equipment) when UDM (universal data management) fails.
The method provided by the application can be applied to various communication scenes, such as a 5G system, a long term evolution (long term evolution, LTE) system, a global system for mobile communication (global system for mobile communication, GSM) or a code division multiple access (code division multiple access, CDMA) network, a wideband code division multiple access (wideband code division multiple access, WCDMA) network and the like, and can also be a future communication network, such as a 6G network, a 7G network and the like, and the names of the related network elements are not limited, and can be replaced by the names of the network elements with the same or similar functions in the future communication network, so the application is not limited.
Illustratively, the communication system provided herein may be as shown with reference to fig. 1. The communication system may include network elements such AS policy control functions (policy control function, PCF), policy and charging rules functions (policy and charging rules function, PCRF), routing agent nodes (Diameter Routing Agent, DRA), proxy call session control functions (proxy-call session control function, P-CSCF), session edge control (session border control, SBC), query call session control functions (interrating-call session control function, I-CSCF), serving call session control functions (serving-call session control function, S-CSCF), internet protocol Short Message gateways (internet protocol-Short-Message-Gateway, IP-SM-GW), multimedia telephony application servers (Multi Media Telephony application server, MMTel AS), service centralization and continuity application servers (service call continuity application server, SCC AS), unified data management (unified data management, UDM), home subscriber servers (home subscriber server, HSS), and the like.
The above network elements are all corresponding network elements in the existing communication network, which are not described in detail in this application. For ease of understanding, the following brief description is given by way of example, respectively.
PCF: the method is used for controlling policies such as subscription bandwidth, QOS and the like of 5G users, and can be generally integrated and deployed with PCRF network elements of an EPC network.
PCRF: the function in the EPC network is similar to the PCF network element in the 5G network, being a network element in the EPC network.
Wherein, PCF and PCRF can be combined and called PCF/PCRF.
DRA: for completing aggregation and routing forwarding of Diameter signaling.
UDM: as a user data database, user account opening data and subscription data are stored. User account opening data and subscription data are stored in a 5G network or a 2\3\4\IMS\5G converged network.
HSS: as a user database of the 2/3/4 g/ims converged network, user account opening data and subscription data are stored.
The UDM and HSS may be combined, which is called as a UDM/HSS, and when combined, the below-mentioned UDM network element in the present application may also be a network element that is combined by the HSS, and the below-mentioned UDM fault may refer to a UDM or a UDM/HSS fault. In addition, the "/" between network elements in the following embodiments of the present application may be understood as a network element co-arrangement, and will not be described in detail below.
MMTel AS: MMTel application server. Providing basic service and supplementary service of multimedia telephone; and providing a T-ADS (Terminating Access Domain Selection) function to complete the domain selection of the called party at the network side.
SCC AS: SCC application server. And is matched with SRVCC IWF and ATCF/ATGW to realize eSRVCC (enhanced Single Radio Voice Call Continuity) function.
I-CSCF: the I-CSCF follows the 3GPP TS 24.229 protocol and realizes the SIP proxy function defined by RFC3261, which is the entry point of IMS home network operator;
S-CSCF: the S-CSCF follows 3GPP TS 24.229, manages the conversation state of UE, and maintains the conversation state of service, and the S-CSCF is in the control position of the core in the conversation control layer of the whole IMS core network;
IP-SM-GW: providing a short message intercommunication function between an IMS domain and a CS domain;
P-CSCF: the P-CSCF conforms to the 3gpp TS 24.229 protocol and implements the SIP proxy function defined by RFC 3261. The P-CSCF is the first entry point of the IMS network, UE (User Equipment) finds the address of the P-CSCF by configuration or P-CSCF discovery mechanism;
SBC: network security, signaling and media proxy functions in the VoLTE/5G network are provided, and a built-in P-CSCF entity is supported.
UE: devices such as a mobile phone or a CPE are formulated in the 5G network and the EPC network. The UE may be used to provide voice/data connectivity to a user, e.g., a handheld device with wireless connectivity, or an in-vehicle device, etc. May also include smart mobile phones, mobile Stations (MSs), mobile Terminals (MTs), etc., which may also be referred to as terminal devices hereinafter. The UE may be deployed on land, including indoors or outdoors, hand-held or vehicle-mounted; can also be deployed on the water surface (such as ships, etc.); but may also be deployed in the air (e.g., on aircraft, balloon, satellite, etc.). The UE may be a terminal device (terminal device) capable of accessing a mobile network, a mobile phone (mobile phone), a tablet (pad), a computer with a wireless transceiving function, a Virtual Reality (VR) terminal, an augmented reality (augmented reality, AR) terminal, a wireless terminal in industrial control (industrial control), a wireless terminal in self driving (self driving), a wireless terminal in telemedicine (remote media), a wireless terminal in smart grid (smart grid), a wireless terminal in transportation security (transportation safety), a wireless terminal in smart city (smart city), a wireless terminal in smart home (smart home), and so on.
Some of the communication interfaces between the network elements are described below.
Rx interface: the Rx interface is located between PCRF and AF (Application Function). The Rx interface is used to exchange session information at the application level. This information will be entered as part of the policy and charging control decision made by the PCRF. The PCRF will exchange policy and charging control rules for the decision with the PCEF.
Cx interface: the Cx interface is located between the CSCF and the HSS. The information that the CX interface primarily interacts with includes: the I-CSCF (inter-Serving-Call Session Control Function) selects necessary information required for S-CSCF (Serving-Call Session Control Function), a route information query from CSCF to HSS, the CSCF obtains relevant information about roaming authorization from HSS, the CSCF downloads security parameters required for IMS user access authentication from HSS, and the HSS transfers IMS session filter subscription data to CSCF.
Sh interface: the Sh interface is located between the HSS and the SIP AS. The AS queries the HSS through the Sh interface to acquire the related data of the value-added service logic or synchronizes the related data to the HSS.
ISC interface: the ISC interface is located between the S-CSCF and the AS. The S-CSCF carries out service triggering judgment according to the IMS subscription triggering rule obtained from the HSS and the SIP service request from the IMS terminal, and routes the session to a specific AS server to finish the final processing of the value added service logic.
Mw interface: the Mw interface is located between CSCFs. The Mw interface is used for IMS registration and message communication and proxy forwarding between CSCFs in session flows.
Gm interface: the Gm interface is located between the IMS user terminal and the P-CSCF. The Gm interface is used for registration and session control of IMS users.
The method provided by the application can be used for the scenes of UE registration, re-registration in the heartbeat maintaining process, voice call or short message transmission and the like.
For example, taking one of the voice call scenarios as an example, the call flow may be as shown in fig. 2.
For example, the methods provided herein may be deployed in 5G semantic solutions. The 5G voice solution typically employs a IMS (IP Multimedia Subsystem) network voice solution of the third generation partnership project (3rd Generation Partnership Project,3GPP) standard, in which the 5G core network + NR network serves as the access network for the UE to the IMS core network. In areas where no new air interface voice-over-carrier (Voice over New Radio, VONR) is deployed, after a UE initiates a call, a 5G NR base station will drop a user back to an evolved packet core (evolved packet core, EPC) network, where an EPC network+long term evolution (Long Term Evolution, LTE) network is used as an access network from the UE to an IMS network, and the area where the VONR is deployed can complete a voice call without dropping back to the EPC and LTE networks.
In the communication process, after the calling IMS sends a session initiation protocol (Session initialization Protocol, SIP) call request message to the called IMS network, the called IMS extracts the number information such as the international ISDN number (Mobile Station international ISDN number, MSISDN) of the mobile station in the SIP request message, and then the corresponding relation between the MSISDN and the host name of the S-CSCF is required to be inquired and obtained in the UDM so as to find the S-CSCF network element serving the called UE. When UDM fails, user data is typically imported into the VOLTE network original HSS manually to restore the traffic. The recovery mode performed manually is quite low in efficiency, so that the application provides a data processing method for efficiently recovering multiple services of the UE when the UDM fails.
Referring to fig. 3, a flow chart of a data processing method provided in the present application is as follows.
301. The UE sends a registration request to the communication system.
The communication system may include various network elements, such as DRA, UDM, S-CSCF entity, I-CSCF entity, or IP-SM-GW, as shown in fig. 1, where in the process of registering the UE with the communication system, the UE may send a registration request to a device in the communication system, where the registration request carries identity information of the UE, so that the device in the communication system may verify the identity of the UE, and confirm whether the UE is registered.
302. The first network device sends a first message to the DRA.
The first network device may be a device in a communication system, for example, the first network device may include a device such as an S-CSCF entity or an IP-SM-GW.
The first message may be used to request user data, such as user account opening data or subscription data stored in the UDM, such as identity information, authentication information, or service information, from the UDM network element.
In the process of registering the UE, user data of the UE needs to be requested to the UDM, and data transmission between the first network device and the UDM network element may be forwarded by the DRA, so that when the first network device needs to send data to the UDM network element, the data may be forwarded via the DRA.
303. The DRA forwards the first message to the UDM.
The DRA, upon receiving a first message from a first network device, may forward the first message to a UDM network element.
For example, the first network device may carry routing information such as an identifier or an address of the UDM network element in the first message, and after the DRA receives the first message, it may learn that the next hop device to be forwarded is the UDM network element based on the information carried in the first message, and may forward the first message to the UDM network element. For another example, the first network device may carry the type of the first message in a first message, and the DRA may forward the type of message to the UDM network element after receiving the first message.
304. The UDM feeds back a first response message to the DRA.
After receiving the first message forwarded by the DRA, the UDM may extract information of the UE, such as user account opening data or subscription data of the UE, such as identity information, authentication information or service information, from locally stored data or from a database.
305. The DRA saves relevant information of the UE.
After receiving the first response message fed back by the UDM network element, the DRA can store the relevant information of the UE.
Specifically, the relevant information of the UE may include identification information of the UE, a mapping relationship between an IMS corresponding to the UE and the first network device, and the like.
In addition, the DRA may forward the first response message to the first network element to enable the first network to obtain the required information.
In a possible implementation manner, the first network device may include an S-CSCF entity, and the relevant information of the UE stored by the DRA may include information of an IMS of the UE and information of the S-CSCF entity, such as a mapping relationship between an IMPI/IMPU and an identity of a home S-CSCF entity. Therefore, in the scenarios of re-registration or voice call of the subsequent UE, even if the UDM network element fails, the DRA may extract information of the home S-CSCF entity, such as Server Capabilities set (Server-Capabilities), host Name (Server-Name), or address, from the stored data according to the IMS identifier corresponding to the UE, so as to facilitate the subsequent registration or voice call flow.
In one possible implementation, the first network device may also include an IP-SM-GW, i.e. the first message may be sent by the IP-SM-GW to the DRA. The relevant information of the UE stored by the DRA in this scenario may specifically include the UE identity and the information of the IP-SM-GW, for example, a mapping relationship between the MSISDN and the identity or address of the IP-SM-GW may be stored. Therefore, in the scenario of transmitting short messages by the subsequent UE, the DRA may query the corresponding IP-SM-GW based on the MSISDN of the UE, so as to implement short message transmission.
In a possible implementation manner, a third party entity, such as a server or a database, may be provided in the communication system, for storing data stored by the DRA. When the DRA stores the UE-related information, the UE-related information may be sent to a third party entity, and the third party entity may store the UE-related information in a database. When the subsequent DRA inquires the related information of the UE, the related information of the UE can be inquired from the third-party entity, and the disaster recovery capability of the communication system can be improved.
306. The DRA forwards the first response message to the first network device.
The DRA may forward the first response message to the first network device after receiving the first response message fed back by the UDM network element. The first response message carries information related to the UE, and the first network device may learn information of the UE required from the first response message, such as account opening information, authentication information, and the like of the UE.
It should be noted that, the execution sequence of the step 305 and the step 306 is not limited in this application, and the step 305 may be executed first, or the step 306 may be executed first, which may be specifically determined according to an actual application scenario.
307. The communication system feeds back a registration response to the UE.
After the network element in the communication system registers the information of the UE, a registration response can be fed back to the UE to notify that the UE has completed registration.
In the embodiment of the application, in the process of registering the UE, the DRA can store the relevant information of the UE, and when the UDM fails, the DRA can extract the relevant information of the UE from the stored data and feed the relevant information back to the responding network element. Therefore, even if the UDM fails, normal communication of the UE can be guaranteed, and user experience is improved.
In one possible scenario, if the DRA receives a user authorization request (user authorization request, UAR) message from an I-CSCF entity corresponding to the UE during the UE re-registration, the UAR message may be used to request information of the S-CSCF entity, such as information of an IP address or an identifier of the S-CSCF entity, from the UDM network element. The DRA determines the fault of the UDM network element, and can read the information of the S-CSCF entity, such as Server-Capabilities, host Name (Server-Name) or address and the like, from the stored data, and generate a user authorization response (user authorization answer, UAA) message, namely, the UAA message carries the information of the S-CSCF entity and feeds back to the I-CSCF entity. Therefore, in the re-registration process of the UE, even if the UDM network element fails, the DRA can read the information of the S-CSCF entity from the stored data so that the I-CSCF entity can acquire the information of the next hop network element to finish the re-registration of the UE.
In one possible scenario, during a call initiation procedure by a UE, the DRA receives a location information request (location info request, LIR) message from an I-CSCF entity to which the UE corresponds, where the LIR message is used to request information of an S-CSCF entity, such as information of a name or an address of the S-CSCF entity, from a UDM network element. The DRA determines the fault of the UDM network element, and can read the information of the S-CSCF entity corresponding to the UE from the stored data, generate a position information response (location info answer, LIA) message, namely, the LIA message carries the information of the S-CSCF entity, such as Server-Capabilities, host Name (Server-Name) or address and the like, and feed back the LIR message to the I-CSCF entity. Therefore, in the embodiment of the application, even if the UDM network element fails in the process of initiating the call by the UE, the DRA can read the information of the S-CSCF entity from the stored information so that the I-CSCF entity obtains the information of the next hop network element, thereby ensuring that the UE can normally call.
In one possible scenario, the aforementioned first network device may comprise an IP-SM-GW, and the data stored by the DRA may comprise a mapping relationship between MSISDN and IP-SM-GW. In the scenario where the UE transmits a short message, the SMSC may send an SRI-FOR-SM (map_ send routing information _for_short message) message to the DRA to query the UDM FOR information of the next-hop network element, i.e., information of the IP-SM-GW. The DRA determines the fault of the UDM network element, extracts the information of the IP-SM-GW from the stored data, generates an SRI-FOR-SM response message, and feeds back the SRI-FOR-SM response message to the SMSC. Therefore, in the embodiment of the application, in the scene of transmitting the short message by the UE, even if the UDM network element fails, the SMSC can be ensured to inquire the next-hop network element, thereby ensuring that the UE can finish the transmission of the short message.
In a possible implementation manner, the foregoing determination, by the DRA, that the UDM network element fails may include: the DRA determines that the feedback of the UDM network element aiming at the heartbeat maintenance message is overtime, and then the fault of the UDM network element can be determined; or when the feedback of the UDM network element aiming at the heartbeat maintenance message is timed out, the DRA can determine the fault of the UDM network element by receiving a preset response code after the service message is sent to the UDM network element through the C link. The preset response code may be a predetermined response code for indicating a failure of the UDM network element, and the C-link may be a backup link for communication between two peer DRAs.
The foregoing describes the flow of the data processing method provided in the present application, and for convenience of understanding, the flow of the method provided in the present application is described in more detail below in conjunction with a more specific application scenario.
In the method provided by the application, when the UE is registered, the DRA stores the relevant information of the UE, and in the subsequent re-registration, calling or short message scene, if the UDM network element fails, the relevant information of the UE can be read from the data stored by the DRA so as to complete the re-registration, calling or short message transmission of the UE, and the like, thereby ensuring the normal communication of the UE and improving the disaster tolerance capability of a communication system.
For ease of understanding, the present application will be described by taking registration, re-registration, calling, and short message scenarios as examples, and different scenarios will be described in detail below. It should be understood that, in the following embodiments, only the flow related to the present application is described, and some existing flows of steps may refer to related standards, which are not described in detail in the present application.
1. Registration scenario
First, a more detailed UE registration procedure will be described.
Referring to fig. 4, a flow chart of another data processing method provided in the present application is as follows.
401. The UE sends a register message to the P-CSCF/SBC entity.
When the UE initiates registration, a register message may be first sent to the P-CSCF/SBC entity, where the message may carry information about the UE, such as a unique identifier or name of the UE, to request registration of the UE in the communication system.
When the UE initiates initial registration, the authentication and authorization information in the register header field may be null or an initial value, and may specifically be sent through the Gm interface.
402. The P-CSCF/SBC entity sends a register message to the I-CSCF entity.
The P-CSCF/SBC entity may further forward the register message to the I-CSCF entity after receiving the register message.
Specifically, the P-CSCF/SBC entity may forward the register message directly to the I-CSCF entity, or may obtain a new register message after processing, and send the new register message to the I-CSCF entity for requesting registration of the UE with the I-CSCF entity.
403. The I-CSCF entity sends the UAR message to the UDM.
In order to obtain the authority of the UE, the I-CSCF entity may send, according to the received register message, a UAR message to a UDM (combined with the HSS) of the home domain through a Cx interface, where the UAR message carries user information, such as a user identifier or a corresponding IMSI identifier, so as to request to query the home S-CSCF entity of the UE.
Specifically, the message sent by the I-CSCF entity to the UDM needs to be sent to the DRA, and the DRA routes to the UDM network element DRA to the home HSS based on the IMSI/hostname, and typically the UDM and the HSS are combined, i.e. the DRA sends the UAR message to the UDM.
404. The UDM network element feeds back the UAA message to the I-CSCF entity.
If the UE is an initially registered device, the UDM may allocate a suitable S-CSCF entity to the UE, and if the UE is a non-initially registered device, the UDM may query the stored data for the S-CSCF entity corresponding to the UE. After determining that the UE is opposite to one your S-CSCF entity, a UAA message may be generated, that is, the UAA message carries information of the S-CSCF entity corresponding to the UE, such as information of an identifier or an address of the S-CSCF entity, and the UAA message is fed back to the I-CSCF entity through DRA.
405. The I-CSCF entity sends the register message to the S-CSCF entity.
After receiving the UAA message forwarded by the DRA, the I-CSCF entity can acquire the information to the S-CSCF entity, such as the information of the identifier or the address, which can be routed to the S-CSCF entity, to which the UE belongs. The I-CSCF entity may then send a register message to the S-CSCF entity to request registration of the UE with the S-CSCF entity.
406. The S-CSCF entity sends a multimedia authentication request (multimedia authorization request, MAR) message to the UDM.
After receiving the register message sent by the I-CSCF, the S-CSCF entity may send a MAR message to the UDM network element, that is, request an IMS authentication message, where relevant information of the UE is carried, for example, authentication may be performed by using a message digest algorithm 5 (MD 5) manner.
407. The UDM feeds back a multimedia authentication response (multimedia authorization answer, MAA) message to the S-CSCF entity.
After receiving the MAR message, the UDM network element can authenticate the information of the UE carried in the MAR message, and feeds back the MAA message after the authentication is passed.
408. The S-CSCF entity sends 401 a message to the P-CSCF/SBC entity.
After the S-CSCF entity receives the MAA message, it confirms that authentication for the UE is completed, and then a message, i.e. an authentication challenge message, may be sent 401 to the P-CSCF/SBC entity. The integrity protection key IK or the encryption key CK, etc. may be carried in the 401 message and passed to the P-CSCF/SBC entity via the I-CSCF entity.
409. The P-CSCF/SBC entity feeds 401 the message back to the UE.
After the P-CSCF/SBC entity receives 401 the message, it can reject CK and IK therein, and then pass the rest information, such as rest authentication element RAND/AUTH authentication algorithm, to the UE through 401 the message.
410. The UE sends a register message to the P-CSCF/SBC entity.
The foregoing steps 401-409 may be understood as an initial registration procedure of the UE, and after the UE receives the 401 authentication challenge message of the S-CSCF entity, the UE may initiate a second registration procedure, i.e. send a register message to the P-CSCF/SBC entity again.
For example, the UE may verify AUTH to determine if the network is legitimate based on an algorithm, a random number, and a shared key in the USIM card. After passing the verification, the RES/CK/IK is calculated based on the shared secret key, the RAND and the algorithm, and the digest authentication data is sent to the P-CSCF/SBC entity through the Gm port.
411. The P-CSCF/SBC entity sends a register message to the I-CSCF entity.
412. The I-CSCF entity sends the UAR message to the UDM network element.
413. The UDM network element feeds back the UAA message to the I-CSCF entity.
Steps 411 to 413 are similar to steps 402 to 404, and are not repeated here.
The difference is that the header field portion of the message may be different, such as an Authorization header field content adjustment "integrity-protected=yes" tag, indicating that the registration message is protected; and adding cell ID to the P-Access-Network-Info header field content.
414. The S-CSCF entity sends the SAR message to the UDM.
In the process of the secondary registration, the data of the UE already exists in the UDM, and the S-CSCF entity also sends SAR information to the UDM network element to request the related information of the UE from the UDM network element.
For example, the SAR message is represented by a command code 301 and a set command flag "R" for requesting the HSS (i.e. the co-located UDM network element) to download user data and requesting the HSS to store the server name currently serving the user. The SAR message is sent by the S-CSCF entity to the HSS (i.e. the co-located UDM network element) when used in the Cx interface.
415. The UDM network element feeds back the SAA message to the S-CSCF entity.
After receiving the SAR message, the UDM network element feeds back an SAA message to the S-CSCF entity aiming at the SAR message, wherein the SAA message can carry service information such as user subscription data or charging information domain.
416. The DRA stores the data.
The SAA information fed back by the UDM network element to the S-CSCF entity carries service information such as user subscription data or charging information fields, the SAA information needs to be forwarded by the DRA, and when the SAA information is received by the DRA, the DRA can read the information carried in the SAA information and store the information carried in the SAA.
Specifically, the SAA message carries information of an S-CSCF entity corresponding to the UE, such as Server-Capabilities (Server-names), host names (Server-names) or addresses of the S-CSCF entity, and the DRA can store the information of the S-CSCF entity, such as the mapping relation between the IMPU or IMPI of the UE and the Name of the S-CSCF entity to which the UE belongs.
Furthermore, in one possible scenario, a third party entity may be provided for the DRA-saved data, which may be used to save the DRA-saved data. If massive UE is accessed in a common communication system, a large amount of data needs to be stored, and the method and the device for storing the related information of the UE store a large amount of UE in a mode of setting a third-party entity, so that when a UDM network element fails, the related information of the UE can be read through the third-party entity to ensure the normal operation of the service of the UE.
417. The S-CSCF entity sends 200 a message to the P-CSCF/SBC entity.
The S-CSCF entity either returns the SIP in the original path or delivers the SIP internally, i.e. delivers 200 the message to the P-CSCF/SBC entity, i.e. the feedback for the register message in step 410.
418. The S-CSCF entity feeds back 200 the message to the UE.
Specifically, the P-Associated-URI header field of the 200 message may include two IMPUs, which may be in Tel URI and SIP URI formats, respectively, where the SIP URI format contains the user home province information, the Tel URI is used for subsequent voice calls, and the SIP URI is used for IMS network routing. The Contact header field is the IMSI, IPV6 address and port number, re-registration duration, terminal support service type, etc. of the registered successful user. The Service-Route header field contains the S-CSCF name to which the user belongs, and is sent by the S-CSCF entity to the I-CSCF entity, and then is transferred by the I-CSCF entity to the P-CSCF entity.
The P-CSCF stores the name or the identification of the home S-CSCF entity of the UE, and the name or the identification of the S-CSCF entity of the next hop can be obtained after the non-registration type SIP message sent after the UE is registered successfully reaches the P-CSCF entity, so that the subsequent flow is carried out.
419. The S-CSCF entity sends a register message to the MMTel AS/IP-SM-GW.
After the basic registration of the UE is completed, the home S-CSCF entity may initiate a third party registration, for example, send a register message to the MMTel AS/IP-SM-GW to register the short message service of the UE, where the register message may carry the identifier of the UE requesting registration.
In general, since the IP short message gateway address is not in the HSS subscription data, a data update process is required between the node and the UDM network element (fused HSS), and the data update is implemented by using a PUR/PUA process, and after the user data update is completed, the UDM network element (fused HSS) can provide routing information for the receiving short message, that is, the IP address of the IP-SM-GW.
420. The MMTel AS/IP-SM-GW sends an attribute update request (Profile Update Request, PUR) message to the UDM network element.
The PUA message is represented by a command code 307 and a set command flag "R" for the AS to request the HSS to update the transparent data or alias transparent data of the specified user.
421. The UDM network element feeds back an attribute update response (Profile Update Answer, PUA) message to the MMTel AS/IP-SM-GW.
The PUA message is represented by a command code 307 and a clear command flag "R" for replying PUR (Profile Update Request) the message, and the UDM network element, because it merges the HSS, notifies the MMTel AS/IP-SM-GW whether the update request is completed successfully or returns corresponding error information when an error occurs.
422. The DRA stores the data.
After receiving the PUA message, the DRA can read the information carried in the PUA message, wherein the message generally carries the information such as the name or address of the IP-SM-GW, and the DRA can store the information of the IP-SM-GW registered for the UE carried therein, so that in the subsequent short message transmission process, even if the UDM network element fails, the short message transmission service of the UE can be ensured.
Therefore, in the embodiment of the application, for the call or short message transmission service of the UE, the relevant information of the UE is stored by the DRA, and even if the subsequent UDM network element fails, the DRA can read the current backbone information of the UE from the stored data, so as to ensure that the call or short message transmission service of the UE can be normally executed.
2. Re-registration scenario
Illustratively, a scenario in which the UE performs re-registration may be as shown in fig. 5, as described below.
501. The UE sends a register message to the P-CSCF/SBC entity.
502. The P-CSCF/SBC entity sends a register message to the I-CSCF entity.
503. The I-CSCF entity sends the UAR message to the UDM.
Step 501 to step 503 may refer to the foregoing steps 401 to step 403, and are not described herein.
504. The DRA determines that the UDM network element failed.
After determining the fault of the UDM network element, the DRA can trigger the failure flow process.
The manner in which the DRA determines that the UDM network element fails may include various manners, such as the DRA identifying that all Diameter links of the UDM duplex (typically including the backup Device) send DWR (Device-watch-Request) HEARTBEAT and wait for DWA (Device-watch-Answer) response message timeout, or the DAR identifying that all flow control transmission protocols (Stream Control Transmission Protocol, SCTP) link HEARTBEAT requests of the UDM duplex Request, wait for the heatbeat_ack response message timeout, etc.
Optionally, when the DRA determines that the UDM network element feedback for the heartbeat maintenance message is overtime, i.e. there is no feedback, the UDM network element failure can be determined. Or on the basis that the feedback of the heartbeat maintenance message of the UDM network element is overtime, the DRA can send a service message to the UDM network element through a C link, and if the DRA receives a preset response code, such as 30002, the DRA determines that the UDM has complete fault.
505. The DRA reads data from a data node (Back End, BE).
The BE may BE understood as a third party entity for storing data, and after the DRA determines that the UDM network element fails completely, the information of the home S-CSCF entity of the UE, such as Server Capabilities set (Server-Capabilities), host Name (Server-Name), or address, may BE read from the BE.
506. The DRA feeds back UAA message to the I-CSCF entity.
After the DRA reads the information of the home S-CSCF entity of the UE from the BE, a UAA message may BE generated, where the UAA message is used to answer the UAR message, i.e. respond to the user authorization request command.
507. The I-CSCF entity sends a register message to the S-CSCF entity.
After receiving the UAA message, the I-CSCF entity sends a register message to the S-CSCF entity to instruct the S-CSCF entity to carry out a re-registration flow.
508. The S-CSCF entity does not send a MAR (Multimedia-Auth-Request) message to the UDM.
After the failed procedure is started, the S-CSCF entity closes the authentication for the re-registered user, and does not send MAR information to the DRA any more, namely the DRA does not need to carry out authentication.
509. The S-CSCF entity sends SAR (Server-Assignment-Request) message to DRA
The S-CSCF entity also sends SAR information to the DRA network element, and the DRA responds to SAA (Server-Assignment-Answer) information according to the UE user data information cached during initial registration of the UE.
Steps 508 to 509 may refer to steps 414 to 415 described above, and the difference is that the message sent to the UDM network element in fig. 4 is sent to the DRA in steps 508 to 509 and responded by the DRA, so as to implement an abnormal re-registration procedure of the UE.
Therefore, in the embodiment of the present application, in the process of re-registering the UE, even if the UDM fails, the DRA may extract information related to the UE from the stored data, such as routing information of a next hop network element, so that the UE may complete re-registration of the abnormal flow under the condition of the UDM failure.
3. Call scenario
For example, reference may be made to fig. 6 for a call scenario, as described below.
601. The last hop network element sends an invite message to the I-CSCF entity.
After the UE initiates the call request, the calling RRC setup procedure may be triggered by sending an INVITE message, where the INVITE message includes the number of the called party, the media type and coding supported by the calling party, etc.
During the call, the last hop network element, such as the P-CSCF entity, sends an invite message to the I-CSCF entity to request the UE to initiate the call. The invite message may carry a user identifier of the called UE.
602. The I-CSCF entity sends the LIR message to the UDM network element.
The I-CSCF entity sends the LIR message to the UDM network element, which may carry the user identity of the called UE, to request the S-CSCF entity to which the called UE is registered.
For example, the LIR message is represented by a command code 302 and a set command flag "R" for requesting acquisition of the name of the S-CSCF currently serving the UE. The LIR message is sent by the I-CSCF entity to the HSS when used in the Cx interface.
603. The DRA determines that the UDM network element failed.
Step 603 may refer to the related description of step 504, which is not described herein.
604. The DRA inquires the BE about the S-CSCF entity corresponding to the UE.
After the DRA determines that the UDM network element has complete faults, the information of the S-CSCF entity registered by the called UE, such as the name or the identifier of the S-CSCF entity registered by the called UE, and the like, can BE queried from the data stored by the BE based on the user identifier of the called user, and LIR information is generated, wherein the LIR information carries the name or the identifier of the S-CSCF entity registered by the called UE.
605. The DRA feeds back LIA message to the I-CSCF entity.
The DRA replaces the UDM network element to feed back the generated LIA message to the I-CSCF entity.
For example, the LIA message is represented by a command code 302 and a clear command flag "R" for providing server address or capability set information of the S-CSCF to which the UE belongs in response to the LIR message, i.e., in response to the location information request command. The LIA message is sent by the HSS to the I-CSCF when used in the Cx interface.
606. The I-CSCF entity sends an invite message to the S-CSCF entity.
After determining the S-CSCF entity to which the called UE belongs, the I-CSCF entity can send an invite message, namely the first message of the sip call, to the S-CSCF entity, wherein the initial message carries the user identification of the called UE.
607. The S-CSCF entity sends an invite message to the SCC AS entity.
After receiving the invite request from the I-CSCF entity, the S-CSCF entity needs to send the invite request to the SCC AS entity to complete the called domain selection, i.e. to confirm whether the called is under the IMS network or the non-CS network.
608. The ACC AS entity sends UDR (User Data Request) a message to the DRA.
After receiving the invite request message from the S-CSCF entity, the SCC AS entity sends UDR (User Data Request) message (the message needs to be forwarded by DRA) to the UDM entity, requesting to obtain user data, including user identity data, service subscription data, and domain information of the called user.
609. The DRA queries whether there is S-CSCF information.
After the DRA determines that the UDM network element has complete faults, the DRA can replace the UDM network element to realize the response to the UAA.
The DRA may query the BE for the presence of the home S-CSCF entity, if so, the feedback domain selection result is the IMS domain, and if only CS (circuit switched) is present, the feedback domain selection result is the CS domain (indicating that the UE is accessed from the 2G or 3G network).
If the DRA can query the BE to obtain the corresponding S-CSCF hostname of the IMPU of the called UE, if the S-CSCF hostname exists, the UDA (User Data Answer) response message returns to RAT-TYPE as 1004, and if only CS exists, the feedback RAT-TYPE is 1000 (indicating 3G) or 1001 (indicating 2G).
610. The DRA feeds back UDA messages to the SCC AS entity.
After the DRA queries from the BE whether the S-CSCF exists or not, the UDA message can BE fed back to indicate that the called domain is an IMS domain or a CS domain.
611. The SCC AS entity sends an invite message to the S-CSCF entity.
After the SCC AS entity determines that the domain currently corresponding to the called UE is IMS, the SCC AS sends an invite request to the S-CSCF entity.
612. The S-CSCF entity sends an invite message to the visited domain.
After receiving the invite request from SCC AS, S-CSCF entity can send invite message to P-CSCF/SBC entity in visited domain of called UE so AS to implement call to called UE.
Therefore, in the embodiment of the application, even if the UDM network element fails in the process of initiating a call by the calling UE, the DRA can read the data from the stored data to replace the UDM network element to respond, so that a normal call flow can be performed, and the call service of the UE is completed.
4. Short message transmission
For the short message scenario, reference may be made to fig. 7, as follows.
701. The SMSC sends an SRI-FOR-SM message to the DRA.
In the scene of transmitting short messages by UE, the SMSC sends SRI-FOR-SM messages to the UDM network element through DRA, wherein the SRI-FOR-SM messages carry user identification of the UE so as to request the network element forwarded by the next hop.
FOR example, the SRI-FOR-SM message may be used FOR the SMSC to the HSS to which the called subscriber belongs to obtain the called UE home MSC (mobile switching center) information and routing information to transfer the short message sent by the calling UE to the domain in which the called subscriber is located.
702. The DRA acknowledges the UDM network element full failure.
Step 702 may refer to the related description of step 504, which is not described herein.
703. The DRA queries the BE for the IP-SM-GW address.
After the DRA confirms the fault of the UDM network element, the DRA can inquire the information such as the identification or address of the next hop network element, namely the IP-SM-GW, from the BE and generate an SRI-FOR-SM response message.
704. The DRA sends an SRI-FOR-SM response message to the SMSC.
After generating the SRI-FOR-SM response message in place of the UDM network element, the DRA can send the SRI-FOR-SM response message to the SMSC so that the SMSC can know the identification or address of the IP-SM-GW according to the SRI-FOR-SM response message to forward the short message to the IP-SM-GW.
The embodiment of the present application only introduces some of the flows in the short message transmission process, and may further include other steps, for example, steps after forwarding to the IP-SM-GW, and may refer to related standards, which are not described in detail in the present application.
Therefore, in the embodiment of the application, even if the UDM fails, the DRA can read the related data from the stored data and replace the UDM to feed back, so that the short message transmission service of the UE can be normally performed, and the user experience is improved in the scene of the UDM failure.
The foregoing describes the flow of the method provided by the present application, and the following describes an apparatus for performing the method provided by the present application.
A communication device provided in the embodiments of the present application is described below, and in one embodiment of the present application, the communication device may be a DRA, or may be a chip or a chip system in the DRA, and the communication device may be used to perform the steps performed by the DRA in the embodiments shown in fig. 3 to fig. 7, and reference may be made to the related description in the foregoing method embodiments.
Referring to fig. 8, a schematic structural diagram of a communication device provided in the present application includes:
a transceiver module 801, configured to forward a first message to a UDM network element, where the first message is used to request user data from the UDM network element, and the first message includes a message sent to a DRA by a first network device during a registration process of a UE;
the transceiver module 801 is further configured to receive a first response message fed back by the UDM network element, where the first response message carries relevant information of the UE;
A processing module 802, configured to store relevant information of the UE according to the first response message, so that the DRA queries relevant information of the UE from the stored data when the UDM network element fails.
In a possible implementation manner, the first network device includes a serving call session control function S-CSCF entity, and the relevant information of the UE includes information of an IP multimedia subsystem IMS and information of the S-CSCF entity corresponding to the UE.
In a possible implementation manner, the transceiver module 801 is further configured to receive a user authorization request UAR message from an I-CSCF entity corresponding to the UE during the process of re-registering the UE, where the UAR message is used to request information of an S-CSCF entity from the UDM, and determine that the UDM network element fails;
the processing module 802 is further configured to read information of the S-CSCF entity from the stored data, and generate a user authorization response UAA message;
the transceiver module 801 is further configured to feed back the UAA message to the I-CSCF entity.
In one possible implementation, the transceiver module 801 is further configured to: in the process of a call initiated by UE, the DRA receives a location information request LIR message from an I-CSCF entity corresponding to the UE, wherein the LIR message is used for requesting information of an S-CSCF entity from a UDM network element and determining the fault of the UDM network element;
The processing module 802 is further configured to read information of the S-CSCF entity from the stored data, and generate a location information response LIA message;
the transceiver module 801 is further configured to feed back the LIR message to the I-CSCF entity.
In one possible implementation, the first network device comprises an IP short message gateway IP-SM-GW, and the UE-related information comprises information of a mobile station international integrated services digital network number MSISDN and the IP-SM-GW.
In a possible implementation manner, the transceiver module 801 is further configured to receive an SRI-FOR-SM message from the short message center SMSC, where the SRI-FOR-SM message is used to request a network element FOR forwarding a next hop from the UDM network element;
a transceiver module 801, configured to determine a fault of the UDM network element;
a processing module 802, configured to read information of the IP-SM-GW from the stored data, and generate an SRI-FOR-SM response message;
the transceiver module 801 is further configured to send an SRI-FOR-SM response message to the SMSC.
In one possible implementation, the transceiver module 801 is specifically configured to: determining feedback timeout of the UDM network element for the heartbeat maintenance message; or after the C link sends the service message to the UDM network element, receiving a preset response code, wherein the preset response code is used for indicating the fault of the UDM network element, and the C link is a link between the DRA and the UDM network element.
In one possible implementation, the processing module 802 is specifically configured to instruct the transceiver module to send relevant information of the UE to the third party entity, so as to instruct the third party entity to store the relevant information of the UE in the database.
The present application further provides a communication apparatus 900, referring to fig. 9, in an embodiment of the present application, the communication apparatus may be a DRA, or a chip or a system on a chip located in the DRA, where the communication apparatus may be used to perform the steps performed by the DRA in the embodiments shown in fig. 3-7, and reference may be made to the related descriptions in the above method embodiments.
The communication device 900 includes: a processor 901, a memory 902, an input output device 903, and a bus 904.
In a possible implementation, the processor 901, the memory 902, and the input output device 903 are each connected to the bus 904, where the memory stores computer instructions.
The transceiver module 801 in the foregoing embodiment may be specifically the input/output device 903 in the present embodiment, so that detailed implementation of the input/output device 903 is not described herein.
It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, which are not repeated herein.
In another possible design, when the communication device is a chip, the chip includes: a processing unit, which may be, for example, a processor, and a communication unit, which may be, for example, an input/output interface, pins or circuitry, etc. The processing unit may execute the computer-executable instructions stored in the storage unit, so that the chip performs the data processing method of any one of the above-mentioned soil 3-fig. 7. Alternatively, the storage unit is a storage unit in the chip, such as a register, a cache, or the like, and the storage unit may also be a storage unit in the terminal located outside the chip, such as a read-only memory (ROM) or other type of static storage device that may store static information and instructions, a random access memory (random access memory, RAM), or the like.
The processor referred to in any of the foregoing may be a general purpose Central Processing Unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to control the execution of programs in the data processing method.
In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product.
The computer program product includes one or more computer instructions. When loaded and executed on a computer, produces a flow or function in accordance with embodiments of the present invention, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by a wired (e.g., coaxial cable, fiber optic, digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer readable storage medium may be any available medium that can be stored by a computer or a data storage device such as a server, data center, etc. that contains an integration of one or more available media. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid State Disk (SSD)), etc.
In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods may be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.
The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in each embodiment of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.
The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be embodied in essence or a part contributing to the prior art or all or part of the technical solution in the form of a software product stored in a storage medium, including several instructions to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
The above embodiments are merely for illustrating the technical solution of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit and scope of the corresponding technical solutions.

Claims (28)

1. A method of data processing, comprising:
the routing agent node DRA forwards a first message to a Unified Data Management (UDM) network element, wherein the first message is used for requesting user data from the UDM network element, and the first message comprises a message sent to the DRA by first network equipment in the process of registering User Equipment (UE);
the DRA receives a first response message fed back by the UDM network element, wherein the first response message carries relevant information of the UE;
and the DRA stores the related information of the UE according to the first response message so that the DRA queries the related information of the UE from the stored data when the UDM network element fails.
2. The method according to claim 1, wherein the first network device comprises a serving call session control function, S-CSCF, entity, and the UE related information comprises information of an IP multimedia subsystem, IMS, corresponding to the UE and information of the S-CSCF entity.
3. The method according to claim 2, wherein the method further comprises:
in the process of re-registering the UE, the DRA receives a user authorization request UAR message from an inquiring-calling session control function I-CSCF entity corresponding to the UE, wherein the UAR message is used for requesting the information of the S-CSCF entity from the UDM network element;
The DRA determines that the UDM network element fails;
the DRA reads the information of the S-CSCF entity from the stored data and generates a user authorization response UAA message;
the DRA feeds back the UAA message to the I-CSCF entity.
4. A method according to claim 2 or 3, characterized in that the method further comprises:
in the process of the UE initiating a call, the DRA receives a location information request LIR message from an I-CSCF entity corresponding to the UE, wherein the LIR message is used for requesting information of the S-CSCF entity from the UDM network element;
the DRA determines that the UDM network element fails;
the DRA reads the information of the S-CSCF entity from the stored data and generates a location information response LIA message;
the DRA feeds back the LIR message to the I-CSCF entity.
5. The method according to any of claims 1-4, wherein the first network device comprises an IP short message gateway, IP-SM-GW, and the UE related information comprises a mobile station international integrated services digital network number, MSISDN, and information of the IP-SM-GW.
6. The method of claim 5, wherein the method further comprises:
the DRA receives an SRI-FOR-SM message from a short message center SMSC, wherein the SRI-FOR-SM message is used FOR requesting a network element forwarded by a next hop from the UDM network element;
The DRA determines that the UDM network element fails;
the DRA reads the information of the IP-SM-GW from the stored data and generates an SRI-FOR-SM response message;
the DRA sends the SRI-FOR-SM response message to the SMSC.
7. The method according to any of claims 2-4, 6, wherein the DRA determining the UDM network element failure comprises:
the DRA determines that the feedback of the UDM network element aiming at the heartbeat maintenance message is overtime;
or after the DRA sends the service message to the UDM network element through a C link, the DRA receives a preset response code, where the preset response code is used to indicate that the UDM network element is faulty, and the C link is a link between two peer DRAs.
8. The method according to any of claims 1-7, wherein the DRA storing relevant information for the UE according to the first response message comprises:
and the DRA sends the relevant information of the UE to a third party entity so as to instruct the third party entity to store the relevant information of the UE in a database.
9. A data processing method for use in a communication system, the method comprising:
the method comprises the steps that first network equipment sends a first message to a routing agent node DRA in the process of registering user equipment UE, wherein the first message is used for requesting user data from the UDM network element;
The DRA forwards the first message to a Unified Data Management (UDM) network element;
the UDM network element reads the related information of the UE from the local and generates a first response message, wherein the first response message carries the related information of the UE;
the UDM network element sends the first response message to the DRA;
and the DRA stores the relevant information of the UE according to the first response message, so that the DRA can inquire the relevant information of the UE from the stored data when the UDM network element fails.
10. The method according to claim 9, wherein the first network device comprises a serving call session control function, S-CSCF, entity, and the UE related information comprises information of an IP multimedia subsystem, IMS, corresponding to the UE and information of the S-CSCF entity.
11. The method according to claim 10, wherein the method further comprises:
the query-call session control function (I-CSCF) entity sends a User Authorization Request (UAR) message to the DRA, wherein the UAR message is used for requesting the information of the S-CSCF entity to the UDM network element;
the DRA determines that the UDM network element fails;
the DRA reads the information of the S-CSCF entity from the stored data and generates a user authorization response UAA message;
The DRA feeds back the UAA message to the I-CSCF entity.
12. The method according to claim 10 or 11, characterized in that the method further comprises:
in the process of the UE initiating a call, an I-CSCF entity sends a location information request LIR message to the DRA, wherein the LIR message is used for requesting the information of the S-CSCF entity to the UDM network element
The DRA determines that the UDM network element fails;
the DRA reads the information of the S-CSCF entity from the stored data and generates a location information response LIA message;
the DRA feeds back the LIR message to the I-CSCF entity.
13. The method according to any of claims 9-12, wherein the first network device comprises an IP short message gateway, IP-SM-GW, and the UE related information comprises a mobile station international integrated services digital network number, MSISDN, and information of the IP-SM-GW.
14. The method of claim 13, wherein the method further comprises:
the short message center SMSC sends SRI-FOR-SM information to the DRA, wherein the SRI-FOR-SM information is used FOR requesting a network element forwarded by the next hop to the UDM network element;
the DRA determines that the UDM network element fails;
the DRA reads the information of the IP-SM-GW from the stored data and generates an SRI-FOR-SM response message;
The DRA sends the SRI-FOR-SM response message to the SMSC.
15. The method according to any of claims 10-12, 14, wherein the DRA determining the UDM network element failure comprises:
the DRA determines that the feedback of the UDM network element aiming at the heartbeat maintenance message is overtime;
or after the DRA sends the service message to the UDM network element through a C link, the DRA receives a preset response code, where the preset response code is used to indicate that the UDM network element is faulty, and the C link is a link between two peer DRAs.
16. The method according to any of claims 9-15, wherein the DRA storing relevant information for the UE according to the first response message comprises:
and the DRA sends the relevant information of the UE to a third party entity so as to instruct the third party entity to store the relevant information of the UE in a database.
17. A communication device, comprising:
a transceiver module, configured to forward a first message to a unified data management UDM network element, where the first message is used to request user data from the UDM network element, and the first message includes a message sent to the DRA by a first network device in a process of registering a user equipment UE;
The transceiver module is further configured to receive a first response message fed back by the UDM network element, where the first response message carries relevant information of the UE;
and the processing module is used for storing the related information of the UE according to the first response message, and the DRA is used for inquiring the related information of the UE from the stored data when the UDM network element fails.
18. The apparatus according to claim 17, wherein the first network device comprises a serving call session control function, S-CSCF, entity, and the UE related information comprises information of an IP multimedia subsystem, IMS, corresponding to the UE and information of the S-CSCF entity.
19. The apparatus of claim 18, wherein the device comprises a plurality of sensors,
the transceiver module is further configured to receive a user authorization request UAR message from an I-CSCF entity of a query-call session control function corresponding to the UE in a process of re-registering the UE, where the UAR message is used to request information of the S-CSCF entity to the UDM;
the receiving and transmitting module is further used for determining the fault of the UDM network element;
the processing module is also used for reading the information of the S-CSCF entity from the stored data and generating a user authorization response UAA message;
And the receiving and transmitting module is further used for feeding back the UAA message to the I-CSCF entity.
20. The device according to claim 18 or 19, wherein,
the receiving and transmitting module is further configured to, in a process of the UE initiating a call, receive, by the DRA, a location information request LIR message from an I-CSCF entity corresponding to the UE, where the LIR message is used to request information of the S-CSCF entity to the UDM network element;
the receiving and transmitting module is further used for determining the fault of the UDM network element;
the processing module is further used for reading the information of the S-CSCF entity from the stored data and generating a location information response LIA message;
and the receiving and transmitting module is further used for feeding back the LIR message to the I-CSCF entity.
21. The apparatus according to any of claims 17-20, wherein the first network device comprises an IP short message gateway, IP-SM-GW, and the UE related information comprises a mobile station international integrated services digital network number, MSISDN, and information of the IP-SM-GW.
22. The apparatus of claim 21, wherein the device comprises a plurality of sensors,
the receiving and transmitting module is further configured to receive an SRI-FOR-SM message from a short message center SMSC, where the SRI-FOR-SM message is used to request a network element forwarded by a next hop to the UDM network element;
The receiving and transmitting module is further used for determining the fault of the UDM network element;
the processing module is further used FOR reading the information of the IP-SM-GW from the stored data and generating an SRI-FOR-SM response message;
the transceiver module is further configured to send the SRI-FOR-SM response message to the SMSC.
23. The apparatus according to any one of claims 18-20, 22, wherein the transceiver module is specifically configured to:
determining feedback timeout of the UDM network element for the heartbeat maintenance message;
or, after sending the service message to the UDM network element through a C link, receiving a preset response code, where the preset response code is used to indicate that the UDM network element is faulty, and the C link is a link between the two peer DRAs.
24. The device according to any one of claims 17-23, wherein,
the processing module is specifically configured to instruct the transceiver module to send the relevant information of the UE to a third party entity, so as to instruct the third party entity to store the relevant information of the UE in a database.
25. A communication apparatus, characterized in that the communication processing apparatus comprises: a processor coupled to the memory;
the memory is used for storing a computer program;
The processor configured to execute the computer program stored in the memory, to cause the communication processing apparatus to execute the data processing method according to any one of claims 1 to 7.
26. A communication system, the communication system comprising: routing agent node DRA, first network device, UDM network element;
the DRA being configured to perform the steps performed by the DRA according to any of claims 9 to 16;
the first network device being configured to perform the steps performed by the first network device of any of claims 9 to 16;
the UDM network element being adapted to perform the steps performed by the UDM network element according to any of claims 9 to 16.
27. A computer program product containing instructions which, when run on a computer, cause the computer to perform the method of any one of claims 1 to 8.
28. A computer readable storage medium comprising instructions which, when run on a computer, cause the computer to perform the method of any one of claims 1 to 8.
CN202211214133.XA 2022-09-30 2022-09-30 Data processing method and device Pending CN117812619A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202211214133.XA CN117812619A (en) 2022-09-30 2022-09-30 Data processing method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202211214133.XA CN117812619A (en) 2022-09-30 2022-09-30 Data processing method and device

Publications (1)

Publication Number Publication Date
CN117812619A true CN117812619A (en) 2024-04-02

Family

ID=90420684

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202211214133.XA Pending CN117812619A (en) 2022-09-30 2022-09-30 Data processing method and device

Country Status (1)

Country Link
CN (1) CN117812619A (en)

Similar Documents

Publication Publication Date Title
EP2080344B1 (en) Methods and apparatuses for registering a terminal in the ims over a circuit-switched access domain
CN100596084C (en) Method for accessing IMS network to mobile circuit domain user and its registering method
EP2835027B1 (en) Call-back to a ue that has made an emergency call in a visited ims network
US10757645B2 (en) Access control in communications network comprising slices
US9021014B2 (en) Methods, systems, and computer readable media for providing home subscriber server (HSS) proxy
EP2938043B1 (en) Method of access provision
US20220338152A1 (en) Support for ims routing with multiple ims pdu sessions over different 5gc slices
CN109995721B (en) Service request processing method, device and communication system
US8582564B2 (en) Method for providing a roaming service between heterogeneous networks and system therefor
US8935374B2 (en) Method, system, and device for realizing registration mechanism of IP multimedia subsystem
WO2007128221A1 (en) A method and system of routing and addressing for short message
US8782743B2 (en) Methods and apparatus for use in a generic bootstrapping architecture
JP6537919B2 (en) Subscriber information registration method, communication service device and program
WO2009117413A2 (en) A mobile switching center platform having interfaces with functionalities defined by an architecture that provides packet-switched multimedia subscriber services
WO2008134930A1 (en) Method, apparatus and system for message processing in ims network
US9060005B2 (en) Method, apparatus, system and related computer program product for handover management
KR101513451B1 (en) Apparatus for inducing re-registration in wireless communication systems and method thereof
CN117812619A (en) Data processing method and device
WO2023093271A1 (en) Method and apparatus for determining s-cscf
KR101360151B1 (en) Method of sip message transmission between gruu users in ims network, and device of the same
KR101629815B1 (en) 3G Mobile Communication System supporting Service Centralized and Continuity and Method thereof
US9173184B2 (en) Mobile communication system supporting service centralization and continuity and method thereof
CN117896707A (en) Calling method, system, equipment and storage medium based on integration of satellite and Internet of vehicles
CN117397220A (en) System and method for facilitating routing of primary numbers

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