CN1921482B - Method and device for business processing based on conversation initiating protocol - Google Patents

Abstract

The present invention provides a service processing method and device based on the Session Initiation Protocol. The core of the method is: setting terminal equipment identification information for identifying the terminal equipment for the terminal equipment, the SIP node obtains the terminal equipment identification information, and according to the terminal equipment Device identification information for business processing. The present invention can enable each SIP node in the SIP network to obtain terminal device identification information, and enable each SIP node to use the terminal device identification information to process services; thereby realizing the optimization of service processing process, improvement of network security performance, The purpose of improving service quality, improving user satisfaction, and improving IMS network operability and manageability.

Description

A service processing method and device based on session initiation protocol

technical field

The invention relates to the technical field of network communication, in particular to a service processing method and device based on a session initiation protocol.

Background technique

SIP (Session Initiation Protocol, Session Initiation Protocol) is an IP telephony signaling protocol proposed by IETF (Interne Engineering Task Force). As its name implies, SIP is used to initiate sessions, which can control the establishment and termination of multimedia sessions attended by one or more participants, and can dynamically adjust and modify session attributes, such as session bandwidth requirements and transmitted media types Such as voice, video, text, etc., media codec format, support for multicast and unicast, etc.

SIP provides the necessary protocol mechanism to ensure that the terminal system and proxy server provide the following services: user location; user capability; user availability; call establishment; call processing; call forwarding, unconditional call forwarding, etc.; calling number delivery, where the calling number can be a calling number delivery named using any naming scheme; personal mobility, such as reaching the called party through a single, location-independent address Even if the called party changes the terminal; terminal type negotiation and selection, that is, the caller can give a choice how to reach the other party, such as through Internet telephony, mobile phone or answering service, etc.; terminal capability negotiation; caller and callee Authentication; uninformed and guided call transfer; multicast conference invitation, etc.

The protocol mechanisms provided by SIP include: name translation and user location, that is, to ensure that the call reaches the called party no matter where the called party is, perform any mapping of description information to location information, and ensure that the essential details of the call/session are supported; feature negotiation , since not all parties are able to support the same level of features, allowing call-related groups including groups for multi-party calls to agree on features supported; call participant management, that is, participants in a call can introduce other users to join call or cancel the connection to other users, in addition, the user can be transferred or put on hold; call characteristics change, that is, the user should be able to change the call characteristics during the call, such as a call can be set to "voice-only", However, during the call, the user can enable the video function according to actual needs, that is to say, a third party joining the call can enable different features in order to join the call.

With the development of broadband networks, mobile communications will not be limited to traditional voice communications, but multimedia services that combine audio, video, pictures, and texts will gradually develop. The combination of management, short message, WEB (web page) browsing, location information, PUSH (push service), file sharing and other data services can meet various needs of users.

Driven by a variety of applications, standard organizations such as 3GPP and 3GPP2 have successively launched IP-based multimedia subsystem architectures. Provide users with more choices and richer feelings.

In the 3GPP Release 5 (R5) stage, the IP Multimedia Subsystem domain, referred to as IMS, was introduced. IMS is superimposed on the packet domain network, and consists of CSCF (Call State Control Function), MGCF (Media Gateway Control Function), Function) and HSS (Home Subscriber Server) and other functional entities, wherein: CSCF can be divided into three logical entities: S-CSCF (Serving CSCF), P-CSCF (Proxy CSCF) and I-CSCF (Querying CSCF). S-CSCF is the service switching center of IMS, which performs session control, maintains session state, manages user information, generates billing information, etc.; P-CSCF is the access point for terminal users to access IMS, completes user registration, and is responsible for QoS control and security management, etc., I-CSCF is responsible for the intercommunication between IMS domains, manages the allocation of S-CSCF, hides network topology and configuration from the outside, and generates billing data, etc. The MGCF controls the gateway to realize the intercommunication between the IMS network and other networks, and the MRF provides media resources, such as audio playback, codec, and multimedia conference bridge. HSS (Home Subscriber Server) is a user database, which stores subscription data and configuration information of IMS users.

Because the structure of the IMS network is independent of the underlying bearer network, the IMS network defined by 3GPP can also be applied to other packet networks other than the packet domain network defined by 3GPP, such as the packet network defined in 3GPP2, WLAN network, and NGN networks, etc., have achieved independence from the type of user terminal and access network type. Therefore, IMS is not limited to be applied to 3GPP-related networks and applications. Other types of access networks and bearer networks Businesses and applications can also be implemented using the IMS architecture.

