WO2009146618A1

WO2009146618A1 - Methods, device and systems for forwarding message to function entity which can be relocated in communication systems

Info

Publication number: WO2009146618A1
Application number: PCT/CN2009/071262
Authority: WO
Inventors: 张伟
Original assignee: 华为技术有限公司
Priority date: 2008-06-06
Filing date: 2009-04-14
Publication date: 2009-12-10
Also published as: CN101599912A; CN101599912B

Abstract

Methods, a device and systems for forwarding message to function entity which can be relocated in communication systems are provided, which makes the service request message be sent to the correct A-RACF entity in the scene of an A-RACF entity being relocated. The method includes the following steps. A PDF entity receives user's A-RACF information. The PDF entity receives service request message. The PDF entity forwards the service request message to corresponding A-RACF entity according to the A-RACF information. A method for forwarding message to function entity which can be relocated in communication systems is also provided. The method includes the following steps. An SPDF entity receives service request message. The service request message carries user's A-RACF information. The SPDF entity forwards the service request message to the corresponding A-RACF entity according to the A-RACF information.

Description

Method, device and system for forwarding messages to a migratable functional entity in a communication system

The present invention relates to the field of communications technologies, and in particular, to a method, device, and system for forwarding a message to a migratable functional entity in a communication system. Background technique

Worldwide Interoperability for Microwave Access (WMAX) is a wireless metropolitan area network technology based on the IEEE802.16 standard. WiMAX network wireless side is a wireless metropolitan area network access technology based on the IEEE802.16d/e standard, which adopts Orthogonal Frequency Division Multiplexing (OFDM) and OFDM access (OFDM Access, hereinafter referred to as: OFDMA)'s physical layer technology is effective against multipath fading. In the case of optimal channel fading, the transmission rate can approach 75 Mbps. The IEEE 802.16e in question has added technology to support simple mobile communication and full mobile communication.

Figure 1 is a schematic diagram of the structure of a WiMAX network in the prior art. The logical architecture of the WiMAX network is as shown in Figure 1. The WiMAX network consists of the following three parts:

(1) Terminal: It includes a Subscriber Station (hereinafter referred to as SS) or a Mobile Station (hereinafter referred to as MS), and the user uses the device to access the WiMAX network.

(2) Access service network: Access Service Network (ASN) is defined as a set of network functions that provide wireless access services for WiMAX terminals. The ASN includes a base station (Base Station, hereinafter referred to as BS) and an ASN Gateway (ASN Gateway, hereinafter referred to as: ASN-GW).

(3) Connection service network: The Connectivity Service Network (CSN) is defined as an IP connection service for WiMAX terminals. The CSN mainly includes a prepaid server (Prepaid Server, hereinafter referred to as PPS) and a logical entity such as Authentication, Authorization and Accounting (hereinafter referred to as AAA) server. The main functions provided are: MS IP address Assignment, Internet access, AAA proxy or server, terminal-based authorization control, etc.

In the prior art, the R1 interface in FIG. 1 is a wireless air interface, which is mainly defined by IEEE802.16d/e, R2 is a logical interface, and R3, R4, and R5 interfaces are all wired interfaces.

Figure 2 is a schematic diagram of the Quality of Service (QoS) framework in the STAGE2 baseline document of the 20060808 version of the WiMAX NWG in the prior art. As shown in Figure 2, the various functional entities in this framework are described as follows:

MS/SS is a user terminal;

The SFM is a Service Flow Management (hereinafter referred to as SFM), which is responsible for establishing a user service flow and allocating radio resources for the service flow. The function body exists in the ASN;

The SFA is a Service Flow Authorization (SFA), which is responsible for authorizing the corresponding service flow. This function exists in the ASN.

PF is a Policy Function (hereinafter referred to as PF), which provides a policy for a user service flow. This function exists in the NSP. In the roaming scenario, it will access the PF ( Visited PF) and the primary PF ( Home PF ) exists in both;

