RU2387103C2 - Method and system for establishing connection between network elements - Google Patents

Abstract

FIELD: information technology.

SUBSTANCE: invention proposes a method and a system for establishing or processing a connection between a first and a second network element connected to different networks, e.g. a GPRS/UMTS based network and to an IP based network. Connection is established through at least a third network element e.g. SGSN or GGSN which is in one of the said networks. The third network element can send a query to a fourth network element which can be an element which provides a call state control function (CSCF), an element which provides a strategy control function (SCF), or a call processing server (CPS) when connection establishment information is received. Through a query, permission for establishing the requested type of connection is requested or a request is given to check the connection parametre. The first and/or second network element and/or the established connection or the type of connection is indicated in the query. The fourth network element returns a reply containing permission for establishing connection or type of connection, or in which the connection parametre is indicated.

EFFECT: improved process of establishing connection between various network elements.

98 cl, 7 dwg

Description

FIELD OF THE INVENTION

The invention relates to a method and system for establishing a connection between two or more network elements. This connection can be, for example, a call via the Protocol PDPSI (VoIP) (voice over Internet Protocol (IP)). For this connection, for example, a network layer or a network providing telephone communication via the Internet, and a network based on SPROP / USMS (General Packet Radio Communication System / Universal Mobile Communication System), (GPRS / UMTS), providing call transfer, can be used .

State of the art

To ensure appropriate establishment and processing of a connection between network elements, for example, between subscriber equipment, which is, for example, a mobile terminal, and another terminal or another database, etc., one or more intermediate network elements are usually used, for example support nodes. To specify the characteristics of the connection, one or more connection parameters are used, for example, contextual information about the DAA (packet data transfer protocol) (PDP), information about the required or provided quality of service (QoS), information about charging, for example, the payment rate , etc..

In particular, in the case when the connection is carried out using two or more networks of various types, for example, networks that use different transmission protocols, for example, networks based on SPROP / USMS (public packet radio communication system / universal mobile communication system) and networks Based on the Internet Protocol (IP), problems may arise when establishing an appropriate connection and setting connection parameters.

SUMMARY OF THE INVENTION

The present invention provides a method and system by which an appropriate process for establishing a connection between network elements, for example, located in different networks, mainly as set forth in the attached claims, can be provided.

An appropriate procedure for establishing or processing a connection, for example, for charging, can be implemented by exchanging requests and responses between the third and fourth network elements related to obtaining permission to establish a connection (or the type of connection, for example a connection using DAA), or to a connection parameter , for example, to QA (to quality of service), whereby they provide appropriate connection service.

The third network element may be a support node, which preferably is a gateway support node, and the fourth network element may be an element that provides FUSW (call state control function (CSCF)) or FUS (strategy control function (PCF)), or OWL (call processing server (CPS)). The fourth network element can be a part of the network layer that provides telephone communications over the Internet, or itself provide it.

According to one of the features of the present invention, information is exchanged between a packet switched network (CP) network area (for example, a BSS (gateway support SPROP) (GGSN) or a BSS (gateway service support node) (SGSN)) and between the elements of the multimedia network subsystem based on the Internet Protocol (IM) (providing FUSW).

According to one preferred embodiment of the invention, the fourth network element, which is, for example, the network level of telephone communications over the Internet, is provided with the ability to control at least one connection parameter, for example, to limit activation or modification of the DAA context (packet data protocol) . For example, the DAA dialogue context, that is, a connection that allows voice communication between the calling and called subscribers, can only be activated when the first network element, such as a mobile terminal, attempts to call the second network element. For example, in the case where the connection parameter is the DAA context, and an activation request is made or the DAA context is changed, the third network element, for example, Hub, can send a request for permission to connect to the fourth network element, for example, to the element providing FUSW or FUS, or in the COB, to verify the validity of the activation of the DAA context or its modification.

This approach provides several advantages. Firstly, the fourth network element, for example, FUSW, receives information from the request about the address of the third network element, for example, Hub, and, therefore, it knows the address to which the response should be returned. Otherwise, when the fourth network element is configured to transmit information to the third network element before address information from the third network element is transmitted to it, then if the fourth network element does not contain address information of the third network element, responsible for maintaining the connection, problems may occur.

Even in the case when, when trying to establish a connection, for example, a call, the first network element, for example, a mobile terminal, must transmit information directly to the fourth network element, the first network element has not yet received information about the address of the third network element, which provides subsequent connection maintenance and therefore, it is not able to transmit this address information to the fourth network element. In addition, if at first a message, for example, an access authorization message, was transmitted from the fourth network element to the third network element, the third network element would have to memorize information about the call processing parameters, for example, DAA contexts that are not yet active. After this, the third network element may have to activate the timer and delete access authorization information after a period of time specified by the timer, if for some reason activation of the DAA context should not be performed.

In addition, the solution proposed in the present invention is also applicable to subscribers using roaming, which, therefore, provides additional benefits.

In the General case, according to one of the features of the present invention, it proposes a solution that restricts, for example, activation or modification of the DAA context, based on the characteristics of the call, the transfer of which is based on the DAA context.

According to one preferred embodiment of the invention, in networks or network layers operating in accordance with various protocols, for example, in the SPROP / USMS layer and in the network layer that provides telephone communications over the Internet, as well as in a means of controlling or performing functions such as FUSW or FUS create a common identifier. This common identifier can be used to display the DAA context in the call. The common identifier may be, for example, the Call Identifier "Call Identifier" (Call_Id), already available in the messages PISS (Protocol initiation of communication session (SIP)).

Alternatively, the common identifier may also be an identifier located in one of the network layers, for example, in the SPROP / USMS layer. For example, in this case, the common identifier may be ITDSS (Network Service Access Point Identifier (NSAPI)). In a preferred embodiment, this common identifier is transmitted to the fourth network element, for example, to the element providing the FUSW, in a protocol message, for example, in an "INVITE" PESS message. Then, a common identifier (for example, ITDSS) can be transferred from the third network element, for example, from SCWS, to the fourth network element (for example, to the element providing FUS), and also from the fifth network element (for example, from FUSW) to the fourth network element . After this, the fourth network element establishes the correspondence of the request (transmitted by the third network element) and access permission (transmitted by the fifth network element, for example, an element providing FUSW), based on a common identifier, for example ITDSS.

According to another preferred embodiment of the invention, it provides means for combining a connection parameter, for example, charging information generated in the first network, for example, in the core mobile communication network (for example, in the LMSS and STPS), and in the second network, for example in the TSPI core network (telephony based on the Internet protocol) (IPT), for example, in the COB. In this embodiment of the invention, it is possible to charge for the level of QoS (quality of service) used for telephone communications.

According to this aspect of the invention, there is provided a means for combining call charging information and managing correspondence between reservation of TO in a single network (for example, in a TSPI network in which transmission of data on a reservation of TO TSPI is carried out, for example, in the PISS "INVITATION" message) and reservation QoS (by activating the context, for example, the QoS context of the DAA) in another network (for example, in the core mobile network with packet data transmission). For example, for charging tasks, the transmitted identifier Call_ID (Call_Id) is checked, and the correspondence level of the requested QoS or request is checked both in the protocol message (for example, in the PISS "INVITATION" message) and in the activation message (s) DAA context.

When activating the DAA context, a new parameter can be introduced by means of which a third network element, for example, Hub, is notified of the fourth network element, which is, for example, an element that provides service to the FUSW or the combination of FUSW / FUS, or OWL. Therefore, it is ensured that the third network element receives information about the address of the fourth network element to which the request for QoS verification should be sent.