Each user who has signed an IMS service is assigned one or more private user identifiers IMPI by the home network operator for use in the registration, authorization, management and billing process. The IMPI uses NAI (Network Access Identifier, Network Access Identifier, Incoming ID) format, each IMS user also has one or more public user IDs IMPU, which are used to identify themselves and find each other when communicating with other users. Private user IDs are generally not disclosed to the outside world, while public user IDs are open to the outside world and used during sessions of various services. The MSISDN used in the existing circuit switching network can continue to be used in the IMS network, and can be regarded as a special public user identity.

HSS is the most important database for each user, which stores all the information related to the subscription, and is used to support the processing of calls and sessions by various network entities. The stored information includes: user identification, number and addressing information, user security information , user location information, and user profile information. A home network can have one or more HSSs, and the number of HSSs depends on the number of mobile subscribers, the capacity of network equipment, and specific networking conditions. There are interfaces between the HSS and various entities in the network.

In IMS, the SIP protocol is used as the signaling control protocol of the IP multimedia session to establish, modify and delete the IP multimedia session to meet the user's requirements for multimedia communication. Compared with the ordinary SIP network, the IMS network has a remarkable feature: the IMS network will be a carrier-class network that can be operated and managed. Users who sign up for the IMS network service will be able to obtain a service quality guarantee by paying a certain fee. At the same time, enjoy other value-added services provided by operators.

Currently, the IMS network uses logical identifiers IMPI and IMPU for identifying users to manage the services of each IMS-subscribed user. In this way, after a user loses his own terminal equipment, the network side can restrict others from using this user. However, since the network side cannot determine whether the terminal device is used by a legal user, anyone who obtains the terminal device can use the terminal device without paying any price. For many users, this kind of loss is unavoidable, which will cause user dissatisfaction, and is also a hindrance to the development of IMS services.

What's more serious is that some user information will be stored more or less in the terminal equipment, such as ISIM/USIM (IMS SIM, the service identification module/universal subscriber identification module used in the IMS network) configured on the terminal equipment of the IMS network , ISIM/USIM stores information such as IMPI (Private User Identity) and IMPU (Public User Identity) used by the user for authentication, and the network side cannot restrict others from obtaining and using this information from the terminal device. impact on security.

Considering the coexistence of multiple access technologies, terminal equipment is evolving towards multi-mode. A terminal equipment can use different access methods to access IMS network services in different access networks. Business processing with identification can no longer meet the maintenance and management needs of operators. For example, the network side does not allow two terminal devices to register repeatedly, but allows one multi-mode terminal device to register at the same time. When a multi-mode terminal device that supports multiple access methods During roaming, the network side cannot determine whether two terminal devices register repeatedly or a multi-mode terminal simultaneously registers according to the user logical identifier.

Considering the user's convenience and habits, the IMS network allows a user to use the same public user ID on multiple terminal devices. The user can choose to use one of the terminals to establish a session with the other party according to the actual situation, but because of the multiple Capabilities that terminal devices can support are likely to be different. Therefore, selecting a terminal device means selecting a range of capabilities that can be supported by subsequent sessions. The implementation mechanism of the current SIP specification can only select the communication according to logical identifications such as public user IDs or private user IDs, thus making the IMS network's support for multi-terminal devices blind and limited.

To sum up, the SIP protocol, as a protocol serving the Internet, cannot meet the carrier-class requirements of the IMS network to a certain extent.

Contents of the invention

The purpose of the present invention is to provide a service processing method based on the session initiation protocol, which optimizes the service processing process by introducing terminal equipment identification information into service management, so that the SIP protocol can meet the requirements of the IMS network carrier level.

In order to achieve the above object, the present invention provides a service processing method based on session initiation protocol, including:

a. Set terminal device identification information for identifying the terminal device for the terminal device;

b. The SIP node acquires the identification information of the terminal equipment, and performs service optimization processing according to the identification information of the terminal equipment.

The SIP node is: a SIP user agent and/or a SIP server.

The SIP node is: a SIP server, and the step of the SIP node obtaining terminal device identification information in the step b specifically includes:

The SIP user agent carries the identification information of the terminal device in the SIP message and transmits it to the SIP server;

The SIP server acquires terminal device identification information from the SIP message it receives.

The SIP node is: a SIP user agent, and the step of the SIP node obtaining terminal device identification information in the step b specifically includes:

b1. The SIP user agent obtains the terminal device identification information from the information stored in the terminal device; and/or

b2. Other SIP nodes transmit the identification information of the terminal equipment in the SIP message to the SIP user agent;

b3. The SIP user agent obtains the terminal device identification information from the SIP message it receives.

Described step b2 specifically comprises:

The SIP server allocates identification information for identifying the terminal device to the terminal device, and transmits the terminal device identification information to the SIP user agent in a SIP message; and/or

Other SIP user agents carry the terminal device identification information in the SIP message, and transmit it to the SIP user agent through the SIP server.

The step of transmitting through the SIP server is: transparently transmitting through the SIP server, or performing corresponding processing on the SIP message through the SIP server before transmitting.

The terminal device identification information in step b is: the calling terminal device identification information and/or the called terminal device identification information.

The terminal device identification information includes: a terminal device identifier; or

The terminal device identification information includes: a terminal device identification type and a terminal device identifier.

The terminal equipment identification type includes: MAC, IMEI, MEID.

The terminal device identifier includes: a public user identifier and a terminal device index value.

The public user identity includes: IMPU, MSISDN.

The step of carrying the identification information of the terminal equipment in the SIP message specifically includes:

x. Extending the SIP message, carrying the identification information of the terminal device in the extended domain of the SIP message; or

y. Carrying the identification information of the terminal equipment in a predetermined field in the SIP message.

Described step x specifically comprises:

A feature tag is added in the Contact header field of the SIP message, and the terminal device identification information is carried in the SIP message according to the added feature tag.

The predetermined field in step y includes: Call-Info information field.

The present invention also provides a service processing device based on the session initiation protocol, and the service processing device includes: a terminal device identification acquisition module and a service processing module;

The acquiring terminal equipment identification module: acquiring terminal equipment identification information, and transmitting it to the service processing module;

Business processing module: perform business optimization processing according to the received terminal equipment identification information.

It can be seen from the description of the above technical solution that the present invention can effectively identify terminal equipment by setting identification information, and transmit terminal equipment identification information between SIP nodes, such as transmitting terminal equipment between SIP user agents and SIP servers, and between different SIP user agents Identification information, so that each SIP node in the SIP network can obtain terminal equipment identification information, so that each SIP node can use this terminal equipment identification information to optimize the service; for example, the SIP server can restrict illegal users according to the terminal equipment identification information Use other people's terminal equipment to realize services; for example, the SIP server can restrict others from illegally using legal user authentication IMPI, IMPU and other information through the association between authentication information and terminal equipment identification information, ensuring the security of user communication; another example, SIP The server can accurately distinguish the repeated registration of two terminal devices or the simultaneous registration of a multi-mode terminal according to the identification information of the terminal device; in addition, the SIP proxy and the SIP server can also control subsequent services through the association between the identification information of the terminal device and the supporting functions of the terminal device The realization of the following business guarantees the realizability of the follow-up service, so that the IMS network can better support multiple terminal devices; the present invention provides a variety of methods for utilizing SIP messages to carry terminal device identification information, and the implementation method is flexible; thus the present invention provides The technical solution realizes the purpose of optimizing business processing process, improving network security performance, improving service quality, improving user satisfaction, and improving IMS network operability and manageability.

Description of drawings

Fig. 1 is a schematic diagram 1 of the business processing method of the present invention;

Fig. 2 is the second schematic diagram of the business processing method of the present invention;

Fig. 3 is the third schematic diagram of the business processing method of the present invention;

Fig. 4 is a fourth schematic diagram of the service processing method of the present invention.

Detailed ways

When the network side is processing related services, it is not enough to only consider the user's logical identification information. If the network side is performing related service processing, it can obtain the identification information used to identify the terminal device and introduce the terminal device identification information into the relevant business In the process of processing, it can effectively solve many problems in the prior art. For example, when an illegal user uses other people's terminal equipment to realize services, the network side can restrict the service according to the identification information of the terminal equipment; When using information such as IMPI and IMPU authenticated by legitimate users, the network side can limit the illegal use of others through the association between authentication information and terminal device identification information, ensuring the security of user communication; in addition, when multiple interfaces are supported When a multi-mode terminal device in the access mode roams, the network side can accurately determine whether two terminal devices are registered repeatedly or a multi-mode terminal is simultaneously registered according to the identification information of the terminal device; in addition, when the terminal device is selected incorrectly, the network The implementation of subsequent services can be controlled on the side by associating the identification information of the terminal equipment with the supporting functions of the terminal equipment, which ensures the realizability of the subsequent services and enables the IMS network to better support multiple terminal equipment. It can be seen from the above description that the service processing process can be greatly optimized through the identification information of the terminal equipment, thus, it is of great significance for realizing an operable and manageable carrier-class network.

