WO2005039104A1

WO2005039104A1 - A method and apparatus for implementing internet protocol (ip) multicasting service in the mobile communication system

Info

Publication number: WO2005039104A1
Application number: PCT/CN2003/000724
Authority: WO
Inventors: Jie Feng; Dongliang Liu
Original assignee: Utstarcom(China)Co.Ltd.
Priority date: 2003-08-27
Filing date: 2003-08-27
Publication date: 2005-04-28
Also published as: CN100375423C; CN1820454A; AU2003261578A1

Abstract

A method for implementing Internet protocol OP) Multicasting service in the mobile communication system, in which the said mobile communication system comprises a gateway GPRS support node (GGSN) and a domain name system (DNS). The said method is characterized in that comprises the steps of: receiving a access point name (APN) and a plurality of mobile station integrated service digital network (MSISDN) numbers by the said GGSN; creating the said APN policy, and adding the tag information of the said APN into the APN tag list of the said GGSN; adding a record including the IP addresses of the said APN and the said GGSN into the database of the said DNS; creating a data structure in the said GGSN, for storing the said APN and the said a plurality of MSISDN number, and in the data structure, retaining each of MSISDN numbers a storage space for storing the address of packet data protocol (PDP), so that the information stored in the said data structure identifies a newly created user group. The present invention provides a kind of new point-to-point data service with much attraction for the mobile data user.

Description

Method and device for implementing internet protocol multicast service in mobile communication system

The present invention relates to Internet Protocol (IP) multicast technology, and in particular, to a method and apparatus for providing IP multicast services in a mobile communication system. Background technique

In conventional mobile data networks, such as GPRS (General Packet Radio Service) and CDMA (Code Division Multiple Access) IX networks, mobile data users can only implement simple point-to-point services, and the services they can enjoy are therefore Restricted.

In the fixed IP network, IP multicast (IP Multicasting) services have many applications, but the IP multicast service based on IGMP (Internet Group Multicast Protocol) used in traditional fixed networks is used in mobile data networks. The operability is poor, so it is not applicable in mobile data networks and cannot be widely used.

Therefore, there is a need for a method and apparatus for providing IP multicast services in a mobile communication system. Summary of the invention

A first object of the present invention is to provide a method for providing an IP multicast service in a mobile communication system.

A second object of the present invention is to provide an apparatus for providing an IP multicast service in a mobile communication system.

To achieve the above first object, the present invention provides a method for implementing an Internet Protocol (IP) multicast service in a mobile communication system. The mobile communication system includes a General Packet Radio Service Gateway Support Node (GGSN) and a domain name server ( DNS), the method is characterized by including the following steps:

Receiving, by the GGSN, an access point name (APN) and multiple mobile station international integrated services digital network (MSISDN) numbers;

Generating the APN policy, and adding the APN feature information to the GGSN APN feature table; Adding a record including the II »address of the APN and the GGSN to the database of the DNS;

Establishing a data structure in the GGSN for storing the APN and the multiple MSISDN numbers, and reserving one for each of the MSISDN numbers in the data structure for storing a packet data protocol (PDP) ) Address storage space, so that the information stored in the data structure identifies a newly created user group.

In order to achieve the above second object, the present invention provides a network device used as a general packet wireless service gateway support node (GGSN) in a mobile communication system, which is characterized by including:

A device for receiving an access point name (APN) and multiple mobile station international integrated services digital network (MSISDN) numbers;

A device for generating a strategy of the APN and adding feature information of the APN to an APN feature table in the GGSN;

A device for instructing a domain name server (DNS) in the mobile communication system to add a record including the IP address of the APN and the GGSN to a database of the DNS;

And means for establishing a data structure in the GGSN, where the data structure is used to store the APN, the plurality of MSISDN numbers, and reserve one in the data structure for each of the MSISDN numbers A storage space for storing a packet data protocol (PDP) address, so that the information stored in the data structure identifies a newly established user group.

In order to achieve the above object, the present invention also provides a computer-readable program storage medium storing computer program code for instructing a general packet radio service gateway support node (GGSN) in a mobile communication system to perform operations. The program Storage media are characterized by:

A code device for receiving an access point name (APN) and multiple mobile station international integrated services digital network (MSISDN) numbers;

A means for generating the APN strategy and adding feature information of the APN to a code device in an APN feature table in the GGS;

Used to indicate that a domain name server (DNS) in the mobile communication system is in the DNS Adding a code device including a record of the APN and the IP address of the GGSN to the database;

A code device for establishing a data structure in the GGSN, where the data structure is used to store the APN, the multiple MSISDN numbers, and is reserved in the data structure for each of the MSISDN numbers A storage space for storing a packet data protocol (PDP) address, so that the information stored in the data structure identifies a newly established user group.

The method and device of the present invention adopt a powerful portal service platform in a general packet wireless service gateway support node (GGSN), a public data network (PDN), or a public data network (PDN) that supports multiple access point names (APN) and dynamic APN. The combination of the user management system in the mobile communication system provides a new class of very attractive point-to-multipoint data services for mobile data users.

According to the method and device of the present invention, many new services can be provided for mobile data users. A typical application of this type of new service is to implement a user group chat function between mobile data users similar to MSN or QQ provided by Microsoft (Microsoft) Corporation in a fixed IP network. In the present invention, such new services are referred to as mobile virtual data user group services. The mobile virtual data user group service will bring many new mobile data users to mobile operators, which is of great significance to mobile operators.

The present invention is applied in a public land mobile network (PLMN), regardless of how many GGSNs are configured in the network. Overview of the drawings

FIG. 1 is a schematic structural diagram of a mobile communication system in which the present invention is implemented;

