Session anchor point selection method, device, network equipment and storage medium

Abstract

The present application discloses a method, apparatus, network device, and storage medium for selecting a session anchor point. The method includes: a first terminal moves to an edge service side; the first terminal accesses a network through a first session anchor point; the terminal accessing the first session anchor point uses a first Internet Protocol (IP) domain; a session established based on the first IP domain belongs to a first session group; and the network device selects a second session anchor point for the first terminal, where the second session anchor point is bound to the first session group.

Description

Technical Field

[0001] The present application relates to the field of communications, and in particular to a method, apparatus, network device, and storage medium for selecting a session anchor point. Background Art

[0002] To meet the business requirements of edge business data not leaving the factory and low latency, the 5G network sinks the user plane function (UPF) to the business side and offloads the traffic accessing local business by means of local business diversion. For individual (2C) users, data services use the universal data network name (DNN) and generally adopt the uplink classifier (ULCL) diversion technology, such as Figure 1 As shown in the figure, ULCL UPF and PSA1 UPF (i.e., auxiliary anchor point) are deployed on the edge service side. In the same session, uplink data is sent from the base station to the ULCL UPF. The ULCL UPF diverts local traffic to the PSA1 UPF, and non-local traffic (i.e., public network traffic) is transmitted back to the primary anchor point UPF of the prefecture-level city, i.e., PSA0 UPF.

[0003] The capacity of the IPv4 private network address segment planned for users in the current network can no longer meet the needs of the Session Management Function (SMF) and UPF group pool (Pool) in some provinces with a large number of users. Therefore, when planning the network, Figure 2 As shown, the SMF only ensures that users accessing the UPF under the same Network Address Translation (NAT) device use a non-duplicate private network address pool. However, users accessing the UPF under different NAT devices may use the same IPv4 private network address. Therefore, when users access from UPFs in different offices (i.e., different NAT devices), they may be assigned the same IPv4 private network address. If these users all need to insert a local offload UPF (ULCL+PSA1 UPF) to access local services, if the same local offload UPF is selected, there will be a conflict in the user Internet Protocol (IP) address under the same local auxiliary anchor UPF, which will cause the user's local offload to fail to work properly. Summary of the Invention

[0004] To solve related technical problems, embodiments of the present application provide a session anchor point selection method, apparatus, network device, and storage medium.

[0005] The technical solution of the embodiment of the present application is implemented as follows:

[0006] An embodiment of the present application provides a session anchor point selection method, applied to a network device, including:

[0007] A first terminal moves to an edge service side; the first terminal accesses a network through a first session anchor point; the terminal accessing the first session anchor point uses a first IP domain; a session established based on the first IP domain belongs to a first session group;

[0008] A second session anchor is selected for the first terminal, where the second session anchor is bound to the first session group.

[0009] In the above solution, the terminal accessing the third session anchor point uses the second IP domain; the first IP domain is the same as or different from the second IP domain.

[0010] In the above solution, selecting a second session anchor point for the first terminal includes:

[0011] A session anchor point is selected from at least one session anchor point bound to the first session group as a second session anchor point selected for the first terminal.

[0012] In the above solution, selecting a second session anchor point for the first terminal includes:

[0013] selecting a session anchor from at least one session anchor that is not bound to at least one session group;

[0014] using the selected session anchor point as a second session anchor point selected for the first terminal;

[0015] Establish a binding relationship between the second session anchor point and the first session group.

[0016] In the above solution, selecting a second session anchor point for the first terminal includes:

[0017] receiving a first message sent by a fourth session anchor point; the first message indicating that establishment of a session between the fourth session anchor point and the first terminal has failed; and the session of the fourth session anchor point includes a session of a second terminal having the same IP domain as the first terminal;

[0018] reselecting the second session anchor point for the first terminal;

[0019] Establish a binding relationship between the second session anchor point and the first session group.

[0020] In the above solution, the method further includes:

[0021] When there is no locally split session for the second session anchor point, the second session anchor point is deleted, and a binding relationship between the second session anchor point and the first session group is deleted.

[0022] In the above solution, the locally split session without the second session anchor point includes:

[0023] When the local session anchor point of the first session anchor point is updated to the fifth session anchor point, there is no locally split session of the second session anchor point.