Therefore, the core of the present invention is: setting terminal equipment identification information for identifying the terminal equipment for the terminal equipment, the SIP node obtains the terminal equipment identification information, and performs service optimization processing according to the terminal equipment identification information.

The technical solution provided by the present invention will be further described below based on the core idea of the present invention.

The present invention first needs to set identification information for the terminal equipment. The identification information is different from the user logic identification information, etc. It is mainly used to identify the terminal equipment. An identification information in the present invention uniquely identifies a physical terminal equipment. Therefore, it can be called Terminal device identification information.

The terminal device identification information can be solidified and stored in the terminal device. For example, the terminal device can save the preset self-identification information before leaving the factory and can be read and used by SIP UA (SIP UserAgent, SIP User Agent) in a certain way. ; The terminal device identification information can also be sent to the SIP UA of the terminal device by the network side through message transmission, that is, the network entity with the terminal device identification information distribution function on the network side is registered by the terminal device through the SIP UA and realizes the service. , assign terminal device identification information to the terminal device, and transmit it to the SIP UA of the corresponding terminal device.

A network entity with the function of distributing terminal device identification information such as various SIP servers (SIPServer), the SIP Server can transmit the terminal device identification information it assigns to the terminal device to the SIP UA through the SIP message.

When the SIP Server assigns the terminal device identification information to the terminal device during the process of the terminal device implementing the service through SIP UA, the SIP Server can send the terminal device identification information and the identification information of the business counterparty terminal device to the terminal device through the SIP message The SIP UA on the Internet enables the SIP UA to perform related business processing based on the identification information of the terminal equipment of both parties.

When a terminal device needs to implement services through SIP UA, SIP UA can transmit the terminal device identification information to the SIP node on the network side such as SIP Server, and SIP UA can obtain the terminal device identification information from its own solidified storage information and transmit it To the SIP Server, it can also transmit the terminal device identification information obtained from the received SIP message to the SIP Server. The SIP message here is transmitted by other SIP nodes, such as SIP Server, other SIP UAs, etc.

In addition to transmitting its own identification information to the SIP node on the network side, the SIP UA on the terminal device can also transmit the identification information of the other party's terminal equipment to the network side, that is, transmit the identification information of the calling and called terminal equipment to the SIP Server, It enables the SIP Server to perform relevant business processing according to the identification information of the terminal equipment of both sides of the business.

The SIP UA can transmit the identification information of itself and/or the counterpart terminal device to the SIP Server on the network side through the SIP message.

SIP Server assigns terminal equipment identification information to terminal equipment, and the method for transmitting terminal equipment identification information between SIP UA and SIP Server and different SIP UAs and performing related business optimization processing is shown in Figures 1 to 4.

In Figure 1, the SIP UA on the terminal device transmits the terminal device identification information to the SIP Server in charge of processing business in the SIP network through the SIP request message, and the SIP Server obtains the terminal device identification information from the SIP request message, and uses the terminal device identification information Optimize the business requested by SIP UA.

The SIP Server sends a SIP response message to the SIP UA according to the service processing result, and the SIP UA performs corresponding service processing on the service requested by the terminal device according to the terminal device identification information and the service processing result in the response message received.

In Figure 2, the SIP Server is responsible for allocating terminal equipment identification information to the terminal equipment, and the SIP Server transmits the identification information allocated to the terminal equipment to the SIP UA through a SIP request message. This SIP request message can be generated by the SIP Server itself or can It is a SIP request message from other SIP UA, such as SIP Server receives the SIP request message transmitted by other SIP UA, and performs corresponding processing on the message such as modifying the message content, etc., and then sends it to the SIP UA in Figure 2. After receiving the SIP request message, the SIP UA sends a SIP response message to the SIP Server. In this way, when a terminal device needs to conduct business through SIP UA in the future, SIP UA can carry the terminal device identification information assigned by SIP Server in the service request message, and both SIP Server and SIP UA can use this terminal device identification information to optimize services deal with.