Another optional characteristic, which can be controlled by the end user, is the ability of the terminal device (for example, the first network element) to transmit the request for QoS verification contained in the protocol message, for example, in the PISS "INVITATION" message.

According to this feature of the invention, it is possible to compile a payroll statement based on data on the TO.

BRIEF DESCRIPTION OF THE DRAWINGS

In FIG. 1 shows the basic structure and flow of messages according to one embodiment of the method and system of the present invention;

in FIG. 2 shows another embodiment of a system and method according to the present invention;

in FIG. 3 shows yet another embodiment of a system and method according to the present invention;

in FIG. 4 shows yet another embodiment of a system and method according to the present invention;

in FIG. 5 shows yet another embodiment of a system and method according to the present invention;

in FIG. 6 shows a modified embodiment of the system and method of FIG. 2; and

in FIG. 7 shows another embodiment of a system and method according to the present invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

In FIG. 1 shows a first embodiment of a method or system according to the present invention. This embodiment provides the activation or modification of the DAA context allowed by the element performing the FUSW. The first network element is a user equipment (AO) 1, which may be a mobile station. SHUPO 2 is a service node (gateway service support node SPROP), providing maintenance of subscriber equipment 1 while maintaining a connection with another network element (with the second network element), which is, for example, the terminal device of the called subscriber, not shown in FIG. 1. SCWS (gateway support node SPROP) 3 is a gateway node through which connections are made to another network to which the terminal device of the called subscriber can be connected. The fourth network element is element 4, which provides a call state management function (an element that provides FUSW), which decides whether to enable or modify the DAA context.

In the case when, using subscriber equipment 1, an attempt is made to make a call to a terminal device located in another network, for example, a network based on the Internet protocol (IP), subscriber equipment 1 transmits to element 4 providing FUSW, a message, for example, a PESS message ( Session Initiation Protocol) "INVITATION". After that, preferably after receiving from the element 4 providing FUSW, a response message notifying the acceptance of the request to establish a call, the subscriber equipment 1 transmits a request to activation (or change) of the DAA context to the VLBF 2. In response to this request for activation (or change) of the DAA context, STUP 2 sends to SCPS 3 a request to create (or update) the DAA context.

ШУПС 3 is made in such a way that, in response to this request, received from ШУПО 2, it does not immediately perform the operation of creating or updating DAA contexts, but first sends a request for permission to the element 4 providing the FUSW. In the embodiment shown in FIG. 1, SCWS 3 sends this request for permission to element 4, providing FUSW, to check the validity of activation / modification of the DAA context. In a modified embodiment, a request for permission may also be transmitted to an element providing a strategy management function (FUS), which may be an additional optional network element or may be combined with an element providing an FUSW.

The structure of the request for authorization of SHUPS 3 includes MIAMS / MNPSTSKU (International Mobile Subscriber Identity ID, IMSI / International Mobile Station Number in the Integrated Services Digital Network (ISDN), MSISDN) (and, possibly, the DAA), by which they provide recognition mobile telephone apparatus, that is, subscriber equipment 1. As part of the request for permission, the SCS 3 may additionally transmit the requested QoS values (quality of service), as well as the address of the called subscriber (subscriber address B) if it is present in the traffic flow template (TFT) (TFT). In the event that MIAMS / MNPSTSKU (and, possibly, the address of the DAA) are not sufficient for identification of the subscriber equipment 1 or the call, additional information can be used, for example, ITDSS, which is transmitted to the SCPS 3. In this case, the preferred option is that in which the subscriber equipment 1 transmits information about the ITDSS of the DAA context to the element providing FUSW, in the message transmitted during the establishment of the call, for example, in the message PISS "INVITATION". In this case, the element 4 providing the FUSW (or alternatively or additionally providing the FUS) is made in such a way that it verifies that the ITDSS for the call contained in the message transmitted during the establishment of the call is equivalent to the ITDSS for the DAA context transmitted from ШУПС 3 as part of the request for permission, therefore, element 4 providing FUSW (or element providing FUS), can give permission to use the correct context DAA. In the case of the presence of a separate element providing FUS, element 4 providing FUSW, is designed in such a way that ensures the transfer of ITDSS to the element providing FUS. Similarly, in this case, the BSS 3 is designed in such a way that it ensures the transfer of the request for a permit containing ITDSS to a separate element providing the FUS.

In response to a request for permission and after performing the above verification operation, element 4 providing FUSW (or an element providing FUS) transmits an authorizing response to STMC 3. The authorizing response contains MIAMS / MNPSTSKU, through which the identification of subscriber equipment 1 or call for which the DAA context is to be created or updated, and in a preferred embodiment, the enabling response further comprises information such as, for example, “call characteristics”. In a preferred embodiment, the information about the characteristics of the call contains acceptable QoS values, acceptable information about subscriber B (which in the preferred embodiment is the IP address and port number of the called subscriber), as well as a pointer by which indicate whether the call is a regular call or an urgent call .

ШУСС 3 is made in such a way that sets the QoS values equal to those obtained from the element 4 providing FUSW (or from the element providing FUS). ШУПС 3 can set the highest priority value of allocation / conservation of resources in case the call is an urgent call. In addition, ШУС 3 can set a traffic flow pattern (ШПТ) in accordance with information about subscriber B.

In the event that the call is an urgent call, and the DAA context is used for this urgent call, the subscriber equipment 1 can be notified of it by transmitting this information from the STM 3 to the STM 2, which sends this information to the user equipment 1 (mobile communication) .

In order to transmit a request for a permit, ШУС 3 must have information about the address of the element 4, which provides FUSW, to establish communication with it. In one embodiment of the invention, the address of the element providing FUSW is added as a new parameter to the message requesting the activation (or modification) of the DAA context and to the message requesting the creation (or updating) of the DAA context. In an alternative embodiment, the BSS 3 is designed in such a way that it extracts the address of the element providing the FUSW from the BFT of the transmitted DAA context.

In addition, SHUPS 3 can also receive information about the address of the element 4 that provides FUSW, in any other way.

In the case when a different network element is used to make a decision on access permission, for example, an element that provides FUS, then the address of this network element (for example, an element that provides FUS) can be transferred to STM 3 (via an access point) and to element 4 providing FUSW.

In addition, according to another possible feature of the invention, in the event that the above-described functionalities (request for permission and resolving answer) must also be provided to subscribers using roaming, then the information about the subscription to services contained in the subscriber database (for example , in the register of the source location, ROME (HLR)), add a new parameter that describes whether it is really necessary to obtain permission to activate (or modify) the DAA context from the element providing FU SV (or element providing FUS). This parameter may depend on the specific DAA context.

Returning now to FIG. 1, upon receipt of an authorization response, SCWS 3 sets the DAA context and, as necessary, additional information corresponding to the information contained in the authorization response, for example, an acceptable QoS value, etc. In addition, SCPS 3 returns to SCUP 2 a response about creating (or updating) the DAA context. In response to it, SHUPO 2 transmits to the subscriber equipment 1 a response about activation (or modification) of the DAA context. After that, the call is considered established and provide its service in a known manner.

In FIG. 2 shows another embodiment of the invention (method and / or system), which is equipped with a strategy management function (FCS). An element providing FUSW has an interface with an FCS, as well as with an element providing FUSW. An element providing FUS, can be used for communication between the network level of telephone communications via the Internet, that is, an intermediary element providing FUS, and the network level SPROP / USMS (SHUPS). For example, a call may affect the DAA context activated for that call.

