RU2257674C2 - System and method for multimedia broadcast and multi-address service in mobile communication network - Google Patents

Abstract

FIELD: mobile communications.

SUBSTANCE: invention concerns mobile communication with multi-station access with code channel separation containing multiple radio network controllers, multiple service nodes for GPRS support, connected to each radio network controller and multiple user equipment, made with possible connection to radio network controller via radio means. Maintenance nodes for GPRS support control procedure, related to multimedia broadcast/ multi-address service, for groups of user equipment stations, requesting current service. GPRS nodes by default are marked for each next service of multimedia broadcast/multi-address service. By default GPRS node through radio network controllers sends multimedia/multi-address data for current service to user station groups, which requested current service.

EFFECT: higher efficiency.

4 cl, 19 dwg

Description

The present invention generally relates to a device and method for creating a channel for multimedia broadcasting / multicast services in a mobile communication system, in particular to a device and method for creating a channel in response to a request for multimedia broadcasting / multicast.

In connection with the development of the communications industry, currently the services provided by the code division multiple access mobile access system (hereinafter referred to as CDMA) are evolving into multicast multimedia communication, which transmits voice service data and such high-capacity data as packet data and channel data. To provide multicast multimedia communication, broadcast / multicast service is required, in which one data source provides services for the equipment of many users (hereinafter referred to as UB). Broadcast / multicast service can be divided into cellular broadcast service (hereinafter CBO), which is a message service, and multimedia broadcast / multicast service (hereinafter referred to as MVMO), which provides multimedia data such as image and speech, in real time, still image and text.

NWO is a service for broadcasting multiple messages on all UBFs located in a given service area. This service area in which the CBO is provided may be the entire zone in which the CBO is provided in one cell. MVMO is a service that simultaneously provides voice and image data, and it requires a large number of transmission resources. MVMOs are provided over the broadcast channel, since at the same time in the same cell it is possible to provide many types of services.

As indicated above, in a conventional mobile communication system, where the same request for MVMO is received from multiple POs that are controlled by the same cell, or the same radio network controller (hereinafter KRS): channels or data transmission channels of MVMO in this system must be assigned separately when responding to each request from the software.

Therefore, a conventional mobile communication system requires some signaling procedure to provide the same MVMO service for many Pobs. But if a certain number of channels (or MVMO data transmission channels) are assigned to provide the same MVMO service to different UEs, then an unnecessary waste of resources may occur and the signaling procedure may become complicated.

Therefore, the objective of the present invention is to provide a device and method for efficiently allocating resources to multiple POs that request the same MVMO service in a mobile communication system.

Another objective of the present invention is to provide a device and method for assigning a minimum number of data transmission channels in a PoE that request the same MVMO service in a mobile communication system.

Another objective of the present invention is to provide a device and method for simplifying the signaling procedure for channel assignment by controlling the channels in accordance with the UEs that receive specific MVMO service.

Another objective of this invention is to provide a device and method for managing the information generated by one cattle for a specific service MVMO.

Another objective of this invention is to provide a device and method for managing the information generated by one cattle in connection with a specific service MVMO using one AUPR (Administrative Node Serving ODA (General Packet Radio Service)).

According to a first aspect of the present invention: they provide a device for providing MVMO services. Multimedia Broadcasting / Multicast Services for groups of Pob (User Equipment) requesting MVMO services in a code division multiple access (CDMA) mobile communication system, which includes many radio network controllers ( KRS), a lot of AUPR (Administrative Node, Serving ODA (General Packet Radio Service)) connected to each of the KRS, and many POB, connecting Mykh to the RNC using radio MVMO and providing service to the UE. In the device: FOBs request the necessary MVMO service and receive the MVMO service when they respond to the request. The RNCs transmit data related to the MVMO service to the PoB connected to these controllers from among the PoB that requested this service. AUPR manages the procedure related to the maintenance of the MVMO for FOBs requesting this service. AUPR by default is separately designated for the maintenance of IMMO; and AUPR, by default, transmits AUPR data for MVMO service to the PoS, which requested MVMO service, through cattle controllers.

In accordance with a second aspect of the present invention: provide a method for defining AUPR (Administrative Node Serving ODA (General Packet Radio Service)) by default for providing MVMO (Multimedia Broadcasting / Multicast Service) service for UBs requesting MVMO service in a code-based mobile communication system channel separation (CDMA), having a first group that includes many radio network controllers (RNC), a second group that includes many AUPR connected to each of the RNC the first group and a plurality of groups of the UE connected to the RNC via radio. According to this method: accept, through one of the cattle, a service request for this service IMMO; if the default AUPR information corresponding to the MVMO service is not remembered in the one who received the request for cattle service, then the one who received the request for cattle service selects one of the AUPR as the default AUPR; inform, with the help of the selected AUPR by default, to all other cattle, with the exception of the one who received the request for cattle service, that the AUPR is controlled by MVO by default.

According to a third aspect of the present invention: they provide a method for defining AUPR (Administrative Node Serving ODA (General Packet Radio Service)) by default to provide MVMO (Multimedia Broadcasting / Multicast Service) services for user equipment groups (Pobs) requesting MVMO service in a mobile system communication with code division multiplexing (CDMA), having the first group, which includes many radio network controllers (RNC), the second group, which includes many AUPR, This turns with each of the RNC in the first group and a plurality of UE connected to the RNC via radio. According to this method: accept, through one of the AUPR, a service request for a given MVMO service; if the default AUPR information corresponding to the MVMO service is not stored in the receiver of the service request for cattle, then the accepted AUPR service selects itself as the default AUPR; and inform, using the selected AUPR by default, by another AUPR that the default AUPR manages the MVMO service.

In accordance with the fourth feature of this invention: provide service MVMO (Multimedia Broadcasting / Multicast Service) for one AUPR (Administrative Node Serving ODA (General Packet Radio Service)) from among the many AUPR in a mobile communication system with code division multiplexing (CDMA), containing a plurality of radio network controllers (RNC), a plurality of AUPRs connected to each of the RNCs, and a plurality of POBs connected to the RNC controllers by radio; and provide an IMMO service for VOB. According to this method: using the cattle that received a service request for MVMO service from among the cattle controllers: designate one of the AUPR as the default AUPR, taking into account the load of each of the AUPR; transmitting an identifier for identifying an MVMO service and an identifier for identifying a default AUPR for a given AUPR by default; and determine, by default AUPR, whether this MVMO service is available; and transmitting an identifier for identifying the MVMO service and an identifier for identifying the default AUPR to all other RNCs, with the exception of the RNC, which accepted the service request for this MVMO service.

Brief Description of the Drawings

The above and other objectives, features and advantages of this invention will become more apparent from the following detailed description in conjunction with the accompanying drawings, in which:

FIG. 1 schematically illustrates a CDMA mobile communication system for serving an IMMO according to an embodiment of the present invention;

FIG. 2 is a flowchart illustrating a procedure for creating a transmission channel in accordance with the MVMO service; FIG.

FIG. 3 is a flowchart of a signaling procedure for designating a transmission channel according to an ongoing MVMO service; FIG.

FIG. 4 is a flowchart of a signaling procedure for assigning a transmission channel according to an IMMO service scheduled for subsequent implementation; FIG.

5 is a diagrammatic illustration of the structure of a mobile communication system according to the structure of lu-Flex, for which it is advisable to use the present invention;

6 is a block diagram schematically illustrating an exemplary method of assigning a transmission channel that can be proposed in a lu-Flex mobile communication system according to one embodiment of the present invention;

Fig. 7 is a flowchart illustrating a signaling procedure for assigning a transmission channel in an initial MVMO service in a lu-Flex mobile communication system according to one embodiment of the present invention;

Fig. 8 is a flowchart illustrating a signaling procedure for assigning a new transmission channel in an MVMO service in a lu-Flex mobile communication system according to one embodiment of the present invention;

FIG. 9 is a flowchart illustrating a signaling procedure for assigning a new transmission channel in an MVMO service in a lu-Flex mobile communication system according to one embodiment of the present invention; FIG.

Fig. 10 is a flowchart illustrating a signaling procedure for informing a desired UE about the start of an MVMO service scheduled for subsequent provision in a lu-Flex mobile communication system according to one embodiment of the present invention;

11 is a block diagram illustrating a signaling procedure performed when the UE selects an MVMO service in a lu-Flex mobile communication system according to one embodiment of the present invention;

12 is a flowchart illustrating a signaling procedure for completing an ongoing MVMO service in a lu-Flex mobile communication system according to one embodiment of the present invention;

13 is a flowchart illustrating a signaling procedure for assigning a transmission channel in an initial MVMO service in a lu-Flex mobile communication system according to another embodiment of the present invention;

Fig. 14 is a flowchart illustrating a signaling procedure for assigning a new transmission channel in an MVMO service in a lu-Flex mobile communication system according to another embodiment of the present invention;

FIG. 15 is a flowchart illustrating a signaling procedure for designating a new transmission channel in an MVMO service in a combined mobile communication system according to yet another embodiment of the present invention; FIG.

FIG. 16 is a flowchart illustrating a signaling procedure performed when an PSE selects an MVMO service in a mobile communication system according to another embodiment of the present invention; FIG.

