WO2010121511A1 - 多网接入控制方法、通讯系统以及相关设备 - Google Patents

多网接入控制方法、通讯系统以及相关设备 Download PDF

Info

Publication number
WO2010121511A1
WO2010121511A1 PCT/CN2010/071147 CN2010071147W WO2010121511A1 WO 2010121511 A1 WO2010121511 A1 WO 2010121511A1 CN 2010071147 W CN2010071147 W CN 2010071147W WO 2010121511 A1 WO2010121511 A1 WO 2010121511A1
Authority
WO
WIPO (PCT)
Prior art keywords
user terminal
multiple access
access
indication information
information
Prior art date
Application number
PCT/CN2010/071147
Other languages
English (en)
French (fr)
Inventor
胡颖
王珊珊
王宁沈
Original Assignee
华为技术有限公司
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 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP10766601.8A priority Critical patent/EP2410701B1/en
Priority to ES10766601.8T priority patent/ES2526565T3/es
Priority to BRPI1016177-5A priority patent/BRPI1016177B1/pt
Priority to JP2012506316A priority patent/JP5379297B2/ja
Publication of WO2010121511A1 publication Critical patent/WO2010121511A1/zh
Priority to US13/243,142 priority patent/US8718031B2/en

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/10Connection setup
    • H04W76/15Setup of multiple wireless link connections
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W8/00Network data management
    • H04W8/22Processing or transfer of terminal data, e.g. status or physical capabilities
    • H04W8/24Transfer of terminal data
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W88/00Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02Terminal devices
    • H04W88/06Terminal devices adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W88/00Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08Access point devices
    • H04W88/10Access point devices adapted for operation in multiple networks, e.g. multi-mode access points

