WO2008025257A1 - An intercommunication method and a communication system between different networks - Google Patents

An intercommunication method and a communication system between different networks Download PDF

Info

Publication number
WO2008025257A1
WO2008025257A1 PCT/CN2007/002564 CN2007002564W WO2008025257A1 WO 2008025257 A1 WO2008025257 A1 WO 2008025257A1 CN 2007002564 W CN2007002564 W CN 2007002564W WO 2008025257 A1 WO2008025257 A1 WO 2008025257A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
service identifier
communication command
receiving
unit
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.)
Ceased
Application number
PCT/CN2007/002564
Other languages
English (en)
French (fr)
Inventor
Youzhu Shi
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 EP07800783A priority Critical patent/EP2056556A4/en
Publication of WO2008025257A1 publication Critical patent/WO2008025257A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M7/00—Arrangements for interconnection between switching centres
    • H04M7/12—Arrangements for interconnection between switching centres for working between exchanges having different types of switching equipment, e.g. power-driven and step by step or decimal and non-decimal
    • H04M7/1205—Arrangements for interconnection between switching centres for working between exchanges having different types of switching equipment, e.g. power-driven and step by step or decimal and non-decimal where the types of switching equipement comprises PSTN/ISDN equipment and switching equipment of networks other than PSTN/ISDN, e.g. Internet Protocol networks
    • H04M7/128—Details of addressing, directories or routing tables
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1069—Session establishment or de-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2101/00—Indexing scheme associated with group H04L61/00
    • H04L2101/30—Types of network names
    • H04L2101/38—Telephone uniform resource identifier [URI]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2101/00—Indexing scheme associated with group H04L61/00
    • H04L2101/30—Types of network names
    • H04L2101/385—Uniform resource identifier for session initiation protocol [SIP URI]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/30—Managing network names, e.g. use of aliases or nicknames
    • H04L61/301—Name conversion
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/1016—IP multimedia subsystem [IMS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/08—Protocols for interworking; Protocol conversion
    • H04L69/085—Protocols for interworking; Protocol conversion specially adapted for interworking of IP-based networks with other networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2242/00—Special services or facilities
    • H04M2242/04—Special services or facilities for emergency applications

Definitions

  • the present invention relates to data transmission technologies in the field of communications, and in particular, to a method and a communication system for interworking between different networks. Background technique
  • IP Multimedia Subsystem IP Multimedia
  • IMS 3rd Generation Partnership Project
  • 3GPP 3rd Generation Partnership Project
  • 3G 3rd Generation
  • the IMS adopts the IP packet domain as the bearer channel for its control signaling and media transmission, and uses the Session Initiation Protocol (SIP) as the call control signaling, which realizes the separation of service management, session control and bearer access.
  • SIP Session Initiation Protocol
  • the SIP protocol is an application layer control protocol for establishing, changing, and terminating multimedia sessions or calls. These multimedia sessions include multimedia conferencing, distance learning, Internet telephony, etc., and its core is the Internet Engineering Task Force (IETF). Standard organization definition, but in different networks and applications, there are different set specifications, such as IMS-defined IMS set SIP protocol, and there is also an integrated service digital network defined by the International Telecommunication Union-Telecommunication Standards Department (Integrated Services Digital Network) Network, ISDN) ISDN User Part (ISUP) SIP-I protocol for signaling.
  • ITU-T International Telecommunication Union-Telecommunication Standardization Sector
  • ETSI European Telecommunications Standards Institute
  • IMS interworking generally refers to communication between an IMS network and a heterogeneous network, and between IMS networks of different operators.
  • Heterogeneous networks include traditional circuit networks and other IP-based multimedia networks, ie IP-based but non-IMS-based multimedia networks, such as public switched telephone networks.
  • PSTN Public Switched Telephone Network
  • ISDN Integrated Services Digital Network
  • PLMN Public Land Mobile Network
  • MGCF Media Gateway Control Function
  • IBCF Interconnection Border Control Function
  • I-CSCF Interrogating Call Session Control Function
  • IBCF Interrogating Call Session Control Function
  • different networks refer to IMS networks and heterogeneous networks of different operators, and any network having different service identification protocols may be referred to as different networks.
  • the call information initiated by the user needs to be confirmed at both ends of the network.
  • the call information protocols of the two ends of the network may be different, or the identifiers defined by different operators for the same service may be different, the consequences of the call for the service identifier cannot be completed. Therefore, service identification between the two ends of the network is required. Convert to complete the call for the service identity between the networks at both ends.
  • the purpose of the embodiments of the present invention is to provide a method and a communication system for interworking between different networks, so as to solve the problem that the communication service for the service identifier cannot be completed when the IMS is intercommunicated in the prior art. question.
  • a network inter-network interworking device is provided between the transmitting side and the receiving side, and the device includes:
  • a service identifier conversion unit configured to receive a communication command on the sending side, and obtain a receiving side service identifier corresponding to the sending side service identifier according to the correspondence between the sending side service identifier and the receiving side service identifier, where the sending side communication
  • the command includes the sending side service identifier, and then sends a communication command including the receiving side service identifier to the receiving side.
  • a method for implementing interworking between different networks includes: receiving, by the first network side, a communication command including a service identifier of the first network side, according to services on the first network side and the second network side Corresponding relationship of the identifier, the second network side service identifier corresponding to the first network side service identifier is found, and the communication command including the second network side service identifier is sent to the second network side.
  • a communication system provided by an embodiment of the present invention includes a first network side and a second network side, the system further includes one or more network interworking devices, and the first network passes through one or more network interworking devices and Two networks connected;
  • the network interworking device is configured to: after receiving the communication command from the device of the previous node, convert the service identifier of the sending side in the communication command into the communication identifier according to the obtained correspondence between the sending side service identifier and the receiving side service identifier. Receiving the service identifier, and then transmitting the communication command after the service identifier is converted to the next network interworking device connected thereto until the communication command is sent to the second network side.
  • the network interworking is implemented by converting the service identifiers on the network side of the two ends, and the communication service problem for the service identifier, such as the call service, the subscription/notification service, and the message service, can be completed, and the service interworking function is implemented.
  • the service interworking function is implemented.
  • the IMS network can better inherit the services of the traditional circuit network and facilitate the evolution of the traditional circuit network to the IMS network.
  • FIG. 2 is a schematic structural diagram of a network interworking device according to an embodiment of the present invention.
  • FIG. 3 is another schematic structural diagram of a network interworking device according to an embodiment of the present invention.
  • FIG. 4 is a schematic flowchart of a method for implementing interworking in different networks according to Embodiment 1 of the present invention
  • FIG. 5 is a schematic flowchart of a method for implementing interworking from an IMS network of an Internet Protocol Multimedia Subsystem to a different network of a traditional circuit according to Embodiment 2 of the present invention
  • FIG. 6 is a schematic flow chart of implementing an interworking method by two network interworking devices according to Embodiment 3 of the present invention.
  • FIG. 7 is a schematic flow chart of implementing an interworking method by two network interworking devices according to Embodiment 4 of the present invention.
  • FIG. 8 is a schematic flowchart of a method for implementing interworking between a traditional circuit network and an Internet Protocol multimedia subsystem IMS network according to Embodiment 5 of the present invention
  • FIG. 9 is a schematic flowchart of a method for implementing interworking from an Internet Protocol Multimedia Subsystem IMS network to a legacy circuit network according to Embodiment 6 of the present invention.
  • FIG. 10 is a schematic flowchart of a method for implementing interworking from an Internet Protocol Multimedia Subsystem IMS Network A to an Internet Protocol Multimedia Subsystem IMS Network B according to Embodiment 7 of the present invention. detailed description
  • the network interworking is implemented by converting the service identifiers on the network side of the two ends, and the communication service problem for the service identifier, such as the call service, the subscription/notification service, and the message service, can be completed, and the service interworking function is implemented.
  • the communication system of the embodiment of the present invention includes a first network side and a second network side, and further includes one or more network interworking devices, and the first network side passes one or more network interworking devices and the first The two network sides are connected.
  • the network interworking device includes: a correspondence relationship storage unit 21 and a service identity conversion unit 22.
  • the correspondence relationship storage unit 21 is configured to store and provide the service identifier conversion unit 22 Correspondence between the sending side service identifier and the receiving side service identifier.
  • the service identifier conversion unit 22 is configured to: after obtaining the communication command sent by the sending side, find the corresponding receiving side service identifier in the corresponding relationship storage unit 21 according to the service identifier of the sending side, and insert the receiving side service identifier into the communication command, Send this communication command to the receiving side.
  • the service identification conversion unit 22 further includes: a receiving unit 31, a converting unit 32, a converted service identification inserting unit 33, and a transmitting unit 34.
  • the receiving unit 31 is configured to receive a sending side communication command of the sending side service identifier.
  • the converting unit 32 is configured to find, in the correspondence between the sending side service identifier and the receiving side service identifier, the receiving side service identifier corresponding to the sending side service identifier included in the communication command.
  • the converted service identifier insertion unit 33 is configured to insert the receiving side service identifier into the communication command.
  • the sending unit 34 is configured to send a communication command including the receiving side service identifier to the receiving side.
  • the correspondence relationship storage unit 21 may include a plurality of storage entities, such as a network node entity, a network server entity, a network hard disk, or a network driver.
  • the correspondence between the sending side service identifier and the receiving side service identifier may be stored in the storage entity in any order. It can also be stored according to a specific requirement. For example, if it is desired to speed up the processing when an emergency call is initiated, all emergency service identifiers may be stored in a specific storage entity, and the service identity conversion unit obtains the emergency service identity of the transmitting side and directly goes to the specific storage. Find in the entity to improve the efficiency of finding emergency services.
  • the first network side is the transmitting side of the network interworking device
  • the second network side is the receiving side of the network interworking device.
  • each network interworking device receives the communication service request from the previous node device, and then according to the corresponding relationship between the stored transmission side service identifier and the receiving side service identifier. Transmitting the service identifier of the sending side in the communication service request into the receiving side service identifier, and then transmitting the communication service request after converting the service identifier to the next network interworking device connected thereto until the communication service request is sent to the second network side.
  • the network interworking device 41 is configured to obtain, after obtaining a communication command sent by the transmitting side, a receiving side service identifier corresponding to the sending side service identifier included in the communication command, and then The communication command of the receiving side service identifier is forwarded to the receiving side.
  • the network interworking device 41 includes a service identification conversion unit 51 and a correspondence relationship storage unit 52.
  • the service identifier conversion unit 51 is configured to obtain, after obtaining the communication command sent by the transmitting side, the receiving side service identifier corresponding to the sending side service identifier included in the communication command, and forward the communication command including the receiving side service identifier to the receiving side.
  • the correspondence relationship storage unit 52 is configured to store and use the correspondence between the call sending side service identifier and the receiving side service identifier provided to the service identifier converting unit 51.
  • the service identification conversion unit 51 includes: a receiving unit 61, a converting unit 62, a converted service identification inserting unit 63, and a transmitting unit 64.
  • the receiving unit 61 is configured to receive a sending side communication command of the sending side service identifier.
  • the converting unit 62 is configured to find, in the correspondence between the sending side service identifier and the receiving side service identifier, the receiving side service identifier corresponding to the sending side service identifier included in the communication command.
  • the converted service identifier insertion unit 63 is configured to insert the receiving side service identifier into the communication command.
  • the sending unit 64 is configured to send a communication command including the receiving side service identifier to the receiving side.
  • the transmitting side of the network interworking device 41 is an IMS network
  • the receiving side is an IP multimedia subsystem network or a heterogeneous network or an external network interworking device.
  • the transmitting side is a heterogeneous network
  • the receiving side is an IMS network or a heterogeneous network or an external network interworking device.
  • the transmitting side is an external network interworking device
  • the receiving side is an IMS network or a heterogeneous network or an external network interworking device.
  • the external network interworking device may be the network interworking device 41 in the embodiment of the present invention, or may be a device capable of realizing the network interworking function in other networks.
  • the network interworking device 41 may be located in a service control unit, a Call Session Control Function (CSCF), an MGCF, an IBCF, or an Interworking Fundation (IFF).
  • CSCF Call Session Control Function
  • MGCF MGCF
  • IBCF Interworking Fundation
  • IFF Interworking Fundation
  • the service control unit completes the service control function of the IMS network, and can implement a service processing function, such as an application server (Application Server, AS), or implement a service trigger function, and trigger the service to be processed on the application server, such as a service agent. (Service Broker);
  • a service processing function such as an application server (Application Server, AS)
  • AS Application Server
  • service trigger function such as a service trigger function
  • FIG. 3 is an example of interworking between an IMS network and a heterogeneous network, illustrating a network in the embodiment of the present invention. Schematic diagram of the structure of the interworking device.
  • the IMS network is the transmitting side and the heterogeneous network is the receiving side.
  • the call session control unit is a core network element in the IMS network, and performs functions such as session control and registration services.
  • the call session control unit and the receiving unit 61 are connected by a SIP protocol
  • the sending unit 64 is connected to the heterogeneous network by using an E1 interface.
  • the sending unit 64 can be connected to the heterogeneous network through other network interworking devices, and the transmitting unit 64 and the other network interworking devices adopt an E2 interface.
  • the network interworking device 41 performs the signaling translation function between the SIP protocol and the E1/E2 interface protocol, and performs the service identifier conversion function between the identity formats supported by the SIP protocol and the E1/E2 interface protocol respectively.
  • the network interworking device 41 may be located on the MGCF, and the E1 interface protocol is traditional circuit domain inter-office signaling such as the integrated service digital network user part signaling.
  • the network interworking device 41 may be located on the IBCF, the IWF, and the E1 interface protocol may be a packet signaling such as a SIP protocol or an H.323 protocol other than the IMS set.
  • a communication system when a communication system includes only one network interworking device, a schematic diagram of a method for implementing interworking between different networks, the method mainly includes the following steps:
  • Step 401 The user initiates a communication service, inserts a transmission side service identifier in the communication command, and routes the communication command to the conversion unit 32.
  • the user terminal or the user may perform the task of inserting the sending side service identifier in the communication command.
  • the sending side is the IMS network
  • the calling session control unit may also perform the insertion and sending in the communication command.
  • Side business identifies this task.
  • the method of inserting the service identifier in the communication command is: If the sending side is the IMS network, the service identifier may be inserted in the header field of the Request Provider (RequestURI) of the SIP INVITE message according to the definition of the IETF.
  • the service identifier in the IMS network can be saved not only in the SIP INVITE message, but also in other SIP messages, such as command response messages.
  • ACK information message
  • MESSAGE response message
  • SS7 SS7
  • the service identifier, the service identifier of the heterogeneous network may be stored in other parameters of the SS7 signaling, or may be stored in other protocols, such as the H.323 protocol.
  • the service identifier may include an emergency service identifier, such as a fire alarm, a police or emergency service, a called service identification, a card number service identifier, a billing notification service identifier, a reverse billing service identifier, a conference service identifier, a message service identifier, and the like.
  • the message service refers to services such as instant messaging and short message.
  • the called address information is already included in the request message.
  • the call session control unit in the IMS network determines, according to the called address information, which network the call needs to be processed. For example, if the called address is in the local network, no subsequent network interworking process is required; if the called address is in another IMS network or a heterogeneous network, the call session control unit routes the request message and subsequent other communication commands to the receiving. In unit 31, it is then resent into conversion unit 32.
  • the sending side is a heterogeneous network, the heterogeneous network itself can also determine which network the communication service needs to be processed according to the called address information.
  • the heterogeneous network routes the communication command to the receiving. In unit 31, it is then resent into conversion unit 32.
  • Step 402 The converting unit 32 converts the sending side service identifier into a receiving side service identifier.
  • the conversion method is: after the conversion unit 32 receives the transmission side service identifier, it immediately goes to the correspondence relationship storage unit 21 to perform a search.
  • the service identifier corresponding to the traditional circuit network in China is the telephone number 120.
  • the converting unit 32 After receiving the service identifier UMSi:sosiirstaid on the transmitting side, the converting unit 32 obtains the corresponding service identifier 120 of the receiving side according to the found correspondence, that is, the conversion of the sending side and the receiving side service identifier is completed.
  • Step 403 The converted service identifier insertion unit 33 inserts the converted service identifier into the communication command.
  • the converted service identifier insertion unit 33 inserts the converted service identifier into the communication command, if the converted service identifier is a service identifier of the heterogeneous network, the service identifier can be inserted in the called user identifier of the SS7 signaling. .
  • This service identifier can be stored in other parameters of the SS7 signaling, or can be stored in other protocols, such as the H.323 protocol.
  • the converted business identifier is IMS business
  • the service identifier may be inserted in the RequestURI header field of the SIP INVITE message according to the definition of the IETF.
  • the service identifier in the IMS network may be stored not only in the SIP INVITE message but also in other SIP messages, such as ACK, MESSAGE. , response message, etc.; can be saved not only in the RequestURI header field of the SIP message, but also in other headers i or other message bodies of the SIP message.
  • Step 404 The transmitting unit 34 forwards the converted communication command to the corresponding service processing portion on the receiving side. At this time, the receiving side returns a response message of the above communication command, and the response message is sent to the transmitting side user in the reverse order of the route through the network interworking device.
  • the IMS network is used as the transmitting side, and the traditional circuit network is the receiving side.
  • the user in the IMS network initiates a fire emergency call, and the Public Safety Access Point (PSAP) is located in the traditional circuit network.
  • PSAP Public Safety Access Point
  • Step 501 The user initiates a fire emergency call on the IMS network side, and the user terminal inserts the fire emergency service identifier in the fire emergency communication command after detecting the fire emergency call.
  • the method of inserting the fire emergency service identifier may be: inserting URN: sos.fire in the RequestURI header field of the SIP INVITE message according to the definition of the IETF, indicating that an emergency call is initiated, and the emergency type is a fire alarm.
  • the user terminal sends a fire emergency call inserted with the fire emergency service identifier to the call session control unit, and the unit determines, by using the called address information in the request message, that the emergency call needs to be processed by the PSAP located in the traditional circuit network, and then The fire emergency communication command is routed to the receiving unit 31 and then resent to the conversion unit 32.
  • Step 502 After receiving the fire emergency communication command, the converting unit 32 converts the fire emergency service identifier in the IMS network into a fire emergency service identifier of the traditional circuit network.
  • the conversion mode is: the conversion unit 32 obtains the correspondence between the service identifier in the IMS network and the service identifier in the heterogeneous network in the corresponding relationship storage unit 21, and then finds the difference according to the correspondence relationship according to the service identifier in the IMS network. Construct the corresponding service identifier in the network.
  • the fire emergency service identifier is a telephone number 119.
  • the conversion unit 32 needs to convert the emergency service identity URN:sos.fire in the emergency communication command into the emergency service identity 119 in the legacy circuit network. That is, according to the correspondence of the saved service identifiers, the service identifier 119 in the traditional circuit network corresponding to the service identifier URN:sos.fire in the IMS network is found, that is, the conversion of the service identifiers on the transmitting side and the receiving side is completed.
  • Step 503 The converted service identifier insertion unit 33 inserts the converted service identifier into the communication command.
  • the insertion method is: inserting the 119 in the called subscriber identity of the SS7 signaling, and then the transmitting unit 34 forwards the communication command for inserting the converted service identifier to the PSAP in the legacy circuit network.
  • Step 504 After receiving the above communication command, the PSAP recognizes that this is an emergency call, and the emergency type is a fire alarm, and then completes the corresponding processing of the emergency call. At the same time, the response message of the communication command is returned to the user on the transmitting side, and the interworking between the IMS network on the transmitting side and the traditional circuit network on the receiving side is completed.
  • the IMS network is used as the transmitting side
  • the traditional circuit network is the receiving side
  • the user in the IMS network initiates a fire emergency call
  • the public safety access point is used.
  • PSAP is located in the traditional circuit network to illustrate the steps of interworking between two networks through two network interworking devices in this case:
  • Step 601 The user initiates a fire emergency call on the IMS network side, and the user terminal inserts a fire emergency service identifier in the fire emergency communication command after detecting the fire emergency call.
  • the method of inserting the fire emergency service identifier may be: inserting URN: sos.fire in the RequestURI header field of the SIP INVITE message according to the definition of the IETF, indicating that an emergency call is initiated, and the emergency type is a fire alarm.
  • the user terminal sends a fire emergency call inserted with the fire emergency service identifier to the call session control unit, and the unit determines, by using the called address information in the request message, that the emergency call needs to be processed by the PSAP located in the traditional circuit network, and then The fire emergency communication command is routed to the receiving unit of the first network interworking device, and then sent to the conversion unit.
  • Step 602 After receiving the fire emergency communication command, the conversion unit of the first network interworking device converts the fire emergency service identifier in the IMS network into the fire emergency service identifier on the receiving side.
  • the conversion mode is: the conversion unit of the first network interworking device obtains the IMS network in the entity storing the correspondence The corresponding relationship between the service identifier in the network and the service identifier of the receiving side, and then the corresponding service identifier in the receiving side can be found according to the corresponding relationship according to the service identifier in the IMS network.
  • the fire emergency service identifier is set to the priority header field
  • the conversion unit of the first network interworking device converts the emergency service identifier URN:sos.fire in the emergency call request. to the receiving side in ES_Flag, such as setting "emergency" 0 in the header field priority (priority) of
  • Step 603 The converted service identification insertion unit of the first network interworking device inserts the converted service identifier into the communication command.
  • the insertion method is: inserting an emergency service identifier emergency into the priority of the SIP INVITE message, and then the sending unit forwards the communication command for inserting the converted service identifier to the second network interworking device.
  • Step 604 The second network interworking device performs an identity conversion function.
  • the second network interworking device converts the emergency service identifier emergency inserted in the priority of the SIP INVITE message into the emergency service identifier of the traditional circuit network.
  • the fire emergency service identifier is a telephone number 119
  • the conversion unit of the second network interworking device obtains the correspondence between the emergency and the traditional circuit network service identity in the entity storing the corresponding relationship, and searches
  • the receiving side service identifier 119 is inserted into the called subscriber identity of the SS7 signaling, and then the transmitting unit forwards the communication command for inserting the converted service identifier to the PSAP in the legacy circuit network.
  • the second network interworking device may also adopt other schemes to implement the function of service identifier conversion.
  • Step 605 When the PSAP receives the above communication command, it recognizes that this is an emergency call, and the emergency type is a fire alarm, and then the corresponding processing of the emergency call is completed. At the same time, a response message is returned to the user on the transmitting side to complete the communication between the IMS network on the transmitting side and the traditional circuit network on the receiving side.
  • Embodiment 4 is still when the communication system includes two network interworking devices, the IMS network is the transmitting side, the traditional circuit network is the receiving side, and the users in the IMS network initiate a fire emergency call, and the public safety access point (PSAP) is located in the traditional
  • PSAP public safety access point
  • the situation in the circuit network is different from that in the third embodiment.
  • the service identifiers identified by the second network interworking device in the fourth embodiment are different from those in the sixth embodiment.
  • the network interworking modes of the two ends are implemented by two network interworking devices:
  • Step 701 The user initiates a fire emergency call on the IMS network side. After detecting the fire emergency call, the user terminal inserts a fire emergency service identifier into the fire emergency communication command.
  • the way to insert a fire emergency service identifier can be: According to the definition of the IETF, in the SIP INVITE message
  • Inserting URN sos.fire in the RequestURI header field indicates that an emergency call is initiated, and the emergency type is a fire alarm.
  • the user terminal sends a fire emergency call inserted with the fire alarm 'emergency service identifier to the call session control unit, and the unit determines that the emergency call needs to be processed by the PSAP located in the traditional circuit network by using the called address information in the request message.
  • the fire emergency communication command is then routed to the receiving unit of the first network interworking device, which in turn transmits the fire emergency communication command to the conversion unit.
  • Step 702 After receiving the fire emergency communication command, the conversion unit of the first network interworking device converts the fire emergency service identifier in the IMS network into the fire emergency service identifier on the receiving side.
  • the conversion mode is: the conversion unit of the first network interworking device obtains the correspondence between the service identifier in the IMS network and the service identifier of the receiving side in the entity storing the corresponding relationship, and then according to the service identifier in the IMS network, according to the corresponding The relationship finds the corresponding service identifier in its receiving side.
  • the fire emergency service identifier identified by the second network interworking device is a telephone universal resource identifier (TEL URI) format, such as: TEL: 119, and the conversion unit of the first network interworking device sets the emergency service identifier in the emergency call request.
  • TEL URI telephone universal resource identifier
  • URN The sos.fire is converted into the emergency service identity TEL: 119 in the receiving side.
  • Step 703 The converted service identifier insertion unit of the first network interworking device inserts the converted service identifier into the communication command.
  • the insertion method is: inserting an emergency service identifier TEL: 119 in the RequestURI of the SIP INVITE message, and then the transmitting unit forwards the communication command for inserting the converted service identifier to the second network interworking device.
  • Step 704 The second network interworking device performs an identity conversion function.
  • the second network interworking device inserts the emergency service into the RequestURI of the SIP INVITE message.
  • Identification TEL: 119 is converted into an emergency service identity of a traditional circuit network.
  • the fire emergency service identifier is the telephone number 119
  • the conversion unit of the second network interworking device obtains the correspondence between the TEL: 119 and the service identifier of the traditional circuit network in the entity storing the corresponding relationship.
  • the receiving side service identifier 119 is found, and the 119 is inserted in the called user identifier of the SS7 signaling, and then the sending unit forwards the communication command for inserting the converted service identifier to the PSAP in the traditional circuit network.
  • the second network interworking device may also adopt other schemes to implement the function of service identifier conversion; Step 705: After the PSAP receives the above communication command, it recognizes that this is an emergency call, and the emergency type is a fire alarm, and then the emergency call is completed accordingly. deal with. Interworking between 0 simultaneously, but also returns a response message sent to the user side, the IMS network to complete the transmission side and the reception side of the conventional circuit network
  • the traditional circuit network is used as the transmitting side, and the IMS network is the receiving side.
  • the user in the traditional circuit network initiates an emergency call, and the PSAP is located in the IMS network.
  • the steps of interworking between the two ends of the network are:
  • Step 801 The user initiates an emergency call on the traditional circuit network side, and inserts an emergency service identifier in the called user identifier of the SS7 signaling.
  • an emergency service identifier For example, the emergency service uniform number in Europe is 112, indicating that an emergency call is initiated.
  • the traditional circuit network judges that the emergency call needs to be processed by the PSAP located in the IMS network by using the called address information in the request message, and then the emergency communication command inserted into the emergency service identifier is routed to the receiving unit 31, and then It is sent to the conversion unit 32.
  • Step 802 After receiving the emergency communication command, the converting unit 32 converts the emergency service identifier in the traditional circuit network into an emergency service identifier of the IMS network.
  • the corresponding relationship storage unit 21 finds the service identifier U N:sos in the IMS network corresponding to the service identifier 112 in the obtained conventional circuit network, that is, the conversion of the service identifiers on the transmitting side and the receiving side is completed.
  • Step 803 The converted service identifier insertion unit 33 inserts the converted service identifier into the communication command.
  • the transmitting unit 34 forwards the communication command to the call session control unit that handles the emergency service.
  • Step 804 After receiving the emergency communication command, the call session control unit routes the request to the PSAP in the IMS network. After receiving the communication command, the PSAP recognizes that this is an emergency call, and then completes the corresponding processing of the emergency call. . At the same time, a response message is returned to the user on the transmitting side to complete the interworking between the traditional circuit network on the transmitting side and the IMS network on the receiving side.
  • the IMS network is used as the transmitting side, and the traditional circuit network is the receiving side.
  • the user in the IMS network initiates the called pay service, and the called party is located in the traditional circuit network.
  • the network interworking steps at both ends are:
  • Step 901 On the IMS network side, the user initiates a called pay communication command, such as calling a company service center, and using the called pay service.
  • the user inserts the called pay service identifier in the communication command, such as the SIP INVITE communication command message insertion header field P-Called-Charged: true abc@abc.com, to indicate the called pay service that initiates a certain telephone number.
  • the user terminal sends a communication command that has been inserted into the called payment service identifier to the call session control unit, and the unit determines that the call needs to be processed by the traditional circuit network by using the called address information in the request message, and is then called
  • the payment communication command is routed to the receiving unit 31 and then resent to the conversion unit 32.
  • Step 902 After receiving the called payment communication command, the converting unit 32 converts the called payment service identifier in the IMS network into the called payment service identifier in the traditional circuit network.
  • the conversion unit 32 finds the service identifier of the IMS network in the correspondence relationship storage unit 21.
  • the service identifier in the traditional circuit network corresponding to the P-Called-Charged: true-abc@abc.com is the telephone number.
  • Step 903 The converted service identifier insertion unit 33 inserts the converted service identifier into the communication command.
  • the converted service identifier insertion unit 33 inserts the converted service identifier into the communication command by inserting the service identifier 800-12345678 into the called subscriber identifier of the SS7 signaling, and then the sending unit 34 forwards the communication command to the legacy circuit.
  • the traditional circuit network After receiving the communication command, the traditional circuit network identifies that the call is a called service according to the service identifier, and then forwards the communication command to the service center of the company, and implements the called payment service according to the called payment identifier.
  • a response message is returned to the user on the transmitting side to complete the interworking between the IMS network on the transmitting side and the traditional circuit network on the receiving side.
  • the IMS network A is the transmitting side, and the other IMS network B is the receiving side.
  • the user in the IMS network A initiates the card number service, and the called party is located in the IMS network B of the other carrier.
  • the IMS network A and the IMS network B use different card number service identifiers.
  • the network interworking steps at both ends are:
  • Step 1001 On the IMS network A side, the user initiates a card number service communication command. After detecting the communication command, the user terminal inserts a card number service identifier TEL: 201 in the RequestURI header field of the SIP INVITE message, and a subsequent card number and password, indicating This is a card number business.
  • TEL card number service identifier
  • the user terminal forwards the communication command inserted with the card number service identifier to the call session control unit, and the unit determines that the call needs to be processed by the IMS network B of another operator by using the called address information in the request message, and then the The communication command is routed to the receiving unit 31 and then resent to the converting unit 32.
  • Step 1002' After receiving the card number service communication command, the conversion unit 32 converts the card number service identifier TEL: 201 in the IMS network A into a card number service identifier TEL: 202 in the IMS network B.
  • the service identifier TEL: 202 in the IMS network B corresponding to the service identifier TEL: 201 in the obtained IMS network A is found, that is, the conversion of the service identifiers on the transmitting side and the receiving side is completed.
  • Step 1003 The converted service identifier insertion unit 33 inserts the converted service identifier into the communication command.
  • the converted service identification insertion unit 33 inserts the converted service identifier into the communication command by inserting the converted card number service identifier TEL: 202 in the RequestURI header field of the SIP INVITE message, and then the transmitting unit 34 forwards the inserted TEL: 202 Communication commands to IMS network B.
  • Step 1004 After receiving the communication command, the IMS network B identifies that the card number service is based on the service identifier, and then implements the card number service. At the same time, it also returns a response message to the sending side. The user completes the interworking between the IMS network A on the transmitting side and the IMS network B on the receiving side.
  • the network communication between the network side of the two ends is implemented by the embodiment of the present invention, and the service identifiers of the network side of the two ends are inconsistent due to the inconsistency of the signaling protocols supported by the respective networks, and/or the identifiers defined by the respective carriers are resolved.
  • the problem is that the communication service problem for the service identifier, such as the call service, the subscription/notification service, the message service, etc., can be completed, and the service interworking function is realized.
  • the service interworking function is realized for the user, in a different network, a consistent service experience can be obtained, and the continuity and consistency of the service are improved, thereby improving the user's satisfaction.
  • the IMS network can better inherit the services of the traditional circuit network and facilitate the evolution of the traditional circuit network to the IMS network.
  • the spirit and scope of the invention Thus, it is intended that the present invention cover the modifications and variations of the inventions

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Multimedia (AREA)
  • Telephonic Communication Services (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Description

一种不同网络间互通的方法及通信系统 技术领域
本发明涉及通信领域的数据传输技术， 尤其涉及一种不同网络间互通的 方法及通信系统。 背景技术
互联网协议 ( Internet Protocol, IP ) 多媒体子系统 （ IP Multimedia
Subsystem, IMS )是由第三代移动通信标准化伙伴项目 （ 3rd Generation Partnership Project, 3GPP )标准定义的， 是第三代（ 3rd Generation, 3G )移动 网实现分组话音和分组数据， 提供统一的多媒体业务和应用的目标网络。
IMS采用 IP分组域作为其控制信令和媒体传输的承载通道， 采用会话发 起协议 ( Session Initiation Protocol, SIP )作为呼叫控制信令， 实现了业务管 理、 会话控制及承载接入的三者分离。
SIP协议是一个用于建立、更改和终止多媒体会话或呼叫的应用层控制协 议， 这些多媒体会话包括多媒体会议、 远程教学、 因特网电话等， 它的核心 由因特网工程部 （Internet Engineering Task Force, IETF )标准组织定义， 但 是在不同网絡及应用中， 有不同的集合规范， 如有 IMS定义的 IMS集 SIP协 议， 此外还有国际电信联盟-电信标准部定义的可以封装综合业务数字网 ( Integrated Services Digital Network, ISDN )用户部分（ ISDN User Part, ISUP ) 信令的 SIP-I协议等。
目前， 其它国际标准组织， 如国际电信联盟-电信标准部（International Telecommunication Union - Telecommunication Standardization Sector, ITU-T )、 欧洲电信标准协会 ( European Telecommunications Standards Institute, ETSI ) 等也采用 IMS作为其定义的核心网络。
现在， 随着网络技术的发展和网络的普及， 在不同网络间互通运用的范 围越来越广。 其中， · IMS互通一般指的是在 IMS网络和异构网络之间、 '以及 不同运营商的 IMS网络之间的通讯。 异构网絡包括传统电路网络和其它基于 IP的多媒体网络， 即基于 IP但非 IMS的多媒体网络，前者如公共电话交换网
( Public Switched Telephone Network, PSTN )、 综合业务数字网 （Integrated Services Digital Network, ISDN 公用陆地移动通信网 （Public Land Mobile Network, PLMN ) 等， IMS 和传统电路域网络之间采用媒体网关控制功能
( Media Gateway Control Function, MGCF ) 互通； 后者如视听及多媒体系统 等， IMS 和其它基于 IP 的多媒体网络之间采用互通边界控制功能
( Interconnection Border Control Function, IBCF )互通。不同运营商之间的 IMS 网络可以采用问询呼叫会话控制功能 ( Interrogating Call Session Control Function, I-CSCF )、 IBCF互通。
在本发明中， 不同网络是指不同运营商的 IMS网络和异构网络中， 只要 是业务标识协议不同的网络就可以称之为不同网络。
当前 IMS网络和异构网络或不同运营商的 IMS网络互通时，如果呼叫的 被叫号码不是一个用户标识而是一个业务标识， 用户发起的呼叫信息需要在 两端网络得到确认。 但由于两端网络的呼叫信息协议可能不同， 或者不同运 营商给同一种业务定义的标识可能不同， 会造成无法完成针对业务标识的呼 叫这一后果， 所以需要在两端网絡之间进行业务标识转换， 来完成两端网络 之间针对业务标识的呼叫。 但是， 现有技术中没有给出 IMS网络和异构网络 或不同运营商的 IMS网络之间的业务标识转换的具体实现方法， 导致在 IMS 互通时无法完成针对业务标识的呼叫， IMS 网络和异构网络之间， 以及不同 的 IMS网络之间的业务互通和交互无法达到， 以至于导致互通的不可实际商 用。 发明内容
本发明实施例的目的是提供一种不同网絡间互通的方法及通信系统， 以 解决现有技术中存在的在 IMS 互通时无法完成针对业务标识的通信业务问 题。
本发明实施例提供的一种不同网络间网絡互通装置， 应用于发送侧与接 收侧之间， 该装置包括：
业务标识转换单元， 用于接收到发送侧的通信命令， 根据发送侧业务标 识和接收侧业务标识的对应关系， 获得发送侧业务标识所对应的接收侧业务 标识， 其中， 所述发送侧的通信命令中包括所述发送侧业务标识， 再将含有 接收侧业务标识的通信命令发送到接收侧。
本发明实施例提供的一种在不同网络间实现互通的方法， 该方法包括： 第一网络侧收到含有第一网络侧业务标识的通信命令 , 根据第一网络侧 和第二网络侧的业务标识的对应关系， 查找出第一网络侧业务标识所对应的 第二网络侧业务标识 , 并将包含第二网络侧业务标识的通信命令发送到第二 网络侧。
本发明实施例提供的一种通信系统， 包括第一网络侧和第二网洛侧， 该 系统还包括一个或一个以上网络互通装置， 并且， 第一网络通过一个或一个 以上网络互通装置与第二网络相连；
其中， 每个网络互通装置， 用于收到来自上一节点设备的通信命令后， 根据获得的发送侧业务标识和接收侧业务标识的对应关系， 将通信命令中的 发送侧的业务标识转换为接收侧业务标识， 然后将转换业务标识后的通信命 令发送给与其连接的下一网络互通装置， 直到将通信命令发送至第二网络侧。
本发明实施例通过对两端网络侧的业务标识的转换来实现网络互通， 可 以完成针对业务标识的通信业务问题， 例如呼叫业务， 订阅 /通知业务， 消息 业务等， 实现业务的互通功能。 对用户来说， 在不同网絡中， 可以获得一致 的业务体验， 提高了业务的连续性和一致性， 从而提高了用户的满意度。 同 时， 对于网络来说， 通过本发明的方案， IMS 网络可以更好的继承传统电路 网络的业务， 便于传统电路网络向 IMS网络的演进。 附图说明 图 1为本发明实施例的通信系统的结构示意图；
图 2为本发明实施例的网络互通装置的一种结构示意图；
图 3为本发明实施例的网络互通装置的另一种结构示意图；
图 4为本发明实施例一在不同网络中实现互通方法流程示意图； 图 5为本发明实施例二中从互联网协议多媒体子系统 IMS网络到传统电 路不同网络的实现互通方法流程示意图；
图 6为本发明实施例三中通过两个网络互通装置来实现互通方法流程示 意图；
图 7为本发明实施例四中通过两个网络互通装置来实现互通方法流程示 意图；
图 8 为本发明实施例五中从传统电路网络到互联网协议多媒体子系统 IMS网络的实现互通方法流程示意图；
图 9为本发明实施例六中从互联网协议多媒体子系统 IMS网络到传统电 路网络的实现互通方法流程示意图；
图 10为本发明实施例七中从互联网协议多媒体子系统 IMS网络 A到互联 网协议多媒体子系统 IMS网络 B的实现互通方法流程示意图。 具体实施方式
本发明实施例通过对两端网络侧的业务标识的转换来实现网络互通， 可 以完成针对业务标识的通信业务问题， 例如呼叫业务， 订阅 /通知业务， 消息 业务等， 实现业务的互通功能。
下面结合附图对本发明实施例作进一步详细说明。
如图 1 所示， 本发明实施例的通信系统包括第一网络侧和第二网络侧， 还包括一个或一个以上网络互通装置， 并且， 第一网络侧通过一个或一个以 上网络互通装置与第二网络侧相连。
该网络互通装置包括： 对应关系存储单元 21和业务标识转换单元 22。 对应关系存储单元 21 用于存储并用于提供给所述业务标识转换单元 22 的发送侧业务标识和接收侧业务标识的对应关系。
业务标识转换单元 22用于在获得发送侧发出的通信命令后， 根据发送侧 的业务标识在对应关系存储单元 21中查找出相应的接收侧业务标识， 并将接 收侧业务标识插入通信命令中， 将此通信命令发送到接收侧。
业务标识转换单元 22还包括： 接收单元 31、 转换单元 32、 转换后业务 标识插入单元 33和发送单元 34。
接收单元 31 , 用于接收含有的发送侧业务标识的发送侧通信命令。
转换单元 32, 用于在发送侧业务标识和接收侧业务标识的对应关系中查 找出该通信命令含有的发送侧业务标识所对应的接收侧业务标识。
转换后业务标识插入单元 33 , 用于将接收侧业务标识插入通信命令中。 发送单元 34, 用于将含有接收侧业务标识的通信命令发送到接收侧。
对应关系存储单元 21可以包含若干个存储实体， 如网絡节点实体、 网络 服务器实体、 网络硬盘中或网络驱动器等， 发送侧业务标识和接收侧业务标 识的对应关系可以按任意顺序存储在这些存储实体中， 也可以按某一特定要 求存储。 例如， 若希望在发起紧急呼叫时能够加快处理速度， 则可以把所有 紧急业务标识存储到某一特定存储实体中， 当业务标识转换单元获得发送侧 的紧急业务标识后直接到这一特定的存储实体中查找， 提高对紧急业务的查 找效率。
当该通信系统只包括一个网络互通装置时， 第一网络侧为网络互通装置 的发送侧， 第二网络侧为网络互通装置的接收侧。 当该通信系统包含两个或 两个以上网络互通装置时， 每个网络互通装置收到来自上一节点设备的通信 业务请求后， 才 据存储的发送侧业务标识和接收侧业务标识的对应关系， 将 通信业务请求中的发送侧的业务标识转换为接收侧业务标识， 然后将转换业 务标识后的通信业务请求发送给与其连接的下一网络互通装置， 直到将通信 业务请求发送至第二网络侧。
如图 2所示， 网络互通装置 41用于在获得发送侧发出的通信命令后， 获 得该通信命令含有的发送侧业务标识所对应的接收侧业务标识， 再将含有接 收侧业务标识的通信命令转发到接收侧。
网络互通装置 41包括业务标识转换单元 51和对应关系存储单元 52。 业务标识转换单元 51用于在得到发送侧发出的通信命令后， 获得该通信 命令含有的发送侧业务标识所对应的接收侧业务标识， 再将含有接收侧业务 标识的通信命令转发到接收侧。
对应关系存储单元 52用于存储并用于提供给业务标识转换单元 51的呼 叫发送侧业务标识和接收侧业务标识的对应关系。
业务标识转换单元 51 包括： 接收单元 61、 转换单元 62、 转换后业务标 识插入单元 63和发送单元 64。
接收单元 61 , 用于接收含有的发送侧业务标识的发送侧通信命令。
转换单元 62, 用于在发送侧业务标识和接收侧业务标识的对应关系中查 找出该通信命令含有的发送侧业务标识所对应的接收侧业务标识。
转换后业务标识插入单元 63 , 用于将接收侧业务标识插入通信命令中。 发送单元 64, 用于将含有接收侧业务标识的通信命令发送到接收侧。 当网络互通装置 41的发送侧为 IMS网络时， 其接收侧为 IP多媒体子系 统网络或异构网络或外部网络互通装置。 当发送侧为异构网络时， 其接收侧 为 IMS网络或异构网络或外部网络互通装置。 当发送侧为外部网络互通装置 时， 接收侧为 IMS网络或异构网络或外部网络互通装置。 此时， 外部网络互 通装置可以是本发明实施例中的网络互通装置 41 , 也可以是其它网络中能够 实现网络互通功能的装置。
在本发明实施例中， 网络互通装置 41可以位于业务控制单元、 呼叫会话 控制单元（Call Session Control Function, CSCF )、 MGCF、 IBCF或互通功能 网元 ( Interworking Fundation, IWF )上。
其中， 业务控制单元完成 IMS网络的业务控制功能， 它可以实现业务处 理功能， 如应用服务器（Application Server , AS ), 也可以实现业务触发的功 能， 将业务触发到应用服务器上处理， 如业务代理（Service Broker );
图 3是以 IMS网络与异构网络之间互通为例， 说明本发明实施例中网络 互通装置的结构示意图。
如图 3 所示， IMS网络为发送侧， 异构网络为接收侧。 呼叫会话控制单 元是 IMS网络中的核心网元， 完成会话控制、 注册服务等功能。 IMS网络中 呼叫会话控制单元与接收单元 61之间釆用 SIP协议连接， 发送单元 64与异 构网络之间采用 E1接口连接。 发送单元 64可以通过其它网络互通装置连接 到异构网络， 发送单元 64与其它网络互通装置之间采用 E2接口。 网络互通 装置 41将完成 SIP协议和 E1/E2接口协议之间的信令转译功能， 在 SIP协议 和 E1/E2接口协议所分别支持的标识格式之间完成业务标识转换功能。
当异构网络为传统电路域网络时， 网络互通装置 41可以位于 MGCF上， E1接口协议为综合业务数字网用户部分信令等传统电路域局间信令。 异构网 络为其它基于 IP的多媒体网络时， 网络互通装置 41可以位于 IBCF， IWF上， E1接口协议可以是 IMS集以外的 SIP协议、 H.323协议等分组信令。
如图 4并结合图 1所示， 本发明实施例中， 当通信系统只包含一个网絡 互通装置时， 在不同网络间实现互通的方法流程示意图， 该方法主要包括以 下步骤：
步驟 401: 用户发起通信业务， 在通信命令中插入发送侧业务标识， 并将 此通信命令路由到转换单元 32中。
在这一步骤中， 可以是用户终端或用户来执行在通信命令中插入发送侧 业务标识这一任务， 当发送侧为 IMS网络时， 还可以是呼叫会话控制单元来 执行在通信命令中插入发送侧业务标识这一任务。
完成在通信命令中插入业务标识的方式是： 若发送侧是 IMS网络时， 可 以按照 IETF的定义， 在会话发起（ SIP INVITE ) 消息的统一请求资源标识 ( RequestURI )头域中插入该业务标识， IMS网络中的业务标识不仅可以保 存在 SIP INVITE消息中， 也可以保存在其它 SIP消息， 如命令应答消息
( ACK ), 信息消息（MESSAGE ), 响应消息等； 不仅可以保存在 SIP消息的 RequestURI头域中， 也可以保存在 SIP消息的其它头域或其他消息体中； 若 发送侧是异构网络时， 可以在第七号信令系统（SS7 )的被叫用户标识中插入 该业务标识， 异构网络的业务标识可以保存在 SS7信令的其它参数中， 也可 以保存在其它协议中， 如 H.323协议。
业务标识可以包括紧急业务标识， 例如火警、 匪警或急救业务， 被叫付 费业务标识， 卡号业务标识， 计费通知业务标识， 反转计费业务标识、 会议 业务标识、 消息业务标识等。 消息业务指即时消息、 短消息等业务。
当用户发起通信业务时， 在请求消息里就已经包含了被叫地址信息。 当 发送侧为 IMS网络时， IMS网络中的呼叫会话控制单元就根据此被叫地址信 息判断该呼叫需要由哪一网络来处理。 例如， 若被叫地址在本网络， 则不需 要进行后续的网络互通过程； 若被叫地址在其他 IMS网络或异构网络中， 则 呼叫会话控制单元将请求消息及后续其它通信命令路由到接收单元 31中， 随 即再发送到转换单元 32中。 当发送侧为异构网络时， 异构网络自身也能够根 据被叫地址信息判断该通信业务需要由哪一网络来处理， 当被叫地址在其他 网络时， 异构网络将通信命令路由到接收单元 31中， 随即再发送到转换单元 32中。
步骤 402: 转换单元 32将发送侧业务标识转换为接收侧业务标识。
在本实施方式中， 该转换方法为： 转换单元 32收到发送侧业务标识后 , 随即到对应关系存储单元 21中进行查找。 例如，在 IMS网络侧急救业务标识 为 URN:sos.firstaid， 则在中国的传统电路网絡中与之对应的业务标识是电话 号码 120。 当转换单元 32收到发送侧的业务标识 UMSi:sosiirstaid后， 就根据 查找出的对应关系获得对应的接收侧的业务标识 120,即完成了发送侧和接收 侧业务标识的转换。
步驟 403： 转换后业务标识插入单元 33将转换后的业务标识插入通信命 令中。
转换后业务标识插入单元 33将转换后的业务标识插入通信命令中的方式 是： 若转换后的业务标识为异构网络的业务标识， 可以在 SS7信令的被叫用 户标识中插入该业务标识。 此业务标识可以保存在 SS7信令的其它参数中， 也可以保存在其它协议中， 如 H.323协议。 若转换后的业务标识为 IMS的业 务标识， 可以按照 IETF的定义， 在 SIP INVITE消息的 RequestURI头域中插 入该业务标识， IMS网络中的业务标识不仅可以保存在 SIP INVITE消息中， 也可以保存在其它 SIP消息， 如 ACK, MESSAGE , 响应消息等； 不仅可以 保存在 SIP消息的 RequestURI头域中， 也可以保存在 SIP消息的其它头 i或或 其他消息体中。
步骤 404: 发送单元 34将转换后的通信命令转发到接收侧相应的业务处 理部分。 此时接收侧返回上述通信命令的应答消息， 通过网络互通装置， 按 照路由的逆向顺序将此应答消息发送给发送侧用户。 如图 5所示，实施例 2是当通信系统只包含一个网络互通装置时，以 IMS 网絡为发送侧， 传统电路网络为接收侧。 IMS网络中的用户发起火警紧急呼 叫， 公共安全接入点 （PSAP )位于传统电路网络中， 在该情况下两端网络互 通步骤为：
步骤 501: 在 IMS网络侧用户发起火警紧急呼叫， 用户终端检测到该火 警紧急呼叫后在火警紧急通信命令中插入火警紧急业务标识。 插入火警紧急 业务标识的方式可以是：按照 IETF的定义，在 SIP INVITE消息的 RequestURI 头域中插入 URN: sos.fire, 表示发起紧急呼叫， 紧急类型是火警。
用户终端将插入了火警紧急业务标识的火警紧急呼叫发送到呼叫会话控 制单元， 该单元通过在请求消息里的被叫地址信息判断出该紧急呼叫需要由 位于传统电路网络中的 PSAP来处理，随即将该火警紧急通信命令路由到接收 单元 31中， 随即再发送到转换单元 32中。
步骤 502: 转换单元 32接收到火警紧急通信命令后， 将 IMS网络中的火 警紧急业务标识转换成传统电路网络的火警紧急业务标识。 转换方式是： 转 换单元 32在对应关系存储单元 21中获得 IMS网络中的业务标识和异构网络 中业务标识的对应关系， 然后根据获得 IMS网絡中的业务标识就可以根据此 对应关系查找出异构网络中相应的业务标识。
本实施例中，如：在传统电路网絡里，火警紧急业务标识是电话号码 119, 转换单元 32需要将紧急通信命令中的紧急业务标识 URN:sos.fire转换成传统 电路网络中的紧急业务标识 119。 即 艮据已保存的业务标识对应关系， 查找出 IMS网络中业务标识 URN:sos.fire所对应的传统电路网络中的业务标识 119, 即完成了发送侧和接收侧业务标识的转换。
步骤 503： 转换后业务标识插入单元 33将转换后的业务标识插入通信命 令中。
此插入方法是： 在 SS7信令的被叫用户标识中插入该 119，然后发送单元 34转发该插入转换后的业务标识的通信命令到传统电路网络中的 PSAP。
步骤 504: 当 PSAP收到上述通信命令后， 识别出这是一次紧急呼叫， 且 紧急类型是火警， 随即完成紧急呼叫的相应处理。 同时， 还要返回通信命令 的应答消息给发送侧的用户， 完成发送侧的 IMS网络与接收侧的传统电路网 络之间的互通。
如图 6所示， 实施例 3是当通信系统包含两个网络互通装置时， 以 IMS 网络为发送侧， 传统电路网络为接收侧， IMS网络中的用户发起火警紧急呼 叫， 公共安全接入点 （PSAP )位于传统电路网络中的情况， 来说明在该情况 下通过两个网絡互通装置来实现两端网络互通步骤为：
步骤 601 : 在 IMS网絡侧用户发起火警紧急呼叫， 用户终端检测到该火 警紧急呼叫后在火警紧急通信命令中插入火警紧急业务标识。 插入火警紧急 业务标识的方式可以是：按照 IETF的定义，在 SIP INVITE消息的 RequestURI 头域中插入 URN: sos.fire, 表示发起紧急呼叫， 紧急类型是火警。
用户终端将插入了火警紧急业务标识的火警紧急呼叫发送到呼叫会话控 制单元， 该单元通过在请求消息里的被叫地址信息判断出该紧急呼叫需要由 位于传统电路网络中的 PSAP来处理，随即将该火警紧急通信命令路由到第一 网络互通装置的接收单元中， 随即再发送到转换单元中。
步骤 602: 第一网络互通装置的转换单元接收到火警紧急通信命令后，将 IMS网络中的火警紧急业务标识转换成其接收侧的火警紧急业务标识。 转换 方式是： 第一网絡互通装置的转换单元在存储对应关系的实体中获得 IMS网 络中的业务标识和其接收侧业务标识的对应关系， 然后才艮据获得 IMS网络中 的业务标识就可以才艮据此对应关系查找出其接收侧中相应的业务标识。
本实施例中， 在分组电路网络里， 火警紧急业务标识是优先权头域设置 为 "紧急，，， 第一网络互通装置的转换单元将紧急呼叫请求中的紧急业务标识 URN:sos.fire转换成接收侧中的紧急业务标识， 如在优先权头域（priority )中 设置 "emergency" 0
步骤 603:第一网络互通装置的转换后业务才示识插入单元将转换后的业务 标识插入通信命令中。
此插入方法是： 在 SIP INVITE消息的 priority中插入紧急业务标识 emergency, 然后发送单元转发该插入转换后的业务标识的通信命令到第二网 络互通装置。
步骤 604: 第二网络互通装置执行标识转换功能。
笫二网络互通装置将 SIP INVITE消息的 priority中插入的紧急业务标识 emergency转换成传统电路网络的紧急业务标识。 本实施例中， 在中国的传统 电路网络里， 火警紧急业务标识是电话号码 119, 第二网络互通装置的转换单 元在存储对应关系的实体中获得 emergency与传统电路网络的业务标识对应 关系，查找出接收侧业务标识 119,在 SS7信令的被叫用户标识中插入该 119, 然后发送单元转发该插入转换后的业务标识的通信命令到传统电路网络中的 PSAP。
第二网络互通装置也可以采用其它方案， 实现业务标识转换的功能。 步驟 605: 当 PSAP收到上述通信命令后， 识别出这是一次紧急呼叫 , 且 紧急类型是火警， 随即完成紧急呼叫的相应处理。 同时， 还要返回响应消息 给发送侧的用户， 完成发送侧的 IMS网络与接收侧的传统电路网络之间的互 通。
实施例 4仍然是当通信系统包含两个网络互通装置时， 以 IMS网络为发 送侧， 传统电路网络为接收侧， IMS网络中的用户发起火警紧急呼叫， 公共 安全接入点 （PSAP )位于传统电路网络中的情况， 与实施例 3不同的是实施 例 4中第二网络互通装置所识别的业务标识与实施例 6中不同， 如图 7所示， 在该情况下通过两个网络互通装置来实现两端网络互通步像为：
步骤 701: 在 IMS网络侧用户发起火警紧急呼叫， 用户终端检测到该火 警紧急呼叫后， 在火警紧急通信命令中插入火警紧急业务标识。 插入火警紧 急业务标识的方式可以是： 按照 IETF的定义， 在 SIP INVITE消息的
RequestURI头域中插入 URN: sos.fire,表示发起紧急呼叫， 紧急类型是火警。
用户终端将插入了火警 '紧急业务标识的火警紧急呼叫发送到呼叫会话控 制单元， 该单元通过在请求消息里的被叫地址信息判断出该紧急呼叫需要由 位于传统电路网络中的 PSAP来处理，随即将该火警紧急通信命令路由到第一 网络互通装置的接收单元中， 该接收单元再将该火警紧急通信命令发送到转 换单元中。 - 步骤 702: 第一网络互通装置的转换单元接收到火警紧急通信命令后， 将 IMS网络中的火警紧急业务标识转换成其接收侧的火警紧急业务标识。 转换 方式是： 第一网络互通装置的转换单元在存储对应关系的实体中获得 IMS网 络中的业务标识和其接收侧业务标识的对应关系， 然后根据获得 IMS网络中 的业务标识就可以根据此对应关系查找出其接收侧中相应的业务标识。
本实施例中， 第二网络互通装置识别的火警紧急业务标识是电话通用资 源标识 (TEL URI)格式， 如： TEL:119, 第一网络互通装置的转换单元将紧急 呼叫请求中的紧急业务标识 URN:sos.fire转换成接收侧中的紧急业务标识 TEL: 119。
步骤 703:第一网絡互通装置的转换后业务标识插入单元将转换后的业务 标识插入通信命令中。
此插入方法是： 在 SIP INVITE消息的 RequestURI中插入紧急业务标识 TEL: 119,然后发送单元转发该插入转换后的业务标识的通信命令到第二网络 互通装置。
步骤 704: 第二网络互通装置执行标识转换功能。
第二网络互通装置将 SIP INVITE消息的 RequestURI中插入的紧急业务 标识 TEL: 119转换成传统电路网络的紧急业务标识。 本实施例中， 在中国的 传统电路网络里， 火警紧急业务标识是电话号码 119, 第二网络互通装置的转 换单元在存储对应关系的实体中获得 TEL: 119与传统电路网络的业务标识对 应关系， 查找出接收侧业务标识 119, 在 SS7信令的被叫用户标识中插入该 119, 然后发送单元转发该插入转换后的业务标识的通信命令到传统电路网络 中的 PSAP。
第二网络互通装置也可以采用其它方案， 实现业务标识转换的功能； 步骤 705: 当 PSAP收到上述通信命令后， 识别出这是一次紧急呼叫， 且 紧急类型是火警， 随即完成紧急呼叫的相应处理。 同时， 还要返回响应消息 给发送侧的用户， 完成发送侧的 IMS网络与接收侧的传统电路网络之间的互 通0
如图 8所示， 实施例 5是当通信系统只包含一个网絡互通装置时， 以传 统电路网络为发送侧， IMS网络为接收侧。 传统电路网络中的用户发起紧急 呼叫， PSAP位于 IMS网絡中， 在该情况下两端网络互通的步骤为：
步驟 801 :在传统电路网络侧用户发起紧急呼叫，并在 SS7信令的被叫用 户标识中插入紧急业务标识。 如欧洲的紧急业务统一号码为 112, 表示发起紧 急呼叫。
传统电路网络通过在请求消息里的被叫地址信息判断出该紧急呼叫需要 由位于 IMS网络中的 PSAP来处理， 随即将上述已插入紧急业务标识的紧急 通信命令路由到接收单元 31中， 随即再发送到转换单元 32中。
步驟 802: 转换单元 32接收到该紧急通信命令后， 将传统电路网络中的 紧急业务标识转换成 IMS网络的紧急业务标识。在对应关系存储单元 21查找 出已获得的传统电路网络中的业务标识 112所对应的 IMS网络中的业务标识 U N:sos, 即完成了发送侧和接收侧业务标识的转换。
步骤 803: 转换后业务标识插入单元 33将转换后的业务标识插入通信命 令中。
转换后业务标识插入单元 33将转换后的业务标识插入通信命令中的方式 是： 在 SIP INVITE消息的 RequestURI头域中插入该 URN:sos。 发送单元 34 转发该通信命令到处理紧急业务的呼叫会话控制单元。
步骤 804: 呼叫会话控制单元收到该紧急通信命令后， 将该请求路由到 IMS网络中的 PSAP中， PSAP收到上述通信命令后， 识别出这是一次紧急呼 叫， 随即完成紧急呼叫的相应处理。 同时， 还要返回响应消息给发送侧的用 户， 完成发送侧的传统电路网络与接收侧的 IMS网络之间的互通。
如图 9所示，实施例 6是当通信系统只包含一个网络互通装置时，以 IMS 网络为发送侧， 传统电路网络为接收侧。 IMS网络中的用户发起被叫付费业 务， 被叫位于传统电路网络中为例， 在该情况下两端网络互通步骤为：
步骤 901: 在 IMS网络侧， 用户发起被叫付费通信命令， 如呼叫某公司 服务中心， 且使用被叫付费业务。 用户在通信命令中插入被叫付费业务标识， 如在 SIP INVITE通信命令消息插入头域 P-Called-Charged: true abc@abc.com, 来表示发起某电话号码的被叫付费业务。
. 用户终端将已插入被叫付费业务标识的通信命令发送到呼叫会话控制单 元中， 该单元通过在请求消息里的被叫地址信息判断出该呼叫需要由传统电 路网络来处理， 随即将被叫付费通信命令路由到接收单元 31中， 随即再发送 到转换单元 32中。
步骤 902: 转换单元 32接收到该被叫付费通信命令后， 将 IMS网络中的 被叫付费业务标识转换为传统电路网络中的被叫付费业务标识。 转换单元 32 在对应关系存储单元 21中查找出 IMS网絡的业务标识 P-Called-Charged: true-abc@abc.com所对应的传统电路网络中的业务标识为电话号码
800-12345678, 即完成了发送侧和接收侧业务标识的转换。
步骤 903： 转换后业务标识插入单元 33将转换后的业务标识插入通信命 令中。
转换后业务标识插入单元 33将转换后的业务标识插入通信命令中的方式 是： 在 SS7信令的被叫用户标识中插入该业务标识 800-12345678, 然后发送 单元 34转发该通信命令到传统电路网络中。 步骤 904: 当传统电路网络收到上述通信命令后， 根据业务标识识别出这 是一次被叫付费业务， 随即转发通信命令到该公司的服务中心， 并根据被叫 付费标识实现被叫付费业务。 同时， 还要返回响应消息给发送侧的用户， 完 成发送侧的 IMS网络与接收侧的传统电路网络之间的互通。
如图 10所示，实施例 7是当通信系统只包含一个网络互通装置时，以 IMS 网络 A为发送侧， 另一 IMS网络 B为接收侧。 IMS网络 A中的用户发起卡 号业务， 被叫位于其它运营商的 IMS网络 B中， IMS网络 A和 IMS网络 B 使用不同的卡号业务标识， 在该情况下两端网络互通步骤为：
步骤 1001: 在 IMS网络 A侧， 用户发起卡号业务通信命令， 用户终端检 测到这一通信命令后， 在 SIP INVITE消息的 RequestURI头域插入卡号业务 标识 TEL: 201 , 以及后续的卡号和密码， 表示这是一个卡号业务。
用户终端将插入了卡号业务标识的通信命令转发到呼叫会话控制单元， 该单元通过在请求消息里的被叫地址信息判断出该呼叫需要由另一运营商的 IMS网络 B来处理， 随即将该通信命令路由到接收单元 31中， 随即再发送到 转换单元 32中。
步驟 1002'.转换单元 32收到该卡号业务通信命令后，将上述 IMS网络 A 中的卡号业务标识 TEL: 201转换成 IMS网络 B中的卡号业务标识 TEL: 202。 在对应关系存储单元 21中查找出已获得的 IMS网络 A中的业务标识 TEL: 201所对应的 IMS网络 B中的业务标识 TEL: 202, 即完成了发送侧和接收侧 业务标识的转换。
步骤 1003:转换后业务标识插入单元 33将转换后的业务标识插入通信命 令中。
转换后业务标识插入单元 33将转换后的业务标识插入通信命令中的方式 是： 在 SIP INVITE消息的 RequestURI头域插入转换后的卡号业务标识 TEL: 202, 然后发送单元 34转发已插入 TEL: 202的通信命令到 IMS网络 B。
步骤 1004: 当 IMS网络 B收到上述通信命令后，根据业务标识识别出这 是一次卡号业务， 随即实现卡号业务。 同时， 还要返回响应消息给发送侧的 用户， 完成发送侧的 IMS网络 A与接收侧的 IMS网络 B之间的互通。
通过本发明实施例对两端网络侧的业务标识的转换来实现网络互通， 解 决了两端网络侧的业务标识因各自网络支持的信令协议不一致、 和 /或各自运 营商定义的标识不一致的问题， 可以完成针对业务标识的通信业务问题， 例 如呼叫业务， 订阅 /通知业务， 消息业务等， 实现业务的互通功能。 对用户来 说， 在不同网络中， 可以获得一致的业务体验， 提高了业务的连续性和一致 性， 从而提高了用户的满意度； 同时， 对于网络来说， 通过本发明实施例的 方案， IMS网絡可以更好的继承传统电路网络的业务， 便于传统电路网络向 IMS网络的演进。 发明的精神和范围。 这样， 倘若本发明的这些修改和变型属于本发明权利要 求及其等同技术的范围之内， 则本发明也意图包含这些改动和变型在内。

