WO2009092307A1

WO2009092307A1 - A method,system and device for accessing non-sip resource

Info

Publication number: WO2009092307A1
Application number: PCT/CN2009/070054
Authority: WO
Inventors: Bo Zheng; Youzhu Shi; Hongbo Liao
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2008-01-09
Filing date: 2009-01-07
Publication date: 2009-07-30
Also published as: CN101483581A

Abstract

A method for accessing non-SIP resource comprises the following steps: the interworking function entity receives a SIP access request carrying non-SIP resource location information which is forwarded by the call session control function entity; the interworking function entity converts the SIP access request into the heterogeneous request and sends it to the server at which the non-SIP resource is; the interworking function entity receives the heterogeneous response carrying non-SIP resource data which is sent by the server, converts the heterogeneous response to the SIP response and sends it to the call session control function entity. A system and device for accessing non-SIP resource is disclosed. By using the provided method, the IMS network user or other elements establish the access to non-SIP resource by SIP, then the IT and CT fusion service is provided in IMS, which establishes the base for the IMS network utilizes Web service.

Description

Method, system and device for accessing non-SIP resources. The application is filed on January 9, 2008, and the application number is 200810002579.X. The invention is entitled "A method, system and device for accessing non-SIP resources." The priority of the Chinese Patent Application, the entire contents of which is incorporated herein by reference. Technical field

The embodiments of the present invention relate to the field of network technologies, and in particular, to a method, a system, and a device for accessing a non-SIP (Session Initiation Protocol) resource. Background technique

At present, with the continuous maturity of packet technology, traditional telecommunication networks based on circuit switching are developing towards packet-switched broadband telecommunication networks, and the use of SIP as the packet telecommunication core network for call control signaling is one of the current technological development trends. , ITU-T (International Telecommunication Union - Telecommunication Standardization Sector) and ETSI (European Telecommunications Standards Institute) and other standards organizations conduct NGN (Next Generation Network) In the research, the IMS (IP Multimedia Subsystem, IP, Multimedia Subsystem) network architecture defined by the 3GPP (3rd Generation Partnership Project) standard organization is adopted as the core network of NGN.

The communication network from circuit switching to soft interaction until the development of IMS has absorbed many excellent IT (Information Technology) technologies, such as IP technology, distributed concept, SIP, Diameter, DNS (Dynamic Network Services), XML (extensible Markup Language) and so on, but IMS is not the end. At present, the integration of IMS and the Internet has received a lot of attention and opportunities. Many organizations and standards organizations have started related research, some big ones. Vendors are also developing IMS and Internet convergence services.

The convergence of IMS and the Internet is, to a large extent, an attempt to take advantage of the Internet's content delivery to provide richer services to users of the telecommunication network. IMS networks necessarily involve access to Internet content when using Internet content. Accessing Internet content in IMS is access to the Internet URI (Universal Resource Identifier). Specifically, the access to resources such as an HTTP (Hypertext Transfer Protocol) URI, an FTP (File Transfer Protocol) URI, and the like may be collectively referred to as a non-SIP resource. Such access can be initiated by users in the IMS network or other IMS network elements that need to use Internet resources, such as AS (Application Server).

Currently, access to non-SIP resources can be applied to the specification protocol of the resource identification subordinate. When directly accessing non-SIP resources (such as HTTP URI, FTP URI, etc.) using protocols such as HTTP or FTP, the IMS network will not be aware of the above-mentioned non-SIP resource application because the SIP protocol uses the SIP protocol as its application layer protocol. In the prior art, when the SIP protocol is used as an application layer protocol to access non-SIP resources (such as an HTTP URL FTP URI), since the requested resource is not semantically supported by the server, the server will reject the access. Therefore, IMS cannot function as a target network for unified multimedia services and applications, and thus cannot provide integrated and integrated services for target users. Summary of the invention

Embodiments of the present invention provide a method, system, and device for accessing non-SIP resources to implement access of non-SIP resources by IMS network users or other network elements.

To achieve the above objective, an embodiment of the present invention provides a method for accessing a non-SIP resource, including the following steps:

The interworking function entity receives the SIP access request that carries the non-SIP resource location information forwarded by the call session control function entity;

The interworking function entity converts the SIP access request into a heterogeneous request and sends Giving the server where the non-SIP resource is located;

The interworking function entity receives a heterogeneous response sent by the server carrying non-SIP resource data, converts the heterogeneous response into a SIP response message, and sends the message to the call session control function entity.