[0024] In the above solution, the locally split session without the second session anchor point includes:

[0025] When the first session anchor point no longer requires local traffic diversion, there is no session for local traffic diversion by the second session anchor point.

[0026] In the above solution, the method further includes:

[0027] After selecting the second session anchor point for the first terminal, the downlink tunnel endpoint information of the first session anchor point and the uplink tunnel endpoint information of the new radio (NR) are updated.

[0028] The embodiment of the present application further provides a session anchor point selection device, comprising:

[0029] An access processing unit is configured to enable a first terminal to move to an edge service side, so that the first terminal accesses a network through a first session anchor point; the terminal accessing the first session anchor point uses a first IP domain; and a session established based on the first IP domain belongs to a first session group;

[0030] The selecting unit is configured to select a second session anchor point for the first terminal, where the second session anchor point has a binding relationship with the first session group.

[0031] The embodiment of the present application further provides a network device, comprising: a processor and a communication interface; wherein,

[0032] The processor is configured to move a first terminal to an edge service side, enabling the first terminal to access a network through a first session anchor point; the terminal accessing the first session anchor point uses a first IP domain; the session established based on the first IP domain belongs to a first session group; and select a second session anchor point for the first terminal, where the second session anchor point has a binding relationship with the first session group.

[0033] The embodiment of the present application further provides a network device, comprising: a processor and a memory for storing a computer program that can be run on the processor,

[0034] The processor is configured to execute the steps of any of the above methods when running the computer program.

[0035] An embodiment of the present application further provides a storage medium on which a computer program is stored. When the computer program is executed by a processor, the steps of any of the above methods are implemented.

[0036] The embodiment of the present application provides a session anchor selection method, apparatus, network device, and storage medium. The first terminal moves to the edge service side; the first terminal accesses the network through the first session anchor; the terminal accessing the first session anchor uses the first IP domain; the session established based on the first IP domain belongs to the first session group; the network device selects a second session anchor for the first terminal, and the second session anchor has a binding relationship with the first session group. The solution provided by the embodiment of the present application ensures that users assigned the same IP address select different local diversion session anchors when inserting into the local diversion session anchor through the binding relationship between the session group and the local diversion session anchor, so that all users can perform local diversion normally. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] Figure 1 is a schematic diagram of a ULCL network architecture;

[0038] Figure 2 This is a schematic diagram of IP address planning;

[0039] Figure 3 This is a schematic diagram of selecting different local offload UPFs for terminals accessing the same IP address pool UPF according to an embodiment of the present application;

[0040] Figure 4 A flow chart of the method for selecting a session anchor point according to an embodiment of the present application;

[0041] Figure 5 A schematic diagram of the process of allocating a local offload UPF according to an embodiment of the present application;

[0042] Figure 6 This is a flow chart of the terminal updating the local offload UPF in the application embodiment of the present application;

[0043] Figure 7 This is a flow chart of deleting the local offload UPF in the embodiment of the present application;

[0044] Figure 8 This is a structural diagram of a session anchor point selection device according to an embodiment of the present application;

[0045] Figure 9 This is a schematic diagram of the network device structure of an embodiment of the present application. DETAILED DESCRIPTION

[0046] The present application will be described in further detail below with reference to the embodiments.

[0047] Users accessed by UPF under the same NAT device use a non-repeated private network address pool, but users accessed by UPF under different NAT devices may use the same IPv4 private network address. When users assigned the same IP address (i.e. the same IPv4 private network address) insert a local split UPF, they need to select a different local split UPF to ensure that all users can perform ULCL local splitting, such as Figure 3 Here, in actual application, the ULCL UPF and the auxiliary anchor point UPF can be set together during deployment.

[0048] Based on this, in various embodiments of the present application, an independent session group is established for the session accessing the UPF group, and the binding relationship between the session group and the local diversion anchor point is maintained. Through the binding relationship between the session group and the local diversion session anchor point, it is ensured that when users assigned the same IP address insert into the local diversion session anchor point, different local diversion session anchor points are selected.

[0049] The embodiment of the present application provides a session anchor point selection method, which is applied to a network device, such as Figure 4 As shown, the method includes:

[0050] Step 401: A first terminal moves to an edge service side; the first terminal accesses a network through a first session anchor point; the terminal accessing the first session anchor point uses a first IP domain; a session established based on the first IP domain belongs to a first session group;

