WO2008092346A1 - Procédé, système et appareil pour l'établissement d'un support de signalisation - Google Patents

Procédé, système et appareil pour l'établissement d'un support de signalisation Download PDF

Info

Publication number
WO2008092346A1
WO2008092346A1 PCT/CN2007/070841 CN2007070841W WO2008092346A1 WO 2008092346 A1 WO2008092346 A1 WO 2008092346A1 CN 2007070841 W CN2007070841 W CN 2007070841W WO 2008092346 A1 WO2008092346 A1 WO 2008092346A1
Authority
WO
WIPO (PCT)
Prior art keywords
bearer
message
ims
identifier
entity
Prior art date
Application number
PCT/CN2007/070841
Other languages
English (en)
Chinese (zh)
Inventor
Anning Xie
Weimin Chen
Junxian Mo
Jiaxing Xiao
Original Assignee
Huawei Technologies Co., Ltd.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Publication of WO2008092346A1 publication Critical patent/WO2008092346A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1069—Session establishment or de-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/1016—IP multimedia subsystem [IMS]

Definitions

  • the present invention relates to mobile communication technologies, and in particular, to a signaling bearer establishment method, system and apparatus. Background of the invention
  • IP Internet Protocol
  • IMS Internet Multimedia Subsystem
  • FIG. 1 is a schematic structural diagram of a WiMAX system in the prior art.
  • the WiMAX system mainly includes a mobile terminal (MS), an Access Service Network (ASN), and a Connectivity Service Network (CSN).
  • the ASN mainly includes a base station (BS) and an access service network gateway (ASN-GW);
  • the CSN mainly includes a prepaid server (PPS) and authentication, authentication, and accounting. (Authentication Authorization Accounting, AAA)
  • the server Server
  • other functional entities mainly includes a WiMAX system in the prior art.
  • the WiMAX system mainly includes a mobile terminal (MS), an Access Service Network (ASN), and a Connectivity Service Network (CSN).
  • the ASN mainly includes a base station (BS) and an access service network gateway (ASN-GW);
  • the CSN mainly includes a prepaid server (PPS) and authentication, authentication, and accounting. (Authentication Authorization Accounting, AAA)
  • AAA Authentication Authorization Accounting
  • FIG. 2 is a schematic structural diagram of a WiMAX system that provides Quality of Service (QoS) in the prior art.
  • QoS Quality of Service
  • NSG WiMAX Network Work Group
  • the MS is the user's mobile terminal, and the user interacts with the network through the MS;
  • the service flow management entity Service in the ASN
  • SFM Flow Manager
  • SFA Service Flow Authorization
  • SFA Service Flow Authorization
  • SFA Service Flow Authorization
  • SFA Serving SFA
  • SFA Anchor SFA
  • Anchor SFA Anchor SFA
  • the Policy Function (PF) provided by the Network Service Provider (NSP) is used to provide policies for the user's service flow.
  • the PF is divided into the visited PF (Visited PF). (V-PF) and the home network PF (Home PF, H-PF); the Application Function (AF) provided by the NSP, the user's MS directly accesses the AF through the application layer protocol connection, and the AF will notify the PF to actively The user creates a business flow.
  • V-PF visited PF
  • Home PF, H-PF home network PF
  • AF Application Function
  • FIG. 3 is a schematic structural diagram of a WiMAX system for providing charging in the prior art.
  • the MS is equivalent to the user in the charging, and the accounting client is used to collect all the charging information and provide it to the AAA server;
  • AAA Proxy is an optional intermediate device. After receiving the received accounting packets, it generates a new accounting packet and forwards it to the local AAA Server or the AAA Server.
  • AAA Server etc.;
  • the local AAA server is the home AAA server, that is, the AAA server that is initially registered by the user or the AAA server of the user's home.
  • the local AAA server stores the user's subscription information, including the charging policy, and the user's charging processing. It is mainly implemented in the local AAA Server.
  • the AAA Server is the AAA Server of the user's visited place. It is used to record, transparently transmit and forward the charging information when the user roams.
  • the system can control and bill directly or through policies.
  • the basic functional architecture of the PCC includes: AF, which provides service information for related decisions; and a subscription profile storage entity (SPR), which is mainly used to save real-time information.
  • AF which provides service information for related decisions
  • SPR subscription profile storage entity
  • User and contracting policy Policy and Charging Enforce Function (PCRF), used to formulate rules
  • PCEF Policy and Charging Enforce Function
  • PCEF Policy and Charging Enforce Function
  • GW Gateway (Gateway) GW)
  • OCS Online Charging System
  • OFCS Offline Charging System
  • Figure (5a ⁇ 5d) is a schematic diagram of the structure of the existing WiMAX-IMS system.
  • Figure 5a shows the structure of a WiMAX-IMS (WiMAX Stand alone) system using a non-PCC architecture.
  • the system maintains the existing WiMAX Qos architecture unchanged, except that the PF needs to support the modification of the interface Rx.
  • Figure 5b shows the structure of a WiMAX-IMS (WiMAX Stand alone) system using PCC architecture.
  • the system supports the convergence of the PCC architecture, but the existing PCC architecture has been modified. The key point is that the R3-PCC interface supports mobility.
  • FIG 5c is a block diagram of a WiMAX-IMS (WiMAX Stand alone) system using a PCC architecture with a Gx proxy (Agent/Proxy).
  • the system supports the convergence of the PCC architecture, and there is no change to the existing PCC architecture.
  • the key to the change lies in the R3-PCC interface between the SFA and the Agent/Proxy.
  • the system shields the SFA through the Agent/Proxy.
  • the mobility shifts the changes in the PCC architecture into changes to the WiMAX internal interface, thereby circumventing PCC changes.
  • Figure 5d is a system structure diagram of WiMAX-3GPP-IMS (WiMAX-3GPP Interworking).
  • the PCRF in the system is provided by the 3GPP Core.
  • the system also introduces Agent/Proxy to shield the mobility of the SFA and avoid the changes of the existing PCC architecture.
  • Agent/Proxy lies in the Agent/Proxy and R3-PCC architecture. achieve.
  • the related functional units such as SFA, Agent/Proxy can be regarded as a complete PCEF, and the architecture of the WiMAX-IMS fusion can be ensured that the architecture is based on PCC.
  • existing mobile communication systems similar to those introduced with IMS can implement different services in the system, but do not establish dedicated services or signaling bearers for various services, such as IMS service, WIMAX multicast broadcast (WIMAX MBS). Service, WIMAX location service (WIMAX LCS), etc., so that the establishment process of the service is slow, and the efficiency of the service implementation is not high. Summary of the invention
  • the present invention provides a signaling bearer establishment method, which can speed up the service establishment process.
  • the present invention provides a signaling bearer establishment system, which can speed up the service establishment process.
  • the invention provides a signaling bearer establishing device, which can speed up the service establishment process.
  • a signaling bearer establishing method includes: sending a message, where the message carries an identifier indicating that the signaling dedicated bearer is established; and the identifier indicating that the signaling dedicated bearer is established is used by the terminal and the network side to establish a signaling dedicated bearer.
  • a signaling bearer establishment system includes: a first network element and a second network element,
  • the first network element is configured to send, to the second network element, a message for establishing a dedicated bearer, where the message carries an identifier indicating that the signaling bearer is established.
  • a signaling bearer establishing device comprising: a transceiver unit and a message generating unit; the transceiver unit is configured to generate a message carrying an identifier indicating that the signaling dedicated bearer is established, and provide the generated message to the transceiver unit;
  • the transceiver unit is configured to send a message from the message generating unit to the outside. It can be seen that the embodiment of the present invention shortens the time required for the service establishment process of services such as the IMS service and the WIMAX MBS service by establishing a dedicated bearer for transmitting a certain signaling, thereby improving the efficiency of the implementation; In the technical solution of the embodiment of the present invention, any entity in the terminal and the network side may initiate the establishment of the bearer, thereby making the present invention
  • the technical solution of the implementation method is applicable to various scenarios and has high versatility. BRIEF DESCRIPTION OF THE DRAWINGS
  • FIG. 1 is a schematic structural diagram of a WiMAX system in the prior art
  • FIG. 2 is a schematic structural diagram of a WiMAX system providing QoS in the prior art
  • FIG. 3 is a schematic structural diagram of a WiMAX system providing charging in the prior art
  • FIG. 4 is a schematic diagram of a PCC architecture in the prior art
  • Figure (5a ⁇ 5d) is a schematic structural diagram of an existing WiMAX-IMS system
  • FIG. 6 is a structural diagram of a system for establishing a signal in an embodiment of the present invention.
  • FIG. 7 is a flowchart of a signaling bearer establishing method 1 according to an embodiment of the present invention
  • FIG. 8 is a flowchart of a signaling bearer establishing method 2 according to an embodiment of the present invention
  • FIG. 9 is a signaling bearer establishing method 3 according to an embodiment of the present invention
  • FIG. 10 is a flowchart of a signaling bearer establishing method 4 according to an embodiment of the present invention
  • FIG. 11 is a flowchart of a signaling bearer establishing method 5 according to an embodiment of the present invention
  • FIG. 13 is a flowchart of a signaling bearer establishing method 7 according to an embodiment of the present invention
  • FIG. 14 is a flowchart of a signaling bearer establishing method 8 according to an embodiment of the present invention.
  • any entity in the network initiates a dedicated service bearer/signaling bearer of a certain service by sending a request or a trigger event in the network, for example, Layer layer signaling, or Internet Protocol (IP) layer signaling, or session layer signaling, or Medium Access Control (MAC) layer signaling bearer, or transport layer signaling
  • IP Internet Protocol
  • MAC Medium Access Control
  • the network entity is triggered to establish, for example, an application layer bearer, or an IP layer signaling bearer, or a session layer signaling bearer, or a MAC layer signaling bearer, or a transport corresponding to the identifier.
  • Layer signaling bearer or physical layer signaling bearer.
  • the existing bearer needs to be changed to, for example, an application layer signaling bearer, or an IP layer signaling bearer, or a session layer signaling bearer, or a MAC layer signaling bearer, or a transport layer signaling bearer, or a physical layer
  • a dedicated bearer such as a signaling bearer can also be processed according to the above basic idea
  • the application layer signaling bearer can be a dedicated bearer for IMS signaling, or can be a dedicated bearer for WIMAX MBS service or a dedicated bearer for WIMAX MBS signaling. Wait.
  • the system for establishing a signaling bearer in the embodiment of the present invention includes: a terminal and a network side, where the network side includes a decision entity.
  • the decision entity in the network side determines whether the identifier can be established for the terminal or the corresponding event of the trigger event according to a trigger event or a received request indicating that a certain dedicated identifier is established. If the decision is successful, Then, the terminal establishes the identifier or the bearer corresponding to the triggering event, that is, triggers the corresponding network entity to establish the bearer corresponding to the identifier, and sends an indication that carries the identifier indicating the bearer type, indicating that the bearer or request corresponding to the identifier is successfully established. Other functional entities establish bearers corresponding to the identifier.
  • the decision entity may be any functional entity on the network side; if the technical solution of the embodiment is applied to the WIMAX system, the trigger event may be any existing WIMAX related event; the sent request may be an existing one.
  • the foregoing identifier may be referred to as a bearer identifier, and is used to indicate that the bearer is a certain type of dedicated bearer when establishing different types of bearers, such as an application layer signaling bearer, or an IP layer signaling bearer, or a session layer signaling bearer, or A specific bearer such as a MAC layer signaling bearer.
  • a bearer identifier is used to indicate that the bearer is a certain type of dedicated bearer when establishing different types of bearers, such as an application layer signaling bearer, or an IP layer signaling bearer, or a session layer signaling bearer, or A specific bearer such as a MAC layer signaling bearer.
  • the bearer identifier when establishing an IMS signaling bearer, the bearer identifier may be referred to as an IMS signaling bearer identifier.
  • the bearer identifier may be a scalable and configurable field, code or list, which may be represented as a 0-256 indicator code, 0 for IMS signaling bearer, 1 for WIMAX MBS signaling bearer, 2 for WIMAX MBS service bearer, 3 indicates the WIMAX LCS service bearer, etc., and other values are reserved for subsequent expansion.
  • the bearer ID can correspond to the Service Flow Scheduling type.
  • a function entity that is a decision entity in the network side after determining whether the bearer corresponding to the bearer identifier can be established, by using one of the fields in the bearer identifier as the result information, that is, the successful establishment or the establishment fails, and directly Or the other function entity in the network side sends an indication that carries the bearer identifier to the terminal, that is, carries the result information of the bearer identifier, indicating that the bearer has been successfully established or requests another functional entity to establish the bearer.
  • the decision entity may also send the relevant configuration parameters of a certain service stored by the terminal to the terminal according to the request of the terminal or other functional entity. If the decision entity does not store the relevant configuration parameter of a certain service, the entity may also The other entity in the network side requests to send the relevant configuration parameters of the service to the terminal.
  • the terminal sends a request to carry the bearer, or sends a request to establish a bearer, that is, does not carry the request for carrying the bearer.
  • the network side can be requested to obtain related configuration parameters of the service by carrying an indication that the relevant configuration parameter of the service is obtained in the request.
  • the indication of obtaining the relevant configuration parameter may be carried in the same request as the identifier, or may be carried in a certain request separately, that is, the terminal or the network function entity that sends the request may simultaneously request to establish a dedicated bearer and obtain related configuration. Parameters, you can also request them separately
  • the relevant configuration parameters may be related configuration parameters of services such as IMS, WIMAX MBS, and WIMAX LCS, that is, IMS related configuration parameters, or MBS related configuration parameters, or LCS related configuration parameters.
  • the IMS related configuration parameters include: IMS signaling bearer related information, Proxy-Call Session Control Function (P-CSCF) address, and Domain Name Server (DNS) address, etc. Or the parameter carried in the data path message; the indication of obtaining the IMS-related configuration parameter, or an extensible and configurable field, code, or list similar to the bearer identifier; the terminal receiving the IMS-related configuration parameter sent by the network side After that, the parameter is stored for implementing the subsequent IMS service.
  • P-CSCF Proxy-Call Session Control Function
  • DNS Domain Name Server
  • the process of allocating relevant configuration parameters by the network side can be implemented in the process of establishing a certain type of dedicated bearer in this embodiment or in the process of establishing a bearer.
  • the determining entity on the network side in the foregoing system can make a decision to establish a bearer according to the received request, and can also initiate the establishment of the bearer.
  • the device that includes the entity may include: a transceiver unit, a message parsing unit and a message generating unit; the transceiver unit sends a request from the outside carrying the bearer identifier indicating the establishment of the signaling bearer to the message parsing unit; and sends the result information of the bearer identifier from the message generating unit to the outside; Sending a request message carrying the bearer identifier of the message generating unit to the outside;
  • the message parsing unit parses out the bearer identifier provided by the transceiver unit, and if it has the decision-making capability, determines whether the signaling bearer corresponding to the bearer identifier can be established, and provides the decision result and the bearer identifier to the message generating unit;
  • the decision-making capability directly provides the parsed bearer identifier to the message generating unit;
  • the message generation unit is configured to carry the indication establishment signaling.
  • the request message carrying the bearer identifier is sent to the transceiver unit according to the decision result from the message parsing unit, and the result information carrying the identifier is generated according to the decision result and the identifier from the message parsing unit, indicating that the bearer identifier is successfully established.
  • the corresponding signaling bearer or setup fails, and is provided to the transceiver unit.
  • the request message for establishing the bearer is generated according to the bearer identifier from the message parsing unit, and the bearer identifier is carried in the generated request message and provided to the transceiver unit.
  • the device for establishing a bearer can also initiate a bearer setup according to a trigger event on the network side, and the device further includes: a detecting unit, requesting, by the message parsing unit, to establish a bearer according to a trigger event on the network side, and generating a bearer type that is requested to be established.
  • the corresponding bearer identifier is carried in the request;
  • the message parsing unit if the message parsing unit has the decision-making capability, the message parsing corresponding to the bearer identifier can be determined according to the request of the detecting unit and the bearer identifier included in the request, and the decision result and the bearer identifier are determined.
  • the bearer identifier provided by the detecting unit is directly provided to the message generating unit.
  • the message generating unit generates a request message for establishing a bearer according to the bearer identifier from the message parsing unit, and carries the identifier in the generated request message and provides the request message to the transceiver unit.
  • the signaling bearer establishing method in this embodiment includes: establishing, in the network, a dedicated bearer for transmitting signaling for the terminal.
  • the method can be implemented in the following manner: Any one of the network side has a decision-making capability, for example, a function entity that stores a related policy, and establishes a certain dedicated bearer identifier according to a certain trigger event or received bearer on the network side.
  • the request that is, the request carrying the bearer identifier, whether the decision can be used to establish a bearer corresponding to the bearer identifier for the terminal, and if the decision is successful, the bearer corresponding to the bearer identifier is triggered, and the indication carrying the bearer identifier is sent, indicating that the bearer identifier is successfully established. 7 or request other functional entities to establish the 7-bearer corresponding to the identifier.
  • the network side may also store any one of the related configuration parameters of a certain service, according to the request of the terminal, according to the network side. It requests the entity or automatically sends the parameter to the terminal.
  • the related configuration parameters may be services such as IMS, WIMAX MBS, and WIMAX LCS.
  • the related configuration parameters are: IMS related configuration parameters, or MBS related configuration parameters, or LCS related configuration parameters.
  • a data path (DATA PATH ) needs to be established at the same time as or after the establishment of the service flow.
  • the process of establishing a DATA PATH can be the same as that defined by the existing WIMAX NWG protocol.
  • the ASN GW Address for user traffic and the ASN GW Address for Control Plane are optionally added in the message of establishing the DATA PATH to implement service flow separation between the user plane and the control plane.
  • the foregoing solution may be implemented by various logical functional entities; the policy for determining whether the bearer can be established may be the subscription information of the user.
  • the technical solution of the present embodiment is applied to the WiMAX-IMS system to establish an IMS signaling bearer, the bearer identifier is an IMS signaling bearer identifier, and the related configuration parameters are IMS related configuration parameters, and combined with different initiation methods,
  • the system for establishing a signaling bearer and the method for establishing a signaling bearer in the embodiment are described in detail.
  • FIG. 6 is a structural diagram of a system for establishing a bearer in an embodiment of the present invention.
  • the signaling bearer is an IMS signaling bearer.
  • the system for establishing a signaling bearer in this embodiment includes: a terminal and a network side, where the network side includes: a service flow management entity, a policy execution function entity, and a policy. Decision function entity.
  • the terminal, the service flow management entity, the policy enforcement function entity, and the policy decision function entity may initiate the establishment of the bearer; the service flow management entity, the policy execution function entity, and the policy decision function entity may all pre-store the IMS related Configuration parameters, and/or as decision entities store relevant policies and make decisions to establish bearers.
  • the terminal if the terminal initiates the establishment of the bearer, the terminal sends a request for carrying the bearer identifier to the network side, and the network side performs the function entity according to the service flow management entity and the policy. And the order of the policy decision function entity, reporting the request to the network entity of the level one level up to the above “3 ⁇ 4 to the policy decision function entity. If an entity on the network side can make a decision, receiving the request carrying the bearer identifier After the report is not continued, the decision is made to trigger the establishment or decision-making of the dedicated bearer corresponding to the bearer identifier, and the bearer is carried in the order of the policy decision function entity, the policy enforcement function entity, and the service flow management entity.
  • the indication of the identifier indicates that the loading or failure corresponding to the identifier is successfully established.
  • the entity directly makes a decision in the case that the entity can make a decision, triggers the establishment or decision-making of the dedicated bearer corresponding to the bearer identifier, and determines the functional entity and policy according to the policy.
  • the function entity and the service flow management entity are sequentially sent to carry the bearer identifier, and the function entity that successfully establishes the bearer identifier is triggered, or the function entity that requests the indication is triggered to establish the bearer corresponding to the identifier;
  • the entity that initiates the bearer establishment reports the request carrying the bearer identifier to the network entity at the next level, in the order of the service flow management entity, the policy enforcement function entity, and the policy decision function entity, until the report is sent to the network entity.
  • the policy decision function entity if the upper entity of the entity can make a decision, does not continue to report after receiving the request carrying the bearer identifier, but performs a decision, triggers the establishment or decision failure of the dedicated bearer corresponding to the bearer identifier, and according to Strategic decision making
  • the sequence of the entity, the policy enforcement function entity, and the service flow management entity sends an indication of carrying the bearer identifier to the terminal, indicating that the bearer or the failure corresponding to the bearer identifier is successfully established, or the function entity requesting to receive the indication triggers the establishment of the identifier.
  • Corresponding bearer The same is true for the principle of providing IMS-related configuration parameters to the terminal.
  • the QoS information related to the signaling flow can also be sent at the same time.
  • the terminal that is, the MS, the mobile station (MSS)
  • MS mobile station
  • the terminal may initiate the establishment of the IMS signaling bearer, and send a request for establishing the IMS signaling bearer to the service flow management entity, where the request carries the IMS signaling bearer for the terminal.
  • the indication that is, the IMS signaling bearer identifier
  • the request may further carry an indication for acquiring the IMS-related configuration parameter; receive and store the indication of the IMS signaling bearer identifier sent by the service flow management entity, and simultaneously receive and store the IMS-related configuration parameter.
  • the terminal and the service flow management entity may perform the interaction by using a dynamic service addition (DSA) message, and carry the IMS signaling bearer identifier in the extended domain of the QoS parameters of the DSA message;
  • DSA dynamic service addition
  • the bearer is changed to the required bearer, and the terminal and the service flow management entity can interact with each other through a dynamic service change (DSC) message.
  • DSA dynamic service addition
  • DSC dynamic service change
  • the base station establishes an IMS signaling bearer for the terminal;
  • the IMS signaling bearer is set up to send a request for carrying the IMS signaling bearer identifier to the policy enforcement function entity. If the service flow management entity does not store the IMS related configuration parameter, the request may also carry the identifier for acquiring the IMS related configuration parameter.
  • the indication that carries the IMS signaling bearer identifier sent by the policy enforcement function entity may be received, and the corresponding network entity is triggered to establish an IMS signaling bearer for the terminal according to the indication, and may also receive the IMS related configuration parameter or obtain the IMS related configuration parameter.
  • the indication that the IMS signaling bearer identifier is carried may be sent to the terminal, indicating that the bearer corresponding to the bearer identifier is successfully established or fails to be established or the bearer is requested to be established, and the received or pre-stored IMS related configuration parameter may also be sent.
  • the message that the service flow management entity interacts with the policy execution function entity may be a resource-reservation (RR) message.
  • RR resource-reservation
  • the policy enforcement function entity such as one or any combination of a gateway, a proxy, a relay, a network access server NAP, a WIMAX SFA, a PCEF, a FA, and a bearer channel function entity, may receive the bearer IMS signaling bearer sent by the service flow management entity.
  • the IMS signaling bearer request is created, and the decision is to establish an IMS signaling bearer for the terminal, and after the decision is successful, the corresponding network entity is triggered to establish an IMS signaling bearer for the terminal; or the IMS signaling bearer is initiated by itself, and the decision is
  • the terminal establishes an IMS message, and triggers the corresponding network entity to establish an IMS signaling bearer for the terminal after the decision is successful, or sends a request for carrying the IMS signaling bearer identifier to the policy decision function entity;
  • the IMS signaling bearer identifier is used to create an IMS signaling bearer request, and the decision is to establish an IMS signaling bearer for the terminal, and after the decision is successful, trigger the corresponding network entity to establish an IMS signaling bearer for the terminal; or send the bearer IMS to the service flow management entity.
  • the sent request may also carry an indication of acquiring the IMS-related configuration parameter or a pre-stored IMS-related configuration parameter; if the decision execution function entity itself If the IMS-related configuration parameter is not stored, the sent request may further include an indication of acquiring an IMS-related configuration parameter; and receiving an indication that the QoS-initiated identifier is sent by the policy-determining function entity, and triggering the corresponding network entity according to the indication Terminal construction
  • the IMS signaling bearer may be received; the IMS-related configuration parameter may be received at the same time; the indication carrying the IMS signaling bearer identifier may be sent to the service flow management entity or the policy decision function entity, indicating that the 7-load or the corresponding 7-bearing identifier is successfully established or failed
  • the request to establish the 7-load can also send the received or pre-stored I
  • the message of interaction between the policy enforcement function entity and the policy decision function entity may be a Diameter protocol/Policy-Decision (PD)/RR cancellation policy decision function entity, such as a PCRF, PF, AAA server.
  • PD Diameter protocol/Policy-Decision
  • the HSS, the HLR, the proxy, and the relay may receive the IMS signaling bearer request that carries the IMS signaling bearer identifier sent by the policy enforcement function entity, and determines whether the terminal establishes the IMS signaling load and determines After the success, the corresponding network entity is triggered to establish an IMS signaling bearer for the terminal; or the request for the IMS signaling bearer is sent to the policy enforcement function entity, and the IMS signaling bearer identifier is carried in the request; Whether the decision is to establish an IMS signaling bearer for the terminal, and after the decision is successful, trigger the corresponding network entity to establish IMS signaling for the terminal; or send the IMS signaling bearer carrying the IMS signaling bearer identifier
  • the MIS-related configuration parameter may also be received at the same time; the request or the indication carrying the IMS signaling bearer identifier may be sent to the policy enforcement function entity, indicating that the 7-load identifier corresponding to the 7-load identifier is successfully established or the request is established.
  • the request or the indication carrying the IMS signaling bearer identifier is sent to the policy enforcement function entity, the received or pre-stored IMS-related configuration parameters may be simultaneously sent, or an indication for acquiring the IMS-related configuration parameter may be simultaneously sent.
  • the flow of data or signaling includes a terminal identifier (MS ID) and a monthly service flow identifier (SFID)
  • the combination of the MS ID and the SFID may correspond to one IMS payload, and thus, The letter carries one of the five existing types of streams
  • the QoS information and/or the charging information related to the signaling flow carried in the indication carrying the bearer identifier is used to set a higher QoS level for signaling corresponding to the bearer identifier, such as IMS signaling.
  • the bearer type, the MS ID, and the SFID can be distinguished according to the bearer identifier, that is, the bearer type, that is, the bearer type. Signaling bearer.
  • This bearer can be mapped to the bearer type in the network, for example, the type defined by the existing 802.16E/D: 0: Reserved; 1: for Undefined (BS implementation- dependent); 2: for BE (default); 3: for nrtPS; 4: for rtPS; 5: Reserved; 6: for UGS; 7-255: Reserved. Or define this parameter in a certain type.
  • the bearer identifier can be associated with the identifier of the DATA PATH, or
  • the IP quintuple (source address, source port, destination address, destination port, protocol number) is associated.
  • the terminal, and the network entity where the service flow management entity, the policy enforcement function entity, and the policy decision function entity are located, if the flow or bearer needs to be processed, can distinguish the bearer type according to the bearer identifier and the DATA PATH identifier, or according to the bearer identifier and the IP five yuan. Group to distinguish the type of bearer.
  • the terminal, the policy enforcement function entity, and the policy decision function entity may be distinguished from the MS ID and the SFID, or the bearer identifier and the DATA PATH identifier, or the 7-digit identifier and the IP quintuple according to the IMS signaling bearer identifier in the flow.
  • the signaling used to establish the IMS signaling bearer in the current flow; the received IMS related configuration parameters may be saved.
  • Corresponding relationship 1 in the flow or bearer: MS ID, SFID, and bearer ID (eg, 0: IMS signaling bearer, 1: WIMAX MBS signaling bearer, 2: WIMAX LCS signaling bearer); Correspondence in flow or bearer 2: Bearer identification and IP quintuple;
  • Bearer ID and DATA PATH ID.
  • the service flow management entity can bear the identity and the MS ID according to the IMS signaling in the flow.
  • SFID or the bearer identifier and the DATA PATH identifier, or the bearer identifier and the IP quintuple distinguish the IMS signaling SDU in the current protocol data unit (SDU), and the IMS signaling SDU is used to establish the IMS signaling bearer; Establish an IMS signaling bearer for the terminal.
  • SDU current protocol data unit
  • the policy enforcement function entity is a logical function entity including an SFA, it may further include a proxy entity (Agent/Proxy) connected between the SFA and the policy decision function entity.
  • the Agent/Proxy is used to implement the relay or proxy function to shield the mobility of the SFA.
  • the policy decision function entity is PF/PCRF (the PF/PCRF in this embodiment represents PF and/or PCRF)
  • Bay ij PF/PCRF It can be divided into the home network PF/PCRF (H-PF/H-PCRF) and the visited PF/PCRF (V-PF/V-PCRF).
  • the policy decision function entity includes the home network PF/ PCRF and access PF/PCRF.
  • the policy decision function entity only includes the home network PF/PCRF.
  • the PF, the anchor SFA or the service SFA can also be assigned to generate the user plane address ASN GW Address for user traffic and the control plane address ASN GW Address for Control Plane, and directly or indirectly send to the network entity where the SFM is located, for example Base station.
  • the data plane gateway address carries the user plane data
  • the control plane gateway address carries the control plane data. Therefore, when the functional entity and the network entity are not the same entity, the SFM can implement the service flow separation between the user plane and the control plane according to the foregoing two addresses. .
  • the policy for determining whether the bearer can be established is preferably stored in the policy decision function entity, such as PF/PCRF; IMS related configuration parameters such as P-CSCF address and DNS server address.
  • the PF can be stored in the policy decision function entity. For example, if the PF is the same entity as the AAA server, the P-CSCF address is configured in the PF/AAA server. If the PF is not the same as the AAA server, the PF can be Generate IMS-related configuration parameters yourself, which can also be obtained from the AAA server.
  • the policy execution function entity is used as the service SFA and the anchor SFA
  • the policy decision function entity is the home network PF/PCRF
  • the IMS related configuration parameter is stored in the home network PF/PCRF as an example.
  • the signaling bearer establishment method in this embodiment is described in detail.
  • the present embodiment includes eight signaling bearer establishment methods, where the signaling bearer establishment method 1 is applicable to a case where the system does not include an agent/proxy, and the signaling bearer establishment method 7 is applicable to a case where the system includes an Agent/Proxy.
  • the bearer initiates the bearer establishment;
  • the signaling bearer establishment method 2 ⁇ 6 is applicable to the case where the system does not include the agent/proxy, and the bearer establishment method 8 is applicable to the case where the system includes the agent/proxy, and the signaling bearer is established.
  • both are initiated by the network side.
  • FIG. 7 is a flowchart of a method 1 for establishing a letter in the embodiment of the present invention. As shown in FIG. 7, the establishment of the IMS signaling bearer by the MS is taken as an example. In the present embodiment, the signaling bearer establishment method 1 includes the following steps:
  • Step 701 When the IMS service needs to be used, in order to speed up the IMS service establishment process, the application layer signaling bearer of the IMS service is established for the MS before the IMS service establishment process, that is, the IMS signaling bearer, for example, the Session Initiated Protocol (Session Initiated Protocol, SIP)
  • the IMS signaling bearer for example, the Session Initiated Protocol (Session Initiated Protocol, SIP)
  • SIP Session Initiated Protocol
  • the IMS bearer is carried in the request sent by the MS. Therefore, the bearer that is requested to be established is the IMS signaling bearer. If the MS needs to obtain the IMS-related configuration parameters such as the P-CSCF address, the DSA-REQ The message also carries an indication of obtaining IMS related configuration parameters.
  • Step 702 The SFM cannot determine whether to establish an IMS signaling bearer for the MS. After receiving the DSA-REQ message from the MS, the SFM sends an RR-Request message to the serving SFA, and carries the IMS signaling bearer identifier in the message, requesting to establish. Signaling bearer.
  • the SFM also carries the indication in the RR-Request message.
  • Step 703 The serving SFA cannot determine whether to establish an IMS signaling bearer for the MS. After receiving the RR-Request message from the SFM, the service SFA sends an RR-Request message to the anchor SFA, and carries the IMS signaling bearer identifier in the message. Request to establish a signaling bearer.
  • the service SFA also carries the indication in the RR-Request message sent to the anchor SFA.
  • Step 704 The anchor SFA cannot decide whether to establish an IMS signaling bearer for the MS. After receiving the RR-Request message from the serving SFA, send a Diameter CCR/PD-Request/RR-Request message to the home network PF/PCRF, and The message carries the IMS signaling 7 carrying identifier, requesting to establish signaling 7.
  • the anchor SFA In this step, if the MS is in the home network, the anchor SFA directly requests the home network PF/PCRF to establish a signaling bearer; if the MS is in the visited network, the anchor SFA passes the visited PF/PCRF to the home network PF/PCRF. Requesting to establish a signaling bearer; if the RR-Request message carries an indication of obtaining an IMS-related configuration parameter, the anchor SFA also carries the indication in the Diameter CCR/PD-Request message.
  • Step 705 The home network PF/PCRF stores the user subscription information, and can determine whether to establish an IMS signaling bearer for the MS. After receiving the Diameter CCR/PD-Request message from the anchor SFA, determine whether to establish IMS signaling for the MS. The bearer determines whether to trigger the establishment of the IMS signaling bearer according to the result of the decision, and sends a Diameter CCA/PD-Response/RR-Response message carrying the IMS signaling bearer identifier to the anchor SFA, Indicates whether the IMS signaling bearer is established for the MS, or the IMS signaling bearer is successfully established or failed.
  • the home network PF/PCRF carries the pre-stored IMS-related information to the Diameter CCA/PD-Response/ The RR-Response message is provided to the MS; if the MS is in the home network, the home network PF/PCRF directly sends a Diameter CCA/PD-Response/RR-Response message to the anchor SFA to respond; if the MS is in the visited network, The home network PF/PCRF responds by sending a Diameter CCA/PD-Response/RR-Response message to the anchor SFA via the visited PF/PCRF.
  • Steps 706 to 708 Anchoring the SFA, the service SFA, and the SFM, and determining whether to establish an IMS signaling bearer for the MS according to the received message carrying the IMS signaling bearer identifier, that is, whether the IMS signaling bearer is established for the MS. And sending an indication of whether the IMS signaling bearer is established for the MS by using an RR-Response message, an RR-Response message, and a DSA-RSP message carrying the IMS signaling bearer identifier.
  • the MS requests the IMS-related configuration parameters, such as the P-CSCF address, to obtain the IMS-related configuration parameters, such as the P-CSCF address, in step 710, the SFA, the service SFA, and the SFM are anchored, and the RR-Response message is sequentially passed, and the RR-Response is passed.
  • the message and the DSA-RSP message also send the IMS-related configuration parameters provided by the PF/PCRF to the MS.
  • the network entity where the SFM is located triggers a DATA PATH establishment process.
  • the DATA PATH setup message for example, the Path Pre-Registration Request or the Path Registration Request message carries the bearer identifier, that is, the IMS signaling bearer identifier in this embodiment.
  • the DATA PATH setup process can be merged with resource reservations or it can be a separate process.
  • the DATA PATH process does not necessarily trigger after receiving step 707.
  • the network can select the appropriate time and step to trigger the DATA PATH setup.
  • the SFM, or the service SFA, or the anchor SFA may also decide whether the IMS signaling bearer can be established for the MS. In this case, a decision is made at step 702, or step 703, or step 704 without continuing the request.
  • the SFM, or the GW where the service SFA is located, or the GW where the anchor SFA is located has an IMS-related configuration parameter such as a P-CSCF address and a DNS server address, then at step 702, or step 703, or step 704, SFM, or service
  • the SFA, or the anchor SFA does not need to request the IMS-related configuration parameters, but the IMS-related configuration parameters are passed through the DSA-RSP message, or through the RR-Response message, or through the RR-Response message, immediately or together with the decision result. MS sent.
  • the MS is in the visited network, whether the decision can establish an IMS signaling bearer for the MS can also be completed by the visited PF/PCRF; the IMS related configuration parameters can also be stored in the visited PF/PCRF.
  • the user plane address ASN GW Address for user traffic and the control plane address ASN GW Address for Control Plane may be generated by the PF, the anchor SFA or the service SFA, and sent to the network entity where the SFM is located, for example, the base station, by the SFM. Separate the business flow between the user plane and the control plane.
  • the two addresses are generated by the PF allocation, it is sent to the network entity where the SFM is located through steps 705 to 707; if the two addresses are generated by the anchor SFA allocation, then the step S706 and step 707 are sent to the SFM.
  • the above is a description of the signaling bearer establishment method 1 in the present embodiment.
  • the signaling bearer establishment method 2 in the present embodiment will be described.
  • Figure 8 is a flow chart showing a method 2 of establishing a letter in the embodiment of the present invention.
  • the establishment of the IMS signaling bearer by the anchor SFA as the policy enforcement function entity in the network side is taken as an example.
  • the bearer establishment method 2 includes the following steps:
  • Step 801 When the IMS service needs to be used, to speed up the IMS service establishment process, the IMS signaling bearer is established for the MS before the IMS service establishment process, for example, the signaling bearer of the SIP session, and the anchor SFA is initiated due to an event trigger.
  • the IMS signaling bearer, the anchor SFA cannot decide whether to establish an IMS signaling bearer for the MS, and send a Diameter CCR/PD-Request/RR-Request message to the home network PF/PCRF, and carry the IMS signaling bearer identifier in the message. Request to establish a signaling bearer.
  • the bearer is requested, so the bearer that is requested to be established is the IMS signaling bearer; if the MS is in the home network, the anchor SFA directly requests the home network PF/PCRF to establish signaling. Bearer; if the MS is in the visited network, the anchor SFA requests to establish a signaling bearer to the home network PF/PCRF through the visited PF/PCRF; if the IMS related configuration parameters such as the P-CSCF address need to be provided to the MS, the SFA is anchored.
  • the indication of obtaining the IMS-related configuration parameters is also carried in the Diameter CCR/PD-Request/RR-Request message.
  • Step 802 The home network PF/PCRF stores the user subscription information, and can determine whether to establish an IMS signaling bearer for the MS. After receiving the Diameter CCR/PD-Request message from the anchor SFA, determine whether to establish IMS signaling for the MS. The bearer determines whether to trigger the establishment of the IMS signaling bearer according to the result of the decision, and sends a Diameter CCA/PD-Response/RR-Response message carrying the IMS signaling bearer identifier to the anchor SFA, indicating whether to establish an IMS signaling bearer for the MS. , or the IMS signaling bearer is successfully established or failed.
  • the home network PF/PCRF carries the pre-stored IMS-related information, such as the P-CSCF address, in the Diameter CCA/PD-Response/RR-Response message, and sends the information to the anchor SFA; If the MS is in the home network, the home network PF/PCRF directly sends a Diameter CCA/PD-Response/RR-Response message to the anchor SFA to respond; if the MS is in the visited network, the home network PF/PCRF passes the visited PF/PCRF. A Diameter CCA/PD-Response/RR-Response message is sent to the anchor SFA to respond.
  • IMS-related information such as the P-CSCF address
  • Steps 803 to 805 Anchoring the SFA, the service SFA, and the SFM, and determining whether to establish an IMS signaling bearer for the MS according to the received message carrying the IMS signaling bearer identifier, that is, whether the IMS signaling bearer is established for the MS. And transmitting an indication of whether the IMS signaling bearer is established for the MS by using the RR-Request message, the RR-Request message, and the DSA-REQ message carrying the IMS signaling bearer identifier.
  • the anchor SFA requests to provide an IMS-related configuration parameter such as a P-CSCF address to the MS by obtaining an indication of the IMS-related configuration parameter in step 801
  • the SFA, the service SFA, and the SFM are anchored, and the RR-Request is sequentially passed.
  • the message, the RR-Request message, and the DSA-REQ message also send the IMS-related configuration parameters provided by the home network PF-PCRF to the MS.
  • the network entity where the SFM is located triggers a DATA PATH establishment process.
  • the DATA PATH setup message for example, the Path Pre-Registration Request or the Path Registration Request message carries the bearer identifier, that is, the IMS signaling bearer identifier in this embodiment.
  • the DATA PATH setup process can be merged with resource reservations or it can be a separate process.
  • the DATA PATH process does not necessarily trigger after receiving step 804.
  • the network can choose the appropriate one.
  • Step 806 to step 808 The MS sequentially passes the SFM and the service SFA, that is, through the message flows of the DSA-RSP message, the RR-Response message, and the RR-Response message, and successfully responds to the anchor SFA by performing IMS signaling.
  • all the messages used for the response may also carry the IMS signaling bearer identifier, indicating that the IMS signaling bearer is successfully established.
  • the anchor SFA, or the service SFA, or the SFM can also decide whether the IMS signaling bearer can be established for the MS. In this case, the decision is made in step 801, or step 804, and the IMS signaling bearer is established for the terminal according to the result of the decision, and then step 803 is directly executed, or the subsequent steps are performed to deliver the IMS for the terminal. An indication of the signaling bearer.
  • step 801 the anchor SFA, or the service SFA, or the SFM does not need to request to acquire the IMS-related configuration parameters, but sends the IMS-related configuration parameters together with the decision result to the MS.
  • the MS is in the visited network, whether the decision can establish an IMS signaling bearer for the MS can also be completed by the visited PF/PCRF; the IMS related configuration parameters can also be stored in the visited PF/PCRF.
  • the IMS signaling bearer identifier may not be carried in each message, but only the indication of obtaining the IMS-related configuration parameter or the IMS-related configuration parameter that is delivered, that is, the relevant configuration parameters of various services are obtained in this embodiment.
  • the method also applies to the existing bearer establishment process.
  • the user plane address ASN GW Address for user traffic and the control plane address ASN GW Address for Control Plane may be generated by the PF, the anchor SFA or the service SFA, and sent to the network entity where the SFM is located, for example, the base station, by the SFM. Separate the business flow between the user plane and the control plane.
  • the network entity where the SFM is located is sent through steps 802 to 804; if the two addresses are generated by the anchor SFA allocation, then the SFM is sent to the SFM through steps 803 and 804. The network entity; if the two addresses are generated by the service SFA allocation, then it is sent to the network entity where the SFM is located via step 804.
  • FIG. 9 is a flow chart showing a method 3 of establishing a letter in the embodiment of the present invention.
  • the establishment of the IMS bearer is initiated by the home network PF/PCRF as the policy decision function entity in the network side.
  • the bearer establishment method 3 includes the following steps: Step 901: When the IMS service needs to be used In order to speed up the IMS service establishment process, the IMS signaling bearer is established for the MS before the IMS service establishment process, for example, the signaling bearer of the SIP session.
  • the home network PF/PCRF initiates the establishment of the IMS signaling bearer,
  • the network PF/PCRF stores the user subscription information, determines whether the IMS signaling bearer is established for the MS, determines whether to trigger the establishment of the IMS signaling bearer according to the decision result, and carries the Diameter RAR/PD-Request carrying the IMS signaling.
  • the /RR-Request message is sent to the anchor SFA, indicating whether the IMS signaling bearer is established, or the IMS signaling bearer is successfully established or failed.
  • the home network PF/PCRF carries the indication of the pre-stored IMS-related configuration parameter in the Diameter CCA/PD-Request/RR-Request message. ; If the MS is in the home network, the home network PF/PCRF sends the Diameter directly to the anchor SFA; CCA/PD-Request/RR-Request message; If the MS is in the visited network, the home network PF/PCRF sends a Diameter CCA/PD-Request/RR-Request message to the anchor SFA through the visited PF/PCRF.
  • step 901 If the message in step 901 is a Diameter RAR message, the message needs to be processed first by one of the following two processing modes before step 902: 1. Modify the RAR message to complete a PD-Request/RR-Request. The function of the message; 2. After receiving the Diameter RAR message, the anchor SFA initiates a Diameter CCR message to the PF, and the PF initiates a Diameter CCA message to the SFA, and then performs step 902.
  • Step 902 to step 904 Anchoring the SFA, the service SFA, and the SFM, and determining whether to establish an IMS signaling bearer for the MS according to the received message carrying the IMS signaling bearer identifier, that is, whether the IMS signaling bearer is established for the MS. And sending an indication of whether to establish an IMS signaling bearer for the MS to the MS by using the RR-Request message, the RR-Request message, and the DSA-REQ message carrying the IMS signaling bearer identifier.
  • the home network PF/PCRF provides IMS-related configuration parameters
  • the SFA, the service SFA, and the SFM are anchored, and the IMS-related configuration parameters are also passed through the RR-Request message, the RR-Request message, and the DSA-REQ message. Send to MS.
  • the network entity where the SFM is located triggers a DATA PATH establishment process.
  • the DATA PATH setup message for example, the Path Pre-Registration Request or the Path Registration Request message carries the bearer identifier, that is, the IMS signaling bearer identifier in this embodiment.
  • the DATA PATH setup process can be merged with resource reservations or it can be a separate process.
  • the DATA PATH process does not necessarily trigger after receiving step 903, and the network can select the appropriate time and step to trigger the DATA PATH setup.
  • the MS sequentially passes the SFM, the service SFA, and the anchor SFA, that is, the message flow through the DSA-RSP message, the RR-Response message, the RR-Response message, and the Diameter RAA/PD-Response/RR-Response message.
  • the IMS signaling 7 on the home network PF/PCRF establishes a successful response.
  • step 905 to step 908 all the messages used for the response may also carry the IMS signaling bearer identifier, indicating that the IMS signaling bearer is successfully established.
  • the anchor SFA, or the service SFA, or the SFM may also decide whether the IMS signaling bearer can be established for the MS. And determining whether to establish an IMS signaling bearer for the terminal according to the decision result.
  • the home network PF/PCRF sends a request to carry the IMS signaling bearer identifier to the anchor SFA directly or through the visited PF/PCRF, and in step 902, or step 903, or step 904 The decision is made, and then the subsequent steps are performed in sequence, and an indication of whether to establish an IMS signaling bearer for the terminal is sent.
  • step 901 If the GW in which the SFA is located, or the GW or the SFM in which the SFA is located, and the IMS-related configuration parameters such as the P-CSCF address and the DNS server address are not present, and the parameter is not present in the home network PF/PCRF, then in step 901 In the request that the home network PF/PCRF sends the IMS-related configuration parameter directly or through the PF/PCRF to the anchor SFA, and in step 902, or step 903, or step 904, anchor the SFA, or The serving SFA, or SFM, sends the IMS related configuration parameters along with the decision result to the MS.
  • the MS is in the visited network, whether the decision can establish an IMS signaling bearer for the MS can also be completed by the visited PF/PCRF; the IMS related configuration parameters can also be stored in the visited PF/PCRF.
  • the IMS signaling bearer identifier may not be carried in each message, but only the indication for obtaining the IMS-related configuration parameter or the IMS-related configuration parameter delivered, that is, the actual configuration
  • the method for obtaining relevant configuration parameters of various services in the manner of applying is also applicable to the existing bearer establishment process.
  • the user plane address ASN GW Address for user traffic and the control plane address ASN GW Address for Control Plane may be generated by the PF, the anchor SFA or the service SFA, and sent to the network entity where the SFM is located, for example, the base station, by the SFM. Separate the business flow between the user plane and the control plane.
  • the network entity where the SFM is located is sent through steps 901 to 903; if the two addresses are generated by the anchor SFA allocation, then the SFM is sent to the SFM through steps 902 and 903. The network entity; if the two addresses are generated by the service SFA allocation, then it is sent to the network entity where the SFM is located via step 903.
  • the above is a description of the signaling bearer establishment method 3 in the present embodiment.
  • the following describes the signaling bearer establishment method 4 in this embodiment.
  • FIG. 10 is a flowchart of a method 4 of establishing a bearer according to an embodiment of the present invention.
  • the establishment of the IMS bearer by the access PF/PCRF as the policy decision function entity in the network side is taken as an example.
  • the bearer establishment method 4 includes the following steps: Step 1001: The MS is in the visited network.
  • the IMS signaling bearer is established for the MS before the IMS service establishment process, for example, the signaling bearer of the SIP session, and the PF/PCRF is initiated by the access site due to an event trigger.
  • the access PF/PCRF cannot decide whether to establish IMS signaling for the MS, send a Diameter CCR/PD-Request/RR-Request message to the home network PF/PCRF, and carry the IMS signaling in the message. Bearer identification, request to establish signaling 7 load.
  • the bearer that is requested to be established is the IMS signaling bearer; if the IMS needs to provide the P-CSCF address to the MS,
  • the relevant configuration parameters are also carried in the Diameter CCR/PD-Request/RR-Request message by the PF/PCRF to obtain the indication of the IMS-related configuration parameters.
  • Step 1002 The home network PF/PCRF stores the user subscription information, and can determine whether to establish an IMS signaling bearer for the MS. After receiving the Diameter CCR/PD-Request/RR-Request message from the visited PF/PCRF, the decision is made. Establishing an IMS signaling bearer for the MS, and determining whether to trigger the establishment of the IMS signaling bearer according to the decision result, and sending a Diameter CCA/PD-Response/RR-Response message carrying the IMS signaling 7 identifier to the visited PF/PCRF, Indicates whether the IMS signaling bearer is established, or the IMS signaling bearer is successfully established or failed.
  • the home network PF/PCRF carries the pre-stored IMS-related information such as the P-CSCF address to the Diameter CCA/PD- The Response message is sent to the anchor SFA.
  • the message in the step 1002 may also be a Diameter RAR message.
  • the message needs to be processed by one of the following two processing modes before the step 1003: 1. Modify the RAR message to complete a PD-Request-like operation.
  • the function of the RR-Request message is as follows: 2. After receiving the Diameter RAR message, the anchor SFA initiates a Diameter CCR message to the PF, and the PF initiates a Diameter CCA message to the SFA, and then performs step 1003.
  • Steps 1003 to 1006 The access PF/PCRF, the anchor SFA, the service SFA, and the SFM are sequentially determined according to the received message carrying the IMS signaling bearer identifier, that is, whether the IMS signaling bearer is established for the MS, and whether the The MS establishes an IMS signaling bearer, and delivers the IMS signaling bearer to the MS through the Diameter RAR/PD-Request/RR-Request message, the RR-Request message, the RR-Request message, and the DSA-REQ message. An indication of the IMS signaling bearer is established for the MS.
  • Access PF/PCRF provides IMS related configuration parameters
  • Access PF/PCRF, anchor SFA, service SFA, and SFM and IMS-related configuration parameters are also passed through Diameter RAR/PD-Request/RR-Request messages, RR-Request messages, RR-Request messages, and DSA-REQ messages. Send to MS.
  • the network entity where the SFM is located triggers a DATA PATH establishment process.
  • the DATA PATH setup message for example, the Path Pre-Registration Request or the Path Registration Request message carries the bearer identifier, that is, the IMS signaling bearer identifier in this embodiment.
  • the DATA PATH setup process can be merged with resource reservations or it can be a separate process.
  • the DATA PATH process does not necessarily trigger after receiving step 1005.
  • the network can select the appropriate time and steps to trigger the DATA PATH setup.
  • Steps 1007 to 1010 The MS sequentially passes the SFM, the service SFA, and the anchor SFA, that is, the message flows through the DSA-RSP message, the RR-Response message, the RR-Response message, and the Diameter RAA/PD-Response/RR-Response message. A successful response to the establishment of the IMS signaling bearer for the visited PF/PCRF.
  • all the messages used for the response may also carry the IMS signaling bearer identifier, indicating that the IMS signaling bearer is successfully established.
  • the anchor SFA, or the service SFA, or the SFM may also decide whether the IMS signaling bearer can be established for the MS.
  • the home network PF/PCRF sends a request to carry the IMS bearer identifier directly or through the visited PF/PCRF to the anchor SFA, and in step 1004, or step 1005, or Step 1006: making a decision, and determining, according to the result of the decision, whether to establish an IMS signaling bearer for the terminal Then, the subsequent steps are performed in sequence, and the indication of whether the IMS signaling bearer is established for the terminal is sent.
  • the home network PF/PCRF carries the indication for acquiring the IMS-related configuration parameter directly or through the request of the visited PF/PCRF to the anchor SFA, and in step 1004, or step 1005, or step 1006, anchors the SFA, Or the service SFA, or SFM sends the IMS related configuration parameters along with the decision result to the MS.
  • whether the decision can establish an IMS signaling bearer for the MS can also be performed by the visited PF/PCRF; the IMS related configuration parameters can also be stored in the visited PF/PCRF.
  • the IMS signaling bearer identifier may not be carried in each message, but only the indication of obtaining the IMS-related configuration parameter or the IMS-related configuration parameter that is delivered, that is, the relevant configuration parameters of various services are obtained in this embodiment.
  • the method also applies to the existing bearer establishment process.
  • the user plane address ASN GW Address for user traffic and the control plane address ASN GW Address for Control Plane may be generated by the home network PF, the visited PF, the anchor SFA, or the service SFA, and sent to the network entity where the SFM is located.
  • the base station, the service flow separation between the user plane and the control plane is implemented by the SFM.
  • the process is sent to the network entity where the SFM is located through steps 1002 to 1005; if the two addresses are generated by the access PF, the process is sent to the network through steps 1003 to 1005.
  • the above is a description of the signaling bearer establishment method 4 in the present embodiment.
  • the signaling bearer establishment method 5 in the present embodiment will be described.
  • FIG. 11 is a flowchart of a signaling bearer establishing method 5 according to an embodiment of the present invention.
  • the establishment of the IMS signaling bearer initiated by the anchor SFA in the network side as the policy enforcement function entity is as follows.
  • the method 5 includes the following steps:
  • Step 1101 When the IMS service needs to be used, to speed up the IMS service establishment process, the IMS signaling bearer is set up for the MS before the IMS service establishment process, for example, the signaling bearer of the SIP session, and the service SFA initiates the establishment of the IMS due to an event trigger.
  • the signaling bearer, the service SFA cannot decide whether to establish an IMS signaling bearer for the MS, and sends an RR-Request message to the anchor SFA, and carries the IMS signaling bearer identifier in the message, requesting to establish a signaling bearer.
  • the IMS message carries the IMS message, so the bearer that is requested to be established is the IMS signaling bearer. If the IMS-related configuration parameters such as the P-CSCF address need to be provided to the MS, the service SFA obtains the IMS. The indication of the relevant configuration parameters is also carried in the RR-Request message.
  • Step 1102 The anchor SFA cannot decide whether to establish an IMS signaling bearer for the MS, and after receiving the RR-Request message from the serving SFA, send a Diameter CCR/PD-Request/RR-Request message to the home network PF/PCRF, and The IMS signaling bearer identifier is carried in the message, and the signaling bearer is requested to be established.
  • the anchor SFA directly requests the home network PF/PCRF to establish a signaling bearer; if the MS is in the visited network, the anchor SFA passes the visited PF/PCRF to the home network PF/PCRF. Requesting to establish a signaling bearer; if the RR-Request message carries an indication of obtaining an IMS-related configuration parameter, the anchor SFA also carries the indication in the Diameter CCR/PD-Request/RR-Request message.
  • Step 1103 The home network PF/PCRF stores the user subscription information, and the decision can be made.
  • the IMS signaling bearer is set up for the MS.
  • the decision is to establish an IMS signaling bearer for the MS, and decide whether to trigger the IMS signaling bearer according to the decision result.
  • the establishment of the Diameter CCA/PD-Response/RR-Response message carrying the IMS signaling identifier is sent to the anchor SFA, indicating whether the IMS signaling bearer is established for the MS, or the IMS signaling bearer is successfully established or failed.
  • the home network PF/PCRF carries the pre-stored IMS-related information such as the P-CSCF address to the Diameter.
  • the CCA/PD-Response/RR-Response message is sent to the anchor SFA; if the MS is in the home network, the home network PF/PCRF directly sends a Diameter CCA/PD-Response/RR-Response message to the anchor SFA to respond; The MS is in the visited network, and the home network PF/PCRF responds by sending a Diameter CCA/PD-Response/RR-Response message to the anchor SFA through the visited PF/PCRF.
  • Steps 1104 to 1106 Anchoring the SFA, the serving SFA, and the SFM, and determining whether to establish an IMS signaling bearer for the MS according to the received message carrying the IMS signaling bearer identifier, that is, whether the IMS signaling bearer is established for the MS. And transmitting an indication of whether to establish an IMS signaling bearer for the MS by using an RR-Response message, an RR-Request message, and a DSA-REQ message carrying the IMS signaling bearer identifier.
  • the service SFA requests the IMS-related configuration parameters such as the P-CSCF address to be provided to the MS by the indication of the IMS-related configuration parameter in step 1101, in the above step, the SFA, the service SFA, and the SFM are anchored, and the RR-Response message is sequentially passed.
  • the RR-Request message and the DSA-REQ message also send the IMS-related configuration parameters provided by the home network PF-PCRF to the MS.
  • step 1105 if the DATA PATH is established during the resource reservation phase, Then the service flow and DATA PATH are established at this time; if the data path DATA PATH has not been established, the network entity where the SFM is located triggers a DATA PATH establishment process, such as Path Pre-Registration Request or Path Registration in the DATA PATH setup message.
  • the request message carries the bearer identifier, that is, the IMS signaling bearer identifier in this embodiment.
  • the DATA PATH setup process can be merged with resource reservations or it can be a separate process.
  • the DATA PATH process does not necessarily trigger after receiving step 1105.
  • the network can select the appropriate time and steps to trigger the DATA PATH setup.
  • Step 1107 to step 1108 The MS successfully responds to the establishment of the IMS signaling bearer by using the SFM, that is, the message flow of the DSA-RSP message and the RR-Response message.
  • all the messages used for the response may also carry the IMS signaling bearer identifier, indicating that the IMS signaling bearer is successfully established.
  • the service SFA, or the anchor SFA, or the SFM may also decide whether the IMS signaling bearer can be established for the MS. According to the decision result, it is decided whether to establish an IMS signaling bearer for the terminal, and the home network PF/PCRF cannot make a decision. In this case, the decision is made in step 1101, or step 1102, step 1106, and then the steps are directly performed.
  • step 1105 or step 1104, or continue to perform the subsequent steps, and deliver an instruction of whether to establish an IMS signaling bearer for the terminal.
  • step 1101 If the GW in which the SFA is located, or the GW in which the SFA is anchored, or the SF-related configuration parameters such as the P-CSCF address and the DNS server address, but not in the home network PF/PCRF, In step 1101, or step 1102, or step
  • the service SFA, or the anchor SFA, or the SFM will immediately associate the IMS-related configuration parameters or Send to the MS along with the decision result.
  • the MS is in the visited network, whether the decision can establish an IMS signaling bearer for the MS can also be completed by the visited PF/PCRF; the IMS related configuration parameters can also be stored in the visited PF/PCRF.
  • the IMS signaling bearer identifier may not be carried in each message, but only the indication of obtaining the IMS-related configuration parameter or the IMS-related configuration parameter that is delivered, that is, the relevant configuration parameters of various services are obtained in this embodiment.
  • the method also applies to the existing bearer establishment process.
  • the user plane address ASN GW Address for user traffic and the control plane address ASN GW Address for Control Plane may be generated by the PF, the anchor SFA or the service SFA, and sent to the network entity where the SFM is located, for example, the base station, by the SFM. Separate the business flow between the user plane and the control plane.
  • the steps are sent to the network entity where the SFM is located through steps 1103 to 1104; if the two addresses are generated by the anchor SFA allocation, then the SFM is sent to the SFM through steps 1103 and 1104.
  • the above is a description of the signaling bearer establishment method 5 in the present embodiment.
  • the following describes the signaling bearer establishment method 6 in this embodiment.
  • FIG. 12 is a flowchart of a method 6 for establishing a payload in an embodiment of the present invention. As shown in Figure 12, the establishment of the IMS signaling bearer by the SFM as the service flow management entity on the network side is taken as an example. In the present embodiment, the method 6 includes the following steps:
  • Step 1201 When the IMS service needs to be used, to speed up the IMS service establishment process, the IMS signaling bearer is established for the MS before the IMS service establishment process, for example, the signaling bearer of the SIP session, and the SFM initiates the establishment of the IMS message due to an event trigger.
  • the bearer, SFM can't The decision is to establish an IMS signaling bearer for the MS, and send an RR-Request message to the serving SFA, and carry the IMS signaling bearer identifier in the message, requesting to establish a signaling bearer.
  • the bearer that is requested to be established is not the IMS service bearer but the IMS signaling bearer. If the IMS-related configuration parameters such as the P-CSCF address need to be provided to the MS, The indication of the IMS-related configuration parameters is also carried in the RR-Request message.
  • Step 1202 The serving SFA cannot determine whether to establish an IMS signaling bearer for the MS. After receiving the RR-Request message from the SFM, the service SFA sends an RR-Request message to the anchor SFA, and carries the IMS message with the identifier. Request to establish a letter
  • the service SFA After receiving the RR-Request message from the SFM, the service SFA sends an RR-Request message to the anchor SFA, and carries the IMS message with the identifier. Request to establish a letter
  • the service SFA also carries the indication in the RR-Request message sent to the anchor SFA.
  • Step 1203 The anchor SFA cannot decide whether to establish an IMS signaling bearer for the MS, and after receiving the RR-Request message from the serving SFA, send a Diameter CCR/PD-Request/RR-Request message to the home network PF/PCRF, and The IMS signaling bearer identifier is carried in the message, and the signaling bearer is requested to be established.
  • the anchor SFA directly requests the home network PF/PCRF to establish a signaling bearer; if the MS is in the visited network, the anchor SFA passes the visited PF/PCRF to the home network PF/PCRF. Requesting to establish a signaling bearer; if the RR-Request message carries an indication of obtaining an IMS-related configuration parameter, the anchor SFA also carries the indication in the Diameter CCR/PD-Request/RR-Request message.
  • Step 1204 The home network PF/PCRF stores the user subscription information, and can determine whether to establish an IMS signaling bearer for the MS. After receiving the Diameter CCR/PD-Request/RR-Request message from the anchor SFA, the decision is whether the MS is the MS. Establish an IMS signaling bearer, and decide whether to trigger the establishment of the IMS signaling bearer according to the decision result, and carry the IMS The signaling of the Diameter CCA/PD-Response/RR-Response message is sent to the anchor SFA, indicating whether the IMS signaling bearer is established for the MS, or the IMS signaling bearer is successfully established or failed.
  • the home network PF/PCRF carries the pre-stored IMS-related information such as the P-CSCF address to the Diameter.
  • the CCA/PD-Response/RR-Response message is sent to the anchor SFA; if the MS is in the home network, the home network PF/PCRF directly sends a Diameter CCA/PD-Response/RR-Response message to the anchor SFA to respond; The MS is in the visited network, and the home network PF/PCRF responds by sending a Diameter CCA/PD-Response/RR-Response message to the anchor SFA through the visited PF/PCRF.
  • Steps 1205 to 1207 Anchoring the SFA, the service SFA, and the SFM, and determining whether to establish an IMS signaling bearer for the MS according to the received message carrying the IMS signaling bearer identifier, that is, whether the IMS signaling bearer is established for the MS. And transmitting an indication of whether the IMS signaling bearer is established for the MS by using the RR-Response message, the RR-Response message, and the DSA-REQ message, which are carried by the IMS signaling.
  • the service SFA requests the IMS-related configuration parameters such as the P-CSCF address to be provided to the MS by the indication of the IMS-related configuration parameter in step 1101, in the above step, the SFA, the service SFA, and the SFM are anchored, and the RR-Response message is sequentially passed.
  • the RR-Request message and the DSA-REQ message also send the IMS-related configuration parameters provided by the home network PF-PCRF to the MS.
  • the service flow and the DATA PATH are established at this time; if the data path DATA PATH has not been established, the network entity where the SFM is located triggers a DATA PATH establishment process.
  • the DATA PATH setup message such as Path Pre-Registration Request or Path
  • the registration request message carries the bearer identifier, that is, the IMS signaling bearer identifier in this embodiment.
  • the DATA PATH setup process can be merged with resource reservations or it can be a separate process.
  • the DATA PATH process does not necessarily trigger after receiving step 1206.
  • the network can select the appropriate time and steps to trigger the DATA PATH setup.
  • Step 1208 The MS successfully responds to the SFM by using the DSA-RSP message to perform IMS signaling loading.
  • all the messages used for the response may also carry the IMS bearer identifier, indicating that the IMS signaling bearer is successfully established.
  • the SFM, or the service SFA, or the anchor SFA can also decide whether the IMS information can be established for the MS. In this case, the decision is made in step 1201, or step 1202, step 1203, and according to the decision result, it is determined whether to establish an IMS signaling bearer for the terminal, and then directly perform step 1207, or step 1206, or step 1205, step by step. Whether to send an indication of the IMS signaling bearer for the terminal.
  • the SFM, or the serving SFA, or the anchor SFA sends the IMS-related configuration parameters to the MS either immediately or with the decision result.
  • the MS is in the visited network, whether the decision can establish an IMS signaling bearer for the MS can also be completed by the visited PF/PCRF; the IMS related configuration parameters can also be stored in the visited PF/PCRF.
  • each message may also not carry the IMS signaling bearer identifier, but only carry
  • the method for obtaining the IMS-related configuration parameters or the IMS-related configuration parameters that are delivered, that is, the method for obtaining the relevant configuration parameters of the various services in this embodiment is also applicable to the existing bearer establishment process.
  • the user plane address ASN GW Address for user traffic and the control plane address ASN GW Address for Control Plane may be generated by the PF, the anchor SFA or the service SFA, and sent to the network entity where the SFM is located, for example, the base station, by the SFM. Separate the business flow between the user plane and the control plane.
  • the two addresses are generated by the PF allocation, they are sent to the network entity where the SFM is located through steps 1204 to 1206; if the two addresses are generated by the anchor SFA allocation, then the SFM is sent to the SFM through steps 1205 and 1206. The network entity; if the two addresses are generated by the service SFA allocation, then it is sent to the network entity where the SFM is located via step 1206.
  • the bearer establishment method 7 in this embodiment is implemented by adding an agent/proxy to the system and according to the initiation and decision mode of the bearer establishment method 1.
  • FIG. 13 is a flowchart of a method 7 for establishing a letter in the embodiment of the present invention. As shown in FIG. 13, the method for establishing the IMS signaling bearer is initiated by the MS, and the system includes the agent/proxy.
  • the signaling bearer establishing method 7 in this embodiment includes the following steps:
  • Step 1301 When the IMS service needs to be used, to speed up the IMS service establishment process, the IMS signaling bearer is established for the MS before the IMS service establishment process, for example, the signaling bearer of the Session Initiated Protocol (SIP) session, MS direction
  • SIP Session Initiated Protocol
  • the SFM sends a DSA-REQ message, and carries the IMS signaling bearer identifier in the message, requesting to establish a signaling bearer.
  • the DSA-REQ message also carries an indication for obtaining the IMS-related configuration parameter.
  • Step 1302 The SFM cannot determine whether to establish an IMS signaling bearer for the MS. After receiving the DSA-REQ message from the MS, the SFM sends an RR-Request message to the serving SFA, and carries the IMS signaling bearer identifier in the message, requesting to establish Signaling bearer.
  • the SFM also carries the indication in the RR-Request message.
  • Step 1303 The service SFA cannot determine whether to establish an IMS signaling bearer for the MS. After receiving the RR-Request message from the SFM, the service SFA sends an RR-Request message to the anchor SFA, and carries the IMS signaling bearer identifier in the message. Request to establish a signaling bearer.
  • the service SFA also carries the indication in the RR-Request message sent to the anchor SFA.
  • Step 1304 The anchor SFA cannot decide whether to establish an IMS signaling bearer for the MS. After receiving the RR-Request message from the serving SFA, send a Diameter CCR/RR-Request/PD-Request message to the Agent/Proxy, and The message carries the IMS signaling bearer identifier, and requests to establish a signaling bearer.
  • the anchor SFA also carries the indication to the Diameter CCR/ sent to the Agent/Proxy. In the RR-Request/PD-Request message.
  • Step 1305 The Agent/Proxy acts as a relay and a proxy, and cannot decide whether to establish an IMS signaling bearer for the MS.
  • the Agent/Proxy In this step, if the MS is in the home network, the Agent/Proxy directly requests the home network PF/PCRF to establish a signaling bearer. If the MS is in the visited network, the Agent/Proxy accesses the home network PF/PCRF through the visited PF/PCRF. Requesting to establish a signaling payload; If the RR-Request message carries an indication of obtaining an IMS-related configuration parameter, the Agent/Proxy also carries the indication in the Diameter CCR/PD-Request/RR-Request message.
  • Step 1306 The home network PF/PCRF stores the user subscription information, and can determine whether to establish an IMS signaling bearer for the MS. After receiving the Diameter CCR/PD-Request/RR-Request message from the Agent/Proxy, the decision is whether the MS is the MS. Establish an IMS signaling bearer, and determine whether to trigger the establishment of the IMS signaling bearer according to the result of the decision, and send a Diameter CCA/PD-Response/RR-Response message carrying the IMS signaling bearer identifier to the Agent/Proxy, indicating whether the MS is established for the MS. The IMS signaling bearer, or the IMS signaling bearer is successfully established or failed.
  • the home network PF/PCRF also carries the pre-stored IMS-related information such as the P-CSCF address.
  • the Diameter CCA/PD-Response/RR-Response message is provided to the MS; if the MS is in the home network, the home network PF/PCRF directly sends a Diameter CCA/PD-Response/RR-Response message to the Agent/Proxy to respond; The MS is in the visited network, and the home network PF/PCRF responds by sending a Diameter CCA/PD-Response/RR-Response message to the Agent/Proxy through the visited PF/PCRF.
  • Steps 1307 to 1310 The agent/proxy, the anchor SFA, the service SFA, and the SFM are sequentially determined according to the received message carrying the IMS signaling bearer identifier, that is, whether the IMS signaling bearer is established for the MS, and whether the MS is established for the MS.
  • the Agent/Proxy, the anchor SFA, the monthly service SFA, and the SFM are sequentially passed through the RR- The Response message, the RR-Response message, the RR-Response message, and the DSA-RSP message also send the IMS-related configuration parameters provided by the PF/PCRF to the MS.
  • the network entity where the SFM is located triggers a DATA PATH establishment process.
  • the DATA PATH setup message for example, the Path Pre-Registration Request or the Path Registration Request message carries the bearer identifier, that is, the IMS signaling bearer identifier in this embodiment.
  • the DATA PATH setup process can be merged with resource reservations or it can be a separate process.
  • the DATA PATH process does not necessarily trigger after receiving step 1309.
  • the network can select the appropriate time and steps to trigger the DATA PATH setup.
  • the SFM, or the service SFA, or the anchor SFA may also decide whether the IMS signaling bearer can be established for the MS. In this case, the decision is made in step 1302, or step 1303, or step 1304, and the request is no longer sent, and the IMS signaling bearer is established for the terminal according to the decision result, and then step 1310, or step 1309, or directly In step 1308, an indication of whether to establish an IMS signaling bearer for the terminal is sent.
  • the SFM, or the GW where the service SFA is located, or the GW where the SFA is anchored If there are IMS-related configuration parameters such as the P-CSCF address and the DNS server address, then in step 1302, or step 1303, or step 1304, the SFM, or the service SFA, or the anchor SFA does not need to request to obtain the IMS-related configuration parameters, but The IMS-related configuration parameters are sent to the MS immediately or through the RR-Response message through the DSA-RSP message, or through the RR-Response message, or through the RR-Response message.
  • IMS-related configuration parameters such as the P-CSCF address and the DNS server address
  • the MS is in the visited network, whether the decision can establish an IMS signaling bearer for the MS can also be completed by the visited PF/PCRF; the IMS related configuration parameters can also be stored in the visited PF/PCRF.
  • the IMS signaling bearer identifier may not be carried in each message, but only the indication of obtaining the IMS-related configuration parameter or the IMS-related configuration parameter that is delivered, that is, the relevant configuration parameters of various services are obtained in this embodiment.
  • the method also applies to the existing bearer establishment process.
  • the user plane address ASN GW Address for user traffic and the control plane address ASN GW Address for Control Plane may be generated by the PF, the anchor SFA or the service SFA, and sent to the network entity where the SFM is located, for example, the base station, by the SFM. Separate the business flow between the user plane and the control plane.
  • the process is sent to the network entity where the SFM is located through steps 1306 to 1309; if the two addresses are generated by the anchor SFA allocation, then the process is sent to the SFM through steps 1308 and 1309.
  • FIG. 14 is a flowchart of a signaling bearer establishing method 8 according to an embodiment of the present invention.
  • the home network PF/PCRF which is a policy decision function entity in the network side, initiates the establishment of the IMS signaling bearer, and the system includes the agent/proxy as an example.
  • the signaling bearer establishment method 8 includes the following steps:
  • Step 1401 When the IMS service needs to be used, to speed up the IMS service establishment process, the IMS signaling bearer is established for the MS before the IMS service establishment process, for example, the signaling bearer of the SIP session, triggered by an event, the home network PF/PCRF Initiating the establishment of the IMS signaling bearer, the home network PF/PCRF stores the user subscription information, determines whether the IMS signaling bearer is established for the MS, determines whether to trigger the establishment of the IMS signaling bearer according to the decision result, and carries the IMS signaling bearer identifier.
  • the PD-Request/RR-Request message is sent to the Agent/Proxy, indicating whether the IMS signaling bearer is established, or the IMS signaling bearer is successfully established or failed.
  • the home network PF/PCRF carries the indication of the pre-stored IMS-related configuration parameter in the Diameter RAR/RR-Request/PD-Request message. If the MS is in the home network, the home network PF/PCRF sends a Diameter RAR/RR-Request/PD-Request message directly to the Agent/Proxy; if the MS is in the visited network, the home network PF/PCRF passes the visited PF/PCRF. Send a Diameter RAR/RR-Request/PD-Request message to the Agent/Proxy.
  • Steps 1402 to 1405 The agent/proxy, the anchor SFA, the service SFA, and the SFM are sequentially determined according to the received message carrying the IMS signaling bearer identifier, that is, whether the IMS signaling bearer is established for the MS, and whether the MS is established for the MS.
  • the IMS signaling bearer sends an indication of whether the IMS signaling is established for the MS to the MS through the RR-Request message, the RR-Request message, the RR-Request message, and the DSA-REQ message.
  • the home network PF/PCRF provides IMS-related configuration parameters
  • the SFA, the service SFA, and the SFM are anchored, and the RR-Request message and the RR-Request are sequentially passed.
  • the message and the DSA-REQ message also send the IMS related configuration parameters to the MS.
  • step 1401 and step 1402 is a Diameter RAR message
  • the message needs to be processed by one of the following two processing modes before step 1403: 1. Modify the RAR message to complete a PD-like operation. The function of the Request/RR-Request message; 2. After receiving the Diameter RAR message, the anchor SFA initiates a Diameter CCR message to the PF, and the PF initiates a Diameter CCA message to the SFA, and then performs step 1403.
  • Steps 1406 to 1410 The MS sequentially passes the SFM, the service SFA, the anchor SFA, and the Agent/Proxy, that is, the DSA-RSP message, the RR-Response message, the RR-Response message, and the Diameter RAA/RR-Response/PD-Response message.
  • the message flow of the Diameter RAA/RR-Response/PD-Response message is used to establish a successful response to the IMS signaling of the home network PF/PCRF.
  • all the messages used for the response may also carry the IMS signaling bearer identifier, indicating that the IMS signaling bearer is successfully established.
  • the network entity in which the SFM is located triggers a DATA
  • the PATH establishment process in the DATA PATH setup message, for example, the Path Pre-Registration Request or the Path Registration Request message, carries the bearer identifier, that is, the IMS signaling bearer identifier in this embodiment.
  • the DATA PATH setup process can be merged with resource reservations or it can be a separate process.
  • the DATA PATH process does not necessarily trigger after receiving step 1404 or step 1406.
  • the network can select the appropriate time and step to trigger the DATA PATH setup.
  • the anchor SFA, or the service SFA, or the SFM can also be determined. Whether an IMS signaling bearer can be established for the MS.
  • step 1401 to step 1402 the home network PF/PCRF sends a request for carrying the IMS signaling bearer identifier to the anchor SFA through the Agent/Proxy or through the visited PF/PCRF and the Agent/Proxy, and
  • step 1403, or step 1404, or step 1405 a decision is made, and whether the IMS signaling bearer is established for the terminal is determined according to the result of the decision, and then the subsequent steps are sequentially performed to deliver an indication of whether the IMS signaling bearer is established for the terminal.
  • the home network PF/PCRF carries an indication for acquiring the IMS related configuration parameter in the request sent by the anchor SFA through the Agent/Proxy or the visited PF/PCRF and the Agent/Proxy, and in step 1403, or step 1404, or step 1405, the anchor SFA, or the service SFA, or the SFM sends the IMS related configuration parameters along with the decision result to the MS.
  • the MS is in the visited network, whether the decision can establish an IMS signaling bearer for the MS can also be completed by the visited PF/PCRF; the IMS related configuration parameters can also be stored in the visited PF/PCRF.
  • the IMS signaling bearer identifier may not be carried in each message, but only the indication of obtaining the IMS-related configuration parameter or the IMS-related configuration parameter that is delivered, that is, the relevant configuration parameters of various services are obtained in this embodiment.
  • the method also applies to the existing bearer establishment process.
  • the user plane address ASN GW Address for user traffic and the control plane address ASN GW Address for Control Plane may be generated by the PF, the anchor SFA or the service SFA, and sent to the network entity where the SFM is located, for example, the base station, by the SFM. Separate the business flow between the user plane and the control plane.
  • step 1404 the process proceeds from step 1401 to step 1404.
  • the network entity where the SFM is located if the two addresses are generated by the anchor SFA allocation, then the network entity where the SFM is located is sent through step 1403 and step 1404; if the two addresses are generated by the service SFA, then Step 1404 is sent to the network entity where the SFM is located.
  • the signaling bearer establishing method 7 and the signaling bearer establishing method 8 describe the procedure for establishing the IMS signaling bearer initiated by the MS and the home network PF/PCRF only when the system includes the Agent/Proxy. If the establishment of the bearer is initiated by other entities on the network side, the specific implementation principle is the same as the signaling bearer establishing method 7 and the signaling bearer establishing method 8.
  • Agent/Proxy is added to the system, and the Agent/Proxy receives and sends the request message and the response message according to the working mode of the anchor SFA, and other types can be implemented based on the signaling bearer establishment methods 2, 4, 5, and 6. Including the agent / Proxy ⁇ ⁇ load establishment method.
  • the bearer bearer identifier is sent, that is, the indication of the IMS signaling bearer in the embodiment is carried, and At the same time, QoS information and/or charging information related to the signaling flow is delivered, and a higher QoS level is set for signaling corresponding to the bearer identifier, such as IMS signaling.
  • the MS, and the network entity where the SFM, the service SFA, the anchor SFA, and the PF/PCRF are located can distinguish the bearer type, that is, the bearer, according to different combinations of the bearer identifier, the MS ID, the SFID, and the DATA PATH. What kind of service is the signalling bearer.
  • the functional units in the system for establishing a bearer in this embodiment may perform bearer establishment according to the principles described in the foregoing process.
  • the bearer to be established is not an IMS signaling bearer, but is, for example, an IMS service bearer or a signaling bearer or a service bearer of the WIMAX MBS or the WIMAX LCS
  • Other types of bearers can be implemented by replacing the IMS signaling bearer identifiers in the system and the process with the IMS service bearer identifier, the WIMAX MBS signaling bearer identifier, or the service bearer identifier.
  • the indications of the relevant configuration parameters of the service are required to be carried in the request.
  • the above-mentioned system and method are used to obtain the parameters.
  • the bearer to be established is a normal bearer, that is, the bearer identifier is not included in the request, the service configuration parameter may be delivered to the terminal by carrying the foregoing indication. If no IMS-related configuration parameters are requested, the IMS-related configuration parameters may not be carried in all response messages sent by the network.
  • the relevant configuration parameters are WIMAX MBS related configuration parameters
  • the parameters include: P-CSCF address, DNS server address, WIMAX MBS server address, WIMAX LCS server address, etc., which need to be carried in the service flow message or data path message.
  • a request message carrying an IMS signaling bearer identifier may be sent by any one of a network element such as a terminal, an SFM, an SFA, or a PF/PCRF, thereby implementing IMS signaling.
  • a network element such as a terminal, an SFM, an SFA, or a PF/PCRF.
  • the establishment of bearers accelerates the establishment of subsequent IMS services.
  • the network side can carry the IMS-related configuration parameter in the response message and send it to the terminal. Therefore, the terminal can acquire the parameter in the bearer establishment process.
  • the PF, the anchor SFA, or the service SFA may also be assigned to generate a user plane address ASN GW Address for user traffic and a control plane address ASN GW Address for Control Plane, and send to the network entity where the SFM is located, such as a base station, so that the SFM can implement the user.
  • the business flow of the face and control plane is separated.
  • a system, apparatus and method are also suitable for establishing bearer service.