Claims

权 利 要 求
1、 一种不同网络间网络互通装置， 应用于发送侧与接收侧之间， 其特征 在于， 该装置包括：
业务标识转换单元， 用于接收到发送侧的通信命令， 根据发送侧业务标 识和接收侧业务标识的对应关系， 获得发送侧业务标识所对应的接收侧业务 标识， 其中， 所述发送侧的通信命令中包括所述发送侧业务标识， 再将含有 接收侧业务标识的通信命令发送到接收侧。
2、 如权利要求 1所述装置， 其特征在于， 所述业务标识转换单元包括： 接收单元， 用于接收发送侧通信命令；
转换单元， 用于在发送侧业务标识和接收侧业务标识的对应关系中查找 出所述通信命令中含有的发送侧业务标识所对应的接收侧业务标识；
转换后业务标识插入单元， 用于将接收侧业务标识插入通信命令中； 发送单元， 用于将含有接收侧业务标识的通信命令发送到接收侧。
3、 如权利要求 1所述装置， 其特征在于， 所述装置还包括：
对应关系存储单元， 用于存储并用于提供给所述业务标识转换单元的呼 叫发送侧业务标识和接收侧业务标识的对应关系。
4、 如权利要求 1所述装置， 其特征在于， 所述业务标识转换单元， 与保 存呼叫发送侧业务标识和接收侧业务标识的对应关系的外部网络节点相连。
5、 如权利要求 3所述装置， 其特征在于， 所述对应关系存储单元包含若 干个存储实体。
6、如权利要求 1所述装置， 其特征在于， 当所述发送侧为 IP多媒体子系 统网络时， 所述接 4史侧为 IP多媒体子系统网络， 或异构网络， 或外部网络互 通装置；
当所述发送侧为异构网络时， 所述接收侧为 IP多媒体子系统网络， 或异 构网络， 或外部网络互通装置；
当所述发送侧为外部网络互通装置时， 所述接收侧为 IP多媒体子系统网 络， 或异构网络， 或外部网络互通装置。
7、 如权利要求 6所述装置， 其特征在于， 所述异构网络为传统电路网络 或基于 IP的非 IP多媒体子系统的多媒体网络。
8、如权利要求 7所述装置， 其特征在于， 当所述发送侧为 IP多媒体子系 统网络时， 该网络与接收单元之间采用会话发起协议连接；
当所述发送侧为传统电路网络时， 该网络与接收单元之间采用传统电路 域局间信令连接；
当所述发送侧为基于 IP的多媒体网络时， 该网络与接收单元之间采用 IP 多媒体子系统以外的会话发起协议或视听及多媒体协议连接。
9、如权利要求 7所述装置， 其特征在于， 当所述接收侧为 IP多媒体子系 统网络时， 该网络与发送单元之间釆用会话发起协议连接；
当所述接收侧为传统电路网络时， 该网络与发送单元之间采用传统电路 域局间信令连接；
当所述接收侧为基于 IP的多媒体网络时， 该网络与发送单元之间采用 IP 多媒体子系统以外的会话发起协议或视听及多媒体协议连接。
10、 如权利要求 1所述装置， 其特征在于， 所述装置位于业务控制单元、 呼叫会话控制单元、 媒体网关控制网元、 互通边界控制功能网元或互通功能 网元中。
11、 如权利要求 1 所述装置， 其特征在于， 所述业务标识为紧急业务标 识、 被叫付费业务标识、 卡号业务标识、 计费通知业务标识或反转计费业务 标识中的一种或几种。
12、 一种在不同网络间实现互通的方法， 其特征在于， 该方法包括： 第一网络侧收到含有第一网络侧业务标识的通信命令， 根据第一网络侧 和笫二网络侧的业务标识的对应关系， 查找出第一网络侧业务标识所对应的 第二网络侧业务标识 , 并将包含第二网络侧业务标识的通信命令发送到第二 网络侧。
13、如权利要求 12所述方法， 其特征在于， 当所述第一网络侧为 IP多媒 体子系统网络时， 所述第二网络侧为 IP多媒体子系统网络， 或异构网络， 或 外部网络互通装置；
当所述第一网络侧为异构网络时， 所述第二网絡侧为 IP多媒体子系统网 络， 或异构网络， 或外部网络互通装置；
当所述第一网络侧为其它网络互通装置时， 所述第二网络侧为 IP多媒体 子系统网络， 或异构网络， 或外部网络互通装置。
14、 如权利要求 13所述方法， 其特征在于， 所述异构网络为传统电路网 络或基于 IP的非 IP多媒体子系统的多媒体网络。
15、 如权利要求 12所述方法， 其特征在于， 所述业务标识为紧急业务标 识、 被叫付费业务标识、 卡号业务标识、 计费通知业务标识或反转计费业务 标识中的一种或几种。
16、 一种通信系统， 包括第一网络侧和第二网络侧， 其特征在于， 该系 统还包括一个或一个以上网络互通装置， 并且， 第一网络通过一个或一个以 上网络互通装置与第二网络相连；
其中， 每个网络互通装置， 用于收到来自上一节点设备的通信命令后， 根据获得的发送侧业务标识和接收侧业务标识的对应关系， 将通信命令中的 发送侧的业务标识转换为接收侧业务标识， 然后将转换业务标识后的通信命 令发送给与其连接的下一网络互通装置， 直到将通信命令发送至第二网络侧。
17、 如权利要求 16所述系统， 其特征在于， 所述网络互通装置包括： 对应关系存储单元， 用于存储并用于提供给所述业务标识转换单元的发 送侧业务标识和接收侧业务标识的对应关系；
业务标识转换单元， 用于收到发送侧发出的通信命令， 根据所述发送侧 业务标识和接收侧业务标识的对应关系， 获得所述通信命令中含有的发送侧 的业务标识所对应的接收侧业务标识， 并将接收侧业务标识插入通信命令中， 将此通信命令发送到接收侧。
18、如权利要求 17所述系统，其特征在于， 所述业务标识转换单元包括： 接收单元， 用于接收含有的发送侧业务标识的发送侧通信命令； 转换单元， 用于在发送侧业务标识和接收侧业务标识的对应关系中查找 出该通信命令含有的发送侧业务标识所对应的接收侧业务标识；
转换后业务标识插入单元， 用于将接收侧业务标识插入通信命令中； 发送单元， 用于将含有接收侧业务标识的通信命令发送到接收侧。
19、 如权利要求 17所述系统， 其特征在于， 所述对应关系存储单元包含 若干个存储实体； 所述存储实体为网络节点实体、 网络服务器实体、 网络硬 盘或网络驱动器。
20、 如权利要求 16所述系统， 其特征在于， 所述网絡互通装置位于业务 控制单元、 呼叫会话控制单元、 媒体网关控制网元、 互通边界控制功能网元 或互通功能网元中。
21、如权利要求 16所述系统， 其特征在于， 当所述第一网络侧为 IP多媒 体子系统网络时， 所述第二网絡侧为 IP多媒体子系统网絡或异构网络； 当所 述第一网络侧为异构网络时， 所述第二网络侧为 IP多媒体子系统网络或异构 网络。
22、 如权利要求 21所述系统， 其特征在于， 所述异构网络为传统电路网 络或基于 IP的非 IP多媒体子系统的多媒体网络。
PCT/CN2007/002564 2006-08-25 2007-08-24 An intercommunication method and a communication system between different networks Ceased WO2008025257A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP07800783A EP2056556A4 (en) 2006-08-25 2007-08-24 INTERCOM COMMUNICATION PROCESS AND COMMUNICATION SYSTEM BETWEEN DIFFERENT NETWORKS

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200610109946.7A CN101132378B (zh) 2006-08-25 2006-08-25 一种不同网络间互通的方法及通信系统
CN200610109946.7 2006-08-25