The above description of Fig. 2 is the process of allocating the identification information of the terminal equipment, and the process in Fig. 2 can also be described as: the SIP Server transmits the identification information allocated to the terminal equipment and/or the identification information of the terminal equipment of the service counterparty through the SIP request message To the SIP UA, after receiving the SIP request message, the SIP UA sends a SIP response message to the SIP Server. In this way, in the subsequent service implementation process, the SIP UA can carry the identification information of the terminal equipment assigned by the SIP Server and/or the identification information of the terminal equipment of the service partner in the service request message, that is, the identification information of the calling and called terminal equipment, Both the SIP Server and the SIP UA can use the identification information of the calling and called terminal equipment for business optimization.

In Fig. 3, after receiving the SIP request message sent by the SIP UA, the SIP Server transmits the terminal device identification information allocated to the terminal device to the SIP UA through the response message of the request message. In this way, in the subsequent service implementation process, the SIP UA can carry the terminal device identification information assigned by the SIP Server in the service message, so that both the SIP Server and the SIP UA can use the terminal device identification information for service optimization processing.

The above description of Fig. 3 is the terminal device identification information distribution process, and the process in Fig. 3 can also be described as: after the SIP Server receives the SIP request message sent by the SIP UA, it assigns the identification information and/or Or the identification information of the business counterparty terminal equipment is transmitted to the SIP UA through the SIP response message. In this way, in the subsequent service implementation process, the SIP UA can carry the identification information of the terminal equipment assigned by the SIP Server and the identification information of the other party's terminal equipment in the service message, that is, the identification information of the calling and called terminal equipment, so that the SIP Server and the Both SIP UA can use the identification information of calling and called terminal equipment for business optimization processing.

In addition to the need to transmit, obtain and use terminal device identification information for business optimization between SIP UA and SIP Server, in some application scenarios, device identification information can also be transmitted, saved and service optimized between different SIPUAs The processing is specifically shown in Figure 4.

In Figure 4, SIP UA1 carries its corresponding terminal device identification information in the SIP request message, and transparently transmits it to SIP UA2 through the SIP Server. Here, the SIP Server does not need to identify the terminal device identification information. SIP UA2 can also carry its corresponding terminal device identification information in the SIP response message, and transparently transmit it to SIP UA1 through the SIP Server. Here, the SIP Server also does not need to identify the terminal device identification information. Through the above process, both SIP UA1 and SIP UA2 can obtain the identification information of the calling and called terminal equipment, and use the identification information of the calling and called terminal equipment to perform service optimization processing.

In the descriptions of the above processes, the SIP request message and the SIP response message may be a registration message, an OPTIONS response message, a request and response message for creating a dialog, such as an INVITE message, and the like.

It can be seen from the above description that the present invention can transmit, save and use the terminal equipment identification information between the SIPUA and the SIP Server, or between different SIP UAs through the SIP message, so as to assist and optimize the business processing process.

There are two main methods for transmitting terminal device identification information through SIP messages:

Method 1: Use a new information field added in the SIP message to bear and transmit the terminal device identification information.

The method for carrying and transmitting terminal device identification information in a SIP message is described below by taking adding a new information field, that is, adding a new parameter, in the Contact header field of the SIP message as an example.

The present invention needs to add a new feature tag (featuretag) in the Contact header field of the SIP specification. The feature tag indicates terminal device identification information. The feature tag can be similarly defined as: sip.device_id.

The feature tag can directly carry a specific terminal device identifier, such as the identification information used to identify the terminal device that is uniformly distributed in the SIP network according to a certain rule; the feature tag can also carry the type of terminal device identification information and the specific terminal device at the same time. device identifier. The feature tag may also indicate a part of the terminal device identifier, and the other part may be information originally carried in the Contact header field, such as a public user identifier.

The feature tag can be represented by a character string, for example, firstly, it clearly indicates which type the terminal device identifier is, and secondly, it further indicates a specific terminal device identifier.

There are many types of typical terminal equipment identifiers, that is, the values of the terminal equipment identifier types include: MAC, IMEI, MEID, and so on. Of course, the terminal device identification types are not limited to the above three types, if other types of terminal devices appear in the future, the value of the terminal device identification type can be increased accordingly.

After the value of the terminal device identification type is determined, it is necessary to determine the specific terminal device identifier. If the type of terminal device identification information is IMEI, the subsequent terminal device identifier is the IMEI value stored in the terminal device corresponding to the SIP UA; Another example is that the terminal device identification type is MAC, then the following terminal device identifier is the MAC address stored on the terminal device corresponding to the SIP UA.

There are many specific forms of terminal device identification types and terminal device identifiers in the Contact header field. Here are a few specific examples to illustrate:

Example 1. The message format of the terminal device identification type and terminal device identifier separately represented in the Contact header field is as follows:

Contact:<sip:user@example.com>;audio;video;mobility="mobile";

+message="TRUE";device_id="IMEI";imei="350112408932969";

methods="INVITE,OPTIONS,BYE,CANCEL,ACK";schemes="sip,http"

Among them: the new feature tag in the Contact header field is: device_id, the terminal device identification type is: IMEI, and the specific terminal device identifier is: 350112408932969. The terminal equipment identifier here may have its own independent naming principle, or may adopt an existing naming principle.

The above message format can be transformed into the following assertion:

(&(audio=TRUE)

(video=TRUE)

(sip. mobility=mobile)

(message=TRUE)

(|(sip.identifier=IMEI)(sip.identifier.imei=350112408932969))

(|(sip.methods=INVITE)(sip.methods=OPTIONS)(sip.methods=BYE)

(sip.methods=CANCEL)(sip.methods=ACK))

(|(sip. schemes=sip)(sip. schemes=http)))

Example 2. The message format of combining the terminal device identification type and the terminal device identifier in the Contact header field is:

Contact:<sip:user@example.com>;audio;video;mobility="mobile";

+message="TRUE";device_id="IMEI:350112408932969";

methods="INVITE,OPTIONS,BYE,CANCEL,ACK";schemes="sip,http"

Among them: the new feature tag in the Contact header field is: device_id, the terminal device identification type is: IMEI, and the specific terminal device identifier is: 350112408932969. The terminal equipment identifier here may have its own independent naming principle, or may adopt an existing naming principle.

Example 3. The message format for only setting the terminal device identifier in the Contact header field is:

Contact:<sip:user@example.com>;audio;video;mobility="mobile";

  +message="TRUE";device_id="00-20-ed-aa-49-e8";

methods="INVITE,OPTIONS,BYE,CANCEL,ACK";schemes="sip,http"

Among them: the new feature tag in the Contact header field is: device_id, and the terminal device identifier is: 00-20-ed-aa-49-e8. The terminal equipment identifier here should have its own independent naming principle.

Example 4. The message format for only setting the terminal device identifier in the Contact header field is:

Contact:<sip:user@example.com>;audio;video;mobility="mobile";

  +message="TRUE";device_id="03";

methods="INVITE,OPTIONS,BYE,CANCEL,ACK";schemes="sip,http"

Among them: the newly added feature tag in the Contact header field is: device_id, and the content in the feature tag is a part of the terminal device identifier, such as the second half or the first half or the middle part. The terminal device identifier can be composed of a public user identifier such as IMPU or MSISDN and an index value of the terminal device, and the terminal device identifier can distinguish a certain terminal device among several terminal devices sharing a common user identifier. The terminal device identifier in Example 4 is composed of the IMPU carried in contact and the index value in device_id, that is, the terminal device identifier is sip:user@example.com:03, where the index value of has its own independent Naming principles. Because a character string is filled here, and the two-digit index can represent 100 different values from 0 to 99, so this example can distinguish 100 different terminal devices under the same IMPU. The combined use of the IMPU and the index value can uniquely identify multiple terminals owned by a user and share one IMPU.

After the terminal device identification information is set in the Contact header field, the SIP node can use the transmission mechanism for the Contact header field in the current SIP network to realize the transmission of the terminal device identification information.

Example 5: Reuse the existing UUID namespace and use UUID to uniquely identify a terminal device, specifically: device_id="<urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6>".

Certainly, the method for constructing the identification information of the terminal equipment and the method for adding a new information field in SIP to carry and transmit the identification information of the terminal equipment in the present invention are not limited to the above-mentioned examples.

In Method 1, the terminal device identification information carried in the new information field of the SIP message may be the calling terminal device identification information, the called terminal identification information, or the calling terminal device identification information and the called terminal identification information. Information is also carried in the new information field.

Method 2: Use the existing information field in the SIP message to carry and transmit the terminal device identification information, that is, extend the existing information field in the SIP specification, so that the expanded information field can carry the terminal device identification information. Therefore, the transmission of the identification information of the terminal equipment can be realized by utilizing the existing mechanism.

For SIP nodes that do not know the expanded information domain, do not process the expanded information domain, that is, skip this part of the unknown information domain, and continue to process the subsequent information domain in the SIP message according to the implementation principle of the existing SIP protocol. Therefore, the implementation process of the existing SIP protocol will not be affected.

