WO2015169055A1 - 用户签约信息的响应、请求方法及装置 - Google Patents

用户签约信息的响应、请求方法及装置 Download PDF

Info

Publication number
WO2015169055A1
WO2015169055A1 PCT/CN2014/088676 CN2014088676W WO2015169055A1 WO 2015169055 A1 WO2015169055 A1 WO 2015169055A1 CN 2014088676 W CN2014088676 W CN 2014088676W WO 2015169055 A1 WO2015169055 A1 WO 2015169055A1
Authority
WO
WIPO (PCT)
Prior art keywords
subscription information
user subscription
identifier
hss
aaa server
Prior art date
Application number
PCT/CN2014/088676
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 WO2015169055A1 publication Critical patent/WO2015169055A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/06—Authentication

Definitions

  • the present invention relates to the field of communications, and in particular to a response, request method and apparatus for user subscription information.
  • the authentication and authorization accounting server Authentication, Authorization, Accounting, AAA for short
  • the user home server Home
  • Subscriber Server communicates through the SWx interface to meet user access requests from other non-3GPP networks (such as CDMA, WLAN, WiMAX, etc.), which involves multimedia authentication request/multimedia authentication response MAR/MAA (Multimedia-Authentication) -Request/Answer) message, service subscription request/service subscription response SAR/SAA (Server-Assignment-Request/Answer) message.
  • MAR/MAA Multimedia-Authentication
  • SAR/SAA Server-Assignment-Request/Answer
  • the MAR/MAA message is responsible for exchanging authentication information between the two.
  • the SAR/SAA message is responsible for user registration, registration, PGW update, and user subscription information.
  • the AAA cannot know the status of the change.
  • the SAR message is used to obtain the latest data every time the AAA is online, and the user is subscribed.
  • the SAA response message is usually larger because it carries Non-3GPP-User-Data.
  • the embodiment of the invention provides a response, request method and device for user subscription information, so as to at least solve the problem that the user subscription information between the AAA server and the HSS occupies a large bandwidth in the related art.
  • a method for responding to user subscription information including: receiving a request message sent by an AAA server, where the request message carries an identifier of the first user subscription information in the AAA server The identifier of the user subscription information is used to distinguish user subscription information that is different from the same user content.
  • the response message is sent to the AAA server according to the identifier of the first user subscription information and the identifier of the corresponding second user subscription information in the HSS.
  • the method further includes: sending the second user subscription information to the AAA server in response to the request that the AAA server receives the response message.
  • the response message is sent to the AAA server, where the response message carries the identifier of the second user subscription information and/or the second user subscription information.
  • the identifier includes at least one of the following: a version number, a modification time, and a modified serial number.
  • a method for requesting user subscription information including: sending a request message to an HSS, where the request message carries an identifier of the first user subscription information, and the user subscription information is identified by And a response message sent by the HSS according to the identifier of the first user subscription information and the identifier of the corresponding second user subscription information in the HSS; determining, according to the response message, the response message Whether the first user subscription information is valid.
  • the response message carries the identifier of the second user subscription information; determining whether the first user subscription information is valid according to the response message, including: determining the identifier of the first user subscription information and the second Whether the identifiers of the user subscription information are consistent; if they are consistent, it is determined that the first user subscription information is valid.
  • the method further includes: if the content is inconsistent, sending a request for acquiring the second user subscription information to the HSS; receiving the second user subscription information sent by the HSS in response to the request, and signing the second user The identification of the information.
  • the response message carries the indication information indicating whether the second user subscription information is consistent with the first user subscription information; determining, according to the response message, whether the first user subscription information is valid, including: The indication information indicates that the first user subscription information is consistent with the second user subscription information, and determines that the first user subscription information is valid.
  • the indication information indicates that the first user subscription information is inconsistent with the second user subscription information, send a request for acquiring the second user subscription information to the HSS; and receiving the HSS to send the request in response to the request.
  • the second user subscription information and the identifier of the second user subscription information are inconsistent with the second user subscription information.
  • a response device for user subscription information including: a receiving module, configured to receive a request message sent by an AAA server, where the request message carries the AAA server An identifier of a user subscription information, where the identifier of the user subscription information is used to distinguish user subscription information of different user content; the sending module is configured to be based on the identifier of the first user subscription information and the corresponding second user subscription information in the HSS. Identifying, sending a response message to the AAA server.
  • the sending module is configured to send the response message to the AAA server, where the response message carries an identifier of the second user subscription information.
  • the sending module is further configured to send the second user subscription information to the AAA server in response to the request that the AAA server receives the response message.
  • the sending module includes: a determining unit, configured to determine whether the identifier of the first user subscription information is consistent with the identifier of the second user subscription information; and the sending unit is configured to send the response message to the AAA server,
  • the response message carries indication information indicating whether the first user subscription information is consistent with the second user subscription information.
  • the sending unit is further configured to send the response message to the AAA server if the first user subscription information is inconsistent with the second user subscription information, where the response message carries the The second user subscription information and/or the identification of the second user subscription information.
  • a request device for user subscription information including: a sending module, configured to send a request message to an HSS, where the request message carries an identifier of the first user subscription information, and the user The identifier of the subscription information is used to distinguish the user subscription information of the same user content.
  • the receiving module is configured to receive the response sent by the HSS according to the identifier of the first user subscription information and the identifier of the corresponding second user subscription information in the HSS.
  • a determining module configured to determine, according to the response message, whether the first user subscription information is valid.
  • the response message carries the identifier of the second user subscription information.
  • the determining module includes: a determining unit, configured to determine whether the identifier of the first user subscription information and the identifier of the second user subscription information are The determining unit is configured to determine that the first user subscription information is valid if the identifier of the first user subscription information is consistent with the identifier of the second user subscription information.
  • the sending module is further configured to send a request for acquiring the second user subscription information to the HSS if the identifier of the first user subscription information is inconsistent with the identifier of the second user subscription information.
  • the receiving module is further configured to receive the identifier of the second user subscription information and the second user subscription information that are sent by the HSS in response to the request.
  • the response message carries indication information indicating whether the second user subscription information is consistent with the first user subscription information; the determining module is configured to indicate, in the indication information, the first user subscription information and When the second user subscription information is consistent, it is determined that the first user subscription information is valid.
  • the sending module is further configured to: when the indication information indicates that the first user subscription information is inconsistent with the second user subscription information, send a request for acquiring the second user subscription information to the HSS;
  • the receiving module is further configured to receive the identifier of the second user subscription information and the second user subscription information that are sent by the HSS in response to the request.
  • the embodiment of the present invention receives a request message that is sent by an AAA server and carries an identifier of the user subscription information in the AAA server.
  • the identifier of the user subscription information is used to distinguish user subscription information with different user content; according to the user subscription information in the AAA server.
  • the identifier of the corresponding user subscription information in the identifier and the HSS is sent to the AAA server. Overall, the bandwidth occupied by the user subscription information between the AAA server and the HSS is reduced.
  • FIG. 1 is a flowchart of a method for responding to user subscription information according to an embodiment of the present invention
  • FIG. 2 is a structural block diagram of a response device for user subscription information according to an embodiment of the present invention
  • FIG. 3 is a flowchart of a method for requesting user subscription information according to an embodiment of the present invention.
  • FIG. 4 is a structural block diagram of a requesting apparatus for user subscription information according to an embodiment of the present invention.
  • FIG. 5 is a schematic diagram of a delivery system of user subscription information according to an embodiment of the present invention.
  • FIG. 6 is a flowchart of a method for acquiring user subscription information according to a preferred embodiment 1 of the present invention
  • FIG. 7 is a flowchart of a method for acquiring user subscription information according to a preferred embodiment 2 of the present invention.
  • FIG. 8 is a flowchart of a method for acquiring user subscription information according to a preferred embodiment 3 of the present invention.
  • FIG. 9 is a schematic diagram of a SAR/SAA message between an AAA server and an HSS according to an embodiment of the present invention.
  • FIG. 1 is a flowchart of a method for responding to user subscription information according to an embodiment of the present invention. As shown in FIG. 1, the method includes steps S102 to S104.
  • Step S102 Receive a request message sent by the AAA server, where the request message carries an identifier of the user subscription information in the AAA server, and the identifier of the user subscription information is used to distinguish user subscription information with different user content.
  • Step S104 Send a response message to the AAA server according to the AAA service identifier of the user subscription information and the identifier of the corresponding user subscription information in the HSS.
  • the embodiment of the present invention receives a request message that is sent by an AAA server and carries an identifier of the user subscription information in the AAA server.
  • the identifier of the user subscription information is used to distinguish user subscription information with different user content; according to the user subscription information in the AAA server.
  • the identifier of the corresponding user subscription information in the identifier and the HSS is sent to the AAA server. Overall, the bandwidth occupied by the user subscription information between the AAA server and the HSS is reduced.
  • the corresponding user subscription information includes the user subscription information of the user corresponding to the user subscription information in the AAA server in the HSS.
  • the user subscription information in the AAA server is consistent with the user subscription information in the HSS.
  • the response message may be sent to the AAA server, where the response message carries the identifier of the corresponding user subscription information in the HSS. Further, the AAA server may determine whether the user subscription information in the AAA server is consistent according to the identifier of the corresponding user subscription information in the HSS.
  • the AAA server may send a request to obtain corresponding user subscription information in the HSS.
  • the AAA server may send the corresponding user subscription information in the HSS to the AAA server in response to the request after receiving the response message.
  • step S104 it may be determined whether the identifier of the user subscription information in the AAA server is consistent with the identifier of the corresponding user subscription information in the HSS, and sends a response message to the AAA server, where the response message is sent.
  • the indication information indicating whether the user subscription information in the AAA server is consistent with the corresponding user subscription information in the HSS is carried. Further, the AAA server may determine, according to the indication information, whether the user subscription information is consistent.
  • the step S104 or the step S104 may send a response message to the AAA server.
  • the response message carries the corresponding user subscription information in the HSS and/or the identifier of the user subscription information.
  • the above identifier may include a version number, a modification time, a modification serial number, and the like.
  • the device may include: a receiving module 10 and a sending module 20.
  • the receiving module 10 is configured to receive a request message sent by the AAA server, where the request message carries an identifier of the user subscription information in the AAA server, and the identifier of the user subscription information is used to distinguish user subscription information with different user content.
  • the sending module 20 is connected to the receiving module 10, and is configured to send a response message to the AAA server according to the identifier of the user subscription information in the AAA server and the identifier of the corresponding user subscription information in the HSS.
  • the sending module 20 may be configured to send a response message to the AAA server, where the response message carries an identifier of the corresponding user subscription information in the HSS.
  • the AAA server may determine whether the user subscription information is consistent according to the identifier of the corresponding user subscription information in the HSS. In case of inconsistency, the AAA server may request to obtain the corresponding user subscription information in the HSS.
  • the sending module 20 may be further configured to send the corresponding user subscription information in the HSS to the AAA server in response to the request that the AAA server receives the response message.
  • the sending module 20 may include: a determining unit, configured to determine whether the identifier of the user subscription information in the AAA server and the identifier of the corresponding user subscription information in the HSS are The sending unit is configured to send a response message to the AAA server, where the response message carries indication information indicating whether the user subscription information in the AAA server is consistent with the corresponding user subscription information in the HSS.
  • the sending unit is further configured to: when the user subscription information in the AAA server is inconsistent with the corresponding user subscription information in the HSS, send a response message to the AAA server, where the response message is carried in the response message. There is corresponding user subscription information in the HSS and/or an identifier of the user subscription information.
  • the sending unit may send a response message to the AAA server, where the response message carries the corresponding user subscription information in the HSS and/or the identifier of the user subscription information.
  • the user subscription information in the HSS may be sent when the AAA server receives the request for the corresponding user subscription information in the HSS.
  • the above identifier may include a version number, a modification time, a modification serial number, and the like.
  • FIG. 3 is a flowchart of a method for requesting user subscription information according to an embodiment of the present invention. As shown in FIG. 3, the method includes steps S302 to S306.
  • Step S302 Send a request message to the HSS, where the request message carries an identifier of the user subscription information in the AAA server, and the identifier of the user subscription information is used to distinguish user subscription information with different user content.
  • Step S304 Receive a response message sent by the HSS according to the identifier of the user subscription information in the AAA server and the identifier of the corresponding subscriber subscription information in the HSS.
  • Step S306 determining, according to the response message, whether the user subscription information in the AAA server is valid.
  • the request message is sent to the HSS, where the request message carries the identifier of the user subscription information in the AAA server, and the identifier of the user subscription information is used to distinguish the user subscription information with different user content, and the receiving HSS is according to the AAA server.
  • the response message sent by the identifier of the user subscription information and the identifier of the corresponding user subscription information in the HSS determines whether the user subscription information in the AAA server is valid according to the response message. Overall, the bandwidth occupied by the user subscription information between the AAA server and the HSS is reduced.
  • the corresponding user subscription information includes the user subscription information of the user corresponding to the user subscription information in the AAA server in the HSS.
  • the user subscription information in the AAA server is consistent with the user subscription information in the HSS.
  • the response message carries an identifier of the corresponding user subscription information in the HSS.
  • step S306 it can be determined whether the identifier of the user subscription information in the AAA server is consistent with the identifier of the corresponding user subscription information in the HSS; if they are consistent, it is determined that the first user subscription information is valid.
  • the request for acquiring the corresponding subscriber subscription information in the HSS may also be sent to the HSS. Receiving the corresponding user subscription information in the HSS sent by the HSS in response to the request and the identifier of the user subscription information.
  • the response message carries the indication information indicating whether the user subscription information in the AAA server is consistent with the corresponding user subscription information in the HSS.
  • the indication information indicates AAA
  • the user subscription information in the service is consistent with the corresponding user subscription information in the HSS, and it can be determined that the user subscription information in the AAA server is valid. Further, the user subscription information in the AAA server can be used to authenticate the corresponding user.
  • the request for acquiring the corresponding user subscription information in the HSS may be sent to the HSS.
  • the above identifier may include a version number, a modification time, a modification serial number, and the like.
  • the apparatus may include: a sending module 30, a receiving module 40, and a determining module 50.
  • the sending module 30 is configured to send a request message to the HSS, where the request message carries the identifier of the user subscription information in the AAA service, and the identifier of the user subscription information is used to distinguish the user subscription information with different user content; the receiving module 40 And a response message sent by the HSS according to the identifier of the user subscription information in the AAA service and the identifier of the corresponding user subscription information in the HSS.
  • the determining module 50 is configured to determine, according to the response message, whether the user subscription information in the AAA server is valid.
  • the request message is sent to the HSS, where the request message carries the identifier of the user subscription information in the AAA server, and the identifier of the user subscription information is used to distinguish the user subscription information with different user content, and the receiving HSS is according to the AAA server.
  • the identifier of the user subscription information and the corresponding user subscription letter in the HSS The response message sent by the identifier of the information determines whether the user subscription information in the AAA server is valid according to the response message. Overall, the bandwidth occupied by the user subscription information between the AAA server and the HSS is reduced.
  • the corresponding user subscription information in the HSS includes the user subscription information of the user corresponding to the user subscription information in the AAA server in the HSS.
  • the user subscription information in the AAA server is consistent with the user subscription information in the HSS.
  • the response message carries an identifier of the corresponding user subscription information in the HSS.
  • the determining module 50 may include: a determining unit, configured to determine whether the identifier of the user subscription information in the AAA server is consistent with the identifier of the corresponding user subscription information in the HSS; and the determining unit is configured to identify the user subscription information and the HSS in the AAA server. If the identifiers of the corresponding user subscription information are the same, it is determined that the user subscription information in the AAA server is valid.
  • the sending module 30 may be configured to send the identifier to the HSS when the identifier of the user subscription information in the AAA server is different from the identifier of the corresponding user subscription information in the HSS.
  • the receiving module 40 may be configured to receive the corresponding user subscription information and the identifier of the user subscription information in the HSS sent by the HSS in response to the request.
  • the response message carries indication information indicating whether the user subscription information in the AAA server is consistent with the corresponding user subscription information in the HSS.
  • the determining module 50 may be configured to determine that the user subscription information in the AAA server is valid when the indication information indicates that the user subscription information in the AAA server is consistent with the corresponding user subscription information in the HSS. Further, the user subscription information in the AAA server can be used to authenticate the corresponding user.
  • the sending module 30 is further configured to: when the indication information indicates that the user subscription information in the AAA server is inconsistent with the corresponding user subscription information in the HSS, send the information to the HSS for acquiring the HSS.
  • a corresponding request for user subscription information The receiving module 40 is further configured to receive the corresponding user subscription information and the identifier of the user subscription information in the HSS sent by the HSS in response to the request. Further, the corresponding user subscription information may be used to authenticate the corresponding user.
  • the method and apparatus of the embodiments of the present invention can be implemented by a computer program unit.
  • the foregoing method and apparatus of the embodiments of the present invention may be implemented in an HSS or AAA server, or may be implemented in a device or an apparatus.
  • the embodiment of the invention further provides a device, which may include a processor, a storage medium and other general components.
  • a computer program element implementing the above methods, apparatus can be stored in the storage medium, and the processor can execute the computer program element.
  • FIG. 5 is a schematic diagram of a delivery system for user subscription information according to an embodiment of the present invention.
  • the system includes: an AAA server 1 and an HSS server 2.
  • the AAA server 1 may include a processor 10 and a storage medium 12, and computer program instructions in the storage medium 12 that can store the request method of the user subscription information, and the processor 10 can execute the computer program instructions.
  • the HSS server 2 may include a processor 20 and a storage medium 22, computer program instructions in the storage medium 22 that may store the response method of the user subscription information, and the processor 20 may execute the computer program instructions.
  • the AAA server sends a request message to the HSS, where the request message carries the identifier of the user subscription information in the AAA server, and the HSS sends the identifier of the corresponding user subscription information in the HSS to the AAA server, and the AAA server compares the two. Whether the identifiers are the same and follow-up processing based on the results of the comparison.
  • FIG. 6 is a flowchart of a method for acquiring user subscription information according to a preferred embodiment 1 of the present invention. As shown in FIG. 6, the method includes steps S602 to S612.
  • Step S602 the AAA server sends a request message to the HSS, where the request message carries the identifier of the user subscription information.
  • the request message when the user goes online, the request message may be sent to the HSS to request the user's subscription information. It may also be that when the user subscription information in the AAA server needs to be updated, the above message is triggered to be sent to the HSS.
  • the preferred embodiment is not limited thereto.
  • Step S604 The HSS receives the request message, and sends a response message to the AAA server, where the response message carries the identifier of the corresponding user subscription information in the HSS.
  • step S606 the AAA server receives the response message sent by the HSS server, and compares the identifier of the user subscription information in the AAA server with the identifier of the corresponding user subscription information in the HSS. If they are consistent, it is determined that the user subscription information in the AAA server is valid.
  • Step S608 if not, send a request for requesting corresponding user subscription information in the HSS to the HSS.
  • Step S610 the HSS receives the request, and sends a response carrying the corresponding user subscription information in the HSS to the AAA server.
  • Step S612 the AAA server receives the response, obtains the user subscription information from the response, and further deletes the previously saved user subscription information.
  • the AAA server sends a request message to the HSS, where the request message carries the identifier of the user subscription information in the AAA server, and the HSS compares the identifier of the user subscription information in the AAA server with the identifier of the corresponding user subscription information in the HSS. And sending an indication to the AAA server whether the two are consistent, and the AAA server performs subsequent processing according to the instruction.
  • FIG. 7 is a flowchart of a method for acquiring user subscription information according to a preferred embodiment 2 of the present invention. As shown in FIG. 7, the method includes steps S702 to S704.
  • Step S702 the AAA server sends a request message to the HSS, where the request message carries the identifier of the user subscription information.
  • the request message when the user goes online, the request message may be sent to the HSS to request the user's subscription information. It may also be that when the user subscription information in the AAA server needs to be updated, the above message is triggered to be sent to the HSS.
  • the preferred embodiment is not limited thereto.
  • Step S704 the HSS receives the request message, compares the identifier of the user subscription information in the AAA server with the identifier of the corresponding user subscription information in the HSS, and sends a response message to the AAA server, where the response message carries the indication information of whether the two are consistent.
  • the corresponding user subscription information in the HSS may also be carried.
  • the HSS can also actively send the corresponding user subscription information in the HSS to the AAA server through other messages, and is not limited to the above response message.
  • Step S706 the AAA server receives the response message sent by the HSS server, and determines, according to the indication information, whether the user subscription information in the AAA server needs to be updated. If they are consistent, it is determined that the user subscription information in the AAA server is valid.
  • Step S708 if not, send a request for requesting corresponding user subscription information in the HSS to the HSS.
  • step S708 to step S712 may be omitted.
  • Step S710 the HSS receives the request, and sends a response carrying the corresponding user subscription information in the HSS to the AAA server.
  • Step S712 the AAA server receives the response, obtains the user subscription information from the response, and further deletes the previously saved user subscription information.
  • the AAA server sends a request message to the HSS, where the request message carries the identifier of the user subscription information in the AAA server, and the HSS compares the identifier of the user subscription information in the AAA server with the identifier of the corresponding user subscription information in the HSS. And in case of inconsistency, the corresponding user subscription information in the HSS is sent to the AAA server, and if the information is consistent, the indication information is sent.
  • FIG. 8 is a flowchart of a method for acquiring user subscription information according to a preferred embodiment 3 of the present invention. As shown in FIG. 8, the method includes steps S802 to S806.
  • Step S802 the AAA server sends a request message to the HSS, where the request message carries the identifier of the user subscription information.
  • the request message when the user goes online, the request message may be sent to the HSS to request the user's subscription information. It may also be that when the user subscription information in the AAA server needs to be updated, the above message is triggered to be sent to the HSS.
  • the preferred embodiment is not limited thereto.
  • step S804 the HSS receives the request message, compares the identifier of the user subscription information in the AAA server with the identifier of the corresponding user subscription information in the HSS, and sends a response message to the AAA server. If they match, the indication information indicating the consistency is carried. If they are inconsistent, they carry the corresponding user subscription information in the HSS.
  • the HSS may also actively send the corresponding user subscription information in the HSS to the AAA server by using other messages, and is not limited to the foregoing response message.
  • Step S806 the AAA server receives the response message sent by the HSS server.
  • the data version number is used to identify the old and new user subscription information held by the AAA and whether it has been modified.
  • the user subscription information is relatively stable, and the subscription data is the same as the previous time.
  • the contract data remains unchanged with a very high probability.
  • the above data version number may be various ways of indicating the time of data modification, or the incremental sequence number of data modification, as long as it can distinguish whether it is changed.
  • the user subscription information sent by the HSS to the AAA is cached on the AAA side, and the version number of the subscription data is saved.
  • the HSS updates the version number of the user subscription data when modifying the user subscription information.
  • the HSS When receiving the request of the AAA to obtain the user subscription information, the HSS checks the version number field in the request. If the version number is the same as the local version, the information related to the version number such as Non-3GPP-User-Data does not need to be sent. At the same time, the data version number AVP is added in the SAA, and the version numbers are the same. As to how to indicate the version number in the HSS-approved SAR request, this embodiment does not impose constraints, such as the value of the same data version number brought back by the same AVP as described herein.
  • the HSS When receiving the request of the AAA to obtain the user subscription information, the HSS checks the version number field in the request, and if it is different from the local data version number, the subscription information such as Non-3GPP-User-Data is delivered, and the SAA needs to be added.
  • the data version number AVP is the data version number of the user on the HSS side.
  • AAA and HSS if either party does not support this function, the data version number AVP field is ignored. Does not affect the normal interaction process.
  • FIG. 9 is a schematic diagram of a SAR/SAA message between an AAA server and an HSS according to an embodiment of the present invention. As shown in FIG. 9, the method includes:
  • Step S902 the first access, the AAA sends the SAR request user data, and carries the user data version number (User_Data_Version) (hereinafter referred to as UDV) to 0.
  • UDV user data version number
  • Step S910 the HSS modifies the user subscription data.
  • Step S914 the HSS checks that the latest version of the user subscription data is newer than the requested version, and sends an SAA, where the UDV is a new version number 1456238240, and carries Non-3GPP-User-Data.
  • step S904 when the AAA receives the SAA response with the new version number of the HSS, the AAA saves the version number and Non-3GPP-User-Data in the SAA.
  • the AAA needs to retrieve the previously saved user subscription information and its version number before sending the SAR to the HSS to obtain the user subscription information.
  • step S908 only a method indicating that the requester owns the latest data is given here, and may also be marked in the response in other ways.
  • the User_Data_Version mentioned in the step description is just an example and is not limited by name.
  • the present invention achieves the following technical effects: the bandwidth occupied by the user subscription information between the AAA server and the HSS is reduced as a whole.
  • modules or steps of the present invention described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.
  • the steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated as a single integrated circuit module.
  • the invention is not limited to any specific combination of hardware and software.
  • the response, request method, and apparatus for user subscription information provided by the embodiments of the present invention have the following beneficial effects: the bandwidth occupied by the user subscription information between the AAA server and the HSS is reduced as a whole.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