FIG. 17 is a flowchart illustrating a signaling procedure for completing a currently provided MVMO service in a lu-Flex mobile communication system according to another embodiment of the present invention; FIG.

Fig. 18 is a flowchart illustrating a signaling procedure according to which an unavailable level (NU) message is used to designate a transmission channel in an MVMO service in a lu-Flex mobile communication system according to one embodiment of the present invention; and

FIG. 19 is a flowchart illustrating a signaling procedure for creating and releasing a data channel before completing the MVMO service after the MVMO data transmission has actually been started in the lu-Flex mobile communication system according to embodiments of the present invention.

The following is a detailed summary of several preferred embodiments of the present invention with reference to the accompanying drawings. In the drawings, similar elements are denoted by the same reference numerals despite the fact that they are illustrated in different drawings. A detailed description of the known functions and configurations included in this invention is not provided — for brevity.

First, the following is a definition of terms used in implementations of the present invention. The term “IMMO data” means data for IMMO services provided by the service provider for the UE; and the term “AUPR” refers to a specific AUPR that manages the information of a particular MVMO service, among the AUPR assigned to the same group.

Figure 1 illustrates the basic structure of a mobile communication system in relation to which implementations of the present invention are applied. Figure 1 illustrates the basic elements for providing MVMO services and illustrates their relationship in a mobile communication system.

Turning to FIG. 1: VOB 101 is a subscriber unit configured to receive MVMO data provided for MVMO service. NSRUS (Terrestrial Radio Access Network of the Universal System of Mobile Telecommunications) 102 is a device for transmitting MVMO service data to POB 101 and includes a RNC (Radio Network Controller) and a Node B (not shown). AUPR (Administrative Node Serving ODA (General Packet Radio Service)) 103 manages the MVMO service procedure of each PoE. Typically, AUPR 103 manages the credentials of each FSA and selectively transmits MVMO data to a specific NRS. AUMPRO (Administrative Node of the Internet Packet Radio Service) 104 selectively transmits the MVMO data of the PS (content provider) 106 received from the SPR-SK (Main Resource Viewing Service Channel) 105 to a specific AUPR and maintains all the credentials of all the receivers that received the data MVMO. SPR-SK 105 presents an MVMO data source and conducts planning for MVMO data. SPR-SK 105 also verifies the authenticity of the IMMO data provider to provide the IMMO service for UE. The cell’s broadcast center (hereinafter referred to as the UTCJ) 107 informs the UB about the menu related to the current IMMO or information about the IMMO service scheduled for subsequent servicing. The MVMO service provided subsequently refers to the MVMO service that cannot be provided at this time because it is not possible to assign the service or resources provided in this mobile communication system, but which can be provided later when resources can be assigned. The Subscriber Register (hereinafter RA) 108 stores the confidential data of the registered Pobs and identifies the Pobs requesting communication services, or the Pobs requesting MVMO data.

FIG. 2 is a flowchart illustrating a procedure for assigning channels to each UE to receive MVMO services from a mobile communication system. That is, FIG. 2 illustrates the procedure for powering the POB in a given cell and then creating a channel for receiving MVMO data based on the functions of the elements illustrated in FIG. 1 and their relationships. According to Figure 2: the procedure for creating a channel for transmitting MVMO data is divided into two procedures according to the characteristics of the MVMO service selected by the UE data. As used herein, the term “MVMO service characteristic” refers to the current MVMO service or the MVMO service provided later.

First, a description is given of the procedure for receiving a parameter in the UE for receiving MVMO data for the selected MVMO service when the MVMO service selected by the equipment is currently provided by the mobile communication system. FIG. 3 illustrates a signaling procedure for receiving MVO data currently provided by a mobile communication system in the PoE 101. Here, the MVMO data reception parameter may comprise information related to the physical channel and information related to the transport channel. If the corresponding MVMO service is encrypted before transmission, then this parameter may also contain the information needed to decrypt the MVMO data.

Turning to FIGS. 2 and 3: if the power of the PS 101 is turned on at step 201, the PS 101 performs registration (initial registration) in a specific cell at step 202. To register in a specific cell: PS 101 can use the existing registration procedure. That is, POB 101 establishes a connection to the URR (Radio Resource Management) with the NRUS 102 and then transmits its own MIMA (International Mobile Subscriber Identifier) value to the AUPR 103 using the NU (Unavailable Level) message. AUPR 103 then asks the RA 108 to check whether the software is previously registered, which performs the initial registration.

At step 203: POB 101 obtains information about the type of MVMO service currently being presented in the cell, or which is scheduled for subsequent provision. At this point, the UTCJ 107 can be used to broadcast information related to the maintenance of the MVMO. An example of a signaling procedure for broadcasting information related to the MVMO service using the UHSC 107 may be steps 302 and 303 of FIG. 3. At step 204, UE 101 selects the desired MVMO service based on the received information related to the MVMO service. In addition, Software 101 determines whether the selected service is currently available or if it is planned for subsequent provision. If the selected MVMO service is currently being provided, then PoE 101 may receive the desired MVMO data in steps 211–213. At step 211: POB 101 provides information to the NRUS 102 about the type of MVMO service it needs and the information needed for authentication. The NRCS 102 then determines whether it can provide the MVMO service selected by the PoS 101 equipment based on information received from the PoS 101. The elements involved at this stage and an example of the signal transmission procedure between them are presented at steps 304 and 305 - FIG. 3. At step 304: POB 101 transmits the identifier of the selected MVMO service and its own special identifier (eg, MIMA) to AUPR 103. AUPR 103 then, at step 305, inquires from RA 108 about the possibility of verifying the authenticity of the Pob 101 and receiving the selected MVMO service. At step 212: The POB determines the success of authentication. If VOB 101 has the right to receive the selected MVMO service, then it proceeds to step 213. NRUS 102 then transmits information to VB 101 for transmitting the selected MVMO data. In this case, an example of the expected signal transmission procedure between the NRUS 102 and the UE 101 is represented by steps 306, 307, 308, 309 and 310 - FIG. 3. If the AUPR 103 informs the NRUS 102 that the authentication of the PoS 101 was successfully completed at step 306, then the NSA 102 provides for the PoP 101 the information needed to receive the selected MVMO data, at step 307. After the channel has been successfully created based on the information necessary to receive the selected IMMO data, PoB 101 reports the final information to the NRUS 102 at step 308. At step 309: the NRUS 102 again transmits the final information to AUPR 103. At step 310: AUPR 103 informs AUMPRO 104 that a certain OP has started receiving the corresponding MVMO data. Step 310 is designed to transmit the basic credentials corresponding to the reception of the MVMO service, and its description, as a description of the accounting system, can be omitted. For example, if the credentials of the APP are controlled by AUPR 103, then step 310 may be skipped. Or, step 310 may be performed upon completion of service. But if the request for MVMO service is not fulfilled for the reason that PoB 101 cannot accept the selected MVMO data, then the NRUS 102 may refuse to provide the selected MVMO service.

The following is a description of the procedure for creating a channel for MVMO service, when the MVMO service selected with the UE is scheduled for subsequent provision. The elements related to MVMO and the expected signal transmission procedure between them are illustrated in FIG. 4.

Turning to FIGS. 2 and 4: if the VOB 101 determines in step 204 that the MVMO data selected by the VB 101 itself will be provided later, the method proceeds to step 205. At step 205: the VOB 101 may pre-register the receipt of the corresponding service. In this case, the expected signal transmission procedure can be represented by steps 404, 405 and 406 of FIG. 4. At step 404: POB 101 transmits the identifier of the selected MVMO service and its own Pob identifier in AUPR 103. The PID identifier may contain MIMA, PVIMS (Packet-Temporary Naming of the Mobile Station) or RSVI (Radio Network Temporary Naming). PVIMS is the identifier of a PoB that has been assigned by a packet-switched network or AUPR node; RSVI is the identifier of the FSN assigned by the channel network, or UKSPO. The AUPR 103 then, at step 405, inquires with the RA 108 about the possibility of receiving the selected MVMO data by the appropriate SOP 101. If the SOP 101 can receive the selected MVMO data, then the AUPR 103 reports to the UB that the registration of the service in step 406 was successful. In this case, AUPR 103 may designate a WIGG (Temporary Naming of a Multicast Group), an UI identifier designated as a general identifier for a selected MVMO service. At step 407: AUPR 103 informs for AUMPRO 104 that a request for MVMO service has been received, selected in NRUS 102, which is controlled by AUPR 103. AUMPRO 104 again transmits the information provided from AUPR 103 to SPR-SK 105. At the specified In this step, you can create a channel for the corresponding MVMO service between the SPR-SK (MVMO source) 105 and AUPR 103.

At step 206: FOB 101 may be previously notified by the appropriate elements that the selected MVMO data will be provided soon. The time period when information should have been provided by the elements before the actual presentation of the IMMO data can be determined in various ways. For example, a signaling procedure that can be used in step 206 is represented by step 408 - FIG. 4. At step 408: SPR-SK 105 determines the provision of the selected MVMO data through planning and then announces the result to the appropriate AUPR 103. AUPR 103 then announces the result to the relevant VOB groups via the NRS 102. As a way of announcing the relevant VBMs to start the corresponding MVMO service, you can use the search call procedure in force in the existing asynchronous CDMA mobile communication system.