The AAA server is a system that provides authentication, authorization, and accounting services, and is responsible for preserving user QoS. Profile and related policy rules;

The AF entity is an application service function (Application Function, hereinafter referred to as AF) entity. The terminal directly accesses the AF entity through the application layer protocol. The AF entity will notify the PF to actively create a service flow for the user. This function exists in the NSP.

The Resource and Admission Control Subsystem (hereinafter referred to as RACS) was originally proposed for the fixed network, which isolates the application layer from the transport layer, shields the transport layer details for the application layer, and provides a common policy-based approach for the application layer. The bearer control mechanism enables value-added services to obtain network resources. Its main functions are: admission control, resource reservation, policy control, NAT/gating. Figure 3 is a schematic diagram of the basic functional architecture of the RACS of the TISPAN standard in the prior art. As shown in Figure 3, in the Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN) The RACS architecture clearly divides the bearer control function into two parts: the Session Policy Decision Function (SPDF) and the Access-Resource and Admission Control Function (A-). RACF).

The SPDF entity performs the NAT/NAT-PT conversion by interacting with the Core Border Gateway Function (C-BGF) according to the service attribute and policy configuration of the session, and indicates the media stream transmission to the C-BGF. Policy, requesting resource admission control from the A-RACF entity. The SPDF entity does not care about how the client accesses the network, but its control capabilities cover the entire access network (indirectly controlled by the A-RACF entity) and the Core Border Gateway (C-BGF).

The A-RACF entity accepts the resource reservation request from the SPDF entity, determines the legitimacy of the session resource according to the user QoS subscription information, and performs the admission control according to the session QoS parameter and the access network resource topology. The system generates a transmission policy according to the characteristics of the session QoS parameters, the characteristics of the access network (LAN, xDSL), and the bearer point (DSLAM, BRAS), and applies the policy to the bearer gateway resource control execution function entity (Resource Control Enforcement Function, hereinafter referred to as: RCEF).

The Network Attachment Sub-System (NASS) performs access authentication, address management, location management, and access subscription management.

In the RACS architecture, the access mode of the access network function entity is: the NASS informs the current user of the SPDF information of the AF entity through the e2 interface with the AF entity, and the AF entity sends the authorization request signaling to the SPDF through the Gq' interface. Entity, if the AF entity is not directly connected to the SPDF entity, the AF entity sends to its connected SPDF entity and is forwarded by the SPDF entity to the user-related SPDF entity; due to the characteristics of the fixed network, the SPDF entity is configured The A-RACF information of the user, the SPDF entity sends signaling to the A-RACF entity through the Rq interface.

With the requirements of network evolution and convergence, a unified architecture is required for policy and charging control of fixed networks and mobile networks. Therefore, policy and charging control (Policy and Charging Control) of TISPAN RACS and mobile networks is required. : PCC) The system is integrated to achieve unified policy control and charging control, providing a unified interface to the application layer.

FIG. 4 is a schematic diagram of a TISPAN RACS fusion WiMAX architecture in the prior art. In the architecture shown in Figure 4, the A-RACF entity is located on the ASN entity of WiMAX, the SPDF entity is located in the core network, and the NASS and AAA are integrated on the same functional module. The A-RACF entity in WiMAX is connected to the Local A-RACF entity through the Ha interface. In this architecture, the original RACS design can be reused to the greatest extent possible.

The inventors have found that in the prior art, the A-RACF entity is located above the ASN entity, and in the WiMAX NWG protocol, the ASN can be migrated. The existing RACS system is based on solid The design and consideration of the scene does not take into account the changes in the functional entities in the system caused by the movement of the user terminal. If the ASN is migrated, the A-RACF entity will migrate with it. The prior art architecture does not take into account the impact of A-RACF entity migration, resulting in the SPDF entity not being able to address the correct A-RACF entity after the A-RACF entity migration, the authorization performed by the original A-RACF entity The functions such as service establishment/modification/release cannot be performed normally, and the business process cannot be performed normally. Therefore, the way to maintain the A-RACF entity of the user by the SPDF entity is no longer feasible in the scenario where the ASN is migrated. Summary of the invention

