CN114785756A - Information sending method, device and equipment - Google Patents

Abstract

The application provides an information sending method, device and equipment, wherein an IPv6interface ID is obtained by a UPF in a PPP negotiation process with an LNS, an IPv6interface ID is sent to the SMF, at least an IPv6 address prefix is obtained by reading a message sent by the UE or the message sent to the UE, and the IPv6 address prefix is reported to the SMF when the UPF indicated by a first IPv6 mark bit newly added in a PFCP session creation request message reports the IPv6 address prefix to the SMF, or the IPv6 address prefix and the IPv6interface ID are reported to the SMF when the first IPv6 indicates the UPF to report the IPv6 address prefix and the IPv6interface ID to the SMF. It can be seen that, by applying the technical scheme provided by the embodiment of the present application, while the unique and complete IPv6 address allocated by the LNS to the UE can be obtained, the problem that the session binding property of the 5G core network cannot be supported can also be avoided.

Description

Information sending method, device and equipment

Technical Field

The present application relates to the field of 5G communications technologies, and in particular, to an information sending method, apparatus, and device.

Background

The 3GPP Protocol specifies that L2TP (Layer 2 Tunneling Protocol) functional characteristics can be selectively supported between a CP (Control Plane) and a DP (Data Plane). Based on this, in a 5G (Fifth Generation) mobile communication network architecture, a Session Management Function (SMF) and a User Plane Function (UPF) in a core network may support L2TP Function characteristics through PPP (point to point Protocol) negotiation.

However, the 3GPP Protocol does not support that the UPF carries an IPv6interface ID (Identity document) negotiated by an LNS (L2 TP Network Server ) in a PFCP (Packet Forwarding Control Protocol) session creation response, that is, the IPv6interface ID sent by the SMF to the UE is not an LNS negotiated result. Thus, multiple UEs belonging to the same lan may acquire the same IPv6interface ID and generate the same IPv6 address, which may cause IPv6 address collision of the multiple UEs. In addition, the 3GPP protocol also does not support that the UPF notifies the IPv6 address prefix allocated by the SMF LNS in a message cell other than the PDR (Packet Detection Rule) established in the PFCP session creation response and the PFCP session modification response, and also does not support that the UPF acquires the IPv6 address prefix allocated to the UE during the PPP negotiation process.

Based on the existing 5G standard and PPP standard, the SMF cannot acquire the unique IPv6interface ID which is distributed by the LNS for the UE in the same local area network, which may cause IPv6 address conflict of a plurality of UEs in the same local area network; and the SMF cannot acquire the complete IPv6 address distributed by the LNS for the UE, so that the problem that the session binding property of the 5G core network cannot be supported is caused.

Disclosure of Invention

In view of this, the present application provides an information sending method and apparatus, so that an SMF can obtain an IPv6interface ID and an IPv6 address prefix allocated by an LNS to a UE.

In a first aspect, an information sending method in an embodiment of the present application is applied to a user plane network element UPF, and includes:

acquiring an IPv6interface identification ID in the process of point-to-point protocol PPP negotiation with an LNS, sending the acquired IPv6interface ID to an SMF, and allocating the IPv6interface ID to UE which requests allocation of the IPv6interface ID to the SMF by the SMF;

the method comprises the steps that at least IPv6 address prefixes distributed by UE are obtained by reading messages sent by the UE or messages sent to the UE, when newly added first IPv6 marking bits exist in received PFCP session creation request messages sent in the process that the UPF and SMF create PFCP sessions, and the first IPv6 marking bits are used for indicating that the UPF reports the IPv6 address prefixes distributed by the UE to the SMF, the IPv6 address prefixes distributed by the UE and obtained by reporting to the SMF are obtained, and the SMF obtains the IPv6interface ID and the IPv6 address prefixes distributed by the UE; or a newly added first IPv6 flag bit exists in a received PFCP session creation request message sent in the process of creating a PFCP session between the UPF and the SMF, and the first IPv6 is used for reporting, to the SMF, an IPv6 address prefix and an IPv6interface ID allocated to the UE, when the UPF reports the IPv6 address prefix and the IPv6interface ID allocated to the UE to the SMF, so that the SMF obtains the IPv6interface ID and the IPv6 address prefix allocated to the UE.

In a second aspect, an embodiment of the present application provides a message sending apparatus, where the apparatus is applied to a user plane network element UPF, and the apparatus includes:

an interface ID sending unit, configured to obtain an IPv6interface ID during a point-to-point protocol PPP negotiation with the LNS, send the obtained IPv6interface ID to the SMF, and allocate the IPv6interface ID to the UE that requests allocation of the IPv6interface ID to the SMF by the SMF;

an IPv6 address information obtaining unit, configured to obtain at least an IPv6 address prefix allocated to the UE by reading a packet sent by the UE or a packet sent to the UE, and when a received PFCP session creation request message sent in a process of creating a PFCP session between the UPF and an SMF includes a newly added first IPv6 flag bit, and the first IPv6 flag bit is used to indicate the UPF to report an IPv6 address prefix allocated to the UE to the SMF, report the obtained IPv6 address prefix allocated to the UE to obtain, by the SMF, an IPv6interface ID and an IPv6 address prefix allocated to the UE; or a newly added first IPv6 flag bit exists in a received PFCP session creation request message sent in the process of creating a PFCP session between the UPF and the SMF, and the first IPv6 is used for reporting, to the SMF, an IPv6 address prefix and an IPv6interface ID allocated to the UE, when the UPF reports the IPv6 address prefix and the IPv6interface ID allocated to the UE to the SMF, so that the SMF obtains the IPv6interface ID and the IPv6 address prefix allocated to the UE.

According to the technical scheme, by applying the embodiment of the application, the UPF in the 5G core network obtains an IPv6interface ID in the PPP negotiation process with the LNS, and sends the obtained IPv6interface ID to the SMF, so that the SMF allocates the IPv6interface ID to the UE; the method comprises the steps of at least obtaining IPv6 address prefixes distributed by UE by reading messages sent by the UE or messages sent to the UE, reporting at least obtained IPv6 address prefixes distributed by the UE to SMF when newly added first IPv6 marking bits exist in PFCP session creation request messages and the first IPv6 marking bits are used for indicating UPF to report the IPv6 address prefixes distributed by the UE to the SMF, or reporting the obtained IPv6 address prefixes distributed by the UE and the IPv6interface IDs distributed by the UE to the SMF when newly added first IPv6 marking bits exist in the PFCP session creation request messages and the first IPv6 is used for indicating UPF to report the IPv6 address prefixes and the IPv6interface IDs distributed by the UE to the SMF. Finally, the SMF obtains the IPv6interface ID and the IPv6 address prefix assigned by the UE. It can be seen that the IPv6interface ID of the UE sent by the UPF to the SMF in the embodiment of the present application is the result of LNS negotiation, and meanwhile, the UPF reports to the SMF in a manner of reading a message sent by the UE or a message sent to the UE to obtain an IPv6 address prefix allocated to the UE, or an IPv6interface ID and an IPv6 address prefix, so that the SMF can obtain a unique and complete IPv6 address allocated to the UE by the LNS according to the IPv6interface ID and the IPv6 address prefix allocated to the UE, and can also avoid the problem that the session binding property of the 5G core network cannot be supported.