Upon learning about the start of the selected MVMO service at step 206, PoE 101 confirms the receipt of the relevant MVMO data at step 207. The reason for this is that even the FSU that previously requested the MVMO service may not receive MVMO data - due to circumstances. The NRUS 102 may re-identify the VOB 101, which has requested the receipt of the corresponding MVMO data. This corresponds to steps 409 and 410 of FIG. 4. At step 409: POB 101 may transmit its own special identifier: identifier WIMG or MVMO.

At step 208: POB 101 determines the success of the identification of POB. If it is determined that the identification of the UE has been successful, then the UE 101 performs the channel creation procedure for providing MVMO service between the NRUS 102 and the UB 101 and between the NRUS 102 and the AUPR 103 at step 209. Steps 411, 412, 413 and 414 in FIG. 4 illustrate an example of creating the corresponding channels using the procedure previously defined in the existing asynchronous CDMA mobile communication system.

At step 415: AUPR 103 informs AUMPRO 104 that the corresponding FOB 101 receives the IMMO data. Since step 415, similar to step 310 of FIG. 3, is intended to transmit basic credentials corresponding to receiving an IMMO service, therefore, it can be skipped according to the accounting system. Or step 415 can be performed after the end of the service.

The present invention is set forth above on the assumption that a mobile communication system contains one NRUS and one AUPR. But the present invention is also applicable to a mobile communication system comprising a plurality of NRUS and AUPR. In the description that follows, reference is made to a method of creating a transmission channel for serving MVMO in a mobile communication system comprising a plurality of NRUS and AUPR. Further, in the description below, a lu-Flex structure is introduced in order to subdivide a plurality of DRS (Radio Access Networks) into a predetermined number of groups and define groups using the terms “combined CS domain” and “combined PS domain”.

Figure 5 illustrates the relationship between cattle and fixed network using lu-Flex. In Fig. 5, channels between cattle and UKSPO (Nodes of Switching Messages of Mobile Objects) are intended for channel service, and channels between cattle and AUPR are intended for batch service. Since this invention relates to the transmission of MVMO data, therefore, the description of the present invention is given by the example of signal transmission between cattle and AUPR.

Referring to Figure 5: when applying the concept of lu-Flex, you can connect multiple cattle to a fixed network through multiple AUPR (or UKSPO). Cattle, which are co-managed by AUPR, are referred to as the “joint PS area”; and cattle, which are managed jointly by the UKSPO, are referred to as the “joint CS area”. Moreover, such devices located in the same hierarchical position as UKSPO and AUPR are called the “core network” (BS). Each AUPR (or UKSPO) has an IRS (Network Resource Identifier), which is assigned its own special identifier. The IRS becomes part of the PVIMS (or SIMS), a temporary identifier assigned to this PSB. That is, when the RNC must create a connection to a fixed network to provide a certain packet (or channel) service for the UE, then the connection between the RNC and a specific AUPR (or USPO) is established based on the IRS included in the PWIMS (or SIMS), which is assigned to Vp If the PVIMS (or SIMS) is not assigned to the POB, as during the initial registration, then the RNC establishes a connection with a specific AUPR (or UESPO) taking into account the load of AUPR (or MCC). The relevant AUPR (or UCSPO) designates for PVIMS (or SIMS) its own IRS, which has been assigned to VOB.

If this procedure for creating a channel for transmitting MVMO data, described with respect to FIGS. 3 or 4, is applied in the situation where the lu-Flex concept is used, then the channel for transmitting MVMO data is re-formed in the same combined region PS, which is undesirable. That is, according to FIG. 5: if the data of the PSB group, which belong to the combined area PS No. 2, select the same MVMO service and then report the selection result to the corresponding AUPR, then there will be 12 possible transmission channels according to the RNC to which the data refers groups POB, and according to the type of the corresponding AUPR - Fig.6.

According to Fig.6: each DRS has many different channels corresponding to AUPR. For example, Region No. 2 of the SRD node is connected to AUPR No. 3, AUPR No. 4 and AUPR No. 5 using three different channels 601, 602 and 603, respectively; and Region No. 3 of the SRD node is connected to AUPR No. 3, AUPR No. 4 and AUPR No. 5 by three different channels 604, 605 and 606, respectively. Moreover, Region No. 6 of the SRD node is connected to AUPR No. 3, AUPR No. 4 and AUPR No. 5 by three different channels 607, 608 and 609, respectively; and Region No. 7 of the SRD node is connected to AUPR No. 3, AUPR No. 4 and AUPR No. 5 by three different channels 610, 611 and 612, respectively. In addition, AUMPRO is connected to AUPR No. 4, AUPR No. 5 and AUPR No. 6 by three different channels 613, 614 and 615.

But since AUPR No. 3, AUPR No. 4 and AUPR No. 5 control the same combined PS area (Region No. 2 of the SRD node, Region No. 3 of the SRD node, Region No. 6 of the SRD node and Region No. 7 of the SRD node), then it will be enough for AUMPRO to create a MVMO data channel to only one of the AUPRs; and it will be enough for the AUPR to transmit the MVMO data to the corresponding RNC (or the Area of the SRD nodes). In this case, the number of actually needed MVMO data channels is 5: 4 between the Region of the SRD and AUPR node, and 1 between the AUPR and AUMPRO.

The present invention provides a method for efficiently forming a channel for providing MVMO service even when applying the lu-Flex concept in MVMO service.

For this, two embodiments are proposed.

(1) Default AUPR information management method using cattle;

(2) A default AUPR information management method using AUPR.

The default AUPR information (hereinafter referred to as the Def_SGCN_MBMS_sel parameter) has a value corresponding to the AUPR identifier designated as default AUPR.

1. Method for managing default information using cattle

First, a description is given of a method for efficiently generating, using RNC, a transmission channel for providing MVMO services based on default AUPR information.

In order for cattle to manage the default AUPR information related to the corresponding IMMO service, additional rules need to be defined for the case when the concept

lu-flex is not applicable.

(1) The cattle must memorize and manage the default AUPR information according to the IMMO identifiers and provide relevant information for other AUPRs.

(2) The default AUPR information is set when the UEB selects the appropriate UE service and then informs the RNC of the selection result, or when other AUPRs provide default AUPR information for the RNC.

(3) If the default AUPR related to the MVMO service selected by a particular UE is not indicated, then the RNC deals with the value corresponding to the AUPR identifier calculated from the PVIMS of this UE as the default AUPR.

(4) The RNC remembers the default AUPR value of the MVMO service received from other AUPRs.

(5) AUPR, designated as the default AUPR for a given MVMO service, when it does not have information related to the corresponding MVMO service (information about POB, VIMG, etc.), provides the MVMO identifier and its own identifier to all cattle related to this combined PS area.

(6) Upon completion of a certain MVMO service, the corresponding AUPR, by default, must announce the end of the corresponding service to all cattle belonging to this combined PS area; and then the cattle erase the relevant information.

The description is further set forth by the example of redefining the signaling procedure defined in FIGS. 3 and 4, based on the additional rules set forth above.

For convenience of presentation: a separate description is provided with reference to the first method of initial registration for a specific MVMO service from among the groups of PSBs belonging to a specific joint area PS; and a second method for selecting the same MVMO service as another FSB belonging to the same combined PS domain after successful completion of the first method.

1.1 Initial registration procedure for a specific IMMO service

FIG. 7 illustrates a method for selecting a specific service by a first UE from among the groups of UEs related to a specific unified PS domain. This procedure corresponds to steps 404 to 406 of FIG. 4. According to Fig.7, it is assumed that POB No. 1 is located in the area (Region No. 1 of the SRD node), which is managed by the RNC No. 1, and has a PVIMS assigned by AUPR No. 1 during the initial registration process. It is also assumed that cattle No. 1, cattle No. 2 and cattle No. n belong to the same combined area PS 701; and that the joint area PS 701 is jointly managed by AUPR No. 1, AUPR No. 2 and AUPR No. n 702.

Turning to FIG. 7: At No. 1, at the stage of receiving the service, it obtains information about the available MVMO service from the cell in which the No. 1 is now located, and then selects the specific available MVMO service. If this service is selected by MVMO, then No. 1 informs for RNC No. 1, to which No. 1 belongs, that this service is selected - at step 703. At this time, No. 1 sends its own identifier to Cattle No. 1 ( e.g. PVIMS) and the identifier of the selected MVMO. This corresponds to the procedure performed between the PSA and the NRUS in step 404 of FIG. 4.

Cattle No. 1 then checks and changes the default AUPR information related to the selected MVMO service, based on the information received from POB No. 1 at step 704. The signaling procedure illustrated in FIG. 7 is performed in accordance with the MVMO service first selected by the equipment FOB No. 1 in a specific joint area PS. Therefore, it is obvious that the Def_SGSN_MBMS_sel parameter related to a specific MVMO service has not yet been generated. Having determined that the parameter related to the maintenance of the IMMO selected by the equipment of the software No. 1 is absent, the cattle No. 1 denotes the AUPR identifier (or default AUPR), corresponding to the IRS calculated from PVIMS, the identifier of No. 1 as the parameter Def_SGSN_MBMS_sel. That is, the value of the Def_SGSN_MBMS_sel parameter for identifying the corresponding AUPR, the existing ID_NNS (Cross-Domain Selector Node Selector) value can be assigned, or another constant can be assigned using a specific formula for identifying the default AUPR. In the implementation of the present invention: the value of the parameter Def_SGSN_MBMS_sel is set as the value corresponding to the identifier AUPR No. 1. If the value of the Def_SGSN_MBMS_sel parameter is set successfully, then the KRS No. 1 can manage the information illustrated in Table 1 about the maintenance of the IMMO selected by POB No. 1.