Taking the extension of the existing Call-Info information field as an example below, the method of using the existing information field in the SIP message to carry and transmit the identification information of the terminal device of the present invention will be described.

The Call-Info information field carries the additional information of the calling party in the request message, and the additional information of the called party in the response message. Therefore, the Call-Info information field is very suitable for transmitting the identification information of the terminal equipment of both parties.

Example 6. Add a new purpose in the Call-Info information field to indicate that the Call-Info information field carries terminal equipment identification information, and the terminal equipment identification type and terminal equipment identifier are separately represented. The message format is as follows:

Call-Info:<urn:imei:350112408932969>;purpose=di

Among them: di is the newly added purpose, the terminal equipment identification type is: IMEI, and the specific terminal equipment identifier is: 350112408932969. The terminal equipment identifier here may have its own independent naming principle, or may adopt an existing naming principle.

Example 7. Use the existing purpose to carry terminal device identification information. The message format is as follows:

Call-Info:<urn:imei:350112408932969>;purpose=info

Among them: info is an existing purpose, the terminal equipment identification type is: IMEI, and the specific terminal equipment identifier is: 350112408932969. The SIP network functional entity that processes this information needs to be able to understand the naming principle of the terminal device identification information, so as to be able to resolve whether the Call-Info information domain carries the terminal device identification information or the original attachment information. The terminal equipment identifier here may have its own independent naming principle, or may adopt an existing naming principle.

Example 8. Add a new purpose in the Call-Info information field to indicate that the Call-Info information field carries terminal device identification information, and the terminal device identification information only includes: terminal device identifier, and its message format is as follows:

Call-Info:<urn:00-20-ed-aa-49-e8>;purpose=di

Where: di is a newly added purpose, and the terminal device identifier is: 00-20-ed-aa-49-e8. The terminal equipment identifier here should have its own independent naming principle.

Example 9. The format of the message that only sets the terminal device identifier in the Contact header field is:

Call-Info:<urn:sip:user@example.com:03>;purpose=di

Among them: di is a newly added purpose, and the terminal device identifier is: sip:user@example.com:03. The terminal device identifier can be composed of a public user identifier such as IMPU or MSISDN and the index value of the terminal device. The terminal device identifier The character can distinguish a certain terminal equipment among several terminal equipments sharing a common user identifier. Here, the first half of the terminal device identifier such as sip:user@example.com can use the existing name, and the second half such as: 03 should have its own independent naming principle.

In the second method, the identification information of the calling terminal device can be carried and transmitted through the SIP request message, and the identification information of the called terminal device can be carried and transmitted through the SIP response message, that is, the identification information of the calling terminal device and the identification information of the called terminal device are different. can be carried in one SIP message at the same time.

The service processing device based on the session initiation protocol provided by the present invention is located in a SIP node, such as in a SIP UA or a SIP Server. The device mainly includes: a terminal device identification acquisition module and a service processing module.

The terminal device identification module is mainly used to obtain terminal device identification information. For example, terminal device identification information can be obtained from SIP messages received by it, such as SIP request messages, SIP responses, etc., or from its own solidified stored information Obtain terminal device identification information, and the terminal device identification acquisition module transmits the acquired terminal device identification information to the service processing module. In addition, this module can also transmit the obtained terminal equipment identification information to the terminal equipment identification acquisition module of other service processing devices through SIP messages. The specific process of transmitting the identification information of the terminal device through the SIP message is as described in the above method, and will not be described in detail here.

The business processing module is mainly used to perform business optimization processing according to the terminal device identification information transmitted by the terminal device identification module, such as restricting illegal users from using other people's terminal devices.

Although the present invention has been described by way of example, those of ordinary skill in the art know that there are many variations and changes in the present invention without departing from the spirit of the invention, and the claims of the application document of the present invention include these variations and changes.

Claims (11)

1. the method for processing business of a dialogue-based initiation protocol is characterized in that, comprising:

Terminal equipment is provided with the Terminal Equipment Identifier information that is used for marking terminal equipment, and described Terminal Equipment Identifier information comprises the Terminal Equipment Identifier symbol, or comprises Terminal Equipment Identifier type and Terminal Equipment Identifier symbol; Described Terminal Equipment Identifier information is different from the user logic identification information, physical terminal equipment of a described Terminal Equipment Identifier information unique identification;

The SIP node obtains Terminal Equipment Identifier information, and carries out Business Processing according to described Terminal Equipment Identifier information; Described SIP node is sip user agent and/or sip server;