Drawings

Fig. 1 is a schematic flowchart of a method for allocating an IPv6 address by an L2TP session LNS in the prior art according to an embodiment of the present application;

fig. 2 is a schematic diagram of an exemplary IPv6 address collision in a local area network according to an embodiment of the present application;

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

fig. 4 is a schematic diagram illustrating an IPv6 address allocated by an L2TP session LNS applied to a 5G core network according to an embodiment of the present application;

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

fig. 6 is a hardware structure diagram of an electronic device according to an embodiment of the present application.

Detailed Description

Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in this application and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.

It is to be understood that although the terms first, second, third, etc. may be used herein to describe various information, such information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of the present application. The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination", depending on the context.

The 3GPP Protocol specifies that L2TP (Layer 2 Tunneling Protocol) functional characteristics can be selectively supported between a CP (Control Plane) and a DP (Data Plane). And L2TP is a UDP (User Datagram Protocol) based data link layer Protocol, which is commonly used in virtual private networks. The method mainly comprises control type messages and data type messages, wherein the control type messages follow UDP protocol regulations, and a link between an LAC (L2 TP Access Concentrator ) and an LNS (L2 TP Network Server, L2TP Network Server) is established according to a fixed flow; the dataclass messages pass data content between the LAC (L2 TP Access Concentrator ) and the LNS primarily based on PPP frames. Where the LAC is a device with PPP and L2TP processing capabilities on the switched network. The LAC establishes an L2TP tunnel connection with the LNS according to the user name or domain name information carried in the PPP message, and applies PPP negotiation to the LNS (L2 TP Network Server ). The LNS is one end for terminating the PPP session, and the PPP session negotiation is successful through the authentication of the LNS, so that the remote user can access the resources of the enterprise headquarters.

In contrast, in a 5G core network under a 5G (Fifth Generation) mobile communication network architecture, the UPF has a LAC Function, establishes an L2TP tunnel and PPP negotiation with the LNS, can complete authorization and data transmission of the UE, and can support L2TP functional characteristics through PPP negotiation between an SMF (Session Management Function) and an UPF (User Plane Function) in the core network.

Referring to fig. 1, when receiving a PFCP (Packet Forwarding Control Protocol) session creation request initiated by a UE, an SMF selects an UPF supporting L2TP characteristics according to a characteristic list negotiated between the SMF and a plurality of UPFs locally for access. At this time, the selected UPF, as a role of the LAC, completes the L2TP tunnel establishment, L2TP session establishment, and PPP negotiation process with the LNS in sequence, and completes authentication authorization at both ends, UE address allocation, L2TP data channel link establishment, and the like. And then, sending the processing result back to the SMF, and finally responding to the UE to complete the access process of the UE. Then, when the UE sends an uplink Data packet to a DN-Server (Data Network Server), encapsulating a GTP header of the uplink Data packet by a gNB (next Generation Node B), and sending the packet encapsulating the GTP header to an UPF; the UPF is responsible for decapsulating the GTP header, encapsulating the decapsulated GTP header with a header L2TP, and then sending the encapsulated header L2TP to the LNS, so that the LNS is responsible for decapsulating the header L2TP, and then the LNS sends the decapsulated header L2TP to a DN-Server, such as an intranet Server, accessed by the UE. When the DN-Server sends a downlink data message to the UE, the head of L2TP is packaged through the LNS, and the message for packaging the head of L2TP is sent to the UPF; the UPF is responsible for decapsulating the L2TP header, encapsulating the GTP header and sending the GTP header to the gNB; and the gNB is responsible for decapsulating the GTP heads and finally sending the messages with the decapsulated GTP heads to the UE.

As mentioned above, the PPP negotiation procedure between the UPF and the LNS may implement the allocation of the UE address, as shown in fig. 1, the SMF sends the PFCP session creation request message indicating that the UPF allocates the IPv6interface ID to the UE, and the UPF locally selects to complete the address allocation procedure by the LNS. In the PPP negotiation process, the UPF and the LNS negotiate the IPv6interface ID1 of both parties, and since the 3GPP protocol does not support the UPF to carry the IPv6interface ID negotiated by the LNS in the PFCP session creation response, the SMF may allocate an IPv6interface ID2 in a private manner since the IPv6interface ID1 cannot be included in the session creation response returned to the UE. The UE initiates an RS (Router Solicitation) request with this IPv6interface ID2 constituting an IPv6 address, forwards the request to the LNS via the gNB and the UPF, the LNS identifies and processes the request, and a corresponding RA response, containing the IPv6 address prefix, is forwarded to the UE via the UPF and the gNB. So far, the UE acquires a complete IPv6 address, i.e., IPv6 prefix + IPv6interface ID. In the whole process, UPF does not need to concern RS/RA message content, and only needs to carry out data forwarding corresponding to the matched GTP and L2TP tunnels.

It is obvious that, since the 3GPP protocol does not support that the UPF carries the IPv6interface ID of the LNS negotiation in the PFCP session creation response, that is, the IPv6interface ID sent by the SMF to the UE, is not the result of the LNS negotiation. Therefore, multiple UEs belonging to the same lan may acquire the same IPv6interface ID and generate the same IPv6 address, that is, multiple UEs are assigned the same IPv6 address, which may cause IPv6 address collision of the multiple UEs. As shown in fig. 2, when the UPF cannot bring the IPv6interface ID allocated by the LNS back to the SMF, the SMF may allocate the IPv6interface ID of the UE, but this only ensures that the SMF is internally unique, and there is no standard protocol to support that the SMF can negotiate with all routing nodes in the same lan and further ensure uniqueness in the lan. If fig. 2 shows that two different SMFs are assigned the same IPv6interface ID, x, for their respective UEs, this may result in a conflicting IPv6interface ID being assigned between the two SMFs. Meanwhile, there may be other devices in the lan, such as a host that directly negotiates with the LNS to allocate an IPv6interface ID without passing through the 5G core network, that is, x in fig. 2, and the LNS cannot know the IPv6interface ID already allocated by each SMF, which may also cause a collision.

In addition, the 3GPP protocol does not support that the UPF notifies the IPv6 address prefix allocated by the SMF LNS in the message cell except for the PDR (Packet Detection Rule) established in the PFCP session creation response and the PFCP session modification response, but does not support that the UPF acquires the IPv6 address prefix allocated to the UE during the PPP negotiation.