Abstract

Procédé pour l'établissement d'un support de signalisation. Dans des modes de réalisation de la présente invention, le procédé consiste à envoyer le message contenant l'identificateur afin d'établir le support privé de signalisation. Des modes de réalisation de l'invention portent également sur un système et un appareil d'établissement de support de signalisation. La durée nécessaire à l'établissement du service, tel qu'un service IMS, un service WIMAX MBS est réduite via l'établissement du support privé destiné à la transmission de certains types de signalisation, parallèlement, dans le schéma de l'invention, l'entité côté réseau et le terminal peuvent initier l'établissement du support, le schéma présenté dans les modes de réalisation étant alors universel. Au cours de l'établissement du support, les paramètres de configuration comprenant les informations d'adresse P-CSCF, l'adresse de serveur DNS, l'adresse de serveur WIMAX MBS, peuvent être distribués au terminal depuis le côté réseau.
PCT/CN2007/070841 2007-01-25 2007-09-29 Procédé, système et appareil pour l'établissement d'un support de signalisation WO2008092346A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN 200710000391 CN101232433A (zh) 2007-01-25 2007-01-25 信令承载建立方法和建立信令承载的系统及装置
CN200710000391.7 2007-01-25

Publications (1)

Publication Number Publication Date
WO2008092346A1 true WO2008092346A1 (fr) 2008-08-07

