CN109729042B

CN109729042B - Information transmission and processing method and device

Info

Publication number: CN109729042B
Application number: CN201711027491.9A
Authority: CN
Inventors: 吴鹏程
Original assignee: Datang Mobile Communications Equipment Co Ltd
Current assignee: Datang Mobile Communications Equipment Co Ltd
Priority date: 2017-10-27
Filing date: 2017-10-27
Publication date: 2021-03-12
Anticipated expiration: 2037-10-27
Also published as: CN109729042A

Abstract

The application discloses an information transmission and processing method and device, which are used for distinguishing access setting permission of UE (user equipment) to PCO (personal computer) and meeting different requirements of different UEs. The application provides an information transmission method, which comprises the following steps: determining a protocol configuration option PCO permission list of user equipment UE; and informing a Mobile Management Entity (MME) of the PCO permission list of the UE so that the MME receives and records the PCO permission list of the UE. According to the method and the device, the PCO permission list of the user equipment UE is determined, and the PCO permission list of the UE is notified to the mobility management entity MME, so that the MME can process PCO information requested by the UE according to the PCO permission list of the UE, the access setting permission of the UE to the PCO can be distinguished, and different requirements of different UEs can be met.

Description

Information transmission and processing method and device

Technical Field

The present application relates to the field of communications technologies, and in particular, to an information transmission method and an information processing method and an information transmission device.

Background

Long Term Evolution (LTE) is deployed in an enterprise network, and a user can access the internet and IP Multimedia Subsystem (IMS) devices through a mobile phone terminal. In the signaling flow, the mobile phone terminal may request an address of a Domain Name Server (DNS) Server and an entry address of a Proxy Call Session Control Function (P-CSCF) entity from an Evolved Core network (EPC) in an attach process. Meanwhile, the user can also request a DNS address from the EPC through the attachment process and realize the internet surfing function in the subsequent action; in addition, some services may be performed by requesting access to an address according to methods specified in the protocol.

However, in some scenarios, an enterprise needs to manage and control data services, for example, an enterprise network user may perform an audio-video call, but it is not desirable that most employees surf the internet during work, and only a few employees in need are allowed to access the internet through the enterprise network. This requirement is not achievable using the methods specified by existing protocols.

Disclosure of Invention

The embodiment of the application provides an information transmission and processing method and device, which are used for distinguishing access setting permission of UE (user equipment) to PCO (personal computer) and meeting different requirements of different UEs.

An information transmission method provided by an embodiment of the present application includes:

determining a protocol configuration option PCO permission list of user equipment UE;

and informing a Mobile Management Entity (MME) of the PCO permission list of the UE so that the MME receives and records the PCO permission list of the UE.

According to the embodiment of the application, the PCO permission list of the UE is determined, and the PCO permission list of the UE is notified to the mobility management entity MME, so that the MME receives and records the PCO permission list of the UE, and the MME can process PCO information requested by the UE according to the PCO permission list of the UE, so that access setting permission of the UE to PCO can be distinguished, and different requirements of different UEs can be met.

Optionally, notifying the PCO permission list of the UE to a mobility management entity MME, specifically including:

and informing the PCO authority list to MME through an authentication process or a location updating process.

Optionally, the PCO permission list includes information on whether one or a combination of the following is allowed:

an access proxy call session control function P-CSCF IP version 6IPV6 address;

accessing a CN subsystem signal identifier of an IP multimedia IM core network;

access domain name server DNS IPV6 address;

accessing a dual stack mobile IPv6 home agent address;

accessing a dual stack mobile IPv6 home network address;

accessing a dual stack mobile IPv6IP version 4IPv4 home agent address;

accessing IP address allocation through non-access stratum (NAS) signaling;

allocating IPV4 address through dynamic host control protocol version 4DHCPv 4;

requesting a P-CSCF IPv4 address;

IPV4 address of the requesting DNS;

requesting a mobile subscriber integrated services digital network ISDN number MSISDN;

requesting the P-CSCF for reallocation.

An information processing method provided by an embodiment of the present application includes:

receiving protocol configuration option PCO information from user equipment UE;

and when the PCO permission list of the UE is determined to exist, processing the PCO information of the UE according to the PCO permission list of the UE.

Optionally, the method further comprises:

and receiving and recording a PCO authority list of the UE sent by a Home Subscriber Server (HSS).

Optionally, when it is determined that the PCO permission list of the UE exists, processing the PCO information of the UE according to the PCO permission list of the UE specifically includes:

when the PCO permission list of the UE is determined to exist, filtering the PCO information which is not allowed in the PCO information of the UE by using the PCO permission list of the UE to obtain the filtered PCO information;

and when the filtered PCO information is empty, feeding back a rejection message to the UE, wherein the rejection reason value is indication information that the requested PCO content is not allowed.

Optionally, the method further comprises:

and when the filtered PCO information is not empty, sending the filtered PCO information to a Serving Gateway (SGW).

Optionally, the method further comprises:

and when the PCO authority list of the UE does not exist, sending the PCO information of the UE to a Serving Gateway (SGW).

An information transmission device provided in an embodiment of the present application includes:

a first unit, configured to determine a PCO permission list of a user equipment UE;

a second unit, configured to notify a mobility management entity MME of the PCO permission list of the UE, so that the MME receives and records the PCO permission list of the UE.

Optionally, the second unit is specifically configured to: and informing the PCO authority list to MME through an authentication process or a location updating process.

an access proxy call session control function P-CSCF IP version 6IPV6 address;

accessing a CN subsystem signal identifier of an IP multimedia IM core network;

access domain name server DNS IPV6 address;

accessing a dual stack mobile IPv6 home agent address;

accessing a dual stack mobile IPv6 home network address;

accessing a dual stack mobile IPv6IP version 4IPv4 home agent address;

accessing IP address allocation through non-access stratum (NAS) signaling;

allocating IPV4 address through dynamic host control protocol version 4DHCPv 4;

requesting a P-CSCF IPv4 address;

IPV4 address of the requesting DNS;

requesting the P-CSCF for reallocation.

a receiving unit, configured to receive protocol configuration option PCO information from a user equipment UE;

and the processing unit is used for processing the PCO information of the UE according to the PCO authority list of the UE when the PCO authority list of the UE is determined to exist.

Optionally, the receiving unit is further configured to:

Optionally, the processing unit is specifically configured to:

Optionally, the processing unit is further configured to: and when the filtered PCO information is not empty, sending the filtered PCO information to a Serving Gateway (SGW).

Optionally, the processing unit is further configured to: and when the PCO authority list of the UE does not exist, sending the PCO information of the UE to a Serving Gateway (SGW).

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, 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 schematic diagram illustrating an HSS sending a PCO permission list to an MME according to an embodiment of the present application;

fig. 2 is a schematic processing flow diagram of an MME after receiving PCO information of a UE according to an embodiment of the present application;

fig. 3 is a schematic view of an attachment process according to an embodiment of the present application;

fig. 4 is a schematic flowchart of an information transmission method according to an embodiment of the present application;

fig. 5 is a schematic flowchart of an information processing method according to an embodiment of the present application;

fig. 6 is a schematic structural diagram of an information transmission apparatus according to an embodiment of the present application;

fig. 7 is a schematic structural diagram of an information processing apparatus according to an embodiment of the present application.

Detailed Description

The technical scheme provided by the embodiment of the application is a method and a device for controlling an EPC network. The access authority of different users can be configured in HSS, and different network addresses of the users can be configured in EPC, so that the purpose of network control can be achieved. The technical scheme can be conveniently deployed in the existing network, particularly enterprise network users. Is very close to practical application.

In the embodiment of the present application, different user Protocol Configuration Options (PCO) permission lists are configured in the HSS for different UEs.

The PCO permission list for each UE is defined as follows:

TABLE 1PCO Authority List

In the HSS, each UE information has a PCO permission list for indicating the PCO contents that the UE is allowed to access, and indicating in the table whether to allow the request of the contents corresponding to the PCO.

Referring to fig. 1, the HSS may transfer the PCO permission list to the MME through an s6a interface in any procedure, such as an authentication procedure or a location update procedure.

New defined Attribute-Value-Pairs (AVP) are required:

specifically, the method comprises the following steps:

correspondingly, in the flow, the MME introduces a method for processing PCO information sent by the UE, where the PCO information may be a part of information in a PCO permission list.

Referring to fig. 2, in an attach procedure or a request PDN connectivity (UE requested PDN connectivity) procedure, a processing procedure of receiving, by an MME, PCO information uploaded from a UE includes:

step 201, in the authentication information acquisition process of the attachment process, the HSS transfers the PCO permission list of the UE to the MME. And the MME is stored in the information instance corresponding to the UE.

Step 202, after receiving the PCO information sent by the UE, the MME first queries whether a PCO permission list of the UE exists. If not, go to step 203; if so, step 204 is performed.

Step 203, sending the PCO information to the SGW.

Step 204, filtering the received PCO information of the UE according to the PCO permission list of the UE, and recombining the PCO options allowed by the PCO permission list of the UE, which are contained in the PCO information of the UE, into PCO information.