本发明公开了一种用户签约信息的响应、请求方法及装置。其中，用户签约信息的响应方法包括：接收AAA服务器发送的携带有AAA服务器中用户签约信息的标识的请求消息，用户签约信息的标识用于区分同一用户内容不同的用户签约信息；根据AAA服务器中用户签约信息的标识和HSS中对应的用户签约信息的标识，向AAA服务器发送响应消息。通过本发明，整体上降低了AAA服务器和HSS之间传递用户签约信息占用的带宽。

Description

用户签约信息的响应、请求方法及装置 技术领域
本发明涉及通信领域，具体而言，涉及一种用户签约信息的响应、请求方法及装置。
背景技术
在3GPP长期演进技术(Long Term Evolution，简称为LTE)演进核心网(Evolved Packet Core，简称为EPC)中，认证授权计费服务器(Authentication、Authorization、Accounting，简称为AAA)与用户归属服务器(Home Subscriber Server，简称为HSS)通过SWx接口通信以满足用户从其他非3GPP网络(如CDMA、WLAN、WiMAX等)的接入请求，其中涉及到多媒体认证请求/多媒体认证应答MAR/MAA(Multimedia-Authentication-Request/Answer)消息，服务签约请求/服务签约应答SAR/SAA(Server-Assignment-Request/Answer)消息。MAR/MAA消息负责在两者之间交换鉴权信息。SAR/SAA消息负责用户注册、去注册、PGW更新及获取用户签约信息等。
用户在非3GPP离线状态时，如果HSS修改用户签约信息，AAA是无法知道此变更状态的，为了数据一致性，在每次从AAA上线时都要通过SAR消息去获取最新数据，在获取用户签约信息时SAA响应消息因为携带Non-3GPP-User-Data而通常较大。
针对相关技术中AAA服务器和HSS之间传递用户签约信息占用较大带宽的问题，目前尚未提出有效的解决方案。
发明内容
本发明实施例提供了一种用户签约信息的响应、请求方法及装置，以至少解决相关技术中AAA服务器和HSS之间传递用户签约信息占用较大带宽的问题。
根据本发明的一个实施例，提供了一种用户签约信息的响应方法，包括：接收AAA服务器发送的请求消息，其中，所述请求消息中携带有所述AAA服务器中第一用户签约信息的标识，用户签约信息的标识用于区分同一用户内容不同的用户签约信息；根据所述第一用户签约信息的标识和HSS中对应的第二用户签约信息的标识，向所述AAA服务器发送响应消息。
根据所述第一用户签约信息的标识和HSS中对应的第二用户签约信息的标识，向所述AAA服务器发送响应消息，包括：向所述AAA服务器发送所述响应消息，其中，所述响应消息中携带有所述第二用户签约信息的标识。
上述方法还包括：响应所述AAA服务器接收到所述响应消息后的请求，向所述AAA服务器发送所述第二用户签约信息。
根据所述第一用户签约信息的标识和HSS中对应的第二用户签约信息的标识，向所述AAA服务器发送响应消息，包括：判断所述第一用户签约信息的标识与所述第二用户签约信息的标识是否一致；向所述AAA服务器发送所述响应消息，其中所述响应消息中携带有指示所述第一用户签约信息与所述第二用户签约信息是否一致的指示信息。
如果不一致，向所述AAA服务器发送所述响应消息，其中所述响应消息中携带有所述第二用户签约信息和/或所述第二用户签约信息的标识。
所述标识包括以下至少之一：版本号、修改时间、修改序列号。
根据本发明的另一个实施例，提供了一种用户签约信息的请求方法，包括：向HSS发送请求消息，其中所述请求消息中携带有第一用户签约信息的标识，用户签约信息的标识用于区分同一用户内容不同的用户签约信息；接收所述HSS根据第一用户签约信息的标识和所述HSS中对应的第二用户签约信息的标识发送的响应消息；根据所述响应消息判断所述第一用户签约信息是否有效。
所述响应消息中携带有所述第二用户签约信息的标识；根据所述响应消息判断所述第一用户签约信息是否有效，包括：判断所述第一用户签约信息的标识与所述第二用户签约信息的标识是否一致；如果一致，确定所述第一用户签约信息有效。
上述方法还包括：如果不一致，向所述HSS发送用于获取所述第二用户签约信息的请求；接收所述HSS响应所述请求发送的所述第二用户签约信息和所述第二用户签约信息的标识。
所述响应消息中携带有指示所述第二用户签约信息与所述第一用户签约信息是否一致的指示信息；根据所述响应消息判断所述第一用户签约信息是否有效，包括：如果所述指示信息指示所述第一用户签约信息与所述第二用户签约信息一致，确定所述第一用户签约信息有效。
如果所述指示信息指示所述第一用户签约信息与所述第二用户签约信息不一致，向所述HSS发送用于获取所述第二用户签约信息的请求；接收所述HSS响应所述请求发送的所述第二用户签约信息和所述第二用户签约信息的标识。
根据本发明的再一个实施例，提供了一种用户签约信息的响应装置，包括：接收模块，设置为接收AAA服务器发送的请求消息，其中，所述请求消息中携带有所述AAA服务器中第一用户签约信息的标识，用户签约信息的标识用于区分同一用户内容不同的用户签约信息；发送模块，设置为根据所述第一用户签约信息的标识和HSS中对应的第二用户签约信息的标识，向所述AAA服务器发送响应消息。
所述发送模块，设置为向所述AAA服务器发送所述响应消息，其中，所述响应消息中携带有所述第二用户签约信息的标识。
所述发送模块，还设置为响应所述AAA服务器接收到所述响应消息后的请求，向所述AAA服务器发送所述第二用户签约信息。
所述发送模块包括：判断单元，设置为判断所述第一用户签约信息的标识与所述第二用户签约信息的标识是否一致；发送单元，设置为向所述AAA服务器发送所述响应消息，其中所述响应消息中携带有指示所述第一用户签约信息与所述第二用户签约信息是否一致的指示信息。
所述发送单元，还设置为在所述第一用户签约信息与所述第二用户签约信息不一致的情况下，向所述AAA服务器发送所述响应消息，其中所述响应消息中携带有所述第二用户签约信息和/或所述第二用户签约信息的标识。
根据本发明的又一个实施例，提供了一种用户签约信息的请求装置，包括：发送模块，设置为向HSS发送请求消息，其中所述请求消息中携带有第一用户签约信息的标识，用户签约信息的标识用于区分同一用户内容不同的用户签约信息；接收模块，设置为接收所述HSS根据第一用户签约信息的标识和所述HSS中对应的第二用户签约信息的标识发送的响应消息；确定模块，设置为根据所述响应消息判断所述第一用户签约信息是否有效。
所述响应消息中携带有所述第二用户签约信息的标识；所述确定模块包括：判断单元，设置为判断所述第一用户签约信息的标识与所述第二用户签约信息的标识是否 一致；确定单元，设置为在所述第一用户签约信息的标识与所述第二用户签约信息的标识一致的情况下，确定所述第一用户签约信息有效。
所述发送模块，还设置为在所述第一用户签约信息的标识与所述第二用户签约信息的标识不一致的情况下，向所述HSS发送用于获取所述第二用户签约信息的请求；所述接收模块，还设置为接收所述HSS响应所述请求发送的所述第二用户签约信息和所述第二用户签约信息的标识。
所述响应消息中携带有指示所述第二用户签约信息与所述第一用户签约信息是否一致的指示信息；所述确定模块，设置为在所述指示信息指示所述第一用户签约信息与所述第二用户签约信息一致时，确定所述第一用户签约信息有效。
所述发送模块，还设置为在所述指示信息指示所述第一用户签约信息与所述第二用户签约信息不一致时，向所述HSS发送用于获取所述第二用户签约信息的请求；所述接收模块，还设置为接收所述HSS响应所述请求发送的所述第二用户签约信息和所述第二用户签约信息的标识。
通过本发明实施例，接收AAA服务器发送的携带有AAA服务器中用户签约信息的标识的请求消息，用户签约信息的标识用于区分同一用户内容不同的用户签约信息；根据AAA服务器中用户签约信息的标识和HSS中对应的用户签约信息的标识，向AAA服务器发送响应消息。整体上降低了AAA服务器和HSS之间传递用户签约信息占用的带宽。
附图说明
此处所说明的附图用来提供对本发明的进一步理解，构成本申请的一部分，本发明的示意性实施例及其说明用于解释本发明，并不构成对本发明的不当限定。在附图中：
图1是根据本发明实施例的用户签约信息的响应方法的流程图；
图2是根据本发明实施例的用户签约信息的响应装置的结构框图；
图3是根据本发明实施例的用户签约信息的请求方法的流程图；
图4是根据本发明实施例的用户签约信息的请求装置的结构框图；
图5是根据本发明实施例的用户签约信息的传递系统的示意图；
图6是根据本发明实例优选实施方式一的用户签约信息的获取方法的流程图；
图7是根据本发明实例优选实施方式二的用户签约信息的获取方法的流程图；
图8是根据本发明实例优选实施方式三的用户签约信息的获取方法的流程图；以及
图9是根据本发明实施例AAA服务器与HSS间SAR/SAA消息的示意图。
具体实施方式
下文中将参考附图并结合实施例来详细说明本发明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。
图1是根据本发明实施例的用户签约信息的响应方法的流程图，如图1所示，该方法包括步骤S102至步骤S104。
步骤S102，接收AAA服务器发送的请求消息，其中，该请求消息中携带有AAA服务器中用户签约信息的标识，用户签约信息的标识用于区分同一用户内容不同的用户签约信息。
步骤S104，根据AAA服务其中用户签约信息的标识和HSS中对应的用户签约信息的标识，向AAA服务器发送响应消息。
通过本发明实施例，接收AAA服务器发送的携带有AAA服务器中用户签约信息的标识的请求消息，用户签约信息的标识用于区分同一用户内容不同的用户签约信息；根据AAA服务器中用户签约信息的标识和HSS中对应的用户签约信息的标识，向AAA服务器发送响应消息。整体上降低了AAA服务器和HSS之间传递用户签约信息占用的带宽。
上述步骤S104中，对应的用户签约信息包括上述AAA服务器中用户签约信息对应的用户在HSS中的用户签约信息。但不限于此，对于需要保证AAA服务器中用户签约信息与HSS中的用户签约信息一致的情况，都是可以的。
在本发明实施例的一个实施方式中，上述步骤S104，可以向AAA服务器发送响应消息，其中，响应消息中携带有HSS中对应的用户签约信息的标识。进一步的，AAA服务器可以根据HSS中对应的用户签约信息的标识，确定AAA服务器中用户签约信息是否一致。
在本发明实施例的一个实施方式中，如果AAA服务器确定其用户签约信息与HSS中对应的用户签约信息不一致，可以发送请求获取HSS中对应的用户签约信息。上述步骤S104之后，可以响应AAA服务器接收到上述响应消息后的请求，向AAA服务器发送HSS中对应的用户签约信息。
在本发明实施例的另一个实施方式中，上述步骤S104，可以判断AAA服务器中用户签约信息的标识与HSS中对应的用户签约信息的标识是否一致，向AAA服务器发送响应消息，其中该响应消息中携带有指示AAA服务器中用户签约信息与HSS中对应的用户签约信息是否一致的指示信息。进一步的，AAA服务器可以根据该指示信息，确定其用户签约信息是否一致。
在本发明实施例的一个优选实施方式中，在AAA服务器中用户签约信息的标识与HSS中对应的用户签约信息的标识不一致时，上述步骤S104或上述步骤S104之后，可以向AAA服务器发送响应消息，其中响应消息中携带有HSS中对应的用户签约信息和/或该用户签约信息的标识。
上述标识可以包括版本号、修改时间、修改序列号等。
图2是根据本发明实施例的用户签约信息的响应装置的结构框图，如图2所示，该装置可以包括：接收模块10和发送模块20。其中，接收模块10，设置为接收AAA服务器发送的请求消息，其中，该请求消息中携带有AAA服务器中用户签约信息的标识，用户签约信息的标识用于区分同一用户内容不同的用户签约信息；发送模块20，与接收模块10相连接，设置为根据AAA服务器中用户签约信息的标识和HSS中对应的用户签约信息的标识，向AAA服务器发送响应消息。
在本发明实施例的一个实施方式中，发送模块20可以设置为向AAA服务器发送响应消息，其中，响应消息中携带有HSS中对应的用户签约信息的标识。
进一步的，AAA服务器可以根据HSS中对应的用户签约信息的标识，确定其用户签约信息是否一致，在不一致的情况下，可以请求获取HSS中对应的用户签约信息。
在本发明实施例的一个优选实施方式中，发送模块20还可以设置为响应AAA服务器接收到上述响应消息后的请求，向AAA服务器发送HSS中对应的用户签约信息。
在本发明实施例的另一个实施方式中，发送模块20可以包括：判断单元，设置为判断AAA服务器中用户签约信息的标识与HSS中对应的用户签约信息的标识是否一 致；发送单元，设置为向AAA服务器发送响应消息，其中该响应消息中携带有指示AAA服务器中用户签约信息与HSS中对应的用户签约信息是否一致的指示信息。
在本发明实施例的一个优选实施方式中，上述发送单元还设置为在AAA服务器中用户签约信息与HSS中对应的用户签约信息不一致的情况下，向AAA服务器发送响应消息，其中响应消息中携带有HSS中对应的用户签约信息和/或该用户签约信息的标识。
上述发送单元，可以主动向AAA服务器发送响应消息，其中响应消息中携带有HSS中对应的用户签约信息和/或该用户签约信息的标识。也可以在接收到AAA服务器用于获取HSS中对应的用户签约信息的请求时，发送上述HSS中对应的用户签约信息。
上述标识可以包括版本号、修改时间、修改序列号等。
图3是根据本发明实施例的用户签约信息的请求方法的流程图，如图3所示，该方法包括步骤S302至步骤S306。
步骤S302，向HSS发送请求消息，其中请求消息中携带有AAA服务器中用户签约信息的标识，用户签约信息的标识用于区分同一用户内容不同的用户签约信息。
步骤S304，接收HSS根据AAA服务器中用户签约信息的标识和HSS中对应的用户签约信息的标识发送的响应消息。
步骤S306，根据上述响应消息判断AAA服务器中用户签约信息是否有效。
通过本发明实施例，向HSS发送请求消息，其中请求消息中携带有AAA服务器中用户签约信息的标识，用户签约信息的标识用于区分同一用户内容不同的用户签约信息，接收HSS根据AAA服务器中用户签约信息的标识和HSS中对应的用户签约信息的标识发送的响应消息，根据上述响应消息判断AAA服务器中用户签约信息是否有效。整体上降低了AAA服务器和HSS之间传递用户签约信息占用的带宽。
上述步骤S304中，对应的用户签约信息包括上述AAA服务器中用户签约信息对应的用户在HSS中的用户签约信息。但不限于此，对于需要保证AAA服务器中用户签约信息与HSS中的用户签约信息一致的情况，都是可以的。
在本发明实施例的一个实施方式中，上述响应消息中携带有HSS中对应的用户签约信息的标识。上述步骤S306，可以判断AAA服务器中用户签约信息的标识与HSS中对应的用户签约信息的标识是否一致；如果一致，确定第一用户签约信息有效。
在本发明实施例的一个优选实施方式中，如果AAA服务器中用户签约信息的标识与HSS中对应的用户签约信息的标识不一致，还可以向HSS发送用于获取HSS中对应的用户签约信息的请求；接收HSS响应该请求发送的HSS中对应的用户签约信息和该用户签约信息的标识。
在本发明实施例的另一个实施方式中，上述响应消息中携带有指示AAA服务器中用户签约信息与HSS中对应的用户签约信息是否一致的指示信息；上述步骤S304中，如果该指示信息指示AAA服务中用户签约信息与HSS中对应的用户签约信息一致，可以确定AAA服务器中用户签约信息有效。进一步的，可以使用AAA服务器中的用户签约信息对对应用户鉴权。
在本发明实施例的一个优选实施方式中，如果上述指示信息指示AAA服务器中用户签约信息与HSS中对应的用户签约信息不一致，可以向HSS发送用于获取HSS中对应的用户签约信息的请求，接收HSS响应该请求发送的HSS中对应的用户签约信息和该用户签约信息的标识。进一步的，可以使用接收到的用户签约信息对对应用户鉴权。
上述标识可以包括版本号、修改时间、修改序列号等。
图4是根据本发明实施例的用户签约信息的请求装置的结构框图，如图4所示，该装置可以包括：发送模块30、接收模块40和确定模块50。其中，发送模块30，设置为向HSS发送请求消息，其中该请求消息中携带有AAA服务中用户签约信息的标识，用户签约信息的标识用于区分同一用户内容不同的用户签约信息；接收模块40，设置为接收HSS根据AAA服务中用户签约信息的标识和HSS中对应的用户签约信息的标识发送的响应消息；确定模块50，设置为根据上述响应消息判断AAA服务器中用户签约信息是否有效。
通过本发明实施例，向HSS发送请求消息，其中请求消息中携带有AAA服务器中用户签约信息的标识，用户签约信息的标识用于区分同一用户内容不同的用户签约信息，接收HSS根据AAA服务器中用户签约信息的标识和HSS中对应的用户签约信 息的标识发送的响应消息，根据上述响应消息判断AAA服务器中用户签约信息是否有效。整体上降低了AAA服务器和HSS之间传递用户签约信息占用的带宽。
上述HSS中对应的用户签约信息包括：上述AAA服务器中用户签约信息对应的用户在HSS中的用户签约信息。但不限于此，对于需要保证AAA服务器中用户签约信息与HSS中的用户签约信息一致的情况，都是可以的。
在本发明实施例的一个实施方式中，上述响应消息中携带有HSS中对应的用户签约信息的标识。上述确定模块50可以包括：判断单元，设置为判断AAA服务器中用户签约信息的标识与HSS中对应的用户签约信息的标识是否一致；确定单元，设置为在AAA服务器中用户签约信息的标识与HSS中对应的用户签约信息的标识一致的情况下，确定AAA服务器中用户签约信息有效。
在本发明实施例的一个优选实施方式中，上述发送模块30，还可以设置为在AAA服务器中用户签约信息的标识与HSS中对应的用户签约信息的标识不一致的情况下，向HSS发送用于获取HSS中对应的用户签约信息的请求；接收模块40，还可以设置为接收HSS响应该请求发送的HSS中对应的用户签约信息和该用户签约信息的标识。
在本发明实施例的一个实施方式中，上述响应消息中携带有指示AAA服务器中用户签约信息与HSS中对应的用户签约信息是否一致的指示信息。上述确定模块50，可以设置为在该指示信息指示AAA服务器中用户签约信息与HSS中对应的用户签约信息一致时，确定AAA服务器中用户签约信息有效。进一步的，可以使用AAA服务器中的用户签约信息对对应用户鉴权。
在本发明实施例的一个优选实施方式中，上述发送模块30，还设置为在上述指示信息指示AAA服务器中用户签约信息与HSS中对应的用户签约信息不一致时，向HSS发送用于获取HSS中对应的用户签约信息的请求。上述接收模块40，还设置为接收HSS响应该请求发送的HSS中对应的用户签约信息和该用户签约信息的标识。进一步的，可以使用接收到的用户签约信息对对应用户鉴权。
可以预料的是，本发明实施例的方法及装置可以通过计算机程序单元实现。本发明实施例的上述方法、装置可以在HSS或AAA服务器中实现，也可以在设备或装置中实现。
本发明实施例还提供了一种设备，该设备可以包括处理器、存储介质以及其他通用部件。实现上述方法、装置的计算机程序单元可以存储在该存储介质中，处理器可以执行该计算机程序单元。
图5是根据本发明实施例的用户签约信息的传递系统的示意图，如图5所示，该系统包括：AAA服务器1和HSS服务器2。其中，AAA服务器1可以包括：处理器10和存储介质12，存储介质12中可以存储上述用户签约信息的请求方法的计算机程序指令，处理器10可以执行该计算机程序指令。HSS服务器2可以包括：处理器20和存储介质22，存储介质22中可以存储上述用户签约信息的响应方法的计算机程序指令，处理器20可以执行该计算机程序指令。
下面结合图5所示的系统，对本发明实施例AAA从HSS传递用户签约信息的方法进行描述。
优选实施方式一
该优选实施方式中，AAA服务器向HSS发送请求消息，在请求消息中携带AAA服务器中用户签约信息的标识，HSS将HSS中对应的用户签约信息的标识发给AAA服务器，由AAA服务器比较两个标识是否相同，并根据比较的结果进行后续处理。
图6是根据本发明实例优选实施方式一的用户签约信息的获取方法的流程图，如图6所示，该方法包括步骤S602至步骤S612。
步骤S602，AAA服务器向HSS发送请求消息，在该请求消息中携带用户签约信息的标识。
在该优选实施方式中，可以是在用户上线时，向HSS发送上述请求消息，请求该用户的用户签约信息。也可以是在需要更新AAA服务器中用户签约信息时，触发向HSS发送上述消息。但该优选实施方式不限于此。
步骤S604，HSS接收上述请求消息，向AAA服务器发送响应消息，在响应消息中携带HSS中对应的用户签约信息的标识。
步骤S606，AAA服务器接收HSS服务器发送的响应消息，比较AAA服务器中的用户签约信息的标识与HSS中对应的用户签约信息的标识是否一致，如果一致，确定AAA服务器中的用户签约信息有效。
步骤S608，如果不一致，向HSS发送用于请求HSS中对应的用户签约信息的请求。
步骤S610，HSS接收上述请求，并向AAA服务器发送携带有HSS中对应的用户签约信息的响应。
步骤S612，AAA服务器接收上述响应，从该响应中得到用户签约信息，进一步的可以删除原先保存的用户签约信息。
优选实施方式二
该优选实施方式中，AAA服务器向HSS发送请求消息，在请求消息中携带AAA服务器中用户签约信息的标识，HSS将AAA服务器中用户签约信息的标识与HSS中对应的用户签约信息的标识进行比较，并向AAA服务器发送两者是否一致的指示，由AAA服务器根据该指示进行后续处理。
图7是根据本发明实例优选实施方式二的用户签约信息的获取方法的流程图，如图7所示，该方法包括步骤S702至步骤S704。
步骤S702，AAA服务器向HSS发送请求消息，在该请求消息中携带用户签约信息的标识。
在该优选实施方式中，可以是在用户上线时，向HSS发送上述请求消息，请求该用户的用户签约信息。也可以是在需要更新AAA服务器中用户签约信息时，触发向HSS发送上述消息。但该优选实施方式不限于此。
步骤S704，HSS接收上述请求消息，将AAA服务器中用户签约信息的标识与HSS中对应的用户签约信息的标识进行比较，并向AAA服务器发送响应消息，响应消息中携带两者是否一致的指示信息。
优选地，上述步骤704中，在两者不一致的情况下，还可以携带HSS中对应的用户签约信息。当然，HSS也可以主动通过其他消息将HSS中对应的用户签约信息发送给AAA服务器，并不限于在上述响应消息中。
步骤S706，AAA服务器接收HSS服务器发送的响应消息，根据上述指示信息判断是否需要更新AAA服务器中用户签约信息。如果一致，确定AAA服务器中的用户签约信息有效。
步骤S708，如果不一致，向HSS发送用于请求HSS中对应的用户签约信息的请求。
优选地，如果在步骤S704中携带有HSS中对应的用户签约信息，则步骤S708至步骤S712可以省略。
步骤S710，HSS接收上述请求，并向AAA服务器发送携带有HSS中对应的用户签约信息的响应。
步骤S712，AAA服务器接收上述响应，从该响应中得到用户签约信息，进一步的可以删除原先保存的用户签约信息。
优选实施方式三
该优选实施方式中，AAA服务器向HSS发送请求消息，在请求消息中携带AAA服务器中用户签约信息的标识，HSS将AAA服务器中用户签约信息的标识与HSS中对应的用户签约信息的标识进行比较，并在不一致的情况下，向AAA服务器发送HSS中对应的用户签约信息，在一致的情况下，发送指示信息。
图8是根据本发明实例优选实施方式三的用户签约信息的获取方法的流程图，如图8所示，该方法包括步骤S802至步骤S806。
步骤S802，AAA服务器向HSS发送请求消息，在该请求消息中携带用户签约信息的标识。
在该优选实施方式中，可以是在用户上线时，向HSS发送上述请求消息，请求该用户的用户签约信息。也可以是在需要更新AAA服务器中用户签约信息时，触发向HSS发送上述消息。但该优选实施方式不限于此。
步骤S804，HSS接收上述请求消息，将AAA服务器中用户签约信息的标识与HSS中对应的用户签约信息的标识进行比较，并向AAA服务器发送响应消息，如果一致则携带指示一致的指示信息，如果不一致，则携带HSS中对应的用户签约信息。
优选地，上述步骤804中，HSS也可以主动通过其他消息将HSS中对应的用户签约信息发送给AAA服务器，并不限于在上述响应消息中。
步骤S806，AAA服务器接收HSS服务器发送的响应消息。
下面以一个具体实例对本发明实施例进行描述。
在本实例中，利用数据版本号来标识AAA所持有的用户签约信息的新旧及是否被改动过，在实际运营过程中，用户签约信息是比较稳定的，每次上线时签约数据与前一次的签约数据以极高概率保持不变的。
上述数据版本号可以是表示数据修改的时间，或数据修改的递增序列号等各种方式，只要能区分出是否变动即可。
HSS发给AAA的用户签约信息在AAA侧缓存，同时保存该签约数据的版本号。HSS在修改用户签约信息时更新该用户签约数据的版本号。
HSS在收到AAA的获取用户签约信息的请求时，检查请求中的版本号字段，如果与本地的数据版本号相同，则不必下发Non-3GPP-User-Data等与版本号相关的信息。同时在SAA中增加数据版本号AVP，版本号一致。至于通过什么方式表明HSS认可SAR请求中的版本号，本实施例不做约束，例如此处描述的通过相同AVP带回相同的数据版本号取值。
HSS在收到AAA的获取用户签约信息的请求时，检查请求中的版本号字段，如果与本地的数据版本号不同，则下发Non-3GPP-User-Data等签约信息，在SAA中需要增加数据版本号AVP，其值为HSS侧该用户的数据版本号。
对于AAA与HSS，任一方在不支持此功能时，忽略数据版本号AVP字段即可。不影响正常交互流程。
图9是根据本发明实施例AAA服务器与HSS间SAR/SAA消息的示意图，如图9所示，包括：
步骤S902，第一次接入，AAA发送SAR请求用户数据，携带用户数据版本号(User_Data_Version)(后简称UDV)为0。
步骤S904，HSS返回用户签约数据，并携带UDV＝1456237850。
步骤906，第二次接入，AAA发送SAR请求用户数据，携带UDV＝1456237850。
步骤S908，HSS检查该用户签约数据最新版本与请求版本一致，发送SAA，其中UDV＝1456237850，不携带Non-3GPP-User-Data。
步骤S910，HSS修改该用户签约数据。
步骤S912，第三次接入，AAA发送SAR请求用户数据,携带UDV＝1456237850。
步骤S914，HSS检查该用户签约数据最新版本比请求版本要新，发送SAA，其中UDV为新版本号1456238240，同时携带Non-3GPP-User-Data。
在上述步骤S904中，AAA收到HSS具有新版本号的SAA响应时，AAA保存此版本号及SAA中的Non-3GPP-User-Data。
在上述步骤S906及S912中，在用户新接入时，AAA向HSS发送SAR获取用户签约信息前需要检索此前保存的该用户签约信息及其版本号。
在上述步骤S908中，这里只是给出了一种表示请求方拥有的已经是最新数据的方法，也可用其他方式在应答中标志。步骤描述中所说的User_Data_Version只是举例，并不做名称限制。
从以上的描述中，可以看出，本发明实现了如下技术效果：整体上降低了AAA服务器和HSS之间传递用户签约信息占用的带宽。
显然，本领域的技术人员应该明白，上述的本发明的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本发明不限制于任何特定的硬件和软件结合。
以上所述仅为本发明的优选实施例而已，并不用于限制本发明，对于本领域的技术人员来说，本发明可以有各种更改和变化。凡在本发明的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。
工业实用性
如上所述，本发明实施例提供的一种用户签约信息的响应、请求方法及装置，具有以下有益效果：整体上降低了AAA服务器和HSS之间传递用户签约信息占用的带宽。