The embodiment of the present invention further provides a system for implementing access to a non-SIP resource, including: an access request function entity, configured to generate a SIP access request for accessing non-SIP resource location information, and send the call to the call session control function entity;

a call session control function entity, configured to send the access request function entity

The SIP access request is routed to the interworking function entity, and the response carrying the non-SIP resource data returned by the interworking function entity is routed to the access request function entity;

An interworking function entity, configured to convert a SIP access request routed by the call session control function entity into a heterogeneous request and send the message to a server where the non-SIP resource is located; and receive a heterogeneous response carrying the non-SIP resource data, The response is converted to a SIP response message and sent to the call session control function entity;

The server where the non-SIP resource is located is configured to receive the heterogeneous request sent by the interworking function entity, and send the heterogeneous response carrying the non-SIP resource data to the interworking function entity.

The embodiment of the present invention further provides an access request function entity, including: a non-SIP resource location information generating module, configured to receive non-SIP resource identifier information to be accessed and generate non-SIP resource location information, and generate non-SIP resource location information. Send to the access request initiation module;

The access request initiating module is configured to add the non-SIP resource location information received from the non-SIP resource location information generating module to the SIP access request, and send the message to the call session control function entity in the network.

An embodiment of the present invention further provides an interworking function entity, including:

a SIP message module, configured to receive a SIP access request carrying non-SIP resource location information from the IMS domain and send the SIP access request to the protocol capability conversion module; and configured to receive a SIP response message from the protocol capability conversion module;

a protocol capability conversion module, configured to receive the SIP message module or heterogeneous message The message of the module, completes the protocol capability interworking conversion of the SIP message and the heterogeneous message, converts the SIP access request from the SIP message module into a heterogeneous request, and sends the message to the heterogeneous message module, which will be from the heterogeneous message The heterogeneous response of the module is converted into a SIP response and sent to the SIP message module;

The heterogeneous message module is configured to receive the heterogeneous request from the protocol capability conversion module, send the heterogeneous request to the server where the non-SIP resource is located, and receive the heterogeneous non-SIP resource data from the server where the non-SIP resource is located. In response, the heterogeneous response is sent to the protocol capability conversion module.

Embodiments of the present invention have the following advantages over the prior art:

Through the protocol conversion function of the interworking function entity, the protocol conversion between the access request function entity and the server where the non-SIP resource is located is realized, so that the IMS network user or other network element can establish access to the non-SIP resource through the SIP; The non-SIP resource location information is generated on the access request function entity according to the request for accessing the non-SIP resource, so that the request for accessing the non-SIP resource can reach the interworking function entity and is finally accepted by the server where the non-SIP resource is located. DRAWINGS

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the description of the embodiments will be briefly described below. It is obvious that the drawings in the following description are only some embodiments of the present invention. Other drawings may also be obtained from those of ordinary skill in the art in view of the drawings.

1 is a schematic diagram of a system for accessing non-SIP resources in an embodiment of the present invention; FIG. 2 is a schematic structural diagram of an access request function entity in an embodiment of the present invention; FIG. 3 is a structure of an interworking function entity in an embodiment of the present invention; 4 is a flow chart of accessing non-SIP resources in an embodiment of the present invention;

FIG. 5 is a flowchart of a method for accessing non-SIP resources in an embodiment of the present invention; FIG. 6 is a flowchart of another method for accessing non-SIP resources in an embodiment of the present invention. detailed description

In an embodiment of the invention, a system and device for accessing non-SIP resources is provided. Through the system architecture, IMS network users or other network elements can establish access to non-SIP resources through SIP.

The system structure diagram for accessing non-SIP resources in the embodiment of the present invention is as shown in FIG. 1, and includes: an access request function entity 10, a call session control function entity 20, an interworking function entity 30, and a non-SIP resource 40. among them:

The access request function entity 10 is configured to initiate an access request for the non-SIP resource and receive a response to the access request. In the IMS network, the functional entity may be a UE (User Equipment), or may be another network element of the IMS network, such as an AS, a MRFC (Media Resource Function Control), or the like. Specifically, the access request function entity 10 receives the information of the non-SIP resource to be accessed, completes the positioning process of the non-SIP resource in the SIP domain, generates non-SIP resource location information, and then initiates carrying the non-SIP to the call session control function entity 20. For the access request of the resource location information, the request may carry the non-SIP resource location information through the Request-URI or the Route header field.