In step 205, it is determined whether the recombined PCO information (i.e., the new PCO information obtained after filtering) is empty, i.e., whether the PCO option in table 1 is included. If yes, go to step 207; otherwise, step 206 is performed.

In step 206, if the filtered PCO information is not null, the MME sends the filtered PCO information to the SGW.

Step 207, if the filtered PCO information is empty, a corresponding reject message is replied to the UE according to the flow type, and the flow is ended. Specifically, if the flow type is an attach flow, replying the corresponding reject message to the UE is replying an attach reject message to the UE; and if the flow type is a request PDN connection (UE requested PDN connection) flow, replying a corresponding rejection message to the UE as a PDN connection REJECT message to the UE.

In the embodiment of the present application, a reject cause value is newly defined: the requested PCO content is not allowed. The reject cause value may be carried in a reject message that is fed back to the UE by the MME.

Specific examples are as follows:

the PCO information sent by the UE to the network side through the NAS message carries the following information:

{ P-CSCF IPv6Address Request (visiting P-CSCF IPV6 Address) }

{ IM CN Subsystem Signaling (Access to IM CN Subsystem Signal) }

{ DNS Server IPv6Address Request (Access DNS Server IPV6 Address) }

However, in the PCO authority table, if the settings are as shown in table 2 below:

whether or not to permit (0 represents not permit, 1 represents permit)	Number of	Explaining the meaning
			0	0001H	Visiting P-CSCF IPV6address
1	0002H	Accessing IM CN subsystem signal identification
			1	0003H	Accessing DNS server IPV6address

TABLE 2

It means that the UE is not allowed to access the P-CSCF IPV6address in the MME.

Other PCO options of "access IM CN subsystem signal identification", "access DNS server IPV6 address" are allowed.

The PCO permission set (that is, the PCO information obtained by filtering the PCO information of the UE according to the PCO permission list, or referred to as regenerated PCO information) transferred by the MME to the SGW and the PGW only includes two pieces of PCO information, i.e., { "signal identifier for accessing the IM CN subsystem", "address of accessing the DNS server IPV 6" };

{ P-CSCF IPv6Address Request (visiting P-CSCF IPV6 Address) } is filtered out by the MME and is not passed and requested backwards any more.

If in the MME setting, the PCO permission list is as set as shown in table 3 below:

TABLE 3

Then, all PCO information corresponding to the UE request is prohibited by the table 3, and the filtered PCO permission set is empty, that is, all PCO information is not requested to be accessed.

Referring to fig. 3, the overall process flow is illustrated as follows:

in step 301, the UE initiates an Attach request message (Attach request) (including parameters such as TMSI, UE capability, and PDN address) and a network selection indication to an evolved node b (eNB). A PDN connection Request (PDN Connect Request) message is nested in the Attach Request, and the UE requests some addresses of the access points, such as DNS server addresses, P-CSCF addresses, etc., through the identifier in the PCO information. PCO information, present in the transferred Attach Request or PDN Connect Request messages.

In step 302, the eNB derives an MME according to an SAE-Temporary Mobile Subscriber identity (SAE-Temporary Mobile Subscriber identity, S-TMSI) and a network selection indication. If the eNB cannot deduce the MME, the MME is selected through an MME selection function, and the attach request message is forwarded to the MME.

Step 303, if the Global Unique Temporary Identity (GUTI) is invalid, the UE context information is not stored in the network side. The MME will send an authentication Request message (Identity Request) message to the UE to Request IMSI information.

Step 304, the UE sends an authentication Response (Identity Response) message to the MME, where the Identity Response message carries International Mobile Subscriber Identity (IMSI) information.

In step 305, the MME sends an Authentication Information Request (Authentication Information Request) message to the HSS.

Step 306, the HSS sends an Authentication Information Answer (Authentication Information Answer) message to the MME, and carries the Authentication vector to the MME. And the HSS inquires whether the UE contains a PCO authority list, if the PCO authority list of the UE is stored in the HSS, the HSS carries the PCO authority list of the UE to the MME through the authentication information response message. (there may be no function of setting PCO permission list for instance information corresponding to the UE in HSS. there is no set, then it is processed as it is.)

Step 307, the MME selects one group from the acquired Authentication vectors, and sends an Authentication Request (Authentication Request) to the terminal UE.

Step 308, after receiving the Authentication request, the UE performs Authentication on the terminal side, and if the Authentication is successful, replies an Authentication Response (Authentication Response) message to the MME.