The step of obtaining Terminal Equipment Identifier information when described SIP node during for sip server specifically comprises:

Sip user agent transfers to sip server with the Terminal Equipment Identifier information-bearing in sip message;

Sip server obtains Terminal Equipment Identifier information from the sip message of its reception;

The step of obtaining Terminal Equipment Identifier information when described SIP node during for sip user agent specifically comprises:

Sip user agent obtains Terminal Equipment Identifier information from terminal equipment curing canned data; And/or

Other SIP node transfers to sip user agent with the Terminal Equipment Identifier information-bearing in sip message;

Described sip user agent obtains Terminal Equipment Identifier information from the sip message of its reception.

2. the method for processing business of a kind of dialogue-based initiation protocol as claimed in claim 1 is characterized in that, described other SIP node transfers to sip user agent with the Terminal Equipment Identifier information-bearing and specifically comprises in sip message:

Sip server is used in marking terminal equipment mark information for the terminal equipment branch, and the Terminal Equipment Identifier information-bearing is transferred to sip user agent in sip message; And/or

Other sip user agent in sip message, and transfers to described sip user agent by sip server with the Terminal Equipment Identifier information-bearing.

3. the method for processing business of a kind of dialogue-based initiation protocol as claimed in claim 2 is characterized in that, described step by sip server transmission is: by the sip server transparent transmission, or transmit after by sip server sip message being carried out respective handling.

4. as the method for processing business of the described a kind of dialogue-based initiation protocol of arbitrary claim in the claim 1 to 3, it is characterized in that described Terminal Equipment Identifier information is: calling terminal equipment identification information and/or terminal called equipment identification information.

5. the method for processing business of a kind of dialogue-based initiation protocol as claimed in claim 1 is characterized in that, described Terminal Equipment Identifier type comprises: MAC, IMEI or MEID.

6. the method for processing business of a kind of dialogue-based initiation protocol as claimed in claim 1 is characterized in that, described Terminal Equipment Identifier symbol comprises: public user identity and terminal equipment index value.

7. the method for processing business of a kind of dialogue-based initiation protocol as claimed in claim 6 is characterized in that, described public user identity comprises: IMPU or MSISDN.

8. the method for processing business of a kind of dialogue-based initiation protocol as claimed in claim 1 or 2 is characterized in that, described the step of Terminal Equipment Identifier information-bearing in sip message is specifically comprised:

The expansion sip message, with the Terminal Equipment Identifier information-bearing in the territory of sip message expansion; Or

In the predetermined domain of Terminal Equipment Identifier information-bearing in sip message.

9. the method for processing business of a kind of dialogue-based initiation protocol as claimed in claim 8 is characterized in that, described expansion sip message specifically comprises the Terminal Equipment Identifier information-bearing in the territory of sip message expansion:

In the Contact header field of sip message, increase feature tag, according to the feature tag of described increase with the Terminal Equipment Identifier information-bearing in sip message.

10. the method for processing business of a kind of dialogue-based initiation protocol as claimed in claim 1 is characterized in that, described predetermined domain comprises: the Call-Info information field.

11. the business processing device of a dialogue-based initiation protocol, described device comprises: obtain Terminal Equipment Identifier module and Service Processing Module;

The described Terminal Equipment Identifier module of obtaining: obtain Terminal Equipment Identifier information, and transmit it to Service Processing Module, described Terminal Equipment Identifier information comprises the Terminal Equipment Identifier symbol, or comprises Terminal Equipment Identifier type and Terminal Equipment Identifier symbol; Described Terminal Equipment Identifier information is different from the user logic identification information, physical terminal equipment of a described Terminal Equipment Identifier information unique identification;

Described device is sip user agent and/or sip server;

The described Terminal Equipment Identifier module of obtaining specifically is used for when described device is sip server:

Sip user agent transfers to sip server with the Terminal Equipment Identifier information-bearing in sip message;

Sip server obtains Terminal Equipment Identifier information from the sip message of its reception;

The described Terminal Equipment Identifier module of obtaining specifically is used for when described device is sip user agent:

Sip user agent obtains Terminal Equipment Identifier information from terminal equipment curing canned data; And/or

Other SIP node transfers to sip user agent with the Terminal Equipment Identifier information-bearing in sip message;

Described sip user agent obtains Terminal Equipment Identifier information from the sip message of its reception;

Service Processing Module: the Terminal Equipment Identifier information according to its reception is carried out Business Processing.

Images