In FIG. Figure 2 shows an example of a stream of transmissions and messages between the SPROP / USMS network layer, that is, STS, and the network level of telephone communication via the Internet, that is, an element providing FUSW, which is carried out through an element providing FUS. It is possible to limit the activation (or modification) of the DAA context at the network level of telephone communications via the Internet.

According to FIG. 2, permission to activate / modify the context of DAAs is issued based on the type of call. In the embodiment depicted in the drawing, the procedure for activating the DAA context in the case of a call originating from a mobile communication device, that is, a call originating from a mobile station (MS) 21 is shown, wherein the called subscriber is a network element 27 (user equipment, database and etc.). A request for permission to activate the DAA context is sent to element 25 providing the FUS. Only those parameters are shown and described below that are necessary for communication between the intermediary element (access module) 26, which provides FUSW, and the element, which provides FUS, 25, and for communication between ШУС 24 and the element, which provides ФУС, 25.

In the general case, according to the embodiment of the invention shown in FIG. 2, in the network level SPROP / USMS (that is, in ShUPS 24 communication systems of the third generation (3G)), in the network level of telephone communication via the Internet, for example, in element 26 providing FUSW, and in element 25 providing FUS, a common identifier by which the DAA context is displayed in a call. The presence of only a subscriber identifier, for example MIAMS, is insufficient when the MS 21 simultaneously supports multiple calls. In this case, according to FIG. 2, the common identifier used is the call identifier Call_ID (Call_Id), which already exists in the PISS messages. The device that initiated the call, which in this example is the mobile station 21, allocates the Call_ID (Call_Id) in a known manner, for example, from the PISS protocol, and this Call_ID identifier uniquely characterizes the call.

According to a preferred embodiment of the invention, such as that shown in FIG. 2, this common identifier, for example, Call_ID (Call_Id), is transmitted from the MS 21 to the GCS 23 and from the GCS 23 to the SCC 24. In addition, this common identifier is transmitted from the mobile station 21 to the intermediary element 26 providing the CGS, in the preferred embodiment it transmit in the message initiating the establishment of the call, for example in the message PISS "INVITATION". In addition, this common identifier is transmitted from the FUSW element 26, to the FUS, to the element 25, and, moreover, from the FCS 24 to the FUS element 25. Then, the element 25 providing the FUS, establishes the correspondence of the request transmitted from the FCS 24 with the permission transmitted from the element 26 providing the FUS, according to the common identifier (for example, by the identifier Call_ID (Call_Id)), and decides on the resolution of the call and / or about the connection parameters used, for example about KO.

In a modified embodiment of the invention, an identifier is used as a common identifier that is available at the network level of the SPROP / USMS, for example, in SCAS 24. For example, ITDS is used as such a common identifier. According to one embodiment of the invention, in this case, the transfer of ITDSS from the MS 21 to the FUSW element 26 is carried out in an “INVITATION” message or in another message when a call is established. In addition, ITDSS is transmitted from SCWS 24 to the FUSW element 25, and from the FUSW element 26 to the FUS element 25. In this case, the element 25, providing FUS, establishes the correspondence of the request transmitted from the STS 24 with the permission transmitted from the element 26, providing FUSV, ITDSS.

The operator can configure the system in such a way that it provides information about the access point to the control system by means of which they indicate whether it is necessary to establish communication with the element providing the CCF, and for what specific DAI context it is necessary, for example, it may be necessary only in in the case when the category of QoS means the presence of dialogue communication, that is, the transmission of speech data. The system configuration can also be set in such a way that it transmits the address of the FUSW element 25 to the Hub 24 and to the FUSW element 26, due to which the Hub 24 and the FUSW element 26 can communicate with one and the same the same element 25, providing FUS.

In an alternative embodiment of the invention, in which the address of the FUS providing element is not transmitted to each of the network elements, for example, to the elements 24 and 26, into the subscription information contained in the subscriber database, for example, in the home location register ( ROM) (HLR) and / or in the SPA (in the server of the movement of subscribers (UMS)), a new parameter can be included, for example, the address of the element providing the FUS. SHUPO 23 receives the address of the element 25 providing FUS, from a subscriber database, for example, from ROME, and transmits it to STEPS 24. After receiving the address of the element 25 providing FUS, STEPS 24 has information about which element 25 providing FUS , he should establish a connection. The element providing the FUSW receives from the SPA the same address of the element 25 providing the FUS and can establish communication with the same element 25 providing the FUS.

The presence of the need to establish communication with the element 25, providing FUS, or its absence may depend on the operator of the source network. For subscribers using roaming, a new parameter is added to the information on subscribing to services contained in the RIM and in the SPA of the subscriber database, describing whether it is necessary to establish communication with element 25 providing FUS, for example, information “Interaction with an element providing FUS " The information “Interaction with an element providing the FUS is required”, contained in the RIM, may relate to a specific option of subscribing to services or may relate to a specific context of DAAs. SHUPO 23 receives information “Interaction with an element providing FUS” is required from the RIM and transmits it to STOPS 24. After receiving information “It is necessary to interact with an element providing FUS”, STOPS 24 has information about the need to establish communication with an element providing FUS, or about the absence of this need when establishing a connection or changing a connection, or in similar operations. Element 26 providing FUSW receives information "Interaction with an element providing FUS" is required from the SPA and from it receives information about whether it is necessary to establish communication with element 25 providing FUSW or not.

Therefore, according to this feature of the invention, it proposes three new concepts, used optionally or in combination:

(a) create a common identifier to ensure consistency between the DAA context and the call;

(b) create a new parameter for RIM and SPA, namely the address of the element that provides the FUS; and / or

(c) in ROME and SPA create a new parameter "Interaction with an element providing FUS" is necessary.

The following illustrates and describes the interaction of a packet switched network (CP) network area with an element 25 providing a strategy control function (FCS) according to an embodiment of the invention, which is shown in FIG. 2. The following is a more detailed description of the operations performed during the establishment of the connection, with reference to the operation numbers shown in FIG. 2.

In step 1, the mobile station 21 transmits an “INVITATION” message to the intermediary element 26 providing FUSW, while the “INVITATION” message contains the Subscriber Identifier (Subscriber Id) identifier and the Call Identifier (Call_Id) identifier. The intermediary element 26, providing FUSW, transmits these messages to the called subscriber 27.

In step 2, the intermediary element 26 providing FUSW receives from the terminal of the called subscriber 27 an acknowledgment message, for example, message 183w / BDOPA (subscriber parameter service database (SDP)) provided in the PISS. The intermediary element 26, providing FUSW, transmits this confirmation to the mobile station 21 (to the caller).

In step 3, after receiving the acknowledgment message from the called subscriber 27, the intermediary element 26 providing the CSCF transmits a request for granting access right (containing the subscriber identifier, call identifier "Call_ID" (Call_Id), the agreed value of QoS , transport address of the called subscriber) to element 25, providing FUS. The subscriber identifier can be, for example, MIAMS, MNPSSKU or the IP address of the calling subscriber 21 (that is, the address of the DAA in the network level SPROP / USMS). In order to ensure that the call corresponds to the corresponding DAA context in the element 25 providing the FUS, the Call_Id used for this is necessary. The agreed value of the QoS contains the QoS parameters obtained for the call as a result of coordination. In the case of an urgent call, the intermediary element 26, providing FUSW, sets the highest value allocated / stored priority for the parameter Qo. The transport address of the called subscriber is used in the SPROP / USMS network layer to specify the BWP (traffic flow pattern) for the DAA context.