FIG. 2 is a schematic flowchart of an operation of implementing an IP multicast service in a mobile communication system according to an embodiment of the present invention; FIG.

FIG. 3 is a schematic message flow diagram of a process of creating a user group in the embodiment shown in FIG. 2; FIG. 4 is a schematic diagram of an example of a data transmission process when an IP multicast service is implemented after the user group is created;

5 is a schematic message flow diagram of a user group deletion process initiated by a user; 6 is a schematic message flow diagram of a user group deletion process initiated by a GGSN; FIG. 7 is a schematic structural diagram of a network device used as a general packet wireless service gateway support node (GGSN) in a wireless communication system according to the present invention. DETAILED DESCRIPTION OF THE INVENTION

The following describes specific embodiments of the present invention with reference to the accompanying drawings.

FIG. 1 is a schematic structural diagram of a mobile communication system in which the present invention is implemented. As shown in FIG. 1, the mobile communication system includes three basic parts, namely a core network indicated by reference numeral 3, a universal mobile communication system (UMTS) terrestrial radio access network (UTRAN) indicated by reference numeral 4, and a user equipment indicated by reference numeral 5. .

The user equipment 5 may be, for example, a mobile phone with a subscriber identity module (USIM) in a Universal Mobile Telecommunications System (UMTS). Of course, in order to implement the present invention, the user equipment 5 needs to satisfy some conditions, which will be described later. The user equipment 5 is connected to the UMTS Terrestrial Radio Access Network (UTRAN) 4 through an air interface (for example, a wireless interface).

The UMTS Terrestrial Radio Access Network (UTRAN) 4 includes at least one Radio Network Controller (RNC) 141 (although only one is shown in the figure) and multiple nodes-B 142. Node-B 142 is used as a base station in the third generation mobile communication system, and communicates with multiple user equipments 5. Each wireless network controller 141 is connected to a corresponding plurality of nodes-B 142 through a ground line or a microwave, and controls the nodes-B 142 connected thereto. Therefore, in some networks, the wireless network controller 141 is also called a base station controller (BS). Each wireless network controller 141 is connected to the core network 3.

The core network 3 includes at least two domains, namely a circuit switched domain (CS domain) and a packet switched domain (PS domain). The radio network controller 141 assigns a message, or a call session, from the user equipment 5 to a circuit switched domain or a packet switched domain.

The circuit switched domain includes a mobile switching center / visit location register (MSC / VLR) 132, and a gateway mobile switching center (GMSC) 131. The mobile switching center (MSC) is responsible for all switching and signaling functions of the user equipment 5 within its jurisdiction. The visit location register (VLR) is a database that stores user preset data, related identification and user equipment location information. Mobile Switching Center / Visit Location Register (MSC VLR) 132 and GPRS services described below The support node (SGSN) 135 jointly performs mobility management.

The packet switching domain includes a GPRS Service Support Node (SGSN) 135 and a GPRS Gateway Support Node (GGSN) 134. Among them, GPRS refers to the general packet radio service.

The GPRS service support node (SGSN) 135 is equivalent to the mobile switching center / visit location register (MSC / VLR) in the traditional GSM system. Its main function is to perform authentication and mobility management on user equipment 5, perform routing selection, and establish users. The transmission channel from the device 5 to the GGSN 134 receives the data sent by the user equipment 5 from the UTRAN 4, performs protocol conversion, and transmits the data to the GGSN 134 through the GPRS backbone network (not shown), or works in the reverse direction and performs charging And business statistics.

When the GPRS is attached, the SGSN 135 establishes an MM (Mobility Management) context, which contains information related to the mobility and security of the user equipment 5. When PDP (Packet Data Protocol) context is active, 8081 135 and 008 ^^ 134 establish one? 0? Context, used for routing purposes.

The GPRS gateway supports a node (GGSN) 134, which is a node that accesses an external data network. To the external network, GGSN 134 is a sub-network router. The GGSN 134 receives the data sent by the user equipment 5, chooses to route to the corresponding external network, or receives the data from the external network, selects the transmission channel in the GPRS network according to its address, and transmits it to the corresponding SGSN 135.

Based on the point-to-point address analysis, the external packet data network accesses the GGSN 134. This address contains the routing information of the GPRS-attached user. This routing information is used to tunnel the PDU (packet data unit) to the current node of the user equipment 5, namely, the SGSN 135. GGSN 134 is the first entry point for public data network (PDN) 2 and core network 3 described below, which is the Gi reference point supported by GGSN 134.

Both the circuit switched domain and the packet switched domain are connected to a Home Location Register (HLR) 133. HLR 133 is a database that stores user preset data and routing information. For GPRS, HLR 133 also stores location information such as the SGSN number currently registered by user equipment 5, various identifications of mobile users, and information about services.

The GPRS gateway support node (GGSN) 134 is connected to the public data network (PDN) 2. The public data network (PDN) 2 may be the Internet, X.25 / X.75 and other networks. The public data network 2 shown in FIG. 1 is the Internet, which includes a portal 121 and a router 122. The gateway mobile switching center (GMSC) 131 is connected to a public switched telephone network / Integrated Services Digital Network (PSTN / ISDN) 1.

In order to implement the present invention, the components shown in FIG. 1 have the following requirements.

The user equipment 5 supports multiple access point names (APNs), that is, mobile users can use the user equipment 5 to set a new APN. A brief explanation of APN is given below.

In the core network 3, APN is a network name of an external packet data network, and corresponds to a physical interface or a serial interface in the GGSN 134. APN parameters represent the combination of application services provided by the mobile network to users. In order to roam between public land mobile networks (PLMN), the internal GPRS DNS (Domain Name System) function is needed to translate APN into the IP address of GGSN.

APN consists of two parts:

(1) APN network logo, which defines the external network to which the GGSN can connect, is assigned to the ISP by the network operator, and its uniqueness is guaranteed, which is equivalent to the domain name of the ISP;

(2) APN operator logo, which defines the PLMN GPRS backbone network where the GGSN is located, in the form "mnc <MNC> .mcc <MCO.gprs", which is used to mark the home network. Among them, MNC is a mobile network code, and MCC is a mobile country code.

The AP network identification is usually stored in the home location register (HLR) 133 as user subscription data. When initiating a packet service, the user can also provide the SGSN 135 with a decision to access the corresponding external network.

When a home public land mobile network (HPLMN) operator allows a user to access any network of the specified packet data protocol (PDP) type, the user's wildcard APN can be included in the home location register (HLR) 133, that is, a single "* ", Its length byte is 1. After the SGSN 135 receives the wildcard APN, when the PDP context is activated, it can choose the APN network flag received from the user equipment 5 or the default APN network flag to address the GGSN 134. That is, the user or the SGSN 135 can choose to access an APN that is not stored in the HLR 133.

The Domain Name System (DNS) is used by SGSN 135 and GGSN 134 to resolve APN. A domain name server (not shown) is used to provide 32-bit IP addresses and symbolic names. Mechanism for converting between, for example, www.chinamobile.com to 291.100.7.97.

The reason why DNS can complete this conversion function is because it has a database that contains the correspondence between IP addresses and symbolic names. When the local DNS cannot find the relevant data, it can access the upper-level DNS for query. There are currently 8 top-level DNS worldwide.

In addition to supporting multiple APNs, the user equipment 5 also needs to be installed with chat software or software with similar functions.

Because the mobile user can use the user equipment 5 to set the desired APN, the domain name system (DNS) is required to dynamically add or delete APN records.

GGSN 134 also needs to support multiple APNs and dynamic APNs to be able to dynamically update DNS. For example, GGSN 134 may be a MovingMedia WCDMA GGSN8000 product manufactured by UTStarcom.

It should be noted here that although MovingMedia WCDMA GGSN8000 produced by UTStarcom can be used as the GGSN in each embodiment of the present invention, the method and device of the present invention can also be used in GPRS / EDGE (Enhanced Data rates for Global Evolution, that is, Improved data rate GSM service), adopted in CDMA2000. That is, the type of mobile communication system does not constitute a limitation on the present invention.

The portal 121 communicates with the short message service center (SMSC) 6, so that the short message can be sent to the user equipment 5 through the short message service center (SMSC) 6.

In addition, the portal 121 and the GGSN 134 communicate using the Remote Authentication Dial-In User Service (RADIUS) protocol. RADIUS is used to control the access, authentication, and accounting of remote users who dial into a server to obtain network services. The RADIUS protocol is described, for example, in "RADIUS: Remote Authentication Dial-In User Service: Remote Network Access Security in an Open Systems Environment" at http: 〃 www.kmj.com/radius.html. The RADIUS protocol works below the application layer and is usually implemented in network devices in a way that is closely integrated with the functions implemented by the device. When using the RADIUS protocol for communication, the GGSN 134 acts as a RADIUS client and the portal 121 acts as a RADIUS server.

In the home location register (HLR) 133, a group of APNs need to be configured as "*" (that is, Wildcard APN) PDP context data, so that when the mobile user uses the newly created APN, the SGSN 135 addresses the GGSN 134 through the new APN.

FIG. 2 is a schematic flowchart of an operation of implementing an IP multicast service in a mobile communication system according to an embodiment of the present invention. The steps in Figure 2 are shown in four columns. The first column indicates the operations performed by the user equipment (initiating user equipment or invited user equipment). The second column shows the operations in the core network 3, especially in the GGSN 134. The third column indicates operations in the portal 121. The fourth column indicates operations in the short message service center 6.

As shown in FIG. 2, in step 201, an originating user equipment, such as an end user equipment in WCDMA, accesses portal 121 using a specific APN (that is, an APN corresponding to portal 121). This data access request arrives at the portal 121 in the public data network 2 via the GGSN 134 (equivalent to a router) and the router 122.

In step 202, the portal 121, in response to the received data access request, sends a user group creation web page to the initiating user device via the router 122 and the GGSN 134. The user group creation webpage is used to collect information necessary for creating a user group from the initiating user device, such as a new APN to identify the new user group, and the MSISDN number of the user device to invite to join the new user group. It should be noted here that the portal 121 may define a new APN for identifying a new user group without having to ask the originating user equipment.

The user group creation web page is pre-written and stored in the portal 121. User group web pages can be written using Hypertext Markup Language (HTML) or Wireless Markup Language (WML) or other applicable languages. Different webpage writing languages do not constitute a limitation on the present invention.

In step 203, the initiating user equipment receives a user group creation page. The user who initiated the user device clicks the hyperlink in the user group creation page, and enters the information required to create the user group step by step under the guidance of the page wizard. As described above, the information includes, for example, a new APN for identifying a new user group, an MSISDN number of a user equipment to be invited to join the new user group, and the like. The above information entered by the user is used as a parameter for creating a new user group.

The initiating communication between the user device and the portal 121 may use Hypertext Transfer Protocol (HTTP) or Wireless Access Protocol (WAP) or other applicable protocols. The communication protocol between the originating user equipment and the portal 121 does not constitute a limitation on the present invention.

In step 204, after the portal 201 has collected the parameters for creating a new user group, The portal sends parameters such as the new APN and the MSISDN numbers of all the user equipments to be invited to the GGSN 134 through the RADIUS interface, and waits for the GGSN 134 to respond. Here, the portal 121 functions as a RADIUS server.