[0051] Step 402: Select a second session anchor for the first terminal, where the second session anchor is bound to the first session group.

[0052] In actual application, the network device may be an SMF, and the terminal may be referred to as a user equipment (UE) or a user.

[0053] In step 401, in actual application, the network device allocates a first session anchor point to the first terminal according to a session establishment request initiated by the first terminal, so that the first terminal accesses the network through the first session anchor point.

[0054] The first terminal accesses the network through the first session anchor point, which can be understood as the first terminal establishing a protocol data unit (PDU) session through the first session anchor point, specifically referring to the network device establishing a PDU session for the terminal.

[0055] The first session anchor point is the primary session anchor point; accordingly, when the first terminal moves to the edge service side, it is necessary to insert a local split session anchor point (including ULCL+PSA1 UPF) for the terminal. Therefore, the second session anchor point can also be called a local split session anchor point (can be referred to as a local split anchor point for short), and the second session anchor point is a secondary session anchor point. Figure 3 It can be seen that the first session anchor point can also be called the primary anchor point UPF, that is, PSA0 UPF, such as PSA0UPF1 and PSA0 UPF2, and the second session anchor point can also be called the local split UPF, that is, ULCL+PSA1 UPF, such as ULCL+PSA1 UPF1 and ULCL+PSA1 UPF2. Figure 3 In the ULCL UPF, the auxiliary anchor point UPF is set together.

[0056] An IP domain may also be referred to as an IP segment or an IP address pool. Therefore, the first IP domain may also be referred to as a first IP segment or a first IP address pool.

[0057] In actual application, the terminal accessing the first session anchor point uses a different IP address.

[0058] In an embodiment of the present application, a terminal accessing other primary session anchor points different from the first session anchor point uses the IP domain planned by the network device for the other primary session anchor points, and the IP domain of the other primary session anchor points may be the same as or different from the IP domain of the first session anchor point.

[0059] Specifically, in one embodiment, the terminal accessing the third session anchor point uses a second IP domain; the first IP domain is the same as or different from the second IP domain.

[0060] Here, the third session anchor point is the primary session anchor point. The second IP domain may also be referred to as a second IP segment or a second IP address pool.

[0061] In this case, the IP address used by the terminal accessing the first session anchor point and the IP address used by the terminal accessing the third session anchor point may be the same or different.

[0062] At least one local diversion anchor point corresponding to a main anchor point can be called a local diversion anchor point group, specifically a UPF group. The network device establishes an independent session group for a session accessing a local diversion anchor point group, that is, a main anchor point corresponds to an independent session group, and plans the same or different IP domains for each local diversion anchor point group, that is, the IP address pool (i.e., IP domain) used between groups can be repeated.

[0063] In step 402, selecting the second session anchor point for the first terminal may be referred to as inserting the second session anchor point for the first terminal.

[0064] When there is no binding relationship between the second session anchor point and the first session group, the network device needs to establish a binding relationship between the second session anchor point and the first session group and save it; when there is already a binding relationship between the second session anchor point and the first session group, that is, the network device has saved the binding relationship between the second session anchor point and the first session group, the network device does not need to establish a binding relationship.

[0065] In actual application, the network device can use the conditions for inserting a local diversion anchor point, such as the location of the first terminal, to select a second session anchor point for the first terminal. The selected second session anchor point may be a session anchor point that has established a binding relationship with the first session group, or it may be other available session anchor points that have not established a binding relationship with the first response group.

[0066] The timing for the network device to establish the first session group for the first session anchor point can be set as needed. For example, after the network device starts communicating with the first session anchor point, it establishes the first session group for the first session anchor point.

[0067] When the selected second session anchor point is a session anchor point that has established a binding relationship with the first session group, the network device selects a session anchor point from at least one second session anchor point bound to the first session group, and uses the selected session anchor point as the second session anchor point selected for the first terminal.

[0068] In the case where the selected second session anchor point is not a session anchor point with which a binding relationship has been established with the first session group, the network device may select in the following two ways:

[0069] In a first manner, the network device directly selects. Specifically, the network device may select a session anchor point from at least one session anchor point that is not bound to at least one session group; use the selected session anchor point as the second session anchor point selected for the first terminal; establish a binding relationship between the second session anchor point and the first session group, and save the binding relationship between the second session anchor point and the first session group;

[0070] The second method is that the network device initiates reselection through other local diversion session anchor points. Specifically, the network device randomly selects a local diversion session anchor point, and the randomly selected local diversion session anchor point initiates reselection; specifically, the first message sent by the fourth session anchor point is received; the first message indicates that the session establishment between the fourth session anchor point and the first terminal has failed; the session of the fourth session anchor point includes a session of a second terminal with the same IP domain as the first terminal; the second session anchor point is reselected for the first terminal; and a binding relationship between the second session anchor point and the first session group is established, and the binding relationship between the second session anchor point and the first session group is saved.

[0071] The network device needs to maintain the binding relationship between the session group and the local traffic distribution anchor point, and the maintenance includes establishing and releasing the binding relationship.

[0072] Based on this, in one embodiment, when there is no locally split session of the second session anchor point, the second session anchor point is deleted, and the binding relationship between the second session anchor point and the first session group is deleted.

[0073] When the local session anchor of the first session anchor is updated to the fifth session anchor, the locally branched session of the second session anchor no longer exists. That is, when the network device updates the local session anchor of the first session anchor as needed, the locally branched session of the second session anchor is updated to the new local session anchor, and the locally branched session of the second session anchor no longer exists.

[0074] When the first session anchor point no longer requires local traffic diversion, the locally diverted session of the second session anchor point no longer exists. That is, when the network device determines, as needed, that the first session anchor point no longer requires local traffic diversion, the network device deletes the locally diverted session anchor point, and the locally diverted session of the second session anchor point no longer exists.

[0075] The network device interacts with the local offload session anchor point to delete all local offload sessions on the local offload session anchor point, thereby deleting the local offload session anchor point.

[0076] In actual application, after the second session anchor point is selected for the terminal, uplink and downlink information needs to be updated so that data can be transmitted in the correct tunnel.

[0077] Based on this, in one embodiment, the method may further include:

[0078] After selecting the second session anchor point for the first terminal, update the downlink tunnel endpoint information of the first session anchor point and the uplink tunnel endpoint information of the NR.

[0079] The session anchor point selection method provided in the embodiment of the present application is as follows: a first terminal moves to the edge service side; the first terminal accesses the network through the first session anchor point; the terminal accessing the first session anchor point uses the first IP domain; the session established based on the first IP domain belongs to the first session group; the network device selects a second session anchor point for the first terminal, and the second session anchor point has a binding relationship with the first session group. The solution provided in the embodiment of the present application ensures that when users assigned the same IP address insert a local diversion session anchor point, different local diversion session anchor points are selected, so that all users can perform local diversion normally.

[0080] The present application will be described in further detail below in conjunction with application examples.

[0081] In this application embodiment, it is assumed that UPF1 and UPF2 are the main anchor points of the prefecture-level city, PSA 0UPF1 and PSA 0UPF2 belong to different NAT areas respectively, and the same private network address pool is planned for PSA 0UPF1 and PSA 0UPF2 on the SMF, and supports the establishment of two session groups for users accessing PSA 0UPF1 and PSA 0UPF2 (that is, the Message Forwarding Control Protocol (PFCP) sessions established in the UPF of the same private network address pool belong to different session groups, the session group of PSA 0UPF1 is called session group 1, and the session group of PSA 0UPF2 is called session group 2), maintains the binding relationship between the two session groups and the corresponding local diversion UPF, and multiple local diversion UPFs (including ULCL and auxiliary anchor point UPF) are deployed on the edge side.

[0082] In this application embodiment, the ULCL UPF and the auxiliary anchor point UPF are combined together.

[0083] like Figure 5 As shown, the process of allocating local offload UPF in this application embodiment includes the following steps:

[0084] Step 501: Assume that UE1 accesses the network from PSA 0UPF1, where SMF allocates a private network IPv4 address to UE1, and SMF stores UE1's PFCP session in session group 1; when UE1 moves to the edge service side, SMF is triggered to insert local offload UPF1 for UE1, and SMF records the binding relationship between local offload UPF1 (i.e., ULCL+PSA1 UPF1) and session group 1.