The call session control function entity 20 is configured to process call session control based on SIP signaling. In the IMS network, the functional entity may be a CSCF (Call Session Control Function). Specifically, the call session control function entity 20 may route the access request to the interworking function entity 30 according to the access request that carries the non-SIP resource location information sent by the access request function entity 10.

The interworking function entity 30 is configured to provide protocol capability interworking of the IMS network entity to access non-IMS resources. In an IMS network, the functional entity may be an IBCF (Interconnection Border Control Function) or an AS. Specifically, the interworking function entity 30 completes the protocol capability interworking conversion between the SIP message and the heterogeneous message (non-SIP message) according to the non-SIP resource location information received from the call session control function entity 20, and sends the converted request to the Non-SIP resources being accessed. In addition, the interworking function entity 30 is further configured to receive an access response message from the non-SIP resource 40, which will ring After the message is exchanged for the protocol capability of the SIP message and the heterogeneous message, the SIP session is sent to the call session control function entity 20.

The non-SIP resource 40 is configured to save the resource that the access request function entity 10 requests to access, and provides the saved resource to the interworking function entity 30. The resource can be accessed through the specification corresponding to the resource identifier. For example, the protocol corresponding to the HTTP URI is an HTTP protocol message, and the FTP URI corresponds to an FTP protocol message. Specifically, the resource can be a file, a streaming link, a service, and the like.

The interfaces between devices in the system are described as follows:

Interface E1: Located between the access request function entity 10 and the call session control function entity 20. The interface E1 uses the SIP protocol. The E1 interface can be either a direct interface or an indirect interface. The indirect interface refers to other intermediate nodes between the access request function entity and the call session control function entity.

Interface E2: Located between the call session control function entity 20 and the interworking function entity 30. The interface E2 uses the SIP protocol. The E2 interface can be either a direct interface or an indirect interface. The indirect interface refers to other intermediate nodes between the call session control function entity and the interworking function entity.

Interface E3: Located between the interworking function entity 30 and the non-SIP resource 40. The interface E3 uses a non-IP application protocol. Specifically, the application protocol corresponding to the compliant scheme is identified for the resource. For example, the HTTP protocol corresponding to the HTTP URI, the FTP protocol corresponding to the FTP URI, and the like. The E3 interface can be either a direct interface or an indirect interface.

The non-SIP resource location information, specifically, in the foregoing architecture for implementing access to the non-SIP resource, may be:

(1) The access request function entity 10 presets a preset route set in the access request, including routing information that the non-SIP resource access request must pass before reaching the accessed non-SIP resource 40, such as the call session control function entity 20. And the routing information of the interworking functional entity 30, etc.; according to the routing information preset in the preset routing set, the non-SIP resource access request can finally reach the accessed non-SIP resource 40 after passing through the call session control function entity 20 and the interworking function entity 30. , and will not be rejected by the network side during the routing process; or

(2) the converted resource identifier; the access request function entity 10 determines that the access resource is The non-SIP resource converts the data according to the preset resource identifier, converts the resource identifier to conform to the resource identifier syntax approved by the SIP protocol, and sends the converted resource identifier as a non-SIP resource location information to the call session in the access request. The control function entity 20: the call session control function entity 20 routes the route to the interworking function entity 30 according to the preset configuration data; the interworking function entity 30 converts the resource identifier according to the resource identifier preset on the interworking function entity 30, and restores the resource identifier. The protocol capability interworking is completed, and the request is sent to the accessed non-SIP resource 40.

The configuration data preset in the call session control function entity may be an Initial Filter Criteria (IFC), and the interworking function entity may be an AS; the configuration data may also be related routing data after the resource identifier is converted. If the routing data is configured on the DNS, the call session control function entity 20 sends a request to the interworking function entity 30 accordingly. In this case, the interworking function entity can be an IBCF.

Specifically, the structure of the access request function entity 10 for performing resource identifier conversion is as shown in FIG. 2, and further includes:

The non-SIP resource location information generating module 11 is configured to receive the non-SIP resource identifier information to be accessed and generate the non-SIP resource location information, and send the generated non-SIP resource location information to the access request initiation module. Specifically, the non-SIP resource location information generating module is configured to receive the to-be-accessed The non-SIP resource identification information is used to complete the non-SIP resource identification to the resource identifier conversion function supported by the SIP protocol, and the converted resource identifier is sent to the access request initiation module 12 as the non-SIP resource location information.