In step 205, the GGSN 134, which is a RADIUS client, generates a specific policy for the new APN received for the new APN, and then adds feature information of the new APN to the APN feature table of the GGSN 134.

The AP feature table describes the attributes of all APNs supported by the GGSN. The attributes of each APN include, for example, the authentication method, IP address allocation method, and access method of the APN. The following table is an example of APN feature table in GGSN.

The specific content of the APN feature table does not constitute a limitation on the present invention.

In step 206, the GGSN 134 instructs the DNS to add a record in its domain name database that includes the new APN and the IP address of the GGSN 134.

In step 207, the GGSN 134 creates a virtual user group within the GGSN 134 based on all the received MSISDN numbers.

This creation process includes, for example, the following steps: Establish a data structure inside the GGSN to store the new APN and multiple MSISDN numbers received, and reserve one for each MSISDN number in the data structure for storing the PDP The storage space of the address and thus the information stored in the newly created data structure identifies the information of a newly created user group. This new user base is identified by the new APN. The data structure here can adopt various feasible structures, such as arrays, linked lists, trees, etc., or database tables. Different data structures do not constitute a limitation on the present invention.

In step 208, the GGSN 134 sends a response message to the portal 121 through the RADIUS interface, which is used to notify the portal 121 that a new user group has been successfully created.

In step 209, the portal 121 receives a response message from the GGSN 134, Initiate the user device to send a prompt that a new user group is created.

Then, in step 211, the portal 121 sends a notification of the new APN to the invited user equipment, for example, through the short message service center 6.

In step 210, after the initiating user equipment receives a prompt that the new user group is successfully created from the portal 121, it can disconnect from the portal 121 and access the new APN, that is, access the newly created user group.

In step 212, after receiving the instruction from the portal 121, the short message service center 6 sends a short message to the invited user equipment, and the content of the short message includes at least the APN used to identify the user group just created. APN.

In step 213, it is assumed that if thousands of invited user equipments receive the short message of the above content sent by the short message service center 6, and then access the APN of the new user group.

In step 214, in GGSN 134, for each user equipment accessing the new APN, the PDP context of the user equipment is activated, and the PDP address of the user equipment is stored in the data structure of the user group identified by the new APN. In the data structure of the user group, the PDP address is stored in a space reserved for the MSISDN number of the user equipment for storing the PDP address. GGSN 134 provides IP multicast services for multiple user equipments corresponding to these PDP addresses based on multiple PDP addresses stored in the data structure of the user group.

FIG. 3 is a message flow diagram of the process of creating a user group in the embodiment shown in FIG. 2. Figure 3 shows only one example. In order to implement the embodiment shown in FIG. 2, and especially to implement the embodiment shown in FIG. 2 in WCDMA, there may be multiple message flow modes.

As shown in FIG. 3, in step 301, a PDP context activation process of a user equipment is completed. In step 302, after completing the PDP context activation process of the user equipment, the GGSN 134 sends a RADIUS address notification message to the portal 121, that is, a RADIUS Addr Notification (MSISDN, GGSN IP address). The MSISDN number in the message is the MSISDN number of the user equipment that initiated the creation of the user group.

The various RADIUS messages described here and below are messages obtained by the inventor after extending RADIUS, and are sometimes referred to as RADIUS UTS extended messages.

The above RADIUS address notification message will notify the portal 121: the MSISDN number of the user equipment that initiated the creation of the new user group (also may carry the International Mobile Subscriber Identity (IMSI) letter Information), and the address of the corresponding RADIUS client on the GGSN 134 side.

In step 303, the portal 121 guides the user of the user equipment to complete the user group creation process, which may include verification of the identity of the user. At the same time, the user needs to be bound to the corresponding RADIUS client on the GGSN 134 side.

In step 304, the portal 121 transmits the information entered by the user to the GGSN 134 through a RADIUS add user group request message, that is, a RADIUS Add Group Request (APN, MSISDN1, MSISDN2 ...). The RADIUS add user group request message here is a reverse RADIUS UTS extended odd request message, which transmits the APN used to identify the new user group and the MSISDN number of each user in the new user group to the GGSN 134. After receiving this information, GGSN 134 will add APN, update DNS, and create a temporary user group. For example, a data structure is established for the new user group as described above with reference to FIG. 2.

In step 304, the GGSN 134 also returns a message indicating the success or failure of the creation to the portal 121, that is, a RADIUS Add Group Ack or a RADIUS Add Group Reject.

In step 305, the gate 121 sends an invitation short message to the invited user device through the short message service center 6.

Here, it should be noted that there are various ways to create a user group. It may be a fixed user accessing the portal 121 through a personal computer (PC) through the Internet instead of a wireless data network, and completing the process of creating a virtual user group. In this case, it is up to the portal 121 to decide which GGSN to use. It is also possible to create a virtual user group through a user management system (SAM, not shown) of the mobile communication system, which uses the same interface as the portal 121, that is, an interface based on the RADIUS protocol.

Secondly, the communication between the user equipment and the portal 121 may adopt multiple protocols. For example, in addition to HTTP, a wireless access protocol (WAP) can also be used.

In addition, there are multiple ways to invite users to join the user group. In addition to short message (SMS), the network defined in the 3G specification can also be used to initiate a PDP context activation process and push (PUSH) service to complete the user invitation process. The latter case would be a practical application of the network-initiated PDP context activation process.

The following describes the data transfer process for users in the successfully created user group. After the virtual user group is successfully created, for any IP data packet whose destination address is a user in the user group, the GGSN 134 will transmit the data packet to all other users in the user group in real time by using multiple copies. Data transmission is transparent to devices such as SGSN 135, UTRAN 4. Using the above data transmission process, IP multicast services are implemented for the created user groups.