[0085] Step 502: UE2 accesses from PSA 0UPF2, SMF allocates the same private network IPv4 address as UE1 to UE2, and SMF stores UE2's PFCP session in session group 2.

[0086] Step 503: When UE2 moves to the edge service side, SMF is triggered to insert a local offload UPF for UE2, which is called local offload UPF2. Specifically, SMF sends a PFCP session establishment request message to local offload UPF2; after receiving the message, local offload UPF 2 returns a PFCP session establishment response to SMF, that is, executes step 503c.

[0087] Among them, when inserting the local diversion UPF, if there is a bound local diversion UPF under session group 2, and the SMF can select a suitable local diversion UPF for UE2 from the bound local diversion UPF based on the conditions for inserting the local diversion UPF (such as the UE location); here, if the SMF fails to select a suitable local diversion UPF for UE2 from the bound local diversion UPF based on the conditions for inserting the local diversion UPF (such as the UE location), the SMF can select a suitable local diversion UPF for UE2 from the unbound local diversion UPF based on the conditions for inserting the local diversion UPF, and save the binding relationship between the local diversion UPF2 and session group 2.

[0088] If there is no bound local diversion UPF under session group 2, SMF selects a local diversion UPF that meets the local diversion insertion conditions except PSA 0UPF1 as the local diversion UPF of UE2, that is, selects a suitable local diversion UPF from the local diversion UPF that has not been bound, and saves the binding relationship between local diversion UPF2 and session group 2.

[0089] There are two solutions for selecting a suitable local offload UPF SMF for UE2 from an unbound local offload UPF:

[0090] The first method is that the SMF directly selects the local offload UPF. Specifically, since UE2 and UE1 access the network through different UPFs, UPF2 and UPF1 respectively, the SMF determines that UE2 and UE1 belong to different session groups. The SMF directly selects the local offload UPF2 that meets the conditions and is not bound to session group 1.

[0091] The second type is that the local diversion UPF initiates reselection. The SMF randomly selects a local diversion UPF according to the local diversion insertion conditions (such as UE location) and initiates a PFCP session establishment request message (i.e., executes step 503a). The message carries the IP address of UE2. If the same local diversion UPF as UE1 is selected, the local diversion UPF1 is selected. When the local session UPF of the local diversion UPF1 receives the PFCP session establishment request message, it finds that there is already a session with the same UE IP in the locally managed PFCP session, and then replies to the SMF with a PFCP session establishment response message (i.e., step 503b), carrying a special cause value. The cause value indicates that the PFCP session establishment failed. The cause value instructs the SMF to reselect the local diversion UPF; when the SMF receives the message of the local diversion UPF1, it re-selects a local auxiliary anchor point UPF for UE2 and completes the insertion (i.e., step 503c).

[0092] Steps 504-505: The SMF updates the downlink tunnel endpoint of the primary anchor point PSA0 UPF2 and the uplink tunnel endpoint of NR to ULCL UPF.

[0093] Among them, SMF updates the uplink tunnel endpoint of NR to the local split UPF2, that is, ULCL+PSA1 UPF2.

[0094] Among them, the local offload UPF can be updated when UE2 moves.

[0095] In this application embodiment, UE2 updates the process of local offload UPF, such as Figure 6 As shown, the following steps are included:

[0096] Step 601: UE2 establishes a session and inserts a local traffic splitting UPF, ie, an old local traffic splitting UPF (which may be referred to as an old ULCL+PSA1 UPF).

[0097] Step 602: Due to the mobility of UE2, the local offload UPF needs to be updated. That is, the SMF selects a new local offload UPF. At the same time, the SMF saves the binding relationship between the new local offload UPF (which can be called the new (new) ULCL+PSA1 UPF) and the session group to which the new local offload UPF belongs; and inserts the new local offload UPF.

[0098] Here, the selection method has been described in detail above and will not be repeated here;

[0099] Steps 603-604: SMF updates the downlink tunnel endpoint of the primary anchor point PSA0 UPF and the uplink tunnel endpoint of NR to the new local split UPF.

[0100] Step 605: SMF deletes the locally diverted session of UE2 on the old local diversion UPF, that is, SMF sends a PDCP session deletion request message to the old local diversion UPF; after receiving the message, the old local diversion UPF deletes the relevant information of the PDCP session and returns a PDCP session deletion response to SMF; if SMF finds that there is no locally diverted session on the old local diversion UPF, SMF releases the binding relationship between the old local diversion UPF and the session group.