The access request initiating module 12 adds the non-SIP resource location information received from the non-SIP resource location information generating module 11 to the SIP access request, and sends the SIP access request to the call session control function entity 20. The request can carry non-SIP resource location information through a Request-URI or a route header field.

Further, the access request function entity 10 may further include:

The first interaction module 13 is configured to receive an instruction from the user, obtain the non-SIP resource identification information to be accessed, and transmit the information to the resource identifier conversion module 11.

The second interaction module 14 is configured to receive the message of the other network entity, obtain the identifier information of the non-SIP resource to be accessed, and transmit the information to the resource identifier conversion module 11; The identification information of the non-SIP resources may be pre-configured locally or from messages received by the first interaction module 13 from other entities.

The first interaction module 13 of the access request function entity 10 obtains the non-SIP resource identification information to be accessed according to the instruction from the operator, or the second interaction module 14 receives the message of the other entity, after the resource identifier conversion module 11 converts the resource identifier. The SIP access request is issued by the access request initiating module 12.

The structure of the interworking function entity 30 is as shown in FIG. 3, and further includes:

The SIP message module 31 is configured to receive a SIP access request sent by the call session control function entity 20 from the IMS domain, and send the request to the protocol capability conversion module 32 to complete the protocol capability interworking. In addition, it is further configured to receive an access response message from the protocol capability conversion module 32, and respond to the SIP access request sent to the call session control function entity 20 in a SIP message format.

The protocol capability conversion module 32 is configured to receive a message from the SIP message module 31 or the heterogeneous message module 33, and complete protocol protocol interworking conversion between the SIP message and the heterogeneous message. Specifically, the SIP message from the SIP message module 31 is converted into a non-SIP heterogeneous message and sent to the heterogeneous message module 33, and the non-SIP heterogeneous message from the heterogeneous message module 33 is converted into a SIP message and sent to the SIP. Message module 31.

The heterogeneous message module 33 is configured to receive a non-SIP resource access request from the protocol capability conversion module 32, send the non-SIP resource access request to the non-SIP resource function entity 40, and further, receive the non-SIP resource 40. The access response message is sent to the protocol capability conversion module 32. Specifically, the heterogeneous message may be a protocol message corresponding to the non-SIP resource identifier, such as an HTTP protocol message corresponding to the HTTP URI, and an FTP protocol message corresponding to the FTP URI.

By using the above-mentioned system and device provided by the present invention, the protocol conversion function between the access request function entity and the server where the non-SIP resource is located is realized by the protocol conversion function of the interworking function entity, so that the IMS network user or other network element can pass the SIP. Establishing access to non-SIP resources; in addition, generating non-SIP resource location information according to the request for accessing non-SIP resources on the access request function entity, so that the request for accessing the non-SIP resource can reach the interworking function entity and is finally located by the non-SIP resource Server attached Accepted.

An embodiment of the present invention further provides a method for implementing non-SIP resource access. As shown in FIG. 4, the method includes the following steps:

Step sl01: The access request function entity in the IMS network initiates an access request for accessing the non-SIP resource to the call session control function entity.

Specifically, the access request function entity initiates a SIP access request for the non-SIP resource, completes the location processing of the non-SIP resource in the SIP domain, and generates the non-SIP resource location information, where the non-SIP resource location information is carried in the access request.

The non-SIP resource location information may be a preset route set preset by the access request function entity in the access request, where the preset route carries the next hop and the multi-hop of the non-strict route. Using the route set, the SIP access request initiated by the access request function entity can reach the interworking function entity via the call session control function entity.

Alternatively, the non-SIP resource location information may also be a converted resource identifier, and the access request function entity determines that the access resource is a non-SIP resource, converts the data according to the preset resource identifier, and converts the resource identifier to conform to the resource approved by the SIP protocol. The identifier syntax is sent to the call session control function entity in the access request as the non-SIP resource location information.

Step sl02: The call session control function entity routes the access request sent by the access request function entity to the interworking function entity.

Specifically, the routing method is: when the non-SIP resource location information is a preset route set, the interworking function entity is obtained according to the preset route set carried in the access request, and the access request is routed to the interworking function entity. Or, when the non-SIP resource location information is the converted resource identifier, the call session control function entity routes the access request to the interworking function entity according to configuration data preset in the call session control function entity, such as an IFC.

