CN111885590B

CN111885590B - Correlation method and system

Info

Publication number: CN111885590B
Application number: CN202010745160.4A
Authority: CN
Inventors: 任驰; 马瑞涛; 陈婉珺
Original assignee: China United Network Communications Group Co Ltd
Current assignee: China United Network Communications Group Co Ltd
Priority date: 2020-07-29
Filing date: 2020-07-29
Publication date: 2022-04-08
Anticipated expiration: 2040-07-29
Also published as: CN111885590A

Abstract

The embodiment of the invention provides a correlation method and a system, wherein the method comprises the following steps: the AS acquires a service order request in the target application, wherein the service order request is a request sent by the UE by using the target account; the AS sends a target AAID and a target URSP association request to the PCF according to the service subscription request, wherein the association request carries a target flow descriptor of a target application, the target AAID and MSMDN currently used by UE, the target flow descriptor is consistent with a flow descriptor in the URSP configured for the target application in the PCF, the target AAID is an account identifier generated by the target application and uniquely corresponding to a target account, the MSMDN is used for positioning the UE, the association request is used for indicating the PCF to search the target URSP which is the same AS the target flow descriptor and is not signed under any SUIP to be associated with the target AAID, and the target URSP is issued to the UE corresponding to the MSMDN to be installed; and receiving a response that the association between the target AAID and the target URSP sent by the PCF is successful.

Description

Correlation method and system

Technical Field

The present application relates to the field of 5G communication technologies, and in particular, to an association method and system.

Background

In the process of gradually evolving from a fourth generation (4th generation, abbreviated as 4G) network to a fifth generation (5th generation, abbreviated as 5G) network, the application types of the mobile network start to show an explosive growth trend, and along with the gradual enrichment of mobile service contents and scenes, the demands of various services on the network start to show significant differences. In order to meet differentiated experience guarantee aiming at diversified services and more efficiently utilize limited network resources, the 5G network defines technologies such as network slices, services and session continuity modes and the like, can respectively face different user groups, and different service types are respectively adapted to relevant service management and control strategies, so that differentiated hierarchical management of the services is realized.

The Function of providing different policies for different services is mainly implemented by a Policy Control Function (PCF) in a 5G core network through a User Equipment (UE) Routing Selection Policy (URSP) subscribed to different services for different users, where a typical URSP Policy includes a traffic descriptor of a target application to guide the UE to identify and match a target application traffic, and configures different network Function application policies for the target application, such as a network slice Selection Policy (including one or more network slice identifiers), a service and session continuity mode Selection Policy, and the like. When the UE recognizes that the application matching the traffic descriptor in the URSP is initiated, the session management attribute included in the URSP is applied, and it is tried to determine whether there is an established Protocol Data Unit (PDU) session that can be matched, or if not, a PDU session is created based on the session management attribute included in the URSP.

However, the current URSP rule can only be configured in user granularity, that is, the issued URSP policy is bound with a Subscription Permanent Identifier (SUPI) or a mobile phone number of a user, and it is difficult to achieve finer-grained control. In the application level, most applications are managed and controlled through application accounts, and the application accounts are not bound with the mobile phone numbers of users in many cases, in this case, if a URSP rule for specific service guarantee is issued and activated for a user, all the accounts logged in by the user through the UE can enjoy the service guarantee policy specified by the URSP, which is greatly different from the service sale mode planned by a third-party service provider, and is not beneficial to landing and developing corresponding business cooperation.

In the related art, an effective solution is not available at present for the problem that all accounts logged in by a user through the UE can enjoy a service provisioning policy specified by a URSP and further do not conform to a service sales mode planned by a third-party service provider because the URSP rule issued by the user for a specific service provisioning is directly bound to the UE.

Disclosure of Invention

The embodiment of the application provides an association method and an association system, which at least solve the problem that in the related technology, URSP rules issued by a user for specific service guarantee can be directly bound to UE, so that all accounts logged in by the user through the UE can enjoy service guarantee strategies designated by the URSP, and further the service sale mode planned by a third-party service provider is not met.

In order to achieve the purpose, the invention adopts the following technical scheme:

in a first aspect, the present application provides an association method, including: an application server AS acquires a service order request in a target application, wherein the service order request is a request sent by user equipment UE by using a target account; the AS sends a target Application Account ID (AAID) and an association request of a target user equipment routing management policy (URSP) to a policy control function module (PCF) according to the service subscription request, wherein the association request carries a target traffic descriptor of the target Application, the target AAID and a telephone number (Mobile Subscriber International ISDN/PSTN number, MSIMDN) currently used by the UE, the target traffic descriptor is consistent with a traffic descriptor in the URSP configured for the target Application in the PCF, the target AAID is an Account ID generated by the target Application and uniquely corresponding to the target Account, the MSIMDN is used for locating the UE, the association request is used for indicating that the PCF searches for the target URSP which is the same AS the target traffic descriptor and is not signed under any permanent subscription identity (SUIP) to be associated with the target AAID, the target URSP is issued to the UE corresponding to the MSIMDN for installation; and receiving a response that the association between the target AAID and the target URSP sent by the PCF is successful.