Figure 4 is a diagram illustrating an example of a data transmission process when an IP multicast service is implemented after a user group is created. As shown in FIG. 4, in step 401, for an IP data packet whose destination address is any PDP address in the user group data structure, that is, for a data packet directed to any user in the user group, the GGSN 134 will The online status of the data, the data is copied in multiple copies, and the data is transmitted to the appropriate SGSN 135 according to the user PDP context information. The data packets copied here by the GGSN 134 and transmitted to the appropriate SGSN 135 are, for example, data between users in the user group or broadcast information to users in the user group. The copy and transfer process is shown in steps 401a to 401n in FIG. 4, for example.

In step 402, the SGSN 135 transmits the received data packet to the corresponding user equipment via the UTRAN 4, just like transmitting a normal data packet.

The replication and transmission of the data packets implemented through steps 401 and 402 are transparent to the SGSN 135, UTRAN 4 and user equipment (for example, user equipment 5).

The following describes the deletion process of the user group.

There are many ways to delete the user group. For example, a user who creates a user group deletes the user group by logging in to the door 121, under the guidance of the web page provided by the portal 121, or using the user management system of the mobile communication system to delete the user group through the same interface. The user group deletion process described above is called a user-initiated user group deletion process.

In addition, the GGSN 134 can also automatically delete a user group according to the activity status of the user group. For example, if a user in a user group is inactive for a configurable period of time (such as 1 hour), GGSN 134 will automatically initiate a user group deletion process.

FIG. 5 is a message flow diagram of a user group deletion process initiated by a user.

As shown in FIG. 5, in step 501, a PDP context activation process of a user equipment that initiates creation of a user group is completed.

In step 502, the portal 121 provides a web page to guide the user through the deletion process of the user group. In step 503, the portal 121 sends a RADIUS delete user group request to the GGSN 134, that is, a RADIUS UTS extended message RADIUS Delete Group Request (APN).

After the GGSN 134 receives the RADIUS user group deletion request, it deletes the APN, updates the DNS, and deletes the user group, including deleting the data structure of the user group. The GGSN 134 will then respond to the portal 121 with a message indicating that the deletion was successful or failed.

FIG. 6 is a message flow diagram of the user group deletion process initiated by the GGSN.

As shown in FIG. 6, after the user group is deleted by the GGSN 134, a RADIUS user group deletion notification is sent to the portal 121 in step 601, that is, a RADIUS UTS extended message RADIUS Group Delete Notification (APN). After receiving the RADIUS user group deletion notification, the portal 121 deletes the user group and the resources allocated for the user group on the portal 121. The resources allocated for the user group on the portal 121 may include storage resources allocated for storing user information of the user group, storage resources allocated for charging users of the user group, database resources, and the like.

The following describes the interface design between the GGSN 134 and the portal 121 or the user management system of the mobile communication system. The interface between the GGSN 134 and the portal 121 or the user management system is implemented by extending the RADIUS protocol. Added RADIUS message types include:

52 RADIUS Addr Notification

53 RADIUS Add Group Request

54 RADIUS Add Group Ack

55 RADIUS Add Group Reject

56 RADIUS Delete Group Request

57 RADIUS Delete Group Ack

58 RADIUS Delete Group Reject

59 RADIUS Group Delete Notification

Each of the above messages is described below.

(1) RADIUS Addr Notification

Calling format: RADIUS Addr Notification (MSISDN, GGSN IP address) Sender: RADIUS client located at GGSN

Receiver: RADIUS server on the portal

Function description: When the user initiates the creation of a user group, After the standby PDP context, the GGSN 134 sends a RADIUS address notification message to the portal 121, and notifies the portal 121 of the MSISDN number of the initiating user equipment and the IP address of the GGSN 134.

(2) RADIUS Add Group Request

Calling format: RADIUS Add Group Request (APN, MSISDN1, MSISDN2 ...)

Sender: RADIUS server on portal

Recipient: RADIUS client at GGSN

Function description: After establishing or receiving the APN of the new user group and receiving the MSISDN number of the user device to be invited from the initiating user device, the portal 121 sends a RADIUS add user group request message to the GGSN 134, and notifies the GGSN 134 of the new user group APN and the MSISDN number of each user equipment to be invited to join the new user group, such as MSISDN 1, MSISDN 2,… and so on.

(3) RADIUS Add Group Ack (add user group response)

Calling format: RADIUS Add Group Ack

Sender: RADIUS client at GGSN

Receiver: RADIUS server on the portal

Function description: After the GGSN 134 completes the creation of the user group, it sends a RADIUS Add User Group Response message to the portal 121, informing the portal 121 that the user group has been successfully created.

(4) RADIUS Add Group Reject

Calling format: RADIUS Add Group Reject

Sender: RADIUS client at GGSN

Receiver: RADIUS server on the portal

Function description: In the case that the user group cannot be successfully created, GGSN 134 sends a RADIUS add user group rejection message to the portal 121, notifying the portal 121 that the user group cannot be created.

(5) RADIUS Delete Group Request

Calling format: RADIUS Delete Group Request (APN)

Sender: RADIUS server on the portal Recipient: RADIUS client at GGSN

Function description: In the user group deletion process initiated by the user, the portal 121 sends a RADIUS delete user group request to the GGSN 134. The request specifies the identifier APN of the user group to be deleted.

(6) RADIUS Delete Group Ack

Calling format: RADIUS Delete Group Ack

Sender: RADIUS client at GGSN

Receiver: RADIUS server on the portal

Function description: After the GGSN 134 successfully deletes the user group, it sends a RADIUS delete user group response to the portal 121 to notify the user group that the user group has been deleted successfully.

(7) RADIUS Delete Group Reject

Calling format: RADIUS Delete Group Reject