Publications (1)

Publication Number Publication Date
WO2008025257A1 true WO2008025257A1 (en) 2008-03-06

Family

ID=39129505

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2007/002564 Ceased WO2008025257A1 (en) 2006-08-25 2007-08-24 An intercommunication method and a communication system between different networks

Country Status (3)

Country Link
EP (1) EP2056556A4 (zh)
CN (1) CN101132378B (zh)
WO (1) WO2008025257A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2025012985A1 (en) * 2023-07-07 2025-01-16 Jio Platforms Limited System and method of interworking between networks

Families Citing this family (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9148769B2 (en) 2008-05-07 2015-09-29 Qualcomm Incorporated System, apparatus and method to enable mobile stations to identify calls based on predetermined values set in a call header
CN101883344B (zh) * 2009-05-06 2013-09-25 华为技术有限公司 网络间关联呼叫接续方法、业务代理系统
CN102026127A (zh) * 2009-09-18 2011-04-20 中兴通讯股份有限公司 紧急呼叫跨越业务的实现方法、装置和系统
CN102316077B (zh) * 2010-06-29 2016-02-10 中兴通讯股份有限公司 公共安全应答点的选择方法、装置及系统
CN102045598A (zh) * 2010-12-31 2011-05-04 华为技术有限公司 在ip多媒体子系统网络实现被叫付费业务的方法和装置
US9369448B2 (en) * 2011-06-01 2016-06-14 Broadcom Corporation Network security parameter generation and distribution
CN103078846B (zh) * 2012-12-20 2017-03-15 华为技术有限公司 Ims架构下信息传送方法、装置和通信系统
CN104714923B (zh) 2013-12-17 2018-04-20 华为技术有限公司 一种实现设备共享的方法和装置
DE102015012569A1 (de) 2014-10-31 2016-05-04 Intel Corporation Vorrichtung, System und Verfahren zur Unterscheidung zwischen einer IMS-Verbindung und einer Nicht-IMS-Verbindung
CN107302485B (zh) * 2016-04-15 2020-11-27 大唐移动通信设备有限公司 一种不同网络中设备互连的方法、设备及装置
CN108076479B (zh) 2016-11-08 2020-01-03 展讯通信（上海）有限公司 多卡移动终端及其业务切换方法、装置

Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2001237898A (ja) * 2000-02-24 2001-08-31 Nippon Telegr & Teleph Corp <Ntt> フレーム転送方法
CN1357210A (zh) * 1999-06-24 2002-07-03 康柏计算机股份有限公司 在使用不同协议的网络上提供电信业务的方法和系统
US6490622B1 (en) * 1997-03-11 2002-12-03 Kabushiki Kaisha Toshiba Node device and scheme for sharing common virtual connection indentifier between end-nodes
US6614809B1 (en) * 2000-02-29 2003-09-02 3Com Corporation Method and apparatus for tunneling across multiple network of different types
CN1487700A (zh) * 2001-03-10 2004-04-07 华为技术有限公司 互通代理装置及不同协议网络之间进行互通的系统和方法
CN1567894A (zh) * 2003-06-17 2005-01-19 华为技术有限公司 无线局域网和移动网互通情况下查询路由的方法
CN1665239A (zh) * 2004-03-03 2005-09-07 联想(北京)有限公司 一种实现不同通信协议设备间信息传输的方法
CN1738308A (zh) * 2004-08-18 2006-02-22 华为技术有限公司 一种多协议网络互联互通方法和系统
WO2006071551A2 (en) * 2004-12-30 2006-07-06 Grape Technology Group, Inc. Cross-platform universal call identifier

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
FR2844415B1 (fr) * 2002-09-05 2005-02-11 At & T Corp Systeme pare-feu pour interconnecter deux reseaux ip geres par deux entites administratives differentes

Patent Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6490622B1 (en) * 1997-03-11 2002-12-03 Kabushiki Kaisha Toshiba Node device and scheme for sharing common virtual connection indentifier between end-nodes
CN1357210A (zh) * 1999-06-24 2002-07-03 康柏计算机股份有限公司 在使用不同协议的网络上提供电信业务的方法和系统
JP2001237898A (ja) * 2000-02-24 2001-08-31 Nippon Telegr & Teleph Corp <Ntt> フレーム転送方法
US6614809B1 (en) * 2000-02-29 2003-09-02 3Com Corporation Method and apparatus for tunneling across multiple network of different types
CN1487700A (zh) * 2001-03-10 2004-04-07 华为技术有限公司 互通代理装置及不同协议网络之间进行互通的系统和方法
CN1567894A (zh) * 2003-06-17 2005-01-19 华为技术有限公司 无线局域网和移动网互通情况下查询路由的方法
CN1665239A (zh) * 2004-03-03 2005-09-07 联想(北京)有限公司 一种实现不同通信协议设备间信息传输的方法
CN1738308A (zh) * 2004-08-18 2006-02-22 华为技术有限公司 一种多协议网络互联互通方法和系统
WO2006071551A2 (en) * 2004-12-30 2006-07-06 Grape Technology Group, Inc. Cross-platform universal call identifier

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP2056556A4 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2025012985A1 (en) * 2023-07-07 2025-01-16 Jio Platforms Limited System and method of interworking between networks

Also Published As

Publication number Publication date
EP2056556A1 (en) 2009-05-06
CN101132378A (zh) 2008-02-27
EP2056556A4 (en) 2009-12-09
CN101132378B (zh) 2010-07-21

Similar Documents

Publication Publication Date Title
WO2008025257A1 (en) An intercommunication method and a communication system between different networks
CN103428218B (zh) 转发用户设备的性能信息的方法和系统
CN101142833B (zh) 用于控制电路交换域用户终端接入ims通信网服务的设备
CN101371532B (zh) 处理因特网协议多媒体子系统终端的包括在因特网协议多媒体子系统域内请求由同时具有组合电路交换呼叫和因特网协议多媒体子系统会话能力的终端接收的实时服务的呼叫请求的方法和装置
US10044553B2 (en) Media resource reservation request failure handling for voice over mobile wireless network
EP1973283A1 (en) Interworking network element, interworking system between the csi terminal and the ims terminal and the method thereof
WO2007143924A1 (en) The method and system for delivering the message service data
CN104202786B (zh) 一种呼叫路由方法及装置
CN100574474C (zh) 一种通讯系统中建立通讯业务连接的方法
US20120163561A1 (en) Method, device and system for implementing emergency call override service
WO2007009298A1 (fr) Appareil et méthode permettant à un terminal traditionnel d’accéder à un système ims
CN1327680C (zh) 一种电路交换网络到ims网络呼叫路由的建立方法
WO2012174904A1 (zh) 一种ims会议接入的方法、装置及系统
CN102804820B (zh) 电信网络中的方法和设备
EP2068517B1 (en) Method and system for implementing simulative service, method for implementing interworking, and unit for controlling interworking
CN104168190B (zh) 一种呼叫路由方法及装置
US8369315B2 (en) Call connection method, equipment, and system in IP multimedia subsystem
WO2011023041A1 (zh) 一种指示终端媒体类型的呼叫方法及系统
CN101815270B (zh) 呼叫的处理方法和装置
EP3094059B1 (en) Routing voice over lte call invites in a terminating ims
WO2008049371A1 (en) A method and system for transferring service event
WO2008017269A1 (fr) Procédé et système pour transférer les informations d&#39;application utilisateur-utilisateur
CN102057701B (zh) 在通信网络中实现呼叫等待功能的方法
CN101304551A (zh) 一种在ims网络中通信的方法、通信系统及装置
CN101800948B (zh) 实现呼叫转向业务的方法、装置和系统

Legal Events

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

Ref document number: 07800783

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2007800783

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE

NENP Non-entry into the national phase

Ref country code: RU