In step 4, the FUS element 25 can send a message confirming the receipt of the authorization request received in step 3 by returning the access authorization confirmation message (containing the subscriber identifier and Call_ID) to the intermediary element 26 providing the FUSW .

In step 5, the MS 21 issues a request to activate the DAA context (for example, the secondary DAA context) for calling by sending to the PLC 23 a message requesting the activation of the (DAA) DAA context (containing the DAA and the Call_ID).

In step 6, the procedure for establishing a unidirectional radio communication channel with subscribers is performed.

In step 7, SHUPO 24 transmits to SCPS 24 a message with a request to create a DAA context (containing the subscriber identifier, Call_ID and the agreed value of TO).

In step 8, SCWS 24 issues a request for permission to activate the DAA context by sending to the element 25 providing the FCS, messages with a request for permission (containing the request identifier, subscriber identifier, Call_ID and the agreed value of QoS). Receiving the first message with the request (during operation 8) leads to the creation in the element 25, which provides the FCM, of the status of the request.

When performing operation 9, the element 25, providing the FUS, sends a response to the control system 24 by sending a decision decision message (containing the request identifier, the agreed value of the TO and the transport address of the called subscriber). ШУС 24 sets the ШПТ for the DAA context according to the transport address of the called subscriber.

In step 10, the BSS 24 may send a notification that it has performed the actions in accordance with the decision made by transmitting to the element 25 providing the FUS a status notification message (containing the request identifier).

When performing operations 11 and 12 transmit messages about the activation of the DAA context in a known manner.

Referring to FIG. 2 messages 8 (request), 9 (decision made) and 10 (status notification) are messages of the COPS protocol (with a common open service strategy (OOSO)).

In FIG. Figure 2 shows an option for activating a DAA context. If it is necessary to modify the context, DAAs perform the same operations 8, 9 and 10, as well as further operations shown in FIG. 2.

The need to obtain permission to activate the DAA context from element 25 providing the FUS may depend on the particular system operator. To provide this function also for subscribers using roaming, a new parameter is introduced into the information about subscribing to services contained in the RIM, for example, "Interaction with an element providing FUS is required." The SHUPO receives information from ROME “It is necessary to interact with the element providing the FSF” and must transmit it to the SCPS 24 upon activation / modification of the DAA context. After receiving the information “It is necessary to interact with the element providing the FUS”, the SPS 24 has information on whether, when creating or changing the context of the DAA, it is necessary to establish a connection with the element 25 providing the FUS or not.

ШУС 3, 24, 33 (depicted in Fig. 3, Fig. 4 and Fig. 5) can obtain information about the address of the element 4 or 26 that provides FUSW (or SOV 34 from Fig. 3 of Fig. 4 and Fig. 5)

- by extracting the address of the intermediary element providing FUSW, from the domain name of the intermediary element providing FUSW (preferred option);

- from the new parameter "address of the element providing FUSW" transmitted to the PS in the activation message (secondary) context DAA;

- from SHPT when transferring the DAA context.

The parameters transmitted from the Hub for detecting the proper telephone call or connection in the element providing FUS (SOM; the element providing FUS is a logical element; it can be a stand-alone element or located in the element providing FUSW, or in the Hub) be:

IP address of the MS (= address SPD) and the port number of the MS (= the port number of the destination in the SHPT) (preferred);

peer IP address (= source address in the BNP) and peer port number (= source port number in the BWT).

In FIG. 3, FIG. 4 and FIG. 5 shows other embodiments of the present invention, in which a method and means for combining charging information generated by a core mobile communication network and a core TSPI network are provided. The basic mobile communication network is represented in the drawing by the elements of ШУПО 32 and ШУС 33. The remaining components necessary for creating a mobile communication network are known to a person skilled in the art and are not shown in the drawings. The TSPI core network is represented by a call processing server (SOC) 34. The remaining components of the TSPI network are known to those skilled in the art and are not shown in the drawings.

Shown in the drawings, embodiments of the invention provide the ability to charge for the level of QO used in telephone calls or other types of connections. For example, telephone calls require real-time traffic, and they typically require a higher QoS level than other types of communication, for example, to send e-mail messages (which can be sent using a lower QoS level and therefore, they are charged at a lower rate).

In the embodiments of the invention shown in the drawings of FIG. 3, FIG. 4 and FIG. 5, a method is proposed for combining call charging information and managing correspondence between the reserved QoS level in the TSPI network (for example, the one requested by the terminal device from which the call originates, for example, in the PISS "INVITATION" message) and the context QoS level DAA of the core mobile communication network with the transmission of packet data (when activating the DAA context), or ensuring their coincidence.

In FIG. 3, FIG. 4 and FIG. 5 shows the process of transmitting messages between a mobile communication terminal device (OUMS) 31 connected to a mobile communication network, ШУПО 32, ШУС 33 (ШУПО 32 and ШУС 33 form part of the mobile communication network to which ОУМС 31 is connected), and the call processing server 34 (OWL). OWL 34 contains an element providing a call state management (FUSW) function similar to that shown in the drawings of FIG. 1 and FIG. 2, therefore, the block 34 may also have the inscription "element providing FUSW."

The following is a more detailed description of the embodiment of the invention shown in FIG. 3.

In the case when, by means of the mobile communication terminal device 31, it is desired to establish a connection with another network element, for example, with the telecommunication equipment of the called party, the mobile communication terminal device 31 issues a call setup request, for example, transmits an “INVITATION” message according to the communication session initiation protocol ( PISS), which is reflected in the drawing as operation 1. The message "INVITATION", which contains the information elements "Call_ID" and "BDOPA: CO" ("SDP: QoS"), is transmitted from OUMS 31 to OWL 34. The abbreviation BDOPA stands for the database for servicing the parameters of subscribers. "Call_ID" is a generic identifier that is created to allow for combining or other appropriate use of the relationship of charging data, for example, DZO (billing information records (CDR)), which are generated by support nodes, for example, UPS (SPROP support nodes) (GSN), and an element providing FUSW (or SOV). The transmission of this common identifier, which is, for example, Call_ID, to the support nodes and to the element providing the FUSW (or to the SOC) is carried out at the stage of establishing a connection (for example, at the stage of establishing a call). By means of this method, unambiguous identification of the established connection or call can be provided in all relevant processing elements, for example, in Hubs and in the SOC, without the need for an interface directly between these components. This method and device provides a means of combining charging data and / or validating QoS in various types of networks, which, for example, provide a connection between all terminal devices via the Internet Protocol (IP), for example, by telephone over the Internet.

When performing the following operation 2, the mobile terminal 31 transmits a request for activation of the DAA context to the PLC 32, and this request contains not only ordinary information, for example, about the type of the unidirectional channel and the codec, but also an additional parameter "Call_ID". Then, this parameter "Call Identifier" and other necessary information elements that are known are transferred from the GCS 32 to the SCC 33, therefore, the SCC 33 also contains information about the common Call Call Identifier assigned to the connection being established. In the next operation 3, the control system 33 transmits the request for verification to the OWL 34, while the request for verification indicates the general identifier "Call_ID" and additional information, such as the type of unidirectional channel and codec.

