[go: up one dir, main page]

WO2016095698A1 - 应用服务器地址获取方法、设备和系统 - Google Patents

应用服务器地址获取方法、设备和系统 Download PDF

Info

Publication number
WO2016095698A1
WO2016095698A1 PCT/CN2015/095998 CN2015095998W WO2016095698A1 WO 2016095698 A1 WO2016095698 A1 WO 2016095698A1 CN 2015095998 W CN2015095998 W CN 2015095998W WO 2016095698 A1 WO2016095698 A1 WO 2016095698A1
Authority
WO
WIPO (PCT)
Prior art keywords
address
entity
user
subscription data
domain name
Prior art date
Application number
PCT/CN2015/095998
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 华为技术有限公司
Publication of WO2016095698A1 publication Critical patent/WO2016095698A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H04W8/20—Transfer of user or subscriber data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming

Definitions

  • the embodiment of the invention relates to the field of communication technologies, and in particular, to an application server (English: Application Server, AS for short) address acquisition method, device and system.
  • application server English: Application Server, AS for short
  • the SAE/LTE network has covered some urban and traffic hotspots.
  • the SAE/LTE network and the 2G/3G network coexist.
  • the SAE/LTE network is used as a packet switching system.
  • the voice service can only be transmitted on the packet switching (English: Packet Switching, PS for short) domain bearer.
  • the IMS controls the voice service through the IP-based network. This is what is commonly referred to as VoLTE.
  • the voice service is generally carried in the circuit switching (English: Circuit Switching, CS: domain) domain.
  • CS voice and VoLTE voice coexist. of.
  • the UE sends a supplementary service setting request to the authentication proxy (English: Authentication Proxy, AP for short); the AP challenges the UE and allows the UE to boot the server function (English: Bootstrapping Server Function, BSF for short)
  • the UE passes the BSF authentication
  • the UE resends the supplementary service setting request to the AP and carries the information passed by the BSF authentication.
  • the AP contacts the BSF to confirm the user authentication, the AP sends the supplementary service setting request to the AP. AS, thus complementing the business setup success.
  • the existing communication carrier is still issued by the global user identification card (English: Universal Subscriber Identity Module, USIM) when deploying VoLTE.
  • the UE derives the Uniform Resource Identifier (English: Uniform Resource Identifier, URI for short) in the following manner:
  • the UE takes the International Mobile Subscriber Identification Number in the USIM (English: International Mobile Subscriber Identification Number, Abbreviated as: Mobile Network Code (English: Mobile Network Code, MNC for short) and Mobile Country Code (English: Mobile Country Code, MCC), assembled into "xcap.mnc ⁇ MNC>.mcc ⁇ MCC >.pub.3gppnetwork.org" is used as the XCAP server URI, and the URI is carried in the supplementary service setting request and sent to the AP, and then the AP sends a supplementary service setting request to the corresponding AS according to the URI.
  • the URI is carried in the supplementary service setting request and sent to the AP, and then the AP sends a supplementary service setting request to the
  • the MNCs and MCCs of the USIMs belonging to the same mobile network are the same, so for the USIMs of different provinces/regions, the XCAP server address derived by the UE is exactly the same.
  • the AP cannot obtain the address of the AS to which the USIM belongs.
  • the AS to which the USIM belongs cannot be correctly addressed.
  • An embodiment of the present invention provides an application server address obtaining method, device, and system, which are used to implement an AP entity to obtain an address of an AS to which a user of a UE belongs.
  • an embodiment of the present invention provides an AS address obtaining method, including:
  • the AP entity receives the service setting message sent by the UE;
  • the AP entity receives subscription data of the user sent by the BSF entity, where the subscription data of the user includes an address of an AS to which the user belongs.
  • the address of the AS is any one of the following: an IP address of the AS, a domain name address of the AS, and a host name address of the AS.
  • the AP entity when the address of the AS is a domain name address of the AS or a host of the AS After the address is received, the AP entity, after receiving the address of the AS sent by the BSF entity, further includes:
  • the AP entity acquires an IP address of the AS according to the domain name address of the AS or the host name address of the AS.
  • the AP entity acquires the information according to the domain name address of the AS or the host name address of the AS
  • the IP address of the AS including:
  • the AP entity according to the domain name address of the AS or the host name address of the AS, and the domain name address of the AS stored in the AP entity or the host name address of the AS and the IP address of the AS Corresponding relationship, obtaining the IP address of the AS; or
  • the AP entity queries the domain name resolution system DNS according to the domain name address of the AS or the host name address of the AS, and obtains the IP address of the AS.
  • a fourth possible implementation of the first aspect when the domain name address of the AS is at least two When the IP address is corresponding, each of the at least two IP addresses has different priorities;
  • the AP entity acquires an IP address of the AS, including:
  • the AP entity obtains the IP address with the highest priority from the at least two IP addresses corresponding to the domain name address of the AS as the IP address of the AS.
  • the method further includes:
  • the AP entity sends the service setting message to the AS according to the IP address of the AS.
  • the method further includes:
  • the AP entity sends the service setting message to the AS according to the address of the AS.
  • an embodiment of the present invention provides an AS address obtaining method, including:
  • the BSF entity receives the service setting message sent by the UE;
  • an embodiment of the present invention provides an AP entity, including:
  • a receiving unit configured to receive a service setting message sent by the UE
  • a sending unit configured to send, by using the service setting message received by the receiving unit, a first request message to a BSF entity, where the first request message is used to request subscription data of a user using the UE;
  • the receiving unit is further configured to receive the subscription data of the user sent by the BSF entity, where the subscription data of the user includes an address of an AS to which the user belongs.
  • an embodiment of the present invention provides a BSF entity, including:
  • a receiving unit configured to receive a service setting message sent by the UE
  • a sending unit configured to send, according to the service setting message received by the receiving unit, a second request message to the HSS, where the second request message is used to request subscription data of a user using the UE;
  • the receiving unit is further configured to receive the subscription data of the user that is sent by the HSS, where the subscription data of the user includes an address of an AS to which the user belongs; and receive the first request sent by the AP entity. a message, the first request message is used to request subscription data of the user;
  • the sending unit is further configured to send the subscription data of the user to the AP entity according to the first request message received by the receiving unit.
  • the embodiment of the present invention provides an AS address obtaining system, which includes: an AP entity provided by the third aspect of the embodiment of the present invention, and a BSF entity provided by the fourth aspect of the embodiment of the present invention.
  • the AS address obtaining method, device, and system provided by the embodiment of the present invention receive the service setting message sent by the UE by using the AP entity, and then send the first request message to the BSF entity according to the service setting message, and then receive the information sent by the BSF entity.
  • FIG. 1 is a schematic diagram of an application network architecture of an AS address obtaining method according to the present invention
  • Embodiment 1 of an AS address obtaining method according to the present invention is a flowchart of Embodiment 1 of an AS address obtaining method according to the present invention
  • Embodiment 3 is a flowchart of Embodiment 2 of an AS address obtaining method according to the present invention.
  • FIG. 5 is a flowchart of Embodiment 4 of an AS address obtaining method according to the present invention.
  • Embodiment 1 of an AP entity according to the present invention
  • Embodiment 7 is a schematic structural diagram of Embodiment 2 of an AP entity according to the present invention.
  • Embodiment 8 is a schematic structural diagram of Embodiment 1 of a BSF entity according to the present invention.
  • Embodiment 9 is a schematic structural diagram of Embodiment 3 of an AP entity according to the present invention.
  • Embodiment 2 of a BSF entity according to the present invention
  • FIG. 11 is a schematic structural diagram of an embodiment of an AS address obtaining system according to the present invention.
  • FIG. 1 is a schematic diagram of an application network architecture of an AS address obtaining method according to the present invention.
  • the AS address obtaining method provided by the embodiments of the present invention can be applied to, for example, a VoLTE network, and the 3GPP standard protocol introduces a UE and an AS.
  • the Ut interface between the UE and the AS communicates through the Ut interface to set up services.
  • the Generic Authentication Architecture (GAA) authentication architecture is defined in the 3GPP standard protocol.
  • GAA Generic Authentication Architecture
  • the introduction of the GAA authentication architecture adds two logical functions to the VoLTE network. Entities are BSF entities and AP entities.
  • the BSF entity communicates with the HSS through the Zh interface, the BSF entity communicates with the AP entity through the Zn interface, the BSF entity communicates with the UE through the Ub interface, and the BSF entity completes the UE legality through interaction with the UE and the HSS.
  • the authentication is performed, and the shared access key is generated on the UE side and the network side.
  • the AP entity is a service access authentication proxy.
  • the AP entity communicates with the UE through the Ua interface.
  • the AP entity first triggers the BSF to the UE.
  • the AP entity acts as a reverse proxy, and acts as an AS for the UE and as a UE for the AS.
  • the AP entity is, for example, a network application function (English: Network Application Function, NAF) entity that implements the AP function.
  • NAF Network Application Function
  • the network architecture shown in FIG. 1 is an example of an application network of the AS address acquisition method of the present invention, but the present invention is not limited thereto.
  • Embodiment 1 of an AS address obtaining method according to the present invention is a flowchart of Embodiment 1 of an AS address obtaining method according to the present invention. As shown in FIG. 2, the method in this embodiment may include:
  • the AP entity receives a service setting message sent by the UE.
  • the user when the user of the UE needs to perform service setting, the user may operate the interface of the UE, so that the UE sends a service setting message to the AP entity, where the service may be a supplementary service, for example: Number display, call barring, setting forwarding number, activation, or deactivation.
  • the service setting message may be a service setting request message or a service setting query message.
  • the AP entity sends a first request message to the BSF entity according to the service setting message, where the first request message is used to request subscription data of a user using the UE.
  • the AP entity after the AP entity receives the service setting message sent by the UE, the AP entity sends a first request message to the BSF entity according to the service setting message, and is used to request the BSF entity to acquire the user who uses the UE. Signing data.
  • the AP entity receives the subscription data of the user sent by the BSF entity, where the subscription data of the user includes an address of an AS to which the user belongs.
  • the BSF entity determines the subscription data of the user according to the first request message, and then sends the subscription data of the user to the AP entity, and the user subscribes.
  • the data includes the address of the AS to which the user belongs, and the AP entity obtains the address of the AS to which the user belongs from the subscription data of the user.
  • the BSF entity may carry the subscription data of the user in the response message corresponding to the first request message and send the data to the AP entity.
  • the subscription data of the user is the Generic Bootstrapping Architecture User Security Settings (GUSS) of the user
  • GUISS Generic Bootstrapping Architecture User Security Settings
  • AS to which the user belongs is the AS that provides the service setting function for the user, for example, If the USIM card in the UE is opened in Beijing, the user of the UE belongs to Beijing, and the AS to which the user belongs is the AS whose home location is Beijing.
  • GUISS Generic Bootstrapping Architecture User Security Settings
  • the first request message is a bootstrapping information request (English: Bootstrapping Information)
  • the request message is a BIR message.
  • the response message corresponding to the first request message is a Bootstrapping Information Answer (BIA) message.
  • BIOS Bootstrapping Information Answer
  • the AP entity receives the service setting message sent by the UE, and then sends a first request message for requesting the user of the UE to the BSF entity according to the service setting message, and then receives the first request message sent by the BSF entity.
  • the subscription data of the user including the address of the AS of the user, so that the AP entity can correctly obtain the address of the AS to which the user belongs, and further, the AP entity can correctly address the user according to the address of the AS.
  • the address of the AS may be any one of the following: an Internet Protocol (English: Internet Protocol, IP address) address of the AS, a domain name address of the AS, and a host name address of the AS.
  • IP address is, for example, 192.168.1.1
  • the domain name address is: as.chinamobile.com
  • the host name address is, for example, as01.chinamobile.com.
  • the AP entity further includes: the AP entity sending the service setting message to the AS according to the address of the AS.
  • the user's service setting message can be routed to the correct AS that can handle the user's service setting message.
  • the service setting message of the user can be routed to the correct AS that can process the service setting message of the user.
  • the AP entity when the address of the AS is an IP address of the AS, the AP entity sends the service setting message to the AS according to the IP address of the AS.
  • the address of the AS is the domain name address of the AS
  • the AP entity can obtain the IP address of the AS according to the domain name address of the AS; and then, according to the IP address of the AS, the AS Send the service setup message.
  • the AP entity may obtain the IP address of the AS according to the domain name address of the AS, including: the AP entity according to the domain name address of the AS, and the domain name address of the AS stored in the AP entity. Acquiring the IP address of the AS to obtain the IP address of the AS; or the AP entity queries the domain name resolution system (English: Domain Name System, DNS for short) according to the domain name address of the AS, and obtains the The IP address of the AS.
  • the domain name resolution system English: Domain Name System, DNS for short
  • the domain name address of the AS corresponds to at least two IP addresses (that is, the AS The domain name address corresponds to at least two ASs, and each of the at least two IP addresses has a different priority;
  • the AP entity Obtaining, by the AP entity, the IP address of the AS, the AP entity acquiring the IP address with the highest priority from the at least two IP addresses corresponding to the domain name address of the AS as the IP address of the AS .
  • the AP entity may select an IP address of one of the normally operating ASs.
  • the address of the AS is the host name address of the AS
  • the AP entity can obtain the IP address of the AS according to the host name address of the AS; and then according to the IP address of the AS, The AS sends the service setup message.
  • the AP entity may obtain the IP address of the AS according to the host name address of the AS, including: the AP entity according to the host name address of the AS, and the host of the AS stored in the AP entity.
  • the corresponding address of the name and the IP address of the AS, the IP address of the AS is obtained; or the AP entity queries the domain name resolution system according to the host name address of the AS (English: Domain Name System, DNS: Get the IP address of the AS.
  • the AP entity can correctly transmit the service setting message sent by the UE of the user to the AS to which the UE belongs according to the address of the AS to which the user belongs.
  • FIG. 3 is a flowchart of Embodiment 1 of an AS address obtaining method according to the present invention. As shown in FIG. 3, the method in this embodiment may include:
  • the BSF entity receives a service setting message sent by the UE.
  • the UE when the user of the UE operates the UE to perform service setting, if the AP entity triggers the UE to authenticate the BSF entity, the UE sends a service setting message to the BSF entity, where the service may be a supplementary service. For example: number display, call barring, setting forward number, activation, or deactivation.
  • the service setting message may be a service setting request message or a service setting query message.
  • the BSF entity sends a second request message to the HSS according to the service setting message, where the second request message is used to request subscription data of a user using the UE.
  • the BSF entity after the BSF entity receives the service setting message sent by the UE, the BSF entity sends a second request message to the HSS, for requesting the HSS to acquire the subscription data of the user using the UE.
  • the BSF entity receives the subscription data of the user sent by the HSS, where the subscription data of the user includes an address of an AS to which the user belongs.
  • the HSS may obtain the subscription data of the user according to the second request message, where the subscription data of the user is the GUSS subscription data of the user,
  • the user's subscription data includes the address of the AS to which the user belongs, and then transmits the subscription data of the user carrying the address of the AS to the BSF entity.
  • the HSS may send the subscription data of the user to the BSF entity in the response message corresponding to the second request message, and the BSF entity obtains the subscription data of the user from the response message.
  • the second request message may be a multimedia authentication request (MAR: Multimedia), and the response message corresponding to the second request message is a multimedia authentication response (English: Multimedia Authentication Answer, Abbreviation: MAA) message.
  • MAR Multimedia
  • MAA Multimedia Authentication Answer
  • the HSS receives a service release message sent by the service distribution device, where the service transmission message includes an address of the AS.
  • the service issuing device sends a service sending message including the subscription data of the user to the HSS.
  • the BSF entity receives a first request message sent by the AP entity, where the first request message is used to request subscription data of the user.
  • the BSF entity receives the first request message sent by the AP entity, and learns from the first request message that the AP entity requests to obtain the subscription data of the user.
  • the BSF entity sends the subscription data of the user to the AP entity according to the first request message.
  • the BSF entity sends the subscription data of the user sent by the HSS to the AP entity according to the first request message, and the AP entity obtains the address of the AS to which the user belongs from the subscription data of the user sent by the BSF entity.
  • the BSF entity may send the subscription data of the user to the AP entity in the response message corresponding to the first request message, and the AP entity obtains the subscription data of the user from the response message.
  • the BSF entity receives the service setting message sent by the UE, and then sends a second request message for requesting to use the subscription data of the user of the UE to the HSS according to the service setting message, thereby receiving the HSS.
  • the sent address including the address of the AS to which the user belongs Receiving the subscription data of the user, and then receiving the first request message sent by the AP entity for requesting the subscription data of the user, and sending the address including the address of the AS to the AP entity according to the first request message.
  • the user's subscription data thus, the AP entity can correctly obtain the address of the AS to which the user belongs. Further, the AP entity can correctly address the AS to which the user belongs according to the address of the AS.
  • the address of the AS may be any one of the following: an IP address of the AS, a domain name address of the AS, and a host name address of the AS.
  • the AP entity obtains the address of the AS to which the user belongs, and may also send a service setting message to the AS according to the address of the AS, thereby implementing the service of the user when multiple ASs are deployed at the same time.
  • the setup message can be routed to the correct AS that can handle the service setup message of the user; for example, if the existing network uses the USIM card to carry out the VoLTE service, and the multiple ASs are deployed, the user's service setting message can be
  • the correct AS for example, if the existing network uses the USIM card to carry out the VoLTE service, and the multiple ASs are deployed, the user's service setting message can be
  • the specific implementation process refer to the related description of the AP entity execution process in the method embodiment of the present invention, and details are not described herein again.
  • Embodiment 3 of an AS address obtaining method according to the present invention. As shown in FIG. 4, the method in this embodiment may include:
  • S301 The service issuing device sends a service release message to the HSS.
  • the service sending message includes subscription data of a user using the UE, and the subscription data of the user includes an address of an AS to which the user belongs.
  • the domain name address of the AS As the AS address.
  • the domain name address of the AS to which the user belongs is: xcap.domain.com.
  • the user's subscription data is described using an XML document, and an example of the subscriber's subscription data including the domain name address of the AS is as follows:
  • the UE sends a first service setting message to the BSF entity.
  • the UE when the user of the UE operates the UE to perform service setting, if the AP entity triggers the UE to authenticate the BSF entity, the UE sends a first service setting message to the BSF entity, where the service may be To supplement the business, such as: number display, call restriction, setting forward number, activation, or deactivation.
  • the first service setting message may be a service setting request message or a service setting query message.
  • the BSF entity sends a second request message to the HSS.
  • the BSF entity after receiving the first service setting message sent by the UE, the BSF entity sends a second request message to the HSS according to the first service setting message, where the second request message is used to request a user using the UE. Signing data.
  • the HSS sends the subscription data of the user to the BSF entity.
  • the HSS after receiving the second request message sent by the BSF entity, acquires the subscription data of the user, and then sends the subscription data of the user to the BSF entity.
  • the UE sends a second service setting message to the AP entity.
  • the UE after the UE authenticates the BSF entity, the UE also sends the AP entity to the AP entity. Send a second service setup message.
  • the AP entity sends a first request message to the BSF entity.
  • the AP entity after receiving the second service setting message sent by the UE, the AP entity sends a first request message to the BSF entity according to the second service setting message, where the first request message is used to request to use the UE.
  • User's contract data After receiving the second service setting message sent by the UE, the AP entity sends a first request message to the BSF entity according to the second service setting message, where the first request message is used to request to use the UE.
  • the BSF entity sends the subscription data of the user to the AP entity.
  • the BSF entity after receiving the first request message sent by the AP entity, acquires the subscription data of the user, and then sends the subscription data of the user to the AP entity.
  • the AP entity obtains the address of the AS from the subscription data of the user.
  • the method in this embodiment may further include: the AP entity sending the service setting message to the AS according to the address of the AS, thereby implementing a service setting message of the user in the case that multiple ASs are deployed at the same time.
  • the AP entity sending the service setting message to the AS according to the address of the AS, thereby implementing a service setting message of the user in the case that multiple ASs are deployed at the same time.
  • the BSF entity obtains the subscription data of the user from the HSS when the user performs the service setting
  • the AP entity obtains the subscription data of the user from the BSF entity.
  • the subscription data to the user so that the AP entity can correctly obtain the address of the AS to which the user belongs. Further, the AP entity can correctly address the AS to which the user belongs according to the address of the AS.
  • FIG. 5 is a flowchart of Embodiment 4 of an AS address obtaining method according to the present invention. As shown in FIG. 5, the method in this embodiment may include:
  • S401 A secure transport layer protocol (English: Transport Layer Security, TLS for short) tunnel is established between the UE and the AP entity.
  • English Transport Layer Security, TLS for short
  • the user can select a specified service to be set on the UE, and then the TLS tunnel is established between the UE and the AP entity, that is, TLS handshake.
  • the UE sends a Hypertext Transfer Protocol (English: Hypertext Transfer Protocol, HTTP) GET message to the AP entity.
  • a Hypertext Transfer Protocol English: Hypertext Transfer Protocol, HTTP
  • the UE may initiate a supplementary service read service setup request message (ie, the above HTTP GET) Message)
  • a supplementary service read service setup request message ie, the above HTTP GET
  • the HTTP GET message carries (3GPP-GBA, Host: AP).
  • the AP entity sends an HTTP 401 Unauthorized Response (English: Response) message to the UE.
  • the AP entity After receiving the HTTP GET message sent by the UE, the AP entity sends an HTTP 401 Unauthorized Response message to the UE to request the UE to authenticate the BSF entity.
  • the UE sends an HTTP GET message to the BSF entity.
  • the HTTP GET message sent by the UE to the BSF entity includes the IP Multimedia Private Identity (IMPI) of the user of the UE.
  • IMPI IP Multimedia Private Identity
  • the BSF entity sends a MAR message to the HSS.
  • the BSF entity After receiving the HTTP GET message sent by the UE, the BSF entity sends a MAR message to the HSS, where the MAR message includes the IMPI, and the MAR message is used to obtain the authentication quintuple and the GUSS subscription data of the user.
  • the HSS sends an MAA message to the BSF entity.
  • the HSS After receiving the MAR message sent by the BSF entity, the HSS determines the authentication quintuple of the user and the GUSS subscription data of the user according to the IMPI in the MAR message, and then sends an MAA message to the BSF entity, where the MAA message is sent.
  • the authentication quintuple and the GUSS subscription data are included, and the authentication quintual includes: a random number (English: RAND), an authentication token (English: Authentication Token, abbreviation: AUTN), and an expected response (English: Expected Response) , referred to as: XRES), encryption key (English: Cipher Key, referred to as: CK), integrity key (English: Integrity Key, referred to as: IK), the GUSS subscription data includes the address of the AS to which the user belongs.
  • the BSF entity sends an HTTP 401 unauthentication response message to the UE.
  • the BSF entity After the BSF entity receives the MAA message sent by the HSS, the BSF entity sends an HTTP 401 Unauthorized Response message to the UE to start challenging the UE (mutual authentication with the UE), where the message includes RAND and AUTN in the authentication quintuple. .
  • the UE performs authentication and authentication on the network.
  • the UE After receiving the HTTP 401 Unauthorized Response message sent by the BSF entity, the UE calculates a message authentication code (English: Message Authorized Code, MAC address for short) and a sequence number (SQN for short) according to the AUTN. When the MAC and SQN are valid, the UE generates RES, IK, CK, etc. according to AUTN and RAND.
  • a message authentication code English: Message Authorized Code, MAC address for short
  • SQN sequence number
  • the UE sends an HTTP GET message to the BSF entity.
  • the UE After the UE completes the network authentication, the UE sends an HTTP GET message to the BSF entity, where the message includes the RES generated by the UE.
  • the BSF entity performs authentication authentication on the UE and generates a guiding key.
  • the BSF entity After the BSF entity receives the HTTP GET message sent by the UE again, the BSF entity calculates an XRES. When the XRES is the same as the RES sent by the UE, it indicates that the UE is successfully challenged, and then the BSF entity calculates and generates a guiding event identifier of the UE. (Bootstrapping Transaction Identity, B-TID for short), and record ⁇ B-TID, IMPI, CK, IK>.
  • the BSF entity sends a 200 OK message to the UE.
  • the BSF entity returns a 200 OK message to the UE indicating that the authentication is successful, and the message includes the B-TID and the valid period of the key.
  • the UE sends an HTTP GET message to the AP entity.
  • the UE After receiving the 200 OK message sent by the BSF entity, the UE generates a key Ks_(ext)_NAF, and saves the B-TID and the generated Ks_(ext)_NAF, and then the UE sends an HTTP GET message to the AP entity again.
  • the HTTP GET message includes B-TID and Ks_(ext)_NAF, wherein the username is the B-TID and the password is Ks_(ext)_NAF.
  • the valid period of the key is the effective period of the key Ks_(ext)_NAF.
  • the AP entity sends a BIR message to the BSF entity.
  • the AP entity After the AP entity receives the HTTP GET message sent by the UE, if the AP entity does not include a key value such as Ks_(ext)_NAF, the AP entity requests the BSF entity to obtain a Ks_(ext)_NAF key through the BIR message. The value and the user's GUSS subscription data.
  • the HTTP GET message includes a B-TID.
  • the BSF entity checks the B-TID and generates a corresponding key.
  • the BSF entity After receiving the BIR message sent by the AP entity, the BSF entity searches for a valid ⁇ B-TID, IMPI, CK, IK> information in the BSF entity according to the B-TID, and if so, the BSF entity calculates Get Ks_(ext)_NAF.
  • the BSF entity sends a BIA message to the AP entity.
  • the BSF entity returns the calculated Ks_(ext)_NAF and the user's GUSS subscription data to the AP entity through the BIA message, and the GUSS subscription data includes the address of the AS to which the user belongs.
  • the AP entity obtains an address of the AS from the GUSS subscription data.
  • the AP entity After receiving the BIA message, the AP entity compares whether the user name (B-TID) and the password (Ks_(ext)_NAF) sent by the UE and the BSF entity are the same. If they are the same, the authentication succeeds, and then the authentication succeeds.
  • the AP obtains the address of the AS that processes the service setting of the user from the GUSS subscription data obtained by the BSF entity.
  • the address of the AS may be the IP address of the AS. If the address of the AS is the domain name address of the AS or the host name address of the AS, the AP entity may obtain the domain name address of the AS or the host name address of the AS.
  • the IP address of the AS may be the IP address of the AS.
  • the AP entity sends the HTTP GET message to the AS.
  • the AP entity sends the HTTP GET message sent by the UE to the correct AS according to the IP address of the AS.
  • the AP entity may also modify the HTTP GET message according to its own configuration, for example, adding a user identifier (UID) parameter.
  • UID user identifier
  • the AS processes the service setting.
  • the AS After receiving the HTTP GET message sent by the AP entity, the AS performs service setting.
  • the AS sends a 200 OK message to the AP entity.
  • the AS After the AS completes the service setup, it sends a 200 OK message to the AP entity.
  • the AP entity adds authentication information to the 200 OK message.
  • the AP entity After receiving the 200 OK message sent by the AS, the AP entity adds authentication information (Authentication-Info) to the 200 OK message.
  • authentication-Info authentication information
  • the AP entity sends the 200 OK message to the UE.
  • the AP entity sends the 200 OK message to the UE, indicating that the UE is successfully authenticated. Specifically, the UE checks the "Authentication-Info" in the 200 OK message. If the authentication succeeds, the UE can access the service, and can also perform subsequent service setting processing.
  • the BSF entity obtains the GUSS subscription data of the user from the HSS by using the address of the AS that provides the service setting by the user in the GUSS subscription data of the user.
  • the AP entity obtains the GUSS subscription data of the user from the HSS, and the AP entity obtains the BSF from the BSF.
  • the entity obtains the GUSS subscription data to obtain the address of the AS that provides the service setting for the user, so that the AP entity can correctly forward the service setting message of the UE to the AS that provides the service setting for the user. Therefore, for example, in the case that the existing network uses the USIM card to carry out the VoLTE service, and in the case of multiple AS deployments, the user's service setting message can be routed to the correct AS that can process the service setting message of the user.
  • FIG. 6 is a schematic structural diagram of Embodiment 1 of an AP entity according to the present invention.
  • the AP entity in this embodiment may include: a receiving unit 11 and a sending unit 12, where the receiving unit 11 is configured to Receiving a service setting message sent by the UE; the sending unit 12 is configured to send, according to the service setting message received by the receiving unit 11, a first request message to the BSF entity, where the first request message is used to request a user using the UE
  • the subscription unit 11 is further configured to receive the subscription data of the user sent by the BSF entity, where the subscription data of the user includes an address of an AS to which the user belongs.
  • the address of the AS is any one of the following: an IP address of the AS, a domain name address of the AS, or a host name address of the AS.
  • the AP entity in this embodiment may be used to perform the technical solution of the AP entity in the foregoing method embodiments of the present invention.
  • the implementation principle and technical effects are similar, and details are not described herein again.
  • FIG. 7 is a schematic structural diagram of Embodiment 2 of an AP entity according to the present invention.
  • the AP entity of this embodiment is further configured to include an acquiring unit 13 for When the address of the AS is the domain name address of the AS or the host name address of the AS, the IP address of the AS is obtained according to the domain name address of the AS or the host name address of the AS.
  • the obtaining unit 13 is specifically configured to: according to the domain name address of the AS or the host name address of the AS, and the domain name address of the AS stored in the AP entity or the host name address of the AS Obtaining the IP address of the AS, and obtaining the IP address of the AS according to the domain name address of the AS or the host name address of the AS.
  • the sending unit 12 is further configured to send the service setting message to the AS according to the IP address of the AS.
  • the sending unit 12 is further configured to send the service setting message to the AS according to the address of the AS.
  • the AP entity in this embodiment may be used to perform the technical solution of the AP entity in the foregoing method embodiments of the present invention.
  • the implementation principle and technical effects are similar, and details are not described herein again.
  • FIG. 8 is a schematic structural diagram of Embodiment 1 of a BSF entity according to the present invention.
  • the BSF entity in this embodiment may include: a receiving unit 21 and a sending unit 22, where the receiving unit 21 is configured to receive a service sent by the UE. a sending unit 22, configured to send, according to the service setting message received by the receiving unit 21, a second request message to the HSS, where the second request message is used to request subscription data of a user using the UE; And receiving, by the HSS, the subscription data of the user, where the subscription data of the user includes an address of an AS to which the user belongs, and receiving a first request message sent by the AP entity.
  • the first request message is used to request the subscription data of the user; the sending unit 22 is further configured to send the subscription data of the user to the AP entity according to the first request message received by the receiving unit 21.
  • the address of the AS is any one of the following: an IP address of the AS, a domain name address of the AS, and a host name address of the AS.
  • the BSF entity in this embodiment may be used to perform the technical solution of the BSF entity in the foregoing method embodiment of the present invention, and the implementation principle and the technical effect are similar, and details are not described herein again.
  • FIG. 9 is a schematic structural diagram of Embodiment 3 of an AP entity according to the present invention.
  • the AP entity in this embodiment may include a receiver 31, a transmitter 32, a memory 33, and a receiver 31, a transmitter 32, and a memory, respectively. 33 connected processor 34.
  • the processor 34 can be a general-purpose central processing unit (English: Central Processing Unit, CPU for short), a microprocessor, an application-specific integrated circuit (ASIC), or one or more applications. An integrated circuit that controls the execution of the program of the present invention.
  • CPU Central Processing Unit
  • ASIC application-specific integrated circuit
  • the memory 33 may be a non-volatile memory, a read-only memory (abbreviation: ROM) or other types of static storage devices that can store static information and instructions, and a random access memory ( Abbreviation: random access memory (abbreviation: RAM) or other types of dynamic storage devices that can store information and instructions, or electrically erasable programmable read-only memory (English: Electrically Erasable Programmable Read-Only) Memory, referred to as: EEPROM), CD-ROM (English: Compact Disc Read-Only Memory, CD-ROM) or other CD storage, CD storage (including compact discs, laser discs, CDs, digital versatile discs, Blu-ray discs, etc.) A disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of an instruction or data structure and that can be accessed by a computer, but is not limited thereto.
  • ROM read-only memory
  • RAM random access memory
  • EEPROM electrically erasable programm
  • the memory 33 is used to store program code for executing the AS address obtaining method of the present invention, and the processor 34 is configured to call the program code stored in the memory 33 for performing the following operations:
  • the address of the AS is any one of the following: an IP address of the AS, a domain name address of the AS, and a host name address of the AS.
  • the processor 34 is further configured to receive, by using the receiver 31, the address of the AS sent by the BSF entity. Then, the IP address of the AS is obtained according to the domain name address of the AS or the host name address of the AS.
  • the processor 34 is configured to obtain the IP address of the AS according to the domain name address of the AS or the host name address of the AS, where the processor 34 is configured to: according to the domain name address or the location of the AS Obtaining the host name address of the AS, the domain name address of the AS stored in the AP entity, or the mapping between the host name address of the AS and the IP address of the AS, and obtaining the IP address of the AS; or The DNS is obtained according to the domain name address of the AS or the host name address of the AS, and the IP address of the AS is obtained.
  • each of the at least two IP addresses has different priorities
  • the processor 34 is configured to obtain the IP address of the AS, where the processor 34 is configured to obtain the IP address with the highest priority from the at least two IP addresses corresponding to the domain name address of the AS as the AS. IP address.
  • the processor 34 is further configured to send the device to the device according to the IP address of the AS.
  • the AS sends the service setting message.
  • the processor 34 is further configured to send the service setting message to the AS according to the address of the AS.
  • the BSF entity in this embodiment may include a receiver 41, a transmitter 42, a memory 43, and a receiver 41, a transmitter 42, and a memory, respectively. 43 connected processor 44.
  • Processor 44 may be a general purpose CPU, microprocessor, ASIC, or one or more integrated circuits for controlling the execution of the program of the present invention.
  • the memory 43 can be a non-volatile memory, ROM or other type of static storage device that can store static information and instructions, RAM or other types of dynamic storage devices that can store information and instructions, and can also be EEPROM, CD-ROM or other.
  • the memory 43 is used to store the program code for executing the AS address obtaining method of the present invention, and the processor 44 is configured to call the program code stored in the memory 43 for performing the following operations:
  • the first request message sent by the AP entity by the sender 42 is used to request subscription data of the user;
  • the subscriber's subscription data is sent by the sender 42 to the AP entity.
  • the address of the AS is any one of the following: an IP address of the AS, a domain name address of the AS, and a host name address of the AS.
  • FIG. 11 is a schematic structural diagram of an embodiment of an AS address obtaining system according to the present invention.
  • the system in this embodiment may include: an AP entity 50 and a BSF entity 60.
  • the AP entity 50 may adopt the FIG. 6 or the present invention. 7 or the structure provided by the embodiment shown in FIG. 9 is implemented.
  • the technical solution executed by the AP entity in the foregoing method embodiment of the present invention may be implemented, and the implementation principle and the technical effect are similar.
  • the BSF entity 60 can be implemented by using the structure provided by the embodiment shown in FIG. 8 or FIG.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本发明实施例提供一种应用服务器地址获取方法、设备和系统，此方法包括：AP实体接收用户设备UE发送的业务设置消息；所述AP实体根据所述业务设置消息向BSF实体发送第一请求消息，所述第一请求消息用于请求使用所述UE的用户的签约数据；所述AP实体接收所述BSF实体发送的所述用户的签约数据，所述用户的签约数据包括所述用户归属的AS的地址。从而实现该AP实体可以获取到该用户归属的AS。

Description

应用服务器地址获取方法、设备和系统
本申请要求了2014年12月19日提交的、申请号为201410804320.2、发明名称为“应用服务器地址获取方法、设备和系统”的中国申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本发明实施例涉及通信技术领域，尤其涉及一种应用服务器(英文：Application Server，简称：AS)地址获取方法、设备和系统。
背景技术
随着系统架构演进(英文：System Architecture Evolution，简称：SAE)/长期演进(英文：Long Term Evolution，简称：LTE)网络技术的发展，SAE/LTE网络已经覆盖到一些城区和话务热点地区，导致目前的通信网络中，SAE/LTE网络和2G/3G网络并存。在SAT/LTE网络下，SAE/LTE网络作为一种分组交换系统，语音业务只能在分组交换(英文：Packet Switching，简称：PS)域承载上传输，IMS通过基于IP的网络来控制语音业务，此即为通常所指的VoLTE。但是当用户设备(英文：User Equipment，简称：UE)在2G/3G网络时，语音业务一般承载在电路交换(英文：Circuit Switching，简称：CS)域上，此时CS语音与VoLTE语音是共存的。
在VoLTE网络中，仍然需要继承在2G/3G移动语音网络中给用户提供的补充业务，如号码显示、呼叫限制、前转号码等；尤其需要支持用户能自助设置这些补充业务。在用户主动设置补充业务时，UE发送补充业务设置请求给鉴权认证代理(英文：Authentication Proxy，简称：AP)；AP挑战UE，让UE去引导服务器功能(英文：Bootstrapping Server Function，简称：BSF)做鉴权；UE到BSF鉴权通过后，UE重新发送补充业务设置请求给AP，并携带BSF鉴权通过的信息；AP联系BSF确认用户鉴权通过后，AP发送该补充业务设置请求给AS，从而补充业务设置成功。
而且，现有的通信运营商在部署VoLTE时发放给用户使用的仍然是全球用户识别卡(英文：Universal Subscriber Identity Module，简称：USIM)。 在这种场景下，UE是按照如下方式推导出AP的统一资源定位符(英文：Uniform Resource Identifier，简称：URI)的：UE取USIM中国际移动用户识别码(英文：International Mobile Subscriber Identification Number，简称：IMSI)中的移动网络号码(英文：Mobile Network Code，简称：MNC)和移动信号国家码(英文：Mobile Country Code，简称：MCC)，组装成“xcap.mnc<MNC>.mcc<MCC>.pub.3gppnetwork.org”作为XCAP server URI，并将该URI携带在补充业务设置请求中发送给AP，再由AP根据该URI将补充业务设置请求发送给对应的AS。
然而，属于同一个移动网络(中国移动或者中国联通或者中国电信)中的各USIM的MNC和MCC是相同的，因此对于不同省份/区域的USIM，UE推导出来的XCAP服务器地址是一模一样的，这样AP就无法获取到该USIM归属的AS的地址，导致无法正确寻址到该USIM归属的AS。
发明内容
本发明实施例提供一种应用服务器地址获取方法、设备和系统，用于实现AP实体获取UE的用户归属的AS的地址。
第一方面，本发明实施例提供一种AS地址获取方法，包括：
AP实体接收UE发送的业务设置消息；
所述AP实体根据所述业务设置消息向引导服务器功能BSF实体发送第一请求消息，所述第一请求消息用于请求使用所述UE的用户的签约数据；
所述AP实体接收所述BSF实体发送的所述用户的签约数据，其中，所述用户的签约数据包括所述用户归属的AS的地址。
在第一方面的第一种可能的实现方式中，所述AS的地址为以下任意一种：所述AS的IP地址，所述AS的域名地址，和所述AS的主机名地址。
结合第一方面或第一方面的第一种可能的实现方式，在第一方面的第二种可能的实现方式中，当所述AS的地址为所述AS的域名地址或者所述AS的主机名地址时，所述AP实体接收所述BSF实体发送的所述AS的地址之后，还包括：
所述AP实体根据所述AS的域名地址或者所述AS的主机名地址，获取所述AS的IP地址。
结合第一方面的第二种可能的实现方式，在第一方面的第三种可能的实现方式中，所述AP实体根据所述AS的域名地址或者所述AS的主机名地址，获取所述AS的IP地址，包括：
所述AP实体根据所述AS的域名地址或者所述AS的主机名地址，以及所述AP实体中存储的所述AS的域名地址或者所述AS的主机名地址与所述AS的IP地址的对应关系，获取所述AS的IP地址；或者，
所述AP实体根据所述AS的域名地址或者所述AS的主机名地址查询域名解析系统DNS，获取所述AS的IP地址。
结合第一方面的第二种可能的实现方式或第一方面的第三种可能的实现方式，在第一方面的第四种可能的实现方式中，当所述AS的域名地址与至少两个IP地址对应时，所述至少两个IP地址中各个IP地址具有不同的优先级；
所述AP实体获取所述AS的IP地址，包括：
所述AP实体从所述AS的域名地址所对应的所述至少两个IP地址中获取优先级最高的IP地址作为所述AS的IP地址。
结合第一方面的第一种至第四种可能的实现方式中的任意一种，在第一方面的第五种可能的实现方式中，还包括：
所述AP实体根据所述AS的IP地址，向所述AS发送所述业务设置消息。
在第一方面的第六种可能的实现方式中，还包括：
所述AP实体根据所述AS的地址，向所述AS发送所述业务设置消息。
第二方面，本发明实施例提供一种AS地址获取方法，包括：
BSF实体接收UE发送的业务设置消息；
所述BSF实体根据所述业务设置消息，向HSS发送第二请求消息，所述第二请求消息用于请求使用所述UE的用户的签约数据；
所述BSF实体接收所述HSS发送的所述用户的签约数据，其中，所述用户的签约数据包括所述用户归属的AS的地址；
所述BSF实体接收所述AP实体发送的第一请求消息，所述第一请求消息用于请求所述用户的签约数据；
所述BSF实体根据所述第一请求消息，向所述AP实体发送所述用户的 签约数据。
第三方面，本发明实施例提供一种AP实体，包括：
接收单元，用于接收UE发送的业务设置消息；
发送单元，用于根据所述接收单元接收的所述业务设置消息向BSF实体发送第一请求消息，所述第一请求消息用于请求使用所述UE的用户的签约数据；
所述接收单元，还用于接收所述BSF实体发送的所述用户的签约数据，其中，所述用户的签约数据包括所述用户归属的AS的地址。
第四方面，本发明实施例提供一种BSF实体，包括：
接收单元，用于接收UE发送的业务设置消息；
发送单元，用于根据所述接收单元接收的所述业务设置消息，向HSS发送第二请求消息，所述第二请求消息用于请求使用所述UE的用户的签约数据；
所述接收单元，还用于接收所述HSS发送的所述用户的签约数据，其中，所述用户的签约数据包括所述用户归属的AS的地址；以及接收所述AP实体发送的第一请求消息，所述第一请求消息用于请求所述用户的签约数据；
所述发送单元，还用于根据所述接收单元接收的所述第一请求消息，向所述AP实体发送所述用户的签约数据。
第五方面，本发明实施例提供一种AS地址获取系统，包括：本发明实施例第三方面提供的AP实体、本发明实施例第四方面提供的BSF实体。
本发明实施例提供的AS地址获取方法、设备和系统，通过AP实体接收UE发送的业务设置消息，然后根据该业务设置消息，向BSF实体发送第一请求消息，再接收该BSF实体发送的包括用户归属的AS的地址的该用户的签约数据，从而实现该AP实体可以正确获取到该用户归属的该AS的地址。
附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案，下面将对实施例或现有技术描述中所需要使用的附图作一简单地介绍，显而易见地，下面描述中的附图是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1为本发明AS地址获取方法的一种应用网络架构图；
图2为本发明AS地址获取方法实施例一的流程图；
图3为本发明AS地址获取方法实施例二的流程图；
图4为本发明AS地址获取方法实施例三的流程图；
图5为本发明AS地址获取方法实施例四的流程图；
图6为本发明AP实体实施例一的结构示意图；
图7为本发明AP实体实施例二的结构示意图；
图8为本发明BSF实体实施例一的结构示意图；
图9为本发明AP实体实施例三的结构示意图；
图10为本发明BSF实体实施例二的结构示意图；
图11为本发明AS地址获取系统实施例的结构示意图。
具体实施方式
为使本发明实施例的目的、技术方案和优点更加清楚，下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本发明一部分实施例，而不是全部的实施例。基于本发明中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本发明保护的范围。
图1为本发明AS地址获取方法的一种应用网络架构图，如图1所示，本发明各实施例提供的AS地址获取方法例如可以应用于VoLTE网络下，3GPP标准协议引入了UE与AS之间的Ut接口，UE与AS通过Ut接口进行通信，以便设置业务。为了完成Ut接口的鉴权，在3GPP标准协议中又定义了通用认证架构(Generic Authentication Architecture，简称：GAA)鉴权架构，GAA鉴权架构的引入，在VoLTE网络中新增了两个逻辑功能实体，分别为BSF实体与AP实体。BSF实体与HSS之间通过Zh接口进行通信，BSF实体与AP实体之间通过Zn接口进行通信，BSF实体与UE之间通过Ub接口进行通信，BSF实体通过与UE、HSS的交互，完成UE合法性认证，并生成UE侧和网络侧的共享访问密钥；AP实体是业务访问认证代理，AP实体与UE之间通过Ua接口进行通信，AP实体对于该UE初次业务访问，会先触发到BSF实体的引导(英文：bootstrapping)，然后基于BSF实体和UE 间生成的共享访问密钥来完成用户业务访问认证；AP实体作为一个反向代理，对于UE来说是作为AS，而对于AS来说是作为UE。其中，该AP实体例如以为实现AP功能的网络应用功能(英文：Network Application Function，简称：NAF)实体。图1所示的网络架构是本发明AS地址获取方法的应用网络的一种示例，但本发明并不限于此。
图2为本发明AS地址获取方法实施例一的流程图，如图2所示，本实施例的方法可以包括：
S101、AP实体接收UE发送的业务设置消息。
本实施例中，当该UE的用户需要进行业务设置时，该用户可以对该UE的界面进行操作，使得该UE向该AP实体发送业务设置消息，其中，该业务可以为补充业务，例如：号码显示、呼叫限制、设置前转号码、激活、或去激活等。该业务设置消息可以为业务设置请求消息或者业务设置查询消息。
S102、所述AP实体根据所述业务设置消息向BSF实体发送第一请求消息，所述第一请求消息用于请求使用所述UE的用户的签约数据。
本实施例中，该AP实体接收到该UE发送的业务设置消息后，该AP实体根据该业务设置消息向BSF实体发送第一请求消息，用于向该BSF实体请求获取使用该UE的用户的签约数据。
S103、所述AP实体接收所述BSF实体发送的所述用户的签约数据，其中，所述用户的签约数据包括所述用户归属的AS的地址。
本实施例中，该BSF实体接收到该AP实体发送的第一请求消息后，根据该第一请求消息确定该用户的签约数据，然后将该用户的签约数据发送给AP实体，该用户的签约数据包括该用户归属的AS的地址，进而AP实体从该用户的签约数据中获取该用户归属的AS的地址。例如BSF实体可以将该用户的签约数据携带在与该第一请求消息对应的响应消息中发送给AP实体。其中，该用户的签约数据为该用户的通用引导架构用户安全性设置(英文：Generic Bootstrapping Architecture User Security Settings，简称：GUSS)，该用户归属的AS即为该用户提供业务设置功能的AS，例如该UE中的USIM卡是在北京开户的，则说明该UE的用户归属地为北京，该用户归属的AS则为归属地为北京的AS。
可选地，该第一请求消息为引导信息请求(英文：Bootstrapping Information  Request，简称：BIR)消息；与该第一请求消息对应的响应消息为引导信息响应(英文：Bootstrapping Information Answer，简称：BIA)消息。
本实施例中，通过AP实体接收UE发送的业务设置消息，然后根据该业务设置消息，向BSF实体发送用于请求使用该UE的用户的签约数据第一请求消息，再接收该BSF实体发送的包括该用户的归属的AS的地址的该用户的签约数据，从而该AP实体可以正确获取到该用户归属的AS的地址，进一步地，该AP实体可以根据该AS的地址正确寻址到该用户所属的AS。
可选地，所述AS的地址可以为以下任意一种：所述AS的互联网协议(英文：Internet Protocol，简称：IP)地址，所述AS的域名地址，所述AS的主机名地址。其中，IP地址例如为：192.168.1.1，域名地址例如为：as.chinamobile.com，主机名地址例如为：as01.chinamobile.com。
可选地，该AP实体接收该BSF实体发送的该用户的签约数据之后，还包括：该AP实体根据该AS的地址，向该AS发送该业务设置消息。从而实现了在同时有多个AS部署的情况下，用户的业务设置消息能被路由到正确的能处理该用户的业务设置消息的AS。例如实现了现有网络在使用USIM卡开展VoLTE业务，同时有多个AS部署的情况下，用户的业务设置消息能被路由到正确的能处理该用户的业务设置消息的AS。
其中，该AP实体根据该AS的地址向该AS发送该业务设置消息的具体实现过程如下所述。
在第一种可行的实现方式中，当该AS的地址为该AS的IP地址，该AP实体根据该AS的IP地址向该AS发送该业务设置消息。
在第二种可行的实现方式中，该AS的地址为该AS的域名地址，该AP实体可以根据该AS的域名地址，获取该AS的IP地址；然后根据该AS的IP地址，向该AS发送该业务设置消息。具体地，该AP实体可以根据该AS的域名地址，获取该AS的IP地址，包括：所述AP实体根据所述AS的域名地址，以及所述AP实体中存储的所述AS的域名地址与所述AS的IP地址的对应关系，获取所述AS的IP地址；或者，所述AP实体根据所述AS的域名地址查询域名解析系统(英文：Domain Name System，简称：DNS)，获取所述AS的IP地址。
可选的，当所述AS的域名地址与至少两个IP地址对应时(即该AS的 域名地址对应至少两个AS)，所述至少两个IP地址中各个IP地址具有不同的优先级；
所述AP实体获取所述AS的IP地址，包括：所述AP实体从所述AS的域名地址所对应的所述至少两个IP地址中获取优先级最高的IP地址作为所述AS的IP地址。
若该至少两个IP地址中存在多个IP地址具有相同的优先级，并且该优先级最高，那么该AP实体可以选取其中一个正常运行的AS的IP地址。
在第三种可行的实现方式中，该AS的地址为该AS的主机名地址，该AP实体可以根据该AS的主机名地址，获取该AS的IP地址；然后根据该AS的IP地址，向该AS发送该业务设置消息。具体地，该AP实体可以根据该AS的主机名地址，获取该AS的IP地址，包括：所述AP实体根据所述AS的主机名地址，以及所述AP实体中存储的所述AS的主机名地址与所述AS的IP地址的对应关系，获取所述AS的IP地址；或者，所述AP实体根据所述AS的主机名地址查询域名解析系统(英文：Domain Name System，简称：DNS)，获取所述AS的IP地址。
通过上述各实现方式AP实体可以根据用户归属的AS的地址将该用户的UE发送的业务设置消息正确传输至该UE归属的AS中。
图3为本发明AS地址获取方法实施例一的流程图，如图3所示，本实施例的方法可以包括：
S201、BSF实体接收UE发送的业务设置消息。
本实施例中，该UE的用户操作该UE进行业务设置时，若AP实体触发该UE向BSF实体进行鉴权，则该UE向该BSF实体发送业务设置消息，其中，该业务可以为补充业务，例如：号码显示、呼叫限制、设置前转号码、激活、或去激活等。该业务设置消息可以为业务设置请求消息或者业务设置查询消息。
S202、所述BSF实体根据所述业务设置消息，向HSS发送第二请求消息，所述第二请求消息用于请求使用所述UE的用户的签约数据。
本实施例中，该BSF实体接收到该UE发送的业务设置消息之后，该BSF实体向HSS发送第二请求消息，用于向该HSS请求获取使用该UE的用户的签约数据。
S203、所述BSF实体接收所述HSS发送的所述用户的签约数据，其中，所述用户的签约数据包括所述用户归属的AS的地址。
本实施例中，该HSS接收到该BSF实体发送的第二请求消息之后，根据该第二请求消息可以获取该用户的签约数据，其中，该用户的签约数据为该用户的GUSS签约数据，该用户的签约数据包括用户归属的AS的地址，然后向该BSF实体发送携带该AS的地址的该用户的签约数据。例如：HSS可以将该用户的签约数据携带在与第二请求消息对应的响应消息中发送给该BSF实体，BSF实体从该响应消息中获取该用户的签约数据。
可选地，该第二请求消息可以为多媒体鉴权请求(英文：Multimedia Authentication Request，简称：MAR)消息；与该第二请求消息对应的响应消息为多媒体鉴权响应(英文：Multimedia Authentication Answer，简称：MAA)消息。
可选的，HSS在向BSF发送用户的签约数据之前，HSS接收业务分发设备发送的业务发放消息，该业务发送消息包括该AS的地址。例如：在该用户进行该UE中的USIM卡的开卡操作时，该业务发放设备会向该HSS发送包括该用户的签约数据的业务发送消息。
S204、所述BSF实体接收所述AP实体发送的第一请求消息，所述第一请求消息用于请求所述用户的签约数据。
本实施例中，该BSF实体会接收到该AP实体发送的第一请求消息，从第一请求消息中获知该AP实体要请求获取该用户的签约数据。
S205、所述BSF实体根据所述第一请求消息，向所述AP实体发送所述用户的签约数据。
本实施例中，该BSF实体根据该第一请求消息将HSS发送的该用户的签约数据发送给AP实体，该AP实体从BSF实体发送的该用户的签约数据中获取该用户归属的AS的地址；例如：BSF实体可以将该用户的签约数据携带在与第一请求消息对应的响应消息中发送给该AP实体，AP实体从该响应消息中获取该用户的签约数据。
本实施例中，通过BSF实体接收UE发送的业务设置消息，然后根据所述业务设置消息，向HSS发送用于请求使用所述UE的用户的签约数据的第二请求消息，从而接收所述HSS发送的包括该用户归属的AS的地址的该用 户的签约数据，然后接收所述AP实体发送的用于请求所述用户的签约数据的第一请求消息，再根据所述第一请求消息，向所述AP实体发送包括该AS的地址的该用户的签约数据；从而实现该AP实体可以正确获取到该用户归属的该AS的地址，进一步地，该AP实体可以根据该AS的地址正确寻址到该用户所属的AS。
可选地，所述AS的地址可以为以下任意一种：所述AS的IP地址，所述AS的域名地址，所述AS的主机名地址。可选地，该AP实体获取到该用户归属的该AS的地址，还可以根据该AS的地址向该AS发送业务设置消息，从而实现了在同时有多个AS部署的情况下，用户的业务设置消息能被路由到正确的能处理该用户的业务设置消息的AS；例如实现了现有网络在使用USIM卡开展VoLTE业务，同时有多个AS部署的情况下，用户的业务设置消息能被路由到正确的能处理该用户的业务设置消息的AS；其具体实现过程可以参见本发明方法实施例一中AP实体执行过程的相关记载，此处不再赘述。
图4为本发明AS地址获取方法实施例三的流程图，如图4所示，本实施例的方法可以包括：
S301、业务发放设备会向HSS发送业务发放消息；
本实施例中，该业务发送消息包括使用UE的用户的签约数据，该用户的签约数据包括该用户归属的AS的地址。
下面以AS的地址为AS的域名地址进行说明，例如该用户归属的AS的域名地址为：xcap.domain.com。用户的签约数据使用XML文档描述，包括该AS的域名地址的用户的签约数据的例子如下：
Figure PCTCN2015095998-appb-000001
Figure PCTCN2015095998-appb-000002
S302、UE向BSF实体发送第一业务设置消息。
本实施例中，使用该UE的用户操作该UE进行业务设置时，若AP实体触发该UE向BSF实体进行鉴权，则该UE向该BSF实体发送第一业务设置消息，其中，该业务可以为补充业务，例如：号码显示、呼叫限制、设置前转号码、激活、或去激活等。该第一业务设置消息可以为业务设置请求消息或者业务设置查询消息。
S303、该BSF实体向该HSS发送第二请求消息。
本实施例中，该BSF实体接收到该UE发送的第一业务设置消息之后，根据该第一业务设置消息向该HSS发送第二请求消息，该第二请求消息用于请求使用该UE的用户的签约数据。
S304、该HSS向BSF实体发送用户的签约数据。
本实施例中，该HSS接收到该BSF实体发送的第二请求消息之后，获取该用户的签约数据，然后将该用户的签约数据发送给BSF实体。
S305、该UE向AP实体发送第二业务设置消息。
本实施例中，在UE向BSF实体鉴权完成后，该UE还会向该AP实体 发送第二业务设置消息。
S306、该AP实体向该BSF实体发送第一请求消息。
本实施例中，该AP实体接收到该UE发送的第二业务设置消息后，根据该第二业务设置消息向该BSF实体发送第一请求消息，该第一请求消息用于请求使用该UE的用户的签约数据。
S307、该BSF实体向该AP实体发送该用户的签约数据。
本实施例中，该BSF实体接收到该AP实体发送的第一请求消息之后，获取该用户的签约数据，然后将该用户的签约数据发送给该AP实体。该AP实体从该用户的签约数据中获取该AS的地址。
可选地，本实施例的方法还可以包括：该AP实体根据该AS的地址，向该AS发送该业务设置消息，从而实现了在同时有多个AS部署的情况下，用户的业务设置消息能被路由到正确的能处理该用户的业务设置消息的AS；例如实现了现有网络在使用USIM卡开展VoLTE业务，同时有多个AS部署的情况下，用户的业务设置消息能被路由到正确的能处理该用户的业务设置消息的AS。其具体实现过程可以参见本发明方法实施例一中AP实体执行过程中的相关记载，此处不再赘述。
本实施例中，通过在用户的签约数据中额外签约为用户提供业务设置的AS的地址，在用户进行业务设置时，BSF实体从HSS获取到该用户的签约数据，AP实体从该BSF实体获取到该用户的签约数据，从而实现该AP实体可以正确获取到为该用户归属的AS的地址，进一步地，该AP实体可以根据该AS的地址正确寻址到该用户所属的AS。
图5为本发明AS地址获取方法实施例四的流程图，如图5所示，本实施例的方法可以包括：
S401、UE与AP实体之间建立安全传输层协议(英文：Transport Layer Security，简称：TLS)隧道。
当用户需要进行业务设置时，该用户可以在UE上选择指定业务进行设置，然后该UE与该AP实体之间建立TLS隧道，即TLS handshake。
S402、该UE向该AP实体发送超文本传送协议(英文：Hypertext transfer protocol，简称：HTTP)GET消息。
该UE可以发起补充业务读取业务设置请求消息(即上述的HTTP GET 消息)到该AP实体，该HTTP GET消息携带(3GPP-GBA,Host:AP)。
S403、该AP实体向该UE发送HTTP 401未鉴权(英文：Unauthorized)响应(英文：Response)消息。
该AP实体接收到该UE发送的HTTP GET消息后，向该UE发送HTTP401Unauthorized Response消息给该UE要求该UE向BSF实体鉴权。
S404、该UE向BSF实体发送HTTP GET消息。
该UE发送给BSF实体的HTTP GET消息中包括该UE的用户的IP多媒体私有标识(英文：IP Multimedia Private Identity，简称：IMPI)。
S405、该BSF实体向HSS发送MAR消息。
该BSF实体接收到该UE发送的HTTP GET消息后，向HSS发送MAR消息，该MAR消息包括该IMPI，该MAR消息用于获取鉴权五元组以及该用户的GUSS签约数据。
S406、该HSS向该BSF实体发送MAA消息。
该HSS接收到该BSF实体发送的MAR消息后，根据该MAR消息中的IMPI确定该用户的鉴权五元组以及该用户的GUSS签约数据，然后向该BSF实体发送MAA消息，该MAA消息中包括该鉴权五元组和该GUSS签约数据，该鉴权五元组包括：随机数(英文：RAND)、认证令牌(英文：Authentication Token，简称：AUTN)、期望响应(英文：Expected Response，简称：XRES)、加密密钥(英文：Cipher Key，简称：CK)、完整性密钥(英文：Integrity Key，简称：IK)，该GUSS签约数据包括该用户归属的AS的地址。
S407、该BSF实体向该UE发送HTTP 401未鉴权响应消息。
该BSF实体接收到该HSS发送的MAA消息之后，该BSF实体向该UE发送HTTP 401Unauthorized Response消息开始挑战该UE(与该UE互相验证)，该消息中包括鉴权五元组中的RAND和AUTN。
S408、该UE对网络进行鉴权认证。
该UE接收到该BSF实体发送的HTTP 401Unauthorized Response消息后，根据该AUTN计算消息鉴权码(英文：Message Authorized Code，简称：MAC)和序列号(英文：Sequence Number，简称：SQN)。当该MAC和SQN有效时，该UE根据AUTN和RAND生成RES、IK、CK等。
S409、该UE向该BSF实体发送HTTP GET消息。
在该UE完成网络鉴权认证后，该UE再次向该BSF实体发送HTTP GET消息，该消息中包括该UE生成的RES。
S410、该BSF实体对该UE进行鉴权认证并生成引导密钥。
该BSF实体接收到该UE再次发送的HTTP GET消息之后，该BSF实体计算XRES，当该XRES与该UE发送的RES相同时，说明挑战UE成功，然后该BSF实体计算生成该UE的引导事物标识(Bootstrapping Transaction Identity，简称：B-TID)，并记录<B-TID，IMPI，CK，IK>。
S411、该BSF实体向该UE发送200OK消息。
BSF实体返回200OK消息给该UE表明鉴权成功，该消息中包括该B-TID以及密钥的有效周期。
S412、该UE向该AP实体发送HTTP GET消息。
该UE接收到该BSF实体发送的200OK消息后，该UE生成密钥Ks_(ext)_NAF，并保存该B-TID和生成的Ks_(ext)_NAF，然后该UE再次发送HTTP GET消息给AP实体请求访问业务设置，该HTTP GET消息包括B-TID和Ks_(ext)_NAF，其中，用户名为该B-TID，密码为Ks_(ext)_NAF。密钥的有效周期即为密钥Ks_(ext)_NAF的有效周期。
S413、该AP实体向BSF实体发送BIR消息。
该AP实体接收到该UE发送的HTTP GET消息之后，若该AP实体中没有包括Ks_(ext)_NAF等键值，则该AP实体通过BIR消息向该BSF实体请求获取Ks_(ext)_NAF等键值以及该用户的GUSS签约数据。该HTTP GET消息中包括B-TID。
S414、该BSF实体检查B-TID并生成对应的密钥。
该BSF实体接收到该AP实体发送的BIR消息后，根据该B-TID查找该BSF实体中是否存在有效的<B-TID，IMPI，CK，IK>等信息，若有，则该BSF实体计算获得Ks_(ext)_NAF。
S415、该BSF实体向该AP实体发送BIA消息。
该BSF实体将计算出来的Ks_(ext)_NAF以及该用户的GUSS签约数据一起通过BIA消息返回给AP实体，该GUSS签约数据包括该用户归属的AS的地址。
S416、该AP实体从该GUSS签约数据中获取该AS的地址。
该AP实体接收到该BIA消息后，比较该UE送过来和该BSF实体返回的用户名(B-TID)和密码(Ks_(ext)_NAF)是否相同，若相同，则说明鉴权成功，然后该AP从BSF实体中获取到的GUSS签约数据中获取处理该用户的业务设置的AS的地址。该AS的地址可以为该AS的IP地址；若该AS的地址为该AS的域名地址或者该AS的主机名地址，该AP实体还可以根据该AS的域名地址或者该AS的主机名地址获取该AS的IP地址。
S417、该AP实体向该AS发送该HTTP GET消息。
该AP实体根据该AS的IP地址，将该UE发送的该HTTP GET消息发送给正确的AS。可选地，该AP实体还可以根据自身配置来修改该HTTP GET消息，例如：增加用户标识(UID)参数。
S418、该AS处理业务设置。
该AS收到该AP实体发送的该HTTP GET消息后，执行业务设置。
S419、该AS向该AP实体发送200OK消息。
该AS完成业务设置后，向该AP实体发送200OK消息。
S420、该AP实体在该200OK消息中增加鉴权信息。
该AP实体接收到该AS发送的200OK消息之后，在该200OK消息中增加鉴权信息(Authentication-Info)。
S421、该AP实体向该UE发送该200OK消息。
该AP实体将该200OK消息发送给该UE，指示该UE鉴权成功。具体地，该UE检查该200OK消息中的“Authentication-Info”，如果鉴权成功，UE可以访问该业务，并且还可以进行后续的业务设置处理。
本实施例中，通过在用户的GUSS签约数据中额外签约为用户提供业务设置的AS的地址，在用户进行业务设置时，BSF实体从HSS获取到该用户的GUSS签约数据，AP实体从该BSF实体获取到该GUSS签约数据从而获得为用户提供业务设置的AS的地址，使得AP实体能将UE的业务设置消息正确的转送到给该用户提供业务设置的AS。从而实现了例如现有网络在使用USIM卡开展VoLTE业务，同时有多个AS部署的情况下，用户的业务设置消息能被路由到正确的能处理该用户的业务设置消息的AS。
图6为本发明AP实体实施例一的结构示意图，如图6所示，本实施例的AP实体可以包括：接收单元11、发送单元12；其中，接收单元11，用于 接收UE发送的业务设置消息；发送单元12，用于根据接收单元11接收的所述业务设置消息向BSF实体发送第一请求消息，所述第一请求消息用于请求使用所述UE的用户的签约数据；接收单元11，还用于接收所述BSF实体发送的所述用户的签约数据，其中，所述用户的签约数据包括所述用户归属的AS的地址。
可选地，所述AS的地址为以下任意一种：所述AS的IP地址，所述AS的域名地址或，所述AS的主机名地址。
上述各单元之间的交互流程具体可以参考本发明方法实施例中的描述，这里不再赘述。
本实施例的AP实体，可以用于执行本发明上述各方法实施例中AP实体执行的技术方案，其实现原理和技术效果类似，此处不再赘述。
图7为本发明AP实体实施例二的结构示意图，如图7所示，本实施例的AP实体在图6所示装置结构的基础上，进一步地，还可以包括：获取单元13，用于当所述AS的地址为所述AS的域名地址或者所述AS的主机名地址时，根据所述AS的域名地址或者所述AS的主机名地址，获取所述AS的IP地址。
可选地，获取单元13具体用于，根据所述AS的域名地址或者所述AS的主机名地址，以及所述AP实体中存储的所述AS的域名地址或者所述AS的主机名地址与所述AS的IP地址的对应关系，获取所述AS的IP地址；或者，根据所述AS的域名地址或者所述AS的主机名地址查询DNS，获取所述AS的IP地址。
可选地，当所述AS的域名地址与至少两个IP地址对应时，所述至少两个IP地址中各个IP地址具有不同的优先级；获取单元13用于获取所述AS的IP地址，包括：获取单元13用于从所述AS的域名地址所对应的所述至少两个IP地址中获取优先级最高的IP地址作为所述AS的IP地址。
可选地，发送单元12，还用于根据所述AS的IP地址，向所述AS发送所述业务设置消息。
可选地，发送单元12，还用于根据所述AS的地址，向所述AS发送所述业务设置消息。
上述各单元之间的交互流程具体可以参考本发明方法实施例中的描述， 这里不再赘述。
本实施例的AP实体，可以用于执行本发明上述各方法实施例中AP实体执行的技术方案，其实现原理和技术效果类似，此处不再赘述。
图8为本发明BSF实体实施例一的结构示意图，如图8所示，本实施例的BSF实体可以包括：接收单元21和发送单元22；其中，接收单元21，用于接收UE发送的业务设置消息；发送单元22，用于根据接收单元21接收的所述业务设置消息，向HSS发送第二请求消息，所述第二请求消息用于请求使用所述UE的用户的签约数据；接收单元21，还用于接收所述HSS发送的所述用户的签约数据，其中，所述用户的签约数据包括所述用户归属的AS的地址；以及接收所述AP实体发送的第一请求消息，所述第一请求消息用于请求所述用户的签约数据；发送单元22，还用于根据接收单元21接收的所述第一请求消息，向所述AP实体发送所述用户的签约数据。
可选地，所述AS的地址为以下任意一种：所述AS的、IP地址，所述AS的域名地址，所述AS的主机名地址。
上述各单元之间的交互流程具体可以参考本发明方法实施例二中的描述，这里不再赘述。
本实施例的BSF实体可以用于执行本发明上述方法实施例中BSF实体执行的技术方案，其实现原理和技术效果类似，此处不再赘述。
图9为本发明AP实体实施例三的结构示意图，如图9所示，本实施例的AP实体可以包括接收器31、发送器32、存储器33以及分别与接收器31、发送器32、存储器33连接的处理器34。
处理器34可以是一个通用中央处理器(英文：Central Processing Unit，简称：CPU)，微处理器，特定应用集成电路(英文：application-specific integrated circuit，简称：ASIC)，或一个或多个用于控制本发明方案程序执行的集成电路。
存储器33可以是非易失性存储器(Non-volatile Memory)，只读存储器(简称：read-only memory，简称：ROM)或可存储静态信息和指令的其他类型的静态存储设备，随机存取存储器(简称：random access memory，简称：RAM)或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器(英文：Electrically Erasable Programmable Read-Only  Memory，简称：EEPROM)、只读光盘(英文：Compact Disc Read-Only Memory，简称：CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。
其中，存储器33用于存储执行本发明AS地址获取方法的程序代码，处理器34用于调用存储器33中存储的程序代码，用于执行如下操作：
通过接收器31接收UE发送的业务设置消息；
根据所述业务设置消息，通过发送器32向BSF实体发送第一请求消息，所述第一请求消息用于请求使用所述UE的用户的签约数据；
通过接收器31接收所述BSF实体发送的所述用户的签约数据，其中，所述用户的签约数据包括所述用户归属的AS的地址。
可选地，所述AS的地址为以下任意一种：所述AS的IP地址，所述AS的域名地址，和所述AS的主机名地址。
可选地，当所述AS的地址为所述AS的域名地址或者所述AS的主机名地址时，处理器34还用于在通过接收器31接收所述BSF实体发送的所述AS的地址之后，根据所述AS的域名地址或者所述AS的主机名地址，获取所述AS的IP地址。
可选地，处理器34用于根据所述AS的域名地址或者所述AS的主机名地址，获取所述AS的IP地址，包括：处理器34用于，根据所述AS的域名地址或者所述AS的主机名地址，以及所述AP实体中存储的所述AS的域名地址或者所述AS的主机名地址与所述AS的IP地址的对应关系，获取所述AS的IP地址；或者，根据所述AS的域名地址或者所述AS的主机名地址查询DNS，获取所述AS的IP地址。
可选地，当所述AS的域名地址与至少两个IP地址对应时，所述至少两个IP地址中各个IP地址具有不同的优先级；
处理器34用于获取所述AS的IP地址，包括：处理器34用于从所述AS的域名地址所对应的所述至少两个IP地址中获取优先级最高的IP地址作为所述AS的IP地址。
可选地，处理器34还用于根据所述AS的IP地址，通过发送器32向所 述AS发送所述业务设置消息。
可选地，处理器34还用于根据所述AS的地址，向所述AS发送所述业务设置消息。
需要说明的是，处理器34通过调用存储器33中存储的程序代码具体实现的技术方案可以参见本发明上述各方法实施例中AP实体执行的技术方案，其实现原理和技术效果类似，在此不再赘述。
图10为本发明BSF实体实施例二的结构示意图，如图10所示，本实施例的BSF实体可以包括接收器41、发送器42、存储器43以及分别与接收器41、发送器42、存储器43连接的处理器44。
处理器44可以是一个通用CPU，微处理器，ASIC，或一个或多个用于控制本发明方案程序执行的集成电路。
存储器43可以是非易失性存储器，ROM或可存储静态信息和指令的其他类型的静态存储设备，RAM或者可存储信息和指令的其他类型的动态存储设备，也可以是EEPROM、CD-ROM或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。
其中，存储器43用于存储执行本发明AS地址获取方法的程序代码，处理器44用于调用存储器43中存储的程序代码，用于执行如下操作：。
通过接收器41接收UE发送的业务设置消息；
根据所述业务设置消息，通过发送器42向HSS发送第二请求消息，所述第二请求消息用于请求使用所述UE的用户的签约数据；
通过接收器41接收所述HSS发送的所述用户的签约数据，其中，所述用户的签约数据包括所述用户归属的AS的地址；
通过发送器42所述AP实体发送的第一请求消息，所述第一请求消息用于请求所述用户的签约数据；
根据所述第一请求消息，通过发送器42向所述AP实体发送所述用户的签约数据。
可选地，所述AS的地址为以下任意一种：所述AS的IP地址，所述AS的域名地址，所述AS的主机名地址。
需要说明的是，处理器44通过调用存储器43中存储的程序代码具体实现的技术方案可以参见本发明上述各方法实施例中BSF实体执行的技术方案，其实现原理和技术效果类似，在此不再赘述。
图11为本发明AS地址获取系统实施例的结构示意图，如图11所示，本实施例的系统可以包括：AP实体50和BSF实体60；其中，AP实体50可以采用本发明图6或图7或图9所示实施例提供的结构来实现，其对应地，可以执行本发明上述方法实施例中的AP实体所执行的技术方案，其实现原理和技术效果类似，详细可以参见上述实施例中的记载，此处不再赘述。BSF实体60可以采用本发明图8或图10所示实施例提供的结构来实现，其对应地，可以执行本发明上述方法实施例中的BSF实体所执行的技术方案，其实现原理和技术效果类似，详细可以参见上述实施例中的记载，此处不再赘述。
最后应说明的是：以上各实施例仅用以说明本发明的技术方案，而非对其限制；尽管参照前述各实施例对本发明进行了详细的说明，本领域的普通技术人员应当理解：其依然可以对前述各实施例所记载的技术方案进行修改，或者对其中部分或者全部技术特征进行等同替换；而这些修改或者替换，并不使相应技术方案的本质脱离本发明各实施例技术方案的范围。

Claims (19)

  1. 一种应用服务器AS地址获取方法，其特征在于，包括：
    鉴权认证代理AP实体接收用户设备UE发送的业务设置消息；
    所述AP实体根据所述业务设置消息向引导服务器功能BSF实体发送第一请求消息，所述第一请求消息用于请求使用所述UE的用户的签约数据；
    所述AP实体接收所述BSF实体发送的所述用户的签约数据，其中，所述用户的签约数据包括所述用户归属的AS的地址。
  2. 根据权利要求1所述的方法，其特征在于，所述AS的地址为以下任意一种：所述AS的互联网协议IP地址，所述AS的域名地址，和所述AS的主机名地址。
  3. 根据权利要求1或2所述的方法，其特征在于，当所述AS的地址为所述AS的域名地址或者所述AS的主机名地址时，所述AP实体接收所述BSF实体发送的所述AS的地址之后，还包括：
    所述AP实体根据所述AS的域名地址或者所述AS的主机名地址，获取所述AS的IP地址。
  4. 根据权利要求3所述的方法，其特征在于，所述AP实体根据所述AS的域名地址或者所述AS的主机名地址，获取所述AS的IP地址，包括：
    所述AP实体根据所述AS的域名地址或者所述AS的主机名地址，以及所述AP实体中存储的所述AS的域名地址或者所述AS的主机名地址与所述AS的IP地址的对应关系，获取所述AS的IP地址；或者，
    所述AP实体根据所述AS的域名地址或者所述AS的主机名地址查询域名解析系统DNS，获取所述AS的IP地址。
  5. 根据权利要求3或4所述的方法，其特征在于，当所述AS的域名地址与至少两个IP地址对应时，所述至少两个IP地址中各个IP地址具有不同的优先级；
    所述AP实体获取所述AS的IP地址，包括：
    所述AP实体从所述AS的域名地址所对应的所述至少两个IP地址中获取优先级最高的IP地址作为所述AS的IP地址。
  6. 根据权利要求2-5任意一项所述的方法，其特征在于，还包括：
    所述AP实体根据所述AS的IP地址，向所述AS发送所述业务设置消息。
  7. 根据权利要求1所述的方法，其特征在于，还包括：
    所述AP实体根据所述AS的地址，向所述AS发送所述业务设置消息。
  8. 一种应用服务器AS地址获取方法，其特征在于，包括：
    引导服务器功能BSF实体接收用户设备UE发送的业务设置消息；
    所述BSF实体根据所述业务设置消息，向归属用户寄存器HSS发送第二请求消息，所述第二请求消息用于请求使用所述UE的用户的签约数据；
    所述BSF实体接收所述HSS发送的所述用户的签约数据，其中，所述用户的签约数据包括所述用户归属的AS的地址；
    所述BSF实体接收所述AP实体发送的第一请求消息，所述第一请求消息用于请求所述用户的签约数据；
    所述BSF实体根据所述第一请求消息，向所述AP实体发送所述用户的签约数据。
  9. 根据权利要求8所述的方法，其特征在于，所述AS的地址为以下任意一种：所述AS的互联网协议IP地址，所述AS的域名地址，所述AS的主机名地址。
  10. 一种鉴权认证代理AP实体，其特征在于，包括：
    接收单元，用于接收用户设备UE发送的业务设置消息；
    发送单元，用于根据所述接收单元接收的所述业务设置消息向引导服务器功能BSF实体发送第一请求消息，所述第一请求消息用于请求使用所述UE的用户的签约数据；
    所述接收单元，还用于接收所述BSF实体发送的所述用户的签约数据，其中，所述用户的签约数据包括所述用户归属的应用服务器AS的地址。
  11. 根据权利要求10所述的AP实体，其特征在于，所述AS的地址为以下任意一种：所述AS的互联网协议IP地址，所述AS的域名地址或，所述AS的主机名地址。
  12. 根据权利要求10或11所述的AP实体，其特征在于，还包括：
    获取单元，用于当所述AS的地址为所述AS的域名地址或者所述AS的主机名地址时，根据所述AS的域名地址或者所述AS的主机名地址，获取所述AS的IP地址。
  13. 根据权利要求12所述的AP实体，其特征在于，
    所述获取单元具体用于，根据所述AS的域名地址或者所述AS的主机名 地址，以及所述AP实体中存储的所述AS的域名地址或者所述AS的主机名地址与所述AS的IP地址的对应关系，获取所述AS的IP地址；
    或者，根据所述AS的域名地址或者所述AS的主机名地址查询域名解析系统DNS，获取所述AS的IP地址。
  14. 根据权利要求12或13所述的AP实体，其特征在于，当所述AS的域名地址与至少两个IP地址对应时，所述至少两个IP地址中各个IP地址具有不同的优先级；
    所述获取单元用于获取所述AS的IP地址，包括：
    所述获取单元用于从所述AS的域名地址所对应的所述至少两个IP地址中获取优先级最高的IP地址作为所述AS的IP地址。
  15. 根据权利要求11-14任意一项所述的AP实体，其特征在于，所述发送单元，还用于根据所述AS的IP地址，向所述AS发送所述业务设置消息。
  16. 根据权利要求10所述的AP实体，其特征在于，所述发送单元，还用于根据所述AS的地址，向所述AS发送所述业务设置消息。
  17. 一种引导服务器功能BSF实体，其特征在于，包括：
    接收单元，用于接收用户设备UE发送的业务设置消息；
    发送单元，用于根据所述接收单元接收的所述业务设置消息，向归属用户寄存器HSS发送第二请求消息，所述第二请求消息用于请求使用所述UE的用户的签约数据；
    所述接收单元，还用于接收所述HSS发送的所述用户的签约数据，其中，所述用户的签约数据包括所述用户归属的应用服务器AS的地址；以及接收所述AP实体发送的第一请求消息，所述第一请求消息用于请求所述用户的签约数据；
    所述发送单元，还用于根据所述接收单元接收的所述第一请求消息，向所述AP实体发送所述用户的签约数据。
  18. 根据权利要求17所述的BSF实体，其特征在于，所述AS的地址为以下任意一种：所述AS的互联网协议IP地址，所述AS的域名地址，所述AS的主机名地址。
  19. 一种应用服务器AS地址获取系统，其特征在于，包括：如权利要求10-16任意一项所述的鉴权认证代理AP实体、如权利要求17或18所述的引导服务器功能BSF实体。
PCT/CN2015/095998 2014-12-19 2015-11-30 应用服务器地址获取方法、设备和系统 WO2016095698A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410804320.2A CN104486460B (zh) 2014-12-19 2014-12-19 应用服务器地址获取方法、设备和系统
CN201410804320.2 2014-12-19

Publications (1)

Publication Number Publication Date
WO2016095698A1 true WO2016095698A1 (zh) 2016-06-23

Family

ID=52760964

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/095998 WO2016095698A1 (zh) 2014-12-19 2015-11-30 应用服务器地址获取方法、设备和系统

Country Status (2)

Country Link
CN (1) CN104486460B (zh)
WO (1) WO2016095698A1 (zh)

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104486460B (zh) * 2014-12-19 2018-04-27 华为技术有限公司 应用服务器地址获取方法、设备和系统
CN105071956A (zh) * 2015-07-23 2015-11-18 苏州汉明科技有限公司 一种用于商业wifi的通信方法与系统
CN107018566B (zh) * 2016-01-28 2021-01-15 中国移动通信集团公司 一种补充业务配置实现方法及终端
CN108696829B (zh) * 2017-04-10 2021-07-09 中国移动通信集团河南有限公司 一种补充业务设置处理方法及装置
CN108882184B (zh) * 2017-05-11 2021-06-18 展讯通信（上海）有限公司 补充业务配置方法、装置及终端
CN115604356A (zh) * 2021-07-07 2023-01-13 北京小米移动软件有限公司（Cn） 数据通信的方法、装置、终端及存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2007028701A1 (de) * 2005-09-09 2007-03-15 Nokia Siemens Networks Gmbh & Co. Kg Verfahren zum gezielten blockieren von diensten in einem ip multimedia subsystem
CN1968138A (zh) * 2006-06-07 2007-05-23 华为技术有限公司 Ims网络用户注册信息的管理方法和装置
CN101448244A (zh) * 2008-04-09 2009-06-03 中兴通讯股份有限公司 Ip多媒体子系统集中业务中用户终端配置业务的方法
CN102595372A (zh) * 2011-01-14 2012-07-18 中兴通讯股份有限公司 用户漫游方法及ics增强网络
CN104486460A (zh) * 2014-12-19 2015-04-01 华为技术有限公司 应用服务器地址获取方法、设备和系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2007028701A1 (de) * 2005-09-09 2007-03-15 Nokia Siemens Networks Gmbh & Co. Kg Verfahren zum gezielten blockieren von diensten in einem ip multimedia subsystem
CN1968138A (zh) * 2006-06-07 2007-05-23 华为技术有限公司 Ims网络用户注册信息的管理方法和装置
CN101448244A (zh) * 2008-04-09 2009-06-03 中兴通讯股份有限公司 Ip多媒体子系统集中业务中用户终端配置业务的方法
CN102595372A (zh) * 2011-01-14 2012-07-18 中兴通讯股份有限公司 用户漫游方法及ics增强网络
CN104486460A (zh) * 2014-12-19 2015-04-01 华为技术有限公司 应用服务器地址获取方法、设备和系统

Also Published As

Publication number Publication date
CN104486460B (zh) 2018-04-27
CN104486460A (zh) 2015-04-01

Similar Documents

Publication Publication Date Title
AU2021248311B2 (en) Communication system, method, and apparatus
JP7047921B2 (ja) 通信装置、第１のネットワーク装置、通信装置の方法、及び第１のネットワーク装置の方法
WO2016095698A1 (zh) 应用服务器地址获取方法、设备和系统
WO2019158818A1 (en) Security management for service authorization in communication systems with service-based architecture
EP3753269A1 (en) Security management for roaming service authorization in communication systems with service-based architecture
US9654966B2 (en) Methods and nodes for mapping subscription to service user identity
KR20200064956A (ko) 5g 슬라이스 식별자의 개인 정보 보호를 위한 방법 및 시스템
US20200305001A1 (en) Routing method, apparatus, and system
US20120284785A1 (en) Method for facilitating access to a first access nework of a wireless communication system, wireless communication device, and wireless communication system
US9985967B2 (en) Gateway, client device and methods for facilitating communication between a client device and an application server
WO2020088026A1 (zh) 一种基于通用引导架构gba的认证方法及相关设备
TW201234904A (en) Client and server group SSO with local OpenID
WO2013003535A1 (en) Automated negotiation and selection of authentication protocols
US12192359B2 (en) Authorization of network request
US20200187000A1 (en) Systems and methods for using gba for services used by multiple functions on the same device
JP2018502491A (ja) Ｏｔｔサービスを使用するインフラストラクチャ・ベースのｄ２ｄ接続設定
CN112136301A (zh) 通信系统中用于安全性管理的错误处理框架
US11171927B2 (en) Method for enabling establishment of a direct connection
US9326141B2 (en) Internet protocol multimedia subsystem (IMS) authentication for non-IMS subscribers
WO2020147854A1 (zh) 认证方法、装置、系统以及存储介质
JP7542676B2 (ja) Ａｋｍａ認証サービスの拡張ａ－ｋｉｄ
WO2022151464A1 (en) Method, device, and system for authentication and authorization with edge data network
WO2023216274A1 (zh) 密钥管理方法、装置、设备和存储介质
WO2021208655A1 (zh) 网络漫游认证方法、装置、电子设备及存储介质
CN117546498A (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: 15869206

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 15869206

Country of ref document: EP

Kind code of ref document: A1