Optionally, before the AS obtains the subscription request of the service in the target application, the method further includes: the AS receives a registration request of registering a target account in the target application by the UE; and the AS generates an AAID uniquely corresponding to the target account according to the registration request.

Optionally, after the AS generates an AAID uniquely corresponding to the target account according to the registration request, the method further includes: and the AS adds the AAID of the user in a data packet sent to the target account.

In a second aspect, the present application provides an association method, including: a policy control function module PCF receives an association request of a target application account identifier AAID and a target user equipment routing management policy URSP, which is sent by an application server AS, wherein the association request carries a target traffic descriptor of a target application, the target AAID, and a phone number MSIMDN currently used by user equipment UE logging in to the target account, the target traffic descriptor is consistent with a traffic descriptor in the URSP configured for the target application in the PCF, the target AAID is an account identifier generated by the target application and uniquely corresponding to the target account, and the MSIMDN is used to locate the UE; the PCF searches the target URSP which is the same as the target traffic descriptor and is not signed under any signed permanent identification SUIP according to the association request, and associates the target URSP with the target AAID; the PCF sends a URSP updating request to an access and mobility management function (AMF), wherein the URSP updating request carries the target URSP and the MSMDN, and the URSP updating request is used for indicating the AMF to send the target URSP to the UE corresponding to the MSMDN for installation; and the PCF sends a response that the association between the target AAID and the target URSP is successful to the AS.

Optionally, before sending a response that the association is successful to the AS, the method further includes: receiving a URSP update completion response sent by the AMF, wherein the URSP update completion response is used for indicating that the UE completes the installation of the target URSP at an operating system layer.

According to another embodiment of the present application, there is also provided an association method including: user Equipment (UE) sends a service subscription request to a target application by using a target account; the UE receives a target user equipment routing Management policy (URSP) issued by an Access and Mobility Management Function module (AMF for short), wherein the target URSP is issued to the AMF by a policy control Function module (PCF), the target URSP is associated with a target AAID by the PCF, the target AAID is an account identifier which is generated by the target application and is uniquely corresponding to the target account, and the target AAID and the target URSP are issued to the PCF by an Application Server (AS) of the target application according to the service order request; the UE installs the target URSP on an operating system layer; and the UE sends a URSP update completion response to the AMF, wherein the URSP update completion response is used for indicating that the PCF sends a response that the association between the target AAID and the target URSP is successful to the AS.

Optionally, after the UE installs the target URSP at an operating system layer, the method further includes: the UE initiates a service by using the target account, wherein an uplink data packet corresponding to the service carries the characteristic information of the service, and the characteristic information of the service at least comprises one of the following information: traffic descriptor information in the URSP corresponding to the service, and a target AAID of the target account; the UE matches the service to a target URSP associated with the target AAID according to the flow descriptor information in the URSP corresponding to the service; and the UE initiates a Protocol Data Unit (PDU) session establishment request to a core network, wherein the session establishment request carries the content specified by the routing descriptor in the target URSP, and the session establishment request is used for indicating the core network to complete the establishment of the PDU session according to the content specified by the routing descriptor.

Optionally, the traffic descriptor includes information of at least one of the following: target IP address, target domain name of access, APP ID of target application.

In a third aspect, the present application provides an association system, comprising:

the user equipment UE is used for sending a service subscription request to a target application by using a target account;

an application server AS, configured to send, to a policy control function module PCF, an association request of a target application account identifier AAID and a target user equipment routing management policy URSP according to the service subscription request, where the association request carries a target traffic descriptor of a target application, the target AAID, and a telephone number MSIMDN currently used by a user equipment UE that logs in the target account, where the target traffic descriptor is consistent with a traffic descriptor in the URSP configured for the target application in the PCF, the target AAID is an account identifier uniquely corresponding to the target account generated by the target application, and the MSIMDN is used to locate the UE;

the PCF is configured to search the target URSP that is the same as the target traffic descriptor and is not signed under any subscription permanent identity SUIP according to the association request, associate the target URSP with the target AAID, and send a URSP update request to an access and mobility management function module AMF, where the URSP update request carries the target URSP and the MSIMDN;

the AMF is used for issuing the target URSP to the UE corresponding to the MSIMDN;

the UE is also used for installing the target URSP on an operating system layer and sending a URSP updating completion response to the AMF;