Family

ID=39673646

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2007/070841 WO2008092346A1 (fr) 2007-01-25 2007-09-29 Procédé, système et appareil pour l'établissement d'un support de signalisation

Country Status (2)

Country Link
CN (1) CN101232433A (fr)
WO (1) WO2008092346A1 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015010325A1 (fr) * 2013-07-26 2015-01-29 华为技术有限公司 Procédé et appareil de transmission de données
CN107889171A (zh) * 2016-09-30 2018-04-06 华为技术有限公司 无线通信方法、用户设备和接入网设备
CN108184206A (zh) * 2012-08-31 2018-06-19 高通股份有限公司 基于演进型多媒体广播/多播服务地理位置的群组呼叫
CN108605320A (zh) * 2016-03-30 2018-09-28 Oppo广东移动通信有限公司 用于建立无线资源控制连接的方法和装置

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102149214B (zh) 2010-02-05 2015-05-13 中兴通讯股份有限公司 一种通信系统中的数据传输方法和系统
US20130137469A1 (en) * 2011-11-30 2013-05-30 Intel Mobile Communications GmbH Method for transmitting an opportunistic network related message
CN103428768B (zh) * 2012-05-16 2016-12-14 华为技术有限公司 一种接入方法、基站、接入点和用户设备
CN103975642B (zh) * 2012-11-22 2018-08-21 华为技术有限公司 一种短距离通信的方法、设备和系统

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1296715A (zh) * 1998-04-03 2001-05-23 诺基亚网络有限公司 与移动台建立信令连接的方法
CN1812356A (zh) * 2005-01-25 2006-08-02 中兴通讯股份有限公司 一种自适应匹配信令连接的方法
US20060291403A1 (en) * 2005-05-27 2006-12-28 Jussi Kahtava Expanded signalling capability for network element, user equipment and system

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1296715A (zh) * 1998-04-03 2001-05-23 诺基亚网络有限公司 与移动台建立信令连接的方法
CN1812356A (zh) * 2005-01-25 2006-08-02 中兴通讯股份有限公司 一种自适应匹配信令连接的方法
US20060291403A1 (en) * 2005-05-27 2006-12-28 Jussi Kahtava Expanded signalling capability for network element, user equipment and system

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108184206A (zh) * 2012-08-31 2018-06-19 高通股份有限公司 基于演进型多媒体广播/多播服务地理位置的群组呼叫
CN108184206B (zh) * 2012-08-31 2020-08-14 高通股份有限公司 基于演进型多媒体广播/多播服务地理位置的群组呼叫
WO2015010325A1 (fr) * 2013-07-26 2015-01-29 华为技术有限公司 Procédé et appareil de transmission de données
CN104995875A (zh) * 2013-07-26 2015-10-21 华为技术有限公司 数据传输方法及装置
CN108605320A (zh) * 2016-03-30 2018-09-28 Oppo广东移动通信有限公司 用于建立无线资源控制连接的方法和装置
CN108605320B (zh) * 2016-03-30 2023-03-14 Oppo广东移动通信有限公司 用于建立无线资源控制连接的方法和装置
CN107889171A (zh) * 2016-09-30 2018-04-06 华为技术有限公司 无线通信方法、用户设备和接入网设备
CN107889171B (zh) * 2016-09-30 2023-10-20 华为技术有限公司 无线通信方法、用户设备和接入网设备