[0101] When the UE no longer needs the local offload UPF, the SMF needs to delete the local offload UPF. The process of deleting the local offload UPF in this application embodiment is as follows: Figure 7 As shown, the following steps are included:

[0102] Step 701: The UE establishes a session and inserts a local offload UPF, then proceeds to step 702;

[0103] Step 702: Since the UE no longer needs the local offload UPF due to mobility, the SMF updates the downlink tunnel endpoint of the primary anchor point PSA0 UPF to NR;

[0104] Step 703: SMF updates the uplink tunnel endpoint of NR to PSA0 UPF;

[0105] Step 704: SMF deletes the local diversion UPF, that is, SMF sends a PDCP session deletion request message to the local diversion UPF; after receiving the message, the local diversion UPF deletes the relevant information of the PDCP session and returns a PDCP session deletion response to the SMF; if the SMF finds that there is no local diversion session on the local diversion UPF, the SMF deletes its binding relationship with the session group.

[0106] From the above description, it can be seen that the solution provided by the embodiment of the present application is that the SMF maintains the binding relationship between the session group and the local diversion anchor point, including the establishment and release of the binding relationship. Through the binding relationship between the session group and the local diversion anchor point, the problem of repeated user IP addresses during diversion can be solved, thereby ensuring that the terminal with repeated user IP addresses recognizes the normal ULCL diversion.

[0107] In order to implement the method of the embodiment of the present application, the embodiment of the present application also provides a session anchor point selection device, which is set on the network device, such as Figure 8 As shown, the device includes:

[0108] Access processing unit 801 is configured to enable a first terminal to move to an edge service side, so that the first terminal accesses a network through a first session anchor point; the terminal accessing the first session anchor point uses a first IP domain; and a session established based on the first IP domain belongs to a first session group;

[0109] The selecting unit 802 is configured to select a second session anchor point for the first terminal, where the second session anchor point has a binding relationship with the first session group.

[0110] In one embodiment, the selection unit 802 is configured to:

[0111] Selecting a session anchor point from at least one session anchor point bound to the first session group as a second session anchor point selected for the first terminal;

[0112] or,

[0113] selecting a session anchor point from at least one session anchor point that is not bound to at least one session group; using the selected session anchor point as a second session anchor point selected for the first terminal; and establishing a binding relationship between the second session anchor point and the first session group;

[0114] or,

[0115] Receiving a first message sent by a fourth session anchor point; the first message indicates that the session establishment between the fourth session anchor point and the first terminal failed; the session of the fourth session anchor point includes a session of a second terminal with the same IP domain as the first terminal; reselecting the second session anchor point for the first terminal; and establishing a binding relationship between the second session anchor point and the first session group.

[0116] In one embodiment, the selection unit 802 is further configured to:

[0117] When there is no locally split session for the second session anchor point, the second session anchor point is deleted, and a binding relationship between the second session anchor point and the first session group is deleted.

[0118] In one embodiment, the selection unit 802 is further configured to:

[0119] After selecting the second session anchor point for the first terminal, update the downlink tunnel endpoint information of the first session anchor point and the uplink tunnel endpoint information of the NR.

[0120] In actual application, the access processing unit 801 and the selection unit 802 can be implemented by a processor in the session anchor point selection device in combination with a communication interface.

[0121] It should be noted that the session anchor selection device provided in the above embodiment only uses the division of the above-mentioned program modules as an example to illustrate the selection of the session anchor. In actual applications, the above-mentioned processing can be assigned to different program modules as needed, that is, the internal structure of the device can be divided into different program modules to complete all or part of the processing described above. In addition, the session anchor selection device provided in the above embodiment and the session anchor selection method embodiment are based on the same concept. The specific implementation process is detailed in the method embodiment and will not be repeated here.

[0122] Based on the hardware implementation of the above program modules, and in order to implement the method of the embodiment of the present application, the embodiment of the present application also provides a network device, such as Figure 9 As shown, the network device 900 includes:

[0123] Communication interface 901, capable of exchanging information with other network devices;