Sender: RADIUS client at GGSN

Receiver: RADIUS server on the portal

Function description: When GGSN 134 cannot delete the user group successfully, it sends a RADIUS delete user group rejection to the portal 121, notifying that the user group cannot be deleted successfully.

(8) RADIUS Group Delete Notification (User Group Delete Notification) Call Format: RADIUS Group Delete Notification (APN)

Sender: RADIUS client at GGSN

Receiver: RADIUS server on the portal

Function description: In the user group deletion process initiated by GGSN, after GGSN 134 successfully deletes the user group identified by APN, it sends a RADIUS user group deletion notification to portal 121 to inform portal 121 that the user group identified by APN has been GGSN 134 deleted. Unified format. In the present invention, all messages contain only one attribute (Attribute), that is, the 26th type attribute in the RADIUS protocol-the vendor-specific attribute (Vendor-Specific). In each message, an information element (IE) is passed between the GGSN 134 and the portal 121 using a vendor-specific attribute. Therefore, specific encoding of vendor-specific attributes is required. In the present invention, this specific encoding is called UTS encoding. The following describes the RADIUS attributes, vendor-specific attributes, and UTS codes used in the present invention one by one as follows.

RADIUS attributes carry specific authentication, authorization, information, and configuration details for requests and responses. The end of the attribute list is determined by the length of the RADIUS packet. The format of the attributes is shown in Table 1.

Table 1: Format type length of RADIUS attributes

The type field is an octet. The value of the latest RADIUS type field is specified in the most recent "Assigned Numbers" RFC [6]. Values 192-223 are reserved for testing purposes, values 224-240 are reserved for specific use, and values 241-255 are reserved and should not be used. The RADIUS server can ignore attributes of unknown types. RADIUS clients can also ignore unknown types of attributes. In the present invention, only an attribute with a value of 26 is used, that is, a vendor-specific attribute (Vendor-Specific).

The length field is also an octet indicating the length of this attribute (including the type field, the length field, and the value field).

The range is zero or more octets and contains attribute-specific information. The format of the range is determined by the type field and the length field.

The following describes vendor-specific attributes. This attribute allows vendors to extend attributes to support their own attributes that are not suitable for general use. It cannot affect the operation of RADIUS. The format of vendor-specific attributes is shown in Table 2.

Table 2: Format of vendor-specific attributes

The value of the type field is 26.

The value of the length field is greater than or equal to 7.

The vendor ID is 4 octets. Among them, the value of the upper octet is 0, and the lower three octets are the manufacturer's network byte order SMI network management dedicated enterprise code. Vendor ID The values are defined in the "Assigned Numbers" RFC [6]. In the present invention, the value of the vendor ID field is 0422, which represents UTStarcom.

A string field is one or more octets. The allowed range of string domains is not specified in the RADIUS protocol. However, the string fields must be encoded in the order of fields such as vendor type / vendor length / attribute-specific values. The attribute-specific value is determined by the manufacturer's definition of the attribute. An example of encoding vendor-specific attributes using this method is shown in Table 3.

Table 3: Examples of encoding of string fields in vendor-specific attributes

The definitions of the type field, length field, and vendor ID field are the same as those in Table 2. The vendor type is defined as follows: (1) When the vendor type value is 1, it indicates that the attribute specific value is the MSISDN number; (2) When the vendor type value is 2, it indicates that the attribute specific value is the GGSN IP address, that is, the RADIUS client IP address;

(3) When the value of the vendor type is 3, it means that the attribute specific value is APN.

Vendor length can represent the total length of vendor type + vendor length + attribute specific value. The vendor length can also be defined as a length representing only a specific value of an attribute.

(1) The length of the MSISDN number. The encoding format of the MSISDN number fully complies with the standards of the 3rd Generation Partnership Project (3GPP), and uses the BCD code format, that is, the binary-decimal code format. Therefore, the length of the MSISDN code is fixed, and the length is, for example, eight octets.

( ² ) The length of the IP address of the GGSN. The IP address of the GGSN is a network byte order IP address code, and its length is four octets.

(3) APN is coded according to the format defined by the 3GPP specification, and its length is also fixed, and its length is, for example, sixteen octets.

The string fields shown in Table 2 may contain one or more combinations of vendor type / vendor length ^ / attribute specific values as shown in Table 3.

Taking the RADIUS Addr Notification message (MSISDN, GGSN IP address) as an example, the vendor-specific attributes are shown in Table 4, for example. Table 4: Examples of vendor-specific attributes for RADIUS address notification messages

FIG. 7 is a schematic structural diagram of a network device used as a general packet radio service gateway support node (GGSN) in a wireless communication system according to the present invention.

As shown in FIG. 7, the network device of the present invention includes a controller 700, which controls the work of main components, such as a DNS management device 701, an AP feature table management device 702, an IP multicast service implementation device 703, and a user group management device. 704. The user equipment activation device 705, the input / output device 706, and other components work. The APN feature table management device 702 is responsible for managing the APN feature table 707. The user group management device 704 is responsible for managing the user group data storage device 708.

When creating a user group, the input / output device 706 is used to receive an access point name (APN) and a plurality of mobile station international integrated services digital network (MSISDN) numbers from, for example, portal 121 or user management of a mobile communication system.

The APN feature table management device 702 is configured to generate a received APN policy and add the feature information of the APN to the APN feature table 707.

The DNS management device 701 is configured to instruct a domain name server (DNS) in the mobile communication system to add a record including the above-mentioned APN and the current GGSN IP address to the DNS database.