Claims (21)

  1. 一种用户签约信息的响应方法，包括：
    接收认证授权计费服务器AAA服务器发送的请求消息，其中，所述请求消息中携带有所述AAA服务器中第一用户签约信息的标识，用户签约信息的标识用于区分同一用户内容不同的用户签约信息；
    根据所述第一用户签约信息的标识和HSS中对应的第二用户签约信息的标识，向所述AAA服务器发送响应消息。
  2. 根据权利要求1所述的方法，其中，根据所述第一用户签约信息的标识和HSS中对应的第二用户签约信息的标识，向所述AAA服务器发送响应消息，包括：
    向所述AAA服务器发送所述响应消息，其中，所述响应消息中携带有所述第二用户签约信息的标识。
  3. 根据权利要求2所述的方法，其中，还包括：
    响应所述AAA服务器接收到所述响应消息后的请求，向所述AAA服务器发送所述第二用户签约信息。
  4. 根据权利要求1所述的方法，其中，根据所述第一用户签约信息的标识和HSS中对应的第二用户签约信息的标识，向所述AAA服务器发送响应消息，包括：
    判断所述第一用户签约信息的标识与所述第二用户签约信息的标识是否一致；
    向所述AAA服务器发送所述响应消息，其中所述响应消息中携带有指示所述第一用户签约信息与所述第二用户签约信息是否一致的指示信息。
  5. 根据权利要求4所述的方法，其中，
    如果不一致，向所述AAA服务器发送所述响应消息，其中所述响应消息中携带有所述第二用户签约信息和/或所述第二用户签约信息的标识。
  6. 根据权利要求1至5中任一项所述的方法，其中，所述标识包括以下至少之一：版本号、修改时间、修改序列号。
  7. 一种用户签约信息的请求方法，包括：
    向用户归属服务器HSS发送请求消息，其中所述请求消息中携带有第一用户签约信息的标识，用户签约信息的标识用于区分同一用户内容不同的用户签约信息；
    接收所述HSS根据第一用户签约信息的标识和所述HSS中对应的第二用户签约信息的标识发送的响应消息；
    根据所述响应消息判断所述第一用户签约信息是否有效。
  8. 根据权利要求7所述的方法，其中，所述响应消息中携带有所述第二用户签约信息的标识；根据所述响应消息判断所述第一用户签约信息是否有效，包括：
    判断所述第一用户签约信息的标识与所述第二用户签约信息的标识是否一致；
    如果一致，确定所述第一用户签约信息有效。
  9. 根据权利要求8所述的方法，其中，还包括：
    如果不一致，向所述HSS发送用于获取所述第二用户签约信息的请求；
    接收所述HSS响应所述请求发送的所述第二用户签约信息和所述第二用户签约信息的标识。
  10. 根据权利要求7所述的方法，其中，所述响应消息中携带有指示所述第二用户签约信息与所述第一用户签约信息是否一致的指示信息；根据所述响应消息判断所述第一用户签约信息是否有效，包括：
    如果所述指示信息指示所述第一用户签约信息与所述第二用户签约信息一致，确定所述第一用户签约信息有效。
  11. 根据权利要求10所述的方法，其中，
    如果所述指示信息指示所述第一用户签约信息与所述第二用户签约信息不一致，向所述HSS发送用于获取所述第二用户签约信息的请求；
    接收所述HSS响应所述请求发送的所述第二用户签约信息和所述第二用户签约信息的标识。
  12. 一种用户签约信息的响应装置，包括：
    接收模块，设置为接收认证授权计费服务器AAA服务器发送的请求消息，其中，所述请求消息中携带有所述AAA服务器中第一用户签约信息的标识，用户签约信息的标识用于区分同一用户内容不同的用户签约信息；
    发送模块，设置为根据所述第一用户签约信息的标识和HSS中对应的第二用户签约信息的标识，向所述AAA服务器发送响应消息。
  13. 根据权利要求12所述的装置，其中，所述发送模块，设置为向所述AAA服务器发送所述响应消息，其中，所述响应消息中携带有所述第二用户签约信息的标识。
  14. 根据权利要求13所述的装置，其中，所述发送模块，还设置为响应所述AAA服务器接收到所述响应消息后的请求，向所述AAA服务器发送所述第二用户签约信息。
  15. 根据权利要求12所述的装置，其中，所述发送模块包括：
    判断单元，设置为判断所述第一用户签约信息的标识与所述第二用户签约信息的标识是否一致；
    发送单元，设置为向所述AAA服务器发送所述响应消息，其中所述响应消息中携带有指示所述第一用户签约信息与所述第二用户签约信息是否一致的指示信息。
  16. 根据权利要求15所述的装置，其中，
    所述发送单元，还设置为在所述第一用户签约信息与所述第二用户签约信息不一致的情况下，向所述AAA服务器发送所述响应消息，其中所述响应消息中携带有所述第二用户签约信息和/或所述第二用户签约信息的标识。
  17. 一种用户签约信息的请求装置，包括：
    发送模块，设置为向用户归属服务器HSS发送请求消息，其中所述请求消息中携带有第一用户签约信息的标识，用户签约信息的标识用于区分同一用户内容不同的用户签约信息；
    接收模块，设置为接收所述HSS根据第一用户签约信息的标识和所述HSS中对应的第二用户签约信息的标识发送的响应消息；
    确定模块，设置为根据所述响应消息判断所述第一用户签约信息是否有效。
  18. 根据权利要求17所述的装置，其中，所述响应消息中携带有所述第二用户签约信息的标识；所述确定模块包括：
    判断单元，设置为判断所述第一用户签约信息的标识与所述第二用户签约信息的标识是否一致；
    确定单元，设置为在所述第一用户签约信息的标识与所述第二用户签约信息的标识一致的情况下，确定所述第一用户签约信息有效。
  19. 根据权利要求18所述的装置，其中，
    所述发送模块，还设置为在所述第一用户签约信息的标识与所述第二用户签约信息的标识不一致的情况下，向所述HSS发送用于获取所述第二用户签约信息的请求；
    所述接收模块，还设置为接收所述HSS响应所述请求发送的所述第二用户签约信息和所述第二用户签约信息的标识。
  20. 根据权利要求17所述的装置，其中，所述响应消息中携带有指示所述第二用户签约信息与所述第一用户签约信息是否一致的指示信息；
    所述确定模块，设置为在所述指示信息指示所述第一用户签约信息与所述第二用户签约信息一致时，确定所述第一用户签约信息有效。
  21. 根据权利要求20所述的装置，其中，
    所述发送模块，还设置为在所述指示信息指示所述第一用户签约信息与所述第二用户签约信息不一致时，向所述HSS发送用于获取所述第二用户签约信息的请求；
    所述接收模块，还设置为接收所述HSS响应所述请求发送的所述第二用户签约信息和所述第二用户签约信息的标识。