Step sl03: The interworking function entity completes the protocol capability interworking conversion between the SIP message and the heterogeneous message according to the resource requested in the received access request, and sends the request to the accessed resource.

Specifically, when the non-SIP resource location information is a preset route set, the interworking function entity converts the SIP request into a heterogeneous message request according to the requested non-SIP resource identifier, and completes The protocol capability interworking converts the converted request to the accessed non-SIP resource. Or, when the non-SIP resource location information is the converted resource identifier, the interworking function entity converts the data according to the preset resource identifier, restores the non-SIP resource identifier, completes the protocol capability interworking conversion, and sends the converted request to the accessed non-access SIP resources.

Step sl04: The interworking function entity receives an access response message from the non-SIP resource, and performs a protocol capability interworking conversion between the heterogeneous message and the SIP message, and then sends a SIP response message to the call session control function entity.

The accessed non-SIP resource information may be carried in the SIP response message and finally reach the access request function entity, or may be delivered by the SIP session in a bearer channel established between the interworking function entity and the access request function entity.

Step sl05: The call session control function entity routes the response message to the access request function entity.

The specific implementation manner of the method for implementing non-SIP resource access in the above steps slO1 to sl05 is described below in combination with several specific application scenarios.

A method for accessing non-SIP resources is provided in Embodiment 1 of the present invention. Specifically, the UE in the IMS domain serves as an access request function entity, and initiates an access request for an HTTP URI. According to the preset route set, the request first reaches the interworking function entity, and the interworking function entity converts the SIP request into an HTTP access request. Complete access to the non-SIP resource. The process is shown in Figure 5, and specifically includes the following steps:

Step s201: The user sends an access request to the non-SIP resource to the call session control function entity, where the request message carries a preset route set.

Specifically, the user initiates an access request for a non-SIP resource as an access request function entity. The request may be a SIP Invite message, where the SIP message carries a preset route set, and the preset route set gives the next and multiple hops of the non-strict route, including the routing information and the interworking function of the call session control function entity. Routing information of the entity;

In the embodiment of the present invention, the request resource and the preset route can be expressed by the SIP protocol: 3⁄4:

INVITE http://www.ietf.org/rfc/rfc3261.txt

Route:<sip:orig@scscfl.home.com;lr> Route :<sip: ias .home .com;lr>

Step s202: The call session control function entity receives an access request from the user, and sends the request to the interworking function entity that is the next hop of the preset route set.

Step s203: The interworking function entity receives the access request, completes the protocol capability interworking of the SIP protocol and the heterogeneous protocol, and converts the SIP request into a non-SIP access request.

Step s204: The interworking function entity establishes a connection according to the resource identifier to be accessed in the converted non-SIP access request.

Step s205: The interworking function entity initiates access to the non-SIP resource.

In this embodiment, an access of the HTTP URI http: 〃 www.ietf.org/rfc/rfc3261.txt is given, and the interworking function entity converts the SIP request into an HTTP GET request, establishes a TCP connection to the resource, and sends the HTTP. GET request.

Step s206: The non-SIP resource sends an access response to the interworking function entity.

Step s207: The interworking function entity converts the heterogeneous message and the SIP message, and converts the non-SIP message into a SIP message.

Step s208: The interworking function entity sends a SIP response message to the call session control function entity.

Step s209: The call session control function entity sends a SIP response message to the UE. In the above process, the UE is used as an access request function entity as an example to implement access to non-SIP resources. For other non-SIP resource accesses, the method of this embodiment is equally applicable. Moreover, the method of this embodiment is also used for other devices that can be used as the access request to initiate the function entity, such as AS, MRFP, etc., and the description is not repeated here.

A method for accessing non-SIP resources is provided in Embodiment 2 of the present invention. The UE, as an access request function entity, initiates an access request according to the human-machine interaction information or the indication of other network elements, and converts the non-SIP resource identifier to conform to the resource identifier syntax recognized by the SIP protocol by using the resource identifier conversion data preset in the UE. And routing it to the call session control function entity for serving; the call session control function entity routes the route session to the interworking function entity according to the preset configuration data; the interworking function entity converts the data according to the preset resource identifier, and restores the resource identifier The non-SIP resource is obtained, so that the UE accesses the non-SIP resource. The process is shown in Figure 6, and specifically includes the following steps: In step s301, the UE functions as an access request function entity, and uses the resource identifier conversion data preset in the UE to convert the non-SIP resource identifier to conform to the resource identifier syntax approved by the SIP protocol.