The embodiment of the invention discloses a method for forwarding a message to a migratable functional entity in a communication system, including:

Policy distribution function The PDF entity receives the access network resource admission control function of the user A-RACF information;

The PDF entity receives the service request message;

The PDF entity forwards the service request message to the corresponding A-RACF entity based on the A-RACF information.

The service policy decision function SPDF entity receives the service request message, and the service request message carries the access network resource admission control function A-RACF information of the user;

The SPDF entity forwards the service request message to a corresponding A-RACF entity according to the A-RACF information. The embodiment of the invention discloses an apparatus for forwarding a message to a migratable functional entity in a communication system, and the structure thereof comprises:

The receiving module is configured to receive an access network resource admission control function of the user, the A-RACF information and the service request message;

And a sending module, configured to forward the service request message received by the receiving module to the corresponding A-RACF entity according to the A-RACF information.

The embodiment of the invention discloses a system for forwarding a message to a migratable functional entity in a communication system, including:

The network attachment subsystem NASS: configured to acquire the access network resource admission control function A-RACF information of the user, and send the A-RACF information to the policy distribution function PDF entity;

Service policy decision function SPDF entity: used to forward a service request message from an application service function AF entity to the PDF entity;

The PDF entity is configured to forward the service request message sent by the SPDF entity to the corresponding A-RACF entity according to the A-RACF information sent by the NASS.

Application service function AF entity: used to obtain the access network resource access control function A-RACF information from the network attachment subsystem NASS, and carry the information in the service request message and send it to the business policy decision function SPDF entity;

The SPDF entity: configured to forward the service request message to a corresponding A-RACF entity according to the A-RACF information. By applying the method, the device and the system disclosed in the embodiments of the present invention, in the scenario of A-RACF entity migration, the correct A-RACF entity can be addressed according to the new user A-RACF information, and the service request message is forwarded. The functions performed by the A-RACF entity and the functions of service establishment/modification/release are performed normally, and the business process is carried out normally.

DRAWINGS

1 is a schematic structural diagram of a WiMAX network in the prior art;

2 is a schematic diagram of a QoS framework in a STAGE2 baseline document of the 20060808 version of the WiMAX NWG in the prior art;

3 is a schematic diagram of a basic functional architecture of a TRAS in the prior art; FIG. 4 is a schematic diagram of a TISPAN RACS integrated WiMAX architecture in the prior art; FIG. 5a is a schematic diagram of a migration function in a communication system according to an embodiment of the present invention; A flow chart of a method for an entity to forward a message;

FIG. 5b is a flowchart of a method for forwarding a message to a migratable functional entity in a communication system according to an embodiment of the present invention;

6 is a flowchart of a method for forwarding a message to a migratable functional entity in a communication system according to an embodiment of the present invention;

FIG. 7 is a schematic structural diagram of an apparatus for forwarding a message to a migratable functional entity in a communication system according to an embodiment of the present disclosure;

FIG. 8 is a schematic structural diagram of a system for forwarding a message to a migratable functional entity in a communication system according to an embodiment of the present disclosure;

FIG. 9 is a message for forwarding a message to a migratable functional entity in a communication system according to an embodiment of the present invention; The system is schematic. detailed description

The embodiments of the present invention will be further described in detail below with reference to the accompanying drawings.

5a is a flowchart of a method for forwarding a message to a migratable functional entity in a communication system according to an embodiment of the present invention. As shown in FIG. 5a, a method for forwarding a message to a migratable functional entity in the communication system includes the following steps;

Step 101: The policy distribution function receives the user's access network resource admission control function A-RACF information;

Step 102: The PDF entity receives a service request message.

Step 103: The PDF entity forwards the service request message to the corresponding A-RACF entity according to the A-RACF information.