Step 309, after receiving the authentication RESponse, the MME compares whether an EXpected user RESponse (XRES) parameter in the authentication RESponse message is consistent with the locally stored XRES parameter, and if so, the authentication is successful. After the authentication is successful, the MME generates an integrity protection key and an encryption key by using the key Kasme, and sends a Security Mode Command (Security Mode Command) message to the UE to initiate a Security control process.

In step 310, the UE checks the integrity protection after receiving the security mode command. And if the verification is successful, sending a Security Mode Complete (Security Mode Complete) message to the MME, and establishing a Security process.

Step 311, the MME takes out the PCO information sent by the UE, filters the PCO permission list sent by the HSS to the MME, if part or all of the PCO requests in the PCO information sent by the UE are not allowed in the PCO permission list, then the PCO request is no longer included when the PCO information is re-composed, and if part or all of the PCO requests in the PCO information sent by the UE are allowed in the PCO permission list, then the allowed entry is used to compose new PCO information (i.e. the PCO permission set applied by the UE is compared with the PCO permission list transferred by the HSS, the restricted PCO request is removed, and new PCO information is generated).

If the new PCO information is not null, the reconstructed PCO information is sent to the SGW, including in a CREATE SESSION REQUEST message, with subsequent procedures consistent with the prior art.

And if the generated new PCO information is empty, namely one or more PCO requests in the PCO information sent by the UE are not allowed, directly replying to an Attach Reject (Attach Reject) message of the UE. And nesting a PDN connection Reject (PDN connect Reject) message in the attach message. The PDN connection Reject (PDN connection Reject) message has a cause value that the requested PCO content is not allowed.

In summary, referring to fig. 4, at the HSS side, an information transmission method provided in the embodiment of the present application includes:

s101, determining a PCO (protocol configuration object) authority list of User Equipment (UE);

s102, notifying a Mobility Management Entity (MME) of the PCO permission list of the UE so that the MME receives and records the PCO permission list of the UE.

According to the embodiment of the application, the PCO permission list of the UE is determined, and the PCO permission list of the UE is notified to the mobility management entity MME, so that the MME can process PCO information requested by the UE according to the PCO permission list of the UE, the access setting permission of the UE to the PCO can be distinguished, and different requirements of different UEs can be met.

Optionally, the PCO permission list includes information on whether one or a combination of the following is allowed (i.e. whether some or all of the contents in table 1 above are allowed):

an access proxy call session control function P-CSCF IP version 6IPV6 address;

accessing a CN subsystem signal identifier of an IM core network;

access domain name server DNS IPV6 address;

accessing a dual stack mobile IPv6 home agent address;

accessing a dual stack mobile IPv6 home network address;

accessing a dual stack mobile IPv6IP version 4IPv4 home agent address;

accessing IP address allocation through non-access stratum (NAS) signaling;

allocating IPV4 address through dynamic host control protocol version 4DHCPv 4;

requesting a P-CSCF IPv4 address;

IPV4 address of the requesting DNS;

requesting the P-CSCF for reallocation.

Correspondingly, on the MME side, referring to fig. 5, an information processing method provided in an embodiment of the present application includes:

s201, receiving Protocol Configuration Option (PCO) information from User Equipment (UE);

s202, when the PCO permission list of the UE is determined to exist, the PCO information of the UE is processed according to the PCO permission list of the UE.

Optionally, the method further comprises:

Of course, the PCO permission list of the UE may be set in advance on the MME side, and the PCO permission list may not be sent by the HSS.

when the PCO permission list of the UE is determined to exist, filtering the PCO information which is not allowed in the PCO information of the UE by using the PCO permission list of the UE to obtain the filtered PCO information (namely the newly generated PCO information);

and when the filtered PCO information is null (that is, all PCO information sent by the UE is not allowed by the PCO permission list of the UE), feeding back a rejection message to the UE, wherein the rejection message carries indication information that the requested PCO content is not allowed.

Optionally, the method further comprises:

The apparatus corresponding to the above method is described as follows:

at the HSS side, referring to fig. 6, an information transmission apparatus provided in an embodiment of the present application includes:

a first unit 11, configured to determine a PCO permission list of a user equipment UE;

a second unit 12, configured to notify the PCO permission list of the UE to a mobility management entity MME, so that the MME receives and records the PCO permission list of the UE.

an access proxy call session control function P-CSCF IP version 6IPV6 address;

accessing a CN subsystem signal identifier of an IM core network;

access domain name server DNS IPV6 address;

accessing a dual stack mobile IPv6 home agent address;

accessing a dual stack mobile IPv6 home network address;