Table 1 Parameter Value MVMO Service Identifier MVMO service identifier selected by equipment Def_SGSN_MBMS_sel AUPR identifier No. 1

Cattle No. 1 must manage the information. Tab. 1 according to the MVMO service.

If the necessary information is completely specified by the specified procedure, then the RNC No. 1 transmits the service identifier of the MVMO selected by the equipment of the software No. 1, and the parameter value 706 to the AUPR No. 1 at step 705. Of course, after authentication, the identifier of the software No. 1 must be transmitted together. This corresponds to the procedure for transmitting the service-related signal from the NRUS to the AUPR in step 404 of FIG. 4.

At step 707, AUPR No. 1 performs the authentication process of No. 1 based on information managed by the RA. This is identical to step 405 of FIG. 4. If the authentication of POB No. 1 is successfully completed by the authentication process, then AUPR No. 1 concludes that the default AUPR for servicing MVMO selected by the equipment of Pob No. 1, it is AUPR No. 1 itself. If AUPR No. 1 concludes that AUPR No. 1 itself is the default AUPR corresponding to the selected MVMO service, then AUPR No. 1 determines that it does not have information about the selected MVMO service. Then, AUPR No. 1 enters the identifier of the equipment No. 1 in the list of groups that designated the WIMH related to the selected MVMO service and then requested the provision of the corresponding service. At step 708: AUPR No. 1 informs all the cattle (Cattle No. 2 - Cattle No. 1) that belong to the same PS area as the Cattle No. 1 that AUPR No. 1 is designated as the default AUPR. The information transmitted at the same time includes the identifier of the MVMO service selected by the equipment of software No. 1. Information Def_SGSN_MBMS_sel provided for AUPR No. 1 from cattle No. 1 can also be transmitted jointly (see 709).

When responding to this procedure: cattle No. 2 – cattle No. n set the parameter Def_SGSN_MBMS_sel related to a specific MVMO service in the same way as cattle No. 1 does at step 704. Then, at step 710, cattle No. 2 – cattle No. n is provided for AUPR No. 1 specified parameter Def_SGSN_MBMS_sel related to a specific service of the IMMO (see 711). This is the process of confirming that AUPR # 1 is successfully registered as AUPR by default. If steps 708–710 are completed successfully, then cattle No. 2 – cattle No. n can manage the same information as in Table. 1 controls cattle number 1.

At step 712, AUPR No. 1 transmits Def_SGSN_MBMS_sel to the RNC No. 1 (see 713), thereby informing the RNC No. 1 that the MVMO service selected by the equipment of the No. 1 software has been successfully registered. At step 714, the RNC No. 1 informs for PoB No. 1 that the selected MVMO service has been successfully registered. This procedure corresponds to step 406 of FIG. 4. At this time, VIMG can also be transmitted together - as described with reference to Figure 4.

In the process described above, FSA No. 1 completes the registration process for the selected specific MVMO service using cattle No. 1 and AUPR No. 1. The remaining steps, similar to step 408 and subsequent steps according to Figure 4, are set forth below. When comparing the signal transmission procedure according to FIG. 4 with the signal transmission procedure implemented by applying the lu-Flex structure, it becomes apparent that a new parameter is introduced that is controlled by the RNC. In addition, it can also be noted that cattle are supplemented by the process (704) of the formation and change of the value of each parameter. Of course, an additional signaling process is also introduced (steps 708-710); and for the same procedure, which is illustrated in FIG. 4, even information is needed, which must be additionally transmitted (see 706, 709 and 711).

1.2 Registration procedure for initially registered specific IMMO services

The following is a description of the process according to which - after PSA No. 1 has successfully completed the initial registration procedure for a specific MVMO service - other groups of FSBs belonging to the same PS area as PSA No. 1 request registration for the same MVMO service . For convenience, a separate description is given of the first registration process of the same IMMO service using other AUPRs; and a second process for registering MVMO services using AUPR No. 1, previously designated as default AUPR.

1.2.1 Registration using AUPR, which is not the default AUPR

FIG. 8 illustrates an example of a signaling procedure expected when a particular UE (hereinafter UE No. 2), belonging to the same combined PS domain as UE No. 1, registers the same MVMO service as the MVMO service provided by the equipment No. No. 1 using AUPR that are not AUPR # 1, designated as default AUPR. According to Fig. 8, it is assumed that POB No. 2 has a PVIMS assigned by AUPR No. 2.

Turning to FIG. 8: at step 803, the POB No. 2 selects the same MVMO service as the POB No. 1, and then forwards the service request for the selected MVMO service to the Cattle No. 2. At the same time, PSB No. 2 transmits its own special identifier and identifier of the selected MVMO service to Cattle No. 2. At step 804: RNC No. 2 verifies that the default AUPR corresponding to the selected MVMO service has been designated as AUPR No. 1 based on the corresponding parameter Def_SGSN_MBMS_sel controlled by the initial registration procedure related to the MVMO selected by the equipment of VOB No. 2. After checking AUPR by default: KRS No. 2 determines from PVIMS equipment No. 2 that the signal transmission connection should be established for AUPR No. 2. Then, at step 805, the cattle No. 2 transmits the identifier of the selected MVMO service and the value of the parameter Def_SGSN_MBMS_sel to AUPR No. 2 (see 806). The values of the transmitted parameters are presented in Table. 1).

At step 807: AUPR No. 2 performs the authentication procedure for POB No. 2 based on information managed by the RA. If authentication for POP No. 2 is successful, then AUPR No. 2 passes at step 808 the MVMO service identifier selected by the equipment of POB No. 2 and the identifier of POB No. 2 (see 809) to AUPR No. 1, AUPR by default. AUPR No. 1, AUPR by default of the selected MVMO service includes POB No. 2 in the list of equipment groups that wish to accept the corresponding MVMO service. After the new registration of POB No. 2 in the list of POs wishing to accept the selected MVMO service, AUPR No. 1 informs at step 810 of AUPR No. 2 that POB No. 2 is registered. At the same time, AUPR No. 1 transmits the identifier of the selected MVMO service, the identifier of POB No. 2, and VIMG together (see 811). At step 812: AUPR No. 2 transmits Def_SGSN_MBMS_sel to the RNC No. 2 (see 813), thereby informing the RNC No. 2 that the MVMO service selected by the equipment of the No. 2 software was successfully registered. At step 814: Cattle No. 2 informs PoB No. 2 of the successful registration of the selected MVMO service.

A comparison of the procedure of FIG. 8 with the procedure of FIG. 7 shows that the process (steps 808–810) of transmitting the PS information to the AUPR, the AUPR, by default, is reintroduced instead of the process (steps 708–711) in which the AUP No. 1 selected in as the default AUPR, transmits information according to Table. 1, related to the selected MVMO service, to all cattle related to a specific combined PS area.

1.2. Registration using AUPR by default

FIG. 9 illustrates an example of a signaling procedure expected when a specific PoE belonging to the same combined PS domain as Bean No. 1 will register the same MVMO service as the MVMO service provided by the No. 1 equipment using AUPR No. 1 AUPR is the default. The signaling procedure of FIG. 9 is part of the signaling procedure described with reference to FIG. 7. That is, the procedure illustrated in FIG. 9 corresponds to steps 703, 704, 705, 707, 712 and 714 of FIG. 7. Since steps 708–710 represent the process performed in the initial registration procedure using POA No. 1, a description thereof is not provided. According to Fig.9, it is assumed that POB No. 3 refers to cattle No. 1, and POB No. 4 refers to cattle No. n. Both POB No. 3 and POB No. 4 have PVIMS designated by AUPR No.1. After the successful completion of the procedure illustrated in FIG. 9: AUPR No. 1, selected as the default AUPR, can obtain information on all the POs that wish to receive the corresponding MVMO service from among the equipment groups belonging to the combined PS area. Therefore, the transmission channel for the transmission of certain MVMO data can only be set between AUPR No. 1, selected as the default AUPR, and AUMPRO.

Turning to FIG. 9: POB No. 3 acquires information about the available MVMO service from the cell in which it is currently located, using the service acquisition procedure, and then selects the specific available service. When choosing a specific MVMO service, POB No. 3 informs the RNC No. 1 to which it relates that a certain MVMO service is selected at step 901. In this case, POB No. 3 transfers its own identifier (eg, PVIMS) and the identifier of the selected service MVMO in cattle number 1.

At step 902: cattle No. 1 checks and changes the default AUPR information related to the selected MVMO service, based on information received from POB No. 3. KRS No. 1, having established that there is a parameter related to the MVMO service selected using POB No. 3, means IRS calculated from PVIMS, identifier POB No. 3 as the parameter Def_SGSN_MBMS_sel. In this example: the value Def_SGSN_MBMS_sel is set as the value corresponding to the identifier AUPR No. 1. If the value Def_SGSN_MBMS_sel is set successfully, then cattle No. 1 can enter the set parameters into the information illustrated in Table. 1, and then manage the MVMO service information selected by the equipment of the No. 3 software.