the AMF is further configured to send the URSP update completion response to the PCF;

and the PCF is also used for sending a response that the association between the target AAID and the target URSP is successful to the AS after receiving the update completion response of the URSP.

In a fourth aspect, the present application provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program is arranged to perform the steps of any of the above method embodiments when executed.

In a fifth aspect, the present application provides an electronic device comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the computer program to perform the steps of any of the above method embodiments.

For a detailed description of the second to fifth aspects and their various implementations in this application, reference may be made to the detailed description of the first aspect and its various implementations; moreover, the beneficial effects of the second aspect to the fifth aspect and the various implementation manners thereof may refer to the beneficial effect analysis of the first aspect and the various implementation manners thereof, and are not described herein again.

These and other aspects of the present application will be more readily apparent from the following description.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.

FIG. 1 is a flow chart of an alternative association method in accordance with an embodiment of the present application;

FIG. 2 is a flow chart of an alternative correlation method according to an embodiment of the present application;

FIG. 3 is a flow chart of an alternative correlation method according to an embodiment of the present application;

FIG. 4 is a block diagram of an alternative association system in accordance with an embodiment of the subject application;

FIG. 5 is an interaction flow diagram of an alternative association method according to an embodiment of the application;

fig. 6 is an interaction flow diagram of URSP rule matching performed by an optional UE according to an embodiment of the present application;

fig. 7 is a schematic structural diagram of an alternative electronic device according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

The terms "first", "second" and "first" are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of the present invention, "a plurality" means two or more unless otherwise specified.

The embodiment of the application provides a correlation method. Fig. 1 is a flowchart of an alternative association method according to an embodiment of the present application, as shown in fig. 1, the method includes:

step S102, an application server AS acquires a service order request in a target application, wherein the service order request is a request sent by user equipment UE by using a target account;

step S104, AS sends a target application account identifier AAID and a correlation request of a target user equipment routing management strategy URSP to a strategy control function module PCF according to a service subscription request, wherein the correlation request carries a target flow descriptor of a target application, the target AAID and a telephone number MSIMDN currently used by UE, the target flow descriptor is consistent with a flow descriptor in the URSP configured for the target application in the PCF, the target AAID is an account identifier which is generated by the target application and uniquely corresponds to the target account, the MSIMN is used for positioning the UE, the correlation request is used for indicating that PCF searches for the target URSP which is the same AS the target flow descriptor and is not signed under any signed permanent identifier to be correlated with the target AAID, and the target URSP is issued to the UE corresponding to the MSIMDN for installation;

step S106, receiving the response of successful association between the target AAID and the target URSP sent by the PCF.

By the method, after the AS acquires the service ordering request sent by the UE in the target application by using the target account, the AS sends the association request of the target AAID and the target URSP to the PCF according to the service ordering request, and then the PCF associates the target AAID and the target URSP and sends the association request to the corresponding UE to install the target URSP. The method and the device solve the problem that in the 5G field, URSP rules for specific service guarantee issued to a user can be directly bound to the UE, so that all accounts logged in by the user through the UE can enjoy the service guarantee strategy appointed by the URSP, and further the service sale mode planned by a third-party service provider is not met. By directly binding the AAID of the target account and the corresponding target URSP, the URSP can correspond to a specific login account, personalized customized services can be performed for different login accounts, flexible control of the application on services corresponding to different accounts is realized, and a service sale mode planned by a third-party service provider is better met.

It should be noted that, the application scenario of the embodiment of the present application may be based on a 5G system architecture. The network entities mainly involved include: the UE is used for storing one or more applications and realizing the normal communication of the applications by establishing a PDU session, wherein the UE needs to set the PDU type of the PDU session request in the process of establishing the PDU session; the AMF is used for being responsible for mobility management of the UE, and comprises registration, location updating and the like; and the PCF is used for storing the UE strategies comprising a user equipment routing strategy URSP.

Wherein the aforementioned UE policy may be, but is not limited to, URSP, it can be derived from the description of URSP in 5G protocol that the PCF stores the URSP, and the DNN selection policy in the URSP is used to select one or more DNNs for the PDU session. One or more rules corresponding to each application may be included in the URSP, and the rules may be made by an operator or made by an operator according to the requirements of an application service provider.

The Service-level Network slice access Selection control is implemented by a URSP Policy signed in a PCF deployed in a 5G core Network, the content of the URSP is defined in a 3GPP standard specification TS 23.503, the URSP rule defines that Service identification and rule matching are performed through a flow descriptor (a target IP address, an accessed target domain name, or an APP ID of a target application), and the URSP rule is associated with a corresponding Network slice Selection Policy component, and the Network slice Selection Policy may include one or more Single Network slice Selection auxiliary Information (S-NSSAI for short), a Service and Session Continuity Selection Policy (SSCMSP for short), and the like, so as to implement differentiated control policies for different services of different users. The URSP rule is issued to the UE by PCF through AMF in the UE registration process, and is installed in the UE operating system, when the UE detects that the user uses the service defined by the flow descriptor in the URSP, the URSP policy corresponding to the service is executed immediately.