accessing a dual stack mobile IPv6IP version 4IPv4 home agent address;

accessing IP address allocation through non-access stratum (NAS) signaling;

allocating IPV4 address through dynamic host control protocol version 4DHCPv 4;

requesting a P-CSCF IPv4 address;

IPV4 address of the requesting DNS;

requesting the P-CSCF for reallocation.

The information transmission device provided in the embodiment of the present application may be, for example, an HSS. The first unit and the second unit may be implemented by a physical device such as a processor.

Referring to fig. 7, on an MME side, an information transmission apparatus provided in an embodiment of the present application includes:

a receiving unit 21, configured to receive protocol configuration option PCO information from a user equipment UE;

and the processing unit 22 is configured to, when it is determined that the PCO permission list of the UE exists, process the PCO information of the UE according to the PCO permission list of the UE.

Optionally, the receiving unit is further configured to:

Optionally, the processing unit is specifically configured to:

The information transmission apparatus provided in the embodiment of the present application may be, for example, an MME entity apparatus on a network side, where the receiving unit may be a transceiver, and the processing unit may be implemented by an entity device such as a processor.

To sum up, the technical scheme provided by the embodiment of the application is very practical, can be applied to the fields of coal, oil, electric power and the like of a private network, and is used for smoothly accessing a newly-built private network to the existing network. Has wide application prospect. Meanwhile, the method does not modify the existing flow and can be compatible with the existing network.

As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, optical storage, and the like) having computer-usable program code embodied therein.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.

Claims

1. An information transmission method is applied to a Home Subscriber Server (HSS) side, and comprises the following steps:

2. The method according to claim 1, wherein notifying a mobility management entity MME of the PCO permission list of the UE specifically includes:

3. The method of claim 1, wherein the PCO permission list includes information on whether one or a combination of the following is allowed:

an access proxy call session control function P-CSCF IP version 6IPV6 address;

accessing a CN subsystem signal identifier of an IP multimedia IM core network;

access domain name server DNS IPV6 address;

accessing a dual stack mobile IPv6 home agent address;

accessing a dual stack mobile IPv6 home network address;

accessing dual stack mobile IPv6IP version 4IPv4 home agent address;

accessing IP address allocation through non-access stratum (NAS) signaling;

allocating IPV4 address through dynamic host control protocol version 4DHCPv 4;

requesting a P-CSCF IPv4 address;

IPV4 address of the requesting DNS;

requesting the P-CSCF for reallocation.

4. An information processing method is applied to a Mobility Management Entity (MME) side, and comprises the following steps:

receiving protocol configuration option PCO information from user equipment UE; and when the PCO permission list of the UE is determined to exist, processing the PCO information of the UE according to the PCO permission list of the UE.

5. The method of claim 4, further comprising:

6. The method according to claim 4, wherein when it is determined that the PCO permission list of the UE exists, processing the PCO information of the UE according to the PCO permission list of the UE specifically includes:

7. The method of claim 6, further comprising:

8. The method of claim 4, further comprising:

9. An information transmission apparatus, applied to a Home Subscriber Server (HSS), includes:

10. The apparatus according to claim 9, wherein the second unit is specifically configured to: and informing the PCO authority list to MME through an authentication process or a location updating process.

11. The apparatus of claim 9, wherein the PCO permission list comprises information on whether one or a combination of the following is allowed:

an access proxy call session control function P-CSCF IP version 6IPV6 address;

accessing a CN subsystem signal identifier of an IP multimedia IM core network;

access domain name server DNS IPV6 address;

accessing a dual stack mobile IPv6 home agent address;

accessing a dual stack mobile IPv6 home network address;

accessing dual stack mobile IPv6IP version 4IPv4 home agent address;

accessing IP address allocation through non-access stratum (NAS) signaling;

allocating IPV4 address through dynamic host control protocol version 4DHCPv 4;

requesting a P-CSCF IPv4 address;

IPV4 address of the requesting DNS;

requesting the P-CSCF for reallocation.

12. An information transmission apparatus, applied to a Mobility Management Entity (MME) side, includes:

13. The apparatus of claim 12, wherein the receiving unit is further configured to:

14. The apparatus according to claim 12, wherein the processing unit is specifically configured to:

15. The apparatus of claim 14, wherein the processing unit is further configured to: and when the filtered PCO information is not empty, sending the filtered PCO information to a Serving Gateway (SGW).

16. The apparatus of claim 12, wherein the processing unit is further configured to: and when the PCO authority list of the UE does not exist, sending the PCO information of the UE to a Serving Gateway (SGW).