The technical solution of this embodiment adds a PDF entity to the network, and the PDF entity forwards the received service request message to the corresponding A-RACF entity according to the received A-RACF information. It can achieve the purpose of sending a service request message to the correct A-RACF entity when the A-RACF entity migrates. The functions performed by the A-RACF entity and the functions of service establishment/modification/release are performed normally, and the business process is carried out normally.

FIG. 5b is a flowchart of a method for forwarding a message to a migratable functional entity in a communication system according to an embodiment of the present invention.

As shown in Figure 5b, the following A-RACF entity is used as a migratable functional entity, and A-RACF The technical solution of this embodiment is to add a Policy Distribution Function (hereinafter referred to as PDF) entity to the network, and the PDF entity is located at the communication peer end of the Rq interface of the SPDF entity. The PDF obtains the user's A-RACF information from the NASS and maintains it by itself. The SPDF entity treats the PDF as an A-RACF entity for information interaction, and sends a service request message to the PDF. The PDF forwards the service request message sent by the SPDF entity to the A-RACF entity. Specific steps are as follows:

Step 501: The user terminal accesses the WiMAX network through the ASN through the access authentication process, and the AAA obtains the information (domain name, identifier, and/or address) of the user-related A-RACF entity in the process of the user terminal accessing the network. Since NASS and AAA are integrated on the same functional module, NASS can also share the A-RACF information in real time.

Step 502: The NASS sends the user subscription information to the network access server (Network Access Server, hereinafter referred to as NAS).

Step 503: The NASS sends the A-RACF information of the user to the PDF, including the A-RACF entity domain name, the identifier, and/or the address. The A-RACF information is the A-RACF information acquired by the NASS in step 501. The PDF maintains the A-RACF information.

The above steps 501 to 503 are processes for obtaining the A-RACF information of the user in the PDF during the initial network access phase of the user.

Step 504: When the user initiates a new service, the AF entity sends a service request message to the user in the future to the SPDF entity where the user is located. The information of the SPDF entity in which the user is located is obtained from the NASS by the AF entity through the e2 interface defined in the TISPAN RACS. This process is similar to the prior art and will not be described here.

Step 505: The SPDF entity sends a service request message to the corresponding PDF. SPDF entity root The PDF is addressed according to the access type requested by the service. The addressing mode used by SPDF entities when addressing PDFs is similar to the prior art. In the prior art, the SPDF entity directly addresses the A-RACF entity using the addressing mode. In the technical solution of the embodiment, since the PDF masks the A-RACF entity to the SPDF entity, the SPDF entity uses the addressing mode to address the PDF, and the implementation process is similar to the prior art, and details are not described herein. .

Step 506: The PDF forwards the service request message to the A-RACF entity according to the A-RACF information it maintains.

The foregoing steps 504 to 506 are processes in which the user initiates a new service request and forwards the service request message to the corresponding A-RACF entity through the PDF in a scenario where the A-RACF entity is fixed. The A-RACF entity authorizes the service according to the user subscription information obtained in step 502, that is, the authorization process of FIG. After the service authorization succeeds, the user needs to establish a required service flow bearer, and the user uses the bearer to enjoy the service.

In some scenarios, the user's A-RACF entity may be triggered to migrate. For example, when the A-RACF entity is located in the Authenticator in the ASN, the Authenticator migration occurs during the re-authentication process during the user roaming process, which causes the A-RACF entity to perform the corresponding migration. In this embodiment, the re-authentication trigger A-RACF entity migration is taken as an example to describe a method for forwarding a message to the A-RACF entity migration scenario.