The URSP defined by the 5G standard is signed and configured according to user granularity, namely a set of URSP policies are associated with a Subscription Permanent Identifier (SUPI) of a user, and in order to meet the requirement of flexible application control, the embodiment of the application provides a method for associating URSP rules with an account number of the user in a certain application, so as to realize more slice access policy control functions.

Optionally, before the step S102, the method further includes:

s1, the AS receives a registration request of registering a target account in a target application by the UE;

and S2, the AS generates an AAID uniquely corresponding to the target account according to the registration request.

Optionally, after the AS generates an AAID uniquely corresponding to the target account according to the registration request, the method further includes:

the AS adds the AAID of the user to the data packet sent to the target account.

It should be noted that, when a user registers and generates an application account (for example, the target account) in an application, a third-party service provider where the application is located should generate a globally unique application account identification AAID for the account. When the UE and the network transmit the corresponding application traffic, the application side should add the AAID of the user in a Hyper Text Transfer Protocol (HTTP) packet header of the corresponding data stream for subsequent URSP rule matching. An operator having a formal business partnership with the third party application provider configures in the PCF a URSP policy not associated with any user SUPI for applications for which the third party service provider wishes to obtain specific slice access capabilities.

According to another embodiment of the present application, there is also provided an association method, and fig. 2 is a flowchart of another optional association method in the embodiment of the present application, as shown in fig. 2, the method includes:

step S202, a policy control function module PCF receives a target application account identification AAID sent by an application server AS and an association request of a target user equipment routing management policy URSP, wherein the association request carries a target flow descriptor of a target application, the target AAID and a telephone number MSIMDN currently used by user equipment UE for logging in the target account, the target flow descriptor is consistent with a flow descriptor in the URSP configured for the target application in the PCF, the target AAID is an account identification which is generated by the target application and uniquely corresponds to the target account, and the MSIMDN is used for positioning the UE;

step S204, PCF searches the target URSP which is the same as the target flow descriptor and is not signed under any signing permanent identification SUIP according to the association request, and associates the target URSP with the target AAID;

step S206, PCF sends URSP updating request to access and mobile management function module AMF, wherein, the URSP updating request carries target URSP and MSIMDN, the URSP updating request is used for indicating AMF to issue target URSP to UE corresponding to MSIMDN for installation;

in step S208, the PCF sends a response to the AS that the association between the target AAID and the target URSP is successful.

Optionally, before step S208, the method further comprises: and receiving a URSP update completion response sent by the AMF, wherein the URSP update completion response is used for indicating that the UE completes the installation of the target URSP at the operating system layer.

According to another embodiment of the present application, there is also provided an association method, and fig. 3 is a flowchart of another optional association method in an embodiment of the present application, as shown in fig. 3, the method includes:

step S302, user equipment UE sends a service order request to a target application by using a target account;

step S304, UE receives a target user equipment routing management strategy URSP issued by an access and mobility management function module AMF, wherein the target URSP is issued to the AMF by a strategy control function module PCF, the target URSP is associated with a target AAID by the PCF, the target AAID is an account identification which is generated by a target application and is uniquely corresponding to the target account, and the target AAID and the target URSP are issued to the PCF by an application server AS of the target application according to a service order request;

step S306, the UE installs the target URSP in an operating system layer;

step S308, the UE sends URSP update completion response to the AMF, wherein the URSP update completion response is used for indicating that the PCF sends the response that the association between the target AAID and the target URSP is successful to the AS.

It should be noted that, after the UE completes the URSP update, the current PDU session in progress should not be released immediately, and the updated URSP rule will take effect when the UE initiates a service for the same application next time (but to ensure the user experience, the application may optionally pop a corresponding prompt to the user, for example, "the service takes effect after logging in next time", and the specific application behavior is not limited in the embodiment of the present application).

When the UE initiates the service corresponding to the URSP by using the account purchased with the acceleration service next time, the UE matches the information contained in the service data packet with the AAID and the application descriptor in the URSP, and initiates the corresponding PDU session according to the content of the matched URSP rule.

Optionally, after the UE installs the target URSP at the operating system layer, the method further includes:

s1, the UE initiates a service by using the target account, wherein the uplink data packet corresponding to the service carries the characteristic information of the service, and the characteristic information of the service at least comprises one of the following: traffic descriptor information in URSP corresponding to a service, and a target AAID of a target account;