The user group management device 704 is configured to establish a data structure in the current GGSN. Such a data structure is stored in the user group data storage device 708, for example. The data structure is used to store the above APN and multiple MSISDN numbers, and a storage space for storing a packet data protocol (PDP) address is reserved for each MSISDN number in the data structure, so that the information identifier stored in the data structure is identified A newly created user base. The network device shown in FIG. 7 further includes a user equipment activation device 705 for activating a PDP context of a user equipment.

When the MSISDN number in the activated PDP context is the same as an MSISDN stored in the user group data structure stored in the user group data storage device 708, the controller 700 also controls the user group management device 704 to store the PDP address in the PDP context into The user group data structure is reserved in the storage space for storing the PDP address for the MSISDN number.

The IP multicast service implementation device 703 is configured to provide an IP multicast service for the current user group according to a plurality of PDP addresses stored in a data structure stored in the user group data storage device 708. The specific implementation process of the IP multicast service may be that when the destination address of an IP data packet is the same as a PDP address stored in the data structure of a user group, the IP multicast service implementation device 703 sends the IP data packet multiple times The copy mode is transmitted to other PDP addresses stored in the data structure in real time.

The user group management device 704 can also delete the data structure of a certain user group stored in the user group data storage device 708. This deletion operation may be initiated by a portal (for example, portal 121), or may be initiated by a user management system (not shown) of the mobile communication system. In addition, the controller 700 may also instruct the user group management device 704 to delete the data structure of the inactive user group from the user group data storage device 708 when a user in a user group is found to be inactive after a predetermined period of time.

The present invention also provides a computer-readable program storage medium on which computer program code for guiding operations of a General Packet Radio Service Gateway Support Node (GGSN) in a mobile communication system is stored. Such a program storage medium may be a magnetic disk, a magnetic tape, an optical disk, a magneto-optical disk, a read-only memory (ROM), an electrically programmable read-only memory (EPROM), and the like. The different forms of storage media do not constitute a limitation on the present invention.

The program storage medium provided by the present invention includes:

A code device for generating the above-mentioned APN strategy and adding the feature information of the APN into the APN feature table in the GGSN;

A database used to indicate the name server (DNS) in the mobile communication system in the DNS A code device including a record of the IP address of the APN and GGSN is added to the code device; a code device for establishing a data structure in the GGSN, the data structure is used to store the APN, the multiple MSISDN numbers, and In the data structure, a storage space for storing a packet data protocol (PDP) address is reserved for each of the above MSISDN numbers, so that the information stored in the data structure identifies a newly established user group.

The program storage medium of the present invention may further include:

A code means for activating a PDP context of a user equipment; when an MSISDN of the same is the same, the PDP address in the PDP context is stored in the above data structure in a storage space reserved for the above MSISDN number for storing the PDP address Code device

A code device for providing an IP multicast service for the newly-established user group according to the multiple PDP addresses stored in the data structure.

The program storage medium of the present invention may further include:

A code device for transmitting an IP data packet to other PDP addresses stored in the data structure in real-time in a manner of multiple copies when the destination address of an IP data packet is the same as a PDP address stored in the data structure.

The program storage medium of the present invention further includes:

Code means for deleting the above data structure in the GGSN.

In the program storage medium of the present invention, the code device for deleting the data structure in the GGSN is started by a portal.

In the program storage medium of the present invention, the code device for deleting a data structure in the GGSN is started by a user management system of a mobile communication system.

In the program storage medium of the present invention, the code device for deleting the data structure in the GGSN is automatically started by the GGSN when GGS finds that the users in the user group have no activity after a predetermined period of time.

Although the method and apparatus of the present invention have been described by way of example with reference to the accompanying drawings, the present invention is not limited to these details, and the present application covers various modifications or changes within the scope of the claims. Industrial applicability

The method, network device and program storage medium of the present invention can be applied to a general packet radio service / improved data rate GSM service (GPRS / EDGE) system, or a wideband code division multiple access (WCDMA) system, or a code division multiple access In the 2000 (CDMA2000) system, Internet protocol multicast services are provided for mobile users in related mobile communication systems.

Claims

Rights request

A method for implementing an Internet Protocol (IP) multicast service in a mobile communication system, the mobile communication system comprising a General Packet Radio Service Gateway Support Node (GGSN) and a Domain Name Server (DNS), the method is characterized by It includes the following steps:

Generating the APN strategy, and adding the APN feature information to the GGSN APN feature table;

Adding a record including the IP address of the APN and the GGSN to the database of the DNS;

Establishing a data structure in the GGSN for storing the APN and the plurality of MSISDN numbers, and reserving one for each of the MSISDN numbers in the data structure for storing a packet data protocol (PDP) ) Address storage space, so that the information stored in the data structure identifies a newly created user group.

2. The method according to claim 1, further comprising the following steps:

Sending the APN to multiple user equipments corresponding to the multiple MSISDN numbers.

3. The method according to claim 2, characterized in that said step of sending said APN to a plurality of user equipments corresponding to said plurality of MSISDN numbers is implemented by using a short message service.

4. The method according to claim 2, characterized in that the step of sending the APN to a plurality of user equipments corresponding to the plurality of MSISDN numbers is to activate and push a PDP context initiated by the mobile communication network ( PUSH) services.

5. The method according to claim 2, further comprising the following steps:

One of the plurality of user equipment requests access to the APN;

Activating a PDP context of the user equipment;

Storing, in the GGSN, the PDP address of the user equipment into a storage space reserved for storing the PDP address in the data structure for the MSISDN number of the user equipment; The GGSN provides an IP multicast service for the newly established user group according to a plurality of the PDP addresses stored in the data structure.

6. The method according to claim 5, further comprising the following steps:

When the destination address of an IP data packet is the same as a PDP address stored in the data structure, the GGSN transmits the IP data packet to the stored in the data structure in multiple copies in real time. Other PDP addresses.