In the next operation 4, COB 34 (or an element providing COBF contained in COB 34) verifies the connection being established, determined by the common identifier Call_ID, and checks the validity of the requested QoS parameters both in the telephone channel (PESS / BDOPA) and in unidirectional channel (DAA contexts). The element providing FUSW (COB 34), performs this check to verify the legitimacy of the requested QoS parameters before approving the call establishment (or continuing it), whereby it can charge for the QoS provided during a call or other type of connection, or it performs this verification for tasks other than charging. After this check (Call_ID, BDOPA: CO, type of unidirectional channel, codec) COB 34 gives a message about a positive test result (YES) or a negative test result (NO) and returns (operation 5) to the joint control system 33 in which the result is indicated checks (positive / negative). SCWS 33 uses the information obtained in step 5 to decide on the admissibility (if the test result is positive, "YES") or the inadmissibility (if the test result is negative, "NO") of activating the DAA context related to the call, and returns a response in SHUPO 32, whereby SHUPO 32 receives information about the admissibility or inadmissibility of activation (or modification) of the DAA context. After receiving a response on the admissibility or inadmissibility of activation, the SHUP 32 performs known operations and transmits the relevant information to the mobile terminal 31.

COB 34 (or an element providing FUSW), returning a response to the call setup request received in step 1, can also transmit the response directly to the mobile terminal 31 (step 6). For example, in step 6, the answer “YES / NO” (“OK / NOK”) can be transmitted using the PISS protocol.

Therefore, in order to make a decision on how to proceed with the establishment of the connection, an additional sequence of messages is exchanged between the element providing FUSW (or SOV), and Hub 33.

In addition to the "Call_ID", OWL 34 (or an element providing FUSW) can also receive additional parameters and make a decision taking into account these additional parameters as well.

The above-described flowchart shown in FIG. 3, is not limited only to those operations that relate to the approval of QoS and charging, but may also relate to the performance of other checks or evaluations. In addition, the decision made by OWL 34 (or by the element providing the FUSW) may also be advisory in nature and need not have only two possible "YES / NO" values.

As shown in FIG. 3, FIG. 4 and FIG. 5, ShUPS 33 is made in such a way that, when performing operation 3, it ensures the transfer of the request for verification to the SOV 34 (to the element providing the FUSW). Consequently, there is a need to transmit information about the address or name of the SOC (element providing the FUSW) to the firewall 33. In the event that the SHPS 33 does not have any information about the service element providing the FUSW (SOV 34), in which the mobile communication terminal device 31 is registered by the registration procedure according to the PESS protocol and to which the “INVITATION” message is transmitted, it is necessary to notify the SHPS 33 about the address or name of this serving element 34, providing FUSW (OWL). The embodiment of the invention shown in FIG. 4 provides a solution to this problem.

In addition to the above structure and functionality of the embodiment of FIG. 3, in the embodiment depicted in FIG. 4, in the request for activation of the DAA context, by means of which they provide notification to the FCS 33 about the address or name of the service element 34 providing the FUSW (or OWL), create a new parameter, for example, "Logical_name_O-FUSW" (logical name of the serving element providing the FUSW, " S-CSCF_logicalname "), due to which SCCS 33 receives information about where the request" for QoS verification "should be sent.

Based on the embodiment of the invention shown in FIG. 4, the above structure depicted in FIG. 3. The above description is also applicable to the sequences of transmitted messages and the operations performed, shown in FIG. four.

The mobile communication terminal device 31 contains information about the COB 34 (or about the element providing the FUSW) in which it is registered, and it is designed in such a way that it includes information about the address or name of the O-FUSW element (the serving element providing the FUSW, which is located in OWL 34) as part of the message sent during operation 2 to the control system 32 and then transmitted to the control system 33. This new parameter, by which the address or name of the service element providing the FSCW is indicated, is shown in FIG. 4 as the parameter "Logical_name_O-FUSW", the transfer of which is carried out in the request for activation of the DAA context. By obtaining this additional information, the "Logical_name_O-FUSW" SHUPS 33 now has information about the address or name of the corresponding element providing the FUSW (SOV), and transmits the request for verification (operation 3) to the SOV 34 (element providing the FUSW) specified through this parameter. Other operations shown in FIG. 4 are identical to the above operations of FIG. 3.

In addition, in FIG. 5 shows an additional optional parameter, which can be controlled by the end user of the mobile communication terminal device 31, and which allows the end user or the telephone equipment from which the call originates to send a request for a QoS check, for example, in the PISS: “INVITATION” message .

The embodiment of FIG. 5 contains all the features of the above embodiments of FIG. 3 and FIG. 4. According to FIG. 5, in addition, the structure of the connection establishment request transmitted during operation 1 from the mobile communication terminal device 31 to the COB 34 (to the element providing the CSCF) includes a new additional parameter, for example, “Require_ggsn_check”.

The circuit and method shown in FIG. 5 are in addition to the methods for combining billing and QoS data, which are described with reference to FIG. 3 and 4. The embodiment of FIG. 5 allows arbitrary selection of whether or not verification operations 3 through 5 should be performed. In the case when in the PISS "INVITATION" message (or in the message requesting to establish a connection of another appropriate type) transmitted from the mobile communication terminal device 31 in the COB 34, the parameter "Require_ggsn_check", COB (or contained in the COB an element providing FUSW) is ready to perform verification according to step 4 and is awaiting receipt of a message from SCPS 33 with a request to perform verification according to step 3. After receiving, at step 3, a request for verification, COB 34 performs a consent check about the above operation 4, after which the sequence of operations continues as described above. In the case when the parameter "Require_ggsn_check" is not specified or is absent in the request for establishing a connection transmitted during step 1, COB 34 (an element providing FUSW) does not check QoS according to step 4, and there is no need to obtain him from SCPS 33 any verification message. Through this information, due to the presence of the new parameter “Require_ggsn_check”, the element providing the CSCF receives information about the necessity or absence of the need to perform the verification procedure to continue the call setup process. The new query request parameter, of course, can have any arbitrary designation, for example, "Require_pdpqos _check", provided that it is understood by the element that provides the FUSW.

This new parameter created according to FIG. 5, and the ability to select an option to perform or not perform QoS checks or any other type of checks (step 4) can also be used in the circuit shown in FIG. 3, in which the logical name or address of the OWL 34 indicated in step 2 of FIG. 4. In particular, they can be used in the event that the Hub 33 receives information about the address of the SOV 34, in which the OUMS 31 is registered, in any other way, for example, by sending a message from the SOV 34 to the ShUPS 33.

The methods and tools proposed in the embodiments of the present invention can be implemented in the form of software contained in SCWS 3 and 33 and / or in the element 34 providing FUSW (in SOV), which allows for the appropriate execution of requests and checks, as well as processing the results of inspections and generating information on charging to create a statement of charging for established connections.

The proposed method and means of checking the parameters of the TO can also be implemented separately from the procedure for generating information on charging.

In addition, the demonstrated embodiments of the invention provide the ability to control and delay, for example, updating the DAA context, for DAA contexts allocated for voice telephone calls, until verification by OWL 34 is performed. This can be implemented by creating another messaging scheme between SCWS 33 and COB 34.

In FIG. 6 shows yet another embodiment of the invention (method and / or system), which is a modified embodiment of the embodiment of FIG. 2. According to FIG. 6, the FUS element providing 25 (see FIG. 2) is combined with the intermediary of the FUS component (see FIG. 2), and is one network element 25 ′. Such a structure provides the advantage that there is no need for any external signal transmission between the element providing the FUS and the element providing the FUS, therefore, steps 3 and 4 of FIG. 2 may be skipped. Authorization verification according to these operations 3 and 4 of FIG. 2 is performed using internal processing in the network element 25 ′ of FIG. 6. In this case, the operation of signal transmission between the element providing FUS, and the element providing FUSW, is simply an internal operation of signal transmission (that is, it is not strictly limited by any standard).