PCT/CN2014/088676 2014-05-07 2014-10-15 用户签约信息的响应、请求方法及装置 WO2015169055A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410191083.7A CN105101197A (zh) 2014-05-07 2014-05-07 用户签约信息的响应、请求方法及装置
CN201410191083.7 2014-05-07

Publications (1)

Publication Number Publication Date
WO2015169055A1 true WO2015169055A1 (zh) 2015-11-12

Family

ID=54392084

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2014/088676 WO2015169055A1 (zh) 2014-05-07 2014-10-15 用户签约信息的响应、请求方法及装置

Country Status (2)

Country Link
CN (1) CN105101197A (zh)
WO (1) WO2015169055A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101064630A (zh) * 2006-04-24 2007-10-31 华为技术有限公司 一种数据同步方法及系统
CN101222451A (zh) * 2008-01-28 2008-07-16 北京亿企通信息技术有限公司 一种在即时通信工具中获取联系人数据的方法
CN101335641A (zh) * 2007-06-29 2008-12-31 华为技术有限公司 一种升级设备的方法、装置及系统
CN101594607A (zh) * 2008-05-27 2009-12-02 华为技术有限公司 分组数据网络网关信息的维护方法、系统及设备
CN101789912A (zh) * 2009-01-23 2010-07-28 华为技术有限公司 更新分组数据网络网关信息的方法、装置及系统

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1324909C (zh) * 2003-10-15 2007-07-04 华为技术有限公司 认证服务器与归属位置寄存器数据同步方法
CN101790150B (zh) * 2009-01-23 2012-01-25 华为技术有限公司 一种更新接入点名称签约配置的方法及装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101064630A (zh) * 2006-04-24 2007-10-31 华为技术有限公司 一种数据同步方法及系统
CN101335641A (zh) * 2007-06-29 2008-12-31 华为技术有限公司 一种升级设备的方法、装置及系统
CN101222451A (zh) * 2008-01-28 2008-07-16 北京亿企通信息技术有限公司 一种在即时通信工具中获取联系人数据的方法
CN101594607A (zh) * 2008-05-27 2009-12-02 华为技术有限公司 分组数据网络网关信息的维护方法、系统及设备
CN101789912A (zh) * 2009-01-23 2010-07-28 华为技术有限公司 更新分组数据网络网关信息的方法、装置及系统