7. The method according to claim 1, further comprising the following steps before the GGSN receives the APN and the plurality of MSISDN numbers:

An initiating user equipment accesses a portal in a public data network through the GGSN;

Creating, by the portal, the APN, and collecting the plurality of MSISDN numbers from the user equipment;

The portal sends the APN and the plurality of MSISDN numbers to the GGSN.

8. The method according to claim 1, further comprising the following steps before the GGSN receives the APN and the plurality of MSISDN numbers:

A personal computer accessing a portal in a public data network;

The portal creates the APN and receives the plurality of MSISDN numbers from the personal computer;

The portal selects a GGSN from the mobile communication network;

The portal sends the APN and the plurality of MSISDN numbers to the GGSN.

9. The method according to claim 1, further comprising the following steps before the GGSN receives the APN and the plurality of MSISDN numbers:

The user management system of the mobile communication system sends the APN and the plurality of MSISDN numbers to the GGSN.

10. The method according to any one of claims 7 to 9, characterized in that sending the APN and the plurality of MSISDN numbers to the GGSN is to dial in a user's service using remote access.

(RADIUS) protocol, where the GGSN acts as a RADIUS client.

11. The method according to claim 1, further comprising the following steps:

Delete the data structure in the GGSN.

12. The method according to claim 11, further comprising the following steps before deleting the data structure in the GGSN:

An initiating user equipment accesses a portal in a public data network through the GGSN, and requests to delete the user group;

The portal sends a message to the GGSN to delete the user group.

13. The method according to claim 11, further comprising the following steps before the deleting the data structure in the GGSN:

A personal computer accessing a portal in a public data network and requesting deletion of said user group;

The portal sends a message to the GGSN to delete the user group.

14. The method according to claim 11, further comprising the following steps before the deleting the data structure in the GGSN:

The user management system of the mobile communication system sends a message to the GGSN to delete the user group.

15. The method according to any one of claims 12 to 14, characterized in that the process of sending a message to the GGSN is performed using a RADIUS protocol, wherein the GGSN serves as a RADIUS client.

16. The method according to claim 11, wherein the step of deleting the data structure in the GGSN is performed when the GGSN finds that the users in the user group have no activity after a predetermined period of time. The GGSN is performed automatically.

17. The method according to claim 1, characterized in that said mobile communication system is a general packet radio service / improved data rate GSM service (GPRS / EDGE), wideband code division multiple access

(WCDMA), Code Division Multiple Access 2000 (CDMA2000) mobile communication system.

18. —A network device used as a general packet radio service gateway support node (GGSN) in a mobile communication system, which includes:

A strategy for generating the APN and adding characteristic information of the APN to the Device in APN feature table in GGSN;

19. The network device according to claim 18, further comprising:

Means for activating a PDP context of a user equipment;

For storing the PDP address in the PDP context in the data structure to pre-store the MSISDN number in a case where the MSISDN number in the activated PDP context is the same as an MSISDN stored in the data structure A device in a reserved storage space for storing a PDP address;

A device for providing an IP multicast service for the newly established user group according to a plurality of the PDP addresses stored in the data structure.

20. The network device according to claim 19, further comprising:

When the destination address of an IP data packet is the same as a PDP address stored in the data structure, the IP data packet is transmitted to the other stored in the data structure in multiple copies in real time. PDP address device.

21. The network device according to claim 18, further comprising:

'Means for deleting the data structure in the GGSN.

22. The network device according to claim 21, wherein: the means for deleting the data structure in the GGSN is activated by a portal.

23. The network device according to claim 21, wherein: the means for deleting the data structure in the GGSN is started by a user management system of the mobile communication system.

24. The network device according to claim 21, wherein: said means for deleting said data structure in said GGSN is found in said user group in said GGSN When the user has no activity after a predetermined period of time, the GGSN is automatically started.

25. The network device according to claim 18, characterized in that said mobile communication system is General Packet Radio Service / Improved Data Rate GSM Service (GPRS / EDGE), Wideband Code Division Multiple Access (WCDMA), Code Division Multiple Access 2000 ( CDMA2000) mobile communication system.

26. A computer-readable program storage medium storing computer program code for guiding operations of a General Packet Radio Service Gateway Support Node (GGSN) in a mobile communication system, the program storage medium being characterized by comprising:

A code device for generating the APN strategy and adding feature information of the APN to an APN feature table in the GGSN;

A code device for instructing a domain name server (DNS) in the mobile communication system to add a record including the IP address of the APN and the GGSN to a database of the DNS;

27. The program storage medium according to claim 26, further comprising:

Code means for activating a PDP context of a user equipment;

And for storing a PDP address in the PDP context in the data structure to pre-store the MSISDN number in a case where an MSISDN number in the activated PDP context is the same as an MSISDN stored in the data structure A code device in a reserved storage space for storing a PDP address;

A code device for providing an IP multicast service for the newly established user group according to a plurality of the PDP addresses stored in the data structure.

28. The program storage medium according to claim 27, further comprising: When the destination address of an IP data packet is the same as a PDP address stored in the data structure, the IP data packet is transmitted to the other stored in the data structure in multiple copies in real time. Code device for PDP address.

29. The program storage medium according to claim 26, further comprising:

Code means for deleting the data structure in the GGSN.

30. The program storage medium according to claim 29, wherein: said code means for deleting said data structure in said GGSN is started by a portal.

31. The program storage medium according to claim 29, wherein: the code means for deleting the data structure in the GGSN is started by a user management system of the mobile communication system.

32. The program storage medium according to claim 29, wherein: the code means for deleting the data structure in the GGSN is after the GGSN finds that a user in the user group has passed a predetermined period of time Automatically initiated by the GGSN in the absence of activity.