Step s302: The UE initiates an access request for a non-SIP resource as an access request function entity.

Specifically, the access request may be a SIP Invite request, where the request includes a SIP identity-approved resource identifier syntax obtained by converting the non-SIP resource identifier, and the UE routes the call session control function entity to the UE. E.g:

Convert the request resource identifier http://www.ietf.org/rfc/rfc3261.txt to the following SIP URI:

SIP: httpApp@http: 〃 www.ietf.org/rfc/rfc3261.txt

Step s303 ~ Step s304: The call session control function entity receives an access request from the user, and routes it to the interworking function entity according to the preset configuration data.

For example, if the initial filtering rule IFC is preset on the call session control function entity, the IFC trigger condition is that the SIP request URI includes a string "httpApp" triggering, and routing it to and as an application server of the interworking function entity.

Step s305: The interworking function entity receives the access request, and restores the access resource identifier according to the preset data.

Step s306: The interworking function entity performs the interworking conversion between the SIP capability and the heterogeneous protocol protocol protocol, and converts the SIP request into a non-SIP access request.

Step s307: The interworking function entity establishes a connection with the non-SIP resource according to the resource identifier to be accessed in the non-SIP access request.

Step s308: The interworking function entity initiates access to the non-SIP resource.

In this example, the HTTP URI http://www.ietf.org/rfc/rfc3261.txt is accessed. The interworking function entity converts the SIP request into an HTTP GET request, establishes a TCP connection to the resource, and sends the HTTP. GET request.

Step s309: The non-SIP resource receives the access request and responds to the access request.

Step s310: The interworking function entity completes conversion between the heterogeneous message and the SIP message, and converts the non-SIP response into a SIP response message. Step s311: The interworking function entity sends the converted response message to the call session control function entity.

Step s312: The call session control function entity sends a response message to the UE.

In the above embodiment, the converted resource identifier conforms to the URI syntax and SIP URI syntax required in the prior art, which ensures that the request message is not rejected in the IMS domain. In addition, the data preset on the call session control function entity in the foregoing embodiment is the initial filtering rule IFC, and may actually be the routing information related to the converted resource identifier. According to the routing information, the call session control function entity may The access request is routed to the interworking function entity.

By using the above method provided by the present invention, the protocol conversion function between the access request function entity and the server where the non-SIP resource is located is realized by the protocol conversion function of the interworking function entity, so that the IMS network user or other network element can establish the arrival through the SIP. Access to non-SIP resources; in addition, by generating non-SIP resource location information according to the request for accessing non-SIP resources on the access request function entity, the request for accessing the non-SIP resource can reach the interworking function entity and finally the server where the non-SIP resource is located Accepted.

Through the description of the above embodiments, those skilled in the art can clearly understand that the present invention can be implemented by means of software plus a necessary general hardware platform, and of course, can also be through hardware, but in many cases, the former is a better implementation. the way. Based on such understanding, the technical solution of the present invention, which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a storage medium, including a plurality of instructions for making a A computer device (which may be a personal computer, server, or network device, etc.) performs the methods described in various embodiments of the present invention.

In conclusion, the above description is only a preferred embodiment of the present invention and is not intended to limit the scope of the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and scope of the present invention are intended to be included within the scope of the present invention.

Claims

Rights request

A method for accessing a non-session initiation protocol SIP resource, the method comprising:

The interworking function entity converts the SIP access request into a heterogeneous request and sends the request to the server where the non-SIP resource is located;

2. The method for accessing a non-SIP resource according to claim 1, wherein before the SIP access request for accessing the non-SIP resource forwarded by the receiving call session control function entity, the method further includes:

The access request function entity in the IMS network receives the information of the non-SIP resource to be accessed, generates a SIP access request carrying the non-SIP resource location information, and sends the SIP access request to the call session control function entity;

The call session control function entity forwards the access request to the interworking function entity.

The method for accessing a non-SIP resource according to claim 2, wherein the access request function entity generates a SIP access request carrying non-SIP resource location information and sends the SIP access request to the call session control function entity:

Generating a SIP access request for accessing a non-SIP resource, carrying a preset route set as non-SIP resource location information in the SIP access request, and sending the message to the call session control function entity;

The forwarding of the access request by the call session control function entity is specifically: forwarding, according to the preset route set carried in the access request, the access request.