Also Published As

Publication number Publication date
CN105101197A (zh) 2015-11-25

Similar Documents

Publication Publication Date Title
CN115442423A (zh) 发现由网络存储库功能提供的服务的方法
JP2003331045A (ja) ポータルサイトサーバシステム、ポータルサイト方法、およびポータルサイトプログラム
US8977758B2 (en) Service bus system, service bus device, and method for assuring connection uniqueness
EP2685679B1 (en) Method, device and system for synchronizing contact information
US10064044B2 (en) Method and apparatus for determining roaming status of terminal, terminal, and server
CN110049031B (zh) 一种接口安全认证方法及服务器、认证中心服务器
US11641356B2 (en) Authorization apparatus, data server and communication system
US20140149194A1 (en) Granting of benefits
CN105472597B (zh) 应用的注册方法及装置
CN112367666B (zh) 一种5G核心网中pNF通过NRF认证cNF的方法、装置及系统
US20110264767A1 (en) Interactive processing method and apparatus between content-id management servers
CN114221959A (zh) 服务共享方法、装置和系统
CN106657140B (zh) 应用授权方法及装置
CN101567879A (zh) 处理终端请求的方法、服务器、设备和系统
CN109842482B (zh) 一种信息同步方法、系统及终端设备
US11777742B2 (en) Network device authentication
CN111371825A (zh) 一种基于http2.0协议的负载均衡方法、装置及设备
CN110401709A (zh) 一种即时通讯应用中会话的处理方法、装置和存储介质
WO2015169055A1 (zh) 用户签约信息的响应、请求方法及装置
CN113055254B (zh) 一种地址配置方法、装置、接入服务器及存储介质
WO2016095472A1 (zh) 资源操作请求的处理方法及装置
EP3451602A1 (en) Registration management method and device
CN110858201B (zh) 数据处理方法及系统、处理器、存储介质
CN114339716A (zh) 签约数据传输方法、系统和服务器
CN111988298A (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: 14891413

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

Country of ref document: EP

Kind code of ref document: A1