Based on the above analysis, it can be seen that based on the existing 5G standard and PPP standard, the SMF cannot acquire the unique IPv6interface ID in the same lan allocated to the UE by the LNS, which may cause IPv6 address conflicts of multiple UEs in the same lan; and the SMF cannot acquire the complete IPv6 address allocated by the LNS for the UE, so that the problem that the session binding property of the 5G core network cannot be supported is caused.

In order to solve the foregoing problem, an embodiment of the present application provides an information sending method, where the method is applied to a user plane network element UPF, and includes: acquiring an IPv6interface identification ID in the PPP negotiation process with the LNS, sending the acquired IPv6interface ID to the SMF, and allocating the IPv6interface ID to the UE which requests the allocation of the IPv6interface ID to the SMF by the SMF; the method comprises the steps that at least IPv6 address prefixes distributed by UE are obtained by reading messages sent by the UE or messages sent to the UE, when newly added first IPv6 marking bits exist in received PFCP session creation request messages sent in the process that the UPF and SMF create PFCP sessions, and the first IPv6 marking bits are used for indicating that the UPF reports the IPv6 address prefixes distributed by the UE to the SMF, the IPv6 address prefixes distributed by the UE and obtained by reporting to the SMF are obtained, and the SMF obtains the IPv6interface ID and the IPv6 address prefixes distributed by the UE; or when a newly added first IPv6 flag bit exists in a received PFCP session creation request message sent in the process of creating a PFCP session between the UPF and the SMF, and the first IPv6 is used for indicating that the UPF reports the IPv6 address prefix and the IPv6interface ID allocated to the UE to the SMF, reporting the obtained IPv6 address prefix and the IPv6interface ID allocated to the UE to the SMF, so that the SMF obtains the IPv6interface ID and the IPv6 address prefix allocated to the UE.

It can be seen that the IPv6interface ID of the UE sent by the UPF to the SMF in this embodiment is the result of LNS negotiation, and meanwhile, the UPF reports to the SMF in a manner of reading a packet sent by the UE or a packet sent to the UE to obtain an IPv6 address prefix allocated to the UE, or an IPv6interface ID and an IPv6 address prefix, so that the SMF can obtain a unique and complete IPv6 address allocated to the UE by the LNS according to the IPv6interface ID and the IPv6 address prefix allocated to the UE, and can also avoid a problem that the session binding property of the 5G core network cannot be supported.

The technical solution of the present application is described in detail by specific examples below.

Fig. 3 is a flowchart of an embodiment of an information sending method according to an exemplary embodiment of the present application, where the method is applied to a user plane network element UPF, where the UPF is a user plane network element UPF supporting a second layer tunneling protocol L2TP characteristic, and as an embodiment, when it is detected that a user plane network element UPF needs to be switched for a UE, an SMF detects whether there is a UPF meeting a characteristic condition of supporting a second layer tunneling protocol L2TP in each UPF currently managed by the SMF, and if there is a UPF in this embodiment, selects a UPF from the UPFs meeting the characteristic condition of supporting the second layer tunneling protocol L2TP as the UPF in this embodiment.

As shown in fig. 3, the method for sending information under a 5G core network includes the following steps:

step 101, acquiring an IPv6interface ID during PPP negotiation with the LNS, and sending the acquired IPv6interface ID to the SMF, so that the SMF allocates the IPv6interface ID to the UE requesting to allocate the IPv6interface ID to the SMF.

Beforestep 101, the UPF selects an LNS to distribute an IPv6interface ID to the UE according to a locally stored configuration policy, wherein the configuration policy at least comprises a policy of distributing an IPv6interface ID to the terminal; establishing an L2TP tunnel between the UPF and the LNS, and establishing an L2TP session connection between the UPF and the LNS which belong to the L2TP tunnel;step 101 is further executed to determine the IPv6interface ID allocated to the UE through PPP negotiation, receive the IPv6interface ID from the LNS transmission through the L2TP session connection, and send the obtained IPv6interface ID to the SMF to allocate the IPv6interface ID to the UE by the SMF.

It should be noted that the UE that the SMF sends the IPv6interface ID to the UE is the UE that has requested to assign the IPv6interface ID to the SMF.

102, at least obtaining an IPv6 address prefix allocated to the UE by reading a message sent by the UE or a message sent to the UE, and reporting an obtained IPv6 address prefix allocated to the UE to the SMF when a newly added first IPv6 flag bit exists in a PFCP session creation request message sent in a process of creating a PFCP session between a received local UPF and the SMF, and the first IPv6 flag bit is used to indicate the UPF to report the IPv6 address prefix allocated to the UE to the SMF, so that the SMF obtains the IPv6interface ID and the IPv6 address prefix allocated to the UE; or when a newly added first IPv6 flag bit exists in a received PFCP session creation request message sent in a process of creating a PFCP session between the UPF and the SMF, and the first IPv6 is used for indicating the UPF to report the IPv6 address prefix and the IPv6interface ID allocated to the UE to the SMF, reporting the IPv6 address prefix and the IPv6interface ID allocated to the UE, which are obtained by the SMF, so that the SMF obtains the IPv6interface ID and the IPv6 address prefix allocated to the UE.

In this embodiment, the first IPv6 flag bit is named for convenience of distinguishing from the IPv6 flag bit described later, and is not limited to an IPv6 flag bit.

For the UE, there is also an IPV6interface ID previously assigned to the SMF request, and a previously requested IPV6 address prefix within the UE. For the UPF, the UPF has obtained the IPv6interface ID assigned by the UE and the IPv6 address prefix assigned by the UE instep 101. Based on the analysis, it can be known that at least the IPv6 address prefix allocated to the UE is obtained by reading the message sent by the UE or the message sent to the UE. It can be understood that, at least, obtaining the IPv6 address prefix allocated to the UE may obtain the IPv6 address prefix allocated to the UE by reading the packet sent by the UE or the packet sent to the UE, or may obtain the IPv6 address prefix and the IPv6interface ID allocated to the UE. In other words, the IPv6 address prefix allocated to the UE, or the IPv6 address prefix and the IPv6interface ID allocated to the UE may be obtained from a packet sent by the UE, or may be obtained by the LNS directly sending the packet of the UE through the UPF.

If only the IPv6 address prefix distributed by the UE is obtained by reading the message sent by the UE or the message sent to the UE, when the first IPv6 marking bit is used for indicating the UPF to report the IPv6 address prefix distributed by the UE to the SMF, the UDP reports the IPv6 address prefix distributed by the UE to the SMF. Thus, the SMF receives the IPv6 address prefix reported by the UDP to the SMF, and after obtaining the IPv6 address prefix, the SMF, in combination with the IPv6interface ID sent by the UPF, may generate the IPv6 address according to the IPv6interface ID and the IPv6 address prefix. If the message sent by the UE or the message sent to the UE is read to obtain the IPv6 address prefix allocated to the UE, and when the first IPv6 flag bit is used to indicate the UPF to report the IPv6 address prefix allocated to the UE to the SMF, only the obtained IPv6 address prefix allocated to the UE is reported to the SMF, so that the SMF receives the IPv6 address prefix reported to the SMF by the UDP, and after obtaining the IPv6 address prefix, an IPv6 address can be generated according to the IPv6interface ID and the IPv6 address prefix, in combination with the IPv6interface ID sent by the UPF that has been obtained before the SMF.