Further operations 1, 2 and 5th to 12th of FIG. 6 are identical to the above operations of FIG. 2.

Therefore, the element providing the FUS can be a separate logical entity 25 shown in FIG. 2 can be combined with an element providing FUSW, as shown in FIG. 6, or may also be combined with SCPS 24.

In FIG. 7 shows another embodiment of a system and method according to the present invention, in which it is possible to activate / modify the DAA context taking into account call characteristics. In FIG. 7 shows a process for activating an DAA context in the event of a call originating from a mobile communication device. It is believed that at least one DAA context is activated for a call. In the element providing the FUS, a request is issued for obtaining permission from it to activate the DAA context. Permission from the element providing the FUS is necessary to adjust the QoS of the DAA context so that it corresponds to the QoS of the call. ShUPS can determine whether it is really necessary to take into account the decision made by the element that provides the FCS, and for which specific DAAs. For example, in the configuration information, it may be indicated that the decision made by the element providing the FCS is necessary only for the dialogue DAA contexts, and for other contexts of the DAA, the activation of the DAA context should take place without interaction with the element providing the FCS. In the description below, only those parameters are shown and described that are necessary to ensure communication between the SCC and the element providing the CSC. The following is a detailed description of the operations shown in FIG. 7.

Operation 1. The PS transmits to the intermediary element providing FUSW, the message "Invitation" (subscriber identifier). The intermediary element providing FUSW, forwards this message to the called subscriber.

Operation 2. The intermediary element providing FUSW receives a confirmation message, for example, 183w / BDOPA. The FUSW intermediary element forwards this confirmation to the caller.

Operation 3. The PS activates the DAA context for the call by sending the request for activation of the DAA secondary context to the VLSI.

Operation 4. Perform the procedure for establishing a unidirectional channel of radio communication with subscribers.

Operation 5. The control system transmits a message with the request to create the DAA context (containing the address of the DAA and the agreed value of the TO) to the gateway.

Operation 6. The control system requests permission to activate the DAA context by transmitting a request message (containing the request identifier, subscriber identifier, and the agreed value of the TO) to the element providing the FUS. The subscriber identifier is an identifier that is known both in the field of a network with a CP and in the multimedia subsystem of the network based on the Internet protocol (IM), for example, the IP address of the MS.

Operation 7. The element that provides the FCS sends a response by sending a message about the decision made (containing the request identifier and the agreed QoS value) to the SCS.

Operations 8 and 9. Activate the DAA context with the approved parameters obtained from the element that provides the FCS.

Operation 10. SCWS can send a message stating that it has successfully completed the decision-making operation by transmitting to the element providing the FCS a status notification message (containing the request identifier).

When changing the context, DAAs perform the same operations 6, 7, and 10.

Although the preferred embodiments of the invention have been demonstrated and described above, the described and demonstrated details of the invention are not limiting, it is understood that the invention encompasses all modifications, omissions and additions of features that are described above and shown in the drawings.

For example, the invention is not limited only by the exchange of information between the Hub (3, 24) and the element that provides the FUS, the element that provides the FUSW (or a combination of the element that provides the FUSW, and the element that provides the FUS). The same exchange of information is possible when replacing the Hubs 3 and 24 with the Hubs 2 and 23, which leads to the fact that the information is exchanged as follows: Hubs - an element that provides FUS, - an element that provides FUSW (or a combination of an element that provides FUSW, and an element providing FUS).

Claims (98)