s2, the UE matches the service to the target URSP associated with the target AAID according to the flow descriptor information in the URSP corresponding to the service;

s3, UE initiates a protocol data unit PDU session establishment request to the core network, wherein, the session establishment request carries the content appointed by the routing descriptor in the target URSP, and the session establishment request is used for indicating the core network to complete the establishment of PDU session according to the content appointed by the routing descriptor.

Through the above description of the embodiments, those skilled in the art can clearly understand that the method according to the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but the former is a better implementation mode in many cases. Based on such understanding, the technical solutions of the present application may be embodied in the form of a software product, which is stored in a storage medium (e.g., ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal device (e.g., a mobile phone, a computer, a server, or a network device) to execute the method according to the embodiments of the present application.

According to another embodiment of the present application, there is also provided an association system, and fig. 4 is a block diagram of an optional association system in an embodiment of the present application, as shown in fig. 4, including:

a user equipment UE402, configured to send a service subscription request to a target application using a target account;

an application server AS404, configured to send, to a policy control function module PCF, an association request of a target application account identifier AAID and a target user equipment routing management policy URSP according to a service subscription request, where the association request carries a target traffic descriptor of a target application, the target AAID, and a telephone number MSIMDN currently used by a user equipment UE that logs in the target account, the target traffic descriptor is consistent with a traffic descriptor in the URSP configured for the target application in the PCF, the target AAID is an account identifier uniquely corresponding to the target account generated by the target application, and the MSIMDN is used to locate the UE;

PCF406, configured to search, according to the association request, the target URSP that is the same as the target traffic descriptor and is not signed under any subscription permanent identity SUIP, associate the target URSP with the target AAID, and send a URSP update request to access and mobility management function module AMF, where the URSP update request carries the target URSP and the MSIMDN;

the AMF408 is used for issuing the target URSP to the UE corresponding to the MSIMDN;

the UE402 is further configured to install the target URSP at an operating system layer, and send a URSP update completion response to the AMF;

AMF408 is further configured to send the URSP update complete response to the PCF;

PCF406 is further configured to send a response to the AS that the association between the target AAID and the target URSP was successful after receiving the URSP update complete response.

When a user activates an acceleration service through a purchase interface built in the application, the application server AS of the third party service provider should trigger a URSP association request to the operator PCF. Fig. 5 is an interaction flowchart of an optional association method according to an embodiment of the present application, and as shown in fig. 5, an interaction process in an association system includes:

0. a user orders an application acceleration service through an in-application purchase interface and triggers URSP updating;

AS initiates an association request of AAID and URSP to PCF in an operator network, wherein the association request carries a flow descriptor (IP triple or domain name or APP ID, and the flow descriptor is consistent with a flow descriptor in URSP pre-configured in PCF), an AAID corresponding to a user account, and a telephone number (MSISDN: Mobile Subscriber International ISD N/PSTN number) currently used by a user, and the MSISDN is mainly used for assisting an operator 5GC in positioning which specific UE the URSP should be issued to;

PCF searches URSP based on the application descriptor carried in AS request, and selects the same flow descriptor AS the AS request, and associates the URSP without any SUPI with the AAID. Such as: the application descriptor carried in the AS request is based on an IP triplet, the IP address is 123.456.789.001, the port number is 1212, the protocol type is UDP, on the premise that the operator and the third party application provider have an explicit cooperation agreement, the operator should sign up the application descriptor in advance in the PCF for the application of the cooperation object and also be the IP triplet, the destination IP address is 123.456.789.001, the port number is 1212, the protocol type is a URSP rule of UDP, and the rule does not belong to any user (SUPI) in the PCF configuration. In the association process, PCF adds the AAID in AS request to the URSP retrieved according to the traffic descriptor issued by AS, and the URSP rule after association should be in the form of the following table:

table 1 and examples of URSP rule content after AAID association

PCF sends URSP updating request to AMF, sends URSP rule associated with AAID to AMF, and carries MSISDN of user obtained from AS;

AMF finds out target UE according to MSISDN obtained from PCF, and issues updated URSP to UE;

5, the UE installs the updated URSP rule on the operating system level;

6, UE returns URSP update completion response to AMF;

AMF replies URSP updating completion response to PCF;

and 8, the PCF replies an AAID and URSP association success response to the AS.

When the UE completes the URSP update, the currently ongoing PDU session should not be released immediately, and the updated URSP rule will take effect the next time the UE initiates a service for the same application. When the UE initiates the service corresponding to the URSP by using the account purchased with the acceleration service next time, the UE matches the information contained in the service data packet with the AAID and the application descriptor in the URSP, and initiates the corresponding PDU session according to the content of the matched URSP rule. Fig. 6 is a flowchart illustrating alternative UE performing URSP rule matching according to an embodiment of the present application, and as shown in fig. 6, the flowchart includes:

UE uses the account number purchased with acceleration service to initiate service, at this time, the uplink service data packet initiated by the client applied at the UE side should contain corresponding service characteristic information, including information (such as IP triple, APP ID, FQDN domain name and the like) corresponding to the flow descriptor in the URSP rule, and AAID corresponding to the account number, the UE should match the service characteristics according to the internal mechanism of the UE, and match the installed URSP rule associated with the AAID;

2, UE initiates a PDU session establishment request to the 5G core network 5GC, and the request message carries the content (such as S-NSSAI, SSC Mode and the like) appointed by the routing descriptor in the matched URSP rule;

3.5 GC completes the establishment of PDU conversation based on the content of the routing descriptor carried in the UE request, including the selection of specific network element, the establishment of user plane path, etc.;

4.5 GC replies a PDU session establishment acceptance message to the UE to complete the PDU session establishment.

The URSP matching and application flow is applied each time the UE initiates a service by using the account subscribed with the acceleration service, until the acceleration service subscribed by the user expires, and the URSP rule corresponding to the acceleration service is not triggered even if the account not subscribed with the application acceleration service is installed on the UE with the URSP.

In order to better understand the technical solution in the embodiments of the present application, the embodiments of the present application are specifically described by the following application examples.

The operator a and the third-party service provider B reach a cooperative agreement for the service C developed thereunder, guarantee for providing access to a specific Network Slice for a paying user, the Network Slice Selection auxiliary Information (S-NSSAI: Single Network Slice Selection Assistance Information) corresponding to the Network Slice is 0x01, before the service is opened, the operator a should sign the URSP rule data for the service C in the PCF of the Network to which the operator a belongs, and the URSP rule does not belong to the SUPI of any existing user. The URSP after subscription is exemplified by the following table:

TABLE 2 URSP content examples for association with AAID

Wherein, the IP address and the port number are the server address and the port number of the application C (i.e. the destination address and the destination port accessed by the user when using the service), and the S-NSSAI is the S-NSSAI corresponding to the network slice for the operator a to provide the accelerated provisioning service for the service C, i.e. 0x 01.

When a certain user D registers an account in the service C, the third-party service provider B immediately generates an AAID for the account: 1A2B3C4D5E6F, when the user D does not purchase acceleration service, the AAID does not trigger any URSP update flow, and when the user purchases corresponding acceleration service through the internal purchase interface of the service C using the mobile phone number 11122223333, the AS of the third party service provider B immediately initiates an AAID and URSP association request to the operator network, where the request carries the traffic descriptor of the application C (AS in the traffic descriptor in table 2 above), the AAID of the current account of the user: 1A2B3C4D5E6F, and the MSISDN currently used by the user: 11122223333.

PCF searches based on the flow descriptor sent by AS, and inquires the signed pre-configured URSP rule AS shown in Table 2, PCF adds AAID information in the URSP rule based on the URSP rule in Table 2, and completes the association between URSP and AAID, the URSP rule after association is shown AS the following table:

TABLE 3 URSP content examples after AAID Association

PCF sends the related URSP rule and the user MSISDN number obtained from AS to AMF, AMF sends it to the corresponding UE, and completes the installation of URSP in the current UE.

Subsequently, when the user uses the current UE and uses the same account to initiate a service again, the UE shall perform matching of traffic characteristics based on the installed URSP rule, detect information in the service data packet, and when the IP triple included in the service data packet and the AAID are both matched with information in the URSP associated with the AAID, the UE will carry an S-NSSAI identifier specified by the URSP in a message initiating a corresponding PDU session establishment request, that is: 0x 01.

The above labels and numbers are all examples and are not intended to limit the embodiments of the present application.

The embodiment of the application defines the requirement that a third-party application provider needs to generate and add an application account ID in an application layer:

after a user registers an account, an application provider should generate a globally unique application account ID, namely an AAID;

in an application data packet interacted between the UE and the network, the third party application provider should add an AAID field in an HTTP header of the data packet.

The embodiment of the application also defines a URSP updating process triggered by ordering the service acceleration service through the user purchasing interface in the application, and the URSP updating process comprises the following steps:

the AS triggers an AAID and URSP association request to the PCF according to the user subscription action, and the content required to be contained in the request;

PCF according to AAID carried in AS sending request and applied flow descriptor carries out URSP and AAID association main process, that is PCF adds requested AAID to associated URSP rule and sends it to UE through AMF;

the URSP update procedure should not affect the currently ongoing service session, but should be performed and validated by the UE the next time the user initiates a service.

According to another aspect of the embodiments of the present application, there is also provided an electronic device for implementing the above-mentioned association method, which may be, but is not limited to, applied in a server. As shown in fig. 7, the electronic device comprises a memory 702 and a processor 704, wherein the memory 702 stores a computer program, and the processor 704 is configured to execute the steps of any of the above method embodiments by the computer program.

Optionally, in this embodiment, the electronic apparatus may be located in at least one network device of a plurality of network devices of a computer network.

Optionally, in this embodiment, the processor may be configured to execute the following steps by a computer program:

s1, the application server AS acquires a service order request in the target application, wherein the service order request is a request sent by the user equipment UE by using the target account;

s2, AS sends the target application account ID AAID and the target user equipment routing management strategy URSP association request to the strategy control function module PCF according to the service order request, wherein, the association request carries the target flow descriptor of the target application, the target AAID and the current used telephone number MSIMDN of the UE, the target flow descriptor is consistent with the flow descriptor in the URSP configured for the target application in the PCF, the target AAID is the unique corresponding account ID of the target account generated by the target application, the MSIMN is used for positioning the UE, the association request is used for indicating the PCF to search the target URSP which is the same AS the target flow descriptor and is not signed under any signed permanent ID to associate with the target AAID, and the target URSP is issued to the UE corresponding to the MSIMN to be installed;

s3, receiving the response that the target AAID and the target URSP sent by PCF are successfully associated.

Alternatively, it can be understood by those skilled in the art that the structure shown in fig. 7 is only an illustration, and the electronic device may also be a terminal device such as a smart phone (e.g., an Android phone, an iOS phone, etc.), a tablet computer, a palm computer, a Mobile Internet Device (MID), a PAD, and the like. Fig. 7 is a diagram illustrating a structure of the electronic device. For example, the electronic device may also include more or fewer components (e.g., network interfaces, etc.) than shown in FIG. 7, or have a different configuration than shown in FIG. 7.

The memory 702 may be used to store software programs and modules, such as program instructions/modules corresponding to the methods and apparatuses in the embodiments of the present application, and the processor 704 executes various functional applications and data processing by running the software programs and modules stored in the memory 702, so as to implement the above-described association method. The memory 702 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 702 can further include memory located remotely from the processor 704, which can be connected to the terminal over a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof. The memory 702 may be used for storing program steps of the association method, but is not limited thereto. AS an example, AS shown in fig. 7, the memory 702 may include, but is not limited to, UE402, AS404, PCF406, AMF408, etc. in the associated system. In addition, other module units in the above-mentioned association apparatus may also be included, but are not limited to them, and are not described in detail in this example.

Optionally, the transmitting device 706 is used for receiving or sending data via a network. Examples of the network may include a wired network and a wireless network. In one example, the transmission device 706 includes a Network adapter (NIC) that can be connected to a router via a Network cable and other Network devices to communicate with the internet or a local area Network. In one example, the transmission device 706 is a Radio Frequency (RF) module, which is used to communicate with the internet in a wireless manner.

In addition, the electronic device further includes: the display 708 is used for displaying alarm pushing of suspicious accounts; and a connection bus 710 for connecting the respective module parts in the above-described electronic apparatus.

Embodiments of the present application further provide a computer-readable storage medium having a computer program stored therein, wherein the computer program is configured to perform the steps of any of the above method embodiments when executed.

Alternatively, in the present embodiment, the storage medium may be configured to store a computer program for executing the steps of:

Optionally, the storage medium is further configured to store a computer program for executing the steps included in the method in the foregoing embodiment, which is not described in detail in this embodiment.

Alternatively, in this embodiment, a person skilled in the art may understand that all or part of the steps in the methods of the foregoing embodiments may be implemented by a program instructing hardware associated with the terminal device, where the program may be stored in a computer-readable storage medium, and the storage medium may include: flash disks, Read-Only memories (ROMs), Random Access Memories (RAMs), magnetic or optical disks, and the like.

The above-mentioned serial numbers of the embodiments of the present application are merely for description and do not represent the merits of the embodiments.

The integrated unit in the above embodiments, if implemented in the form of a software functional unit and sold or used as a separate product, may be stored in the above computer-readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or a part of or all or part of the technical solution contributing to the prior art may be embodied in the form of a software product stored in a storage medium, and including instructions for causing one or more computer devices (which may be personal computers, servers, network devices, or the like) to execute all or part of the steps of the method described in the embodiments of the present application.

In the above embodiments of the present application, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.

In the several embodiments provided in the present application, it should be understood that the disclosed client may be implemented in other manners. The above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units is only one type of division of logical functions, and there may be other divisions when actually implemented, for example, a plurality of units or components may be combined or may be integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, units or modules, and may be in an electrical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The foregoing is only a preferred embodiment of the present application and it should be noted that those skilled in the art can make several improvements and modifications without departing from the principle of the present application, and these improvements and modifications should also be considered as the protection scope of the present application.

Claims

1. An association method, comprising:

an application server AS acquires a service order request in a target application, wherein the service order request is a request sent by user equipment UE by using a target account;

the AS sends a correlation request of target Application Account Identification (AAID) and a target user equipment routing management policy (URSP) to a policy control function module (PCF) according to the service subscription request, wherein the association request carries a target traffic descriptor of the target application, the target AAID and a telephone number MSIMDN currently used by the UE, the target traffic descriptor is identical to a traffic descriptor in a URSP configured for the target application in the PCF, the target AAID is an account identification which is generated by the target application and is uniquely corresponding to the target account, the MSIMDN is used to locate the UE, the association request is used to instruct the PCF to associate the target URSP, which is the same as the target traffic descriptor and is not signed under any subscription permanent identity (SUIP), with the target AAID, the target URSP is issued to the UE corresponding to the MSIMDN for installation;

and receiving a response that the association between the target AAID and the target URSP sent by the PCF is successful.

2. The method of claim 1, wherein before the AS obtains the subscription request for the service within the target application, the method further comprises:

the AS receives a registration request of registering a target account in the target application by the UE;

and the AS generates an AAID uniquely corresponding to the target account according to the registration request.

3. The method AS claimed in claim 2, wherein after the AS generates an AAID uniquely corresponding to the target account according to the registration request, the method further comprises:

and the AS adds the AAID of the user in a data packet sent to the target account.

4. An association method, comprising:

a policy control function module PCF receives an association request of a target application account identifier AAID and a target user equipment routing management policy URSP, which is sent by an application server AS, wherein the association request carries a target traffic descriptor of a target application, the target AAID, and a phone number MSIMDN currently used by user equipment UE logging in to the target account, the target traffic descriptor is consistent with a traffic descriptor in the URSP configured for the target application in the PCF, the target AAID is an account identifier generated by the target application and uniquely corresponding to the target account, and the MSIMDN is used to locate the UE;

the PCF searches the target URSP which is the same as the target traffic descriptor and is not signed under any signed permanent identification SUIP according to the association request, and associates the target URSP with the target AAID;

the PCF sends a URSP updating request to an access and mobility management function (AMF), wherein the URSP updating request carries the target URSP and the MSMDN, and the URSP updating request is used for indicating the AMF to send the target URSP to the UE corresponding to the MSMDN for installation;

and the PCF sends a response that the association between the target AAID and the target URSP is successful to the AS.

5. The method of claim 4, wherein before sending a response to the AS that association was successful, the method further comprises:

receiving a URSP update completion response sent by the AMF, wherein the URSP update completion response is used for indicating that the UE completes the installation of the target URSP at an operating system layer.

6. An association method, comprising:

user Equipment (UE) sends a service subscription request to a target application by using a target account;

the UE receives a target user equipment routing management strategy URSP issued by an access and mobility management function module AMF, wherein the target URSP is issued to the AMF by a strategy control function module PCF, the target URSP and a target AAID are associated by the PCF, the target AAID is an account identification which is generated by the target application and is uniquely corresponding to the target account, and the target AAID and the target URSP are issued to the PCF by an application server AS of the target application according to the service order request;

the UE installs the target URSP on an operating system layer;

and the UE sends a URSP update completion response to the AMF, wherein the URSP update completion response is used for indicating that the PCF sends a response that the association between the target AAID and the target URSP is successful to the AS.

7. The method of claim 6, wherein after the UE installs the target URSP at an operating system level, the method further comprises:

the UE initiates a service by using the target account, wherein an uplink data packet corresponding to the service carries the characteristic information of the service, and the characteristic information of the service at least comprises one of the following information: traffic descriptor information in the URSP corresponding to the service, and a target AAID of the target account;

the UE matches the service to a target URSP associated with the target AAID according to the flow descriptor information in the URSP corresponding to the service;

and the UE initiates a Protocol Data Unit (PDU) session establishment request to a core network, wherein the session establishment request carries the content specified by the routing descriptor in the target URSP, and the session establishment request is used for indicating the core network to complete the establishment of the PDU session according to the content specified by the routing descriptor.

8. The method according to any one of claims 1 to 7,

the traffic descriptor includes information of at least one of the following: target IP address, target domain name of access, APP ID of target application.

9. An association system, comprising:

10. A computer-readable storage medium, in which a computer program is stored, wherein the computer program is configured to carry out the method of any one of claims 1 to 7 when executed.

11. An electronic device comprising a memory and a processor, wherein the memory has stored therein a computer program, and wherein the processor is arranged to execute the computer program to perform the method of any of claims 1 to 7.