[0124] Processor 902, connected to the communication interface 901 to implement information exchange with other network devices, and configured to execute the methods provided by one or more technical solutions on the network device side when running a computer program;

[0125] The computer program is stored in the memory 903 .

[0126] Specifically, the processor 902 is used to move the first terminal to the edge service side, so that the first terminal accesses the network through the first session anchor point; the terminal accessing the first session anchor point uses the first IP domain; the session established based on the first IP domain belongs to the first session group; and selects a second session anchor point for the first terminal, and the second session anchor point has a binding relationship with the first session group.

[0127] In one embodiment, the processor 902 is configured to:

[0128] Selecting a session anchor point from at least one session anchor point bound to the first session group as a second session anchor point selected for the first terminal;

[0129] or,

[0130] selecting a session anchor point from at least one session anchor point that is not bound to at least one session group; using the selected session anchor point as a second session anchor point selected for the first terminal; and establishing a binding relationship between the second session anchor point and the first session group;

[0131] or,

[0132] A first message sent by a fourth session anchor point is received through the communication interface 901; the first message indicates that the session establishment between the fourth session anchor point and the first terminal has failed; the session of the fourth session anchor point includes a session of a second terminal having the same IP domain as the first terminal; the second session anchor point is reselected for the first terminal; and a binding relationship between the second session anchor point and the first session group is established.

[0133] In one embodiment, the processor 902 is further configured to:

[0134] When there is no locally split session for the second session anchor point, the second session anchor point is deleted, and a binding relationship between the second session anchor point and the first session group is deleted.

[0135] In one embodiment, the selection unit 802 is further configured to:

[0136] After selecting the second session anchor point for the first terminal, update the downlink tunnel endpoint information of the first session anchor point and the uplink tunnel endpoint information of the NR.

[0137] It should be noted that the specific processing process of the processor 902 can be understood by referring to the above method.

[0138] Of course, in actual application, the various components in the network device 900 are coupled together through the bus system 904. It is understood that the bus system 904 is used to realize the connection and communication between these components. In addition to the data bus, the bus system 904 also includes a power bus, a control bus, and a status signal bus. However, for the sake of clarity, Figure 9 Various buses are labeled as bus system 904.

[0139] The memory 903 in the embodiment of the present application is used to store various types of data to support the operation of the network device 900. Examples of such data include: any computer program used to operate on the network device 900.

[0140] The methods disclosed in the above embodiments of the present application can be applied to the processor 902 or implemented by the processor 902. The processor 902 may be an integrated circuit chip with signal processing capabilities. During implementation, the steps of the above methods can be completed by hardware integrated logic circuits or software instructions in the processor 902. The above processor 902 may be a general-purpose processor, a digital signal processor (DSP), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The processor 902 can implement or execute the various methods, steps, and logic block diagrams disclosed in the embodiments of the present application. A general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the methods disclosed in the embodiments of the present application can be directly embodied as being executed by a hardware decoding processor, or can be executed by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium, which is located in the memory 903. The processor 902 reads the information in the memory 903 and completes the steps of the above methods in combination with its hardware.

[0141] In an exemplary embodiment, the network device 900 may be implemented by one or more application-specific integrated circuits (ASICs), DSPs, programmable logic devices (PLDs), complex programmable logic devices (CPLDs), field-programmable gate arrays (FPGAs), general-purpose processors, controllers, microcontrollers (MCUs), microprocessors, or other electronic components to perform the aforementioned method.