If only the IPv6 address prefix distributed by the UE is obtained by reading the message sent by the UE or the message sent to the UE, when the first IPv6 marking bit is used for indicating UPF to report the IPv6 address prefix and the IPv6interface ID distributed by the UE to SMF, UDP obtains the IPv6 address prefix distributed by the UE, and reports the IPv6 address prefix and the IPv6interface ID distributed by the UE to the SMF according to the indication of the first IPv6 marking bit by combining the IPv6interface ID distributed by the UE which is locally stored before. Thus, the SMF receives the IPv6 address prefix and the IPv6interface ID reported to the SMF by the UDP, and can directly generate the IPv6 address according to the IPv6 address prefix and the IPv6interface ID. If the message sent by the UE or the message sent to the UE is read to obtain the IPv6 address prefix distributed by the UE, when the first IPv6 marking bit is used for indicating UPF to report the IPv6 address prefix and the IPv6interface ID distributed by the UE to SMF, UDP directly reports the IPv6 address prefix and the IPv6interface ID distributed by the UE to SMF according to the indication of the first IPv6 marking bit. Thus, the SMF receives the IPv6 address prefix and the IPv6interface ID reported by the UDP to the SMF, and the SMF can directly generate an IPv6 address according to the IPv6interface ID and the IPv6 address prefix.

In addition, for the UE, the request information carrying the IPv6 address prefix transmitted by the UE is acquired through the established PFCP session connection, and the request information is forwarded to the LNS through the established L2TP session connection; receiving response information carrying IPv6 address prefixes, forwarded from the LNS in response to request information, by expanding L2TP session information; and sending the response information to the UE through the established PFCP session connection so that the UE generates an IPv6 address belonging to the UE according to the acquired IPv6 address interface ID and the acquired IPv6 address prefix.

Up to this point, the description shown in fig. 3 is completed.

It can be seen from the above technical solutions that, by applying the embodiment of the present application, the UPF in the 5G core network obtains an IPv6interface ID in the PPP negotiation process with the LNS, and sends the obtained IPv6interface ID to the SMF, so that the SMF allocates the IPv6interface ID to the UE; the method comprises the steps of at least obtaining IPv6 address prefixes distributed by UE by reading messages sent by the UE or messages sent to the UE, reporting at least obtained IPv6 address prefixes distributed by the UE to SMF when newly added first IPv6 marking bits exist in PFCP session creation request messages and the first IPv6 marking bits are used for indicating UPF to report the IPv6 address prefixes distributed by the UE to the SMF, or reporting the obtained IPv6 address prefixes and IPv6interface IDs distributed by the UE to the SMF when newly added first IPv6 marking bits exist in the PFCP session creation request messages and the first IPv6 is used for indicating the UPF to report the IPv6 address prefixes and the IPv6interface IDs distributed by the UE to the SMF. Finally, the SMF obtains the IPv6interface ID and the IPv6 address prefix assigned by the UE. It can be seen that the IPv6interface ID of the UE sent by the UPF to the SMF in this embodiment is the result of LNS negotiation, and meanwhile, the UPF reports to the SMF in a manner of reading a packet sent by the UE or a packet sent to the UE to obtain an IPv6 address prefix allocated to the UE, or an IPv6interface ID and an IPv6 address prefix, so that the SMF can obtain a unique and complete IPv6 address allocated to the UE by the LNS according to the IPv6interface ID and the IPv6 address prefix allocated to the UE, and can also avoid a problem that the session binding property of the 5G core network cannot be supported.

After the flowchart shown in fig. 3 is completed, as an embodiment, as shown in fig. 4, sending the obtained IPv6interface ID to the SMF instep 101 includes: and carrying the obtained IPv6interface ID in a PFCP session creation response message and sending the PFCP session creation response message to the SMF.

The obtained IPv6interface ID is carried in the newly added IPv6interface identifier field in the L2TP Session establishment cell Created L2TP Session IE field in the PFCP Session creation response message.

It can be seen that, an IPv6 Identifier field, that is, an IPv6Interface Identifier, is newly added to the L2TP Session establishment cell Created L2TP Session IE field in the PFCP Session creation response message, where the IPv6Interface Identifier is used to indicate that the IPv6Interface ID is carried.

In this embodiment, the UPF carries the obtained IPv6interface ID in the PFCP session creation response message, and sends the response message to the SMF.

The L2TP Session in the PFCP Session creation response message of this embodiment establishes the cell Created L2TP Session IE field to support carrying the IPv6interface ID, as shown in table 1:

table 1 extended Created L2TP Session IE

The L2TP Session establishment new added cell Type Created L2TP Session IE Type = 279 (decimal) in table 1 indicates that the IE Type value of the Created L2TP Session is 279 representing decimal.

Information elements: an information element.

Condition/Comment: condition/comment.

Length: and (4) message length.

O: the representation is optional.

Sxa, Sxb, Sxc, and N4: respectively, the corresponding different interface identifiers between the 4G or 5G network elements, which will not be described in detail here. X indicates support, and-indicates not support.

IPv6Interface Identifier: the IPv6Interface Identifier field added in the Created L2TP Session IE field, and the corresponding IPv6Interface Identifier IE are also the newly added cell type, as shown in table 2 below.

TABLE 2 newly-added IPv6Interface Identifier IE

Bits in table 2: representing a bit. 5 to o indicates 5 to an optional number of bits.

As an embodiment, thestep 102 of obtaining at least an IPv6 address prefix allocated to the UE by reading a message sent by the UE or a message sent to the UE includes: and obtaining the IPv6 address prefix distributed by the UE or obtaining the IPv6interface ID and the IPv6 address prefix distributed by the UE by reading a router Request (RS) message and/or a router Response (RA) message responded by the LNS sent by the UE.

In this step, on the premise that the UPF has obtained the IPv6interface ID allocated by the UE instep 101 and transmitted to the UE through the SMF, in some embodiments, the IPv6 address prefix allocated by the UE, or the IPv6interface ID and the IPv6 address prefix allocated by the UE may be obtained from reading the RS packet sent by the UE. As for obtaining the IPv6 address prefix distributed by the UE, or the IPv6interface ID and the IPv6 address prefix distributed by the UE, the relation exists between the information carried by the RS message sent by the UE, and if the RS message carries the IPv6 address prefix, the IPv6 address prefix is obtained; and if the RS message carries the IPv6interface ID and the IPv6 address prefix, obtaining the IPv6interface ID and the IPv6 address prefix distributed by the UE.