If the necessary information is completely set according to the above procedure, then the RNC No. 1 transfers the identifier of the MVMO service selected by the equipment of the software No. 3, and the parameter value 904 to AUPR No. 1 - at step 903. At step 905: AUPR No. 1 performs the equipment authentication process PSA No. 3 based on information managed by RA. If the authentication of POB No. 3 is successfully completed, then AUPR No. 1 concludes that the default AUPR for servicing MVMO selected by the equipment of POB No. 3 is AUPR No. 1 itself. AUPR No. 1 enters the identifier of the equipment of software No. 3 into the list of groups of equipment of the software that have requested appropriate service. At step 906: AUPR No. 1 transmits Def_SGSN_MBMS_sel to the RNC No. 1, thereby informing the RNC No. 1 that the MVMO service selected by the equipment of POB No. 3 was successfully registered. At step 908: Cattle No. 1 informs PSB No. 3 that the selected MVMO service has been successfully registered.

Although steps 909–916 of the registration of the MVMO service selected by the equipment of POA No. 4 are not described in detail, these steps are performed according to the same procedure as steps 901–908, and therefore are not repeated.

1.3 Service declaration procedure for a specific IMMO service

FIG. 10 illustrates a method for announcing that an MVMO service has actually been provided for UEs for which a particular MVMO service has been registered according to the procedures of FIGS. 7-9. This corresponds to the signaling procedure performed in steps 408–409 of FIG. 4.

Turning to FIG. 10: at step 1001, AUMPRO announces the start of service for AUPR No. 1, selected as the default AUPR: before starting service of the MVMO selected by the POB groups according to FIGS. 7, 8, and 9.

AUPR No. 1 - after announcing the start of the selected MVMO service through AUMPRO - announces the commencement of the corresponding service to cattle controllers that manage groups of POBs that have requested the receipt of the corresponding MVMO service from among all cattle (cattle No. 1 – cattle No. n) related to a certain integrated PS areas: in steps 1002-1004. As the message currently available, you can use the message retrieval call –– the existing message PCSR (Application Component of the Radio Access Network). The search message can be sent to all cattle belonging to this combined PS area: if the PoB, having selected the appropriate MVMO service, moves to another cell.

Upon receipt of the search message: Cattle must announce the start of the registered IMMO service to all relevant VOB groups. This procedure is performed at steps 1005, 1008 and 1012. The message available for these steps includes the paging type No. 1 and the paging type No. 2. The type of message can be selected depending on the URR state of the corresponding software. When receiving a search message of type No. 1 or a search message of type No. 2: POB inform the corresponding RNC that they will actually receive the MVMO service they have chosen. This procedure corresponds to steps 1006, 1009 and 1013. At step 1006: POB No. 1 and POB No. 3 inform cattle No. 1 that they will actually accept the selected MVMO service. At step 1009: FSA No. 2 informs Cattle No. 2 that it will indeed accept the selected MVMO service. At step 1013: FSA No. 4 informs Cattle No. n that it will actually accept the selected MVMO service. The currently available message includes a paging response message.

Cattle inform AUPR, connected to the corresponding MVMO service, that the corresponding groups of FSBs are now requesting MVMO service. That is, cattle No. 1 and cattle No. n inform AUPR No. 1, selected as the default AUPR, that POB No. 1, POB No. 3 and POB No. 4 wish to accept MVMO service. This process corresponds to steps 1007 and 1014. But cattle No. 2 must inform AUPR No. 2 that POB No. 2 wishes to accept MVMO service, and AUPR No. 2 must report this again to AUPR No. 1. This corresponds to steps 1010 and 1011. At step 1011, the MVMO or VIMG identifier and the VOB identifier need to be transmitted.

After all these steps have been successfully completed, the transmission channel for providing MVMO services can be set among the PoB, RNC (or NRUS) and AUPR No. 1, selected as the default AUPR: at stages 411, 412, 413 and 414 according to FIG. 4.

1.4. Registration Procedure for the Currently Available MVMO Service

11 illustrates a procedure expected when an FSE selects an IMMO service that has already been initiated in a specific federated PS domain. In this case, all the cattle that are included in the joint area PS already have default AUPR information for the corresponding MVMO service when all the steps according to Figs. 7 and 10 are performed. According to Fig. 11, it is assumed that No. 5 relates to cattle , and AUPR No. 1 has a designated PVIMS. In addition, it is assumed that the default AUPR of the MVMO service requested by the OP No. 5 has an assigned Def_SGSN_MBMS_sel. It is also assumed that, according to FIG. 11, AUPR is defined by default as Def_SGSN.

Turning to Fig. 11: POB No. 5 selects a previously initiated MVMO service and informs Cattle No. 1 of the selection result. At step 1102: cattle No. 1 checks the parameter Def_SGSN_MBMS_sel related to the maintenance of the IMMO selected by the equipment of the software No. 5. In this example: the value of the Def_SGSN_MBMS_sel parameter means Def_SGSN. At step 1103: KRS No. 1 determines, from PVIMS equipment POB No. 5, that information related to MVMO service selected by equipment POB No. 5 should be transferred to AUPR No. 1, and then announces this to AUPR No. 1. Steps 1101, 1102, and 1103 correspond to step 304 of FIG. 3.

At step 1104: AUPR No. 1 performs the authentication procedure of the equipment of software No. 5 based on information managed by the RA. The authentication procedure corresponds to step 305 of FIG. 3. At step 1105: AUPR No. 1 provides an identifier for the MVMO service selected by the OP equipment No. 5, and an identifier POB No. 5 for Def_SGSN, denoting the default AUPR. Def_SGSN enters the UE No. 5 into the list (for a multicast group) of UE groups for the corresponding MVMO data, and then at step 1106 informs AUPR No. 1 about this introduction of the equipment UE No. 5. At step 1107: AUPR No. 1 informs Cattle No. 1 that the registration of POB No. 5 has been successfully completed. This procedure corresponds to step 306 of FIG. 3.

If the MVMO service, previously selected by the equipment of POB No. 5, is provided even in cattle No. 1, i.e. if other VHF groups related to RNC No. 1 are already receiving the appropriate MVMO service, then RNC No. 1 can transmit the parameter needed for VLR No. 5 when receiving MVMO data at step 1109. But when other RNCs belonging to the same combined PS area, Since KRS No. 1 provides the corresponding MVMO data, and among the groups of VOB related to KRS No. 1, VOB receiving the corresponding MVMO data is not available, in this case, the procedure of step 1108 is necessary to create a channel for the MVMO transmission data between Def_SGSN and Cattle number 1.

Unlike the procedure of FIG. 3: the procedure of FIG. 11 also includes steps 1102, 1104, 1105, 1106, and 1108. Even in step 1103, which has already been determined in FIG. 3, the transmission parameter value is different.

1.5 Completion of a specific service procedure for IMMO

As shown in FIG. 12: if a specific MVMO service is completed, then the corresponding AUPR default information needs to be erased. To do this: By default, AUPR passes the identifier of the corresponding MVMO service to all cattle belonging to the combined PS area. Upon receipt of the MVMO identifier: cattle erase the information illustrated in Table. 1, in the appropriate service managed by them.

1.6 Another example of an initial registration procedure for a specific IMMO service

According to the initial registration procedure described with reference to FIG. 7, it is assumed that the PSB is requesting cattle to provide specific IMMO services. But in another example of the initial registration procedure described below, it is assumed that the PoP requests AUPR to provide a specific MVMO service, and then the AUPR informs the RNC - via the radio facilities connected to the Po - that a specific MVMO service has been requested by this Poob.

According to Fig. 18, the same assumption is made as in Fig. 7. FIG. 18 illustrates a process for initially selecting a specific MVMO service for a particular PHB from among the groups of PHBs related to a particular joint PS domain. In this example: information about the MVMO service selected by this UE is included in the message of the NU. “NU message” is a message that includes content that the cattle cannot know. For convenience, we proceed from the assumption that cattle No. 1 and cattle No. 2 together belong to the same combined PS region, and that AUPR No. 1 and AUPR No. 2 jointly control cattle controllers belonging to the combined PS region.

Turning to FIG. 18: at step 1801, the POB related to BWC No. 1 selects a specific MVMO service and then informs AUPR No. 1 of the selection result, together with its own specific identifier. At the same time, it is assumed that the FSB has a PVIMS assigned by the AUPR No.1 node. An identifier associated with MVMO for identifying a specific MVMO service selected by the PoB equipment, and a PoP identifier can be transferred to AUPR No. 1 by the message of the Request for Activation of the MVMO Context.