4. The method of accessing a non-SIP resource according to claim 2, wherein The access request function entity generates a SIP access request carrying non-SIP resource location information and sends the SIP access request to the call session control function entity as follows:

Converting the non-SIP resource identifier into an identifier conforming to the SIP protocol by using the resource identifier conversion data preset in the access request function entity, and adding the converted identifier as a non-SIP resource location information in the SIP access request, and The call session control function entity sends;

The forwarding of the access request by the call session control function entity is specifically: routing the access request to the interworking function entity according to the configuration data preset by the call session control function entity.

The method for accessing a non-SIP resource according to claim 4, wherein the configuration data preset on the call session control function entity is specifically:

The initial filtering rule iFC, or the converted resource identifier related routing information.

The method for accessing a non-SIP resource according to claim 4, wherein the interworking function entity converts the SIP access request into a heterogeneous request, specifically:

The interworking function entity converts the identifier in the SIP access request to a non-SIP resource identifier according to the preset resource identifier conversion data, and converts the SIP access request into an isomorphic request.

The method for accessing a non-SIP resource according to claim 1, wherein the converting the heterogeneous response into a SIP response message and transmitting the message to the call session control function entity further includes:

The call session control function entity routes the SIP response to an access request function entity.

The method for accessing a non-SIP resource according to claim 1, wherein the conversion of the heterogeneous response into a SIP response message is specifically:

Adding non-SIP resource data carried in the heterogeneous response message to the SIP response message; or

The non-SIP resource data carried in the heterogeneous response message is not added in the SIP response message, but is transmitted in the bearer channel established according to the session formed by the SIP request and the response message.

A system for accessing a non-SIP resource, the method comprising: an access request function entity, configured to generate a SIP access request carrying non-SIP resource location information, and sending the call to the call session control function entity;

a call session control function entity, configured to route the SIP access request sent by the access request function entity to the interworking function entity, and route the response carrying the non-SIP resource data returned by the interworking function entity to the access request function entity ;

The system for accessing a non-SIP resource according to claim 9, wherein the access request function entity further comprises:

The non-SIP resource location information generating module is configured to receive the non-SIP resource identifier information to be accessed and generate non-SIP resource location information, and send the generated non-SIP resource location information to the access request initiation module;

The system for accessing a non-SIP resource according to claim 9, wherein the interworking function entity further comprises:

a protocol capability conversion module, configured to receive a message from the SIP message module or a heterogeneous message module, complete a protocol capability interworking conversion of the SIP message and the heterogeneous message, and convert the SIP access request from the SIP message module into a heterogeneous Requested to be sent to the heterogeneous a message module, converting the heterogeneous response from the heterogeneous message module into a SIP response, and sending the message to the SIP message module;

The system for accessing a non-SIP resource according to claim 9 or 10, wherein the access request function entity is specifically one of: a user equipment UE, an application server AS, a multimedia resource function processor MRFC, or A variety.

13. The system for implementing access to a non-SIP resource according to claim 9, wherein the call session control function entity is a call session control function CSCF.

The system for accessing a non-SIP resource according to claim 9 or 11, wherein the interworking function entity is an interworking boundary control function IBCF or an application server AS.

15. An access request function entity, comprising:

The access request function entity according to claim 15, wherein the non-SIP resource location information generating module is configured to receive non-SIP resource identifier information to be accessed, and complete non-SIP resource identifier to comply with SIP protocol support. The resource identifier conversion function uses the converted identifier as non-SIP resource location information.

The access request function entity according to claim 15, further comprising:

a first interaction module, configured to receive an instruction from an operator, obtain non-SIP resource identification information to be accessed, and transmit the information to the resource identifier conversion module; and or

The second interaction module is configured to receive the message of the other entity, obtain the identifier information of the non-SIP resource to be accessed, and deliver the information to the resource identifier conversion module.

18. An interworking functional entity, comprising:

a protocol capability conversion module, configured to receive a message from the SIP message module or a heterogeneous message module, complete a protocol capability interworking conversion of the SIP message and the heterogeneous message, and convert the SIP access request from the SIP message module into a heterogeneous After the request is sent to the heterogeneous message module, the heterogeneous response from the heterogeneous message module is converted into a SIP response and sent to the SIP message module;

19. The interworking functional entity of claim 18, wherein:

The protocol capability conversion module is further configured to restore the identifier in the SIP access request sent by the SIP message module to a non-SIP resource identifier according to the preset resource identifier conversion data.