Based on the same theoretical basis as above, in other embodiments, the IPv6 address prefix allocated to the UE, or the IPv6interface ID and IPv6 address prefix allocated to the UE may be obtained from reading the packet sent to the UE. When the message carrying the IPv6 address prefix to the UE at this time, the IPv6 address prefix is obtained, and the IPv6interface ID allocated before the UE is combined, based on this, for the UPF, the IPv6interface ID and the IPv6 address prefix allocated to the UE can also be obtained.

In other embodiments, the IPv6 address prefix allocated to the UE, or the IPv6interface ID and IPv6 address prefix allocated to the UE, may be obtained from reading the RS packet sent by the UE and the packet sent to the UE.

In some embodiments, as shown in fig. 4, the reporting of the IPv6 address prefix allocated to the UE, which is obtained by the step of reporting to the SMF, includes the following steps:

and step A, executing step B when only the IPv6 address prefix distributed to the UE is obtained, and executing step C when the IPv6interface ID and the IPv6 address prefix distributed to the UE are obtained.

And step B, carrying the obtained IPv6 address prefix distributed by the UE in a PFCP session report message and reporting the message to the SMF. The PFCP session report message carries a second IPv6 flag bit, where the second IPv6 flag bit is used to characterize that an IPv6 address prefix allocated to the UE is filled in a UE IP address field in the PFCP session report message; the reported IPv6 address prefix distributed to the UE is carried in the UE IP address field in the PFCP session report message.

The second IPv6in this step is only named for the convenience of distinguishing it from other IPv6 flag bits, and is not intended to limit a certain IPv6 flag bit.

In this embodiment, the UDF finds the first IPv6 flag bit, determines, according to the first IPv6 flag bit, to report the IPv6 address prefix allocated to the SMF, and on this premise, carries the obtained IPv6 address prefix allocated to the UE in the PFCP session report message and reports the UE IP address field to the SMF according to the second IPv6 flag bit.

And step C, only carrying the obtained IPv6 address prefix distributed by the UE in a PFCP session report message and reporting the message to the SMF.

In this step, even if the UDF obtains the IPv6interface ID and the IPv6 address prefix allocated to the UE, according to the indication of the first IPv6 flag bit and the content represented by the second IPv6 flag bit, only the UE IP address field in the PFCP session report message, which is carried by the obtained IPv6 address prefix allocated to the UE, is reported to the SMF.

As another embodiment, the implementation of reporting the IPv6 address prefix and the IPv6interface ID allocated to the UE, obtained instep 102, to the SMF includes the following steps:

and D, when only the IPv6 address prefix distributed to the UE is obtained, executing the step E, and when the IPv6interface ID and the IPv6 address prefix distributed to the UE are obtained, executing the step F.

And step E, carrying the obtained IPv6interface ID and IPv6 address prefix distributed by the UE in a PFCP session report message and reporting the PFCP session report message to the SMF. The PFCP session report message carries a second IPv6 flag bit, where the second IPv6 flag bit is used to characterize that an IPv6interface ID and an IPv6 address prefix allocated to the UE are filled in a UE IP address field in the PFCP session report message. And the reported IPv6interface ID and IPv6 address prefix distributed by the UE are carried in the UE IP address field in the PFCP session report message.

In this embodiment, the UDF finds the first IPv6 flag bit, determines to report the IPv6 address prefix and the IPv6interface ID allocated to the SMF according to the first IPv6 flag bit, and reports the obtained IPv6 address prefix allocated to the UE and the IPv6interface ID stored locally before to the SMF according to the second IPv6 flag bit on the premise that the UE IP address field in the PFCP session report message is carried by the obtained IPv6 address prefix allocated to the UE and the obtained IPv6interface ID.

And F, carrying the obtained IPv6interface ID and IPv6 address prefix distributed by the UE in a PFCP session report message and reporting the PFCP session report message to the SMF.

In this step, according to the indication of the first IPv6 flag bit and the content represented by the second IPv6 flag bit, the obtained IPv6 address prefix and IPv6interface ID allocated to the UE are directly carried in the UE IP address field in the PFCP session report message and reported to the SMF.

Based on the above embodiment, the Reporting triggering cells Reporting triggerers IE in the Create URR IE in the extended PFCP session creation request, and the Usage Reporting triggering cells using Report IE and the UE IP address cells UE IP address IE in the volume Reporting cells using Report IE in the extended PFCP session Reporting request, so as to support the UPF to obtain the IPv6 address allocated to the UE and Report to the SMF, as shown in table 3, table 4, and table 5:

TABLE 3 extended Reporting Triggers IE

Spare in table 3, indicates a reserved field, which may be used for an extension field.

XX in tables 3-5 are all general contents of 3GPP protocols, and XX is omitted here and is not shown again.

Table 4 extended Usage Report IE

Table 5 extended use Report Trigger IE

In the PFCP session creation request message, setting a second IPv6 marking bit extended by a Reporting Triggers IE, wherein the second IPv6 marking bit represents that an IPv6 address prefix distributed for the UE is filled in a UE IP address field in the PFCP session Reporting message, or an IPv6interface ID and an IPv6 address prefix distributed for the UE are filled in the UE IP address field. After acquiring the IPv6interface ID and IPv6 address prefix allocated to the UE, the UPF reports the IPv6 address prefix, which is filled in the UE IP address field in the Usage reporting information Usage Report IE in the PFCP session Report message, or the IPv6interface ID and IPv6 address prefix allocated to the UE to the SMF, as to whether the IPv6 address prefix is filled in the UE IP address field in table 4, or the IPv6interface ID and IPv6 address prefix allocated to the UE are filled, which is related to the second IPv6 flag bit, if the second IPv6 flag bit is used to characterize that the IPv6 address prefix allocated to the UE is filled in the UE IP address field in the PFCP session Report message, the corresponding field in table 4 is filled with the IPv6 address prefix allocated to the UE, and if the second IPv6 flag bit is used to characterize that the IPv6interface ID and the IPv6 address prefix allocated to the UE are filled in the UE address field in the PFCP session Report message, the corresponding fields in this table 4 are filled with the IPv6interface ID and IPv6 address prefix assigned by the UE.

As an embodiment, after obtaining the IPv6 address prefix and the IPv6interface ID allocated to the UE by the SMF, the SMF generates an IPv6 address belonging to the UE according to the IPv6 address prefix and the IPv6interface ID, and sends the IPv6 address to the PCF (Policy Control Function, Policy Control report) with the trigger event of the UE address change, see fig. 4.

As another embodiment, after the SMF obtains the IPv6 address prefix and IPv6interface ID allocated to the UE, the SMF reports the obtained IPv6 address prefix and IPv6interface ID allocated to the UE to the PCF as a trigger event of the UE address change.