Upon receipt of the Request for Activation of the MVMO Context: AUPR No. 1 checks whether the FSB can receive the relevant MVMO data - at step 1802. If the verification procedure is successful, then AUPR No. 1 transmits information about the identifier related to the MVMO service selected by the VBM data to Cattle No. 1 - at step 1803. Information about the identifier related to the selected MVMO service can be transmitted through the Request message for Participation in the MVMO. Cattle No. 1 then determines whether the AUPR is designated by default for serving the MVMO corresponding to the identifier associated with the MVMO based on the received information about the identifier related to the MVMO. If AUPR is not designated by default, then KRS No. 1 designates a specific AUPR as the default AUPR. At step 1804: RNC No. 1 transmits the UID identifier and the identifier of the selected MVMO service to the default AUPR designated using the Notification of Participation in MVMO message. But if the default AUPR related to the selected MVMO service is already indicated, then the RNC No. 1 passes the identifier Pob and the identifier of the selected MVMO service to the corresponding AUPR by default. 18, it is assumed that AUPR is designated by default as AUPR No. 2. In this example: this invention provides a method for designating a default AUPR for a specific MVMO service using cattle. According to the simplest method: cattle can assign AUPR by default, taking into account the load of AUPR as in the well-known lu-Flex structure.

AUPR by default sets the information about the selected MVMO service and then provides all the cattle belonging to the same combined PS area, such as cattle No. 1, the identifier of the selected MVMO service and information indicating that it is designated as the default AUPR by the corresponding MVMO service - on step 1805. But if AUPR No. 2 has already memorized the information on the corresponding MVMO service, then it enters the ID of the FSB, adopted at step 1804, in the relevant information related to the maintenance of the MVMO and then proceeds to stage 1809.

Steps 1806 and 1808 represent the process of creating a channel for transmitting the corresponding MVMO data between AUPR No. 2, designated as default AUPR, and AUMPRO. This process is performed when the FSE first selects, at step 1801, the appropriate MVMO service in the combined PS domain managed by the AUPR node 2. When receiving a request to create a channel for transmitting relevant data from AUPR No. 2: AUMPRO transmits a Message about Participation in Multicast IP Transmission to SPR-SK at step 1807 to announce that it has also received IMMO data.

At step 1809: AUPR No. 2 designates a VIMG related to the selected MVMO service, and then transmits the designated VIMG to AUPR No. 1 using the MVMO Context Creation Notification message. At step 1810: AUPR No. 1 transmits VIMG provided from AUPR No. 2 for VOB.

As indicated above, when another PSB related to the same combined PS domain as the PSB selects the same MVMO service, the description of steps 1806, 1807, and 1808 can be omitted. At the same time, at step 1804: cattle (cattle No. 1 or cattle No. 2 in this example) transmits the identifier of the corresponding software and the service identifier of the MVMO to AUPR No. 2, previously designated as the default AUPR.

2. Default AUPR information management method using AUPR

The following is a description of a method for managing the information illustrated in FIG. 1 using AUPR. In order for AUPR to manage information related to the corresponding IMMO service, it is necessary to additionally define the following rules - in contrast to the case when lu-Flex is not used.

(1) AUPR shall memorize and manage the default AUPR information in accordance with the IMMO identifiers. For example, even when lu-Flex is not used, AUPR must manage the VIMG and the list of groups of PoBs that wish to receive the appropriate service data according to the IMMO service.

(2) The default AUPR information is set when the UE accepts the service identifier of the IMMO selected by the UEO, or when the default AUPR information is received from other AUPRs.

(3) If the default AUPR related to the MVMO service selected by the UE data is not indicated, then the AUPR designates its own identifier as the default AUPR value. In addition, AUPR provides its other identifier and corresponding IMMO identifier for other AUPRs.

(4) AUPR remembers the data presented in Table. 1 information using the default AUPR value of the IMMO data received from other AUPR.

(5) At the end of a specific MVMO service, the corresponding AUPR transfers by default the identifier of the corresponding MVMO service to other AUPRs that jointly manage the combined PS area; and all AUPRs that receive the IMMO identifier erase the information in Table 1 that they manage.

The following is a description of the re-definition of the signaling procedure, determined according to FIGS. 3 and 4, based on the additional rules above. For convenience, a separate description is provided with reference to the first initial registration process for a specific MVMO service among the PSB groups belonging to a specific joint PS area, and to the second process of selecting the same MVMO service by other PSB groups belonging to the same combined PS area after successful completion of the first process.

2.1 Initial registration procedure for a specific IMMO service

FIG. 13 illustrates a process for selecting a specific MVMO service by the first UEB from among the UEB groups belonging to a specific unified PS domain. This procedure corresponds to steps 404–406 of FIG. 4 and is another example of the same situation that is described with reference to FIG. 7. According Fig.13: PSA No. 1 is located in the area (Region No. 1 node DRS), which is controlled by cattle No. 1, and it has PVIMS designated node AUPR No. 1 in the initial registration process. It is also assumed that cattle No. 1, cattle No. 2 and cattle No. n belong to the same combined area PS 1301, and the combined region 1301 PS is jointly managed by nodes AUPR No. 1, AUPR No. 2 and AUPR No. n - 1302.

Turning to FIG. 13: VOB # 1 acquires — at the service acquisition stage — information about the existing MVMO service from the cell in which VOB No. 1 is now located, and then selects the specific MVMO service available. If a specific MVMO service is selected, then No. 1 informs, for Cattle No. 1, to which No. 1 belongs, that a certain MVMO was selected at step 1303. Cattle No. 1 identifier POB No. 1 determines that the corresponding message must be transmitted to AUPR No. 1. As a result of this determination, cattle No. 1 transmits a message to AUPR No. 1. At this time, POB No. 1 transfers to AUPR No. 1 its own identifier (eg, PVIMS) and the identifier of the selected MVMO. This corresponds to step 404 of FIG. 4.

Then, AUPR No. 1, at step 1304, performs the authentication process of No. 1 based on information managed by the RA. This is identical to step 405 of FIG. 4. If the authentication for POB No. 1 was successfully completed in the specified authentication process, then AUPR No. 1 concludes that, by default, AUPR for servicing the IMMO selected by the POB No. 1 is AUPR No. 1 itself. If AUPR No. 1 concludes that it is the default AUPR for the selected MVMO service, then AUPR No. 1 determines that it does not have information about the selected MVMO service. Then AUPR No. 1 designates the VIMG related to the selected MVMO service, and then enters the identifier VOB No. 1 into the list of VOBs that requested the appropriate MVMO service. If the authentication was successfully completed by the authentication procedure, then AUPR No. 1 checks and changes the default AUPR information related to the selected MVMO service based on the information received from the POB No. 1 at step 1305. The signaling procedure shown in FIG. 13 performed in relation to the IMMO service selected first by the PSB No. 1 in this combined PS domain. Therefore, it can be understood that the parameter Def_SGSN_MBMS_sel related to the corresponding MVMO service has not yet been generated. The parameter Def_SGSN_MBMS_sel can be generated in accordance with the description of the first implementation. That is, the default identifier for identifying AUPR, a specific identifier for identifying AUPR, can be identified using the available information or a specific formula. Therefore, as for the DefOSGSN_MBMS_sel parameter of the MVMO service selected by the equipment No. 1: Cattle No. 1, having determined that there is no parameter related to the formation, it sets the AUPR identifier corresponding to the IRS calculated from PVIMS, No. identifier No. 1 as the value of the parameter Def_SGSN_MBMS_sel. According to the implementation of the present invention: the value of the parameter Def_SGSN_MBMS_sel is set as the value corresponding to the identifier AUPR No. 1. If the value of the Def_SGSN_MBMS_sel parameter is successfully set, then AUPR No. 1 can control the information illustrated in Table. 2, about the maintenance of MVMO, selected equipment AUPR No. 1.

table 2 Parameter Value MVMO Service Identifier MVMO service identifier selected by equipment Def_SGSN_MBMS_sel AUPR identifier No. 1 WIMG Assigned WIMG FOB List ID of the UM requesting the MVMO service

By default, AUPR, which are selected for certain types of IMMO services, should manage the information in Table. 2, according to the services of the IMMO.

If the necessary information is completely set by the above procedure, then AUPR No. 1 transmits, at step 1306, the service identifier of the MVMO selected by the equipment of POB No. 1, and the parameter value 1307 to all AUPR related to the same combined PS area, as AUPR No. 1. That is, AUPR No. 1 informs the rest of AUPR (AUPR No. 2 – AUPR No. n) that it is designated as the default AUPR for the corresponding MVMO service. The information transmitted in this case can become not only the identifier of the IMMO, but also the default Def_SGSN_MBMS_sel parameter of the AUPR service (see 1307).

At the same time, AUPR No. 2 – AUPR No. n sets the Def_SGSN_MBMS_sel parameter related to a specific MVMO service in the same way as the operation performed at step 1305 does. At 1308: AUPR No. 2 – AUPR No. n pass the set Def_SGSN_MBMS_sel parameter to specific service of MVMO, in AUPR No. 1. (See 1309). This is a process to confirm that AUPR # 1 has been successfully registered as the default AUPR. If steps 1306 and 1308 are successfully completed, then AUPR No. 2 – AUPR No. n can manage the same information as the information in Table. 2, managed by the node AUPR No. 1.

At step 1310: AUPR No. 1 transmits Def_SGSN_MBMS_sel to the RNC No. 1, thereby informing the RNC No. 1 that the MVMO service selected by the equipment of POB No. 1 was successfully registered. Cattle No. 1 then reports to PS No. 1 that the selected MVMO service has been successfully registered. This procedure corresponds to step 406 of FIG. 4. Moreover, VIMG can also be transmitted together - in accordance with the description relative to Figure 4.