1. A method for establishing or modifying a connection for a first network element assigned to a user, which method is that a connection is established or modified for a call between the first network element and the second network element, the connection being established by the third network element, the third network element being located in network, while the first network element generates a request for activation or modification of the connection, and with the help of the third network element when receiving information on request The connection activation request is sent to the fourth network element, and in the request for permission, they request permission to establish the required type of connection, while at least one of the following is indicated in the request for permission: the first network the element, the second network element, the connection being established and the type of connection being established, and using the fourth network element, a response indicating allowed is returned to the third network element e connectionless or connection type, the control establishing or modifying the compound process is carried out depending on said response. 2. The method according to claim 1, characterized in that the third network element is a gateway network element and SCCS (gateway support node SPROP (packet radio communication system)). 3. The method according to claim 1, characterized in that the fourth network element is an element that provides a call state management function (FUSW). 4. The method according to claim 1, characterized in that the fourth network element is an element that provides a strategy management function (FUS). 5. The method according to claim 1, characterized in that the fourth network element is a call processing server (COW). 6. The method according to claim 1, characterized in that the fourth network element is at least partially implemented as part of a third network element. 7. The method according to claim 1, characterized in that the request for permission is a request by which they request permission to activate or modify the context of the packet data protocol (PDP) for the first network element. 8. The method according to claim 1, characterized in that the request for permission contains at least one of the following: MIAMS / MNPSTSKU (international identifier of a mobile subscriber / international number of a mobile station in a digital network with integrated services), address , the required quality of service (QoS) or the address of the second network element. 9. The method according to claim 1, characterized in that the response contains call characteristics, which are preferably acceptable values of quality of service (QoS), and / or acceptable information about the second network element and / or an indicator by which indicate whether this connection is regular call or urgent call. 10. The method according to claim 1, characterized in that when trying to establish a call using the first network element, addressing is made to the fifth network element, while using the fifth network element, an access authorization message is transmitted to the fourth network element, which indicates at least one call parameter. 11. The method according to claim 10, characterized in that the call parameter is at least one of the following: MIAMS, MNPSTSKU, IP address of the first network element, the agreed quality of service, transport address of the called subscriber. 12. The method according to claim 10, characterized in that using the fourth network element, an authorization confirmation message is transmitted to the fifth network element. 13. The method according to claim 9, characterized in that using the fourth network element, a response is generated that is transmitted to the third network element based on the content of the access authorization message. 14. The method according to claim 1, characterized in that the stored information about the subscription to services related to the first network element, contains a parameter that determines the need to transfer the request from the third to the fourth network element when establishing a connection between the first network element and the third network element. 15. The method according to 14, characterized in that the specified parameter is passed to the third network element in the process of establishing a connection between the first network element and the second network element, and with the help of the third network element, a decision is made on whether to transfer the request to the fourth network element, depending from the contents of this parameter. 16. The method according to p. 15, characterized in that in the case when the specified parameter indicates the absence of the need to transfer the request from the third network element to the fourth network element, do not transmit the specified request from the third network element and with it continue the connection establishment procedure between the first and third network elements. 17. The method according to claim 1, characterized in that they create a common identifier by which they identify the network element issuing a request to establish a connection with another network element, or provide call identification in a network based on the Internet Protocol (IP), so and in a network based on SPROP (general packet radio communication system) or USMS (universal mobile communication system). 18. The method according to claim 1, characterized in that a common identifier is created and used to ensure that the connection matches the call, and when a connection is established between the first and third network elements, it is transmitted to the third network element. 19. The method according to 17 or 18, characterized in that the common identifier contains at least one of the following: MIAMS / MNPSTSKU, IP address of the mobile station (MS), port number of the MS, peer IP address, peer port number. 20. The method according to claim 1, characterized in that the stored information about the subscription to services related to the first network element contains the address of the fourth network element, and when a connection is established between the first and third network elements, this address is transmitted to the third network element. 21. The method according to claim 1, characterized in that the address of the fourth network element is configured in the third network element and in the fifth network element. 22. The method according to claim 1, characterized in that the connection is made through a network based on SPROP / USMS (public packet radio system / universal mobile communication system) and a network based on the Internet Protocol (IP), and check and compare the values QO connections provided in both networks, whereby receive new information on charging. 23. The method according to claim 1, characterized in that when transmitting a call setup request, a request for verification is transmitted, by which a parameter related to charging is verified from the first network element to the fourth or other network element. 24. A method of establishing a connection for a first network element assigned to a user, the method being that the connection is established by the third network element, the third network element being in the network, the connection being established or modified for a call between the first and second network elements, wherein the first network the element generates a request for activation of the connection, and using the third network element, upon receipt of information on the request for activation of the connection, a request for execution of verification of the fourth network element, and in the request for verification, they request verification of the connection parameter, while in the request for verification, at least one of the following is indicated: the connection being established or the type of connection being established, and the fourth network element is used to verify returning a response indicating the result of the verification to the third network element, wherein the connection establishment process is controlled depending on the specified response. 25. The method according to p. 24, characterized in that the third network element is a gateway network element and STS (gateway support node SPROP (General Packet Radio Communication System)). 26. The method according to paragraph 24, wherein the fourth network element is an element that provides a call state management function (FUSW). 27. The method according to paragraph 24, wherein the fourth network element is an element that provides the function of strategy management (FUS). 28. The method according to paragraph 24, wherein the fourth network element is a call processing server (COW). 29. The method according to paragraph 24, wherein the fourth network element is at least partially implemented as part of a third network element. 30. The method according to paragraph 24, wherein the request for verification is a request by which to request verification of at least one connection parameter. 31. The method according to p. 24, characterized in that when trying to establish a call using the first network element, addressing is made to the fifth network element, while using the fifth network element, an authorization message is transmitted to the fourth network element, which indicates at least one call parameter. 32. The method according to p. 31, characterized in that the call parameter is at least one of the following: MIAMS, MNPSTSKU, IP address of the first network element, the agreed quality of service, transport address of the called subscriber. 33. The method according to p, characterized in that using the fourth network element transmit to the fifth network element a message confirming authorization of access. 34. The method according to p. 24, characterized in that they create a common identifier by which they identify the network element issuing a request to establish a connection with another network element, or provide call identification in a network based on the Internet Protocol (IP), so and in a network based on SPROP (general packet radio communication system) or USMS (universal mobile communication system). 35. The method according to paragraph 24, wherein the common identifier is created and used to match the call, and when a connection is established between the first and third network elements, it is transferred to the third network element. 36. The method according to any of paragraphs 34 or 35, characterized in that the common identifier contains at least one of the following: MIAMS / MNPSTSKU, IP address of the mobile station (MS), port number of the MS, peer IP address, peer number, peer port. 37. The method according to paragraph 24, wherein the stored information about the subscription to services related to the first network element contains the address of the fourth network element, and when a connection is established between the first and third network elements, this address is transmitted to the third network element. 38. The method according to paragraph 24, wherein the address of the fourth network element is configured in the third network element and in the fifth network element. 39. The method according to paragraph 24, wherein the statement of charge, through which charge for the connection is provided, is created taking into account the result of checking the connection parameter. 40. The method according to paragraph 24, wherein the connection parameter indicates the requested or acceptable QoS level and verifies the QoS information provided both during the transmission of service signals and user traffic, while the payroll statement is created taking into account the result this check. 41. The method according to p, characterized in that the QA check is carried out in response to a request for verification. 42. The method according to paragraph 24, wherein the connection parameter indicates the characteristics of the call, which are preferably acceptable QoS values, and / or information about the second network element and / or a pointer through which indicate whether this connection is a normal call or urgent call. 43. The method according to paragraph 24, wherein the connection is through a network based on SPROP / USMS (public packet radio system / universal mobile communication system) and a network based on the Internet Protocol (IP), and check and compare the values QO connections provided in both networks, whereby receive new information on charging. 44. The method according to p. 24, characterized in that when transmitting a call setup request, a request for verification is transmitted, by which a parameter related to charging is verified from the first network element to the fourth or other network element. 45. A system for establishing or modifying a connection for a first network element assigned to a user, the connection being established or modified for a call between the first network element and the second network element, comprising a third network element located on the network through which the connection is established, the first network the element generates a request for activation or modification of the connection, and the fourth network element, and the third network element is configured to provide in the fourth network element of the request for permission when receiving information on the request for activation or modification of the connection, and the request for permission requests permission to establish the desired type of connection, while the request for permission indicates at least one of the following: the first network element, the second network element, the established connection and the type of established connection, and the fourth network element returns a response indicating the third network element indicating Allowing connection establishment or connection type, the control process of establishing or modifying compound is made depending on said response. 46. The system according to item 45, wherein the third network element is a gateway network element and SCWS (gateway support node SPROP (General Packet Radio Communication System)). 47. The system according to item 45, wherein the fourth network element is an element that provides a call state management function (FUSW). 48. The system according to item 45, wherein the fourth network element is an element that provides the function of strategy management (FUS). 49. The system according to item 45, wherein the fourth network element is a call processing server (SOV). 50. The system of claim 45, wherein the fourth network element is at least partially implemented as part of a third network element. 51. The system according to item 45, wherein the request for permission is a request by which they request permission to activate or modify the context of the packet data Protocol (PDP) for the first network element. 52. The system according to item 45, wherein the request for permission contains at least one of the following: MIAMS / MNPSTSKU (international identifier of the mobile subscriber / international number of the mobile station in a digital network with integrated services), address DAA , the required quality of service (QoS) or the address of the second network element. 53. The system according to item 45, wherein the response contains call characteristics, which are preferably acceptable values of quality of service (QoS), and / or acceptable information about the second network element and / or a pointer indicating whether this connection is a normal call or urgent call. 54. The system according to item 45, wherein the first network element is configured to address the fifth network element when trying to establish a call, while the fifth network element is configured to transmit an authorization message to the fourth network element, in which at least one call parameter is specified. 55. The system according to item 54, wherein the call parameter is at least one of the following: MIAMS, MNPSTSKU, IP address of the first network element, the agreed quality of service, the transport address of the called subscriber. 56. The system according to item 54, wherein the fourth network element is configured to provide transmission of access authorization confirmation messages to the fifth network element. 57. The system of claim 53, wherein the fourth network element is configured to create a response transmitted to the third network element based on the content of the access authorization message. 58. The system according to item 45, wherein the stored information about the subscription to services related to the first network element, contains a parameter that determines the need to transmit a request from the third to the fourth network element when establishing a connection between the first network element and the third network element. 59. The system of claim 58, wherein said parameter is transmitted to the third network element in the process of establishing a connection between the first network element and the second network element, and the third network element is configured to decide whether to transfer the request to the fourth network element in depending on the contents of this parameter. 60. The system according to § 59, characterized in that when the specified parameter indicates that there is no need to transfer the request from the third network element to the fourth network element, the third network element does not transmit the specified request and continues the process of establishing a connection between the first and third network elements. 61. The system according to item 45, characterized in that it creates a common identifier by which they provide identification of a network element issuing a request to establish a connection with another network element, or provide call identification in a network based on the Internet Protocol (IP) and in a network based on SPROP (general packet radio communication system) or USMS (universal mobile communication system). 62. The system according to item 45, wherein the common identifier is created and used to ensure the connection of the call, and when a connection is established between the first and third network elements, it is transmitted to the third network element. 63. The system according to any one of claims 61 or 62, wherein the common identifier contains at least one of the following: MIAMS / MNPSTSKU, IP address of the mobile station (MS), port number of the MS, peer IP address, peer number port. 64. The system according to item 45, wherein the stored information about the subscription to services related to the first network element contains the address of the fourth network element, and when a connection is established between the first and third network elements, this address is transmitted to the third network element. 65. The system according to item 45, wherein the address of the fourth network element is configured in the third network element and in the fifth network element. 66. The system according to item 45, characterized in that it provides a connection through a network based on SPROP / USMS (public packet radio system / universal mobile communication system) and a network based on the Internet Protocol (IP), and provides verification and comparison of values QO connections provided in both networks to receive new information on charging. 67. The system according to item 45, characterized in that when transmitting a request for establishing a call transmits a request for verification, through which provide verification of the parameter associated with charging, from the first network element to the fourth or other network element. 68. A system for establishing a connection for a first network element assigned to a user, comprising a third network element located in a network by which a connection is established, the connection being established or modified for a call between the first network element and the second network element, wherein the first network element generates a connection activation request, and a fourth network element, wherein the third network element is configured to transmit a request to the fourth network element and to verify when receiving information on the request to activate the connection, and the request to perform the verification requests a verification of the connection parameter, while the request for verification indicates at least one of the following: the connection being established or the type of connection being established, and the fourth network element performs a check and returns a response indicating the result of the check to the third network element, and the connection establishment process is controlled depending on the specified response. 69. The system according to p, characterized in that the third network element is a gateway network element and Hubs (gateway support node SPROP (packet radio communication system)). 70. The system of claim 68, wherein the fourth network element is an element providing a call state management (FUSW) function. 71. The system according to p, characterized in that the fourth network element is an element that provides the function of strategy management (FUS). 72. The system of claim 68, wherein the fourth network element is a call processing server (SOC). 73. The system of claim 68, wherein the fourth network element is at least partially implemented as part of a third network element. 74. The system of claim 68, wherein the verification request is a request by which verification of at least one connection parameter is requested. 75. The system according to p, characterized in that the first network element is configured to address the fifth network element when trying to establish a call, while the fifth network element is configured to transmit to the fourth network element access authorization message, in which at least one call parameter is specified. 76. The system of claim 75, wherein the call parameter is at least one of the following: MIAMS, MNPSSKU, IP address of the first network element, consistent quality of service, transport address of the called subscriber. 77. The system of claim 75, wherein the fourth network element is configured to provide an access authorization confirmation message to the fifth network element. 78. The system according to p, characterized in that it creates a common identifier by which they provide identification of a network element issuing a request to establish a connection with another network element, or provide call identification in a network based on the Internet Protocol (IP) and in a network based on SPROP (general packet radio communication system) or USMS (universal mobile communication system). 79. The system of claim 68, wherein the common identifier is created and used to ensure that the connection matches the call, and when a connection is established between the first and third network elements, it is transmitted to the third network element. 80. The system according to any one of claims 78 or 79, characterized in that the common identifier contains at least one of the following: MIAMS / MNPSTSKU, IP address of the mobile station (MS), port number of the MS, peer IP address, peer number port. 81. The system of claim 68, wherein the stored service subscription information related to the first network element contains the address of the fourth network element, and when a connection is established between the first and third network elements, this address is transmitted to the third network element. 82. The system of claim 68, wherein the address of the fourth network element is configured into a third network element and into a fifth network element. 83. The system according to p, characterized in that the statement of charging, through which they provide charging for the connection, is created taking into account the result of checking the connection parameter. 84. The system of claim 68, wherein the connection parameter indicates the requested or acceptable QoS level, and at the same time they provide verification of the QoS information provided both during the transmission of service signals and user traffic, while the payroll statement is created from considering the result of this check. 85. The system of claim 84, wherein the QoS check is carried out in response to a request to perform a check. 86. The system of claim 68, wherein the connection parameter indicates call characteristics, which are preferably acceptable QoS values, and / or information about the second network element and / or a pointer indicating whether the connection is a regular call or an urgent call. 87. The system according to p. 68, characterized in that it provides a connection through a network based on SPROP / USMS (public packet radio system / universal mobile communication system) and a network based on the Internet Protocol (IP), and provides verification and comparison of values QO connections provided in both networks to receive new information on charging. 88. The system according to p, characterized in that when transmitting a call setup request, it transmits a check request, by which a parameter related to charging is verified from the first network element to the fourth or other network element. 89. The method of establishing a connection in a two-level communication network containing a first level of a communication network, designed to establish a communication channel with a terminal device, and a second level of a communication network, designed to establish a communication session on a specified communication channel, which consists in establishing a communication channel by identifier, establish a communication session through the specified identifier, provide authorized access to the specified communication channel through the specified communication session using indicated identifier. 90. The method according to p. 89, characterized in that when providing authorized access when establishing a communication channel using a network element located in the first level of the communication network (for example, SCPS (gateway support node SPROP (packet radio communication system))), initiate the transmission of a request for authorization of access, using the network element located in the second level of the communication network (for example, an element providing a call state management function (FUSW)), perform the specified authorization of access. 91. The method according to any one of claims 89 or 90, characterized in that the first level of the communication network is the network level SPROP / USMS (public packet radio communication system / universal mobile communication system), and the second level of the communication network is a multimedia network subsystem based on Internet Protocol (IP). 92. The method according to any one of p or 90, characterized in that the terminal device is a subscriber equipment or a mobile station. 93. A system for establishing a connection in a two-level communication network comprising a first level of a communication network for establishing a communication channel with a terminal device and a second level of a communication network for establishing a communication session on a specified communication channel, the system being configured to enable a communication channel by means of an identifier, ensuring the establishment of a communication session by means of a specified identifier, providing authorized access to a specified communication channel and by means of said communication session using said identifier. 94. The system of claim 93, wherein, to provide authorized access, a network element located in a first level of a communication network is configured to initiate a request for authorization of access when establishing a communication channel, a network element located in a second level of a communication network, configured to perform said access authorization. 95. The system according to any one of paragraphs 93 or 94, characterized in that the first level of the communication network is the network level SPROP / USMS (public packet radio system / universal mobile communication system), and the second level of the communication network is a multimedia network subsystem based on Internet Protocol (IP). 96. The system according to any one of paragraphs 93 or 94, characterized in that the terminal device is a subscriber equipment or mobile station. 97. A method for making a request for permission when establishing or modifying a connection between a first network element assigned to a user and a third network element, the connection being established or modified for a call between the first network element and the second network element, the connection is established by the third network element located in one of the networks, which consists in transmitting a permission request through a third network element to a fourth network element When receiving information on the request for activation or modification of the connection, moreover, in the request for permission they request obtaining permission to establish the required type of connection, while at least one of the following is indicated in the request for permission: the first network element, the second network element , the connection being established and the type of connection being established, and receiving, by the third network element, a returned response from the fourth network element indicating permission is established e compound or type of compound, and thus control the establishment or modification of a compound based on a specified response. 98. A method of requesting permission to establish or modify a connection for a first network element assigned to a user, the connection being established or modified for a call between the first network element and the second network element, the connection being established by a third network element located in the network, consisting in the fact that they accept through the fourth network element a request for permission, and in the request for permission, request Obtaining permission to establish the desired type of connection, wherein at least one of the following is indicated in the request for permission: the first network element, the second network element, the connection being established and the type of connection being established, and transmitted from the fourth network element to the third network element a response indicating permission to establish a connection or type of connection, and thus control the establishment or modification of the connection depending on the specified response.

Images