In order to make the above embodiments easier to understand, the following description is now made on the whole interaction process for acquiring the IPv6 address in fig. 4, specifically:

UE initiates a session creation request for requesting to distribute IPv6interface ID to SMF, when SMF receives PFCP session creation request initiated by UE, the SMF selects a UPF supporting L2TP characteristic according to characteristic list negotiated by SMF and UPF locally for accessing. At this time, the selected UPF completes the L2TP tunnel establishment, L2TP session establishment, PPP negotiation process with the LNS in sequence, and completes the authentication authorization at both ends, UE address allocation, L2TP data channel link establishment, and the like. And then, sending the processing result back to the SMF, finally responding to the UE, and completing the access process of the UE.

The SMF instructs the UPF to allocate the IPv6interface ID to the UE according to the PFCP session creation request message, and the UPF locally selects the LNS to complete the IPv6interface ID allocation process. And the UPF acquires an IPv6interface ID in the PPP negotiation process with the LNS, sends the acquired IPv6interface ID to the SMF, carries the acquired IPv6interface ID in a PFCP session establishment response message and sends the PFCP session establishment response message to the SMF. And the SMF analyzes the PFCP session establishment response message to acquire the IPv6interface ID, carries the acquired IPv6interface ID in the session establishment response message and sends the IPv 3556 interface ID to the UE requesting to distribute the IPv6interface ID.

The UE sends an RS packet encapsulating a GTP header and requesting an IPv6 address prefix to the UPF through the gNB, the RS packet encapsulating the GTP header is the RS (GTP/IPv 6) in fig. 4, the UPF receives the RS packet, decapsulates the GTP header of the RS packet, encapsulates the L2TP header to the RS packet after decapsulating the GTP header, sends the RS packet encapsulating the L2TP header to the LNS, the RS packet encapsulating the L2TP header is the RS (L2 TP/IPv 6) in fig. 4, the LNS receives the RS packet, decapsulates the L2TP header of the RS packet, the LNS sends an RA packet carrying an IPv6 address prefix and encapsulating the L2TP header to the UPF, the RA packet is a response packet determined according to the RS packet, the RA packet encapsulating the L2TP header is the RA (L2 TP/RA) carrying the IPv6 address prefix in fig. 4 (L2 TP/2), the UPF receives the RA packet, decapsulates the RA packet, the RA packet of the RA packet is an L2 RA 8, and decapsulates the GTP header 23 and sends the GTP header to the UE after decapsulating the IPv6 header carrying the IPv 2 packet carrying the IPv 2 address prefix to the IPv 638, the RA packet encapsulating the GTP header is the RA carrying the IPv6 address prefix in fig. 4 (GTP/IPv 6). For the UPF, the UPF may receive an RS packet that carries the IPv6interface ID and the IPv6 address prefix allocated to the UE and is sent by the UE, or an RS packet that carries the IPv6 address prefix allocated to the UE; the UPF may also analyze an obtained RA packet of the IPv6 address prefix allocated to the UE to obtain an IPv6 prefix address, and in addition, in view of that the UPF has previously obtained an IPv6interface ID allocated to the UE, based on this, the UPF can obtain IPv6 address information allocated to the UE, and the IPv6 address information is the IPv6 address prefix and the IPv6interface ID.

The method comprises the steps that an SMF sends a PFCP session report request carrying PFCP session creation request information in the process of creating PFCP sessions between the SMF and an UPF, and when the UPF determines that a newly added first IPv6 marking bit exists in a received PFCP session creation request information and the first IPv6 marking bit is used for indicating the UPF to report the IPv6 address prefix distributed by UE to the SMF, the obtained IPv6 address prefix distributed by the UE is carried in the PFCP session report information serving as a PFCP session report response and reported to the SMF.

Or when the UPF determines that the newly added first IPv6 flag bit exists in the received PFCP session creation request message and the first IPv6 is used for indicating the UPF to report the IPv6 address prefix and the IPv6interface ID allocated to the UE to the SMF, reporting the IPv6 address prefix and the IPv6interface ID allocated to the UE to the SMF. At this time, the SMF obtains a PFCP session report message that is a PFCP session report response and carries the Pv6interface ID and IPv6 address prefix allocated to the UE.

After the SMF obtains the IPv6 address prefix and the IPv6interface ID which are distributed by the UE, the SMF generates an IPv6 address based on the IPv6 address prefix and the IPv6interface ID which are distributed by the UE, the IPV6 address is sent to the PCF according to the triggering event of the UE address change, and the SMF carries the IP address in the Npcf _ SMpolicyControl _ Update according to the triggering event of the UE address change and sends the IP address to the PCF. After successfully updating the IPv6 address of the UE, the PCF sends 200 OK for indicating that the updating of the address of the UE is successful to the SMF.

The description of the flow in fig. 4 is completed.

Fig. 5 is a diagram of an information sending apparatus 500 according to an embodiment of the present application, where the apparatus is applied to a user plane network element UPF, and includes:

an interface ID sending unit 501, configured to obtain an IPv6interface ID during a point-to-point protocol PPP negotiation with the LNS, send the obtained IPv6interface ID to the SMF, and enable the SMF to allocate the IPv6interface ID to the UE that requests allocation of the IPv6interface ID to the SMF;

an IPv6 address information obtaining unit 502, configured to obtain at least an IPv6 address prefix allocated to the UE by reading a packet sent by the UE or a packet sent to the UE, and when a received PFCP session creation request message sent in a process of creating a PFCP session between the UPF and an SMF includes a newly added first IPv6 flag bit, and the first IPv6 flag bit is used to indicate the UPF to report the IPv6 address prefix allocated to the UE to the SMF, report the obtained IPv6 address prefix allocated to the UE to obtain, by the SMF, the IPv6interface ID and the IPv6 address prefix allocated to the UE; or when a newly added first IPv6 flag bit exists in a received PFCP session creation request message sent in the process of creating a PFCP session between the UPF and the SMF, and the first IPv6 is used for indicating that the UPF reports the IPv6 address prefix and the IPv6interface ID allocated to the UE to the SMF, reporting the obtained IPv6 address prefix and the IPv6interface ID allocated to the UE to the SMF, so that the SMF obtains the IPv6interface ID and the IPv6 address prefix allocated to the UE.

As an embodiment, the interface ID sending unit 501 is specifically configured to:

carrying the obtained IPv6interface ID in a PFCP session creation response message and sending the PFCP session creation response message to the SMF;

the obtained IPv6interface ID is carried in a newly added IPv6interface identification field in the L2TP Session establishment cell Created L2TP Session IE field in the PFCP Session creation response message.

As an embodiment, the IPv6 address information obtaining unit 502 is specifically configured to;