In the course of the process described above: PSA No. 1 completes the registration process for the selected specific service using cattle No. 1 and AUPR No. 1. When comparing the signal transmission procedure according to FIG. 4 with the signal transmission procedure according to the structure with the introduction of lu-Flex, it is clear that the parameter controlled by the AUPR node has been re-introduced. It should also be noted that the process (step 1305) of the formation and change of the value of each parameter is entered into the cattle. Of course, an additional signaling process can also be introduced (steps 1306 and 1308).

2.2 Registration procedure for initially registered specific IMMO services

The following is a description of the process in which, after a successful initial registration procedure with the equipment No. 1 for a specific MVMO service, other groups of PSs belonging to the same PS area as No. 1, request registration of the same MVMO service. For convenience, a separate description is given of the first process of registering the MVMO service using AUPR No. 1, previously designated as default AUPR, and the second process of registering the same MVMO service using other AUPR.

2.2.1 Registration using AUPR which is not the default AUPR

Fig. 14 illustrates an example of a signaling procedure expected when a particular UE (hereinafter UE No. 2), belonging to the same combined PS domain as UE No. 1, registers the same MVMO service as the MVMO service provided by the equipment No. No. 1 using AUPR that is not AUPR No. 1, designated as default AUPR. According Fig.14 it is assumed that POB No. 2 has PVIMS assigned by the node AUPR No. 2.

Turning to FIG. 14: at step 1403, POB No. 2 selects the same MVMO service as POB No. 1, and then sends a service request for the selected MVMO service to BWC No. 2. At the same time, FSA No. 2 transfers its own special identifier and the identifier of the selected MVMO service to AUPR No. 2. At step 1404: AUPR No. 2 performs the authentication procedure of the software No. 2 based on information managed by the RA. If the authentication for POA No. 2 is successfully completed, then AUPR No. 2 can determine, at step 1405, that the value of the Def_SGSN_MBMS_sel parameter related to the MVMO service selected by the equipment of POA No. 2 is set for AUPR No. 1. At step 1406, AUPR No. 2 transmits the MVMO service identifier selected by the VOB No. 2 equipment and VOB 2 identifier (see 1407) to AUPR No. 1, AUPR by default. AUPR No. 1 enters POB No. 2 into the list of POs that wish to accept the appropriate MVMO service, and then informs AUPR No. 2 of the corresponding VIMG (see 1419). At step 1410: AUPR No. 2 informs for POB No. 2 that the registration of the selected MVMO service has been successfully completed.

2.2.2 Registration using default AUPR

FIG. 15 illustrates an example of a signaling procedure expected when other groups of PSAs belonging to the same combined PS domain as PS No. 1 continue to request registration of the same MVMO service using AUPR No. 1, AUPR by default. According to Fig.15, it is assumed that PSA No. 3 refers to cattle No. 1, and PSA No. 4 relates to cattle No. n. It is also assumed that POB No. 3 and POB No. 4 have PVIMS assigned by AUPR No.1.

Turning to FIG. 15: at step 1501, POB No. 3 selects the same MVMO service as PSB No. 1, and then sends a service request for the selected MVMO service to BWC No. 1. Cattle No. 1 again sends the service request to AUPR No. 1, AUPR by default. At this time, POB No. 2 transmits its own special identifier and identifier of the selected MVMO service to Cattle No. 2. At step 1502: AUPR No. 1 performs an authentication procedure for authenticating the software No. 3 based on information managed by the RA. If the authentication for POB No. 3 is successfully completed, then AUPR No. 1 determines, at step 1503, that it has already been designated as the default AUPR for servicing the MVMO selected by the equipment of Pob No. 3. Then, AUPR No. 1 introduces the No. 2 No. 3 into the list of groups of the No. 1 who wish to accept the appropriate MVMO service. At step 1504: AUPR No. 1 transmits Def_SGSN_MBMS_sel to cattle No. 1 (see 1510). Cattle No. 1 transmits Def_SGSN_MBMS_sel, provided from AUPR No. 1, to POB No. 3, thereby informing BS No. 3 that the selected MVMO service was successfully registered. But step 1504 may not be performed.

The registration procedure for POB No. 4, which chose the same MVMO service as POB No. 1, in AUPR, by default, is performed at steps 1506–1509. This procedure is performed in the same manner as the procedure performed in the POB No. 3.

If the procedure according to Figs. 13, 14 and 15 is successfully completed, then AUPR No. 1, selected as the default AUPR, can acquire information on all groups of UBNs that require receiving the corresponding IMMO service from among the UBG groups belonging to the combined PS area . Therefore, a transmission channel for the transmission of certain data of the IMMO can only be created between AUPR No. 1 and AUMPRO.

When the IMMO service is actually provided for groups of PSAs that have completed registration for a specific IMMO service according to the procedure of FIGS. 13, 14 and 15, then the method for reporting this situation follows the signaling procedure illustrated in FIG. 10 according to the first embodiment.

2.2.3 Registration of the initiated MVMO service

FIG. 16 illustrates a channelization procedure expected when an UE selects an IMMO service that has already been initiated in a specific unified PS domain. In this case, all AUPRs that jointly manage the same combined PS domain already have default AUPR information for the corresponding MVMO service due to the procedures performed in accordance with Figs. 13-15. In this case, if the lu-Flex concept is not applied, then the procedure for requesting the already initiated service of the IMMO is given in Figure 3. According to Fig.16, it is assumed that POB No. 5 refers to cattle No. 1, and AUPR No. 1 appointed PVIMS. It is also assumed that, by default, the AUPR of the MVMO service requested by the hardware of software No. 5 is defined as Def_SGSN.

Turning to FIG. 16, at step 1601: POB No. 5 selects an already initiated MVMO service and then sends a service request for the selected MVMO service to RNC No. 1. Cattle No. 1 determines from PVIMS equipment at No. 5 that the information related to the MVMO service selected by equipment at No. 5 should be transferred to AUPR No. 1 and announces the result of the determination to AUPR No. 1. At step 1602: AUPR No. 1 performs an authentication procedure for authenticating the software No. 5 based on information managed by the RA. The authentication procedure corresponds to step 305 of FIG. 3. At step 1603: AUPR No. 1 checks the value of the parameter Def_SGSN_MBMS_sel related to the maintenance of the MVMO selected by the equipment of the software No. 5. In this example: the value Def_SGSN_MBMS_sel indicates Def_SGSN. At step 1604: AUPR No. 1 transmits the service identifier of the MVMO selected by the equipment of the No. 5 software, and its own identifier to Def_SGSN, or AUPR by default. At step 1605: Def_SGSN enters POB No. 5 into the list of groups of PoB receiving the corresponding MVMO data, and then reports the result of such introduction for AUPR No. 1. At step 1606: AUPR No. 1 informs Cattle No. 1 that the registration of POB No. 5 has been successfully completed. This procedure corresponds to step 306 of FIG. 3.

Even if cattle No. 1 now provides MVMO service, already selected by the equipment of software No. 5, i.e. if another PHC related to cattle No. 1 is already receiving the appropriate MVMO service, then cattle No. 1 can transmit the parameter necessary for the code No. 5 when receiving MVMO data at step 1608. Step 1607 can be omitted. But when other cattle belonging to the same joint PS domain as cattle No. 1 provide the corresponding MVMO service, and there is no VOB accepting the corresponding MVMO service among the groups of VOB related to the cattle No. 1, then it is required the procedure of step 1607 to create an MVMO data transmission channel between Def_SGSN and RNC No. 1.

2.3 Completion of a specific MVMO service procedure

17: if a specific MVMO service is completed, then the corresponding default AUPR information in Table 2, managed by each AUPR, needs to be erased. For these purposes, the AUPR by default transmits the identifier of the corresponding MVMO service to all the AUPRs that together manage the same combined PS area. Upon receipt of the MVMO identifier, the specified AUPR are erased, in Table. 2, all the information they manage about the corresponding maintenance of the MVMO.

Of course, the foregoing embodiments are applicable even to the combined CS region in the same way. Accordingly, upon receipt of a data request, although not a request for IMMO data, from groups of POBs belonging to that joint area, the RNC can create a transmission channel using the default AUPR or UCSPO by default when creating the AUPR or UCSPO, thereby ensuring the ability to transmit and receive data. Although the foregoing embodiments are described with reference only to an example of control by means of RNC and AUPR, the present invention can also provide a method for controlling an MBMO transmission channel between RNC and AUPR using RA. In addition, the data transmission channel can be controlled separately according to the types of services, even for services provided in a fixed network, and not MVMO services.

3. The procedure for transmitting data IMMO

Fig. 19 illustrates a procedure for maintaining a service that may occur while the actual transmission of the corresponding IMMO data has begun after the POB groups have selected a specific IMMO service using processes 7, 13 and 18, and after designating the default AUPM corresponding to selected MVMO service.

At step 1901: SPR-SK plans the relevant MVMO data and transfers the planned MVMO data to AUMPRO. AUMPRO again sends MVMO data to AUPR No. 2, AUPR by default. Upon receipt of the MVMO data, AUPR No. 2 notifies the relevant RNC that the MVMO service has actually begun at step 1902. At the same time, each RNC notifies, at step 1903, each BOP that the corresponding MVMO service has actually begun. In this case, the term “corresponding cattle” means cattle, which includes groups of POBs who have chosen the appropriate MVMO service, or all cattle included in this service area.