Definitions

  • Multi-network access control method communication system and related equipment
  • the present invention relates to the field of communications, and in particular, to a multi-network access control method, a communication system, and related devices.
  • BACKGROUND When a user terminal supporting multiple access functions moves from a non-3GPP network to a common coverage area of a non-3GPP network and a 3GPP network, if the user terminal intends to switch part of the service to the 3GPP network, part of the service remains in the non - 3GPP network, the user terminal will initiate a connection establishment on the 3GPP network.
  • a user terminal supporting multiple access functions has a packet data network (PDN) connection, and accesses a packet data network through a packet data network gateway (PGW, PDN Gate Way), and the user terminal intends to connect the PDN.
  • PDN packet data network
  • the user terminal If a part of the service flow is switched to the 3GPP network, the user terminal establishes a new PDN connection in the 3GPP network. If the PGW does not support the multiple access function, the PGW releases the user terminal and the PDN connection on the PGW. Resources, which will cause the user terminal to use the multi-access function, some of the services in the PDN connection that are not switched to the 3GPP network are interrupted, thereby affecting normal network communication. Summary of the invention
  • the embodiments of the present invention provide a multi-network access control method, a communication system, and related devices, which can ensure normal network communication is not interrupted when using multiple access functions.
  • the multi-network access control method provided by the embodiment of the present invention includes: the user terminal receives the multiple access indication information sent by the network side device; the user terminal determines, according to the multiple access indication information, whether the user terminal uses the multiple access function; The terminal initiates a multi-network access connection establishment when using the multi-access function.
  • the network access control method provided by the embodiment of the present invention includes: the network side device receives the request message sent by the user terminal; the network side device acquires the multiple access capability information of each data gateway; And selecting, according to the multiple access capability information of each data gateway, a data gateway supporting the multiple access function to provide a service for the user terminal.
  • the communication system provided by the embodiment of the present invention includes: a network side device, configured to acquire multiple access indication information, and send the multiple access indication information to a user terminal; and the user terminal is configured to receive multiple access sent by the network side device. And indicating, according to the multiple access indication information, determining whether the user terminal uses the multiple access function, and initiating the multiple network access connection establishment request when using the multiple access function.
  • the communication system includes: a network side device, configured to receive a request message sent by a user terminal, obtain multiple access capability information of each data gateway, and select support according to multiple access capability information of each data gateway.
  • a multi-access function data gateway provides a service to the user terminal;
  • a data gateway configured to provide the network side device with multiple access capability information of the data gateway; and
  • a user terminal configured to send to the network side device Request message.
  • the network side device provided by the embodiment of the present invention includes: an acquiring unit, configured to acquire multiple access indication information; a sending unit, configured to send the multiple access indication information to the user terminal, where the multiple access indication information is used Indicates whether the user terminal allows the use of multiple access functions.
  • the network side device includes: a request receiving unit, configured to receive a request message sent by the user terminal, an information acquiring unit, configured to acquire multiple access capability information of each data gateway, and a selecting unit, configured to The multiple access capability information of each data gateway selects a data gateway supporting multiple access functions to provide services for the user terminal.
  • the user terminal provided by the embodiment of the present invention includes: an information receiving unit, configured to receive multiple access indication information sent by the network side device; and an information verification unit, configured to determine, according to the multiple access indication information, whether the user terminal uses more Access function; a multi-network access unit, configured to initiate a multi-network access connection establishment request when using the multi-access function.
  • the user terminal provided by the embodiment of the present invention includes: an indication information determining unit, configured to determine whether the user terminal receives the unauthorized indication information or the selection failure information sent by the network side device, where the unauthorized indication information is used to indicate the user The terminal is not authorized to access multiple times, and the selection failure information is used to indicate that the user terminal does not allow the multi-access function; the multi-network access unit is configured to not receive the unlicensed The right indication information and the selection failure information initiate a multi-network access connection establishment request.
  • the embodiments of the present invention have the following advantages:
  • the user terminal may obtain multiple access indication information from the network side device, and determine whether the user terminal can use the multiple access function by using the multiple access indication information, and determine that the user terminal can use multiple access
  • the user terminal initiates the multi-network access connection establishment request. Therefore, when the user terminal uses the multi-access function to switch some services of the PDN connection to the 3GPP network, other services that do not switch to the 3GPP network can also be maintained at the same time. Normal communication, so that normal network communication is not interrupted;
  • the network side device after receiving the request of the user terminal, selects a data gateway capable of supporting multiple access functions from each of the current data gateways to provide services for the user terminal, thereby enabling the user terminal to be a user terminal.
  • the data gateway providing the service can support the multiple access function, so when the user terminal uses the multiple access function, after some services in the PDN connection are switched to the 3GPP network, other services that do not switch to the 3GPP network can maintain normal communication at the same time, thereby Ensure that normal network communication is not interrupted.
  • FIG. 1 is a schematic diagram of an embodiment of a multi-network access control method according to an embodiment of the present invention
  • FIG. 2 is a schematic diagram of another embodiment of a multi-network access control method according to an embodiment of the present invention.
  • FIG. 3 is a schematic diagram of another embodiment of a multi-network access control method according to an embodiment of the present invention.
  • FIG. 4 is a schematic diagram of another embodiment of a multi-network access control method according to an embodiment of the present invention.
  • FIG. 5 is a schematic diagram of another embodiment of a multi-network access control method according to an embodiment of the present invention.
  • FIG. 6 is a schematic diagram of another embodiment of a multi-network access control method according to an embodiment of the present invention.
  • FIG. 7 is a schematic diagram of another embodiment of a multi-network access control method according to an embodiment of the present invention.
  • FIG. 8 is a schematic diagram of another embodiment of a multi-network access control method according to an embodiment of the present invention.
  • FIG. 9 is a schematic diagram of another embodiment of a multi-network access control method according to an embodiment of the present invention.
  • FIG. 10 is a schematic diagram of an embodiment of a communication system according to an embodiment of the present invention
  • FIG. 11 is a schematic diagram of another embodiment of a communication system according to an embodiment of the present invention
  • FIG. 10 is a schematic diagram of an embodiment of a communication system according to an embodiment of the present invention
  • FIG. 11 is a schematic diagram of another embodiment of a communication system according to an embodiment of the present invention.
  • FIG. 12 is a schematic diagram of an embodiment of a network side device according to an embodiment of the present invention.
  • FIG. 13 is a schematic diagram of another embodiment of a network side device according to an embodiment of the present disclosure.
  • FIG. 14 is a schematic diagram of an embodiment of a user terminal according to an embodiment of the present invention.
  • FIG. 15 is a schematic diagram of another embodiment of a user terminal according to an embodiment of the present invention. detailed description
  • Embodiments of the present invention provide a multi-network access control method, a communication system, and related devices, which are used to ensure that normal network communication is not interrupted when multiple access functions are used.
  • an embodiment of a method for controlling multiple network access in an embodiment of the present invention includes:
  • the user terminal receives multiple access indication information sent by the network side device.
  • the user terminal may receive the multiple access indication information from the network side device, where the multiple access indication information is used to indicate whether the network side supports the multiple access function, and the multiple access indication information may specifically be the network side capability.
  • the information, or directly indicates whether the network side supports the multi-access function.
  • the user terminal may send a request message to the network side device to request to obtain the multiple access indication information, or the user terminal may further receive multiple access indication information that is sent by the network side device, such as a network.
  • the side device automatically broadcasts the current multiple access indication information to the user terminal at a certain interval, or when the network side device detects that the network side capability changes, the current multi-access indication information is broadcast to the user terminal, or is satisfied.
  • the network side device may broadcast the current multiple access indication information to the user terminal, and the specific conditions are not limited herein.
  • the user terminal determines whether to use the multi-access function according to the multi-access indication information, if yes, step 103 is performed, and if not, step 104 is performed;
  • the user terminal may determine whether the current network side supports the multiple access function according to the multiple access indication information. It should be noted that the user terminal may further determine whether the user terminal supports the multiple access function. Multi-access function, if the network side supports multiple access functions, and the user terminal also supports multiple access functions, it is determined that multiple access functions can be used, and step 103 can be performed, if the network The side does not support the multi-access function, or the user terminal does not support the multi-access function, and then determines that the multi-access function cannot be used, and step 104 can be performed;
  • the user terminal can only determine whether the network side supports the multiple access function. If it is supported, it can be determined that the multiple access function can be used, and step 103 can be performed. If not, it is determined that the multiple access function cannot be used. , step 104 can be performed.
  • the multi-network access connection establishment request is allowed to be initiated, that is, when the user requests multi-network access, the user terminal sends an access connection establishment request to the corresponding target network, or is When the network environment changes and multiple network access is required, the user terminal sends an access connection establishment request to the corresponding target network.
  • the user terminal If the user terminal confirms that the multi-access function cannot be used, it is forbidden to initiate a multi-network access connection establishment request, that is, when the user requests multi-network access or the network environment changes, and multiple network access is required, the user terminal refuses to The corresponding target network sends an access connection establishment request.
  • the user terminal may obtain multiple access indication information from the network side device, and determine whether the user terminal can use the multiple access function by using the multiple access indication information, and determine that the user terminal can use multiple access
  • the user terminal initiates the multi-network access connection establishment request. Therefore, when the user terminal uses the multi-access function to switch some services of the PDN connection to the 3GPP network, other services that do not switch to the 3GPP network can also be maintained at the same time. Normal communication ensures that normal network communication is not interrupted.
  • the following is an example of the user terminal requesting the network side device to obtain the multi-access indication information. According to different acquisition processes, the following may be specifically included:
  • the step of acquiring the multiple access indication information in the attaching process in this embodiment may include: (1) the user terminal sends an attach request to the access node;
  • the user terminal When the user terminal enters the coverage of a network, it first requests the access node of the network. When attaching, the user terminal can send an attach request to the access node.
  • the multiple access capability information of the user terminal of the user terminal may be carried in the attach request, and the multiple access capability information of the user terminal is used to indicate whether the user terminal supports multiple access functions, or
  • the attach request may carry an indication for requesting the multiple access indication information, where the indication of the multiple access indication information is used to request the access node to feed back the multiple access indication information, and it may be understood that the attach request in this embodiment may also be Do not carry these parameters.
  • the multiple access indication information in this embodiment may be network side capability information or indication information indicating whether the network side supports multiple access functions.
  • the multiple access capability information or the indication information of the specific user terminal may be carried in the reserved bit of the attach request, or may be newly extended in the attach request to carry the multiple access capability information of the user terminal or
  • the method of requesting multiple access indication information is not limited herein.
  • the access node may obtain multiple access indication information from the data gateway in the process of establishing the PDN connection.
  • the access node may indicate the capability information or request the multiple access indication information in the process of establishing the PDN connection.
  • the PDN connection request message is sent to the data gateway to request the data gateway to feed back the multiple access indication information.
  • the establishing the PDN connection request message in this embodiment may be establishing a default bearer request message.
  • the access node may request the attachment request sent by the user terminal according to the pre-configured policy of the operator.
  • the data gateway feeds back multiple access indication information.
  • the access node or the data gateway may also verify the multi-access capability information of the user terminal, and determine whether the user terminal supports the Multi-access function, if it is determined that the user terminal does not support multiple access functions, then it may not Obtaining multiple access indication information, if it is determined that the user terminal supports multiple access functions, the multiple access indication information may be acquired.
  • the specific check can be divided into access node check and data gateway check:
  • the access node determines whether the user terminal supports multiple access functions according to the multi-access capability information of the user terminal. If supported, the multi-access capability of the user terminal is established during the process of establishing the PDN connection.
  • the information or the indication of the request multiple access indication information generated by the access node itself is sent to the data gateway by requesting the feedback multiple access indication information by establishing a PDN connection request message;
  • the access node When the data gateway verifies, the access node sends the PDN connection request message to the data gateway by establishing a PDN connection request message in the process of establishing the PDN connection, and the data gateway judges according to the multi-access capability information of the user terminal. Whether the user terminal supports the multiple access function, if yes, the multiple access indication information is carried in the setup PDN connection response message and sent to the access node.
  • the verification process of the multi-access capability information of the user terminal is not a necessary process.
  • the multi-access indication information can be directly obtained without verifying the multi-access capability information of the user terminal.
  • the access node may further obtain the subscription information of the user terminal from the database according to the attachment request of the user terminal, and if the subscription information does not include information about whether the user terminal is authorized to access multiple times. Or, the subscription information indicates that the user terminal is authorized to access multiple times, and the access node may obtain multiple access indication information. If the subscription information indicates that the user terminal is not authorized for multiple access, the access node may not acquire. Multi-access indication information, and feedback unauthorized indication information to the user terminal. It can be understood that the verification process of the subscription information of the user terminal is not a necessary process. In actual application, the user terminal subscription information may not be verified directly. Obtain multiple access indication information.
  • the multiple access indication information may be fed back to the user terminal.
  • the access node or the data gateway may return to the user terminal that the user terminal does not support multiple access functions. information.
  • the user terminal receives the multiple access indication information sent by the access node
  • the user terminal may receive the multiple access indication information.
  • the user terminal may directly prohibit the initiation of the multi-network access connection establishment request and end the process.
  • the user terminal determines, according to the multi-access indication information, whether the user terminal can use the multi-access function, and if so, allows the multi-network access connection establishment request to be initiated, and if not, prohibits the initiation of the multi-network access connection establishment request.
  • the user terminal may determine whether the current network side supports the multiple access function according to the multiple access indication information. It should be noted that the user terminal may further determine whether the user terminal supports the multiple access function. Multi-access function, if the network side supports multiple access functions, and the user terminal also supports multiple access functions, it is determined that multiple access functions can be used. If the network side does not support multiple access functions, or the user terminal does not support multiple access functions. Into the function, it is determined that the multi-access function cannot be used;
  • the user terminal can also judge whether the network side supports the multiple access function. If supported, it is determined that the multiple access function can be used. If not, it is determined that the multiple access function cannot be used.
  • the multi-network access connection establishment request is allowed to be initiated, that is, when the user requests multi-network access, the user terminal sends an access connection establishment request to the corresponding target network, or is When the network environment changes and multiple network access is required, the user terminal sends an access connection establishment request to the corresponding target network.
  • the user terminal If the user terminal confirms that the multi-access function cannot be used, it is forbidden to initiate a multi-network access connection establishment request, that is, when the user requests multi-network access or the network environment changes, and multiple network access is required, the user terminal refuses to The corresponding target network sends an access connection establishment request.
  • the access node and the network element referred to by the data gateway may be different, in 3GPP.
  • the access node can be a mobility management entity (MME, Mobility Management Entity)
  • MME Mobility Management Entity
  • SGW Serving GateWay
  • PGW Packet Data Network Gate
  • the user terminal initiates an attach request (Attach Request) to the MME accessing the network.
  • the user terminal When the user terminal enters the coverage of a certain network, it first requests attachment to the MME of the network, and then sends an attach request to the MME.
  • the attach request in this embodiment may include multiple access capability information of the user terminal, or an indication of requesting multiple access indication information, and the attach request may add a field for carrying the multiple access capability information of the user terminal, or request
  • the indication of the multiple access indication information, or other forms of indication information, is used to instruct the MME to feed back the multiple access indication information.
  • the MME initiates an identity certificate request ( Identity Request) to the user terminal.
  • the MME may send an identity authentication request to the user terminal to authenticate the identity of the user terminal.
  • the user terminal sends an identity authentication response ( Identity Response) to the MME.
  • Identity Response an identity authentication response
  • the MME and the user terminal perform mutual authentication (Authentication);
  • the MME can mutually authenticate the user information with the user information stored in the Home Subscriber Server (HSS).
  • HSS Home Subscriber Server
  • the MME performs authentication (IMEI Check) through a device of the user terminal of an Equipment Identity Register (EIR);
  • the above steps 202 to 205 are authentication processes, including identity authentication and device authentication.
  • the MME updates location information (Update Location) of the user terminal in the HSS.
  • the MME receives an update location confirmation message (Update Location Ack) of the HSS, and obtains subscription information of the user terminal. 208.
  • the MME sends a Create Default Bearer Request message to the SGW.
  • the MME sends a default bearer request to the SGW.
  • the message may carry the multi-access capability information of the user terminal that is obtained in step 201 or the indication of the request for the multi-access indication information. It should be noted that if the attach request in step 201 does not carry the multi-connection of the user terminal If the capability information or the indication of the multiple access indication information is requested, the MME may send a default bearer request message to the SGW according to the policy preset by the operator, where the indication of the multiple access indication information is requested in the default bearer request message. The indication of the request multiple access indication information is used to request the PGW to feed back the multiple access indication information.
  • the MME may not carry the indication information in the setup default bearer request message sent to the SGW, but only establishes the defect according to the common process.
  • Independent bearer If the subscription information of the user terminal obtained by the MME in step 207 indicates that the user terminal is not authorized to access multiple times, the MME may not carry the indication information in the setup default bearer request message sent to the SGW, but only establishes the defect according to the common process.
  • Independent bearer may not carry the indication information in the setup default bearer request message sent to the SGW, but only establishes the defect according to the common process.
  • the MME may directly send the setup default bearer request message carrying the indication of the request multiple access indication information to the SGW. If the MME obtains the multiple access capability information of the user terminal in step 201, the MME may further determine, according to the multiple access capability information of the user terminal, whether the user terminal supports multiple access functions, and may support the user terminal. In the case of the multi-access function, the setup default bearer request message carrying the multi-access capability information of the user terminal is sent to the SGW.
  • the verification of the user terminal subscription information and the verification of the multi-access capability of the user terminal mentioned above may also be combined in practical applications, for example, when the subscription information indicates that the user is authorized to access multiple times, and the user terminal supports multiple access.
  • the MME sends the multiple access capability information of the user terminal to the SGW.
  • the verification of the subscription information of the user terminal and the verification of the multiple access capability of the user terminal are not mandatory. In actual applications, the MME may also perform the verification without directly performing the verification.
  • the multiple access capability information or the indication for requesting multiple access indication information is sent to the SGW by establishing a default bearer request message. 209.
  • GTP General Packet Radio Service Tunneling Protocol
  • the SGW sends a Create Default Bearer Request message to the PGW.
  • the SGW sends a proxy binding update message (Proxy Binding Update) to the PGW when using a proxy mobile internet protocol (PMIP, Proxy Mobile IP) for signaling interaction with the PGW;
  • PMIP proxy mobile internet protocol
  • the SGW forwards the received multiple access capability information of the user terminal or the indication of the multiple access indication information to the PGW by establishing a default bearer request message or a proxy binding update message.
  • the SGW may forward the indication of the multiple access indication information to the PGW directly by establishing a default bearer request message or a proxy binding update message.
  • the SGW can also verify whether the user terminal supports the multi-access function, and when the user terminal supports the multi-access function, the user is The multiple access capability information of the terminal is sent to the PGW by establishing a default bearer request message or a proxy binding update message.
  • the SGW may also perform the verification of the multiple access capability information of the user terminal.
  • the province bearer request message or the proxy binding update message is sent to the PGW.
  • the PGW sends a Create Default Bearer Response message to the SGW.
  • the PGW is used. Send a proxy binding confirmation message to the SGW
  • the PGW can check whether the user terminal supports the multi-access function according to the received multi-access capability information of the user terminal, and if it is determined that the user terminal supports multiple access The ingress function, the PGW sends the multiple access capability information of the PGW to the SGW by establishing a default bearer response message or a proxy binding acknowledgement message, and sends the multiple access indication information according to the multiple access capability information of the PGW, that is, the multiple The access indication information may include a multi-access capability letter of the PGW. For example, if it is determined that the user terminal does not support the multiple access function, the establishment of the default bearer response message or the proxy binding acknowledgement message sent by the PGW may not include the multiple access capability information of the PGW.
  • the PGW may directly send the multiple access capability information of the PGW to the SGW by establishing a default bearer response message or a proxy binding acknowledgement message, and according to the PGW.
  • the multiple access capability information sends multiple access indication information.
  • the PGW may also perform the verification by directly establishing a default bearer response message or proxy binding.
  • the message sends the multi-access capability information of the PGW to the SGW.
  • the PGW may send the multiple access capability information of the PGW to the SGW by establishing a default bearer response message or a proxy binding acknowledgement message.
  • the PGW may first determine whether it supports multiple access functions. And the PGW supports the multi-access function indication information, and the multi-access indication information is sent according to the PGW supporting the multi-access function indication information, and if not, the establishment is performed in the establishment of the default bearer response message or the proxy binding acknowledgement message.
  • the PGW does not support the multi-access function indication information in the default bearer response message or the proxy binding acknowledgement message, and sends the multi-access indication information according to the PGW does not support the multi-access function indication information.
  • the SGW sends a Create Default Bearer Response message to the MME.
  • the SGW may establish the missing The province bearer response message forwards the multiple access indication information to the MME.
  • the MME sends an Attach Accept message to an Evolved Universal Mobile Telecommunications System Territorial Radio Access Network (E-UTRAN).
  • E-UTRAN Evolved Universal Mobile Telecommunications System Territorial Radio Access Network
  • the MME may send the multiple access indication information to the E-UTRAN through the attach accept message.
  • the attach accept message sent by the MME to the E-UTRAN may carry the unauthorized indication information, and send the multiple access indication information according to the unauthorized indication information, to indicate that the user terminal is not authorized. Multiple access.
  • the MME may first determine whether the PGW supports the multiple access function according to the received multiple access capability information of the PGW, and if it is determined that the PGW supports multiple access functions, The MME sends the PGW to support the multi-access function indication information to the E-UTRAN. If it is determined that the PGW does not support the multi-access function, the MME sends the PGW to the E-UTRAN to not support the multi-access function indication information, and supports the multi-connection according to the PGW. The incoming function indication information or the PGW does not support the multiple access function indication information to send multiple access indication information.
  • the MME may directly send the multiple access indication information to the E-UTRAN.
  • the MME may directly send the multiple access indication information to the E-UTRAN.
  • the E-UTRAN sends a radio resource control (RRC, Radio Resource Control) connection reconfiguration message (RRC Connection Reconfiguration) to the user equipment.
  • RRC Radio Resource Control
  • the E-UTRAN receives the multiple access indication information sent by the MME (which may be the multiple access capability information of the PGW, or the PGW supports the multiple access function indication information, or the PGW does not support the multiple access function indication information, or the unauthorized indication
  • the E-UTRAN sends the received multiple access indication information to the user terminal through an RRC connection reconfiguration message.
  • the user terminal sends an RRC connection reconfiguration complete message to the E-UTRAN.
  • the E-UTRAN sends an attach complete message (Attach Complete) to the MME.
  • the MME sends an update bearer request message (Update Bearer Request) to the SGW.
  • Update Bearer Request an update bearer request message
  • the SGW sends an Update Bearer Response message to the MME.
  • the user terminal may determine, according to the multiple access indication information, whether the user terminal can use the multiple access function, and if available, the user terminal is allowed to send A multi-network access connection establishment request is initiated, and if not available, a multi-network access connection establishment request is prohibited.
  • the specific determination method can be:
  • the user terminal determines that the multi-access function can be used.
  • the access function if the multi-access capability information of the PGW indicates that the PGW does not support the multi-access function, or the user terminal does not support the multi-access function, the user terminal determines that the multi-access function cannot be used;
  • the user terminal determines that the multi-access function can be used, and if the multi-access indication information includes the PGW, the PGW does not support.
  • the multi-access function indicates information, or the user terminal does not support the multi-access function itself, the user terminal determines that the multi-access function cannot be used.
  • the user terminal determines that the multi-access function cannot be used regardless of whether the user terminal itself supports the multi-access function.
  • the MME in this embodiment may be regarded as an access node, and the access node may be different according to different application networks.
  • the access node may be another network element, for example, a serving general packet radio service support node (SGSN), and the specific access node may also be
  • the data gateway in this embodiment is a PGW. In actual applications, it may also be a Gateway General Packet Radio Service Support Node (GGSN), or a mobile 4 seed point, or other type.
  • GGSN Gateway General Packet Radio Service Support Node
  • the network element is not limited here.
  • the user terminal may send an attach request to the MME to request the MME to feed back the multiple access indication information.
  • the MME may obtain the PGW from the PGW through the SGW in the process of establishing the default bearer. Accessing the capability information, and transmitting the multiple access indication information according to the multiple access capability information of the PGW, or directly acquiring whether the PGW supports the multiple access function indication information, and sending the multiple access indication according to whether the PGW supports the multiple access function indication information.
  • Information so it can end up with the user
  • the terminal feeds back the multiple access indication information, so the user terminal can obtain the multiple access indication information to determine whether the user terminal can have multiple access functions. When it is determined that the multiple access function can be used, the user terminal initiates multiple network access connections.
  • the request is established, so when the user terminal uses the multi-access function, after some services in the PDN connection are switched to the 3GPP network, other services that do not switch to the 3GPP network can also maintain normal communication at the same time, thereby ensuring that normal network communication is not interrupted;
  • the MME can check the subscription information of the user terminal.
  • the multiple access indication information may include only the unauthorized indication information, and does not need to include
  • the multi-access capability information of the PGW can further reduce data transmitted between network elements and reduce network load.
  • a user terminal can also obtain multiple access capability information of a data gateway through an attach procedure in a non-3GPP network.
  • the access node may be a Mobility Access Gateway (MAG)
  • the data gateway may be a PGW.
  • FIG. 3 another embodiment of the multi-network access control method in the embodiment of the present invention. Includes:
  • the user terminal and the MAG perform non-3GPP specific procedures (Non-3GPP specific procedures);
  • the MAG in this embodiment is one of the access nodes, and the MAG may be a non-3GPP network IP access gateway or an Evolved Packet Data Gateway (EPDG).
  • EDG Evolved Packet Data Gateway
  • the user terminal and the MAG perform authentication (Authentication & Authorization) by using an HSS or an Authentication Authorization Accounting (AAA).
  • the MAG can obtain the subscription information of the user terminal through the HSS or the AAA server. .
  • the user terminal initiates a trigger attach procedure (L3 Attach Trigger) to the MAG, and sends an attach request to the MAG access gateway.
  • a trigger attach procedure L3 Attach Trigger
  • the attach request may carry multiple access capability information of the user terminal, or request an indication of multiple access indication information, and the attach request may add a field for carrying the user terminal.
  • the multiple access capability information, or the indication of the multiple access indication information, or other forms of indication information, is used to indicate that the MAG feeds back multiple access indication information.
  • the MAG may carry the message acquired by the MAG when sending the message to the PGW.
  • the multi-access capability information of the user terminal or the indication of the multi-access indication information is requested.
  • the indication that the multi-access capability information of the user terminal or the multi-access indication information is requested is not included in the attach request in step 301.
  • the MAG may send a message to the PGW according to the policy preset by the operator, where the message includes an indication for requesting multiple access indication information, where the indication of the multiple access indication information is used to request the PGW to feed back the multiple access indication information.
  • the MAG may not carry the indication information in the message sent to the PGW, but only processes according to an ordinary process.
  • the MAG may directly send the message carrying the indication of the multiple access indication information to the PGW, if the MAG is in step 301.
  • the multi-access capability information of the user terminal is obtained, and the MAG may further determine, according to the multi-access capability information of the user terminal, whether the user terminal supports multiple access functions, and may support multiple access functions in the user terminal. In this case, the message carrying the multi-access capability information of the user terminal is sent to the PGW.
  • the verification of the user terminal subscription information and the verification of the multi-access capability of the user terminal mentioned above may also be combined in practical applications, for example, when the subscription information indicates that the user is authorized to access multiple times, and the user terminal supports multiple access.
  • the MAG sends the multi-access capability information of the user terminal to the PGW.
  • the verification of the subscription information of the user terminal and the verification of the multi-access capability of the user terminal are not mandatory. In practical applications, the MAG may also perform the verification without directly performing the verification.
  • the multiple access capability information or the indication requesting the multiple access indication information is sent to the PGW.
  • gateway control session establishment procedure (Gateway Control Session Establishment Procedure);
  • the MAG sends a proxy binding update message (Proxy Binding Update) to the PGW.
  • the proxy binding update message may include the multiple access capability information of the user terminal or the information requesting the multiple access indication information in the foregoing step 303.
  • the PGW initiates an IP-Can Session Establishment Procedure (IP-Can Session Establishment Procedure) for the Policy Control and Charging Rules Function (PCRF);
  • IP-Can Session Establishment Procedure Policy Control and Charging Rules Function
  • the PGW updates the PGW identity information and the access point name (APN, Access Point Name) information of the PDN connection of the user to the HSS/AAA server.
  • APN Access Point Name
  • the PGW sends a proxy binding acknowledgement message (Proxy Binding Ack) to the MAG.
  • the PGW may check the multiple access capability information of the user terminal. If the user terminal determines that the user terminal supports the multiple access function, the PGW may send the multiple access indication to the MAG.
  • the PGW may not send multiple access indication information to the MAG.
  • the PGW may directly send the multiple access indication information to the MAG.
  • the PGW can still directly feed back to the MAG according to the operator policy. Multiple access indication information.
  • the multiple access indication information in this step may include multiple access capability information of the PGW. It should be noted that after receiving the message sent by the MAG, the PGW may first determine whether the PGW itself supports multiple access functions. The PGW can be fed back to the MAG to support the multi-access function indication information. If not, the PGW can be fed back to the MAG. The PGW does not support the multi-access function indication information, and the PGW can support multiple access function indication information or the PGW does not support multiple access. The function indication information sends multiple access indication information.
  • Proxy mobile IP tunnel establishment between the PGW and the MAG (PMIP Tunnel);
  • a gateway-controlled session modification process that may be initiated by the home PCRF to update the QoS in the MAG.
  • Information (Gateway Control and QoS Rules Provision Procedure);
  • the MAG may first determine whether the PGW supports multiple access functions. If supported, the MAG completes the attachment. The process of transmitting the PGW support multi-access function indication information to the user terminal, if the MAG determines that the PGW does not support the multi-access function, the MAG sends the PGW not supporting the multi-access function indication information to the user terminal through the process of attaching completion, and according to the PGW.
  • the multiple access function indication information is supported or the PGW does not support the multiple access function indication information to send multiple access indication information.
  • the MAG may also directly send the multiple access indication information including the multiple access capability information of the PGW to the user terminal.
  • the MAG may directly directly indicate the multiple access indication. Information is sent to the user terminal.
  • the MAG may send an unauthorized indication to the user terminal, and send according to the unauthorized indication. Multiple access indication information.
  • the user terminal may determine, according to the multiple access indication information, whether the user terminal can use the multiple access function, and if available, the user terminal is allowed to initiate the establishment of the multiple network access connection.
  • the request if not available, prohibits the initiation of a multi-network access connection establishment request.
  • the specific determination method can be:
  • the user terminal determines that the multi-access function can be used.
  • the access function if the multi-access capability information of the PGW indicates that the PGW does not support the multi-access function, or the user terminal does not support the multi-access function, the user terminal determines that the multi-access function cannot be used;
  • the user terminal determines that the multi-access function can be used. If the multi-access indication information includes the PGW does not support the multi-access function indication information, or the user terminal does not support the multi-access function, the user terminal Make sure you cannot use the multi-access feature.
  • the user terminal determines that the multi-access function cannot be used regardless of whether the user terminal itself supports the multi-access function.
  • the user terminal sends a PDN connection establishment request to the access node
  • the user terminal When the user terminal requests the establishment of a PDN connection, the user terminal may send a PDN connection establishment request to the access node.
  • the PDN connection establishment request may carry the multiple access capability information of the user terminal of the user terminal, and the multiple access capability information of the user terminal is used to indicate whether the user terminal supports multiple access functions.
  • the PDN connection establishment request may carry an indication of requesting multiple access indication information, where the indication of the multiple access indication information is used to request the access node to feed back multiple access indication information, which may be understood in this embodiment.
  • the PDN connection establishment request may also not carry these parameters.
  • the multiple access capability information or indication of the specific user terminal may be carried in the reserved bit of the PDN connection establishment request, or may be newly extended in the PDN connection establishment request to carry multiple access of the user terminal.
  • the capability information or instructions are not limited here.
  • the access node may obtain multiple access indication information from the data gateway in the process of establishing the PDN connection.
  • the access node may provide the capability information or the request in the process of establishing the PDN connection.
  • the request for the multiple access indication information is sent to the data gateway by the PDN connection request message to request the data gateway to feed back the multiple access indication information.
  • the setup PDN connection request message in this embodiment may be a proxy binding update request message.
  • the access node may receive the PDN connection establishment request sent by the user terminal according to the pre-configured policy of the operator. After that, the data gateway is requested to feed back the multi-access indication information.
  • the access node or the data gateway may also verify the multiple access capability information of the user terminal, and determine the user terminal. Whether the multi-access function is supported, if the user terminal does not support the multi-access function, the multi-access indication information may not be obtained. If the user terminal is determined to support the multi-access function, the multi-access indication information may be acquired.
  • the specific check can be divided into access node check and data gateway check:
  • the access node determines whether the user terminal supports multiple access functions according to the multi-access capability information of the user terminal. If supported, the multi-access capability of the user terminal is established during the process of establishing the PDN connection.
  • the information or the indication of the multiple access indication information generated by the access node itself is sent to the data gateway to request feedback of the multiple access indication information by establishing a PDN connection request message.
  • the establishing the PDN connection request message in this embodiment may be a proxy binding. Update request message;
  • the access node When the data gateway verifies, the access node sends the PDN connection request message to the data gateway by establishing a PDN connection request message in the process of establishing the PDN connection, and the data gateway judges according to the multi-access capability information of the user terminal. Whether the user terminal supports the multiple access function, if yes, the multiple access indication information is sent according to the multiple access capability information of the data gateway, and the multiple access indication information is carried in the setup PDN connection response message and sent to the access node;
  • the data gateway when determining that the user terminal supports the multiple access function, may further determine whether the multi-access function is supported by the user terminal. If the multi-access function is supported by the user, the data gateway sends the access node to the access node.
  • the sent PDN connection response message carries the data gateway supporting multiple access function indication information. If the multi-access function is not supported by itself, the data gateway sends a PDN connection to the access node.
  • the data message carrying the response message does not support the multi-access function indication information, and the multi-access indication information is sent according to the data gateway, or the data gateway does not support the multi-access function indication information to send the multi-access indication information.
  • the establishment of a PDN connection response message may be an agent binding update confirmation message.
  • the verification process of the multi-access capability information of the user terminal is not a necessary process.
  • the multi-access indication information can be directly obtained without verifying the multi-access capability information of the user terminal.
  • the access node may further perform verification of the subscription information according to the subscription information acquired by the user terminal when attaching, if the subscription information does not include whether the user terminal is authorized to access multiple times.
  • the information, or the subscription information indicates that the user terminal is authorized to access multiple times the access node may obtain multiple access indication information, and if the subscription information indicates that the user terminal is not authorized for multiple access, the access node may The multi-access indication information is not obtained, and the unauthorized indication information is fed back to the user terminal, and the multiple access indication information is sent according to the unauthorized indication information.
  • the verification process of the subscription information of the user terminal is not a necessary process. In the actual application, the multi-access indication information may be directly obtained without verifying the user terminal subscription information.
  • the multiple access indication information may be fed back to the user terminal.
  • the user terminal receives the multiple access indication information sent by the access node
  • the user terminal may receive the multiple access indication information.
  • the user terminal determines, according to the multi-access indication information, whether the user terminal can use the multi-access function, and if so, allows the multi-network access connection establishment request to be initiated, and if not, prohibits the initiation of the multi-network access connection establishment request.
  • the user terminal may determine whether the current network side supports the multiple access function according to the multiple access indication information. It should be noted that the user terminal may further determine whether the user terminal supports the multiple access function. Multi-access function, if the network side supports multiple access functions, and the user ends If the multi-access function is also supported, the multi-access function can be used. If the network side does not support the multi-access function, or the user terminal does not support the multi-access function, it is determined that the multi-access function cannot be used.
  • the user terminal can also judge whether the network side supports the multiple access function. If supported, it is determined that the multiple access function can be used. If not, it is determined that the multiple access function cannot be used.
  • the multi-network access connection establishment request is allowed to be initiated, that is, when the user requests multi-network access, the user terminal sends an access connection establishment request to the corresponding target network, or is When the network environment changes and multiple network access is required, the user terminal sends an access connection establishment request to the corresponding target network.
  • the user terminal If the user terminal confirms that the multi-access function cannot be used, it is forbidden to initiate a multi-network access connection establishment request, that is, when the user requests multi-network access or the network environment changes, and multiple network access is required, the user terminal refuses to The corresponding target network sends an access connection establishment request.
  • the access node and the data element referred to by the data gateway may be different, in the 3GPP network.
  • the access node may be an MME, and the data gateway may be a PGW.
  • the following is a detailed description of the 3GPP network.
  • another embodiment of the method for controlling multiple network access in the embodiment of the present invention includes:
  • the user terminal sends a PDN Connectivity Request to the MME.
  • the PDN connection request may include multiple access capability information of the user terminal or an indication of requesting multiple access indication information.
  • the MME sends a Create Default Bearer Request message to the SGW.
  • the operations performed by the MME in step 402 are the same as those performed in step 208 in the embodiment shown in FIG. 2, and details are not described herein again.
  • the SGW sends the PGW to the PGW2.
  • Sending a default bearer request message (Create Default Bearer Request);
  • the SGW and the PGW2 use PMIP for signaling interaction, the SGW sends a proxy binding update message (Proxy Binding Update) to the PGW2;
  • the PGW2 is newly selected by the user terminal, and requests to establish a PGW for the PDN connection.
  • the SGW forwards the received multiple access capability information of the user terminal or the indication of the multiple access indication information to the PGW2 by establishing a default bearer request message or a proxy binding update message.
  • the SGW may forward the indication of the multiple access indication information to the PGW2 directly by establishing a default bearer request message or a proxy binding update message.
  • the SGW can also verify whether the user terminal supports the multi-access function, and when the user terminal supports the multi-access function, the user is multiple access capability information of the terminal through the established default bearer request message or a proxy binding update message to the PGW2 0
  • the SGW may also perform the verification of the multiple access capability information of the user terminal.
  • the province bearer request message or the proxy binding update message is sent to PGW2.
  • the PGW2 sends a Create Default Bearer Response message to the SGW.
  • the PGW2 sends a proxy binding confirmation message to the SGW.
  • the PGW2 may check whether the user terminal supports the multi-access function according to the received multi-access capability information of the user terminal, and if it is determined that the user terminal supports multiple access In the function, the PGW2 sends the multiple access capability information of the PGW to the SGW by establishing a default bearer response message or a proxy binding acknowledgement message, and sends multiple access indication information according to the multiple access capability information of the PGW, if the user is determined.
  • the terminal does not support multiple access functions, then PGW2 sends The multi-access capability information of the PGW2 may not be included in the sent default bearer response message or the proxy binding acknowledgement message.
  • the PGW2 may directly send the multiple access capability information of the PGW2 to the SGW by establishing a default bearer response message or a proxy binding acknowledgement message, and according to the PGW.
  • the multiple access capability information sends multiple access indication information.
  • the PGW2 may also perform the verification without directly verifying the default bearer response message or proxy binding.
  • the message sends the multi-access capability information of the PGW2 to the SGW.
  • the PGW2 may send the multiple access capability information of the PGW2 to the SGW by establishing a default bearer response message or a proxy binding acknowledgement message. Similarly, the PGW2 may first determine whether it supports multiple access functions. The PGW is configured to carry the multi-access function indication information in the establishment of the default bearer response message or the proxy binding acknowledgement message. If not, the PGW is not supported in the default bearer response message or the proxy binding acknowledgement message. Entering the function indication information, and sending the multiple access indication message according to the PGW supporting the multiple access function indication information or the PGW does not support the multiple access function indication information
  • the SGW sends a default bearer response message to the MME.
  • the SGW receives the multiple access indication information sent by the PGW2, the SGW forwards the multiple access indication information to the MME.
  • the MME sends a PDN Connectivity Accept message to the E-UTRAN.
  • the MME may send the multiple access indication information to the E-UTRAN through the attach accept message.
  • the MME may send the unauthorized indication information to the E-UTRAN, and according to the unauthorized indication.
  • the information transmission multiple access indication information is used to indicate that the user terminal is not authorized to access multiple times.
  • the MME may also first According to the received multiple access capability information of the PGW2, it is determined whether the PGW2 supports the multiple access function. If it is determined that the PGW2 supports the multiple access function, the MME sends the PGW support multiple access function indication information to the E-UTRAN; if it is determined that the PGW2 does not support For the multiple access function, the MME sends the PGW to the E-UTRAN to not support the multiple access function indication information, and sends the multiple access indication information according to the PGW supporting the multiple access function indication information or the PGW does not support the multiple access function indication information.
  • the MME may directly send the multiple access indication information to the E-UTRAN.
  • the MME may directly send the multiple access indication information to the E-UTRAN.
  • the E-UTRAN sends an RRC Connection Reconfiguration (RRC Connection Reconfiguration) message to the user equipment.
  • RRC Connection Reconfiguration RRC Connection Reconfiguration
  • the E-UTRAN receives the multiple access indication information sent by the MME (which may be the multiple access capability information of the PGW, or the PGW supports the multiple access function indication information, or the PGW does not support the multiple access function indication information, or the unauthorized indication
  • the E-UTRAN sends the received multiple access indication information to the user terminal through an RRC connection reconfiguration message.
  • the user terminal sends an RRC Connection Reconfiguration Complete message to the E-UTRAN.
  • the E-UTRAN sends a PDN Connectivity Complete message to the MME.
  • the MME sends an Update Bearer Request message to the SGW.
  • the SGW sends an Update Bearer Response message to the MME.
  • the MME sends a Notify Request message to the HSS.
  • the HSS sends a notification response message (Notify Response) message to the MME.
  • the user terminal may determine, according to the multiple access indication information, whether the user terminal can use the multiple access function, and if available, the user terminal is allowed to send A multi-network access connection establishment request is initiated, and if not available, a multi-network access connection establishment request is prohibited.
  • the specific determination method can be:
  • the user terminal determines that the user terminal can use more The access function, if the multi-access capability information of the PGW2 indicates that the PGW2 does not support the multi-access function, or the user terminal does not support the multi-access function, the user terminal determines that the multi-access function cannot be used;
  • the user terminal determines that the multi-access function can be used, and if the multi-access indication information includes the PGW, the PGW does not support.
  • the multi-access function indicates information, or the user terminal does not support the multi-access function itself, the user terminal determines that the multi-access function cannot be used.
  • the user terminal determines that the multi-access function cannot be used regardless of whether the user terminal itself supports the multi-access function.
  • the MME in this embodiment may be regarded as an access node, and the access node may be different according to different application networks.
  • the MME In the 3GPP network in this embodiment, only the MME is regarded as an access node as an example. It can be understood that, in an actual application, the access node may be another network element, for example, an SGSN, and the specific access node may be another network element.
  • the data gateway in this embodiment is a PGW, and is actually applied. It can also be a GGSN, or a mobile anchor, or other type of network element, which is not limited herein.
  • the MME may select the same PGW as the PGW that the current user terminal has accessed, that is, the PGW2 and the PGW1 are the same PGW, and the MME may acquire the previously acquired PGW1.
  • the access indication information is sent to the user terminal.
  • the user terminal can also obtain the multiple access indication information through the PDN connection request process in the non-3GPP network.
  • the access node may be a MAG
  • the data gateway may be a PGW.
  • another embodiment of the multi-network access control method in the embodiment of the present invention includes: 501. Trigger a new PDN Connectivity (Trigger new PDN Connectivity) request.
  • the PDN connection request may be sent.
  • the request may carry multiple access capability information of the user terminal, or request an indication of multiple access indication information
  • the PDN connection request may add a field for carrying multiple access capability information of the user terminal, or request multiple access.
  • the indication of the indication information, or other forms of indication information, is used to indicate that the MAG feeds back the multiple access indication information.
  • the MAG in this embodiment is one of the access nodes, and may be a non-3GPP network IP access gateway or an EPDG.
  • the MAG may carry the message acquired by the MAG when sending the message to the PGW2. Multi-access capability information of the user terminal or an indication of requesting multiple access indication information.
  • the MAG may not carry the indication information in the message sent to the PGW2, but only according to the normal process.
  • the MAG may directly send the message carrying the indication of the multiple access indication information to the PGW2, if the MAG obtains the user terminal.
  • the multi-access capability information may be used by the MAG to determine whether the user terminal supports the multi-access function according to the multi-access capability information of the user terminal, and may send the bearer to the PGW2 if the user terminal supports the multi-access function.
  • the verification of the user terminal subscription information and the verification of the multi-access capability of the user terminal mentioned above may also be combined in practical applications, for example, when the subscription information indicates that the user is authorized to access multiple times, and the user terminal supports multiple access.
  • the MAG sends the multi-access capability information of the user terminal to the PGW2.
  • the verification of the subscription information of the user terminal and the verification of the multi-access capability of the user terminal are not mandatory. In practical applications, the MAG may not perform verification directly.
  • the multi-access capability information of the user terminal or the indication requesting the multi-access indication information is sent to the PGW2.
  • the gateway controls a session establishment process.
  • the MAG sends a Proxy Binding Update message to the PGW2.
  • the message carries multiple access capability information of the user terminal or an indication for requesting multiple access indication information.
  • the PGW2 initiates an IP-Can Session establishment process with the PCRF.
  • the PGW2 updates the PGW identity information and the APN information of the PDN connection of the user to the AAA/HSS.
  • the PGW2 sends a Proxy Binding Ack message to the MAG. If the PGW2 receives the multi-access capability information of the user terminal from the MAG, the PGW2 may be based on the received multi-access capability information of the user terminal. Whether the user terminal supports the multiple access function, if it is determined that the user terminal supports the multiple access function, the PGW2 sends the multiple access capability information of the PGW2 to the MAG through the proxy binding acknowledgement message, and according to the multiple access capability information of the PGW. The multiple access indication information is sent. If it is determined that the user terminal does not support the multiple access function, the proxy binding acknowledgement message sent by the PGW2 may not include the multiple access capability information of the PGW2.
  • the PGW2 may directly send the multiple access capability information of the PGW2 to the MAG through the proxy binding acknowledgement message, and send according to the multiple access capability information of the PGW. Multiple access indication information.
  • the PGW 2 may not perform the verification, but directly sends the PGW2 to the MAG through the proxy binding confirmation message. Access capability information.
  • the PGW2 may send the multiple access capability information of the PGW2 to the MAG through the proxy binding acknowledgement message. Similarly, the PGW2 may first determine whether it supports the multiple access function, and if yes, the proxy binding acknowledgement message. The PGW is configured to support the multi-access function indication information. If not, the PGW does not support the multi-access function indication information in the establishment of the default bearer response message or the proxy binding acknowledgement message, and supports multiple access functions according to the PGW. The indication information or PGW does not support multiple access work. The information can be sent to the multi-access indication information.
  • a new PMIP tunnel is established between PGW2 and MAG.
  • the gateway control process initiated by the PCRF may update the QoS information in the MAG. 509.
  • the MAG sends a reply message to the user terminal.
  • the MAG may send the multi-access indication information to the user terminal by using the reply message.
  • the MAG may send the unauthorized indication information to the user terminal, and send according to the unauthorized indication information.
  • the multiple access indication information is used to indicate that the user terminal is not authorized for multiple access.
  • the MAG may first determine whether the PGW2 supports the multiple access function according to the received multiple access capability information of the PGW2, and if it is determined that the PGW2 supports the multiple access function, The MAG sends the PGW to support the multiple access function indication information to the user terminal. If it is determined that the PGW2 does not support the multiple access function, the MAG sends the PGW to the user terminal that does not support the multiple access function indication information, and supports the multiple access function according to the PGW. The indication information or the PGW does not support the multiple access function indication information to send the multiple access indication information.
  • the MME may directly send the multiple access indication information to the E-UTRAN.
  • the MME may directly send the multiple access indication information to the E-UTRAN.
  • the user terminal may determine, according to the multiple access indication information, whether the user terminal can use the multiple access function, and if available, the user terminal is allowed to initiate the establishment of the multiple network access connection.
  • the request if not available, prohibits the initiation of a multi-network access connection establishment request.
  • the specific determination method can be:
  • the user terminal determines that the user terminal can use more Access function, if the multi-access capability information of the PGW2 indicates that the PGW2 is not When the multi-access function is supported, or the user terminal does not support the multi-access function, the user terminal determines that the multi-access function cannot be used;
  • the user terminal determines that the multi-access function can be used, and if the multi-access indication information includes the PGW, the PGW does not support.
  • the multi-access function indicates information, or the user terminal does not support the multi-access function itself, the user terminal determines that the multi-access function cannot be used.
  • the user terminal determines that the multi-access function cannot be used regardless of whether the user terminal itself supports the multi-access function.
  • the MME may select the same PGW as the PGW that the current user terminal has accessed, that is, the PGW2 and the PGW1 are the same PGW, and the MME may acquire the previously acquired PGW1.
  • the access indication information is sent to the user terminal.
  • the user terminal may send a PDN connection request to the MAG to obtain multiple access indication information, and when the user terminal can use the multiple access function, the user terminal initiates a multi-network access connection.
  • the request is established. Therefore, when the user terminal uses the multi-access function to switch some services in the PDN connection to the 3GPP network, other services that do not switch to the 3GPP network can maintain normal communication at the same time, thereby ensuring normal network communication is not interrupted.
  • DHCP Dynamic Host Configuration Protocol
  • the step of acquiring the multiple access indication information in the requesting process in this embodiment may include: (1) the user terminal sends a request message to the network side device;
  • the user terminal when the user terminal requests address allocation, or authentication, or dynamic host configuration protocol (DHCP) discovery, the user terminal sends a corresponding request message to the corresponding network side device to request The network side device feeds back multiple access indication information.
  • DHCP dynamic host configuration protocol
  • the network side device feeds back the multiple access indication information stored in the network terminal by using the response message, and the network side device presets the network side capability information in the network side device, and the network side device receives the After the request message sent by the user terminal, the network side capability information may be carried in the response message fed back to the user terminal, or the network side device may first determine the network side capability information, and directly support the network side according to the network side. Incoming function, or the network side does not support multiple access functions to send multiple access indication information.
  • Another embodiment of the control method includes:
  • the user terminal broadcasts DHCP discovery information (DHCP Discovery) to the network.
  • DHCP Discovery DHCP discovery information
  • the user terminal may broadcast DHCP discovery information to each network element in the network for detecting the DHCP server to request the DHCP server to allocate the corresponding address.
  • the DHCP discovery information may carry an indication of requesting multiple access indication information or multiple access capability information of the user terminal, and is used to instruct the DHCP server to feed back multiple access indication information, and the multiple access indication information in this embodiment.
  • the capability information of the network side may be included, or the information indicating whether the network side supports the multiple access function is directly indicated.
  • the multi-access capability information of the PGW is regarded as an example of the network side capability information. It can be understood that In the actual application, if the other network element provides the data service for the user terminal, the capability information of the network element can also be obtained as the network side capability information.
  • the type of the specific network element is not limited herein.
  • the DHCP discovery information may not carry the multiple access capability information indication of the requesting network or the multiple access capability information of the user terminal, and the DHCP server determines to receive the according to the policy of the operator. After the DHCP discovery information, the multi-access indication letter is fed back to the user terminal.
  • the DHCP server After receiving the DHCP discovery information, the DHCP server sends DHCP providing information (DHCP Offer) to the user terminal.
  • DHCP Offer DHCP providing information
  • the DHCP server After receiving the DHCP discovery information, the DHCP server determines that the multi-access indication information needs to be fed back according to the indication of the request for multiple access indication information or the multi-access capability information of the user terminal.
  • the multi-access capability information of the PGW is queried in the locally preset database, and the multi-access indication information is sent to the user terminal according to the multi-access capability information of the PGW through the DHCP providing information.
  • the DHCP server may also query the multiple access capability information of the PGW according to the operator policy, and The multi-access capability information of the PGW is provided by the DHCP to provide the multi-access indication information to the user terminal.
  • the DHCP server may first determine whether the user terminal supports multiple access functions, and query the PGW when the user terminal supports multiple access functions. The capability information is accessed, and the multiple access capability information multiple access indication information of the PGW is fed back to the user terminal through the DHCP providing information.
  • the DHCP server may not verify the multi-access capability information of the user terminal, but directly query the multi-access capability information of the PGW, and provide the multi-access capability information of the PGW through the DHCP providing information. Information is fed back to the user terminal.
  • the DHCP server may further determine the multiple access capability information of the PGW to determine whether the PGW supports multiple access functions. If supported, the PGW supports the multi-access function indication information to the user terminal, if not supported. And the user terminal is fed back to the user terminal that the PGW does not support the multiple access function indication information, and the multiple access indication information is sent according to the PGW supporting the multiple access function indication information or the PGW does not support the multiple access function indication information.
  • the user terminal broadcasts DHCP request information (DHCP Request) to the network.
  • DHCP Request DHCP request information
  • the DHCP server sends a DHCP acknowledgement message (DHCPACK) to the user terminal.
  • DHCPACK DHCP acknowledgement message
  • the user terminal requests the multi-access indication information from the DHCP server in step 601, and the DHCP server sends the multi-access indication information to the user terminal in step 602.
  • the user terminal may also go to step 603.
  • the DHCP server requests multiple access indication information, and the DHCP server may also send multiple access indication information to the user terminal through step 604.
  • the user terminal may determine, according to the multiple access indication information, whether the user terminal can use the multiple access function, and if available, the user terminal is allowed to send A multi-network access connection establishment request is initiated, and if not available, a multi-network access connection establishment request is prohibited.
  • the specific determination method can be:
  • the user terminal determines that the multi-access function can be used.
  • the access function if the multi-access capability information of the PGW indicates that the PGW does not support the multi-access function, or the user terminal does not support the multi-access function, the user terminal determines that the multi-access function cannot be used;
  • the user terminal determines that the multi-access function can be used, and if the multi-access indication information includes the PGW, the PGW does not support.
  • the multi-access function indicates information, or the user terminal does not support the multi-access function itself, the user terminal determines that the multi-access function cannot be used.
  • the user terminal may send the DHCP discovery information to the DHCP server to request the DHCP server to feed back the multiple access indication information.
  • the DHCP server may query the multiple access indication in the locally preset database. The information is sent to the user terminal by using the information provided by the DHCP, so that the user terminal can obtain the multiple access indication information, and can determine whether the user terminal can use the multiple access function by using the multiple access indication information.
  • the user terminal When it is determined that the user terminal can use the multi-access function, the user terminal initiates the multi-network access connection establishment request, so when the user terminal uses the multi-access function, after the partial service in the PDN connection is switched to the 3GPP network, the user terminal does not switch to Other services of the 3GPP network can also maintain normal communication at the same time, thereby ensuring normal network communication is not interrupted.
  • the foregoing embodiment describes a process in which the network side device sends multiple access indication information to the user terminal, and the multiple access indication information can avoid normal network communication interruption when multiple access is used, except the above manner.
  • the embodiment of the present invention provides another multi-network access control method, which can also avoid normal network communication interruption when multiple access is used. For details, refer to FIG. 7, the multi-network access control method in the embodiment of the present invention.
  • Another embodiment includes:
  • the network side device receives a request message sent by the user terminal.
  • the network side device receives a request message from the user terminal, where the request message may carry multiple access capability information or indication information of the user terminal.
  • the multiple access capability information or the indication information of the user terminal is used to indicate that the user terminal may initiate a multi-network access connection establishment request.
  • the request message in this embodiment may also not carry the multiple access capability information or the indication information of the user terminal, and the network side device may determine, according to the operator policy, that the user terminal is received when the request message is received.
  • a multi-network access connection establishment request may be initiated.
  • the network side device acquires multiple access capability information of each data gateway.
  • the network side device After receiving the request message of the user terminal, the network side device can obtain the capability information of the network as the multi-access capability information of each data gateway in the current network.
  • the network side device selects, according to multiple access capability information of each data gateway, a data gateway that supports multiple access functions to provide services for the user terminal.
  • the data gateway supporting the multiple access function may be selected to provide services for the user terminal.
  • the network side device after receiving the request of the user terminal, selects a data gateway capable of supporting multiple access functions from the current data gateways to provide services for the user terminal, so that the user terminal can be served.
  • the data gateway can support multiple access functions. Therefore, when the user terminal uses the multiple access function, after some services in the PDN connection are switched to the 3GPP network, other services that do not switch to the 3GPP network can maintain normal communication at the same time, thereby ensuring normal operation. Network communication is not interrupted.
  • the specific multi-network access control method in the attach request process may include the following steps:
  • the user terminal sends an attach request to the access node
  • the access node of the network is first requested to attach, and the user terminal may send an attach request to the access node.
  • the attach request may carry multiple connections of the user terminal of the user terminal itself.
  • the capability information, the multiple access capability information of the user terminal is used to indicate whether the user terminal supports the multiple access function, or the attach request may carry the indication information, where the indication information is used to indicate that the access node feeds back the network side capability information. It can be understood that the attach request in this embodiment may also not carry these parameters.
  • the multiple access capability information or the indication information of the specific user terminal may be carried in the reserved bit of the attach request, or may be newly extended in the attach request to carry the multiple access capability information of the user terminal or
  • the information about the instructions is not limited here.
  • the access node acquires multiple access capability information of each data gateway in the current network
  • the access node After receiving the attach request sent by the user terminal, the access node queries the multiple access capability information of the statically configured data gateway, or obtains the data gateway of the current network by means of a domain name server (DNS, Domain Name Server). Multiple access capability information.
  • DNS Domain Name Server
  • the access node can also obtain the multiple access capability information of each data gateway in the current network by using other methods.
  • the specific manner is not limited herein.
  • the access node may perform the subscription information verification on the user terminal or the multi-access capability information verification of the user terminal before acquiring the multiple access capability information of each data gateway in the current network.
  • the specific check mode is similar to the check mode described in the foregoing embodiment, and details are not described herein again.
  • the access node selects a data gateway supporting the multi-access function to provide services for the user terminal. After the access node obtains the multiple access capability information of each data gateway in the current network, the data gateway supporting the multiple access function can be selected from the data gateways to provide services for the user terminal, and it should be noted that If the ingress node does not select a data gateway that supports the multi-access function, it sends a selection failure message to the user terminal to indicate that the data gateway supporting the multi-access function is not selected, that is, the user terminal is not allowed to use the multi-access function.
  • the reason why the data gateway supporting the multiple access function is not selected may be that each data gateway in the current network does not support the multiple access function, or the data gateway supporting the multiple access function in the current network exceeds the load. Preset thresholds, etc. If the user terminal receives the selection failure information from the access node, it indicates that the access node does not select the data gateway supporting the multiple access function, and the user terminal prohibits the initiation of the multi-network access connection establishment request, if the user terminal does not access the access When the node receives the selection failure information, it may indicate that the access node has selected the data gateway supporting the multiple access function by default, and the user terminal allows to initiate the multi-network access connection establishment request.
  • the access node selecting the data gateway in the attaching process is described above.
  • the access node and the data element referred to by the data gateway may be different.
  • the access node may be the MME.
  • the data gateway may be a PGW.
  • the following is a detailed description of the 3GPP network. For details, refer to FIG. 8.
  • Another embodiment of the method for controlling multiple network access in the embodiment of the present invention includes:
  • the user terminal initiates an attach request (Attach Request) to the MME accessing the network.
  • the user terminal When the user terminal enters the coverage of a certain network, it first requests attachment to the MME of the network, and then sends an attach request to the MME.
  • the attach request may carry the multiple access capability information of the user terminal, and the multiple access capability information of the user terminal is used to indicate whether the user terminal supports multiple access functions, or the attach request is
  • the indication information may be carried, and the indication information is used to indicate that the user terminal may initiate a multi-network access connection establishment request.
  • the multiple access capability information or the indication information of the specific user terminal may be carried in the reserved bit of the attach request, or may be newly extended in the attach request to carry the multiple access capability information of the user terminal or
  • the information about the instructions is not limited here.
  • the MME sends an identity authentication request ( Identity Request) to the user terminal.
  • Identity Request an identity authentication request
  • the user terminal sends an identity authentication response ( Identity Response) to the MME.
  • Identity Response Identity Response
  • the MME authenticates each other through the HSS and the user terminal. 805.
  • the MME authenticates the device of the user terminal by using the EIR (IMEI Check).
  • the above steps 802 to 805 are authentication processes, including identity authentication and device authentication.
  • the MME updates the location information (Update Location) of the user in the HSS. 807.
  • the MME receives an update location confirmation message (Update Location Ack) of the HSS, and obtains subscription information of the user terminal.
  • the MME management network element selects a PGW.
  • the MME preferentially selects the multi-access function when selecting the PGW. PGW.
  • the MME may further determine, according to the multiple access capability information of the user terminal, whether the user terminal supports multiple access functions, and if yes, when selecting the PGW. PGWs that support multiple access functions are preferred.
  • the verification of the user terminal subscription information and the verification of the multi-access capability of the user terminal mentioned above may also be combined in practical applications, for example, when the subscription information indicates that the user is authorized to access multiple times, and the user terminal supports multiple access.
  • the MME preferentially selects the PGW that supports the multi-access function when selecting the PGW.
  • the MME in this embodiment may select a PGW that supports multiple access functions in the following manner: Select a PGW that supports the multi-access function that is statically configured by the MME, or obtain the service information supported by the PGW through the DNS resolution mode, and then preferentially obtain the service information from the PGW. Select a PGW that supports multiple access functions.
  • the MME sends a Create Default Bearer Request message to the SGW.
  • the establishment default bearer request message sent by the MME to the SGW includes the address of the selected PGW supporting the multi-access function.
  • the SGW sends a Create Default Bearer Request message to the PGW.
  • the SGW and the PGW use the PMIP protocol to perform signaling interaction, the SGW is used. Send proxy binding update message to PGW
  • the setup default bearer request message received by the SGW from the MME includes the address of the PGW that supports the multiple access function selected by the MME, so the SGW can send the default bearer to the corresponding PGW.
  • the PGW sends a Create Default Bearer Response message to the SGW.
  • the SGW and the PGW use the PMIP protocol to perform signaling interaction, the PGW is used. Send a proxy binding confirmation message to the SGW
  • the SGW sends a Create Default Bearer Response message to the MME.
  • the MME sends an attach accept message (Attach Accept) to the E-UTRAN.
  • the attach accept message sent by the MME to the E-UTRAN includes the selection failure information, which is used to indicate that the PGW supporting the multiple access function is not selected.
  • the user terminal is not allowed to use the multi-access function.
  • the specific reason may be that the PGW supporting the multi-access function does not exist in the current network, or the load of the PGW supporting the multi-access function in the current network exceeds a preset threshold, or It is the cause of other types of failures and is not limited here.
  • the attach accept message sent by the MME to the E-UTRAN includes unauthorized indication information for indicating that the user terminal is not authorized for multiple access.
  • the E-UTRAN sends an RRC connection reconfiguration message to the user equipment.
  • the E-UTRAN If the E-UTRAN receives the selection failure information sent by the MME, or the unauthorized indication information, the E-UTRAN sends the received information to the user terminal through the RRC connection reconfiguration message.
  • the user terminal sends an RRC connection reconfiguration complete message to the E-UTRAN.
  • the E-UTRAN sends an attach complete message (Attach Complete) to the MME.
  • the MME sends an update bearer request message (Update Bearer Request) to the SGW.
  • Update Bearer Request Update Bearer Request
  • the SGW sends an Update Bearer Response message to the MME.
  • the user terminal if the user terminal does not receive the selection failure information sent by the network, the user terminal is The default network is capable of supporting multiple access functions.
  • the user terminal supporting the multiple access function may initiate connection establishment of multiple access networks.
  • the MME in this embodiment may be regarded as an access node, and the access node may be different according to different application networks.
  • the MME In the 3GPP network in this embodiment, only the MME is regarded as an access node as an example. It can be understood that, in an actual application, the access node may be another network element, for example, an SGSN, and the specific access node may be another network element.
  • the data gateway in this embodiment is a PGW, and is actually applied. It can also be a GGSN, or a mobile anchor, or other type of network element, which is not limited herein.
  • the MME after receiving the request of the user terminal, selects a PGW capable of supporting multiple access functions from the current PGWs to provide services for the user terminal, so that the PGW serving the user terminal can support multiple Access function, so when the user terminal uses the multi-access function, after some services in the PDN connection are switched to the 3GPP network, other services that do not switch to the 3GPP network can maintain normal communication at the same time, thereby ensuring normal network communication is not interrupted. ;
  • the MME may determine the multiple access capability information of the user terminal, and determine whether to obtain the capability information of each PGW. Therefore, when determining that the user terminal does not support the multiple access function, the MME may not acquire the PGW. Capability information, thus reducing the operation of the MME and reducing the network load;
  • the MME can check the subscription information of the user terminal.
  • the subscription information indicates that the user terminal is not authorized to access multiple times
  • the capability information of each PGW may not be acquired, so that the operation of the MME can be further reduced. Reduce network load.
  • an access node can also select a data gateway through an attach procedure in a non-3GPP network, in a non-3GPP network.
  • the access node may be a MAG, and the data gateway may be a PGW.
  • FIG. 9 Another embodiment of the multi-network access control method in the embodiment of the present invention includes:
  • the user terminal and the MAG perform non-3GPP specific procedures (Non-3GPP specific procedures);
  • the MAG in this embodiment is one of the access nodes, and may be a non-3GPP network IP access gateway or an EPDG.
  • the user terminal and the MAG perform authentication (Authorization & Authorization) by using an HSS or an AAA (Authentication Authorization Accounting).
  • the MAG can obtain the subscription information of the user terminal through the HSS or the AAA server. .
  • the user terminal initiates an attach attach procedure (L3 Attach Trigger) to the MAG, and sends an attach request to the MAG.
  • L3 Attach Trigger an attach attach procedure
  • the multiple access capability information of the user terminal may be carried in the attach request, and may not be carried.
  • the MAG selects a PGW.
  • the MAG preferentially selects the multi-access function when selecting the PGW. PGW.
  • the MAG may further determine, according to the multi-access capability information of the user terminal, whether the user terminal supports multiple access functions, and if supported, when selecting the PGW. PGWs that support multiple access functions are preferred.
  • the verification of the user terminal subscription information and the verification of the multi-access capability of the user terminal mentioned above may also be combined in practical applications, for example, when the subscription information indicates that the user is authorized to access multiple times, and the user terminal supports multiple access.
  • the MAG preferentially selects the PGW that supports the multi-access function when selecting the PGW.
  • the MAG in this embodiment may select a PGW that supports multiple access functions in the following manner: Select a PGW that supports the multi-access function of the MAG static configuration, or obtain the service information supported by the PGW through the DNS resolution mode, and then preferentially Select a PGW that supports multiple access functions.
  • gateway control session establishment procedure (Gateway Control Session Establishment Procedure);
  • the MAG sends a proxy binding update message (Proxy Binding Update) to the PGW.
  • the PGW initiates and controls the charging rule function entity (PCRF, Policy Control and Charging Rules Function) IP-Can Session Establishment Procedure (IP-Can Session Establishment Procedure);
  • PCRF Policy Control and Charging Rules Function
  • IP-Can Session Establishment Procedure IP-Can Session Establishment Procedure
  • the PGW updates the PGW identity information and the APN information (Update PGW Address) of the PDN connection of the user to the HSS/AAA server.
  • APN information Update PGW Address
  • the PGW sends a proxy binding acknowledgement message (Proxy Binding Ack) to the MAG.
  • Proxy mobile IP tunnel establishment between the PGW and the MAG (PMIP Tunnel);
  • the gateway control control procedure that may be initiated by the home PCRF to update the QoS information in the MAG (Gateway Control and QoS Rules Provision Procedure);
  • the attach complete message sent by the MAG to the user terminal may include selection failure information, which is used to indicate that the PGW supporting the multiple access function is not selected.
  • the user terminal is not allowed to use the multi-access function. The specific reason may be that the PGW supporting the multi-access function does not exist in the current network, or the load of the PGW supporting the multi-access function in the current network exceeds a preset threshold, or It is the cause of other types of failures and is not limited here.
  • the attach complete message sent by the MAG to the user terminal may include unauthorized indication information for indicating that the user terminal is not authorized for multiple access.
  • the user terminal if the user terminal does not receive the selection failure information sent by the MAG, the user terminal is a default network capable of supporting multiple access functions.
  • the user terminal supporting the multiple access function may initiate connection establishment of multiple access networks.
  • the attaching process is taken as an example. It can be understood that the scheme for selecting the PGW by the MAG can also be implemented in other processes, such as PDN connection establishment.
  • the request process, the specific process is not limited here.
  • the MAG after receiving the request of the user terminal, the MAG selects from the current PGWs.
  • the PGW capable of supporting the multi-access function provides services for the user terminal, so that the PGW serving the user terminal can support the multi-access function, so when the user terminal uses the multi-access function, some service switching in the PDN connection is made.
  • other services that do not switch to the 3GPP network can also maintain normal communication at the same time, thereby ensuring that normal network communication is not interrupted;
  • the MAG can determine the multi-access capability information of the user terminal, and determine whether to obtain the capability information of each PGW. Therefore, when determining that the user terminal does not support the multi-access function, the MAGW may not acquire the PGW. Capability information, thus reducing the operation of the MAG and reducing the network load;
  • the MAG can verify the subscription information of the user terminal.
  • the subscription information indicates that the user terminal is not authorized to access multiple times, the capability information of each PGW may not be acquired, so that the operation of the MAG can be further reduced. Reduce network load.
  • an embodiment of the communication system in the embodiment of the present invention includes:
  • the network side device 1001 is configured to acquire multiple access indication information, and send multiple access indication information to the user terminal 1003.
  • the user terminal 1003 is configured to receive multiple access indication information sent by the network side device 1001, determine, according to the multiple access indication information, whether the user terminal 1003 uses the multiple access function, and initiate multiple network access connection establishment when using the multiple access function. Request
  • the data gateway 1002 is configured to provide multiple access indication information to the network side device 1001.
  • the network side device 1001 in this embodiment may be an access node or a DHCP server. It should be noted that the access node is further configured to receive an attach request or a PDN connection establishment request sent by the user terminal 1003, and obtain subscription information of the user terminal 1003.
  • the access node acquires multiple access indication information
  • the access node When the subscription information indicates that the user terminal 1003 is not authorized to access multiple times, the access node according to the unauthorized reference The indication information transmits the multi-access indication information to the user terminal 1003.
  • the access request or the PDN connection establishment request in this embodiment includes multiple access capability information of the user terminal, and the access node is further configured to determine, according to the multiple access capability information of the user terminal, whether the user terminal 1003 supports multiple access functions, if In the process of establishing a PDN connection, the multi-access capability information of the user terminal or the indication of the request for multiple access indication information generated by the access node itself is sent to the data gateway 1002 by receiving a PDN connection request message, and the data gateway is received.
  • the PDN connection response message is sent by the 1002, and the PDN connection response message carries multiple access indication information.
  • the data gateway 1002 in this embodiment is further configured to receive, by the access node, a PDN connection request message that includes multiple access capability information of the user terminal, and determine, according to the multiple access capability information of the user terminal, whether the user terminal supports multiple access.
  • the function if supported, sends the multiple access indication information according to the multiple access capability information of the data gateway, where the multiple access indication information is carried in the setup PDN connection response message and sent to the access node;
  • the data gateway 1002 is further configured to receive, by the access node, a PDN connection request message that includes the multiple access capability information of the user terminal, and determine, according to the multiple access capability information of the user terminal, whether the user terminal supports the multiple access function, if If the data gateway 1002 supports the multiple access function, the multi-access indication information is transmitted according to the data gateway supporting the multiple access function indication information, and the multi-access indication information is carried. And sending the PDN connection response message to the access node, if the data gateway 1002 does not support the multiple access function, the multi-access indication information is sent according to the data gateway not supporting the multiple access function indication information, and the multiple access indication information The packet is sent to the access node in the setup PDN connection response message.
  • another embodiment of the communication system in the embodiment of the present invention includes:
  • the MME 1101 and the SGW 1102 in this embodiment may constitute an access node, and the PGW 1103 may be a data gateway.
  • the MME 1101 is configured to receive an attach request sent by the user terminal 1104, where the attach request carries the user.
  • the multi-access capability information of the terminal or the indication of the request for the multi-access indication information, the multi-access capability information of the user terminal or the indication of the request for the multi-access indication information is used to request the MME 1101 to feed back the multi-access indication information, and the MME 1101 forwards the user to the SGW 1102.
  • the multiple access capability information of the terminal or the indication of the multiple access indication information is received, and the multiple access indication information fed back by the SGW 1102 is received, and the multiple access indication information is sent to the user terminal 1104;
  • the SGW 1102 is configured to receive the multiple access capability information of the user terminal sent by the MME 1101 or the indication of requesting the multiple access indication information, and forward the multiple access capability information of the user terminal or the indication of the multiple access indication information to the PGW 1103, and receive the PGW 1103 feedback. Multiple access indication information, and feeding back multiple access indication information to the MME 1101;
  • the PGW 1103 is configured to receive the multiple access capability information of the user terminal sent by the SGW 1102 or the indication of requesting the multiple access indication information, and feed back the multiple access indication information to the SGW 1102.
  • the multiple access indication information in this embodiment may include the multiple access capability information of the PGW 1103, or include the PGW supporting the multiple access function indication, or the PGW does not support the multiple access function indication.
  • the user terminal 1104 is configured to receive the multiple access indication information sent by the MME 1101, determine whether to use the multiple access function according to the multiple access indication information, and initiate a multiple network access connection establishment request when using the multiple access function.
  • the user terminal 1104 When the user terminal 1104 enters the coverage of a certain network, it first requests attachment to the MME 1101 of the network, and then sends an attach request to the MME 1101.
  • the attach request in this embodiment may include multiple access capability information of the user terminal 1104, or an indication of requesting multiple access indication information, and the attach request may add a field for carrying the multiple access capability information of the user terminal 1104. Or the indication of the multiple access indication information, or other forms of indication information, used to instruct the MME 1101 to feed back the multiple access capability information of the PGW 1103.
  • the MME 1101 sends a setup default bearer request message to the SGW 1102, where the multi-access capability information of the user terminal 1104 or an indication of requesting multiple access indication information is carried.
  • the SGW 1102 sends a default bearer request message or a proxy binding update message to the PGW 1103.
  • the PGW 1103 sends a setup default bearer response message or a proxy binding acknowledgement message to the SGW 1102, where the multi-access indication information is carried.
  • the multiple access indication information may include the multiple access capability information of the PGW 1103, or include the PGW supporting the multiple access function indication, or the PGW does not support the multiple access function indication.
  • the SGW 1102 sends a default bearer response message to the MME 1101, where the multi-access indication information is carried.
  • the MME 1101 transmits multiple access indication information to the user terminal 1104 through the E-UTRAN;
  • the MME 1101 may also obtain the subscription information of the user terminal 1104 and perform verification. If the subscription information indicates that the user terminal 1104 is not authorized for multiple access, the MME 1101 may send the multiple access indication information to the user terminal 1104 according to the unauthorized indication information.
  • the user terminal 1104 may determine, according to the multiple access indication information, whether the user terminal can use the multiple access function, and if available, the user terminal 1104 allows multiple network access to be initiated.
  • the connection establishment request if not available, prohibits the initiation of the multi-network access connection establishment request.
  • the specific determination method can be:
  • the user terminal 1104 determines that If the multiple access function of the PGW indicates that the PGW does not support the multiple access function, or the user terminal 1104 does not support the multiple access function itself, the user terminal 1104 determines that the multiple access function cannot be used;
  • the user terminal 1104 determines that the multi-access function can be used, if the multi-access indication information includes the PGW.
  • the user terminal 1104 determines that the multi-access function cannot be used.
  • the multi-access indication information includes unauthorized indication information, whether the user terminal 1104 itself The multi-access function is supported, and the user terminal determines that the multi-access function cannot be used.
  • the user terminal 1104 may send an attach request to the MME 1101 to request the MME 1101 to feed back the multiple access indication information.
  • the MME 1101 may obtain the default bearer from the PGW 1103 through the SGW 1102.
  • the multi-access indication information can be fed back to the user terminal 1104, so that the user terminal 1104 can obtain the multi-access indication information, and can determine whether to use the multi-access function by using the multi-access indication information.
  • the user terminal 1104 initiates a multi-network access connection establishment request. Therefore, after some services in the PDN connection of the user terminal 1104 are switched to the 3GPP network, other services that are not switched to the 3GPP network can be simultaneously maintained. Normal communication ensures that normal network communication is not interrupted.
  • FIG. 10 specifically includes: a network side device 1001, configured to receive a request message sent by the user terminal 1003, and obtain capability information of each data gateway 1002, according to each data gateway 1002.
  • the capability information selection data gateway 1002 supporting the multiple access function provides a service for the user terminal 1003;
  • the data gateway 1002 is configured to provide the network side device 1001 with multiple access capability information of the data gateway.
  • the user terminal 1003 is configured to send a request message to the network side device 1001.
  • the data gateway in this embodiment may be a PGW
  • the network side device 1001 in this embodiment may be an access node.
  • the access node is further configured to receive an attach request or a PDN connection establishment request sent by the user terminal 1003, and obtain subscription information of the user terminal 1003.
  • the access node acquires network side capability information
  • the access node feeds back the unauthorized indication information to the user terminal 1003.
  • the access request or the PDN connection establishment request in this embodiment includes multiple access capability information of the user terminal, and the access node is further configured to determine, according to the multiple access capability information of the user terminal, whether the user terminal 1003 supports multiple access functions, if Supporting, the data information of each data gateway 1002 is obtained.
  • the network side device 1001 in this embodiment is further configured to: when the PGW supporting the multiple access function is not selected, send the selection failure information to the user terminal 1003, where the selection failure information is used to indicate that the PGW supporting the multiple access function is not selected. , that is, the user terminal is not allowed to use the multi-access function;
  • the user terminal 1003 is further configured to determine whether the selection failure information and the unauthorized indication information sent by the network side device 1001 are received. If the selection failure information and the unauthorized indication information are not received, the multi-network access connection establishment request is initiated.
  • the network side device 1001 selects a data gateway 1002 capable of supporting multiple access functions from each of the current data gateways 1002 to provide services for the user terminal 1003, so that The data gateway 1002 that the user terminal 1003 provides can support the multiple access function. Therefore, after some services in the PDN connection of the user terminal 1003 are switched to the 3GPP network, other services that do not switch to the 3GPP network can maintain normal communication at the same time, thereby ensuring Normal network communication is not interrupted.
  • an embodiment of the network side device in the embodiment of the present invention includes:
  • the obtaining unit 1202 is configured to acquire multiple access indication information.
  • the sending unit 1203 is configured to send, to the user equipment, multiple access indication information, where the multiple access indication information is used to indicate whether the user terminal is allowed to use the multiple access function.
  • the receiving unit 1201 is configured to receive a request message sent by the user terminal, and trigger the obtaining unit 1202 to perform a corresponding operation.
  • the network side device may not include the receiving unit 1201, and the sending unit 1203 actively sends multiple access indication information to the user terminal when the preset condition is met, where the multiple access indication information is used.
  • the sending unit 1203 automatically broadcasts the current multi-access indication information to the user terminal at intervals, or when the multi-access indication information changes, The unit 1203 broadcasts the current multi-access indication information to the user terminal, or when the other preset conditions are met, the sending unit 1203 can broadcast to the user terminal.
  • the previous multiple access indication information, the specific conditions are not limited herein.
  • the connection request is sent to the network side device in the network to perform the attaching, and the receiving unit 1201 may receive the attach request sent by the user terminal, where the attach request may carry the attach request.
  • the multi-access capability information of the user terminal of the user terminal, the multi-access capability information of the user terminal is used to indicate whether the user terminal supports the multi-access function, or the attach request may carry an indication for requesting multiple access indication information.
  • the indication is used to request feedback multiple access indication information;
  • the obtaining unit 1202 After the receiving unit 1201 receives the attach request sent by the user terminal, the obtaining unit 1202 sends the capability information or the request for requesting multiple access indication information to the data gateway through the serving gateway to request acquisition. The multiple access indication information, the data gateway returns the multiple access indication information to the obtaining unit 1202 through the serving gateway;
  • the sending unit 1203 may send the multiple access indication information to the user terminal, so that the user terminal performs multi-network access control.
  • the network side device in this embodiment may also obtain the subscription information of the user terminal, check the subscription information, and/or verify the multiple access capability information of the user terminal, and perform specific verification and
  • the process is similar to the process in the foregoing embodiment shown in FIG. 2 and FIG. 3, and details are not described herein again.
  • the obtaining unit 1202 may obtain the multiple access indication information in the process of establishing the default bearer, and the sending unit 1203 may use the multiple access indication information.
  • the multiple access indication information is used to indicate whether the user terminal is allowed to use the multiple access function, so that the user terminal performs multi-network access control, so that the user terminal can use the multi-access function to make the PDN
  • some services in the connection are switched to the 3GPP network, other services that do not switch to the 3GPP network can also maintain normal communication at the same time, thereby ensuring normal network communication is not interrupted.
  • the request receiving unit 1301 is configured to receive a request message sent by the user terminal.
  • the information acquiring unit 1302 is configured to acquire multiple access capability information of each data gateway.
  • the selecting unit 1303 is configured to select, according to the multiple access capability information of each data gateway, a data gateway supporting the multiple access function to provide a service for the user terminal.
  • the subscription information verification unit 1304 is configured to acquire the subscription information of the user terminal. If the subscription information does not include information that the user terminal is authorized to access multiple times, or the subscription information indicates that the user terminal is authorized to access multiple times, the information acquisition unit is triggered. 1302 performs the corresponding operation.
  • the indication sending unit 1305 is configured to: when the subscription information of the user terminal indicates that the user terminal is not authorized to access multiple times, send the unauthorized indication information to the user terminal, where the unauthorized indication information is used to indicate that the user terminal is not authorized to access multiple times, when selecting When the unit is not selected to the data gateway supporting the multiple access function, the selection failure information is sent to the user terminal, and the failure information is used to indicate that the data gateway supporting the multiple access function is not selected, that is, the user terminal is not allowed to use the multiple access function. .
  • the specific reason may be that the PGW that supports the multiple access function does not exist in the current network, or the load of the PGW that supports the multiple access function in the current network exceeds a preset threshold, or other types of failure causes, which are not limited herein.
  • the request receiving unit 1301 selects a data gateway capable of supporting multiple access functions from the current data gateways to provide services for the user terminal, thereby enabling the user to be a user.
  • the data gateway provided by the terminal can support multiple access functions. Therefore, when the user terminal uses the multiple access function, after some services in the PDN connection are switched to the 3GPP network, other services that do not switch to the 3GPP network can maintain normal communication at the same time. This ensures that normal network communication is not interrupted.
  • an embodiment of the user terminal in the embodiment of the present invention includes:
  • the information receiving unit 1401 is configured to receive multiple access indication information sent by the network side device.
  • the information check unit 1402 is configured to determine whether to use the multiple access function according to the multiple access indication information, and the multiple network access unit 1403 is configured to initiate a multiple network access connection establishment request when using the multiple access function.
  • the user terminal in this embodiment may further include:
  • the request sending unit 1404 is configured to send a request message to the network side device, where the request message carries multiple access capability information of the user terminal or an indication for requesting multiple access indication information, multiple access capability information of the user terminal, or multiple access request
  • the indication of the indication information is used to request the network side device to feed back the multiple access indication information.
  • the request sending unit 1404 may not be needed in this embodiment. If the network side device needs to initiate the request by the user terminal to feed back the multiple access indication information to the user terminal, the request sending unit 1404 is required in this embodiment.
  • the information receiving unit 1401 may obtain multiple access indication information from the network side device, and the information verification unit 1402 can determine whether to use the multiple access function by using the multiple access indication information, when using the multiple access function.
  • the multi-network access unit 1403 initiates a multi-network access connection establishment request, when the user terminal has multiple access functions, and some services in the PDN connection are switched to the 3GPP network, other services that do not switch to the 3GPP network can also be At the same time, normal communication is maintained, so that normal network communication is not interrupted.
  • another embodiment of the user terminal in the embodiment of the present invention includes:
  • the indication information determining unit 1501 is configured to determine whether the user terminal receives the unauthorized indication information or the selection failure information sent by the network side device, where the unauthorized authorization information is used to indicate that the user terminal is not authorized to access multiple times, and the selection failure information is used to indicate The data gateway supporting the multi-access function is not selected, that is, the user terminal is not allowed to use the multi-access function;
  • the multiple network access unit 1502 is configured to initiate a multi-network access connection establishment request when the unauthorized indication information is not received and the failure information is selected.
  • the user terminal in this embodiment is described below with a specific example: When the user terminal enters the coverage of a certain network, the access node of the network is first requested to attach, and then the access node is connected to the access node. Send an attach request.
  • the access node may obtain the subscription information of the user terminal. If the subscription information indicates that the user terminal is not authorized to access multiple times, the access node sends the unauthorized indication information to the user terminal. Used to indicate that the user terminal is not authorized to access multiple times;
  • the access node may obtain multiple access capability information of each data gateway, specifically Yes: Query the multiple access capability information of the statically configured data gateway, or obtain the multiple access capability information of each data gateway in the current network through DNS resolution.
  • the access node can also obtain the multiple access capability information of each data gateway in the current network by using other methods.
  • the specific manner is not limited herein.
  • the data gateway supporting the multiple access function can be selected from the data gateways to provide services for the user terminal, and it should be noted that If the ingress node does not select a data gateway that supports the multi-access function, it sends a selection failure message to the user terminal to indicate that the data gateway supporting the multi-access function is not selected, that is, the user terminal is not allowed to use the multi-access function.
  • the reason why the data gateway supporting the multiple access function is not selected may be that each data gateway in the current network does not support the multiple access function, or the data gateway supporting the multiple access function in the current network exceeds the load. Preset thresholds, etc.
  • the indication information determining unit 1501 in the user terminal may determine whether the selection failure information is received from the access node, or the unauthorized indication information is received. If any one of the information is received, the multiple access function cannot be normally used, The network access unit 1502 prohibits the initiation of the multi-network access connection establishment request, that is, when the user requests multi-network access or the network environment changes, and multiple network access is required, the multi-network access unit 1502 rejects the corresponding target. The network sends an access connection setup request.
  • the multi-network access unit 1502 allows to initiate a multi-network access connection establishment request, that is, when the user requests multi-network access, the multi-network access unit 1502 sends an access connection establishment request to the corresponding target network. Or, when the network environment changes and multiple network access is required, the user terminal sends an access connection establishment request to the corresponding target network.
  • the multi-network access unit 1502 establishes an access connection. Before the request, it is also necessary to determine whether it can support the multi-access function. If it can support, it sends an access connection establishment request. If it cannot be supported, the access connection establishment request will not be sent.
  • the indication information determining unit 1501 does not receive the selection failure information and does not receive the unauthorized indication information, it indicates that the network side device has selected the data gateway capable of supporting the multiple access function for the current user terminal. The service is performed. Therefore, when the user terminal uses the multiple access function, after some services in the PDN connection are switched to the 3GPP network, other services that do not switch to the 3GPP network can maintain normal communication at the same time, thereby ensuring normal network communication is not interrupted.
  • the program can be stored in a computer readable storage medium.
  • the storage medium can include: ROM, RAM, disk or CD, etc.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Telephonic Communication Services (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Telephone Function (AREA)
  • Computer And Data Communications (AREA)

Abstract

本发明实施例公开了一种多网接入控制方法、通讯系统以及相关设备,用于在使用多接入功能时保证正常的网络通信不被中断。本发明实施例方法包括:用户终端接收网络侧设备发送的多接入指示信息;用户终端根据所述多接入指示信息判断用户终端是否使用多接入功能;用户终端在使用多接入功能时发起多网接入连接建立。本发明实施例还提供一种通讯系统以及相关设备。本发明实施例可以使得在使用多接入功能时保证正常的网络通信不被中断。

Description

多网接入控制方法、 通讯系统以及相关设备
技术领域
本发明涉及通讯领域, 尤其涉及一种多网接入控制方法、 通讯系统以及相 关设备。 背景技术 当支持多接入功能的用户终端从 non-3GPP 网络移动到 non-3GPP 网络和 3GPP网络的共同覆盖区域时,如果用户终端打算将部分业务切换到 3GPP网络, 同时部分业务仍保留在 non-3GPP网络,用户终端将在 3GPP网络发起连接建立。 例如, 某支持多接入功能的用户终端有一个分组数据网络(PDN, Packet Data Network )连接, 通过分组数据网络网关( PGW, PDN Gate Way )接入分组数据 网络, 用户终端打算将该 PDN连接的一部分业务流切换到 3GPP网络, 则该用 户终端会在 3GPP网络中建立新的 PDN连接, 如果 PGW不支持多接入功能, 则该 PGW会释放该用户终端与该 PGW上的 PDN连接相关的资源, 这将导致 用户终端使用多接入功能时, PDN连接中没有切换到 3GPP网络的部分业务被 中断, 从而影响正常的网络通信。 发明内容
本发明实施例提供了一种多网接入控制方法、 通讯系统以及相关设备, 能 够在使用多接入功能时保证正常的网络通信不被中断。
本发明实施例提供的多网接入控制方法, 包括: 用户终端接收网络侧设备 发送的多接入指示信息; 用户终端根据所述多接入指示信息判断用户终端是否 使用多接入功能; 用户终端在使用多接入功能时发起多网接入连接建立。
本发明实施例提供的多网接入控制方法, 包括: 网络侧设备接收用户终端 发送的请求消息; 网络侧设备获取各数据网关的多接入能力信息; 网络侧设备 根据所述各数据网关的多接入能力信息选择支持多接入功能的数据网关为所述 用户终端提供服务。
本发明实施例提供的通讯系统, 包括: 网络侧设备, 用于获取多接入指示 信息, 向用户终端发送所述多接入指示信息; 用户终端, 用于接收网络侧设备 发送的多接入指示信息, 根据所述多接入指示信息判断用户终端是否使用多接 入功能, 在使用所述多接入功能时发起多网接入连接建立请求。
本发明实施例提供的通讯系统, 包括: 网络侧设备, 用于接收用户终端发 送的请求消息, 获取各数据网关的多接入能力信息, 根据所述各数据网关的多 接入能力信息选择支持多接入功能的数据网关为所述用户终端提供服务; 数据 网关, 用于向所述网络侧设备提供所述数据网关的多接入能力信息; 用户终端, 用于向所述网络侧设备发送请求消息。
本发明实施例提供的网络侧设备, 包括: 获取单元, 用于获取多接入指示 信息; 发送单元, 用于向用户终端发送所述多接入指示信息, 所述多接入指示 信息用于指示所述用户终端是否允许使用多接入功能。
本发明实施例提供的网络侧设备, 包括: 请求接收单元, 用于接收用户终 端发送的请求消息; 信息获取单元, 用于获取各数据网关的多接入能力信息; 选择单元, 用于根据所述各数据网关的多接入能力信息选择支持多接入功能的 数据网关为所述用户终端提供服务。
本发明实施例提供的用户终端, 包括: 信息接收单元, 用于接收网络侧设 备发送的多接入指示信息; 信息校验单元, 用于根据所述多接入指示信息判断 用户终端是否使用多接入功能; 多网接入单元, 用于在使用多接入功能时发起 多网接入连接建立请求。
本发明实施例提供的用户终端, 包括: 指示信息判断单元, 用于判断用户 终端是否接收到网络侧设备发送的未授权指示信息或选择失败信息, 所述未授 权指示信息用于指示所述用户终端未被授权多接入, 所述选择失败信息用于指 示用户终端不允许使用多接入功能; 多网接入单元, 用于当未接收到所述未授 权指示信息以及所述选择失败信息时发起多网接入连接建立请求。
从以上技术方案可以看出, 本发明实施例具有以下优点:
本发明实施例中, 用户终端可以从网络侧设备获取到多接入指示信息, 并 能通过该多接入指示信息判断用户终端是否可以使用多接入功能, 当判断用户 终端可以使用多接入功能时, 用户终端才会发起多网接入连接建立请求, 所以 当用户终端使用多接入功能,使得 PDN连接中部分业务切换到 3GPP网络之后, 没有切换到 3GPP网络的其他业务也能够同时保持正常通信,从而保证正常的网 络通信不被中断;
本发明另一实施例中, 网络侧设备在接收到用户终端的请求之后, 会从当 前各数据网关中选取能够支持多接入功能的数据网关为该用户终端提供服务, 从而可以使得为用户终端提供服务的数据网关能够支持多接入功能, 所以当用 户终端使用多接入功能, 使得 PDN连接中部分业务切换到 3GPP网络之后, 没 有切换到 3GPP网络的其他业务也能够同时保持正常通信,从而保证正常的网络 通信不被中断。 附图说明
图 1为本发明实施例中多网接入控制方法一个实施例示意图
图 2为本发明实施例中多网接入控制方法另一实施例示意图
图 3为本发明实施例中多网接入控制方法另一实施例示意图
图 4为本发明实施例中多网接入控制方法另一实施例示意图
图 5为本发明实施例中多网接入控制方法另一实施例示意图
图 6为本发明实施例中多网接入控制方法另一实施例示意图
图 7为本发明实施例中多网接入控制方法另一实施例示意图
图 8为本发明实施例中多网接入控制方法另一实施例示意图
图 9为本发明实施例中多网接入控制方法另一实施例示意图
图 10为本发明实施例中通讯系统一个实施例示意图; 图 11为本发明实施例中通讯系统另一实施例示意图;
图 12为本发明实施例中网络侧设备一个实施例示意图;
图 13为本发明实施例中网络侧设备另一实施例示意图;
图 14为本发明实施例中用户终端一个实施例示意图;
图 15为本发明实施例中用户终端另一实施例示意图。 具体实施方式
本发明实施例提供了一种多网接入控制方法、 通讯系统以及相关设备, 用 于在使用多接入功能时保证正常的网络通信不被中断。
请参阅图 1, 本发明实施例中多网接入控制方法一个实施例包括:
101、 用户终端接收网络侧设备发送的多接入指示信息;
本实施例中, 用户终端可以从网络侧设备接收到多接入指示信息, 该多接 入指示信息用于表示网络侧是否支持多接入功能, 该多接入指示信息具体可以 为网络侧能力信息, 或者是直接表示网络侧是否支持多接入功能的指示信息。
需要说明的是, 本实施例中, 用户终端可以通过向网络侧设备发送请求消 息以请求获取多接入指示信息, 或者用户终端还可以接收网络侧设备主动发送 的多接入指示信息, 例如网络侧设备每隔一段时间即自动向用户终端广播当前 的多接入指示信息, 或者是网络侧设备检测到网络侧能力发生变化时, 则向用 户终端广播当前的多接入指示信息, 或者是满足其他的预置条件时, 网络侧设 备均可向用户终端广播当前的多接入指示信息, 具体的条件此处不作限定。
102、 用户终端根据多接入指示信息判断是否使用多接入功能, 若是, 则执 行步骤 103, 若否, 则执行步骤 104;
用户终端在从网络侧设备获取到多接入指示信息之后, 则可根据该多接入 指示信息判断当前网络侧是否支持多接入功能, 需要说明的是, 用户终端还可 以进一步判断自身是否支持多接入功能, 若网络侧支持多接入功能, 且用户终 端也支持多接入功能, 则确定可以使用多接入功能, 即可执行步骤 103, 若网络 侧不支持多接入功能, 或用户终端不支持多接入功能, 则确定不能使用多接入 功能, 即可执行步骤 104;
可以理解的是, 用户终端也可以只判断网络侧是否支持多接入功能, 若支 持, 则确定可以使用多接入功能, 即可执行步骤 103, 若不支持, 则确定不能使 用多接入功能, 即可执行步骤 104。
103、 允许发起多网接入连接建立请求;
若用户终端确认可以使用多接入功能, 则允许发起多网接入连接建立请求, 即当用户请求进行多网接入时, 用户终端向对应的目标网络发送接入连接建立 请求, 或者是当网络环境发生变化, 需要进行多网接入时, 用户终端向对应的 目标网络发送接入连接建立请求。
104、 禁止发起多网接入连接建立请求。
若用户终端确认不能使用多接入功能, 则禁止发起多网接入连接建立请求, 即当用户请求进行多网接入或网络环境发生变化, 需要进行多网接入时, 用户 终端会拒绝向对应的目标网络发送接入连接建立请求。
本发明实施例中, 用户终端可以从网络侧设备获取到多接入指示信息, 并 能通过该多接入指示信息判断用户终端是否可以使用多接入功能, 当判断用户 终端可以使用多接入功能时, 用户终端才会发起多网接入连接建立请求, 所以 当用户终端使用多接入功能,使得 PDN连接中部分业务切换到 3GPP网络之后, 没有切换到 3GPP网络的其他业务也能够同时保持正常通信,从而保证正常的网 络通信不被中断。
为便于理解, 下面以用户终端向网络侧设备请求获取多接入指示信息为例 进行说明, 按照不同的获取流程, 具体可以包括以下几种情况:
一、 附着流程:
本实施例中在附着流程下获取多接入指示信息的步骤具体可以包括: ( 1 )用户终端向接入节点发送附着请求;
当用户终端进入某一网络的覆盖范围时, 首先会向该网络的接入节点请求 进行附着, 则用户终端可以向接入节点发送附着请求。
本实施例中, 该附着请求中可以携带有该用户终端自身的用户终端的多接 入能力信息, 该用户终端的多接入能力信息用于指示该用户终端是否支持多接 入功能, 或者该附着请求中可以携带请求多接入指示信息的指示, 该请求多接 入指示信息的指示用于请求接入节点反馈多接入指示信息, 可以理解的是, 本 实施例中的附着请求也可以不携带这些参数。
本实施例中的多接入指示信息具体可以为网络侧能力信息, 或者是直接表 示网络侧是否支持多接入功能的指示信息。
本实施例中, 具体的用户终端的多接入能力信息或指示信息可以携带在附 着请求的保留位中, 或者可以在附着请求中新扩展一个字段用于携带用户终端 的多接入能力信息或请求多接入指示信息的指示, 具体携带的方式此处不作限 定。
( 2 )接入节点获取多接入指示信息;
本实施例中当接入节点接收到用户终端发送的附着请求之后, 可以在建立 PDN连接的过程中从数据网关获取到多接入指示信息。
若附着请求中携带有用户终端的多接入能力信息或请求多接入指示信息的 指示, 则在建立 PDN连接的过程中, 接入节点可以将该能力信息或请求多接入 指示信息的指示通过建立 PDN连接请求消息发送至数据网关, 以请求数据网关 反馈多接入指示信息, 本实施例中的建立 PDN连接请求消息可以为建立缺省承 载请求消息。
若附着请求中不携带用户终端的多接入能力信息或请求多接入指示信息的 指示, 则接入节点可以按照运营商预先配置的策略, 在接收到用户终端发送的 附着请求之后, 即请求数据网关反馈多接入指示信息。
需要说明的是, 若附着请求中携带的是用户终端的多接入能力信息, 则接 入节点或者数据网关还可以对该用户终端的多接入能力信息进行校验, 判断该 用户终端是否支持多接入功能, 若确定用户终端不支持多接入功能, 则可以不 获取多接入指示信息, 若确定用户终端支持多接入功能, 则可以获取多接入指 示信息。
具体的校验可以分为接入节点校验以及数据网关校验:
当接入节点校验时, 接入节点根据用户终端的多接入能力信息判断用户终 端是否支持多接入功能, 若支持, 则在建立 PDN连接的过程中, 将用户终端的 多接入能力信息或接入节点自身生成的请求多接入指示信息的指示通过建立 PDN连接请求消息发送至数据网关以请求反馈多接入指示信息;
当数据网关校验时, 接入节点在建立 PDN连接的过程中, 将用户终端的多 接入能力信息通过建立 PDN连接请求消息发送至数据网关, 数据网关根据用户 终端的多接入能力信息判断用户终端是否支持多接入功能, 若支持, 则将多接 入指示信息携带于建立 PDN连接响应消息中发送至接入节点。
可以理解的是, 对用户终端的多接入能力信息的校验过程并非是必要过程, 实际应用中, 可以不对用户终端的多接入能力信息进行校验而直接获取多接入 指示信息。
需要说明的是, 本实施例中, 接入节点还可以根据用户终端的附着请求从 数据库中获取该用户终端的签约信息, 若该签约信息中没有包含该用户终端是 否被授权多接入的信息, 或者是该签约信息指示该用户终端被授权多接入, 则 接入节点可以获取多接入指示信息, 若该签约信息指示该用户终端未被授权多 接入, 则接入节点可以不获取多接入指示信息, 并向用户终端反馈未授权指示 信息, 可以理解的是, 对用户终端签约信息的校验过程并非是必要过程, 实际 应用中, 可以不对用户终端签约信息进行校验而直接获取多接入指示信息。
( 3 )接入节点向用户终端反馈多接入指示信息;
接入节点获取到多接入指示信息之后, 则可以向用户终端反馈该多接入指 示信息。
若接入节点或数据网关通过用户终端的多接入能力信息判断用户终端不支 持多接入功能, 则接入节点可以向用户终端返回 "用户终端不支持多接入功能" 信息。
( 4 )用户终端接收接入节点发送的多接入指示信息;
接入节点向用户终端反馈多接入指示信息之后, 则用户终端可以接收到该 多接入指示信息。
如果用户终端接收到接入节点发送的 "用户终端不支持多接入功能"信息, 则用户终端可以直接禁止发起多网接入连接建立请求并且结束流程。
( 5 ) 用户终端根据多接入指示信息判断用户终端是否可以使用多接入功 能, 若是, 则允许发起多网接入连接建立请求, 若否, 则禁止发起多网接入连 接建立请求。
用户终端在从网络侧设备获取到多接入指示信息之后, 则可根据该多接入 指示信息判断当前网络侧是否支持多接入功能, 需要说明的是, 用户终端还可 以进一步判断自身是否支持多接入功能, 若网络侧支持多接入功能, 且用户终 端也支持多接入功能, 则确定可以使用多接入功能, 若网络侧不支持多接入功 能, 或用户终端不支持多接入功能, 则确定不能使用多接入功能;
可以理解的是, 用户终端也可以只判断网络侧是否支持多接入功能, 若支 持, 则确定可以使用多接入功能, 若不支持, 则确定不能使用多接入功能。
若用户终端确认可以使用多接入功能, 则允许发起多网接入连接建立请求, 即当用户请求进行多网接入时, 用户终端向对应的目标网络发送接入连接建立 请求, 或者是当网络环境发生变化, 需要进行多网接入时, 用户终端向对应的 目标网络发送接入连接建立请求。
若用户终端确认不能使用多接入功能, 则禁止发起多网接入连接建立请求, 即当用户请求进行多网接入或网络环境发生变化, 需要进行多网接入时, 用户 终端会拒绝向对应的目标网络发送接入连接建立请求。
上面描述了在附着过程中用户终端从接入节点获取数据网关的多接入能力 信息的流程, 在具体的网络中, 接入节点以及数据网关所指代的网元可能有所 不同, 在 3GPP 网络中, 接入节点可以为移动性管理实体 ( MME, Mobility Management Entity )以 SJ良务网关( SGW, Serving GateWay ), 数据网关可以为 分组数据网络网关( PGW, Packet data network GateWay ), 下面以 3GPP网络为 例进行详细说明, 具体请参阅图 2, 本发明实施例中多网接入控制方法另一实施 例包括:
201、 用户终端向接入网络的 MME发起附着请求( Attach Request );
当用户终端进入某一网络的覆盖范围时,首先会向该网络的 MME请求进行 附着, 则会向 MME发送附着请求。
本实施例中的附着请求可以包含用户终端的多接入能力信息, 或者请求多 接入指示信息的指示, 该附着请求可以增加一个字段, 用于携带用户终端的多 接入能力信息, 或者请求多接入指示信息的指示, 或者其他形式的指示信息, 用于指示 MME反馈多接入指示信息。
202、 MME向用户终端发起身伤 i证请求( Identity Request );
当 MME接收到用户终端发送的附着请求之后,可以向用户终端发送身份认 证请求以对用户终端的身份进行认证。
203、 用户终端向 MME发送身份认证响应 ( Identity Response );
204、 MME与用户终端之间互相进行鉴权 ( Authentication );
MME可以通过归属用户服务器(HSS, Home Subscriber Server ) 中存储的 用户信息与用户终端进行相互鉴权。
205、 MME通过设备识别寄存器(EIR, Equipment Identity Register )用户 终端的设备进行认证 ( IMEI Check );
上述步骤 202至 205为鉴权过程, 包括身份认证和设备认证。
需要说明的是,如果在实际应用中能够保证用户终端与 MME都是绝对安全 可靠的,或者是附着过程对安全性要求不高,则可以不执行上述步骤 202至 205。
206、 MME更新用户终端在 HSS中的位置信息 ( Update Location );
207、 MME接收 HSS的位置更新确认消息( Update Location Ack ), 同时获 得用户终端的签约信息; 208、 MME 向 SGW发送建立缺省承载请求消息 (Create Default Bearer Request );
若 MME在步骤 207中获得的用户终端的签约信息中没有用户终端是否被授 权多接入的信息,或者是签约信息指示用户终端被授权多接入,则 MME向 SGW 发送的建立缺省承载请求消息中可以携带有在步骤 201 中获取到的用户终端的 多接入能力信息或者请求多接入指示信息的指示, 需要说明的是, 若步骤 201 中的附着请求中没有携带用户终端的多接入能力信息或者请求多接入指示信息 的指示, 则 MME可以按照运营商预置的策略向 SGW发送建立缺省承载请求消 息, 该建立缺省承载请求消息中请求多接入指示信息的指示, 该请求多接入指 示信息的指示用于请求 PGW反馈多接入指示信息。
若 MME在步骤 207中获得的用户终端的签约信息指示用户终端未被授权多 接入, 则 MME在发给 SGW的建立缺省承载请求消息可以不携带指示信息, 而 只是按照普通的流程建立缺省承载。
本实施例中,若 MME在步骤 201中获取到的是请求多接入指示信息的指示, 则 MME可以直接将携带该请求多接入指示信息的指示的建立缺省承载请求消 息发送给 SGW,若 MME在步骤 201中获取到的是用户终端的多接入能力信息, 则 MME还可以根据该用户终端的多接入能力信息判断该用户终端是否支持多 接入功能,并且可以在用户终端支持多接入功能的情况下才向 SGW发送携带该 用户终端的多接入能力信息的建立缺省承载请求消息。
上述提到的用户终端签约信息的校验和用户终端的多接入能力的校验在实 际应用中也可以结合进行, 例如当签约信息指示用户被授权多接入, 且用户终 端支持多接入功能时, MME才将用户终端的多接入能力信息发送至 SGW。
需要说明的是, 上述对用户终端签约信息的校验和对用户终端的多接入能 力的校验并非必选的过程, 在实际应用中, MME同样可以不进行校验, 而直接 将用户终端的多接入能力信息或者请求多接入指示信息的指示通过建立缺省承 载请求消息发送给 SGW。 209、 当 SGW与 PGW之间使用通用分组无线业务隧道协议(GTP, General packet radio service Tunneling Protocol )进行信令交互时, SGW向 PGW发送建 立缺省承载请求消息 ( Create Default Bearer Request ); 当 SGW与 PGW之间使 用代理移动互联网协议( PMIP, Proxy Mobile IP )进行信令交互时, SGW向 PGW 发送代理绑定更新消息 ( Proxy Binding Update );
SGW通过建立缺省承载请求消息或代理绑定更新消息向 PGW转发收到的 用户终端的多接入能力信息或者请求多接入指示信息的指示。
本实施例中, 若 SGW接收到的是请求多接入指示信息的指示, 则 SGW可 以直接通过建立缺省承载请求消息或代理绑定更新消息向 PGW转发请求多接 入指示信息的指示。
本实施例中, 若 SGW接收到的是用户终端的多接入能力信息, 则 SGW同 样可以校验该用户终端是否支持多接入功能, 并且可以当用户终端支持多接入 功能时, 将用户终端的多接入能力信息通过建立缺省承载请求消息或代理绑定 更新消息发送至 PGW。
需要说明的是, 上述对用户终端的多接入能力的校验并非必选的过程, 在 实际应用中, SGW同样可以不进行校验, 而直接将用户终端的多接入能力信息 通过建立缺省承载请求消息或代理绑定更新消息发送给 PGW。
210、 当 SGW与 PGW之间使用 GTP协议进行信令交互时, PGW向 SGW 发送建立缺省承载响应消息( Create Default Bearer Response ); 当 SGW与 PGW 之间使用 PMIP协议进行信令交互时, PGW向 SGW发送代理绑定确认消息
( Proxy Binding Ack );
若 PGW从 SGW收到的是用户终端的多接入能力信息, 则 PGW可以根据 收到的用户终端的多接入能力信息校验用户终端是否支持多接入功能, 若确定 用户终端支持多接入功能,则 PGW则通过建立缺省承载响应消息或代理绑定确 认消息向 SGW发送 PGW的多接入能力信息, 并根据该 PGW的多接入能力信 息发送多接入指示信息,即该多接入指示信息中可以包含 PGW的多接入能力信 息, 若确定用户终端不支持多接入功能, 则 PGW发送的建立缺省承载响应消息 或代理绑定确认消息中可以不包含 PGW的多接入能力信息。
若 PGW从 SGW收到的是请求多接入指示信息的指示时, 则 PGW可以直 接通过建立缺省承载响应消息或代理绑定确认消息向 SGW发送 PGW的多接入 能力信息, 并根据该 PGW的多接入能力信息发送多接入指示信息。
需要说明的是, 上述对用户终端的多接入能力的校验并非必选的过程, 在 实际应用中, PGW同样可以不进行校验, 而直接通过建立缺省承载响应消息或 代理绑定确认消息向 SGW发送 PGW的多接入能力信息。
本实施例中, PGW可以通过建立缺省承载响应消息或代理绑定确认消息向 SGW发送 PGW的多接入能力信息, 同样的, PGW也可以先判断自身是否支持 多接入功能, 若支持, 则在建立缺省承载响应消息或代理绑定确认消息中携带 PGW支持多接入功能指示信息, 并根据该 PGW支持多接入功能指示信息发送 多接入指示信息, 若不支持, 则在建立缺省承载响应消息或代理绑定确认消息 中携带 PGW不支持多接入功能指示信息, 并根据该 PGW不支持多接入功能指 示信息发送多接入指示信息。
211、 SGW 向 MME发送建立缺省承载响应消息 (Create Default Bearer Response );
若 SGW从 PGW收到多接入指示信息(可以是 PGW的多接入能力信息, 或 PGW支持多接入功能指示信息, 或 PGW不支持多接入功能指示信息), 则 SGW可以通过建立缺省承载响应消息向 MME转发该多接入指示信息。
212、 MME向演进通用移动通信系统陆地无线接入网(E-UTRAN, Evolved Universal mobile telecommunications system Territorial Radio Access Network )发 送附着接受消息 ( Attach Accept );
若 MME从 SGW收到多接入指示信息, 则 MME可以通过附着接受消息向 E-UTRAN发送多接入指示信息。
需要说明的是,若 MME在之前进行了签约信息的校验,且用户终端未被授 权多接入, 则本步骤中, MME向 E-UTRAN发送的附着接受消息中可以携带未 授权指示信息, 并根据该未授权指示信息发送多接入指示信息, 用于指示用户 终端未被授权多接入。
若该多接入指示信息包含 PGW的多接入能力信息, 则 MME也可以先根据 收到的 PGW的多接入能力信息确定 PGW是否支持多接入功能, 若确定 PGW 支持多接入功能, 则 MME向 E-UTRAN发送 PGW支持多接入功能指示信息; 若确定 PGW不支持多接入功能, 则 MME向 E-UTRAN发送 PGW不支持多接 入功能指示信息, 并根据该 PGW支持多接入功能指示信息或 PGW不支持多接 入功能指示信息发送多接入指示信息。
可以理解的是, 若该多接入指示信息包括 PGW的多接入能力信息, MME 也可以直接将该多接入指示信息发送给 E-UTRAN。
若该多接入指示信息中包含 PGW支持多接入功能指示信息或 PGW不支持 多接入功能指示信息, 则 MME可以直接向 E-UTRAN发送该多接入指示信息。
213、 E-UTRAN 向用户终端发送无线资源控制 ( RRC, Radio Resource Control )连接重配置消息( RRC Connection Reconfiguration );
若 E-UTRAN收到 MME发送的多接入指示信息(可以为 PGW的多接入能 力信息, 或 PGW支持多接入功能指示信息, 或 PGW不支持多接入功能指示信 息, 或未授权指示信息), 则 E-UTRAN将收到的该多接入指示信息通过 RRC 连接重配置消息发送给用户终端。
214、用户终端向 E-UTRAN发送 RRC连接重配置完成消息( RRC Connection Reconfiguration Complete );
215、 E-UTRAN向 MME发送附着完成消息( Attach Complete );
216、 MME向 SGW发送更新承载请求消息( Update Bearer Request );
217、 SGW向 MME发送更新 载响应消息( Update Bearer Response )。 本实施例中, 用户终端收到多接入指示信息之后, 即可以根据多接入指示 信息确定用户终端是否可以使用多接入功能, 若可以使用, 则用户终端允许发 起多网接入连接建立请求, 若不能使用, 则禁止发起多网接入连接建立请求。 具体的确定方式可以为:
若多接入指示信息中包含 PGW的多接入能力信息, 该 PGW的多接入能力 信息指示 PGW支持多接入功能, 且用户终端自身也支持多接入功能时, 用户终 端确定可以使用多接入功能, 若该 PGW的多接入能力信息指示 PGW不支持多 接入功能, 或用户终端自身不支持多接入功能时, 用户终端确定不可以使用多 接入功能;
若多接入指示信息中包含 PGW支持多接入功能指示信息,且用户终端自身 也支持多接入功能时, 用户终端确定可以使用多接入功能, 若多接入指示信息 中包含 PGW 不支持多接入功能指示信息, 或用户终端自身不支持多接入功能 时, 用户终端确定不可以使用多接入功能。
若多接入指示信息中包含未授权指示信息, 则无论用户终端自身是否支持 多接入功能, 用户终端均确定不可以使用多接入功能。
本实施例中的 MME可以看作是接入节点,该接入节点随着不同的应用网络 可能会有所不同,本实施例的 3GPP网络中仅以 MME视为接入节点为例进行说 明, 可以理解的是, 在实际应用中, 该接入节点可以是其他的网元, 例如为服 务通用分组无线业务支持节点 (SGSN, Serving General Packet Radio Service Support Node ), 具体的接入节点还可以是其他网元, 本实施例中的数据网关为 PGW,在实际应用中还可以为网关通用分组无线业务支持节点( GGSN, Gateway General Packet Radio Service Support Node ), 或移动 4苗点, 或其他类型的网元, 此处不作限定。
本实施例中,用户终端可以通过向 MME发送附着请求以请求 MME反馈多 接入指示信息, MME 收到该附着请求后, 可以在建立缺省承载过程中, 通过 SGW从 PGW获取到 PGW的多接入能力信息, 并根据该 PGW的多接入能力信 息发送多接入指示信息, 或者直接获取 PGW是否支持多接入功能指示信息, 根 据 PGW是否支持多接入功能指示信息发送多接入指示信息,所以能够向用户终 端反馈该多接入指示信息, 因此用户终端可以获取到多接入指示信息判断用户 终端是否可以多接入功能, 当判断可以使用多接入功能时, 用户终端才会发起 多网接入连接建立请求, 所以当用户终端使用多接入功能, 使得 PDN连接中部 分业务切换到 3GPP网络之后,没有切换到 3GPP网络的其他业务也能够同时保 持正常通信, 从而保证正常的网络通信不被中断;
其次, 本实施例中, MME可以对用户终端的签约信息进行校验, 当签约信 息指示用户终端未被授权多接入时, 多接入指示信息中可以只包含未授权指示 信息, 而不必包含 PGW的多接入能力信息, 因此能够进一步减少网元之间传输 的数据, 减少网络负荷。
上述实施例中是以 3GPP 网络内的附着流程为例进行说明的, 可以理解的 是,在实际应用中, 用户终端同样可以通过非 3GPP网络内的附着流程获取数据 网关的多接入能力信息, 在非 3GPP 网络中, 接入节点可以为移动接入网关 ( MAG, Mobility Access Gateway ), 数据网关可以为 PGW, 具体请参阅图 3, 本发明实施例中多网接入控制方法另一实施例包括:
301、 用户终端与 MAG 执行非 3GPP 特定流程 ( Non-3 GPP specific procedures );
本实施例中的 MAG为接入节点中的一种, 该 MAG具体可以为非 3GPP网 络 IP 接入网关, 或者是演进分组数据网关 (EPDG , Evolved Packet Data Gateway )。
302、 用户终端与 MAG通过 HSS或认证授权计费 (AAA, Authentication Authorization Accounting )月良务器进行认证 ( Authentication & Authorization ); 本实施例中, MAG可以通过 HSS或 AAA服务器获得用户终端的签约信息。
303、 用户终端向 MAG发起触发附着流程 ( L3 Attach Trigger ), 向 MAG接 入网关发送附着请求;
本实施例中, 该附着请求中可以携带用户终端的多接入能力信息, 或者请 求多接入指示信息的指示, 该附着请求可以增加一个字段, 用于携带用户终端 的多接入能力信息, 或者请求多接入指示信息的指示, 或者其他形式的指示信 息, 用于指示 MAG反馈多接入指示信息。
若 MAG获得的用户终端的签约信息中没有用户终端是否被授权多接入的 信息, 或者是签约信息指示用户终端被授权多接入, 则 MAG在向 PGW发送消 息时可以携带有 MAG获取到的用户终端的多接入能力信息或者请求多接入指 示信息的指示, 需要说明的是, 若步骤 301 中的附着请求中没有携带用户终端 的多接入能力信息或者请求多接入指示信息的指示,则 MAG可以按照运营商预 置的策略向 PGW发送消息, 该消息中包含请求多接入指示信息的指示, 该请求 多接入指示信息的指示用于请求 PGW反馈多接入指示信息。
若 MAG 获得的用户终端的签约信息指示用户终端未被授权多接入, 则 MAG在发给 PGW的消息中可以不携带指示信息,而只是按照普通的流程处理。
本实施例中,若 MAG在步骤 301中获取到的是请求多接入指示信息的指示, 则 MAG可以直接将携带该请求多接入指示信息的指示的消息发给 PGW, 若 MAG在步骤 301中获取到的是用户终端的多接入能力信息, 则 MAG还可以根 据该用户终端的多接入能力信息判断该用户终端是否支持多接入功能, 并且可 以在用户终端支持多接入功能的情况下才向 PGW发送携带该用户终端的多接 入能力信息的消息。
上述提到的用户终端签约信息的校验和用户终端的多接入能力的校验在实 际应用中也可以结合进行, 例如当签约信息指示用户被授权多接入, 且用户终 端支持多接入功能时, MAG才将用户终端的多接入能力信息发送至 PGW。
需要说明的是, 上述对用户终端签约信息的校验和对用户终端的多接入能 力的校验并非必选的过程, 在实际应用中, MAG同样可以不进行校验, 而直接 将用户终端的多接入能力信息或者请求多接入指示信息的指示发送给 PGW。
304、 网关控制会话建立流程 ( Gateway Control Session Establishment Procedure );
305、 MAG向 PGW发送代理绑定更新消息( Proxy Binding Update ); 该代理绑定更新消息中可以包含前述步骤 303 中的用户终端的多接入能力 信息或请求多接入指示信息的信息。
306、 PGW发起与归属策略控制计费规则功能实体( PCRF, Policy Control and Charging Rules Function ) 的 IP 连接接入网会话建立流程 (IP-Can Session Establishment Procedure );
307、 PGW向 HSS/AAA服务器更新用户的 PDN连接的 PGW标识信息和 接入点名称( APN, Access Point Name )信息;
308、 PGW向 MAG发送代理绑定确认消息( Proxy Binding Ack );
当 PGW收到 MAG发送的用户终端的多接入能力信息时, PGW可以校验 用户终端的多接入能力信息, 若确定用户终端支持多接入功能, 则 PGW可以向 MAG发送多接入指示信息;
如果用户终端不支持多接入功能, 则 PGW可以不向 MAG发送多接入指示 信息。
当 PGW收到 MAG发送的请求多接入指示信息的指示时, PGW可以直接 向 MAG发送多接入指示信息。
可以理解的是,若 MAG发送的代理绑定更新消息中既不包含用户终端的多 接入能力信息也不包含请求多接入指示信息的指示,则 PGW仍可以根据运营商 策略直接向 MAG反馈多接入指示信息。
本步骤中的多接入指示信息可以包括 PGW的多接入能力信息,需要说明的 是, PGW在接收到 MAG发送的消息之后, 也可以首先判断 PGW自身是否支 持多接入功能, 若支持, 则可以向 MAG反馈 PGW支持多接入功能指示信息, 若不支持,则可以向 MAG反馈 PGW不支持多接入功能指示信息,可以根据 PGW 支持多接入功能指示信息或 PGW不支持多接入功能指示信息发送多接入指示 信息。
309、 PGW与 MAG之间的代理移动 IP隧道建立 ( PMIP Tunnel );
310、 归属 PCRF可能发起的网关控制的会话修改流程更新 MAG中的 QoS 信息 ( Gateway Control and QoS Rules Provision Procedure );
311、 附着完成。
MAG从 PGW收到多接入指示信息之后,若该多接入指示信息中包含 PGW 的多接入能力信息,则 MAG可以首先判断 PGW是否支持多接入功能,若支持, 则 MAG通过附着完成的过程向用户终端发送 PGW支持多接入功能指示信息, 若 MAG判定 PGW不支持多接入功能, MAG通过附着完成的过程向用户终端 发送 PGW不支持多接入功能指示信息, 并且根据该 PGW支持多接入功能指示 信息或 PGW不支持多接入功能指示信息发送多接入指示信息。
可以理解的是, 本实施例中, MAG也可以将包含该 PGW的多接入能力信 息的多接入指示信息直接发送给用户终端。
需要说明的是,若 MAG从 PGW收到的多接入指示信息中本身就包含 PGW 支持多接入功能指示信息或 PGW不支持多接入功能指示信息, 则 MAG可以直 接将该多接入指示信息发给用户终端。
本实施例中,若步骤 303中 MAG获得的用户终端的签约信息指示用户终端 未被授权多接入, 则在本步骤中, MAG可以向用户终端发送未授权指示, 并根 据该未授权指示发送多接入指示信息。
本实施例中, 用户终端收到多接入指示信息之后, 即可以根据多接入指示 信息确定用户终端是否可以使用多接入功能, 若可以使用, 则用户终端允许发 起多网接入连接建立请求, 若不能使用, 则禁止发起多网接入连接建立请求。
具体的确定方式可以为:
若多接入指示信息中包含 PGW的多接入能力信息, 该 PGW的多接入能力 信息指示 PGW支持多接入功能, 且用户终端自身也支持多接入功能时, 用户终 端确定可以使用多接入功能, 若该 PGW的多接入能力信息指示 PGW不支持多 接入功能, 或用户终端自身不支持多接入功能时, 用户终端确定不可以使用多 接入功能;
若多接入指示信息中包含 PGW支持多接入功能指示信息,且用户终端自身 也支持多接入功能时, 用户终端确定可以使用多接入功能, 若多接入指示信息 中包含 PGW 不支持多接入功能指示信息, 或用户终端自身不支持多接入功能 时, 用户终端确定不可以使用多接入功能。
若多接入指示信息中包含未授权指示信息, 则无论用户终端自身是否支持 多接入功能, 用户终端均确定不可以使用多接入功能。
上述介绍了在附着流程中用户终端获取多接入指示信息的方式, 下面介绍 在另外一种流程中用户终端获取多接入指示信息的方式:
二、 请求 PDN连接流程:
本实施例中在请求 PDN连接流程下获取多接入指示信息的步骤具体可以包 括:
( 1 )用户终端向接入节点发送 PDN连接建立请求;
当用户终端请求进行 PDN连接的建立时, 用户终端可以向接入节点发送 PDN连接建立请求。
本实施例中, 该 PDN连接建立请求中可以携带有该用户终端自身的用户终 端的多接入能力信息, 该用户终端的多接入能力信息用于指示该用户终端是否 支持多接入功能, 或者该 PDN连接建立请求中可以携带请求多接入指示信息的 指示, 该请求多接入指示信息的指示用于请求接入节点反馈多接入指示信息, 可以理解的是, 本实施例中的 PDN连接建立请求也可以不携带这些参数。
本实施例中, 具体的用户终端的多接入能力信息或指示可以携带在 PDN连 接建立请求的保留位中, 或者可以在 PDN连接建立请求中新扩展一个字段用于 携带用户终端的多接入能力信息或指示, 具体携带的方式此处不作限定。
( 2 )接入节点获取多接入指示信息;
本实施例中当接入节点接收到用户终端发送的 PDN连接建立请求之后, 可 以在建立 PDN连接的过程中从数据网关获取多接入指示信息。
若 PDN连接建立请求中携带有用户终端的多接入能力信息或请求多接入指 示信息的指示, 则在建立 PDN连接的过程中, 接入节点可以将该能力信息或请 求多接入指示信息的指示通过建立 PDN连接请求消息发送至数据网关, 以请求 数据网关反馈多接入指示信息, 本实施例中的建立 PDN连接请求消息可以为代 理绑定更新请求消息。
若 PDN连接建立请求中不携带用户终端的多接入能力信息或请求多接入指 示信息的指示, 则接入节点可以按照运营商预先配置的策略, 在接收到用户终 端发送的 PDN连接建立请求之后, 即请求数据网关反馈多接入指示信息。
需要说明的是, 若 PDN连接建立请求中携带的是用户终端的多接入能力信 息, 则接入节点或者数据网关还可以对该用户终端的多接入能力信息进行校验, 判断该用户终端是否支持多接入功能, 若确定用户终端不支持多接入功能, 则 可以不获取多接入指示信息, 若确定用户终端支持多接入功能, 则可以获取多 接入指示信息。
具体的校验可以分为接入节点校验以及数据网关校验:
当接入节点校验时, 接入节点根据用户终端的多接入能力信息判断用户终 端是否支持多接入功能, 若支持, 则在建立 PDN连接的过程中, 将用户终端的 多接入能力信息或接入节点自身生成的请求多接入指示信息的指示通过建立 PDN连接请求消息发送至数据网关以请求反馈多接入指示信息, 本实施例中的 建立 PDN连接请求消息可以为代理绑定更新请求消息;
当数据网关校验时, 接入节点在建立 PDN连接的过程中, 将用户终端的多 接入能力信息通过建立 PDN连接请求消息发送至数据网关, 数据网关根据用户 终端的多接入能力信息判断用户终端是否支持多接入功能, 若支持, 则根据数 据网关的多接入能力信息发送多接入指示信息, 将多接入指示信息携带于建立 PDN连接响应消息中发送至接入节点;
需要说明的是, 本实施例中, 数据网关在确定用户终端支持多接入功能时, 还可以判断自身是否支持多接入功能, 若自身也支持多接入功能, 则数据网关 向接入节点发送的建立 PDN连接响应消息中携带数据网关支持多接入功能指示 信息, 若自身不支持多接入功能, 则数据网关向接入节点发送的建立 PDN连接 响应消息中携带数据网关不支持多接入功能指示信息, 并根据该数据网关支持 多接入功能指示信息, 或数据网关不支持多接入功能指示信息发送多接入指示 信息, 本实施例中的建立 PDN连接响应消息可以为代理绑定更新确认消息。
可以理解的是, 对用户终端的多接入能力信息的校验过程并非是必要过程, 实际应用中, 可以不对用户终端的多接入能力信息进行校验而直接获取多接入 指示信息。
需要说明的是, 本实施例中, 接入节点还可以根据该用户终端在附着时获 取到的签约信息进行签约信息的校验, 若该签约信息中没有包含该用户终端是 否被授权多接入的信息, 或者是该签约信息指示该用户终端被授权多接入, 则 接入节点可以获取多接入指示信息, 若该签约信息指示该用户终端未被授权多 接入, 则接入节点可以不获取多接入指示信息, 并向用户终端反馈未授权指示 信息, 并根据该未授权指示信息发送多接入指示信息, 可以理解的是, 对用户 终端签约信息的校验过程并非是必要过程, 实际应用中, 可以不对用户终端签 约信息进行校验而直接获取多接入指示信息。
( 3 )接入节点向用户终端反馈多接入指示信息;
接入节点获取到多接入指示信息之后, 则可以向用户终端反馈该多接入指 示信息。
( 4 )用户终端接收接入节点发送的多接入指示信息;
接入节点向用户终端反馈多接入指示信息之后, 则用户终端可以接收到该 多接入指示信息。
( 5 ) 用户终端根据多接入指示信息判断用户终端是否可以使用多接入功 能, 若是, 则允许发起多网接入连接建立请求, 若否, 则禁止发起多网接入连 接建立请求。
用户终端在从网络侧设备获取到多接入指示信息之后, 则可根据该多接入 指示信息判断当前网络侧是否支持多接入功能, 需要说明的是, 用户终端还可 以进一步判断自身是否支持多接入功能, 若网络侧支持多接入功能, 且用户终 端也支持多接入功能, 则确定可以使用多接入功能, 若网络侧不支持多接入功 能, 或用户终端不支持多接入功能, 则确定不能使用多接入功能;
可以理解的是, 用户终端也可以只判断网络侧是否支持多接入功能, 若支 持, 则确定可以使用多接入功能, 若不支持, 则确定不能使用多接入功能。
若用户终端确认可以使用多接入功能, 则允许发起多网接入连接建立请求, 即当用户请求进行多网接入时, 用户终端向对应的目标网络发送接入连接建立 请求, 或者是当网络环境发生变化, 需要进行多网接入时, 用户终端向对应的 目标网络发送接入连接建立请求。
若用户终端确认不能使用多接入功能, 则禁止发起多网接入连接建立请求, 即当用户请求进行多网接入或网络环境发生变化, 需要进行多网接入时, 用户 终端会拒绝向对应的目标网络发送接入连接建立请求。
上面描述了在请求 PDN连接流程中用户终端从接入节点获取多接入指示信 息的流程, 在具体的网络中, 接入节点以及数据网关所指代的网元可能有所不 同, 在 3GPP网络中, 接入节点可以为 MME, 数据网关可以为 PGW, 下面以 3GPP网络为例进行详细说明, 具体请参阅图 4, 本发明实施例中多网接入控制 方法另一实施例包括:
400、 用户终端附着到 3GPP网络之后, 与 PGW1建立 PDN连接;
401、 用户终端向 MME发送 PDN连接请求( PDN Connectivity Request )消 本实施例中, 该 PDN连接请求中可以包含用户终端的多接入能力信息或者 请求多接入指示信息的指示。
402、 MME向 SGW发送建立缺省承载请求( Create Default Bearer Request 消息);
本实施例中,步骤 402中 MME所执行的操作与图 2所示的实施例中的步骤 208所执行的操作一致, 此处不再赘述。
403、 当 SGW与 PGW2之间使用 GTP进行信令交互时, SGW向 PGW2发 送建立缺省承载请求消息( Create Default Bearer Request ); 当 SGW与 PGW2之 间使用 PMIP进行信令交互时, SGW向 PGW2发送代理绑定更新消息 (Proxy Binding Update );
本实施例中, PGW2为用户终端新选择的, 请求建立 PDN连接的 PGW。
SGW通过建立缺省承载请求消息或代理绑定更新消息向 PGW2转发收到的 用户终端的多接入能力信息或者请求多接入指示信息的指示。
本实施例中, 若 SGW接收到的是请求多接入指示信息的指示, 则 SGW可 以直接通过建立缺省承载请求消息或代理绑定更新消息向 PGW2转发请求多接 入指示信息的指示。
本实施例中, 若 SGW接收到的是用户终端的多接入能力信息, 则 SGW同 样可以校验该用户终端是否支持多接入功能, 并且可以当用户终端支持多接入 功能时, 将用户终端的多接入能力信息通过建立缺省承载请求消息或代理绑定 更新消息发送至 PGW20
需要说明的是, 上述对用户终端的多接入能力的校验并非必选的过程, 在 实际应用中, SGW同样可以不进行校验, 而直接将用户终端的多接入能力信息 通过建立缺省承载请求消息或代理绑定更新消息发送给 PGW2。
404、 IP-CAN会话建立或者修改;
405、当 SGW与 PGW2之间使用 GTP协议进行信令交互时, PGW2向 SGW 发送建立缺省承载响应消息( Create Default Bearer Response ); 当 SGW与 PGW2 之间使用 PMIP协议进行信令交互时, PGW2向 SGW发送代理绑定确认消息
( Proxy Binding Ack );
若 PGW2从 SGW收到的是用户终端的多接入能力信息, 则 PGW2可以根 据收到的用户终端的多接入能力信息校验用户终端是否支持多接入功能, 若确 定用户终端支持多接入功能, 则 PGW2则通过建立缺省承载响应消息或代理绑 定确认消息向 SGW发送 PGW的多接入能力信息, 并根据该 PGW的多接入能 力信息发送多接入指示信息, 若确定用户终端不支持多接入功能, 则 PGW2发 送的建立缺省承载响应消息或代理绑定确认消息中可以不包含 PGW2的多接入 能力信息。
若 PGW2从 SGW收到的是请求多接入指示信息的指示时, 则 PGW2可以 直接通过建立缺省承载响应消息或代理绑定确认消息向 SGW发送 PGW2的多 接入能力信息, 并根据该 PGW的多接入能力信息发送多接入指示信息。
需要说明的是, 上述对用户终端的多接入能力的校验并非必选的过程, 在 实际应用中, PGW2 同样可以不进行校验, 而直接通过建立缺省承载响应消息 或代理绑定确认消息向 SGW发送 PGW2的多接入能力信息。
本实施例中, PGW2 可以通过建立缺省承载响应消息或代理绑定确认消息 向 SGW发送 PGW2的多接入能力信息, 同样的, PGW2也可以先判断自身是否 支持多接入功能, 若支持, 则在建立缺省承载响应消息或代理绑定确认消息中 携带 PGW支持多接入功能指示信息, 若不支持, 则在建立缺省承载响应消息或 代理绑定确认消息中携带 PGW不支持多接入功能指示信息, 并根据该 PGW支 持多接入功能指示信息或 PGW不支持多接入功能指示信息发送多接入指示信
406、 SGW向 MME发送建立缺省承载响应消息;
如果 SGW收到 PGW2发送的多接入指示信息, 则 SGW向 MME转发该多 接入指示信息。
407、 MME向 E-UTRAN发送 PDN连接接受( PDN Connectivity Accept ) 消息;
若 MME从 SGW收到多接入指示信息, 则 MME可以通过附着接受消息向 E-UTRAN发送多接入指示信息。
需要说明的是,若 MME在之前进行了签约信息的校验,且用户终端未被授 权多接入, 则本步骤中, MME可以向 E-UTRAN发送未授权指示信息, 并根据 该未授权指示信息发送多接入指示信息, 用于指示用户终端未被授权多接入。
若该多接入指示信息包含 PGW2的多接入能力信息, 则 MME也可以先根 据收到的 PGW2 的多接入能力信息确定 PGW2是否支持多接入功能, 若确定 PGW2支持多接入功能, 则 MME向 E-UTRAN发送 PGW支持多接入功能指示 信息; 若确定 PGW2不支持多接入功能, 则 MME向 E-UTRAN发送 PGW不支 持多接入功能指示信息, 并根据该 PGW支持多接入功能指示信息或 PGW不支 持多接入功能指示信息发送多接入指示信息。
可以理解的是, 若该多接入指示信息包括 PGW2的多接入能力信息, MME 也可以直接将该多接入指示信息发送给 E-UTRAN。
若该多接入指示信息中包含 PGW支持多接入功能指示信息或 PGW不支持 多接入功能指示信息, 则 MME可以直接向 E-UTRAN发送该多接入指示信息。
408、 E-UTRAN 向用户终端发送 RRC 连接重配置 ( RRC Connection Reconfiguration ) 消息;
若 E-UTRAN收到 MME发送的多接入指示信息(可以为 PGW的多接入能 力信息, 或 PGW支持多接入功能指示信息, 或 PGW不支持多接入功能指示信 息, 或未授权指示信息), 则 E-UTRAN将收到的该多接入指示信息通过 RRC 连接重配置消息发送给用户终端。
409、 用户终端向 E-UTRAN 发送 RRC 连接重配置 ( RRC Connection Reconfiguration Complete ) 消息;
410、 E-UTRAN向 MME发送 PDN连接完成( PDN Connectivity Complete ) 消息;
411、 MME向 SGW发送更新承载请求( Update Bearer Request ) 消息;
412、 SGW与 PGW2之间更新承载;
413、 SGW向 MME发送更新 载响应 ( Update Bearer Response ) 消息;
414、 MME向 HSS发送通知请求( Notify Request ) 消息;
415、 HSS向 MME发送通知响应消息( Notify Response ) 消息。
本实施例中, 用户终端收到多接入指示信息之后, 即可以根据多接入指示 信息确定用户终端是否可以使用多接入功能, 若可以使用, 则用户终端允许发 起多网接入连接建立请求, 若不能使用, 则禁止发起多网接入连接建立请求。 具体的确定方式可以为:
若多接入指示信息中包含 PGW2的多接入能力信息, 该 PGW2的多接入能 力信息指示 PGW2支持多接入功能, 且用户终端自身也支持多接入功能时, 用 户终端确定可以使用多接入功能, 若该 PGW2的多接入能力信息指示 PGW2不 支持多接入功能, 或用户终端自身不支持多接入功能时, 用户终端确定不可以 使用多接入功能;
若多接入指示信息中包含 PGW支持多接入功能指示信息,且用户终端自身 也支持多接入功能时, 用户终端确定可以使用多接入功能, 若多接入指示信息 中包含 PGW 不支持多接入功能指示信息, 或用户终端自身不支持多接入功能 时, 用户终端确定不可以使用多接入功能。
若多接入指示信息中包含未授权指示信息, 则无论用户终端自身是否支持 多接入功能, 用户终端均确定不可以使用多接入功能。
本实施例中的 MME可以看作是接入节点,该接入节点随着不同的应用网络 可能会有所不同,本实施例的 3GPP网络中仅以 MME视为接入节点为例进行说 明,可以理解的是,在实际应用中,该接入节点可以是其他的网元,例如为 SGSN, 具体的接入节点还可以是其他网元, 本实施例中的数据网关为 PGW, 在实际应 用中还可以为 GGSN, 或移动锚点, 或其他类型的网元, 此处不作限定。
需要说明的是, MME在为用户终端选择 PGW时, 有可能选择与当前用户 终端已经接入的 PGW相同的 PGW,即 PGW2与 PGW1为同一个 PGW,则 MME 可以将之前获取到的 PGW1的多接入指示信息发送给用户终端。
上述实施例中是以 3GPP网络内的 PDN连接请求流程为例进行说明的, 可 以理解的是, 在实际应用中, 用户终端同样可以通过非 3GPP网络内的 PDN连 接请求流程获取多接入指示信息, 在非 3GPP网络中, 接入节点可以为 MAG, 数据网关可以为 PGW, 具体请参阅图 5, 本发明实施例中多网接入控制方法另 一实施例包括: 501、 触发新的 PDN连接 ( Trigger new PDN Connectivity )请求; 本实施例中,用户终端通过 MAG与 PGW1建立有 PIMP隧道之后,若还需 要向 PGW2建立新的 PDN连接, 则可以发送 PDN连接请求, 该请求中可以携 带用户终端的多接入能力信息, 或者请求多接入指示信息的指示, 该 PDN连接 请求可以增加一个字段, 用于携带用户终端的多接入能力信息, 或者请求多接 入指示信息的指示,或者其他形式的指示信息,用于指示 MAG反馈多接入指示 信息。
本实施例中的 MAG为接入节点中的一种, 具体可以为非 3GPP网络 IP接 入网关, 或者是 EPDG。
若 MAG获得的用户终端的签约信息中没有用户终端是否被授权多接入的 信息, 或者是签约信息指示用户终端被授权多接入, 则 MAG在向 PGW2发送 消息时可以携带有 MAG获取到的用户终端的多接入能力信息或者请求多接入 指示信息的指示。
若 MAG 获得的用户终端的签约信息指示用户终端未被授权多接入, 则 MAG在发给 PGW2 的消息中可以不携带指示信息, 而只是按照普通的流程处 理。
本实施例中, 若 MAG获取到的是请求多接入指示信息的指示, 则 MAG可 以直接将携带该请求多接入指示信息的指示的消息发给 PGW2,若 MAG获取到 的是用户终端的多接入能力信息,则 MAG还可以根据该用户终端的多接入能力 信息判断该用户终端是否支持多接入功能, 并且可以在用户终端支持多接入功 能的情况下才向 PGW2发送携带该用户终端的多接入能力信息的消息。
上述提到的用户终端签约信息的校验和用户终端的多接入能力的校验在实 际应用中也可以结合进行, 例如当签约信息指示用户被授权多接入, 且用户终 端支持多接入功能时, MAG才将用户终端的多接入能力信息发送至 PGW2。
需要说明的是, 上述对用户终端签约信息的校验和对用户终端的多接入能 力的校验并非必选的过程, 在实际应用中, MAG同样可以不进行校验, 而直接 将用户终端的多接入能力信息或者请求多接入指示信息的指示发送给 PGW2。
502、 网关控制会话建立流程;
503、 MAG向 PGW2发送代理绑定更新 ( Proxy Binding Update ) 消息; 该消息中携带有用户终端的多接入能力信息或者请求多接入指示信息的指 示。
504、 PGW2发起与 PCRF的 IP-Can Session建立流程;
505、 PGW2向 AAA/HSS更新用户的 PDN连接的 PGW标识信息和 APN 信息;
506、 PGW2向 MAG发送代理绑定确认 ( Proxy Binding Ack ) 消息; 若 PGW2从 MAG收到的是用户终端的多接入能力信息, 则 PGW2可以根 据收到的用户终端的多接入能力信息校验用户终端是否支持多接入功能, 若确 定用户终端支持多接入功能, 则 PGW2则通过代理绑定确认消息向 MAG发送 PGW2的多接入能力信息,并根据该 PGW的多接入能力信息发送多接入指示信 息, 若确定用户终端不支持多接入功能, 则 PGW2发送的代理绑定确认消息中 可以不包含 PGW2的多接入能力信息。
若 PGW2从 MAG收到的是请求多接入指示信息的指示时, 则 PGW2可以 直接通过代理绑定确认消息向 MAG发送 PGW2的多接入能力信息, 并根据该 PGW的多接入能力信息发送多接入指示信息。
需要说明的是, 上述对用户终端的多接入能力的校验并非必选的过程, 在 实际应用中, PGW2同样可以不进行校验,而直接通过代理绑定确认消息向 MAG 发送 PGW2的多接入能力信息。
本实施例中, PGW2可以通过代理绑定确认消息向 MAG发送 PGW2的多 接入能力信息, 同样的, PGW2 也可以先判断自身是否支持多接入功能, 若支 持, 则在代理绑定确认消息中携带 PGW支持多接入功能指示信息, 若不支持, 则在建立缺省承载响应消息或代理绑定确认消息中携带 PGW 不支持多接入功 能指示信息, 并根据该 PGW支持多接入功能指示信息或 PGW不支持多接入功 能指示信息发送多接入指示信息。
507、 PGW2与 MAG之间的新 PMIP隧道建立。
508、 PCRF可能发起的网关控制的^舌修改流程更新 MAG中的 QoS信息; 509、 MAG向用户终端发送回复 Reply消息;
若 MAG从 PGW2收到了多接入指示信息,则 MAG可以通过回复消息向用 户终端发送多接入指示信息。
需要说明的是,若 MAG在之前进行了签约信息的校验,且用户终端未被授 权多接入, 则本步骤中, MAG可以用户终端发送未授权指示信息, 并根据该未 授权指示信息发送多接入指示信息, 用于指示用户终端未被授权多接入。
若该多接入指示信息包含 PGW2的多接入能力信息, 则 MAG也可以先根 据收到的 PGW2 的多接入能力信息确定 PGW2是否支持多接入功能, 若确定 PGW2支持多接入功能, 则 MAG向用户终端发送 PGW支持多接入功能指示信 息; 若确定 PGW2不支持多接入功能, 则 MAG向用户终端发送 PGW不支持多 接入功能指示信息, 并根据该 PGW支持多接入功能指示信息或 PGW不支持多 接入功能指示信息发送多接入指示信息。
可以理解的是, 若该多接入指示信息包括 PGW2的多接入能力信息, MME 也可以直接将该多接入指示信息发送给 E-UTRAN。
若该多接入指示信息中包含 PGW支持多接入功能指示信息或 PGW不支持 多接入功能指示信息, 则 MME可以直接向 E-UTRAN发送该多接入指示信息。
本实施例中, 用户终端收到多接入指示信息之后, 即可以根据多接入指示 信息确定用户终端是否可以使用多接入功能, 若可以使用, 则用户终端允许发 起多网接入连接建立请求, 若不能使用, 则禁止发起多网接入连接建立请求。
具体的确定方式可以为:
若多接入指示信息中包含 PGW2的多接入能力信息, 该 PGW2的多接入能 力信息指示 PGW2支持多接入功能, 且用户终端自身也支持多接入功能时, 用 户终端确定可以使用多接入功能, 若该 PGW2的多接入能力信息指示 PGW2不 支持多接入功能, 或用户终端自身不支持多接入功能时, 用户终端确定不可以 使用多接入功能;
若多接入指示信息中包含 PGW支持多接入功能指示信息,且用户终端自身 也支持多接入功能时, 用户终端确定可以使用多接入功能, 若多接入指示信息 中包含 PGW 不支持多接入功能指示信息, 或用户终端自身不支持多接入功能 时, 用户终端确定不可以使用多接入功能。
若多接入指示信息中包含未授权指示信息, 则无论用户终端自身是否支持 多接入功能, 用户终端均确定不可以使用多接入功能。
需要说明的是, MME在为用户终端选择 PGW时, 有可能选择与当前用户 终端已经接入的 PGW相同的 PGW,即 PGW2与 PGW1为同一个 PGW,则 MME 可以将之前获取到的 PGW1的多接入指示信息发送给用户终端。
本实施例中, 本实施例中, 用户终端可以通过向 MAG发送 PDN连接请求 以获得多接入指示信息, 且当用户终端可以使用多接入功能时, 用户终端才会 发起多网接入连接建立请求, 所以当用户终端使用多接入功能, 使得 PDN连接 中部分业务切换到 3GPP网络之后,没有切换到 3GPP网络的其他业务也能够同 时保持正常通信, 从而保证正常的网络通信不被中断。
三、 动态主机配置十办议 ( DHCP, Dynamic Host Configuration Protocol )请 求流程:
本实施例中在请求流程下获取多接入指示信息的步骤具体可以包括: ( 1 )用户终端向网络侧设备发送请求消息;
本实施例中, 当用户终端请求进行地址分配, 或鉴权, 或动态主机配置协 议 ( DHCP, Dynamic Host Configuration Protocol )发现时, 用户终端会向对应 的网络侧设备发送对应的请求消息, 以请求网络侧设备反馈多接入指示信息。
( 2 ) 网络侧设备通过响应消息向用户终端反馈自身保存的多接入指示信 本实施例中, 网络侧设备内预置有网络侧能力信息, 当网络侧设备接收到 用户终端发送的请求消息之后, 在反馈给用户终端的响应消息中可以携带该预 置的网络侧能力信息, 或者网络侧设备可以先对该网络侧能力信息进行判断, 直接根据网络侧支持多接入功能, 或网络侧不支持多接入功能发送多接入指示 信息。
上面描述了在请求过程中用户终端从网络侧设备获取多接入指示信息的流 程, 为便于理解, 下面以 DHCP发现过程为例进行说明, 请参阅图 6, 本发明实 施例中多网接入控制方法另一实施例包括:
601、 用户终端向网络广播 DHCP发现信息(DHCP Discovery );
本实施例中, 当用户终端接入网络之后, 若该网络中支持 DHCP, 则用户终 端可以向网络中各网元广播 DHCP发现信息, 用于探测 DHCP服务器, 以请求 DHCP服务器分配相应的地址。
在该 DHCP发现信息中可以携带有请求多接入指示信息的指示或者是用户 终端的多接入能力信息, 用于指示 DHCP服务器反馈多接入指示信息, 本实施 例中的多接入指示信息可以包括网络侧的能力信息, 或者直接指示网络侧是否 支持多接入功能的信息,本实施例中以 PGW的多接入能力信息视为网络侧能力 信息的例子进行说明, 可以理解的是, 在实际应用中, 若由其他的网元为用户 终端提供数据服务, 也可以获取这些网元的能力信息视为网络侧能力信息, 具 体网元的类型此处不作限定。
需要说明的是, 本实施例中, 在 DHCP发现信息中也可以不携带请求网络 的多接入能力信息指示或者是用户终端的多接入能力信息, DHCP服务器根据运 营商的策略确定接收到该 DHCP发现信息之后即向用户终端反馈多接入指示信
602、 DHCP服务器收到 DHCP发现信息后, DHCP向用户终端发送 DHCP 提供信息 (DHCP Offer );
DHCP服务器接收到 DHCP发现信息后, 根据其中的请求多接入指示信息 的指示或者是用户终端的多接入能力信息确定需要反馈多接入指示信息, 则在 本地预置的数据库中查询 PGW的多接入能力信息,并通过 DHCP提供信息根据 PGW的多接入能力信息发送多接入指示信息至用户终端。
若 DHCP服务器接收到的 DHCP发现信息中没有携带请求多接入指示信息 的指示或者是用户终端的多接入能力信息, 则 DHCP服务器也可以根据运营商 策略查询 PGW的多接入能力信息, 并通过 DHCP提供信息 ^居 PGW的多接入 能力信息发送多接入指示信息至用户终端。
需要说明的是, 若 DHCP发现信息中携带用户终端的多接入能力信息, 则 DHCP服务器还可以先判断用户终端是否支持多接入功能,并在用户终端支持多 接入功能时查询 PGW的多接入能力信息, 并通过 DHCP提供信息将 PGW的多 接入能力信息多接入指示信息反馈至用户终端。
可以理解的是, DHCP服务器也可以不对用户终端的多接入能力信息进行校 验, 而直接查询 PGW的多接入能力信息, 并通过 DHCP提供信息将 PGW的多 接入能力信息多接入指示信息反馈至用户终端。
本实施例中, DHCP服务器还可以先对 PGW的多接入能力信息进行判断以 确定 PGW是否支持多接入功能, 若支持, 则向用户终端反馈 PGW支持多接入 功能指示信息,若不支持,则向用户终端反馈 PGW不支持多接入功能指示信息, 并根据该 PGW支持多接入功能指示信息或 PGW不支持多接入功能指示信息发 送多接入指示信息。
603、 用户终端向网络广播 DHCP请求信息(DHCP Request );
604、 DHCP服务器向用户终端发送 DHCP确认信息(DHCPACK )。
本实施例中, 用户终端是通过步骤 601向 DHCP服务器请求多接入指示信 息, DHCP服务器是通过步骤 602向用户终端发送多接入指示信息,在实际应用 中,用户终端也可以通过步骤 603向 DHCP服务器请求多接入指示信息, DHCP 服务器也可以通过步骤 604向用户终端发送多接入指示信息。
本实施例中, 用户终端收到多接入指示信息之后, 即可以根据多接入指示 信息确定用户终端是否可以使用多接入功能, 若可以使用, 则用户终端允许发 起多网接入连接建立请求, 若不能使用, 则禁止发起多网接入连接建立请求。 具体的确定方式可以为:
若多接入指示信息中包含 PGW的多接入能力信息, 该 PGW的多接入能力 信息指示 PGW支持多接入功能, 且用户终端自身也支持多接入功能时, 用户终 端确定可以使用多接入功能, 若该 PGW的多接入能力信息指示 PGW不支持多 接入功能, 或用户终端自身不支持多接入功能时, 用户终端确定不可以使用多 接入功能;
若多接入指示信息中包含 PGW支持多接入功能指示信息,且用户终端自身 也支持多接入功能时, 用户终端确定可以使用多接入功能, 若多接入指示信息 中包含 PGW 不支持多接入功能指示信息, 或用户终端自身不支持多接入功能 时, 用户终端确定不可以使用多接入功能。
本实施例中, 用户终端可以通过向 DHCP服务器发送 DHCP发现信息以请 求 DHCP服务器反馈多接入指示信息, DHCP服务器收到该 DHCP发现信息后, 可以在本地预置的数据库中查询多接入指示信息, 并通过 DHCP提供信息将多 接入指示信息反馈至用户终端, 因此用户终端可以获取到多接入指示信息, 并 能通过该多接入指示信息判断用户终端是否可以使用多接入功能, 当判断用户 终端可以使用多接入功能时, 用户终端才会发起多网接入连接建立请求, 所以 当用户终端使用多接入功能,使得 PDN连接中部分业务切换到 3GPP网络之后, 没有切换到 3GPP网络的其他业务也能够同时保持正常通信,从而保证正常的网 络通信不被中断。
上述各实施例中描述了网络侧设备向用户终端下发多接入指示信息的过 程, 通过该多接入指示信息即可避免使用多接入时正常的网络通信被中断, 除 上述的方式之外, 本发明实施例还提供另外一种多网接入控制方法, 同样能够 避免使用多接入时正常的网络通信被中断, 具体请参阅图 7, 本发明实施例中多 网接入控制方法另一实施例包括:
701、 网络侧设备接收用户终端发送的请求消息; 本实施例中, 在某些流程中, 例如附着流程, 鉴权流程等, 网络侧设备会 从用户终端接收到请求消息, 该请求消息中可以携带有用户终端的多接入能力 信息或指示信息, 该用户终端的多接入能力信息或指示信息用于表示该用户终 端可能会发起多网接入连接建立请求。
可以理解的是, 本实施例中的请求消息中同样可以不携带用户终端的多接 入能力信息或指示信息, 而网络侧设备可以根据运营商策略确定接收到该请求 消息时即表示该用户终端可能会发起多网接入连接建立请求。
702、 网络侧设备获取各数据网关的多接入能力信息;
当网络侧设备接收到用户终端的请求消息之后, 可以获取当前网络中各数 据网关的多接入能力信息视为网络的能力信息。
703、 网络侧设备根据各数据网关的多接入能力信息选择支持多接入功能的 数据网关为用户终端提供服务。
当网络侧设备获取到当前网络中各数据网关的多接入能力信息之后, 即可 选取支持多接入功能的数据网关为用户终端提供服务。
本实施例中, 网络侧设备在接收到用户终端的请求之后, 会从当前各数据 网关中选取能够支持多接入功能的数据网关为该用户终端提供服务, 从而可以 使得为用户终端提供服务的数据网关能够支持多接入功能, 所以当用户终端使 用多接入功能, 使得 PDN连接中部分业务切换到 3GPP网络之后, 没有切换到 3GPP网络的其他业务也能够同时保持正常通信, 从而保证正常的网络通信不被 中断。
为便于理解, 下面以附着请求流程对本实施例中的多网接入控制方法进行 描述, 在附着请求流程中具体的多网接入控制方法可以包括如下步骤:
( 1 )用户终端向接入节点发送附着请求;
当用户终端进入某一网络的覆盖范围时, 首先会向该网络的接入节点请求 进行附着, 则用户终端可以向接入节点发送附着请求。
本实施例中, 该附着请求中可以携带有该用户终端自身的用户终端的多接 入能力信息, 该用户终端的多接入能力信息用于指示该用户终端是否支持多接 入功能, 或者该附着请求中可以携带指示信息, 该指示信息用于指示接入节点 反馈网络侧能力信息, 可以理解的是, 本实施例中的附着请求也可以不携带这 些参数。
本实施例中, 具体的用户终端的多接入能力信息或指示信息可以携带在附 着请求的保留位中, 或者可以在附着请求中新扩展一个字段用于携带用户终端 的多接入能力信息或指示信息, 具体携带的方式此处不作限定。
( 2 )接入节点获取当前网络中各数据网关的多接入能力信息;
当接入节点接收到用户终端发送的附着请求之后, 会查询自身静态配置的 数据网关的多接入能力信息,或者通过域名服务器(DNS, Domain Name Server ) 解析的方式获取当前网络中各数据网关的多接入能力信息。
可以理解的是, 接入节点同样还可以通过其他方式获取当前网络中各数据 网关的多接入能力信息, 具体方式此处不作限定。
需要说明的是, 本实施例中, 接入节点在获取当前网络中各数据网关的多 接入能力信息之前还可以对用户终端进行签约信息校验, 或用户终端的多接入 能力信息校验, 具体的校验方式与前述实施例中描述的校验方式类似, 此处不 再赘述。
( 3 )接入节点选择支持多接入功能的数据网关为该用户终端提供服务。 当接入节点获取到当前网络中各数据网关的多接入能力信息之后, 即可从 这些数据网关中选择支持多接入功能的数据网关为该用户终端提供服务, 需要 说明的是, 若接入节点未选择到支持多接入功能的数据网关, 则会向用户终端 发送选择失败信息, 用于指示未选择到支持多接入功能的数据网关, 即不允许 用户终端使用多接入功能。
本实施例中, 具体未选择支持多接入功能的数据网关的原因可以是当前网 络中的各数据网关均不支持多接入功能, 或者是当前网络中支持多接入功能的 数据网关负荷超过预置门限等。 用户终端若从接入节点接收到选择失败信息, 则表示接入节点未选择到支 持多接入功能的数据网关, 则用户终端禁止发起多网接入连接建立请求, 若用 户终端未从接入节点接收到选择失败信息, 则可默认表示接入节点已经选择到 支持多接入功能的数据网关, 则用户终端允许发起多网接入连接建立请求。
上面描述了在附着过程中接入节点选择数据网关的流程, 在具体的网络中, 接入节点以及数据网关所指代的网元可能有所不同,在 3GPP网络中,接入节点 可以为 MME, 数据网关可以为 PGW, 下面以 3GPP网络为例进行详细说明, 具体请参阅图 8, 本发明实施例中多网接入控制方法另一实施例包括:
801、 用户终端向接入网络的 MME发起附着请求( Attach Request );
当用户终端进入某一网络的覆盖范围时,首先会向该网络的 MME请求进行 附着, 则会向 MME发送附着请求。
本实施例中, 该附着请求中可以携带有该用户终端自身的多接入能力信息, 该用户终端的多接入能力信息用于指示该用户终端是否支持多接入功能, 或者 该附着请求中可以携带指示信息, 该指示信息用于表示该用户终端可能会发起 多网接入连接建立请求。
本实施例中, 具体的用户终端的多接入能力信息或指示信息可以携带在附 着请求的保留位中, 或者可以在附着请求中新扩展一个字段用于携带用户终端 的多接入能力信息或指示信息, 具体携带的方式此处不作限定。
802、 MME向用户终端发送身份认证请求( Identity Request );
803、 用户终端向 MME发送身份认证响应 ( Identity Response );
804、 MME通过 HSS与用户终端之间互相进行鉴权 ( Authentication ); 805、 MME通过 EIR对用户终端的设备进行认证 ( IMEI Check );
上述步骤 802至 805为鉴权过程, 包括身份认证和设备认证。
需要说明的是,如果在实际应用中能够保证用户终端与 MME都是绝对安全 可靠的,或者是附着过程对安全性要求不高,则可以不执行上述步骤 802至 805。
806、 MME更新用户在 HSS中的位置信息 ( Update Location ); 807、 MME接收 HSS的位置更新确认消息( Update Location Ack ), 同时获 得用户终端的签约信息;
808、 MME管理网元选择 PGW;
若 MME在步骤 807中获得的签约信息中没有用户终端是否被授权多接入的 信息或者是该签约信息指示用户终端被授权多接入, 则 MME在选择 PGW时优 先选择支持多接入功能的 PGW。
若用户终端的附着请求消息携带有用户终端的多接入能力信息, 则 MME 还可以根据该用户终端的多接入能力信息判断用户终端是否支持多接入功能, 若支持, 则在选择 PGW时优先选择支持多接入功能的 PGW。
上述提到的用户终端签约信息的校验和用户终端的多接入能力的校验在实 际应用中也可以结合进行, 例如当签约信息指示用户被授权多接入, 且用户终 端支持多接入功能时, MME才在选择 PGW时优先选择支持多接入功能的 PGW。
本实施例中的 MME可以采用如下方式选择支持多接入功能的 PGW: 选择 MME静态配置的支持多接入功能的 PGW,或者先通过 DNS解析方式获取 PGW 支持的服^言息, 再从中优先选择支持多接入功能的 PGW。
809、 MME 向 SGW发送建立缺省承载请求消息 (Create Default Bearer Request );
本实施例中, MME发给 SGW的建立缺省承载请求消息中包含有选择到的 支持多接入功能的 PGW的地址。
810、 当 SGW与 PGW之间使用 GTP协议进行信令交互时, SGW向 PGW 发送建立缺省承载请求消息( Create Default Bearer Request ); 当 SGW与 PGW 之间使用 PMIP协议进行信令交互时, SGW向 PGW发送代理绑定更新消息
( Proxy Binding Update );
本实施例中, SGW从 MME接收到的建立缺省承载请求消息中包含有 MME 选择到的支持多接入功能的 PGW的地址, 因此 SGW可以 ^居该地址向对应的 PGW发送建立缺省承载请求消息或代理绑定更新消息。 811、 当 SGW与 PGW之间使用 GTP协议进行信令交互时, PGW向 SGW 发送建立缺省承载响应消息( Create Default Bearer Response ); 当 SGW与 PGW 之间使用 PMIP协议进行信令交互时, PGW向 SGW发送代理绑定确认消息
( Proxy Binding Ack );
812、 SGW 向 MME发送建立缺省承载响应消息 (Create Default Bearer Response );
813、 MME向 E-UTRAN发送附着接受消息( Attach Accept );
若 MME在步骤 808 中没有选择到支持多接入功能的 PGW, 则 MME向 E-UTRAN发送的附着接受消息包含选择失败信息,该选择失败信息用于指示未 选择到支持多接入功能的 PGW, 即不允许用户终端使用多接入功能, 具体原因 可以为当前网络中不存在支持多接入功能的 PGW, 或者是当前网络中支持多接 入功能的 PGW的负荷超过预置的门限, 或者是其他类型的失败原因, 此处不作 限定。
若 MME在步骤 808中判断签约信息指示用户终端未被授权多接入,则 MME 向 E-UTRAN发送的附着接受消息包含未授权指示信息,用于指示该用户终端未 被授权多接入。
814、 E-UTRAN向用户终端发送 RRC连接重配置消息( RRC Connection Reconfiguration );
若 E-UTRAN 收到 MME 发送的选择失败信息, 或未授权指示信息, E-UTRAN将收到的这些信息通过 RRC连接重配置消息发送给用户终端。
815、用户终端向 E-UTRAN发送 RRC连接重配置完成消息( RRC Connection Reconfiguration Complete );
816、 E-UTRAN向 MME发送附着完成消息( Attach Complete );
817、 MME向 SGW发送更新承载请求消息( Update Bearer Request );
818、 SGW向 MME发送更新 载响应消息( Update Bearer Response )。 本实施例中, 用户终端若没有收到网络发送的选择失败信息, 用户终端是 默认网络能够支持多接入功能。
若用户终端没有收到选择失败信息, 也没有收到未授权指示信息, 则支持 多接入功能的用户终端可以发起多个接入网的连接建立。
本实施例中的 MME可以看作是接入节点,该接入节点随着不同的应用网络 可能会有所不同,本实施例的 3GPP网络中仅以 MME视为接入节点为例进行说 明,可以理解的是,在实际应用中,该接入节点可以是其他的网元,例如为 SGSN, 具体的接入节点还可以是其他网元, 本实施例中的数据网关为 PGW, 在实际应 用中还可以为 GGSN, 或移动锚点, 或其他类型的网元, 此处不作限定。
本实施例中, MME在接收到用户终端的请求之后, 会从当前各 PGW中选 取能够支持多接入功能的 PGW为该用户终端提供服务,从而可以使得为用户终 端提供服务的 PGW能够支持多接入功能, 所以当用户终端使用多接入功能, 使 得 PDN连接中部分业务切换到 3GPP网络之后, 没有切换到 3GPP网络的其他 业务也能够同时保持正常通信, 从而保证正常的网络通信不被中断;
其次, 本实施例中, MME可以对用户终端的多接入能力信息进行判断, 从 而决定是否获取各 PGW 的能力信息, 所以当判断用户终端不支持多接入功能 时, 可以不获取各 PGW的能力信息, 因此能够减少 MME的操作, 减少网络负 荷;
再次, 本实施例中, MME可以对用户终端的签约信息进行校验, 当签约信 息指示用户终端未被授权多接入时, 可以不获取各 PGW的能力信息, 因此能够 进一步减少 MME的操作, 减少网络负荷。
上述实施例中是以 3GPP 网络内的附着流程为例进行说明的, 可以理解的 是,在实际应用中,接入节点同样可以通过非 3GPP网络内的附着流程选择数据 网关, 在非 3GPP网络中, 接入节点可以为 MAG, 数据网关可以为 PGW, 具体 请参阅图 9, 本发明实施例中多网接入控制方法另一实施例包括:
901、 用户终端与 MAG 执行非 3GPP 特定流程 ( Non-3 GPP specific procedures ); 本实施例中的 MAG为接入节点中的一种, 具体可以为非 3GPP网络 IP接 入网关, 或者是 EPDG。
902、 用户终端与 MAG通过 HSS或认证授权计费 (AAA, Authentication Authorization Accounting )月良务器进行认证 ( Authentication & Authorization ); 本实施例中, MAG可以通过 HSS或 AAA服务器获得用户终端的签约信息。
903、 用户终端向 MAG发起触发附着流程 ( L3 Attach Trigger ), 向 MAG发 送附着请求;
本实施例中, 该附着请求中可以携带用户终端的多接入能力信息, 也可以 不携带。
904、 MAG选择 PGW;
若 MAG在步骤 902中获得的签约信息中没有用户终端是否被授权多接入的 信息或者是该签约信息指示用户终端被授权多接入, 则 MAG在选择 PGW时优 先选择支持多接入功能的 PGW。
若用户终端的附着请求消息携带有用户终端的多接入能力信息,则 MAG还 可以根据该用户终端的多接入能力信息判断用户终端是否支持多接入功能, 若 支持, 则在选择 PGW时优先选择支持多接入功能的 PGW。
上述提到的用户终端签约信息的校验和用户终端的多接入能力的校验在实 际应用中也可以结合进行, 例如当签约信息指示用户被授权多接入, 且用户终 端支持多接入功能时, MAG才在选择 PGW时优先选择支持多接入功能的 PGW。
本实施例中的 MAG可以采用如下方式选择支持多接入功能的 PGW: 选择 MAG静态配置的支持多接入功能的 PGW,或者先通过 DNS解析方式获取 PGW 支持的服^言息, 再从中优先选择支持多接入功能的 PGW。
905、 网关控制会话建立流程 ( Gateway Control Session Establishment Procedure );
906、 MAG向 PGW发送代理绑定更新消息( Proxy Binding Update );
907、 PGW发起与归属策略控制计费规则功能实体( PCRF, Policy Control and Charging Rules Function ) 的 IP 连接接入网会话建立流程 (IP-Can Session Establishment Procedure );
908、 PGW向 HSS/AAA服务器更新用户的 PDN连接的 PGW标识信息和 APN信息 ( Update PGW Address );
909、 PGW向 MAG发送代理绑定确认消息( Proxy Binding Ack );
910、 PGW与 MAG之间的代理移动 IP隧道建立 ( PMIP Tunnel );
911、 归属 PCRF可能发起的网关控制的^舌修改流程更新 MAG中的 QoS 信息 ( Gateway Control and QoS Rules Provision Procedure );
912、 附着完成。
若 MAG在步骤 904中没有选择到支持多接入功能的 PGW, 则 MAG向用 户终端发送的附着完成消息可以包含选择失败信息, 该选择失败信息用于指示 未选择到支持多接入功能的 PGW, 即不允许用户终端使用多接入功能, 具体原 因可以为当前网络中不存在支持多接入功能的 PGW, 或者是当前网络中支持多 接入功能的 PGW的负荷超过预置的门限, 或者是其他类型的失败原因, 此处不 作限定。
若 MAG在步骤 904中判断签约信息指示用户终端未被授权多接入,则 MAG 向用户终端发送的附着完成消息可以包含未授权指示信息, 用于指示该用户终 端未被授权多接入。
本实施例中,用户终端若没有收到 MAG发送的选择失败信息,用户终端是 默认网络能够支持多接入功能。
若用户终端没有收到选择失败信息, 也没有收到未授权指示信息, 则支持 多接入功能的用户终端可以发起多个接入网的连接建立。
需要说明的是, 图 8与图 9所示的实施例中, 均以附着流程为例进行了说 明, 可以理解的是, MAG选择 PGW的方案同样可以在其他的流程中实现, 例 如 PDN连接建立请求流程, 具体流程此处不作限定。
本实施例中, MAG在接收到用户终端的请求之后, 会从当前各 PGW中选 取能够支持多接入功能的 PGW为该用户终端提供服务,从而可以使得为用户终 端提供服务的 PGW能够支持多接入功能, 所以当用户终端使用多接入功能, 使 得 PDN连接中部分业务切换到 3GPP网络之后, 没有切换到 3GPP网络的其他 业务也能够同时保持正常通信, 从而保证正常的网络通信不被中断;
其次, 本实施例中, MAG可以对用户终端的多接入能力信息进行判断, 从 而决定是否获取各 PGW 的能力信息, 所以当判断用户终端不支持多接入功能 时, 可以不获取各 PGW的能力信息, 因此能够减少 MAG的操作, 减少网络负 荷;
再次, 本实施例中, MAG可以对用户终端的签约信息进行校验, 当签约信 息指示用户终端未被授权多接入时, 可以不获取各 PGW的能力信息, 因此能够 进一步减少 MAG的操作, 减少网络负荷。
下面对本发明实施例中的通讯系统进行描述, 请参阅图 10, 本发明实施例 中的通讯系统一个实施例包括:
网络侧设备 1001, 用于获取多接入指示信息, 向用户终端 1003发送多接入 指示信息;
用户终端 1003, 用于接收网络侧设备 1001发送的多接入指示信息,根据多 接入指示信息判断用户终端 1003是否使用多接入功能, 在使用多接入功能时发 起多网接入连接建立请求;
本实施例中的通讯系统还可以进一步包括:
数据网关 1002, 用于向网络侧设备 1001提供多接入指示信息。
本实施例中的网络侧设备 1001可以为接入节点或者是 DHCP服务器。 需要说明的是,接入节点还用于接收用户终端 1003发送的附着请求或 PDN 连接建立请求, 获取用户终端 1003的签约信息,
当签约信息中不包含用户终端 1003是否被授权多接入的信息, 或者签约信 息指示用户终端 1003被授权多接入时, 接入节点获取多接入指示信息;
当签约信息指示用户终端 1003未被授权多接入, 则接入节点根据未授权指 示信息向用户终端 1003发送多接入指示信息。
本实施例中的附着请求或 PDN连接建立请求中包含用户终端的多接入能力 信息, 接入节点还用于根据用户终端的多接入能力信息判断用户终端 1003是否 支持多接入功能, 若支持, 则在建立 PDN连接的过程中, 将用户终端的多接入 能力信息或接入节点自身生成的请求多接入指示信息的指示通过建立 PDN连接 请求消息发送至数据网关 1002, 接收数据网关 1002发送的建立 PDN连接响应 消息, 该建立 PDN连接响应消息中携带有多接入指示信息。
本实施例中的数据网关 1002还用于接收接入节点发送的包含用户终端的多 接入能力信息的建立 PDN连接请求消息, 根据用户终端的多接入能力信息判断 用户终端是否支持多接入功能, 若支持, 则根据数据网关的多接入能力信息发 送多接入指示信息, 该多接入指示信息携带于建立 PDN连接响应消息中发送至 接入节点;
或者, 数据网关 1002还用于接收接入节点发送的包含用户终端的多接入能 力信息的建立 PDN连接请求消息, 根据用户终端的多接入能力信息判断用户终 端是否支持多接入功能, 若支持, 则继续判断数据网关 1002自身是否支持多接 入功能, 若自身也支持多接入功能, 则根据数据网关支持多接入功能指示信息 发送多接入指示信息, 该多接入指示信息携带于建立 PDN连接响应消息中发送 至接入节点, 若数据网关 1002自身不支持多接入功能, 则根据数据网关不支持 多接入功能指示信息发送多接入指示信息, 该多接入指示信息携带于建立 PDN 连接响应消息中发送至接入节点。
为便于理解, 下面以一具体实例对 3GPP网络中的通讯系统进行说明,请参 阅图 11, 本发明实施例中通讯系统另一实施例包括:
MME1101 , SGW1102, PGW1103以及用户终端 1104;
本实施例中的 MME1101以及 SGW1102可以构成接入节点, PGW1103可 以为数据网关。
MME1101 , 用于接收用户终端 1104发送的附着请求, 附着请求中携带用户 终端的多接入能力信息或请求多接入指示信息的指示, 用户终端的多接入能力 信息或请求多接入指示信息的指示用于请求 MME1101 反馈多接入指示信息, MME1101向 SGW1102转发用户终端的多接入能力信息或请求多接入指示信息 的指示, 接收 SGW1102反馈的多接入指示信息, 向用户终端 1104发送多接入 指示信息;
SGW1102, 用于接收 MME1101发送的用户终端的多接入能力信息或请求 多接入指示信息的指示,向 PGW1103转发用户终端的多接入能力信息或请求多 接入指示信息的指示, 接收 PGW1103反馈的多接入指示信息, 向 MME1101反 馈多接入指示信息;
PGW1103,用于接收 SGW1102发送的用户终端的多接入能力信息或请求多 接入指示信息的指示, 向 SGW1102反馈多接入指示信息;
本实施例中的多接入指示信息可以包括 PGW1103的多接入能力信息,或者 包括 PGW支持多接入功能指示, 或者包括 PGW不支持多接入功能指示。
用户终端 1104, 用于接收 MME1101发送的多接入指示信息, 根据多接入 指示信息判断是否使用多接入功能, 在使用多接入功能时发起多网接入连接建 立请求。
下面以一具体应用场景对本实施例中的通讯系统进行描述:
当用户终端 1104进入某一网络的覆盖范围时,首先会向该网络的 MME1101 请求进行附着, 则会向 MME1101发送附着请求。
本实施例中的附着请求可以包含用户终端 1104的多接入能力信息, 或者请 求多接入指示信息的指示, 该附着请求可以增加一个字段, 用于携带用户终端 1104 的多接入能力信息, 或者请求多接入指示信息的指示, 或者其他形式的指 示信息, 用于指示 MME1101反馈 PGW1103的多接入能力信息。
MME1101向 SGW1102发送建立缺省承载请求消息, 其中携带有用户终端 1104的多接入能力信息或者请求多接入指示信息的指示;
SGW1102向 PGW1103发送建立缺省承载请求消息或代理绑定更新消息, 其中携带有用户终端 1104的多接入能力信息或者请求多接入指示信息的指示; PGW1103向 SGW1102发送建立缺省承载响应消息或代理绑定确认消息, 其中携带有多接入指示信息;
本实施例中, 该多接入指示信息可以包括 PGW1103的多接入能力信息, 或 者包括 PGW支持多接入功能指示, 或者包括 PGW不支持多接入功能指示。
SGW1102向 MME1101发送建立缺省承载响应消息, 其中携带有多接入指 示信息;
MME 1101通过 E-UTRAN向用户终端 1104发送多接入指示信息;
MME1101还可以获取用户终端 1104的签约信息并进行校验, 若该签约信 息指示用户终端 1104未被授权多接入, 则 MME1101可以根据未授权指示信息 向用户终端 1104发送多接入指示信息。
本实施例中, 用户终端 1104收到多接入指示信息之后, 即可以根据多接入 指示信息确定用户终端是否可以使用多接入功能,若可以使用,则用户终端 1104 允许发起多网接入连接建立请求, 若不能使用, 则禁止发起多网接入连接建立 请求。
具体的确定方式可以为:
若多接入指示信息中包含 PGW的多接入能力信息, 该 PGW的多接入能力 信息指示 PGW支持多接入功能, 且用户终端 1104 自身也支持多接入功能时, 用户终端 1104确定可以使用多接入功能, 若该 PGW 的多接入能力信息指示 PGW不支持多接入功能, 或用户终端 1104 自身不支持多接入功能时, 用户终 端 1104确定不可以使用多接入功能;
若多接入指示信息中包含 PGW支持多接入功能指示信息,且用户终端 1104 自身也支持多接入功能时, 用户终端 1104确定可以使用多接入功能, 若多接入 指示信息中包含 PGW不支持多接入功能指示信息, 或用户终端 1104 自身不支 持多接入功能时, 用户终端 1104确定不可以使用多接入功能。
若多接入指示信息中包含未授权指示信息, 则无论用户终端 1104自身是否 支持多接入功能, 用户终端均确定不可以使用多接入功能。
本实施例中, 用户终端 1104 可以通过向 MME1101 发送附着请求以请求 MME 1101反馈多接入指示信息, MME 1101收到该附着请求后, 可以在建立缺 省承载过程中, 通过 SGW1102从 PGW1103获取到多接入指示信息, 所以能够 向用户终端 1104反馈多接入指示信息, 因此用户终端 1104可以获取到多接入 指示信息, 并能通过该多接入指示信息判断是否使用多接入功能, 当使用多接 入功能时,用户终端 1104才会发起多网接入连接建立请求,所以当用户终端 1104 的 PDN连接中部分业务切换到 3GPP网络之后, 没有切换到 3GPP网络的其他 业务也能够同时保持正常通信, 从而保证正常的网络通信不被中断。
本发明实施例中通讯系统的再一实施例同样请参阅图 10, 具体包括: 网络侧设备 1001, 用于接收用户终端 1003发送的请求消息, 获取各数据网 关 1002能力信息, 根据各数据网关 1002能力信息选择支持多接入功能的数据 网关 1002为用户终端 1003提供服务;
数据网关 1002, 用于向网络侧设备 1001提供数据网关的多接入能力信息; 用户终端 1003, 用于向网络侧设备 1001发送请求消息。
本实施例中的数据网关可以为 PGW;
本实施例中的网络侧设备 1001可以为接入节点。
需要说明的是,接入节点还用于接收用户终端 1003发送的附着请求或 PDN 连接建立请求, 获取用户终端 1003的签约信息,
当签约信息中不包含用户终端 1003是否被授权多接入的信息, 或者签约信 息指示用户终端 1003被授权多接入时, 接入节点获取网络侧能力信息;
当签约信息指示用户终端 1003 未被授权多接入, 则接入节点向用户终端 1003反馈未授权指示信息。
本实施例中的附着请求或 PDN连接建立请求中包含用户终端的多接入能力 信息, 接入节点还用于根据用户终端的多接入能力信息判断用户终端 1003是否 支持多接入功能, 若支持, 则获取各数据网关 1002能力信息。 本实施例中的网络侧设备 1001还用于当未选择到支持多接入功能的 PGW 时, 向用户终端 1003发送选择失败信息, 选择失败信息用于指示未选择到支持 多接入功能的 PGW, 即不允许用户终端使用多接入功能;
用户终端 1003还用于判断是否接收到网络侧设备 1001发送的选择失败信 息以及未授权指示信息, 若未接收到选择失败信息以及未授权指示信息, 则发 起多网接入连接建立请求。
本实施例中, 网络侧设备 1001在接收到用户终端 1003的请求之后, 会从 当前各数据网关 1002中选取能够支持多接入功能的数据网关 1002为该用户终 端 1003提供服务, 从而可以使得为用户终端 1003提供服务的数据网关 1002能 够支持多接入功能, 所以当用户终端 1003的 PDN连接中部分业务切换到 3GPP 网络之后, 没有切换到 3GPP网络的其他业务也能够同时保持正常通信,从而保 证正常的网络通信不被中断。
下面介绍本发明实施例中的网络侧设备实施例, 请参阅图 12, 本发明实施 例中的网络侧设备一个实施例包括:
获取单元 1202, 用于获取多接入指示信息;
发送单元 1203, 用于向用户终端发送多接入指示信息, 该多接入指示信息 用于指示所述用户终端是否允许使用多接入功能。
本实施例中的网络侧设备还可以进一步包括:
接收单元 1201, 用于接收用户终端发送的请求消息, 并触发获取单元 1202 执行相应操作。
需要说明的是, 本实施例中的网络侧设备同样可以不包含接收单元 1201, 则发送单元 1203在满足预置的条件时主动向用户终端发送多接入指示信息, 该 多接入指示信息用于指示所述用户终端是否允许使用多接入功能, 例如发送单 元 1203每隔一段时间即自动向用户终端广播当前的多接入指示信息, 或者是当 多接入指示信息发生变化时, 则发送单元 1203向用户终端广播当前的多接入指 示信息, 或者是满足其他的预置条件时, 发送单元 1203均可向用户终端广播当 前的多接入指示信息, 具体的条件此处不作限定。
为便于理解, 下面以一具体实例对上述的网络侧设备进行说明:
当用户终端进入某一网络的覆盖范围时, 首先会向该网络中的网络侧设备 发起附着请求进行附着,则接收单元 1201可以接收到用户终端发送的附着请求, 该附着请求中可以携带有该用户终端自身的用户终端的多接入能力信息, 该用 户终端的多接入能力信息用于指示该用户终端是否支持多接入功能, 或者该附 着请求中可以携带请求多接入指示信息的指示, 该指示用于请求反馈多接入指 示信息;
当接收单元 1201接收到用户终端发送的附着请求之后, 获取单元 1202会 在建立缺省承载的过程中, 将该能力信息或请求多接入指示信息的指示通过服 务网关发送至数据网关以请求获取多接入指示信息, 则数据网关会通过服务网 关向获取单元 1202返回多接入指示信息;
获取单元 1202获取到多接入指示信息之后, 则发送单元 1203可以将该多 接入指示信息发送至用户终端, 以便于用户终端进行多网接入控制。
需要说明的是, 本实施例中的网络侧设备还可以获取用户终端的签约信息, 对签约信息进行校验, 和 /或对用户终端的多接入能力信息进行校验, 具体的校 验以及处理过程与前述图 2以及图 3所示的实施例中的过程类似, 此处不再赘 述。
本实施例中, 接收单元 1201在接收到用户终端的请求消息之后, 获取单元 1202可以在建立缺省承载的过程中获取到多接入指示信息,则发送单元 1203可 以将该多接入指示信息发送至用户终端, 该多接入指示信息用于指示所述用户 终端是否允许使用多接入功能, 以便于用户终端进行多网接入控制, 从而可以 使得用户终端使用多接入功能, 使得 PDN连接中部分业务切换到 3GPP网络之 后, 没有切换到 3GPP网络的其他业务也能够同时保持正常通信,从而保证正常 的网络通信不被中断。
请参阅图 13, 本发明实施例中的网络侧设备另一实施例包括: 请求接收单元 1301, 用于接收用户终端发送的请求消息
信息获取单元 1302, 用于获取各数据网关的多接入能力信息;
选择单元 1303, 用于根据各数据网关的多接入能力信息选择支持多接入功 能的数据网关为用户终端提供服务。
本实施例中的网络侧设备还可以进一步包括:
签约信息校验单元 1304, 用于获取用户终端的签约信息, 若签约信息中不 包含用户终端是否被授权多接入的信息, 或者签约信息指示用户终端被授权多 接入, 则触发信息获取单元 1302执行相应操作。
本实施例中的网络侧设备还可以进一步包括:
指示发送单元 1305, 用于当用户终端的签约信息指示用户终端未被授权多 接入, 向用户终端发送未授权指示信息, 未授权指示信息用于指示用户终端未 被授权多接入, 当选择单元未选择到支持多接入功能的数据网关时, 向用户终 端发送选择失败信息, 选择失败信息用于指示未选择到支持多接入功能的数据 网关, 即不允许用户终端使用多接入功能。
具体原因可以为当前网络中不存在支持多接入功能的 PGW, 或者是当前网 络中支持多接入功能的 PGW的负荷超过预置的门限,或者是其他类型的失败原 因, 此处不作限定。
本实施例中, 请求接收单元 1301在接收到用户终端的请求之后, 选择单元 1303会从当前各数据网关中选取能够支持多接入功能的数据网关为该用户终端 提供服务, 从而可以使得为用户终端提供服务的数据网关能够支持多接入功能, 所以当用户终端使用多接入功能, 使得 PDN连接中部分业务切换到 3GPP网络 之后, 没有切换到 3GPP网络的其他业务也能够同时保持正常通信,从而保证正 常的网络通信不被中断。
下面介绍本发明实施例中的用户终端实施例, 请参阅图 14, 本发明实施例 中的用户终端一个实施例包括:
信息接收单元 1401, 用于接收网络侧设备发送的多接入指示信息; 信息校验单元 1402, 用于根据多接入指示信息判断是否使用多接入功能; 多网接入单元 1403,用于在使用多接入功能时发起多网接入连接建立请求。 本实施例中的用户终端还可以进一步包括:
请求发送单元 1404, 用于向网络侧设备发送请求消息, 请求消息中携带用 户终端的多接入能力信息或请求多接入指示信息的指示, 用户终端的多接入能 力信息或请求多接入指示信息的指示用于请求网络侧设备反馈多接入指示信 需要说明的是, 本实施例中, 若网络侧设备能够主动发送网络侧能力信息, 则本实施例中可以不需要请求发送单元 1404, 若网络侧设备需要用户终端首先 发起请求, 才会向用户终端反馈多接入指示信息, 则本实施例中需要请求发送 单元 1404。
本实施例中的用户终端各单元之间的通信关系以及数据流程与前述图 2或 图 3所示的实施例中的用户终端的操作类似, 此处不再赘述。
本实施例中,信息接收单元 1401可以从网络侧设备获取到多接入指示信息, 并且信息校验单元 1402能够通过该多接入指示信息判断是否使用多接入功能, 当使用多接入功能时, 多网接入单元 1403才会发起多网接入连接建立请求, 所 以当用户终端多接入功能, 使得 PDN连接中部分业务切换到 3GPP网络之后, 没有切换到 3GPP网络的其他业务也能够同时保持正常通信,从而保证正常的网 络通信不被中断。
请参阅图 15, 本发明实施例中的用户终端另一实施例包括:
指示信息判断单元 1501, 用于判断用户终端是否接收到网络侧设备发送的 未授权指示信息或选择失败信息, 未授权指示信息用于指示用户终端未被授权 多接入, 选择失败信息用于指示未选择到支持多接入功能的数据网关, 即不允 许用户终端使用多接入功能;
多网接入单元 1502, 用于当未接收到未授权指示信息以及选择失败信息时 发起多网接入连接建立请求。 为便于理解, 下面以一具体实例对本实施例中的用户终端进行说明: 当用户终端进入某一网络的覆盖范围时, 首先会向该网络的接入节点请求 进行附着, 则会向接入节点发送附着请求。
当接入节点接收到用户终端发送的附着请求之后, 可以获取到该用户终端 的签约信息, 若签约信息指示用户终端未被授权多接入, 则接入节点向用户终 端发送未授权指示信息, 用于指示该用户终端未被授权多接入;
若签约信息中没有包含指示用户终端是否被授权多接入的信息, 或者是若 签约信息指示用户终端被授权多接入, 则接入节点会获取各数据网关的多接入 能力信息, 具体可以是: 查询自身静态配置的数据网关的多接入能力信息, 或 者通过 DNS解析的方式获取当前网络中各数据网关的多接入能力信息。
可以理解的是, 接入节点同样还可以通过其他方式获取当前网络中各数据 网关的多接入能力信息, 具体方式此处不作限定。
当接入节点获取到当前网络中各数据网关的多接入能力信息之后, 即可从 这些数据网关中选择支持多接入功能的数据网关为该用户终端提供服务, 需要 说明的是, 若接入节点未选择到支持多接入功能的数据网关, 则会向用户终端 发送选择失败信息, 用于指示未选择到支持多接入功能的数据网关, 即不允许 用户终端使用多接入功能。
本实施例中, 具体未选择支持多接入功能的数据网关的原因可以是当前网 络中的各数据网关均不支持多接入功能, 或者是当前网络中支持多接入功能的 数据网关负荷超过预置门限等。
则用户终端中的指示信息判断单元 1501可以判断是否从接入节点接收到选 择失败信息, 或者是未授权指示信息, 若接收到其中的任意一个, 则表示无法 正常使用多接入功能, 则多网接入单元 1502禁止发起多网接入连接建立请求, 即当用户请求进行多网接入或网络环境发生变化, 需要进行多网接入时, 多网 接入单元 1502会拒绝向对应的目标网络发送接入连接建立请求。
若指示信息判断单元 1501确定既没有接收到选择失败信息, 也没有接收到 未授权指示信息, 则多网接入单元 1502允许发起多网接入连接建立请求, 即当 用户请求进行多网接入时, 多网接入单元 1502向对应的目标网络发送接入连接 建立请求, 或者是当网络环境发生变化, 需要进行多网接入时, 用户终端向对 应的目标网络发送接入连接建立请求。
需要说明的是, 本实施例中是假设用户终端自身支持多接入功能, 若在实 际应用中不确定用户终端自身是否支持多接入功能, 则多网接入单元 1502在发 送接入连接建立请求之前还需要判断自身是否能够支持多接入功能, 若能够支 持, 则发送接入连接建立请求, 若不能支持, 则不会发送接入连接建立请求。
本实施例中, 若指示信息判断单元 1501既没有接收到选择失败信息, 也没 有接收到未授权指示信息, 则表示网络侧设备已经为当前的用户终端选择了能 够支持多接入功能的数据网关进行服务, 所以当用户终端使用多接入功能, 使 得 PDN连接中部分业务切换到 3GPP网络之后, 没有切换到 3GPP网络的其他 业务也能够同时保持正常通信, 从而保证正常的网络通信不被中断。
本领域普通技术人员可以理解上述实施例的各种方法中的全部或部分步骤 是可以通过程序来指令相关的硬件来完成, 该程序可以存储于一计算机可读存 储介质中, 存储介质可以包括: ROM、 RAM, 磁盘或光盘等。
以上对本发明实施例所提供的多网接入控制方法、 通讯系统以及相关设备 述, 以上实施例的说明只是用于帮助理解本发明的方法及其核心思想; 同时, 对于本领域的一般技术人员, 依据本发明的思想, 在具体实施方式及应用范围 上均会有改变之处, 综上所述, 本说明书内容不应理解为对本发明的限制。

Claims

权 利 要求 书
1、 一种多网接入控制方法, 其特征在于, 包括:
用户终端接收网络侧设备发送的多接入指示信息;
用户终端根据所述多接入指示信息判断用户终端是否使用多接入功能; 用户终端在使用多接入功能时发起多网接入连接建立。
2、 根据权利要求 1所述的方法, 其特征在于, 所述用户终端接收网络侧设 备发送的多接入指示信息之前包括:
用户终端向网络侧设备请求获取所述多接入指示信息。
3、 根据权利要求 1所述的方法, 其特征在于, 所述用户终端接收网络侧设 备发送的多接入指示信息之前包括:
当满足预置的条件时, 所述网络侧设备主动向所述用户终端下发多接入指 示信息。
4、 根据权利要求 2所述的方法, 其特征在于, 所述用户终端向网络侧设备 请求获取所述多接入指示信息包括:
用户终端向所述网络侧设备发送请求消息以请求所述网络侧设备反馈多接 入指示信息;
所述用户终端接收网络侧设备发送的多接入指示信息包括:
网络侧设备根据所述请求消息获取多接入指示信息, 向所述用户终端发送 所述多接入指示信息。
5、根据权利要求 4所述的方法,其特征在于, 所述网络侧设备为接入节点; 所述网络侧设备根据请求消息获取多接入指示信息, 向所述用户终端发送 所述多接入指示信息包括:
接入节点从数据网关获取数据网关的多接入能力信息;
接入节点向所述用户终端转发所述数据网关的多接入能力信息。
6、根据权利要求 4所述的方法,其特征在于, 所述网络侧设备为接入节点; 所述网络侧设备根据请求消息获取多接入指示信息, 向所述用户终端发送 所述多接入指示信息包括:
接入节点从数据网关获取数据网关的多接入能力信息;
接入节点根据所述数据网关的多接入能力信息生成数据网关支持多接入功 能指示信息或数据网关不支持多接入功能指示信息; 接入节点将所述数据网关支持多接入功能指示信息或数据网关不支持多接 入功能指示信息发送至所述用户终端。
7、根据权利要求 4所述的方法,其特征在于, 所述网络侧设备为接入节点; 所述网络侧设备根据请求消息获取多接入指示信息, 向所述用户终端发送 所述多接入指示信息包括:
接入节点从数据网关获取数据网关支持多接入功能指示信息或数据网关不 支持多接入功能指示信息;
接入节点向所述用户终端转发所述数据网关支持多接入功能指示信息或数 据网关不支持多接入功能指示信息。
8、根据权利要求 4所述的方法,其特征在于, 所述网络侧设备为接入节点; 所述网络侧设备根据请求消息获取多接入指示信息, 向所述用户终端发送 所述多接入指示信息包括:
接入节点从归属用户服务器获取所述用户终端的签约信息;
接入节点对所述签约信息进行校验, 将校验结果发送至所述用户终端。
9、 根据权利要求 4所述的方法, 其特征在于, 所述网络侧设备根据请求消 息获取多接入指示信息, 向所述用户终端发送所述多接入指示信息包括:
接入节点获取所述用户终端的多接入能力信息, 数据网关的多接入能力信 息以及用户终端的签约信息中的至少一个;
接入节点根据所述获取的信息向所述用户终端发送多接入指示信息。
10、 根据权利要求 4至 9中任一项所述的方法, 其特征在于, 所述请求消 息为附着请求或分组数据网络 PDN连接建立请求。
11、 根据权利要求 4至 9所述的方法, 其特征在于, 所述接入节点为移动 性管理实体 MME、 服务通用分组无线业务支持节点 SGSN或者移动接入网关; 所述数据网关为分组数据网络网关 PGW、 网关通用分组无线业务支持节点 GGSN或者移动锚点。
12、 根据权利要求 1 所述的方法, 其特征在于, 所述网络侧设备为动态主 机配置协议 DHCP服务器;
所述用户终端接收网络侧设备发送的多接入指示信息包括:
DHCP服务器通过 DHCP提供消息或 DHCP确认消息将多接入指示信息发 送至所述用户终端。
13、 根据权利要求 12所述的方法, 其特征在于, 所述用户终端接收网络侧 设备发送的多接入指示信息之前包括:
用户终端向 DHCP服务器发送 DHCP发现消息或 DHCP请求消息, 所述 DHCP发现消息或 DHCP请求消息携带有所述用户终端的多接入能力信息或请 求多接入指示信息的指示。
14、 根据权利要求 12所述的方法, 其特征在于, 所述 DHCP服务器通过 DHCP提供消息或 DHCP确认消息将多接入指示信息发送至所述用户终端之前 包括:
DHCP服务器获取本地预置的数据网关的多接入能力信息;
DHCP服务器根据所述数据网关的多接入能力信息向所述用户终端发送多 接入指示信息。
15、 根据权利要求 5或 14所述的方法, 其特征在于, 所述用户终端根据所 述多接入指示信息判断用户终端是否使用多接入功能包括:
用户终端根据所述多接入指示信息中包含的数据网关的多接入能力信息判 断数据网关是否支持多接入功能, 若支持, 则确定用户终端使用多接入功能; 或,
用户终端根据所述多接入指示信息中包含的数据网关的多接入能力信息判 断数据网关是否支持多接入功能, 若数据网关支持多接入功能, 则判断用户终 端是否支持多接入功能, 若用户终端支持多接入功能, 则确定用户终端使用多 接入功能。
16、 根据权利要求 6或 7所述的方法, 其特征在于, 所述用户终端根据所 述多接入指示信息判断用户终端是否使用多接入功能包括:
若所述多接入指示信息包括数据网关支持多接入功能指示信息, 则确定用 户终端使用多接入功能。
17、 根据权利要求 8或 9所述的方法, 其特征在于, 所述用户终端根据所 述多接入指示信息判断用户终端是否使用多接入功能包括:
若所述多接入指示信息包含所述签约信息的未授权指示信息或用户终端不 支持多接入功能指示信息, 则确定用户终端不使用多接入功能。
18、 一种多网接入控制方法, 其特征在于, 包括:
网络侧设备接收用户终端发送的请求消息; 网络侧设备获取各数据网关的多接入能力信息;
网络侧设备根据所述各数据网关的多接入能力信息选择支持多接入功能的 数据网关为所述用户终端提供服务。
19、 根据权利要求 18所述的方法, 其特征在于, 所述网络侧设备接收用户 终端发送的请求消息包括:
接入节点接收用户终端发送的附着请求或 PDN连接建立请求;
所述网络侧设备获取各数据网关的多接入能力信息包括:
接入节点获取各数据网关的多接入能力信息;
网络侧设备根据所述各数据网关的多接入能力信息选择支持多接入功能的 数据网关为所述用户终端提供服务包括:
接入节点根据获取到的各数据网关的多接入能力信息选择支持多接入功能 的数据网关为所述用户终端提供服务。
20、 根据权利要求 19所述的方法, 其特征在于, 所述接入节点获取各数据 网关的多接入能力信息之前包括:
接入节点获取所述用户终端的签约信息;
若所述签约信息指示所述用户终端被授权多接入, 则触发所述接入节点获 取各数据网关的多接入能力信息的步骤。
21、 根据权利要求 19 所述的方法, 其特征在于, 当所述附着请求或 PDN 连接建立请求中携带有所述用户终端的多接入能力信息时, 所述接入节点获取 各数据网关的多接入能力信息之前包括:
接入节点根据所述用户终端的多接入能力信息判断所述用户终端是否支持 多接入功能, 若支持, 则触发所述接入节点获取各数据网关的多接入能力信息 的步骤。
22、 根据权利要求 19至 21 中任一项所述的方法, 其特征在于, 所述接入 节点获取各数据网关的多接入能力信息, 并根据获取到的各数据网关的多接入 能力信息选择支持多接入功能的数据网关为所述用户终端提供服务包括:
所述接入节点根据自身静态配置信息选取支持多接入功能的数据网关为所 述用户终端提供服务;
或,
所述接入节点通过域名服务器解析方式获取各数据网关的多接入能力信 选取支持多接入功能的数据网关为所述用户终端提供服务。
23、 根据权利要求 19至 21 中任一项所述的方法, 其特征在于, 所述接入 节点为 MME、 SGSN或移动接入网关, 所述数据网关为 PGW、 GGSN或者移动 锚点。
24、 一种通讯系统, 其特征在于, 包括:
网络侧设备, 用于获取多接入指示信息, 向用户终端发送所述多接入指示 信息;
用户终端, 用于接收网络侧设备发送的多接入指示信息, 根据所述多接入 指示信息判断用户终端是否使用多接入功能, 在使用所述多接入功能时发起多 网接入连接建立请求。
25、 根据权利要求 24所述的通讯系统, 其特征在于, 所述网络侧设备为接 入节点;
所述通讯系统还包括数据网关, 用于向所述接入节点提供多接入指示信息; 所述接入节点还用于接收用户终端发送的附着请求或 PDN连接建立请求, 获取所述用户终端的签约信息, 当所述签约信息指示所述用户终端被授权多接 入时, 获取多接入指示信息。
26、 根据权利要求 25所述的通讯系统, 其特征在于, 所述数据网关还用于 接收所述接入节点发送的包含用户终端的多接入能力信息的建立 PDN连接请求 消息, 根据所述用户终端的多接入能力信息判断所述用户终端是否支持多接入 功能, 若支持, 则将多接入指示信息携带于建立 PDN连接响应消息中发送至所 述接入节点。
27、 根据权利要求 24至 26中任一项所述的通讯系统, 其特征在于, 所述 数据网关为 PGW, GGSN或移动锚点, 所述接入节点为 MME, SGSN或移动接 入网关。
28、 一种通讯系统, 其特征在于, 包括:
网络侧设备, 用于接收用户终端发送的请求消息, 获取各数据网关的多接 入能力信息, 根据所述各数据网关的多接入能力信息选择支持多接入功能的数 据网关为所述用户终端提供服务;
数据网关, 用于向所述网络侧设备提供所述数据网关的多接入能力信息; 用户终端, 用于向所述网络侧设备发送请求消息。
29、 根据权利要求 28所述的通讯系统, 其特征在于, 所述网络侧设备为接 入节点;
所述接入节点还用于获取所述用户终端的签约信息, 当所述签约信息指示 所述用户终端被授权多接入时, 获取各数据网关的多接入能力信息。
30、 根据权利要求 29所述的通讯系统, 其特征在于, 所述请求消息中包含 用户终端的多接入能力信息, 所述接入节点还用于根据所述用户终端的多接入 能力信息判断所述用户终端是否支持多接入功能, 若支持, 则获取各数据网关 的多接入能力信息。
31、 根据权利要求 28至 30中任一项所述的通讯系统, 其特征在于, 所述 数据网关为 PGW, GGSN或移动锚点, 所述接入节点为 MME, SGSN或移动接 入网关。
32、 一种网络侧设备, 其特征在于, 包括:
获取单元, 用于获取多接入指示信息;
发送单元, 用于向用户终端发送所述多接入指示信息, 所述多接入指示信 息用于指示所述用户终端是否允许使用多接入功能。
33、 根据权利要求 32所述的网络侧设备, 其特征在于, 所述网络侧设备还 包括:
接收单元, 用于接收所述用户终端发送的请求消息, 并触发所述获取单元 执行相应操作。
34、 一种网络侧设备, 其特征在于, 包括:
请求接收单元, 用于接收用户终端发送的请求消息;
信息获取单元, 用于获取各数据网关的多接入能力信息;
选择单元, 用于根据所述各数据网关的多接入能力信息选择支持多接入功 能的数据网关为所述用户终端提供服务。
35、 根据权利要 34所述的网络侧设备, 其特征在于, 所述网络侧设备还包 括:
签约信息校验单元, 用于获取所述用户终端的签约信息, 若所述签约信息 指示用户终端被授权多接入, 则触发所述信息获取单元执行相应操作。
36、 根据权利要求 35所述的网络侧设备, 其特征在于, 所述网络侧设备还 包括:
指示发送单元, 用于当所述用户终端的签约信息指示所述用户终端未被授 权多接入, 向所述用户终端发送未授权指示信息, 所述未授权指示信息用于指 示所述用户终端未被授权多接入, 当所述选择单元未选择到支持多接入功能的 数据网关时, 向所述用户终端发送选择失败信息, 所述选择失败信息用于指示 用户终端不允许使用多接入功能。
37、 一种用户终端, 其特征在于, 包括:
信息接收单元, 用于接收网络侧设备发送的多接入指示信息;
信息校验单元, 用于根据所述多接入指示信息判断用户终端是否使用多接 入功能;
多网接入单元, 用于在使用多接入功能时发起多网接入连接建立请求。
38、根据权利要求 37所述的用户终端, 其特征在于, 所述用户终端还包括: 请求发送单元, 用于向所述网络侧设备发送请求消息, 所述请求消息中携 带用户终端的多接入能力信息或请求多接入指示信息的指示, 所述用户终端的 多接入能力信息或请求多接入指示信息的指示用于请求所述网络侧设备反馈所 述多接入指示信息。
39、 一种用户终端, 其特征在于, 包括:
指示信息判断单元, 用于判断用户终端是否接收到网络侧设备发送的未授 权指示信息或选择失败信息, 所述未授权指示信息用于指示所述用户终端未被 授权多接入, 所述选择失败信息用于指示用户终端不允许使用多接入功能; 多网接入单元, 用于当未接收到所述未授权指示信息以及所述选择失败信 息时发起多网接入连接建立请求。
40、 一种计算机程序产品, 其特征在于, 所述计算机程序产品包括计算机 程序代码, 当所述计算才 呈序代码被一个计算机执行的时候, 所述计算机程序 代码可以使得所述计算机执行权利要求 1-23中任意一项的步骤。
PCT/CN2010/071147 2009-04-21 2010-03-19 多网接入控制方法、通讯系统以及相关设备 WO2010121511A1 (zh)

Priority Applications (5)

Application Number Priority Date Filing Date Title
EP10766601.8A EP2410701B1 (en) 2009-04-21 2010-03-19 Method for multi-network-access control, communication system and related devices
ES10766601.8T ES2526565T3 (es) 2009-04-21 2010-03-19 Método para control de acceso a redes múltiples, sistema de comunicación y dispositivos relacionados
BRPI1016177-5A BRPI1016177B1 (pt) 2009-04-21 2010-03-19 Método de controle de acesso a múltiplas redes, sistema de comunicação e equipamento de usuário
JP2012506316A JP5379297B2 (ja) 2009-04-21 2010-03-19 マルチネットワークアクセス制御の方法、通信システム、および関連するデバイス
US13/243,142 US8718031B2 (en) 2009-04-21 2011-09-23 Multi-network access control method, communication system, and relevant devices

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200910135550.3A CN101873589B (zh) 2009-04-21 2009-04-21 多网接入控制方法、通讯系统以及相关设备
CN200910135550.3 2009-04-21

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US13/243,142 Continuation US8718031B2 (en) 2009-04-21 2011-09-23 Multi-network access control method, communication system, and relevant devices

Publications (1)

Publication Number Publication Date
WO2010121511A1 true WO2010121511A1 (zh) 2010-10-28

Family

ID=42998199

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2010/071147 WO2010121511A1 (zh) 2009-04-21 2010-03-19 多网接入控制方法、通讯系统以及相关设备

Country Status (7)

Country Link
US (1) US8718031B2 (zh)
EP (1) EP2410701B1 (zh)
JP (2) JP5379297B2 (zh)
CN (1) CN101873589B (zh)
BR (1) BRPI1016177B1 (zh)
ES (1) ES2526565T3 (zh)
WO (1) WO2010121511A1 (zh)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2012175575A (ja) * 2011-02-23 2012-09-10 Ntt Docomo Inc 通信サービス提供システム、通信サービス制御ノード、移動通信端末装置、通信サービス提供方法
JP2012531134A (ja) * 2009-06-23 2012-12-06 中興通訊股▲ふん▼有限公司 発展型パケットシステムにおける端末のマルチアクセス方法及びシステム
WO2013004793A1 (en) * 2011-07-05 2013-01-10 Nec Europe Ltd. Method for supporting selection of pdn connections for a mobile terminal and mobile terminal
WO2013104951A1 (en) * 2012-01-10 2013-07-18 Alcatel Lucent Method and apparatus for data transmission in communication network via an assistant wireless network
JP2014509477A (ja) * 2011-01-28 2014-04-17 華為技術有限公司 サービングゲートウェイを選択する方法及び装置
CN108463005A (zh) * 2011-07-12 2018-08-28 交互数字专利控股公司 用于多rat接入模式操作的方法和设备

Families Citing this family (27)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
FR2968155A1 (fr) 2010-11-30 2012-06-01 France Telecom Technique de communication entre un equipement utilisateur et un reseau de donnees dans un reseau de communication
FR2968156A1 (fr) * 2010-11-30 2012-06-01 France Telecom Technique de communication entre un equipement utilisateur et un reseau de donnees dans un reseau de communication
CN102685921B (zh) * 2011-03-11 2017-04-26 中兴通讯股份有限公司 一种双通道通信方法和系统
CN102740399B (zh) * 2011-04-13 2014-12-17 华为技术有限公司 一种多接入技术的传输方法及装置
CN107820328B (zh) 2011-08-19 2021-05-28 交互数字专利控股公司 无线发射/接收单元wtru和由wtru执行的方法
CN103002543B (zh) * 2011-09-14 2016-12-21 中兴通讯股份有限公司 一种多接入方法及系统
US9313094B2 (en) * 2011-11-03 2016-04-12 Telefonaktiebolaget Lm Ericsson (Publ) Node and method for signalling in a proxy mobile internet protocol based network
CN109041089B (zh) * 2012-08-08 2021-12-31 华为技术有限公司 信息处理方法和装置
US10638526B2 (en) * 2012-09-24 2020-04-28 Qualcomm Incorporated Transport of control protocol for trusted WLAN (TWAN) offload
CN102984815A (zh) * 2012-12-07 2013-03-20 华为终端有限公司 分组数据连接的处理方法、终端设备、网络侧设备及系统
US9225703B2 (en) * 2013-05-31 2015-12-29 Richo Company, Ltd. Protecting end point devices
CN104796945B (zh) * 2014-01-16 2019-07-02 中国移动通信集团广东有限公司 一种双链路数据传输方法、装置、系统及一种终端
WO2016000759A1 (en) * 2014-07-01 2016-01-07 Telefonaktiebolaget L M Ericsson (Publ) Method and nodes for handling esm information
RU2598337C2 (ru) * 2014-12-19 2016-09-20 Закрытое акционерное общество "Лаборатория Касперского" Система и способ выбора средств перехвата данных, передаваемых по сети
CN105898810A (zh) * 2015-01-26 2016-08-24 中兴通讯股份有限公司 一种用户设备选择网络的方法和装置
CN105992394A (zh) * 2015-01-29 2016-10-05 中兴通讯股份有限公司 网络连接方法及装置
CN106998552A (zh) * 2016-01-26 2017-08-01 中兴通讯股份有限公司 路由控制方法、装置及系统
JP2019505132A (ja) * 2016-02-03 2019-02-21 華為技術有限公司Huawei Technologies Co.,Ltd. ユーザー機器識別子を取得する方法および装置とユーザー機器識別子を送信する方法および装置
CN106358274B (zh) * 2016-10-09 2020-03-17 宇龙计算机通信科技(深圳)有限公司 一种消息传输的省电方法及相关设备
US10405174B2 (en) * 2016-10-18 2019-09-03 Telefonaktiebolaget Lm Ericsson (Publ) Wireless terminal device, network node, method and computer program for simultaneous multiple radio access technology operation
WO2018141081A1 (en) * 2017-02-02 2018-08-09 Qualcomm Incorporated Network assisted multi-subscription physical layer sharing
WO2019011398A1 (en) 2017-07-10 2019-01-17 Motorola Mobility Llc CONNECTING MULTIPLE ACCESS DATA IN A MOBILE NETWORK
US11116028B2 (en) 2017-07-10 2021-09-07 Motorola Mobility Llc Multi-access data connection in a mobile network
US12052606B2 (en) * 2018-04-09 2024-07-30 Lenovo (Singapore) Pte. Ltd. Data packet steering on a multi-access data connection
CN111770554B (zh) * 2019-03-30 2022-04-22 成都华为技术有限公司 一种网络接入的方法和装置
EP3913969B1 (en) * 2020-05-22 2024-07-17 Deutsche Telekom AG Method for providing an enhanced and/or more efficient broadband access functionality within a telecommunications network, using multi path and/or multi access functionality for at least one specific traffic or application category, telecommunications network, user equipment, atsss server functionality node or instance or pcf node or instance, program and computer-readable medium
US20220247831A1 (en) * 2021-02-02 2022-08-04 Lenovo (Singapore) Pte. Ltd. Wifi router buffered download

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101019379A (zh) * 2004-09-13 2007-08-15 法国电信公司 多接入终端与通信网络的关联
WO2007148252A2 (en) * 2006-06-19 2007-12-27 Nokia Corporation Selection of an access layer termination node in a multi-access network environment
CN101127652A (zh) * 2006-08-17 2008-02-20 华为技术有限公司 一种确定用户终端访问外部网络锚点的方法、装置及系统

Family Cites Families (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2373965B (en) * 2001-03-30 2004-07-28 Motorola Inc Apparatus for managing capabilities in a communications network and method therefor
US6697811B2 (en) * 2002-03-07 2004-02-24 Raytheon Company Method and system for information management and distribution
US7158810B2 (en) * 2002-06-27 2007-01-02 Nokia Corporation Indication of user equipment capabilities before radio resource control connection
CN101015174B (zh) 2004-09-06 2013-01-02 艾利森电话股份有限公司 经由不同接入技术的多接入通信
GB0422192D0 (en) 2004-10-06 2004-11-03 Nokia Corp Transfer of a user equipment in a communication system
US20060264217A1 (en) * 2005-05-19 2006-11-23 Interdigital Technology Corporation Method and system for reporting evolved utran capabilities
CN100446492C (zh) * 2005-08-25 2008-12-24 华为技术有限公司 局域网终端接入局域网的方法
US7809125B2 (en) * 2005-09-01 2010-10-05 Avaya Inc. Method and apparatus for selection of special-purpose gateways
WO2007058024A1 (ja) * 2005-11-16 2007-05-24 Nec Corporation 移動通信システム、コアネットワーク、無線ネットワークシステム及びその収容ネットワーク選択方法
WO2008110902A2 (en) * 2007-03-15 2008-09-18 Telefonaktiebolaget Lm Ericsson (Publ) Method and system for global anchor registration
CA2683918C (en) * 2007-04-17 2016-02-02 Telefonaktiebolaget Lm Ericsson (Publ) A method of handling radio access and to prioritize subscribers in case of an emergency
US20090047947A1 (en) * 2007-08-02 2009-02-19 Qualcomm Incorporated Dynamic gateway selection based on data service and roaming protocol
CN101365230B (zh) * 2007-08-07 2010-08-11 华为技术有限公司 异构网络切换/改变时的用户分离方法、系统及装置
US9584622B2 (en) * 2007-08-23 2017-02-28 Telefonaktiebolaget Lm Ericsson (Publ) Method for network controlled access selection
US8391226B2 (en) * 2007-11-26 2013-03-05 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for use in a communications network
US20110040855A1 (en) * 2008-03-27 2011-02-17 Miklos Gyoergy Systems and methods of reducing signaling in a network having a database server
AU2008354992B2 (en) * 2008-04-18 2015-01-15 Telefonaktiebolaget Lm Ericsson (Publ) Access network selection in a multi-access network environment
EP2340657A4 (en) * 2008-10-24 2013-09-25 Mediatek Inc COMPETITION-BASED ACCESS CHANNEL DESIGN IN OFDM / OFDMA MIMO SYSTEMS
CN101931946B (zh) * 2009-06-23 2015-05-20 中兴通讯股份有限公司 演进的分组系统中的终端的多接入方法及系统

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101019379A (zh) * 2004-09-13 2007-08-15 法国电信公司 多接入终端与通信网络的关联
WO2007148252A2 (en) * 2006-06-19 2007-12-27 Nokia Corporation Selection of an access layer termination node in a multi-access network environment
CN101127652A (zh) * 2006-08-17 2008-02-20 华为技术有限公司 一种确定用户终端访问外部网络锚点的方法、装置及系统

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2012531134A (ja) * 2009-06-23 2012-12-06 中興通訊股▲ふん▼有限公司 発展型パケットシステムにおける端末のマルチアクセス方法及びシステム
JP2014509477A (ja) * 2011-01-28 2014-04-17 華為技術有限公司 サービングゲートウェイを選択する方法及び装置
JP2012175575A (ja) * 2011-02-23 2012-09-10 Ntt Docomo Inc 通信サービス提供システム、通信サービス制御ノード、移動通信端末装置、通信サービス提供方法
WO2013004793A1 (en) * 2011-07-05 2013-01-10 Nec Europe Ltd. Method for supporting selection of pdn connections for a mobile terminal and mobile terminal
CN108463005A (zh) * 2011-07-12 2018-08-28 交互数字专利控股公司 用于多rat接入模式操作的方法和设备
EP3554133A1 (en) * 2011-07-12 2019-10-16 InterDigital Patent Holdings, Inc. Method and apparatus for multi-rat access mode operation
CN108463005B (zh) * 2011-07-12 2022-02-25 交互数字专利控股公司 用于多rat接入模式操作的方法和设备
WO2013104951A1 (en) * 2012-01-10 2013-07-18 Alcatel Lucent Method and apparatus for data transmission in communication network via an assistant wireless network
US9520977B2 (en) 2012-01-10 2016-12-13 Alcatel Lucent Method and apparatus for data transmission in communication network

Also Published As

Publication number Publication date
BRPI1016177A2 (pt) 2016-04-19
CN101873589B (zh) 2016-03-09
JP5379297B2 (ja) 2013-12-25
JP2013255292A (ja) 2013-12-19
CN101873589A (zh) 2010-10-27
EP2410701A1 (en) 2012-01-25
BRPI1016177B1 (pt) 2019-02-12
EP2410701B1 (en) 2014-10-15
US20120250616A1 (en) 2012-10-04
US8718031B2 (en) 2014-05-06
ES2526565T3 (es) 2015-01-13
JP2012524485A (ja) 2012-10-11
EP2410701A4 (en) 2012-02-15

Similar Documents

Publication Publication Date Title
WO2010121511A1 (zh) 多网接入控制方法、通讯系统以及相关设备
US8621555B2 (en) Access control method and system for packet data network, PCRF entity
US9167430B2 (en) Access method and system, and mobile intelligent access point
US7733824B2 (en) Fixed access point for a terminal device
US9113436B2 (en) Method and system for information transmission
WO2014056445A1 (zh) 一种路由转发的方法、系统及控制器
WO2009043209A1 (fr) Procédé permettant d'établir une porteuse vers un terminal utilisateur en mode repos
WO2010081329A1 (zh) 业务流迁移过程中对网络资源进行控制的方法和系统
WO2011095100A1 (zh) 一种对本地ip连接的建立进行控制的方法和系统
US9544832B2 (en) Method, apparatus and system for policy control
WO2009124436A1 (zh) 一种承载绑定和事件报告功能策略控制的方法及系统
WO2013131487A1 (zh) 融合的核心网及其接入方法
WO2012019507A1 (zh) 一种实现固定宽带接入网接入的策略控制方法及系统
WO2014067420A1 (zh) 分组数据网络类型的管理方法、装置及系统
WO2012130133A1 (zh) 一种接入点及终端接入方法
US9516681B2 (en) Method, device and system for accessing core network by means of non-3GPP access
CN101909275B (zh) 一种信息同步方法及通讯系统以及相关设备
WO2011017979A1 (zh) 支持ip分流的通信系统中资源管理方法与装置
WO2016065639A1 (zh) 数据处理的方法、装置、终端、移动管理实体及系统
WO2013086917A1 (zh) 会话处理方法及装置
WO2012013103A1 (zh) 一种网关标识上报的方法及系统
WO2012041131A1 (zh) 一种用户参与本地访问连接建立的方法及系统
WO2012024990A1 (zh) 一种网元信息获取方法和系统
WO2013041063A1 (zh) 一种接入核心网以及网络侧发起去附着的方法和系统
WO2011050662A1 (zh) 多接入的处理方法、家乡代理及用户设备

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: 10766601

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2012506316

Country of ref document: JP

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2010766601

Country of ref document: EP

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: PI1016177

Country of ref document: BR

ENP Entry into the national phase

Ref document number: PI1016177

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20111021