and obtaining the IPv6 address prefix distributed by the UE or obtaining the IPv6interface ID and the IPv6 address prefix distributed by the UE by reading a router Request (RS) message and/or a router Response (RA) message responded by the LNS sent by the UE.

As an embodiment, the IPv6 address information obtaining unit 502 includes a first reporting subunit, configured to report the obtained IPv6 address prefix allocated to the UE to the SMF, and specifically configured to:

when only the IPv6 address prefix distributed to the UE is obtained, the obtained IPv6 address prefix distributed to the UE is carried in a PFCP session report message and reported to the SMF;

when the IPv6interface ID and the IPv6 address prefix distributed by the UE are obtained, only the obtained IPv6 address prefix distributed by the UE is carried in a PFCP session report message and reported to the SMF;

the PFCP session report message carries a second IPv6 flag bit, where the second IPv6 flag bit is used to characterize that an IPv6 address prefix allocated to the UE is filled in a UE IP address field in the PFCP session report message;

the reported IPv6 address prefix distributed by the UE is carried in the UE IP address field in the PFCP session report message.

As an embodiment, the IPv6 address information obtaining unit 502 includes a second reporting subunit, configured to report, to the SMF, the obtained IPv6 address prefix and IPv6interface ID allocated to the UE, and specifically configured to:

when only the IPv6 address prefix distributed to the UE is obtained, the obtained IPv6interface ID and IPv6 address prefix distributed to the UE are carried in a PFCP session report message and reported to the SMF;

when the IPv6interface ID and the IPv6 address prefix distributed by the UE are obtained, the obtained IPv6interface ID and the IPv6 address prefix distributed by the UE are carried in a PFCP session report message and reported to the SMF;

the PFCP session report message carries a second IPv6 marking bit, wherein the second IPv6 marking bit is used for representing that an IPv6interface ID and an IPv6 address prefix distributed for the UE are filled in a UE IP address field in the PFCP session report message;

the reported IPv6interface ID and IPv6 address prefix distributed to the UE are carried in the UE IP address field in the PFCP session report message.

As can be seen from the above technical solutions, in the embodiment of the present application, the UPF in the 5G core network obtains an IPv6interface ID during PPP negotiation with the LNS, and sends the obtained IPv6interface ID to the SMF, so that the SMF allocates the IPv6interface ID to the UE; the method comprises the steps of at least obtaining IPv6 address prefixes distributed by UE through reading messages sent by the UE or messages sent to the UE, reporting at least obtained IPv6 address prefixes distributed by the UE to SMF when a newly added first IPv6 marking bit exists in PFCP session creation request messages and the first IPv6 marking bit is used for indicating UPF to report the IPv6 address prefixes distributed by the UE to the SMF, or reporting the obtained IPv6 address prefixes and the IPv6interface IDs distributed by the UE to the SMF when the newly added first IPv6 marking bit exists in the PFCP session creation request messages and the first IPv6 is used for indicating the UPF to report the IPv6 address prefixes and the IPv6interface IDs distributed by the UE to the SMF. Finally, the SMF obtains the IPv6interface ID and the IPv6 address prefix which are allocated by the UE. It can be seen that the IPv6interface ID of the UE sent by the UPF to the SMF in this embodiment is the result of LNS negotiation, and meanwhile, the UPF reports to the SMF in a manner of reading a packet sent by the UE or a packet sent to the UE to obtain an IPv6 address prefix allocated to the UE, or an IPv6interface ID and an IPv6 address prefix, so that the SMF can obtain a unique and complete IPv6 address allocated to the UE by the LNS according to the IPv6interface ID and the IPv6 address prefix allocated to the UE, and can also avoid a problem that the session binding property of the 5G core network cannot be supported.

The implementation process of the functions and actions of each unit in the above device is specifically described in the implementation process of the corresponding step in the above method, and is not described herein again.

In the electronic device provided in the embodiment of the present application, from a hardware level, a schematic diagram of a hardware architecture may be shown in fig. 6. The method comprises the following steps: a machine-readable storage medium and a processor, wherein: the machine-readable storage medium stores machine-executable instructions executable by the processor; the processor is configured to execute machine-executable instructions to perform the operations disclosed in the above examples for information transmission.

Machine-readable storage media are provided by embodiments of the present application that store machine-executable instructions that, when invoked and executed by a processor, cause the processor to perform operations for information transmission as disclosed in the above examples.

Here, a machine-readable storage medium may be any electronic, magnetic, optical, or other physical storage device that can contain or store information such as executable instructions, data, and so forth. For example, the machine-readable storage medium may be: RAM (random Access Memory), volatile Memory, non-volatile Memory, flash Memory, a storage drive (e.g., a hard drive), a solid state drive, any type of storage disk (e.g., an optical disk, a dvd, etc.), or similar storage medium, or a combination thereof.

The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. A typical implementation device is a computer, which may take the form of a personal computer, laptop computer, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email messaging device, game console, tablet computer, wearable device, or a combination of any of these devices.

For convenience of description, the above devices are described as being divided into various units by function, and are described separately. Of course, the functionality of the units may be implemented in one or more software and/or hardware when implementing the present application.

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, embodiments of 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, CD-ROM, 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.

Furthermore, 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.

For the device embodiments, since they substantially correspond to the method embodiments, reference may be made to the partial description of the method embodiments for relevant points. The above-described embodiments of the apparatus are merely illustrative, and 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 position, or may be distributed on multiple network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the scheme of the application. One of ordinary skill in the art can understand and implement without inventive effort.

So far, the description of the apparatus shown in fig. 5 is completed.

The above description is only exemplary of the present application and should not be taken as limiting the present application, as any modification, equivalent replacement, or improvement made within the spirit and principle of the present application should be included in the scope of protection of the present application.

Claims (11)

1. An information sending method, characterized in that the method is applied to a user plane network element (UPF), and comprises:

acquiring an IPv6interface identification ID in the PPP negotiation process with the LNS, sending the acquired IPv6interface ID to the SMF, and allocating the IPv6interface ID to the UE which requests the allocation of the IPv6interface ID to the SMF by the SMF;

the method comprises the steps that at least an IPv6 address prefix distributed by UE is obtained by reading a message sent by the UE or a message sent to the UE, when a newly added first IPv6 marking bit exists in a PFCP session creation request message sent in the process of creating a PFCP session between a UPF and an SMF and the first IPv6 marking bit is used for indicating the UPF to report the IPv6 address prefix distributed by the UE to the SMF, the IPv6 address prefix distributed by the UE obtained by reporting is reported to the SMF, and the SMF obtains the IPv6interface ID and the IPv6 address prefix distributed by the UE; or when a newly added first IPv6 flag bit exists in a received PFCP session creation request message sent in a process of creating a PFCP session between the UPF and the SMF, and the first IPv6 is used for indicating the UPF to report the IPv6 address prefix and the IPv6interface ID allocated to the UE to the SMF, reporting the IPv6 address prefix and the IPv6interface ID allocated to the UE, which are obtained by the SMF, so that the SMF obtains the IPv6interface ID and the IPv6 address prefix allocated to the UE.