[0142] It can be understood that the memory 903 of the embodiment of the present application can be a volatile memory or a non-volatile memory, and can also include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a magnetic random access memory (FRAM), a flash memory, a magnetic surface memory, an optical disc, or a compact disc read-only memory (CD-ROM); the magnetic surface memory can be a magnetic disk memory or a tape memory. The volatile memory can be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), synchronous static random access memory (SSRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct rambus random access memory (DRRAM).The memories described in the embodiments of this application are intended to include, but are not limited to, these and any other suitable types of memories.

[0143] In an exemplary embodiment, the present application also provides a storage medium, namely, a computer storage medium, specifically, a computer-readable storage medium, such as a memory 903 storing a computer program. The computer program can be executed by the processor 902 of the network device 900 to complete the steps of the aforementioned network device-side method. The computer-readable storage medium can be a memory such as FRAM, ROM, PROM, EPROM, EEPROM, Flash Memory, magnetic surface storage, optical disk, or CD-ROM.

[0144] It should be noted that: "first", "second", etc. are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.

[0145] In addition, the technical solutions described in the embodiments of the present application can be arbitrarily combined without conflict.

[0146] The above description is merely a preferred embodiment of the present application and is not intended to limit the scope of protection of the present application.

Claims

1. A method for selecting a session anchor point, characterized in that: Applicable to network equipment, including: A first terminal moves to an edge service side; the first terminal accesses a network through a first session anchor point; the terminal accessing the first session anchor point uses a first Internet Protocol IP domain; the first session anchor point is a primary session anchor point; a session established by a terminal using the first IP domain through the first session anchor point belongs to a first session group; sessions established by terminals using the same IP domain through different primary session anchor points belong to different session groups; A second session anchor is selected for the first terminal, where the second session anchor is a local offload session anchor and is bound only to the first session group.

2. The method according to claim 1, characterized in that The terminal accessing the third session anchor point uses the second IP domain; the first IP domain is the same as or different from the second IP domain.

3. The method according to claim 1, characterized in that The selecting a second session anchor point for the first terminal includes: A session anchor point is selected from at least one session anchor point bound to the first session group as a second session anchor point selected for the first terminal.

4. The method according to claim 1, wherein The selecting a second session anchor point for the first terminal includes: selecting a session anchor from at least one session anchor that is not bound to at least one session group; using the selected session anchor point as a second session anchor point selected for the first terminal; Establish a binding relationship between the second session anchor point and the first session group.

5. The method according to claim 1, characterized in that The selecting a second session anchor point for the first terminal includes: receiving a first message sent by a fourth session anchor point; the first message indicating that establishment of a session between the fourth session anchor point and the first terminal has failed; and the session of the fourth session anchor point includes a session of a second terminal having the same IP domain as the first terminal; reselecting the second session anchor point for the first terminal; Establish a binding relationship between the second session anchor point and the first session group.

6. The method according to claim 1, characterized in that The method further comprises: When there is no locally split session for the second session anchor point, the second session anchor point is deleted, and a binding relationship between the second session anchor point and the first session group is deleted.

7. The method according to claim 6, characterized in that The locally split session without the second session anchor point includes: When the local branching session anchor of the first session anchor is updated to the fifth session anchor, there is no locally branched session of the second session anchor.

8. The method according to claim 6, characterized in that The locally split session without the second session anchor point includes: When the first session anchor point no longer requires local traffic diversion, there is no session for local traffic diversion by the second session anchor point.

9. The method according to any one of claims 1 to 8, characterized in that The method further comprises: After selecting the second session anchor point for the first terminal, the downlink tunnel endpoint information of the first session anchor point and the uplink tunnel endpoint information of the new radio interface NR are updated.

10. A session anchor point selection device, characterized in that: include: An access processing unit, configured to enable a first terminal to access a network through a first session anchor point by moving the first terminal to an edge service side; The terminal accessing the first session anchor point uses the first IP domain; the first session anchor point is the primary session anchor point; the session established by the terminal using the first IP domain through the first session anchor point belongs to the first session group; Sessions established by terminals using the same IP domain through different primary session anchors belong to different session groups; The selecting unit is configured to select a second session anchor point for the first terminal, where the second session anchor point is a local offload session anchor point and is bound only to the first session group.

11. A network device, characterized in that: include: Processor and communication interface; wherein, The processor is configured to move a first terminal to an edge service side, allowing the first terminal to access a network through a first session anchor point; the terminal accessing the first session anchor point uses a first IP domain; the first session anchor point is a primary session anchor point; and a session established by the terminal using the first IP domain through the first session anchor point belongs to a first session group; Sessions established by terminals using the same IP domain through different primary session anchors belong to different session groups; and a second session anchor is selected for the first terminal, where the second session anchor is a local offload session anchor and has a binding relationship only with the first session group.

12. A network device, characterized in that: include: a processor and a memory for storing a computer program capable of being executed on the processor, Wherein, when the processor is used to run the computer program, it executes the steps of the method according to any one of claims 1 to 9.

13. A storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 9 are implemented.

Images