At step 1904: Cattle informs AUPR No. 2 that it will indeed receive MVMO data using the Request for Service MVMO message sent to AUPR No. 2. Cattle and AUPR No. 2 create a channel for transmitting the corresponding MVMO data using steps 1905 and 1906.

If the channel for transmitting the corresponding MVMO data is created using the steps outlined above, then the UB, which was informed at the stage 1903 of starting the service of the MVMO selected by it, informs the corresponding RNC that a radio channel is needed for reception - step 1907. According to another embodiment step 1907 can be performed before step 1904. At step 1908: each RNC provides information related to a given channel to the UE for actually transmitting the corresponding IMMO data to the UE.

AUPR No. 2 transmits the relevant MVMO data to the RNC No. 1 at step 1909, and the RNC No. 1 transfers the MVMO data provided by the AUPR No. 2 to Pob - step 1910. If there is no more MVMO data to transmit, then the RNC No. 1, at step 1911, sends a request to the PSU to release the current channel.

According to the foregoing: this invention forms one channel between the RNC and AUPR and one channel between one AUPR for the combined PS and AUMPRO region for transmitting the same IMMO data, although the IMMO data channel is created in a situation where the lu-Flex concept is applied. Thus, the present invention improves the efficiency of wired / wireless resources to provide MVMO service.

Although the invention has been illustrated and set forth in relation to its preferred embodiment, it will be apparent to those skilled in the art that various formal and particular changes are possible within the concept and scope of the invention as defined by the appended claims.

Claims (21)

1. A system for Multimedia Broadcasting / Multicast Service (MVMO) for user equipment groups (POB) requesting MVMO service in a code division multiple access (CDMA) mobile communication system, comprising: a plurality of POB groups for requesting the desired IMMO service and receiving the IMMO service provided upon request; a plurality of radio network controllers (RNCs) for transmitting data related to MVMO service to the UE groups connected to them by radio facilities from among the UE groups that requested service; and a plurality of Serving GPRS Support Nodes (OUP) connected to each of the RNCs to control the procedure related to the maintenance of the IMMO for groups of POBs requesting service; in which GPRS GUPs by default are exclusively designated for at least each individual MVMO service, while GPRS GUPs by default pass through the KRS controllers the IMMO data for the corresponding MVMO service to the FOB groups requesting this MVMO service. 2. The system according to claim 1, in which the GPRS OUP by default for MVMO service is designated by a cattle controller made with the ability to connect, using radio, to the software that was the first to request MVMO service. 3. The system according to claim 1, in which the GPRS OUP, which assigned SIMS (Temporary Naming of the Mobile Station) to the UE equipment, the first to request MVMO service, is designated as the default GPRS OUP for this MVMO service. 4. A method for determining the default GPRS GUPS Support Node to provide Multimedia Broadcasting / Multicast Service (MVMO) service to user equipment groups (POB) requesting MVMO service in a code division multiple access (CDMA) mobile communication system having a first group comprising a plurality of radio network controllers (RNCs), a second group including a plurality of GPRS OUPs configured to connect to each of the RNCs in the first group, and a plurality POB made with the possibility of connection using radio means with cattle controllers; Whereby accept, by one of the RED, a service request for a given MVMO service; if the GPRS GUP information by default corresponding to this MVMO service is not stored in the one who received the cattle service request - select, using the cattle service request received, one of the GPRS GUPs as the default GPRS GUP; and they report, using the selected default GPRS GUP, to all other cattle - with the exception of those who requested cattle service - that the GPRS GUP is controlled by default by the MVMO service. 5. The method according to claim 4, in which the GPRS OUP by default is selected taking into account the load distribution of the GPRS OUP nodes. 6. The method according to claim 4, which also comprises the step of registering, using the default GPRS OUP, the UE equipment requesting the IMMO service in the list of UMB groups corresponding to the IMMO service. 7. The method according to claim 6, which also includes the step of introducing the UE to the list of UE groups corresponding to the MVMO service, upon request of the GPRS OUP, the connection for signal transmission of which is established with the UB that requested the MVMO using the GPRS OUP, if the GPRS OUP information on the default corresponding to the IMMO service is remembered in the one who received the request for cattle service. 8. The method according to claim 4, which also includes the step of informing, using the default GPRS GUPS, of the UB groups that MVMO service should be initiated, using cattle controllers; and the subsequent step of transferring the IMMO data for the IMMO service to the FSB groups. 9. The method of claim 8, which also includes the step of introducing, by default GPRS OUP, the new PHB into the list of PHB groups corresponding to the MVMO service, and then creating a signal transmission connection with the new MVP if a service request for this MVMO service Adopted by the new FS during the transmission of MVMO data. 10. The method according to claim 4, which also includes the stage according to which the GPRS OUP by default - if the IMMO service is completed - makes a request to the cattle controllers to erase the information stored in them GPRS OUP by default, and the subsequent stage of release of connection with cattle controllers. 11. The default method for determining the GPRS Serving Support Node (GPRS) for providing Multimedia Broadcasting / Multicast Service (MVMO) service to user equipment groups (POB) requesting MVMO service in a code division multiple access (CDMA) mobile communication system, having a first group including a plurality of radio network controllers (RNCs), a second group including a plurality of GPRS GLCs configured to connect to each of the RNCs in the first group, and a plurality in POB, made with the possibility of connection using radio means with cattle controllers; Whereby transmit a service request to any GPRS GUP; accept, by one of the GPRS PMOs, a service request for this IMMO service; if the default GPRS GUP information corresponding to this MVMO service is not stored in the GPRS GUP service who received the service request, then the GPRS GUP service received the service request chooses itself as the default GPRS GUP; and they report, using the selected GPRS GUP by default, to another GPRS GUP, except for the one who received the GPRS GUP service request, that the GPRS GUP is controlled by default by the GPRS service. 12. The method according to claim 11, which also includes the registration step, using the default GPRS OUP, which requested the service of MVMO PoB equipment, in the list of PoB groups corresponding to the MVMO service. 13. The method according to p. 12, which also includes the stage according to which other GPRS GUPs ask the GPRS GPRS to enter the GPRS by default into the list of GPRS groups corresponding to the MVMO service if the GPRS GPRS default information corresponding to this MVMO service is stored. 14. The method according to claim 11, which also includes the stage according to which the GPRS OUP by default informs, with the help of the cattle controllers, a group of UBs that this MVMO service will be initiated; and the subsequent step of transmitting the IMMO data for serving the IMMO in the UE. 15. The method according to claim 14, which also includes the step of introducing, by default GPRS GUPS, a new FSN into the list of FSB groups corresponding to the MVMO service if the request for this MVMO service is accepted by the new FSM during the transmission of MVMO data; and the next step in creating a connection with the new software. 16. The method according to p. 15, which also includes the stage according to which the GPRS GUP by default requests the other GPRS GPRS to erase the default GPRS GPRS information stored in them if the MVMO service is completed. 17. A method of providing a Multimedia Broadcasting / Multicast Service (MVMO) service using a single GPRS Serving Support Node (GUP) from a plurality of GPRS GLC (in a code division multiple access (CDMA) mobile communication system containing a plurality of controllers a radio network (RNC), a plurality of GPRS OUPs connected to each of the RNCs, and a plurality of PoBs configured to be connected by radio means to the RNC; and for the provision of IMMO services for the PHB groups; Whereby: indicate, with the help of cattle that has accepted the request for this MVMO service, one single GPRS GUP as the default GPRS GUP, taking into account the load of each of the GPRS GUPs; transmitting an identifier for identifying the MVMO service and an identifier for identifying the default GPRS GUP to the default GPRS GUP; and Using GPRS OUP, by default, it is determined whether the given MVMO service is available; and transmitting an identifier for identifying a given MVMO service and an identifier for identifying a default GPRS PMO to other RNCs, with the exception of the RNC that received a service request for this MVMO service. 18. The method according to 17, which also includes the step of transmitting, by means of cattle, an identifier for identifying the MVMO service and an identifier for identifying the default GPRS OUP in the GPRS OUP, the signal transmission connection of which with the MVMO requesting this service is established, if already indicated GPRS PMO by default, corresponding to the IMMO service; and the step of transmitting to the GPRS OUP by default, using the GPRS OUP, the signal transmission connection of which is established, an identifier for identifying the MVMO service and an identifier for identifying the UOB requesting this MVMO service. 19. The method according to 17, which also includes the stage according to which the GPRS GUP by default, through the cattle controllers, informs the UB groups that this MVMO service will be initiated; and the subsequent step of transmitting the IMMO data for this IMMO service to the VOB groups. 20. The method according to claim 19, which also comprises the step of creating a connection with the new POB using the GRS OUP by default, if the request for this MVMO service is received from the new POB during the transmission of MVMO data. 21. The method according to 17, which also includes the stage according to which the GPRS OUP by default requests the cattle controllers to erase the GPRS OUP information stored in them, if the MVMO service is completed; and the subsequent step, the release of the connection of cattle.

Images