Step 507: In the re-authentication process, the user performs authentication by interacting with the AAA through the new Authenticator, and the Authenticator migration occurs after the authentication succeeds, triggering the A-RACF entity migration. Since NASS and AAA are integrated on the same functional module, NASS also obtains a new A-RACF entity (New A-RACF entity M message (domain name, identity and/or address) related to the user in the process of re-authentication. The original A-RACF entity (Old A-RACF entity) signs the user obtained in step 502. The information is moved to the new A-RACF entity (New A-RACF entity) along with the migration of the A-RACF entity.

Step 508: The NASS sends signaling according to the new A-RACF information obtained in step 507 to update the user A-RACF information maintained in the PDF. To ensure that the PDF can be addressed to the correct A-RACF entity in subsequent business processes.

The above steps 507 to 508 are processes for the PDF to update the A-RACF information maintained by the A-RACF entity in the scenario of migration.

It should be noted that the PDF is a new functional entity in the network, and its location is not limited, and may be located in an SPDF entity or other physical entity, or may exist independently.

The technical solution of this embodiment adds a PDF entity to the network, and the PDF entity is located at the communication peer end of the Rq interface of the SPDF entity. The PDF obtains the user's A-RACF information from NASS/AAA and maintains it by itself. The SPDF entity treats the PDF as an A-RACF entity for information interaction, and sends a service request message to the PDF. The PDF forwards the service request message sent by the SPDF entity to the A-RACF entity. The technical solution of this embodiment shields the movement of the A-RACF entity from the PDF entity to the SPDF entity, and realizes the purpose of the SPDF entity sending the service request message to the correct A-RACF entity when the A-RACF entity is migrated. The authorization performed by the A-RACF entity and the functions of service establishment/modification/release are performed normally, and the business process is performed normally.

FIG. 6 is a flowchart of a method for forwarding a message to a migratable functional entity in a communication system according to an embodiment of the present invention.

As shown in FIG. 6, the A-RACF entity is a functional entity that can be migrated. This embodiment is another processing method in the scenario of A-RACF entity migration. This embodiment describes the method by taking the NAS where the A-RACF entity is located in the ASN entity as an example. The technical solution of this embodiment is: extending the e2 interface, so that when the NASS communicates with the AF entity, in addition to interacting with the SPDF information, the interactive A-RACF information is also added. The original SPDF entity in the network acts as an addressing/forwarding function entity, and the SPDF entity is changed to address the A-RACF entity, and the A-RACF entity is addressed according to the access network type in the prior art, and is changed to Gq according to the GQ. The A-RACF information specified in the A-RACF entity is addressed. In the re-authentication scenario, after re-authentication, NASS updates the user's NAS/A-RACF information and interacts with the AF entity through the e2 interface. The specific steps are as follows: The user accesses the WiMAX network through the ASN through the access authentication process, and the NASS obtains the NAS information related to the user. Since the A-RACF entity is located on the NAS, the NASS can also obtain the user's new A-RACF information (domain name, Identification and / or address). The NASS maintains user-related SPDF information and the A-RACF information.

Step 601: When the service establishment or deletion or modification is initiated, the AF entity sends a location information request message to the NASS through the e2 interface, requesting the user location information.

Step 602: The NASS sends a location information response message to the AF entity by using the e2 interface, where the location information response message carries the user-related SPDF information, and also carries the current A-RACF information (domain name, identifier, and/or address) of the user. .

Step 603: The AF entity sends a service request message to the SPDF entity, where the service request message carries the A-RACF information in step 602.

Step 604: The SPDF entity addresses the corresponding A-RACF entity according to the A-RACF information in step 603, sends a service request message to the A-RACF entity, and starts the 4 authorization process.

The foregoing steps 601 to 604 are processes in which the user initiates a new service request and obtains a service authorization by forwarding the SPDF entity in a scenario where the A-RACF entity is fixed. After business 4 is authorized, The user is required to establish a required service flow bearer, and the user uses the bearer to enjoy the service.

In some scenarios, the user's A-RACF entity may be triggered to migrate. For example, when the A-RACF entity is located in the NAS in the ASN, the NAS migration occurs during the re-authentication process of the user roaming process, and the A-RACF entity also performs the corresponding migration. In this embodiment, the re-authentication triggers the A-RACF entity migration as an example to describe the processing in the A-RACF entity migration scenario.

During the re-authentication process, the A-RACF entity migrates. Since NASS and AAA are integrated on the same functional module, NASS obtains new NAS information related to the user in the process of re-authentication. Since the A-RACF entity is located on the NAS, NASS can also obtain new A-RACF information of the user ( Domain name, logo and/or address).

Step 605: The NASS actively sends a location information response message to the AF entity according to the new A-RACF information obtained in the re-authentication process, where the response message carries the user's new SPDF information and A-RACF information. The AF entity updates its saved user-related SPDF information, A-RACF information.

The above step 605 is a process of updating the A-RACF information in the AF entity in the scenario where the A-RACF entity migrates. This step applies to modifications or releases to existing services. When the AF entity needs to actively trigger the modification or release of the service, it uses the updated SPDF information to interact with the SPDF entity and sends the new A-RACF information to the SPDF entity, and the SPDF entity addresses the correct according to the new A-RACF information. A-RACF entity. For the newly initiated service request, the NASS may also perform the step of step 605, and send the new A-RACF information after the A-RACF entity is migrated to the AF entity by interacting with the AF entity in steps 601 and 602. The new A-RACF information is forwarded by the AF entity to the SPDF entity, and the SPDF entity directly addresses the correct A-RACF entity based on the new A-RACF information. The process is similar to steps 601 through 604.

The technical solution of this embodiment extends the e2 interface, so that when the NASS communicates with the AF entity, In addition to the mutual SPDF information, interactive A-RACF information is also added. The manner in which the SPDF entity addresses the A-RACF entity is changed, from the prior art addressing the A-RACF entity according to the access network type, to the A-RACF entity addressing according to the A-RACF information specified by the AF entity. The SPDF entity is configured to address the A-RACF entity through the user's real-time A-RACF information, so that the SPDF entity can also send the service request message to the correct A-RACF entity when the A-RACF entity is migrated, so that A-RACF is enabled by A-RACF. The authorization of the entity execution and the functions such as service establishment or modification or release are performed normally, and the business process is performed normally.

FIG. 7 is a schematic structural diagram of an apparatus for forwarding a message to a migratable functional entity in a communication system according to an embodiment of the present invention.

As shown in FIG. 7, the embodiment discloses a device for forwarding a message to a migratable functional entity in a communication system, and the structure thereof includes:

The receiving module 11 is configured to receive A-RACF information and a service request message of the user;

The sending module 13 is configured to forward the service request message received by the receiving module 11 to the corresponding A-RACF entity according to the A-RACF information.

The device for assisting the migration of the functional entity in the communication system may further include:

The maintenance module 15 is connected to the receiving module 11 and the sending module 13 respectively for maintaining the A-RACF information of the user received by the receiving module 11, and providing the A-RACF information to the sending module 13.

The device for forwarding a message to the migratable functional entity in the communication system disclosed in this embodiment can receive the A-RACF information, and after receiving the service request message, forward the the A-RACF entity to the corresponding A-RACF entity according to the A-RACF information. Business request message. In the scenario of A-RACF entity migration, the device receives the user's new A-RACF information through the receiving module, and when the service request message is received, the user can be addressed to the correct A-RACF information by the user. A-RACF entity, the industry will be The request message is forwarded to the correct A-RACF entity. The functions performed by the A-RACF entity and the functions of service establishment/modification/release are performed normally, and the business process is performed normally.

FIG. 8 is a schematic structural diagram of a system for forwarding a message to a migratable functional entity in a communication system according to an embodiment of the present invention.

As shown in FIG. 8, the embodiment of the present invention discloses a system for forwarding a message to a migratable functional entity in a communication system, including:

NASS21: used to obtain the current A-RACF information of the user, and send the A-RACF information to the PDF;

SPDF entity 23: for forwarding a service request message from the AF entity to the PDF entity 25; PDF entity 25: for forwarding the service request message sent by the SPDF entity 23 to the corresponding A-RACF entity according to the A-RACF information sent by the NASS 21 .

The system for forwarding a message to a migratable functional entity in the communication system disclosed in the embodiment of the present invention addresses the A-RACF entity according to the A-RACF information, and sends a service request message to the A-RACF entity. In the scenario of A-RACF entity migration, the system can locate the correct A-RACF entity according to the new user A-RACF information, and complete the forwarding of the service request message. The authorization performed by the A-RACF entity and the functions of service establishment/modification/release are performed normally, and the business process is performed normally.

FIG. 9 is a schematic structural diagram of a system for forwarding a message to a migratable functional entity in a communication system according to an embodiment of the present invention.

As shown in FIG. 9, the embodiment of the present invention discloses a system for forwarding a message to a migratable functional entity in a communication system, including:

AF entity 27: used to obtain A-RACF information from NASS and carry the information in the industry The request message is sent to the SPDF entity 23;

SPDF entity 23: for forwarding the service request message to the corresponding A-RACF entity according to the A-RACF information.

By applying the method, the device and the system disclosed in the embodiments of the present invention, in the scenario of A-RACF entity migration, the correct A-RACF entity can be addressed according to the new user A-RACF information, and the service request message is forwarded. The authorization performed by the A-RACF entity and the functions such as service establishment or modification or release are performed normally, and the business process is performed normally.

The above embodiments are only used to illustrate the technical solutions of the present invention, and are not intended to be limiting; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that The technical solutions are described as being modified, or equivalents are replaced by some of the technical features; and such modifications or substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

Rights request

A method for forwarding a message to a migratable functional entity in a communication system, comprising:

The PDF entity receives the service request message;

2. The method of forwarding a message to a migratable functional entity in a communication system according to claim 1, wherein the receiving, by the PDF entity, the A-RACF information of the user comprises:

The PDF entity receives the network attachment subsystem NASS/Authentication, Authorization, and Accounting A-RACF information sent by the AAA server;

The receiving, by the PDF entity, the service request message includes:

The PDF entity receives a service request message sent by the SPDF entity.

3. The method of forwarding a message to a migratable functional entity in a communication system according to claim 1, wherein the PDF entity is located in an independent physical entity or is located in the same physical entity as the SPDF entity.

4. A method of forwarding a message to a migratable functional entity in a communication system according to claim 2, wherein said PDF entity establishes communication with said SPDF entity via an Rq interface.

The method for forwarding a message to a migratable functional entity in a communication system according to claim 2, wherein after the A-RACF entity is migrated, the NASS actively sends the migrated to the PDF entity. User's A-RACF information; for the service request message received thereafter, PDF The entity forwards according to the new A-RACF information.

The SPDF entity forwards the service request message to a corresponding A-RACF entity according to the A-RACF information.

The method for forwarding a message to a migratable functional entity in a communication system according to claim 6, wherein the SPDF entity receiving the service request message is specifically: the SPDF entity receiving the application service function AF entity Business request message

Before the SPDF entity receives the service request message, the method further includes: the AF entity sending a location information request message to the network attachment subsystem NASS; the NASS sending a location information response message to the AF entity, where the response message carries a user A-RACF information.

The method for forwarding a message to a migratable functional entity in a communication system according to claim 6, wherein the SPDF entity receiving the service request message is specifically: the SPDF entity receiving a service request message sent by the AF entity ;

If the A-RACF entity is migrated, the network attachment subsystem NASS sends a location information response message to the application service function AF entity, where the response message carries the A-RACF information of the user after the A-RACF entity migration.

A device for forwarding a message to a migratable functional entity in a communication system, comprising:

Receiving module: receiving access network resource admission control function A-RACF information and service of the user Request message

The apparatus for forwarding a message to a migratable functional entity in a communication system according to claim 9, further comprising:

The maintenance module is connected to the receiving module and the sending module respectively, and is configured to maintain A-RACF information of the user received by the receiving module, and provide the A-RACF information to the sending module.

A system for forwarding a message to a migratable functional entity in a communication system, comprising:

12. A system for forwarding a message to a migratable functional entity in a communication system, comprising:

The SPDF entity: configured to forward the service request message to a corresponding A-RACF entity according to the A-RACF information.