2. The method of claim 1, wherein sending the obtained IPv6interface ID to the SMF comprises:

carrying the obtained IPv6interface ID in a PFCP session creation response message and sending the PFCP session creation response message to the SMF;

the obtained IPv6interface ID is carried in the newly added IPv6interface identifier field in the L2TP Session establishment cell Created L2TP Session IE field in the PFCP Session creation response message.

3. The method according to claim 1, wherein said obtaining at least the IPv6 address prefix allocated to the UE by reading the packet sent by or to the UE comprises:

and obtaining the IPv6 address prefix distributed by the UE or obtaining the IPv6interface ID and the IPv6 address prefix distributed by the UE by reading a router Request (RS) message and/or a router Response (RA) message responded by the LNS sent by the UE.

4. The method of claim 1, wherein the reporting the obtained IPv6 address prefix allocated to the UE to the SMF comprises:

when only the IPv6 address prefix distributed by the UE is obtained, the obtained IPv6 address prefix distributed by the UE is carried in a PFCP session report message and reported to the SMF;

when the IPv6interface ID and the IPv6 address prefix distributed by the UE are obtained, only the obtained IPv6 address prefix distributed by the UE is carried in a PFCP session report message and reported to the SMF;

the PFCP session report message carries a second IPv6 flag bit, where the second IPv6 flag bit is used to characterize that an IPv6 address prefix allocated to the UE is filled in a UE IP address field in the PFCP session report message;

the reported IPv6 address prefix distributed by the UE is carried in the UE IP address field in the PFCP session report message.

5. The method of claim 1, wherein the reporting the obtained IPv6 address prefix and IPv6interface ID allocated to the UE to the SMF comprises:

when only the IPv6 address prefix distributed by the UE is obtained, the obtained IPv6interface ID and IPv6 address prefix distributed by the UE are carried in a PFCP session report message and reported to the SMF;

when the IPv6interface ID and the IPv6 address prefix distributed by the UE are obtained, the obtained IPv6interface ID and the IPv6 address prefix distributed by the UE are carried in a PFCP session report message and reported to the SMF;

the PFCP session report message carries a second IPv6 marking bit, wherein the second IPv6 marking bit is used for representing that an IPv6interface ID and an IPv6 address prefix distributed for the UE are filled in a UE IP address field in the PFCP session report message;

the reported IPv6interface ID and IPv6 address prefix distributed to the UE are carried in the UE IP address field in the PFCP session report message.

6. A message sending apparatus, which is applied to a user plane network element UPF, and comprises:

an interface ID sending unit, configured to obtain an IPv6interface ID during a point-to-point protocol PPP negotiation process with the LNS, send the obtained IPv6interface ID to the SMF, so that the SMF allocates the IPv6interface ID to the UE that requests allocation of the IPv6interface ID to the SMF;

an IPv6 address information obtaining unit, configured to obtain at least an IPv6 address prefix allocated to the UE by reading a packet sent by the UE or a packet sent to the UE, and when a received PFCP session creation request message sent in a process of creating a PFCP session between the UPF and an SMF includes a newly added first IPv6 flag bit, and the first IPv6 flag bit is used to indicate the UPF to report an IPv6 address prefix allocated to the UE to the SMF, report the obtained IPv6 address prefix allocated to the UE to obtain, by the SMF, an IPv6interface ID and an IPv6 address prefix allocated to the UE; or when a newly added first IPv6 flag bit exists in a received PFCP session creation request message sent in the process of creating a PFCP session between the UPF and the SMF, and the first IPv6 is used for indicating that the UPF reports the IPv6 address prefix and the IPv6interface ID allocated to the UE to the SMF, reporting the obtained IPv6 address prefix and the IPv6interface ID allocated to the UE to the SMF, so that the SMF obtains the IPv6interface ID and the IPv6 address prefix allocated to the UE.

7. The apparatus according to claim 6, wherein the interface ID sending unit is specifically configured to:

carrying the obtained IPv6interface ID in a PFCP session creation response message and sending the PFCP session creation response message to the SMF;

the obtained IPv6interface ID is carried in a newly added IPv6interface identification field in the L2TP Session establishment cell Created L2TP Session IE field in the PFCP Session creation response message.

8. The apparatus according to claim 6, wherein said IPv6 address information obtaining unit is specifically configured to;

and acquiring the IPv6 address prefix distributed by the UE, or acquiring the IPv6interface ID and the IPv6 address prefix distributed by the UE by reading a router request RS message and/or a router response RA message responded by the LNS sent by the UE.

9. The apparatus of claim 6, wherein the IPv6 address information obtaining unit includes a first reporting subunit configured to report the obtained IPv6 address prefix allocated to the UE to the SMF, and is specifically configured to:

when only the IPv6 address prefix distributed by the UE is obtained, the obtained IPv6 address prefix distributed by the UE is carried in a PFCP session report message and reported to the SMF;

when the IPv6interface ID and the IPv6 address prefix distributed by the UE are obtained, only the obtained IPv6 address prefix distributed by the UE is carried in a PFCP session report message and reported to the SMF;

the PFCP session report message carries a second IPv6 flag bit, where the second IPv6 flag bit is used to characterize that an IPv6 address prefix allocated to the UE is filled in a UE IP address field in the PFCP session report message;

the reported IPv6 address prefix distributed by the UE is carried in the UE IP address field in the PFCP session report message.

10. The apparatus according to claim 6, wherein the IPv6 address information obtaining unit includes a second reporting subunit, configured to report the obtained IPv6 address prefix and IPv6interface ID that are allocated to the UE to the SMF, and is specifically configured to:

when only the IPv6 address prefix distributed by the UE is obtained, the obtained IPv6interface ID and IPv6 address prefix distributed by the UE are carried in a PFCP session report message and reported to the SMF;

when the IPv6interface ID and the IPv6 address prefix distributed by the UE are obtained, the obtained IPv6interface ID and the IPv6 address prefix distributed by the UE are carried in a PFCP session report message and reported to the SMF;

the PFCP session report message carries a second IPv6 marking bit, wherein the second IPv6 marking bit is used for representing that an IPv6interface ID and an IPv6 address prefix distributed for the UE are filled in a UE IP address field in the PFCP session report message;

and the reported IPv6interface ID and IPv6 address prefix distributed by the UE are carried in the UE IP address field in the PFCP session report message.

11. An electronic device comprising a readable storage medium and a processor;

wherein the readable storage medium is configured to store machine executable instructions;

the processor configured to read the machine executable instructions on the readable storage medium and execute the instructions to implement the steps of the method of any one of claims 1 to 5.

Images