Also Published As

Publication number Publication date
CN101232433A (zh) 2008-07-30

Similar Documents

Publication Publication Date Title
US8483686B2 (en) Method and communication system for deleting address of network anchor point from network server
US8442522B2 (en) Detection and report of limited policy and charging control capabilities
US8621555B2 (en) Access control method and system for packet data network, PCRF entity
US8364114B2 (en) Emergency and priority calling support in WiMAX
US20100048161A1 (en) Method, system and apparatuses thereof for realizing emergency communication service
WO2008092346A1 (fr) Procédé, système et appareil pour l'établissement d'un support de signalisation
WO2009024048A1 (fr) Procédé, système de réseau, passerelle pdn et système de comptabilité pour gérer une comptabilité
WO2010052030A1 (fr) Appareil de commande de politique et procédé de transfert d'informations de commande de politique
WO2008086754A1 (fr) Procédé, dispositif et système pour l'enregistrement émergent dans un réseau d'accès par connexion ip de l'équipement utilisateur
EP2052513B1 (fr) Gestion de politique dans des scénarios multi-accès
WO2010121460A1 (fr) Procédé pour mettre en oeuvre une commande de politique et de facturation limitée et système associé
WO2011063688A1 (fr) Procédé et système de sélection d'entité à fonction de règles de politique et de facturation
WO2011098155A1 (fr) Procédé et appareil destinés à être utilisés avec un réseau d'accès à connectivité ip
WO2008043307A1 (fr) Procédé, dispositif et système de taxation commune
WO2011018020A1 (fr) Procede et systeme de commande d'equilibre de charge de pcrf et dra de redirection
US8229391B2 (en) Method, apparatus and system for managing emergency services of mobility-restricted mobile station
WO2013135213A1 (fr) Procédé de traitement de session tdf et pcrf
WO2010118673A1 (fr) Procédé, système et dispositif de gestion du contrôle des règles d'utilisation et de facturation
WO2009103244A1 (fr) Procédé et système de configuration de service de diffusion/multidiffusion dans un réseau sans fil
WO2010043095A1 (fr) Procédé de traitement d’échec d’inscription d’un utilisateur et unité de gestion de mobilité associée
WO2010127530A1 (fr) Procédé et système d'établissement de service d'un sous-système multimédia par internet
WO2012155774A1 (fr) Procédé, système d'établissement d'une sous-session s9, et fonction "règles de politique et de facturation"
WO2008061477A1 (fr) Système et procédé de commande de facturation d'une structure de commande de facturation de politique de fusion de réseau
WO2008131695A1 (fr) Procédé, dispositif et système de contrôle de conditions d'utilisation et de facturation dans un système de communication sans fil
US20130097326A1 (en) Visited pcrf s9 session id generation

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 07817032

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 07817032

Country of ref document: EP

Kind code of ref document: A1