Method and apparatus for communicating

Abstract

The application provides a method and device for communication, which can include: a first session management network element determining a splitting point in a visited network according to first information, the first information being used for indicating that splitting in the visited network is allowed, the first session management network element being deployed for a network element in the visited network; and the first session management network element sending a splitting rule to the splitting point, the splitting rule being used for splitting a message to the visited network. Through the application, when a terminal device accesses a visited network in an HR roaming mode, the terminal device can access services in the visited network through a splitting point determined by a first session management network element, so that local splitting in the visited network is realized.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of communication, and more particularly, to a method and apparatus for communication. BACKGROUND

[0002] In edge computing (EC) deployment scenarios, some services can be provided by multiple edge application servers (EASs) deployed at the edge of the network. The multiple EASs can provide the same services and content, and most of them have different internet protocol (IP) addresses. When a user equipment (UE) requests to access the services, the EC scenario requires it to access the available EASs close to the UE. Therefore, the IP address of a suitable EAS is important.

[0003] In some cases, a UE can leave the coverage of a home public land mobile network (PLMN) (home PLMN, HPLMN), access a visited PLMN (VPLMN) in a home routed (HR) manner, and be served by the VPLMN. SUMMARY

[0004] The present application provides a method and apparatus for communication to determine a split point by a session management network element of a VPLMN, and send a split rule to the split point, so that a roaming UE can access services in the VPLMN through the split point.

[0005] In a first aspect, a method for communication is provided, which can be executed by a core network network element, or by a component (such as a chip or circuit) of the core network network element, without limitation. For ease of description, the following is described by way of example of execution by a first session management network element.

[0006] The method can include: determining, by a first session management network element, a split point in a visited network according to first information, the first information indicating that splitting is allowed in the visited network, and the first session management network element being a network element deployed in the visited network; and sending, by the first session management network element, a split rule to the split point, the split rule being used to split a packet to the visited network.

[0007] Based on the above scheme, the first session management network element deployed in the visited network can determine the offloading point according to the first information, and send the offloading rule to the offloading point. In this way, when the terminal device accesses the visited network in the HR roaming mode, the terminal device can access the services in the visited network through the offloading point determined by the first session management network element and the offloading rule sent to the offloading point, so as to realize local offloading in the visited network. In addition, the message accessing the EAS can be offloaded to the visited network through the offloading point, so that the terminal device can also access the edge services of the visited network after accessing the visited network in the HR roaming mode.

[0008] With reference to the first aspect, in some implementations of the first aspect, the method further includes: determining, by the first session management network element, the offloading rule according to the first service, the first service being a service allowed to be offloaded in the visited network.

[0009] Based on the above technical scheme, the first session management network element can determine the offloading rule according to the full domain name corresponding to the service allowed to be offloaded in the visited network, that is, the offloading rule is used to offload the service allowed to be offloaded in the visited network to the visited network. In this way, based on the offloading rule, when the full domain name of a certain service matches the target full domain name, the service is locally offloaded in the visited network.

[0010] With reference to the first aspect, in some implementations of the first aspect, the first information includes an identifier of the first service, and the first information indicates that the first service is allowed to be offloaded in the visited network.

[0011] For example, the identifier of the first service may, for example, be a full domain name (or a full domain name range), an application identifier, an IP address of an application server, or a port number.

[0012] Based on the above technical scheme, the first information indicates that the first service is allowed to be offloaded in the visited network, and accordingly, the offloading rule is used to offload the service allowed to be offloaded in the visited network to the visited network.

[0013] With reference to the first aspect, in some implementations of the first aspect, the method further includes: determining, by the first session management network element, the offloading rule according to the configuration information and / or the first information.

[0014] Based on the above technical scheme, the first session management network element determines the offloading rule according to the configuration information and / or the first information. In this way, the determined offloading rule can match the configuration information and / or the first information, and the terminal device can normally access the edge services in the visited network.

[0015] In a possible implementation of the first aspect, the method further includes: receiving, by the first session management network element, the first information from a second session management network element, the second session management network element being a network element deployed in a home network; or, the first session management network element locally configuring the first information.

[0016] According to the above technical solution, the first session management network element can locally configure the first information, or can receive the first information from another network element (such as the second session management network element).

[0017] In a second aspect, a method for communication is provided, which can be executed by a core network element, or can be executed by a component (such as a chip or a circuit) of the core network element, and the execution is not limited. For ease of description, the method executed by the first session management network element is described below.

[0018] The method can include: determining, by the first session management network element, a split point in a visited network, the first session management network element being a network element deployed in the visited network; sending, by the first session management network element, a split rule to the split point, the split rule being used to split a packet to the visited network; and receiving, by the first session management network element, first information, the first information indicating whether to allow splitting in the visited network.

[0019] According to the above solution, the first session management network element deployed in the visited network can determine the split point and send the split rule to the split point. In this way, when a terminal device accesses the visited network in an HR roaming manner, the terminal device can access services in the visited network through the split point determined by the first session management network element, so as to realize local splitting in the visited network. In addition, the packet accessing the EAS can be split to the visited network through the split point, so that the terminal device can also access edge services in the visited network when the terminal device accesses the visited network in the HR roaming manner. In addition, the first session management network element can receive the first information, and then can process the split point or the split rule according to the first information. That is, the first session management network element can first determine the split point in the visited network, and then can process the split point or the split rule according to the first information, so as to meet the requirements of the first information.

[0020] In a possible implementation of the second aspect, the method further includes: deleting or updating, by the first session management network element, the split rule according to the first information.

[0021] In a possible implementation of the second aspect, the first session management network element deletes or updates the split rule according to the first information, including: if the first information indicates that splitting in the visited network is not allowed, the first session management network element deletes the split rule.

[0022] Based on the above technical solution, if the first information indicates that the first service is not allowed to be split in the visited network, the first session management network element can delete the split rule, so that the split rule meets the requirements of the first information.

[0023] In combination with the second aspect, in some implementations of the second aspect, the first session management network element deletes or updates the split rule according to the first information, including: if the first information indicates that the first service is allowed to be split in the visited network, the first session management network element updates the split rule according to the first service.

[0024] Based on the above technical solution, if the first information indicates that the first service is allowed to be split in the visited network, the first session management network element updates the split rule according to the first service, or can be understood as that the first session management network element re-determines the split rule according to the first service, so that the determined split rule meets the requirements of the first information.

[0025] In combination with the second aspect, in some implementations of the second aspect, the method further includes: the first session management network element deletes or updates the split point according to the first information.

[0026] In combination with the second aspect, in some implementations of the second aspect, the first session management network element deletes or updates the split point according to the first information, including: if the first information indicates that the first service is not allowed to be split in the visited network, the first session management network element deletes the split point.

[0027] Based on the above technical solution, if the first information indicates that the first service is not allowed to be split in the visited network, the first session management network element can delete the split point, so that the split point meets the requirements of the first information.

[0028] In combination with the second aspect, in some implementations of the second aspect, the first session management network element deletes or updates the split point according to the first information, including: if the first information indicates that the first service is allowed to be split in the visited network, the first session management network element updates the split point according to the first service.

[0029] Based on the above technical solution, if the first information indicates that the first service is allowed to be split in the visited network, the first session management network element updates the split point according to the first service, or can be understood as that the first session management network element re-selects the split point according to the first service, so that the re-selected split point is more suitable for the message corresponding to the first service.

[0030] In combination with the second aspect, in some implementations of the second aspect, after the first session management network element deletes or updates the split point, the method further includes: the first session management network element sends updated tunnel information to the second session management network element.

[0031] With reference to the second aspect, in some implementations of the second aspect, the receiving the first information comprises: receiving, by the first session management network element, the first information from a second session management network element, the second session management network element being a network element deployed in a home network.

[0032] With reference to the first aspect or the second aspect, in some implementations, the offloading rule comprises address information of the edge application server, and the offloading rule is used to offload the packet within the edge application server to the visited network.

[0033] With reference to the first aspect or the second aspect, in some implementations, the offloading point is an uplink classifier or a branching point.

[0034] A third aspect provides a method of communication, which can be executed by a core network element or a component (such as a chip or a circuit) of the core network element, and is not limited in this regard. For ease of description, the method is described below as being executed by a second session management network element.

[0035] The method can comprise: obtaining, by the second session management network element, first information indicating whether offloading is allowed in a visited network; and sending, by the second session management network element, the first information to a first session management network element, the first session management network element being a network element deployed in the visited network, and the second session management network element being a network element deployed in a home network.

[0036] Based on the above scheme, the second session management network element deployed in the home network sends first information to the first session management network element deployed in the visited network, the first information indicating that offloading is allowed in the visited network. In this way, the first session management network element deployed in the visited network can learn that offloading is allowed in the visited network, and can then perform some operations, such as determining an offloading point, to access services in the visited network.

[0037] With reference to the third aspect, in some implementations of the third aspect, the method further comprises: sending, by the second session management network element, an identifier of a first service to the first session management network element, the first service being a service for which offloading is allowed in the visited network.

[0038] With reference to the third aspect, in some implementations of the third aspect, the first information comprises an identifier of a first service, and the first information indicates that offloading is allowed for the first service in the visited network.

[0039] With reference to the third aspect, in some implementations of the third aspect, the obtaining the first information comprises: receiving, by the second session management network element, the first information from a policy control network element, the policy control network element being a network element deployed in the home network; or locally configuring, by the second session management network element, the first information.

[0040] In a fourth aspect, a method of communication is provided. The method can be performed by a core network network element, or by a component (e.g., a chip or circuit) of a core network network element, without limitation. For ease of description, the method is described below as being performed by a policy control network element.

[0041] The method can include obtaining, by the policy control network element, first information indicating whether offloading is allowed in a visited network; and sending, by the policy control network element, the first information to a second session management network element. The second session management network element and the policy control network element can be network elements deployed in a home network.

[0042] Based on the above solution, the policy control network element deployed in the home network sends the first information to the second session management network element deployed in the home network. The first information indicates whether offloading is allowed in the visited network. In this way, the second session management network element deployed in the home network can learn whether offloading is allowed in the visited network, and can then perform some operations, such as sending the first information to the first session management network element.

[0043] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the method further includes sending, by the policy control network element, an identifier of a first service to the second session management network element. The first service is a service for which offloading is allowed in the visited network.

[0044] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the first information includes an identifier of a first service, and the first information indicates that offloading is allowed for the first service in the visited network.

[0045] In a fifth aspect, an apparatus for communication is provided. The apparatus can be configured to perform any of the methods in the first aspect through the fourth aspect. Specifically, the apparatus can include means and / or modules for performing the methods in the first aspect through the fourth aspect, such as a processing unit and / or a communication unit.

[0046] In one implementation, the apparatus is a core network network element. When the apparatus is a core network network element, the communication unit can be a transceiver, or an input / output interface; and the processing unit can be at least one processor. Optionally, the transceiver can be a transceiver circuit. Optionally, the input / output interface can be an input / output circuit.

[0047] In another implementation, the apparatus is a chip, chip system, or circuit for a core network network element. When the apparatus is a chip, chip system, or circuit for a core network network element, the communication unit can be an input / output interface, interface circuit, output circuit, input circuit, pin, or related circuitry on the chip, chip system, or circuit; and the processing unit can be at least one processor, processing circuit, or logic circuit.

[0048] In a sixth aspect, a device for communication is provided, the device comprising: at least one processor configured to execute computer programs or instructions stored in a memory to perform the method in any possible implementation of the first aspect to the fourth aspect. Optionally, the device further comprises the memory configured to store the computer programs or instructions. Optionally, the device further comprises a communication interface through which the processor reads the computer programs or instructions stored in the memory.

[0049] In an implementation form, the device is a core network element.

[0050] In another implementation form, the device is a chip, chip system or circuit for a core network element.

[0051] In a seventh aspect, the present application provides a processor configured to perform the method provided in any of the aspects.

[0052] For the sending and obtaining / receiving operations involved in the processor, if no special description is made, or if it is not contrary to the actual role or inherent logic in the related description, it can be understood as the processor output and receive, input and other operations, and can also be understood as the sending and receiving operations performed by the radio frequency circuit and the antenna, which are not limited in the present application.

[0053] In an eighth aspect, a computer readable storage medium is provided, the computer readable medium storing program codes for execution by an apparatus, the program codes comprising instructions for performing the method in any possible implementation of the first aspect to the fourth aspect.

[0054] In a ninth aspect, a computer program product containing instructions which, when the computer program product is executed on a computer, cause the computer to perform the method in any possible implementation of the first aspect to the fourth aspect.

[0055] In a tenth aspect, a communication system is provided, comprising one or more of the first session management network element, the second session management network element, and the policy control network element. BRIEF DESCRIPTION OF DRAWINGS

[0056] Figure 1 A schematic diagram of a network architecture is shown.

[0057] Figure 2 A schematic diagram of another network architecture is shown.

[0058] Figure 3 is a schematic diagram of a communication method 300 provided by an embodiment of the present application.

[0059] Figure 4is a schematic diagram of another method 400 of communication provided by embodiments of the application.

[0060] Figure 5 is a schematic flowchart of a method 500 of communication provided by embodiments of the application.

[0061] Figure 6 is a schematic flowchart of another method 600 of communication provided by embodiments of the application.

[0062] Figure 7 is a schematic flowchart of another method 700 of communication provided by embodiments of the application.

[0063] Figure 8 is a schematic flowchart of another method 800 of communication provided by embodiments of the application.

[0064] Figure 9 is a schematic block diagram of an apparatus 900 of communication provided by embodiments of the application.

[0065] Figure 10 is a schematic block diagram of another apparatus 1000 of communication provided by embodiments of the application. DETAILED DESCRIPTION

[0066] The technical solutions in the present application will be described below with reference to the drawings.

[0067] The technical solutions provided by the present application can be applied to various communication systems, for example: a 5th generation (5G) or new radio (NR) system, a long term evolution (LTE) system, an LTE frequency division duplex (FDD) system, an LTE time division duplex (TDD) system, etc. The technical solutions provided by the present application can also be applied to future communication systems, such as a 6th generation mobile communication system. The technical solutions provided by the present application can also be applied to device to device (D2D) communication, vehicle-to-everything (V2X) communication, machine to machine (M2M) communication, machine type communication (MTC), and internet of things (IoT) communication systems or other communication systems.

[0068] First, the technical solutions provided by the present application will be described in combination with Figure 1 and Figure 2A network architecture applicable to the present application is briefly introduced as follows.

[0069] As an example, Figure 1 A schematic diagram of a network architecture is shown.

[0070] As Figure 1 The network architecture is taken as an example of home routed (HR) roaming.

[0071] A cellular mobile communication network of a certain standard of a certain operator can be referred to as a public land mobile network (PLMN). A PLMN to which a user equipment (UE) is subscribed can be referred to as a home public land mobile network (PLMN) (HPLMN), representing the home operator of the subscribed user. When the UE leaves the coverage of the HPLMN due to movement or other reasons, if there is a PLMN that meets the following conditions: 1) can cover the current location of the UE, 2) its operator has signed a roaming agreement with the operator of the HPLMN of the UE (the roaming agreement means a certain agreement between operators, the content of which can include but is not limited to, for example, the services provided for the subscribed users of the other operator network and the charging mode, etc., which are not limited), then the UE can access the PLMN, and the PLMN can be referred to as a visited PLMN (VPLMN). The behavior of the UE accessing the VPLMN can be referred to as roaming. The roaming scenario can be divided into local breakout (LBO) roaming and home routed (HR) roaming. In the HR roaming scenario, the session management function (SMF) in the VPLMN can forward session management (SM) related information to the SMF in the HPLMN. In the HR roaming scenario, the SMF in the HPLMN can receive the subscription permanent identifier (SUPI) of the terminal device from the SMF in the VPLMN. For the HR roaming scenario, reference can be made to the provisions in the protocol, which are not limited.

[0072] As Figure 1As shown, the network architecture can include, but is not limited to: network slice specific authentication and authorization function (NSSAAF), network slice selection function (NSSF), authentication server function (AUSF), unified data management (UDM), policy control function (PCF), application function (AF), access and mobility management function (AMF), session management function (SMF), user equipment (UE), radio access network device, user plane function (UPF), data network (DN), etc.

[0073] The following briefly introduces each network element shown in the network architecture. Figure 1

[0074] 1. UE: can be referred to as a terminal device, an access terminal, a user unit, a user station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent, or a user device.

[0075] ​The terminal device can be a device providing voice / data to a user, for example, a handheld device with wireless connection function, a vehicle-mounted device, etc. At present, some examples of terminals are: mobile phone, tablet computer, notebook computer, palm computer, mobile internet device (MID), wearable device, virtual reality (VR) device, augmented reality (AR) device, wireless terminal in industrial control, wireless terminal in self driving, wireless terminal in remote medical surgery, wireless terminal in smart grid, wireless terminal in transportation safety, wireless terminal in smart city, wireless terminal in smart home, cellular phone, cordless phone, session initiation protocol (SIP) phone, wireless local loop (WLL) station, personal digital assistant (PDA), handheld device with wireless communication function, computing device or other processing device connected to a wireless modem, wearable device, terminal device in a 5G network, or terminal device in a future evolved public land mobile network (PLMN), etc. The embodiments of the present application are not limited thereto.

[0076] By way of example and not limitation, in the embodiments of the present application, the terminal device can also be a wearable device. The wearable device can also be referred to as a wearable smart device, which is a general term for devices that are designed and developed by applying wearable technology to daily wear, such as glasses, gloves, watches, clothing, and shoes. The wearable device is a portable device that is directly worn on the body or integrated into the user's clothes or accessories. The wearable device is not only a hardware device, but also a device that realizes powerful functions through software support and data interaction and cloud interaction. The general wearable smart device includes a device with full functions and large size, which can realize complete or partial functions without relying on a smart phone, such as a smart watch or smart glasses, and a device that focuses on a certain application function and needs to cooperate with other devices such as a smart phone, such as various smart wristbands and smart jewelry for monitoring vital signs.

[0077] In addition, in the embodiments of the present application, the terminal device can also be a terminal device in an IoT system. IoT is an important part of future information technology development, and its main technical feature is to connect objects through communication technology and network, so as to realize the intelligent network of man-machine interconnection and object-object interconnection.

[0078] It should be noted that the terminal device and the access network device can communicate with each other by using a certain air interface technology (such as NR or LTE technology, etc.). The terminal device and the terminal device can also communicate with each other by using a certain air interface technology (such as NR or LTE technology, etc.).

[0079] In the embodiments of the present application, the device for implementing the function of the terminal device can be a terminal device, or a device capable of supporting the terminal device to implement the function, such as a chip system or a chip, which can be installed in the terminal device. In the embodiments of the present application, the chip system can be composed of a chip, or can include a chip and other discrete devices.

[0080] 2, (wireless) access network ((radio) access network, (R) AN) device: can provide access to a communication network for authorized users in a specific area, which can specifically include a wireless network device in a 3rd generation partnership project (3rd generation partnership project, 3GPP) network, and can also include an access point in a non-3GPP (non-3GPP) network. The following is for convenience. AN device is used to represent.

[0081] AN device can be of different radio access technologies. There are two types of current radio access technologies: 3GPP radio access technology (e.g., radio access technology adopted in third generation (3G), fourth generation (4G) or 5G system) and non-3GPP radio access technology. 3GPP radio access technology refers to access technology conforming to 3GPP standard specification, for example, access network device in 5G system is called next generation Node Base station (gNB) or RAN device. Non-3GPP radio access technology can include air interface technology represented by access point (AP) in wireless fidelity (WiFi), worldwide interoperability for microwave access (WiMAX), code division multiple access (CDMA) and the like. AN device can allow terminal device and 3GPP core network to be interconnected and communicated by using non-3GPP technology.

[0082] AN device can be responsible for functions such as radio resource management on the air interface side, quality of service (QoS) management, data compression and encryption. AN device provides access service for terminal device, and then completes the forwarding of control signals and user data between terminal device and core network.

[0083] The AN device may include, but is not limited to, a macro base station, a micro base station (also referred to as a small station), a radio network controller (RNC), a Node B (NB), a base station controller (BSC), a base transceiver station (BTS), a home base station (for example, a home evolved NodeB or home Node B, HNB), a baseband unit (BBU), an AP in a WiFi system, a wireless relay node, a wireless backhaul node, a transmission point (TP) or a transmission and reception point (TRP), and the like, and can also be a gNB or a transmission point (TRP or TP) in a 5G (for example, NR) system, one or a group (including multiple antenna panels) of antenna panels of a base station in a 5G system, or a network node constituting a gNB or a transmission point, such as a distributed unit (DU), or a base station in a next-generation communication 6G system, and the like. The embodiments of the present application do not limit the specific technology and specific device form adopted by the AN device.

[0084] 3. AMF: mainly used for access control, mobility management, attachment and detachment, and the like.

[0085] 4. SMF: mainly used for user plane network element selection, user plane network element redirection, internet protocol (IP) address allocation of a terminal device, and session management in a mobile network, such as establishment, modification and release of a session and quality of service (QoS) control.

[0086] In the present application, the SMF in the HPLMN is recorded as a home SMF (H-SMF), and the SMF in the VPLMN is recorded as a visited SMF (V-SMF) for distinction.

[0087] 5. UPF: mainly used for receiving and forwarding of user plane data. For example, the UPF can receive user plane data from a DN and send the user plane data to a terminal device through an AN device. The UPF can also receive user plane data from a terminal device through an AN device and forward the user plane data to a DN. The UPF directly connected with the DN through an N6 interface in a session can be referred to as a protocol data unit (PDU) session anchor (PSA).

[0088] In this application, the UPF in the HPLMN is referred to as home UPF (H-UPF) for distinction, and the UPF in the VPLMN is referred to as visited UPF (V-UPF) for distinction. In addition, the PSA in the HPLMN is referred to as home PSA (H-PSA) for distinction, and the PSA in the VPLMN is referred to as visited PSA (V-PSA) (or referred to as local PSA (L-PSA)).

[0089] 6. PCF: a unified policy framework mainly used for guiding network behavior, providing policy rule information, etc. for control plane network elements (such as AMF, SMF, etc.).

[0090] 7. AF: mainly used for providing services to the 3GPP network, such as interacting with the PCF for policy control, etc.

[0091] 8. Network slice selection function (NSSF): mainly used for network slice selection.

[0092] 9. UDM: mainly used for management of subscription data of the UE, including storage and management of UE identity, access authorization of the UE, etc.

[0093] 10. DN: mainly used for providing data services for the UE by the operator network. For example, Internet, third-party service network, IP multi-media service (IMS) network, etc.

[0094] 11. AUSF: mainly used for user authentication, etc.

[0095] As an example, Figure 2 a schematic diagram of another network architecture is shown.

[0096] As Figure 2 shown, this network architecture can be understood as Figure 1Enhancements of the illustrated HR roaming architecture. The network architecture can include, but is not limited to: SMF (such as V-SMF and H-SMF), UE, UPF (such as V-UPF and H-UPF), PSA (such as L-PSA), domain name system (DNS), PCF (such as H-PCF), edge application server discovery function (EASDF). In this architecture, the domain name system (DNS) message can be terminated at the EASDF of the HPLMN. Among them, the DNS message can be terminated at the EASDF of the HPLMN, which can mean that the DNS message is processed by the EASDF of the HPLMN, or can mean that the destination address of the DNS message is the EASDF of the HPLMN, or can mean that the EASDF of the HPLMN receives the DNS message. Among them, the edge application server discovery function, for example, can also be referred to as edge application (service) discovery function, application instance discovery function, edge application instance discovery function, MEC application (server) discovery function, etc., without limitation.

[0097] The EASDF is mainly used to assist edge application server (EAS) discovery, and its main functions include: processing DNS messages according to the indication of the SMF. Among them, processing the DNS message can include, but is not limited to: reporting the DNS message to the SMF, adding an EDNS client subnet option (ECS option) in the DNS query (DNS query), forwarding the DNS query to the DNS server, forwarding the DNS response (DNS response) to the UE, etc. Among them, EDNS is an extended mechanism for DNS (EDNS). In this application, in order to distinguish, the DNS in the HPLMN is recorded as C-DNS, and the UPF in the VPLMN is recorded as L-DNS.

[0098] The introduction of other network elements can refer to the description in Figure 1 , which will not be repeated here.

[0099] In the network architecture illustrated in Figure 1 or Figure 2 , the network elements can interface with each other for communication, for example, the UE connects with the AN device through the radio resource control (RRC) protocol, and the UE and the AN device communicate with each other through the Uu interface. Or it can also refer to the interface shown in Figure 1 , which will not be repeated here.

[0100] It should be understood that the network architecture shown above is only an example, and the network architecture to which the embodiments of the present application are applicable is not limited thereto, and any network architecture capable of realizing the functions of the various network elements described above is applicable to the embodiments of the present application. In addition, the network architecture shown above can also include other more network elements, such as a network storage function network element (network function (NF) repository function, NFR), which is not limited. In the present application, in order to distinguish, the NRF in the HPLMN is referred to as a home NRF (H-NRF), and the NRF in the VPLMN is referred to as a visited NRF (V-NRF).

[0101] It should also be understood that, Figure 1 or Figure 2 The AMF, SMF, UPF, PCF, UDM, NSSF, AUSF, etc. functions or network elements shown in the above can be understood as network elements for realizing different functions, for example, they can be combined into network slices as needed. These network elements can be independent devices, or can be integrated into the same device to realize different functions, or can be network elements in a hardware device, or can be software functions running on a dedicated hardware, or virtualized functions instantiated on a platform (e.g., a cloud platform), and the present application does not limit the specific form of the above network elements.

[0102] It should also be understood that the above naming is only defined for the purpose of distinguishing different functions and should not constitute any limitation on the present application. The present application does not exclude the possibility of using other names in 6G networks and other future networks. For example, in 6G networks, some or all of the above network elements can use the terms in 5G, or other names, etc.

[0103] In an edge computing (EC) deployment scenario, some services can be provided by multiple EASs deployed at the edge of the network. The multiple EASs can provide the same services and content, and most of them have different IP addresses. In the EC scenario, when a UE accesses the service, it can request to access the available EAS closest to the UE. Therefore, it is important to obtain the IP address of a suitable EAS.

[0104] As described above, the UE can access the VPLMN through HR roaming, and the VPLMN provides services for the UE.

[0105] Considering that some services may wish to use EC access when the UE accesses the VPLMN, currently, for the UE in HR roaming, the PDU session establishment stage only provides the UE with the relevant information of the HPLMN (for example, the address information of the edge application server discovery network element of the HPLMN), and the DNS query message sent by the UE cannot reach the edge service discovery network element in the VPLMN, resulting in that the edge application server located in the VPLMN cannot be discovered for the UE. Therefore, the existing edge service discovery mechanism cannot be used in the HR roaming scenario.

[0106] The present application proposes a solution, which determines a split point by a session management network element in the VPLMN, and sends a split rule to the split point, so that the roaming UE can access the service in the VPLMN through the split point.

[0107] For example, the session management network element in the VPLMN can determine the split point in the VPLMN according to information #A, which indicates that the split in the visited network is allowed, and send a split rule to the split point. By inserting the split point in the VPLMN and providing the split rule, the message sent by the terminal device (or the message corresponding to the access to the edge service) can be split to the VPLMN through the split point and the split rule in the VPLMN, and thus the EC access of the local service of the VPLMN in the HR roaming scenario can be realized. In addition, the session management network element in the VPLMN determines the split point in the VPLMN according to the information #A, and thus the requirement of the information #A can be met.

[0108] For another example, the session management network element in the VPLMN determines the split point in the VPLMN, and sends a split rule to the split point. By inserting the split point in the VPLMN and providing the split rule, the message sent by the terminal device (or the message corresponding to the access to the edge service) can be split to the VPLMN through the split point and the split rule in the VPLMN, and thus the EC access of the local service of the VPLMN in the HR roaming scenario can be realized. In addition, the session management network element in the VPLMN receives the information #A, which indicates whether the split in the visited network is allowed, and can determine how to process the split point or the split rule according to the information #A. That is, the session management network element in the VPLMN can first determine the split point in the visited network, and after determining the split point, the information #A can be received, and then the split point or the split rule can be processed according to the information #A, so as to meet the requirement of the information #A.

[0109] Therefore, the present application can be used to solve the edge service discovery in the roaming scenario (such as the HR roaming scenario).

[0110] It can be understood that the term "and / or" described herein is only a description of the association relationship of the associated objects, which means that there can be three relationships, for example, A and / or B can represent three cases of A alone, A and B together, and B alone. In addition, the character " / " herein generally represents an "or" relationship between the front and rear associated objects.

[0111] The communication method provided by the embodiments of the present application will be described in detail below with reference to the drawings. The embodiments provided by the present application can be applied to the network architecture shown in the above Figure 1 or Figure 2 without limitation.

[0112] Figure 3 is a schematic diagram of a communication method 300 provided by an embodiment of the present application. The method 300 can include the following steps.

[0113] 310, the first session management network element determines a splitting point in the visited network according to information #A, the information #A indicating that splitting in the visited network is allowed, and the first session management network element being a network element deployed in the visited network.

[0114] The visited network is a network accessed by the terminal device after leaving the home network, such as VPLMN. The following will be mainly described by taking VPLMN as an example.

[0115] The first session management network element is a network element deployed in the VPLMN. For example, the first session management network element is V-SMF.

[0116] The information #A (i.e., the first information) can also be described as indicating (or representing, or indicating) that splitting is allowed, or can be described as the information #A indicating that VPLMN local splitting is allowed. The following is uniformly described by taking the example of allowing splitting in the VPLMN.

[0117] An example, allowing splitting in the VPLMN, can mean that the HPLMN allows VPLMN local splitting. Accordingly, the information #A indicating that splitting in the VPLMN is allowed can be replaced by: the information #A indicating that the HPLMN allows VPLMN local splitting. Another example, allowing splitting in the VPLMN, can mean that the VPLMN is allowed to determine (or select, or insert) a splitting point. Accordingly, the information #A indicating that splitting in the VPLMN is allowed can be replaced by: the information #A indicating that the VPLMN is allowed to determine (or select, or insert) a splitting point. Another example, allowing splitting in the VPLMN, can mean determining (or selecting, or inserting) a splitting point. Accordingly, the information #A indicating that splitting in the VPLMN is allowed can be replaced by: the information #A being used to indicate that a splitting point is allowed to be determined (or selected, or inserted).

[0118] It can be understood that the present application is mainly described by taking the example of allowing the VPLMN offloading, and does not limit that the VPLMN local offloading is allowed in all cases, in other words, in some cases, the VPLMN offloading can not be allowed (or supported), in which case, the local offloading can not be performed in the VPLMN.

[0119] The present application does not limit the specific name of the information #A. For example, the "information #A" in the present application can be replaced by "authorization policy", or can be replaced by "offloading policy", or can be replaced by "roaming policy", and the like.

[0120] The present application does not limit the form of the information #A. For example, the information #A can be a signal element, or can be a parameter, or can be a text content recorded in a protocol, and the like. For example, the information #A can be implemented by one or more bits. For example, it is assumed that whether the VPLMN offloading is allowed is indicated by 1 bit, if the bit is set to "0", it indicates that the information #A is used to indicate that the VPLMN offloading is allowed; if the bit is set to "1", it indicates that the information #A is used to indicate that the VPLMN offloading is not allowed.

[0121] The scheme of determining the offloading point in the visited network by the first session management network element according to the information #A will be described in detail later.

[0122] The offloading point can be used to offload the message to the VPLMN, such as offloading the message accessing the service deployed in the VPLMN to the VPLMN.

[0123] Optionally, the shunt point is an uplink classifier (UL CL) or a branching point (BP). When the terminal device needs to transmit service, multiple PDU sessions to the same DN or different DNs can be established by the SMF. The SMF can control the data routing of the PDU so that the PDU session can have multiple N6 interfaces at the same time, and the UPF connected to each N6 interface is called PSA, and each PSA provides a different path to the same DN. Therefore, in one possible manner, the V-SMF can determine the UL CL in the VPLMN, and for different types of PDU sessions, the SMF can insert an UL CL in the data transmission path of the PDU session. The UL CL function is provided by the UPF, which is used to forward data packets that meet the service filtering rules to the specified path. When an UL CL is inserted into a PDU session data channel, the PDU session can have multiple PDU session anchors, providing multiple different paths to access the same DN. That is, the function of the UL CL can be to transmit uplink data to different PSAs and combine downlink data to the UE. In another possible manner, the V-SMF can determine the branching point in the VPLMN, and specifically, the data corresponding to each PSA can be converged in a common UPF, and the common UPF has the function of the branching point. The branching point forwards the uplink data to different PSAs upward and combines the downlink data from the PSA downward.

[0124] It can be understood that the above is only an exemplary description, and is not limited thereto. As long as the message can be shunted to the VPLMN through the shunt point, the scheme is applicable to the embodiments of the present application.

[0125] 320, the first session management network element sends a shunt rule to the shunt point, and the shunt rule is used to shunt the message to the visited network.

[0126] The message may, for example, be a message accessing an EAS IP.

[0127] The shunt rule is used to shunt the service flow to the visited network. As an example, the service flow can be represented by one or more of the following: destination IP address or prefix, source IP address or prefix, destination port number, source port number.

[0128] As an example, the shunt rule can include two parts of information, one part of information is used to detect (or match, or identify) the service flow, and the other part of information is used to forward the service flow (such as shunting the matched service flow to the visited network, or in other words, forwarding to the local). For example, the shunt rule includes one or more IP addresses, and if the IP address in the service flow matches the IP address in the shunt rule, the service flow is shunted to the visited network.

[0129] It should be noted that the present application mainly takes the example of the offloading rule being sent by the first session management network element to the offloading point, and the present application is not limited thereto. For example, the offloading rule can also be locally configured by the offloading point.

[0130] Based on the above scheme, the first session management network element deployed in the visited network can determine the offloading point according to the information #A, and send the offloading rule to the offloading point. In this way, when the terminal device accesses the visited network in the HR roaming mode, the terminal device can access the services in the visited network through the offloading point determined by the first session management network element and the offloading rule sent to the offloading point, so as to realize the local offloading in the visited network. In addition, the message for accessing the EAS can also be offloaded to the visited network through the offloading point, so that the terminal device can also access the edge services of the visited network after accessing the visited network in the HR roaming mode.

[0131] Optionally, the first session management network element determines the offloading point in the visited network according to the information #A in step 310, which at least includes the following possible cases.

[0132] The first possible case is that the information #A is used to indicate that the offloading in the visited network is allowed.

[0133] In this case, the first session management network element learns from the information #A that the offloading in the visited network is allowed, and therefore the first session management network element determines the offloading point in the visited network. Alternatively, in this case, the message, such as the message for accessing the EAS IP, can be offloaded to the visited network through the offloading point.

[0134] The second possible case is that the information #A is used to indicate that the first service is allowed to be offloaded in the visited network.

[0135] It can be understood that the first service here represents the service allowed to be offloaded in the visited network, and the first service can include one or more types of services, without limitation.

[0136] In this case, the first session management network element learns from the information #A that the first service is allowed to be offloaded in the visited network, and therefore the first session management network element determines the offloading point in the visited network, through which the first service can be locally offloaded in the visited network.

[0137] Example 1: The information #A includes the identifier of the first service.

[0138] As an example, the identity of the first service, e.g., can be any of the following: a full qualified domain name (FQDN) (or a FQDN range), an application ID (AppID), an IP address, a port number. That is, the information #A can include one or more of the following: a FQDN (or a FQDN range), an AppID, an IP address, a port number.

[0139] Hereinafter, FQDN is taken as an example for illustration, it can be understood that the FQDN in the following examples can also be replaced by any of the following: an AppID, an IP address, a port number.

[0140] For example, the information #A includes one or more FQDNs, which represent FQDNs corresponding to services allowed to be offloaded in the visited network (i.e., FQDNs corresponding to the first service). In one possible implementation, the information #A includes two information elements, one of which is used to indicate that offloading is allowed in the visited network, and the other of which includes the one or more FQDNs, from which the first session management network element can learn that the services corresponding to the one or more FQDNs are allowed to be offloaded in the visited network. In another possible implementation, the information #A includes one or more FQDNs, and the first session management network element determines according to internal logic that the services corresponding to the one or more FQDNs are allowed to be offloaded in the visited network.

[0141] Example 2, the information #A includes an identity of a service other than the first service (e.g., denoted as a second service).

[0142] As an example, the second service, e.g., can be any of the following: a FQDN (or a FQDN range), an AppID, an IP address, a port number. That is, the information #A can include one or more of the following: a FQDN (or a FQDN range), an AppID, an IP address, a port number.

[0143] Hereinafter, FQDN is taken as an example for illustration, it can be understood that the FQDN in the following examples can also be replaced by any of the following: an AppID, an IP address, a port number.

[0144] For example, the information #A includes one or more FQDNs, which represent FQDNs corresponding to services not allowed to be offloaded in the visited network (e.g., FQDNs corresponding to the second service). In one possible implementation, two information elements are included in the information #A, one of which is used to indicate that offloading is not allowed in the visited network, and the other of which includes the one or more FQDNs. The first session management network element can learn from the information #A that services corresponding to the one or more FQDNs are not allowed to be offloaded in the visited network. In another possible implementation, the information #A includes one or more FQDNs. The first session management network element determines from internal logic that services corresponding to the one or more FQDNs are not allowed to be offloaded in the visited network. Furthermore, further, the first session management network element can learn from the information #A that services corresponding to other FQDNs (i.e., FQDNs other than the one or more FQDNs) are allowed to be offloaded in the visited network.

[0145] Example 3, the information #A includes the identities of the first service and the second service.

[0146] The following examples are mainly described by taking FQDNs as examples. It can be understood that the FQDNs in the following examples can also be replaced by any of the following: application identifier, IP address, port number.

[0147] For example, the information #A includes one or more FQDN #1, and one or more FQDN #2, the one or more FQDN #1 represents the FQDN corresponding to the traffic allowed to be offloaded in the visited network, and the one or more FQDN #2 represents the FQDN corresponding to the traffic not allowed to be offloaded in the visited network. In a possible implementation, three information elements are included in the information #A, one information element is used to indicate that the traffic corresponding to the FQDN #1 is allowed to be offloaded in the visited network, another information element includes the one or more FQDN #1, and the other information element includes the one or more FQDN #2, and the first session management network element can know, according to the information #A, that the traffic corresponding to the one or more FQDN #1 is allowed to be offloaded in the visited network, and the traffic corresponding to the one or more FQDN #2 is not allowed to be offloaded in the visited network. In another possible implementation, three information elements are included in the information #A, one information element is used to indicate that the traffic corresponding to the FQDN #2 is not allowed to be offloaded in the visited network, another information element includes the one or more FQDN #1, and the other information element includes the one or more FQDN #2, and the first session management network element can know, according to the information #A, that the traffic corresponding to the one or more FQDN #1 is allowed to be offloaded in the visited network, and the traffic corresponding to the one or more FQDN #2 is not allowed to be offloaded in the visited network. In another possible implementation, two information elements are included in the information #A, one information element includes the one or more FQDN #1, and the other information element includes the one or more FQDN #2, and the first session management network element determines, according to internal logic, that the traffic corresponding to the one or more FQDN #1 is allowed to be offloaded in the visited network, and the traffic corresponding to the one or more FQDN #2 is not allowed to be offloaded in the visited network.

[0148] The third possible case is that the information #A is used to indicate that offloading in the visited network is not allowed.

[0149] In this case, the first session management network element knows, according to the information #A, that offloading in the visited network is not allowed (or not supported), and then the first session management network element can not need to determine the offloading point in the visited network, that is, does not need to determine the offloading point for offloading locally in the visited network.

[0150] Optionally, the method 300 further includes that the first session management network element acquires the information #A.

[0151] The first session management network element can acquire the information #A at least by any of the following manners.

[0152] Manner 1: The first session management network element receives the information #A from the second session management network element.

[0153] For example, taking the first session management network element as a V-SMF and the second session management network element as an H-SMF as an example, the H-SMF sends the information #A to the V-SMF, and correspondingly, the V-SMF receives the information #A from the H-SMF.

[0154] Way 2, the first session management network element locally configures information #A.

[0155] For example, the information #A corresponding to the HPLMN is included in the locally configured roaming agreement, and the first session management network element directly obtains the information #A corresponding to the HPLMN according to the locally configured roaming agreement.

[0156] For another example, one or more information #A is included in the locally configured roaming agreement, and the first session management network element obtains the information #A according to the locally configured roaming agreement. The one or more information #A can be information #A corresponding to one or more PLMNs, and the first session management network element can first determine the HPLMN and then obtain the corresponding information #A according to the HPLMN. For example, the information #A can exist in the form of Table 1 in the first session management network element.

[0157] Table 1

[0158] PLMN identity (ID) Information #A PLMN #1 Information #A1 PLMN #2 Information #A2 PLMN #3 Information #A3

[0159] Taking Table 1 as an example, one possible case is that the PLMN ID can be the ID of the HPLMN, and the information #Ai (i = 1, 2, 3, …) is used to indicate whether the HPLMN allows VPLMN local splitting. For example, if the first session management network element determines that the HPLMN is PLMN #1, it can be known that the information #A corresponding to the HPLMN is information #A1. If information #A1 is used to indicate that PLMN #1 allows VPLMN local splitting, then local splitting can be performed in VPLMN.

[0160] The application does not limit the way in which the first session management network element determines the HPLMN. As an example, the first session management network element can identify the HPLMN according to the identifier of the network element deployed in the HPLMN (such as the identifier of the second session management network element or the identifier of other network elements, etc.). In one possible way, the first session management network element receives the identifier of the second session management network element (such as H-SMF ID, which is not limited by the application) from the AMF, and determines the identifier of the HPLMN, i.e., determines the HPLMN, according to the identifier of the second session management network element.

[0161] It should be understood that Table 1 is only an example and is not limited in this regard, and any variation of Table 1 is applicable to the application. For example, the PLMN ID in the above Table 1 can be replaced by SMF ID, such as one or more SMF IDs (i.e., the ID of one or more SMFs corresponding to the PLMN #1).

[0162] The above two manners are exemplary, and any manner that can enable the first session management network element to acquire the information #A is applicable to the embodiments of the present application.

[0163] Optionally, for the second core network element, the second session management network element can acquire the information #A at least by any of the following manners.

[0164] Manner 1: The second session management network element receives the information #A.

[0165] The policy control network element is a network element deployed in the home network. For example, the policy control network element is an H-PCF or an H-NRF.

[0166] For example, the second session management network element receives the information #A from the policy control network element, wherein the policy control network element is a network element deployed in the home network. Taking the second session management network element as an H-SMF and the policy control network element as an H-PCF as an example, the H-PCF sends the information #A to the H-SMF, and correspondingly, the H-SMF receives the information #A from the H-PCF. The condition for triggering the H-PCF to send the information #A to the H-SMF is not limited. For example, the triggering condition can be that the H-SMF sends the identifier of the VPLMN to the H-PCF.

[0167] For another example, the second session management network element receives the information #A from the network storage network element, wherein the network storage network element is a network element deployed in the home network. Taking the second session management network element as an H-SMF and the network storage network element as an H-NRF as an example, the H-NRF sends the information #A to the H-SMF, and correspondingly, the H-SMF receives the information #A from the H-NRF. The condition for triggering the H-NRF to send the information #A to the H-SMF is not limited. For example, the triggering condition can be that the H-SMF sends the identifier of the VPLMN to the H-NRF. The following examples are given. Figures 5 to 8

[0168] Manner 2: The second session management network element locally configures the information #A.

[0169] For example, the information #A corresponding to the VPLMN is included in the locally configured roaming agreement, and the second session management network element directly acquires the information #A corresponding to the VPLMN according to the locally configured roaming agreement.

[0170] ​For example, the one or more information #A can be information #A corresponding to one or more PLMNs, and the second session management network element can first determine the VPLMN and then obtain the corresponding information #A according to the VPLMN. It should be noted that the second session management network element can determine the information #A according to the message received from the first session management network element and the local configuration. The message can be an Nsmf_PDUSession_Create Request or Nsmf_PDUSession_Update Request message, and the present application does not limit it.

[0171] The information #A can exist in the form of Table 2 in the second session management network element.

[0172] Table 2

[0173] PLMN ID Information #A PLMN #1' Information #A1' PLMN #2' Information #A2' PLMN #3' Information #A3'

[0174] For example, the one or more information #A can be information #A corresponding to one or more PLMNs, and the second session management network element can first determine the VPLMN and then obtain the corresponding information #A according to the VPLMN. It should be noted that the second session management network element can determine the information #A according to the message received from the first session management network element and the local configuration. The message can be an Nsmf_PDUSession_Create Request or Nsmf_PDUSession_Update Request message, and the present application does not limit it.

[0175] The present application does not limit the way the second session management network element determines the VPLMN. As an example, the second session management network element can identify the VPLMN according to the identifier of the network element deployed in the VPLMN (such as the identifier of the first session management network element or the identifier of other network elements). In one possible way, the second session management network element receives the identifier of the first session management network element (such as the V-SMF ID, which is not limited by the present application), and determines the identifier of the VPLMN according to the identifier of the first session management network element, that is, determines the VPLMN. In another possible way, the second session management network element receives the identifier of the VPLMN from the first session management network element. In still another possible way, the second session management network element receives the message of the first session management network element and determines the identifier of the VPLMN according to the message. The message can be an Nsmf_PDUSession_Create Request or Nsmf_PDUSession_Update Request message, and the present application does not limit it.

[0176] It should be understood that Table 2 is only an example and is not limited thereto, and any variation of Table 2 is applicable to the present application. For example, the PLMN ID in Table 2 can be replaced by an SMF ID, e.g., PLMN#1' can be replaced by one or more SMF IDs (i.e., the ID of one or more SMFs corresponding to the PLMN#1').

[0177] The above two manners are examples and any manner that enables the second session management network element to obtain the information #A is applicable to the embodiments of the present application.

[0178] Optionally, the method 300 further comprises: determining, by the first session management network element, the offloading rule.

[0179] In a first possible implementation, the first session management network element determines the offloading rule according to the information #A.

[0180] The information #A can comprise an identifier of the first service, and the first session management network element determines the offloading rule according to the identifier of the first service in the information #A. The offloading rule can be used to offload the packets of the first service to the visited network.

[0181] As an example, the identifier of the first service can be one or more of the following: FQDN, IP address, application identifier, port number, etc. Hereinafter, FQDN is taken as an example for description, and it can be understood that the FQDN in the following examples can be replaced by any one of the following: application identifier, IP address, port number.

[0182] As an example, the information #A comprises one or more FQDNs, denoted as target FQDN#1.

[0183] Optionally, the first session management network element obtains the target FQDN#1. For example, the first session management network element obtains the information #A, and the information #A comprises the target FQDN#1. In a possible implementation, the information #A comprises two information elements, one of which is used to indicate whether offloading in the visited network is allowed, and the other of which comprises the target FQDN#1. The first session management network element can obtain whether the service corresponding to the target FQDN#1 is allowed to offload in the visited network according to the information #A. In another possible implementation, the information #A comprises the target FQDN#1, and the first session management network element determines whether the service corresponding to the target FQDN#1 is allowed to offload in the visited network according to internal logic.

[0184] The target FQDN#1 comprises: an FQDN corresponding to a service allowed to offload in the visited network, and / or an FQDN corresponding to a service not allowed to offload in the visited network. The target FQDN#1 can comprise one or more FQDNs.

[0185] Example 1, the target FQDN#1 includes a FQDN corresponding to traffic allowed to be offloaded in the visited network.

[0186] In this example 1, the information #A in step 310 can be used to indicate that traffic corresponding to the target FQDN#1 is allowed to be offloaded in the visited network, and the packet in step 320 can represent traffic corresponding to the target FQDN#1. In this application, for the convenience of description, the packet accessing traffic corresponding to a certain FQDN can be referred to as the packet corresponding to the FQDN, and details are not described hereinafter.

[0187] In a possible implementation, the information #A includes two information elements, one information element is used to indicate that offloading is allowed, and the other information element includes the target FQDN#1. The first session management network element learns from the information #A that traffic corresponding to the target FQDN#1 is allowed to be offloaded in the visited network, so the first session management network element can determine the offloading point in the visited network, and the first session management network element can determine the offloading rule according to the target FQDN#1 and send the determined offloading rule to the offloading point. In another possible implementation, the information #A includes the target FQDN#1. The first session management network element learns from internal logic that traffic corresponding to the target FQDN#1 is allowed to be offloaded in the visited network, so the first session management network element can determine the offloading point in the visited network, and the first session management network element can determine the offloading rule according to the target FQDN#1 and send the determined offloading rule to the offloading point. In any of the above possible implementations, the offloading rule is used to offload traffic corresponding to the target FQDN#1 to the visited network. Specifically, based on the offloading rule, when the FQDN of a certain traffic matches the target FQDN#1, the traffic is locally offloaded in the visited network.

[0188] Example 2, the target FQDN#1 includes a FQDN corresponding to traffic not allowed to be offloaded in the visited network.

[0189] In this example 2, the information #A in step 310 can be used to indicate that traffic corresponding to FQDNs other than the target FQDN#1 is allowed to be offloaded in the visited network, or the information #A in step 310 can be used to indicate that traffic corresponding to the target FQDN#1 is not allowed to be offloaded in the visited network; and the packet in step 320 can represent traffic corresponding to FQDNs other than the target FQDN#1.

[0190] In a possible implementation, the information A includes two information elements, one of which is used to indicate that splitting is not allowed in the visited network, and the other of which includes the target FQDN 1, and the first session management network element learns, according to the information A, that packets corresponding to FQDNs other than the target FQDN 1 are allowed to be split in the visited network, or the first session management network element learns, according to the information A, that packets corresponding to the target FQDN 1 are not allowed to be split in the visited network, so that the first session management network element can determine the splitting point in the visited network, and the first session management network element can determine the splitting rule according to the target FQDN 1 and send the determined splitting rule to the splitting point. In another possible implementation, the information A includes the target FQDN 1, and the first session management network element learns, according to internal logic, that packets corresponding to FQDNs other than the target FQDN 1 are allowed to be split in the visited network, or the first session management network element learns, according to internal logic, that packets corresponding to the target FQDN 1 are not allowed to be split in the visited network, so that the first session management network element can determine the splitting point in the visited network, and the first session management network element can determine the splitting rule according to the target FQDN 1 and send the determined splitting rule to the splitting point. In any of the above possible implementations, the splitting rule is used to split packets corresponding to FQDNs other than the target FQDN 1 to the visited network, specifically, based on the splitting rule, when the FQDN of a service matches FQDNs other than the target FQDN 1, or when the FQDN of a service does not match the target FQDN 1, the service is locally split in the visited network.

[0191] It can be understood that the above two examples are only exemplary descriptions, and the application is not limited thereto. For example, the target FQDN 1 can include: FQDNs of services allowed to be split in the visited network, and FQDNs of services not allowed to be split in the visited network.

[0192] It can also be understood that in the description of the first possible implementation, FQDN is mainly exemplarily described, and the application is not limited thereto. For example, FQDN can be replaced by IP address, AppID, or any one or more of them.

[0193] In a second possible implementation, the first session management network element determines the splitting rule according to configuration information.

[0194] As an example, the configuration information can be EAS deployment information, or locally configured policy information, or address information (such as EAS IP address) determined for the UE when the UE accesses services in the VPLMN.

[0195] The EAS deployment information includes information about deployment of the EAS in the edge network, for example, can include but is not limited to: FQDN corresponding to the service, EAS IP address information. The first core network element can locally configure the EAS deployment information, or can also receive the EAS deployment information from the AF, without limitation.

[0196] The following is mainly exemplarily described taking the EAS deployment information as an example.

[0197] The first session management network element can determine the offloading rule according to the EAS deployment information, and send the determined offloading rule to the offloading point.

[0198] Suppose that the EAS deployment information includes a range of FQDN corresponding to the service deployed in the VPLMN, denoted as target FQDN#2, or a range of IP corresponding to the service deployed in the VPLMN, denoted as target IP#2.

[0199] For example, the determined offloading rule is to offload the message corresponding to the target FQDN#2 to the visited network, specifically, based on the offloading rule, when the FQDN of the service accessed by a certain message matches the FQDN range corresponding to the offloading rule (i.e., the target FQDN#2), the service is locally offloaded in the visited network. For another example, the determined offloading rule is to offload the message corresponding to the target IP#2 to the visited network, specifically, based on the offloading rule, when the destination IP of a certain message matches the IP range corresponding to the offloading rule (i.e., the target IP#2), the message is locally offloaded in the visited network.

[0200] It can be understood that the address used to determine the offloading rule can also be a certain EAS IP address determined when the UE accesses the service in the VPLMN, such as an EAS IP address obtained by the first session management network element from other network elements, wherein the EAS IP address can be determined for the UE. The IP address can be an IP address received from the second session management network element, for example, such as that the EASDF sends a DNS request message to the DNS server, and receives a DNS response message from the DNS server, the DNS response message containing the IP address; the EASDF receives the DNS response message, and sends the IP address contained in the DNS response message to the second session management network element; the second session management network element receives the IP address, and sends the IP address to the first session management network element. It can be understood that this is not limited.

[0201] The third possible implementation manner is that the first session management network element determines the offloading rule according to the configuration information and the information #A.

[0202] The following is mainly exemplarily described taking the EAS deployment information as an example.

[0203] The first session management network element can determine the offloading rule according to the EAS deployment information and the information #A, and send the determined offloading rule to the offloading point.

[0204] For example, the EAS deployment information includes a FQDN range (denoted as target FQDN#2) corresponding to the service deployed in the VPLMN, or an IP range (denoted as target IP#2) corresponding to the service deployed in the VPLMN; the information #A includes a FQDN range (such as target FQDN#1) corresponding to the service allowed to be offloaded by the VPLMN, or an IP range (such as target IP#1) corresponding to the service allowed to be offloaded by the VPLMN.

[0205] For example, the determined offloading rule is to offload the packet corresponding to the FQDN (denoted as target FQDN#3) in the intersection part of the target FQDN#1 and the target FQDN#2 to the visited network. Specifically, based on the offloading rule, when the FQDN of the service accessed by a certain packet matches the FQDN range (i.e., target FQDN#3) corresponding to the offloading rule, the service is locally offloaded in the visited network.

[0206] For example, the determined offloading rule is to offload the packet corresponding to the IP (denoted as target IP#3) in the intersection part of the target IP#1 and the target IP#2 to the visited network. Specifically, based on the offloading rule, when the destination IP of a certain packet matches the IP range (i.e., target IP#3) corresponding to the offloading rule, the service is locally offloaded in the visited network.

[0207] For example, the first session management network element determines that the IP address range corresponding to the target FQDN#3 is the target IP#3 according to the local configuration, and the determined offloading rule is to offload the packet corresponding to the target IP#3 to the visited network. Specifically, based on the offloading rule, when the destination IP of a certain packet matches the IP range (i.e., target IP#3) corresponding to the offloading rule, the service is locally offloaded in the visited network.

[0208] Figure 4 FIG. 4 is a schematic diagram of another method 400 of communication provided by an embodiment of the present application. The method 400 can include the following steps.

[0209] 410, the first session management network element determines an offloading point in the visited network, and the first session management network element is a network element deployed in the visited network.

[0210] The first session management network element is a network element deployed in the VPLMN. For example, the first session management network element is a V-SMF.

[0211] For the offloading point, refer to the description in the method 300 above, which will not be repeated here.

[0212] Optionally, the first session management network element can determine the offloading point in the visited network according to local configuration or in a manner of obtaining from the NRF network element. As an example, after receiving the session establishment request message, the first session management network element determines the offloading point according to local configuration information.

[0213] It should be noted that the offloading point can be the same network element as the V-UPF serving the current session, or can be a different network element, which is not limited. As an example, the V-UPF is the V-UPF selected by the V-SMF to serve the session when the HR session is established. Details of the V-UPF are not described herein.

[0214] The session establishment request message may, for example, be an Nsmf_PDUSession_CreateSMContext Request message sent by the AMF to the first session management network element, which is not limited by the present application.

[0215] 420, the first session management network element sends the offloading rule to the offloading point, and the offloading rule is used to offload the packet to the visited network.

[0216] 430, the first session management network element receives information #A, wherein the information #A is used to represent whether offloading in the visited network is allowed.

[0217] In one possible implementation, the first session management network element receives the information #A from the second session management network element.

[0218] The information #A can also be described as representing (or indicating, or indicating) whether offloading is allowed. For description of the information #A, reference can be made to the related description in the method 300, which is not described herein.

[0219] Based on the above scheme, the first session management network element deployed in the visited network can determine the offloading point and send the offloading rule to the offloading point. In this way, when the terminal device accesses the visited network in the HR roaming manner, the terminal device can access the services in the visited network through the offloading point determined by the first session management network element, so as to realize local offloading in the visited network. In addition, the packet accessing the EAS can also be offloaded to the visited network through the offloading point, so that the terminal device can also access the edge services in the visited network when the terminal device accesses the visited network in the HR roaming manner. In addition, the first session management network element can determine how to process the offloading point or the offloading rule according to the information #A. That is, the first session management network element can first determine the offloading point in the visited network, and after determining the offloading point, the information #A can be received, and then the offloading point or the offloading rule can be processed according to the information #A, so as to meet the requirements of the information #A.

[0220] Optionally, the method 400 further comprises that the first session management network element can determine the offloading rule.

[0221] In a possible implementation, the first session management network element determines the offloading rule according to the configuration information. Specifically, reference can be made to the related description of the second possible implementation of the "determining the offloading rule by the first session management network element" of the method 300, which will not be repeated here.

[0222] In another possible implementation, the first session management network element can determine the offloading rule according to the locally configured information #A. Specifically, reference can be made to the related description of the first possible implementation of the "determining the offloading rule by the first session management network element" of the method 300, which will not be repeated here.

[0223] Optionally, in step 430, the first session management network element processes the offloading point or the offloading rule according to the information #A, for example, the first session management network element deletes or updates the offloading rule according to the information #A. Optionally, the first session management network element can also delete or update the offloading point according to the information #A. The following introduces several possible cases in combination with the information #A.

[0224] It should be noted that the above mainly takes the processing of the offloading point and the processing of the offloading rule as examples for illustrative purposes, and it can be understood that the present application does not limit to only processing the offloading point or only processing the offloading rule. For example, the first session management network element can also process the offloading point and the offloading rule according to the information #A, that is, the processing object can be the offloading point and the offloading rule. For example, in the case of processing the offloading point, or in the case of processing the offloading rule, or in the case of processing the offloading point and the offloading rule, the specific processing mode can include any one or more of deletion, update, replacement, sending, etc., or can also be no action. It should be noted that when the first session management network element processes the offloading point and the offloading rule, the processing mode of the offloading point and the offloading rule is not limited to be the same. For example, if the first session management network element processes the offloading point and the offloading rule, different actions in the above processing can be performed on the offloading point and the offloading rule, for example, updating the offloading point and sending the offloading rule; or updating the offloading point and deleting the offloading rule; or deleting the offloading rule and the offloading point without action, etc.

[0225] In a first possible case, the information #A is used to indicate that offloading in the visited network is allowed.

[0226] In this case, as an example, the first session management network element can not delete or update the offloading rule, and can not delete or update the offloading point, that is, the offloading point in step 410 and the offloading rule in step 420 are continued to be used.

[0227] It is to be noted that in this case, the first session management network element can also update or delete the split rule, and / or the first session management network element can also update or delete the split point.

[0228] In a second possible case, the information #A is used to indicate that the first traffic is not allowed to be split in the visited network.

[0229] In this case, as an example, the first session management network element can delete the split rule. Optionally, the first session management network element can delete the split point.

[0230] For example, in the case that the split point is different from the V-UPF (i.e. the V-UPF serving the current session), the first session management network element can delete the split point. It can be understood that if the split point is deleted, it means that the split rule of the split point is deleted. Wherein, deleting the split point, as can be understood, means not using the split point, and selecting the V-UPF serving the current session.

[0231] For another example, in the case that the split point is the same as the V-UPF (i.e. the V-UPF serving the current session), the first session management network element can delete the split rule, and not delete the split point.

[0232] In a third possible case, the information #A is used to indicate that the first traffic is allowed to be split in the visited network.

[0233] In this case, as an example, the first session management network element updates the split point or the split rule according to the information #A.

[0234] 1) The first session management network element updates the split rule.

[0235] Example 1, the information #A includes an identification of the first traffic.

[0236] For example, in step 430, the information #A received by the first session management network element includes an identification of the first traffic, and the information #A is used to indicate that the first traffic is allowed to be split in the visited network; the first session management network element updates the split rule according to the first traffic. Optionally, the first session management network element sends the updated split rule to the split point. Wherein, updating the split rule can include determining the updated split rule according to the first traffic in the information #A, and the updated split rule is used to split the packet corresponding to the first traffic to the visited network.

[0237] As an example, the identification of the first traffic can be any of the following: FQDN (or FQDN range), application identification, IP address, port number. That is, the information #A can include one or more of the following: FQDN (or FQDN range), application identification, IP address, port number.

[0238] The following mainly takes FQDN as an example for illustration. It can be understood that the FQDN in the following examples can be replaced by any of the following: application identifier, IP address, port number.

[0239] For example, the information #A includes one or more FQDNs, denoted as target FQDN #4. The information #A in step 430 can be used to indicate that the packet corresponding to the target FQDN #4 is allowed to be offloaded in the visited network. Further, the first session management network element can update the offloading rule according to the target FQDN #4 (or it can be understood that the first session management network element re-determines the offloading rule according to the target FQDN #4).

[0240] In a possible implementation, the information #A includes two information elements, one of which is used to indicate that offloading in the visited network is allowed, and the other includes the target FQDN #4. The first session management network element learns from the information #A that the packet corresponding to the target FQDN #4 is allowed to be offloaded in the visited network. In another possible implementation, the information #A includes the target FQDN #4, and the first session management network element determines according to internal logic that the service corresponding to the target FQDN #4 is allowed to be offloaded in the visited network. In any of the above possible implementations, the first session management network element can update the offloading rule according to the target FQDN #4 (or it can be understood that the first session management network element re-determines the offloading rule according to the target FQDN #4), and send the updated offloading rule to the offloading point. The updated offloading rule is used to offload the packet corresponding to the target FQDN #4 to the visited network. Specifically, based on the offloading rule, when the FQDN of a certain service matches the target FQDN #4, the service is locally offloaded in the visited network.

[0241] Example 2: The information #A includes the identifier of the second service.

[0242] For example, in step 430, the information #A received by the first session management network element includes the identifier of the second service. The information #A is used to indicate that the second service is not allowed to be offloaded in the visited network, or it can also be understood as allowing services other than the second service to be offloaded in the visited network. The first session management network element updates the offloading rule according to the two services. Optionally, the first session management network element sends the updated offloading rule to the offloading point. The updated offloading rule can include determining the updated offloading rule according to the second service in the information #A. The updated offloading rule is used to offload the packet corresponding to the service other than the second service to the visited network.

[0243] As an example, the identifier of the second service can be any of the following: FQDN (or FQDN range), application identifier, IP address, port number. That is, the information #A can include one or more of the following: FQDN (or FQDN range), application identifier, IP address, port number.

[0244] The following mainly takes FQDN as an example for description. It can be understood that the FQDN in the following examples can also be replaced by any of the following: application identifier, IP address, port number.

[0245] For example, the information #A includes one or more FQDNs, denoted as target FQDN #5. The information #A in step 430 can be used to indicate that the packets corresponding to the FQDNs other than the target FQDN #5 are allowed to be offloaded in the visited network, or the information #A in step 430 can be used to indicate that the packets corresponding to the target FQDN #5 are not allowed to be offloaded in the visited network.

[0246] In a possible implementation, the information #A includes two information elements, one information element is used to indicate that offloading in the visited network is not allowed, and the other information element includes the target FQDN #5. The first session management network element learns, according to the information #A, that the packets corresponding to the FQDNs other than the target FQDN #5 are allowed to be offloaded in the visited network. In another possible implementation, the information #A includes the target FQDN #5. The first session management network element determines, according to internal logic, that the service corresponding to the target FQDN #5 is not allowed to be offloaded in the visited network. In any of the above possible implementations, the first session management network element can update the offloading rule according to the target FQDN #5 (or it can be understood that the first session management network element re-determines the offloading rule according to the target FQDN #5), and sends the updated offloading rule to the offloading point. The updated offloading rule is used to offload the packets corresponding to the FQDNs other than the target FQDN #5 to the visited network. Specifically, based on the updated offloading rule, when the FQDN of a certain service matches the FQDNs other than the target FQDN #5, or when the FQDN of a certain service does not match the target FQDN #5, the service is locally offloaded in the visited network.

[0247] It can be understood that the above two examples are only exemplary descriptions, and the present application is not limited thereto. For example, the information #A includes the identifiers of the first service and the second service.

[0248] 2) The first session management network element updates the offloading point.

[0249] Optionally, the information #A includes the identifier of the first service. For the identifier of the first service, refer to the description above, and the following mainly takes FQDN as an example for exemplary description.

[0250] For example, in step 430, the information #A received by the first session management network element includes an identifier of the first service, the information #A is used to indicate that the first service is allowed to be offloaded in the visited network; the first session management network element updates the offloading point according to the identifier of the first service; and the first session management network element can send the offloading rule to the updated offloading point. Wherein, updating the offloading point can include determining a new offloading point according to the first service in the information #A, and the offloading rule is used to offload the packet corresponding to the first service to the visited network through the new offloading point.

[0251] The first session management network element updates the offloading point, or in other words, the first session management network element reselects the offloading point. One possible reason for triggering the first session management network element to update the offloading point is, for example, that the information #A contains one or more FQDNs allowed to be offloaded in the visited network, and there is a UPF with a closer deployment location for the services corresponding to the one or more FQDNs, in which case the first session management network element can select this UPF as the offloading point. It should be noted that if the reselection of the offloading point is performed, the first session management network element sends the offloading rule to the new offloading point and can delete the offloading rule of the old offloading point.

[0252] It can be understood that the above several cases are only exemplary and are not limited thereto. After the first session management network element determines the offloading point in the visited network, the scheme of processing the offloading point or the offloading rule based on the information #A is applicable to the embodiments of the present application.

[0253] Optionally, after the first session management network element updates the offloading point according to the information #A, the method 400 further includes: the first session management network element sends updated tunnel information to a second session management network element. Wherein, the second session management network element is a network element deployed in the home network. For example, the second session management network element is an H-SMF.

[0254] It should be noted that when the selected offloading point in step 410 is different from the V-UPF serving the current session, and the deletion of the offloading point is performed, or the update of the offloading point is performed, the first session management network element sends the updated tunnel information to the second session management network element.

[0255] For example, if the first session management network element deletes the offloading point, the first session management network element determines to update the tunnel information to the second session management network element according to the information #A, and then the first session management network element sends the updated tunnel information to the second session management network element according to the information #A. Wherein, the tunnel information, for example, can include information of the updated offloading point, or can also include information of the original V-UPF.

[0256] For example, if the first session management network element performs the update of the split point, the first session management network element sends the information of the updated split point to the second session management network element, which can include the address of the updated split point, or can also include the identifier of the updated split point.

[0257] For another example, if the first session management network element performs the deletion of the split point, and the split point is different from the original V-UPF of the HR session, the first session management network element sends the information of the original V-UPF of the session (i.e. the HR session) to the second session management network element, which can include the address of the original V-UPF, or can also include the identifier of the original V-UPF.

[0258] For the convenience of understanding, the following will be described in combination with Figures 5 to 8 The following examples assume that the first session management network element is a V-SMF, the second session management network element is an H-SMF, the policy control network element is an H-PCF, and the information #A is an authorization policy. The steps involved can refer to the description above.

[0259] Figure 5 FIG. 5 is a schematic flowchart of a method 500 of communication provided by an embodiment of the present application. The method 500 can be used to implement the scheme of the method 300, for example, the method 500 can be used in the scenario that the V-SMF inserts a split point according to the authorization policy (i.e. the information #A). The method 500 can include the following steps.

[0260] 501, the V-SMF obtains the authorization policy.

[0261] The authorization policy is used to indicate (or represent, or show) whether the VPLMN split is allowed (or the authorization policy is used to indicate (or represent, or show) whether the split is allowed). The authorization policy is mainly used to indicate that the VPLMN split is allowed in the method 500. For the authorization policy, refer to the description of the information #A in the method 300 above, which will not be repeated here.

[0262] The V-SMF obtains the authorization policy, which can be achieved by at least any of the following ways:

[0263] The first possible way is that the V-SMF locally configures the authorization policy. For example, the configuration structure of the authorization policy in the V-SMF is in the form of a {PLMN ID--authorization policy} set, as shown in Table 1 above.

[0264] The second possible way is that the V-SMF receives the authorization policy. For example, the V-SMF receives the authorization policy from the H-SMF.

[0265] As to the specific way for the V-SMF to obtain the authorization policy, refer to the way for the first session management network element to obtain the information #A in the method 300 above, which will not be repeated here.

[0266] Optionally, the authorization policy includes a target FQDN #1 (or FQDN range), and the target FQDN #1 can include one or more FQDNs. The target FQDN #1 includes: FQDNs corresponding to services allowed to be offloaded in the VPLMN, and / or FQDNs corresponding to services not allowed to be offloaded in the VPLMN. For example, the target FQDN #1 includes FQDNs corresponding to services allowed to be offloaded in the VPLMN, specifically, when the FQDN of a service matches the target FQDN #1, the service is allowed to be offloaded in the VPLMN.

[0267] 502, the UE initiates a session establishment procedure.

[0268] In the HR roaming scenario, the UE can initiate an HR session establishment procedure. The present application does not limit the specific session establishment procedure, for example, the following way can be followed: after the AMF receives the session establishment request of the UE, the V-SMF and the H-SMF serving the HR session are selected; after the V-SMF and the H-SMF receive the session establishment request, the V-UPF and the H-UPF serving the HR session are selected respectively, and the N4 session is created, and the user plane tunnel information is sent. If the session establishment is successful, the network side returns a session establishment response to the UE, and then the message can be transmitted through the HR session.

[0269] Specifically, refer to sections 4.3.2.2.2 and the like in 3GPP standard TS 23.502, or the way of session establishment that appears later, which is not limited by the present application.

[0270] It should be understood that step 502 does not limit the execution of a complete HR session establishment procedure, and the steps after step 502 can reuse (or reuse) the HR session establishment procedure, or in other words, the steps after step 502 can be executed in the HR session establishment procedure.

[0271] 503, the AMF sends the H-SMF ID to the V-SMF.

[0272] In one possible case, the configuration structure of the authorization policy in the V-SMF is in the form of a {PLMN ID--authorization policy} set, in which case the AMF can send the H-SMF ID to the V-SMF, and then the V-SMF can determine the HPLMN ID, i.e., determine the HPLMN, according to the H-SMF ID.

[0273] In a possible implementation, the AMF sends, to the V-SMF, an Nsmf interface PDU session establishment session management context request (Nsmf_PDUSession_CreateSMContext Request) message carrying the H-SMF ID, by reusing the HR session establishment procedure.

[0274] It should be understood that the Nsmf_PDUSession_CreateSMContext Request message is only an example and is not limited in this regard.

[0275] 504. The V-SMF determines, according to the H-SMF ID and the authorization policy, that the VPLMN is allowed to split.

[0276] For example, assuming that the configuration structure of the authorization policy in the V-SMF in step 501 is in the form of a {PLMN ID--authorization policy} set, such as in Table 1, the V-SMF can determine the HPLMN ID according to the H-SMF ID received in step 503, and then obtain the authorization policy corresponding to the HPLMN based on Table 1.

[0277] For example, assuming that the configuration structure of the authorization policy in the V-SMF in step 501 is in the form of a {PLMN ID--authorization policy} set, such as in Table 1, the V-SMF can determine the HPLMN ID according to the H-SMF ID received in step 503, and then obtain the authorization policy corresponding to the HPLMN based on Table 1.

[0278] 505. The V-SMF determines the split point according to the UE location and the authorization policy.

[0279] That is, in step 310 in the above method 300, the first session management network element determines the split point in the visited network, which can include that the first session management network element determines the split point according to the UE location and the authorization policy. For example, if the authorization policy is used to indicate that the VPLMN is allowed to split, the V-SMF can insert the split point according to the UE location. It can be understood that if the authorization policy is used to indicate that the VPLMN is not allowed to split, the V-SMF can not insert the split point.

[0280] The split point may, for example, include a UL CL or a BP. Alternatively, the split point can also include an L-PSA. The UL CL can be the same as or different from the V-UPF of the HR session, and is not limited in this regard.

[0281] 506. The V-SMF sends the split rule to the split point.

[0282] The V-SMF can determine the offloading rule and send the offloading rule to the offloading point. The offloading rule contains an IP range, which is used to offload the message accessing the IP range to the L-PSA.

[0283] In one possible implementation, the V-SMF determines the offloading rule according to the locally configured EAS deployment information.

[0284] In another possible implementation, if the authorization policy in step 501 includes a target FQDN#1, the V-SMF can determine the offloading rule according to the target FQDN#1.

[0285] For the above two manners, reference can be made to the description in the method 300, which will not be repeated here.

[0286] The V-SMF sends the offloading rule to the offloading point, which can be implemented by, for example, an N4 session modification request or an N4 session establishment request.

[0287] Taking the UL CL as an example, in a first possible case, the UL CL is the same as the V-UPF of the HR session. In this case, the V-SMF sends the offloading rule to the UL CL, which can include that the V-SMF sends an N4 session modification request message to the UL CL, and the N4 session modification request message includes the offloading rule. Correspondingly, the UL CL can send an N4 session modification response message to the V-SMF.

[0288] In a second possible case, the UL CL is different from the V-UPF of the HR session. In this case, the V-SMF sends the offloading rule to the UL CL, which can include that the V-SMF sends an N4 session establishment request message to the UL CL, and the N4 session establishment request message includes the offloading rule. Correspondingly, the UL CL can send an N4 session establishment response message to the V-SMF.

[0289] 507, the V-SMF sends the address of the H-EASDF to the UE.

[0290] In a possible implementation, the V-SMF sends the address of the V-EASDF to the UE through the AMF. For example, the V-SMF sends an N1 message to the UE through the AMF, where the N1 message includes an N1 SM container carrying the address of the H-EASDF. For example, the V-SMF sends the address of the H-EASDF to the AMF through a Namf_Communication_N1N2MessageTransfer message, and then the AMF sends the address of the H-EASDF to the UE through a non-access stratum (NAS) message. The UE and the AMF can interact through an N1 interface, and the interaction message can be referred to as a NAS message.

[0291] Based on the method 500, when the V-SMF learns, according to the authorization policy, that the VPLMN is allowed to split traffic, the V-SMF determines a splitting point and sends a splitting rule to the splitting point, so that local splitting of the VPLMN in the HR roaming scenario can be implemented.

[0292] Figure 6 FIG. 6 is a schematic flowchart of another method 600 of communication provided by an embodiment of the present application. The method 600 can be used to implement the scheme of the method 300, for example, the method 600 can be used in a scenario where the V-SMF inserts a splitting point according to an authorization policy (i.e., information #A) obtained from the HPLMN. The method 600 can include the following steps.

[0293] 601, the UE initiates a session establishment procedure.

[0294] The step 601 is similar to the step 502, and details are not repeated here.

[0295] 602, the H-PCF sends an authorization policy to the H-SMF.

[0296] The authorization policy is used to indicate (or represent, or show) whether the VPLMN is allowed to split traffic (or the authorization policy is used to indicate whether splitting is allowed). In the method 600, the authorization policy is mainly used to indicate (or represent, or show) that the VPLMN is allowed to split traffic. For the authorization policy, refer to the description of the information #A in the method 300 above, and details are not repeated here.

[0297] In a possible implementation, the HR session establishment procedure is reused, and the authorization policy is implemented through a session management (SM) policy. For example, a PDU session can be established or modified through SM signaling, and in the procedure of establishing or modifying through the SM signaling, the H-PCF sends the authorization policy to the H-SMF.

[0298] Specifically, one possible implementation is that after the H-SMF receives the Nsmf_PDUSession_Create Request message from the V-SMF, the H-PCF selection is triggered. After the H-PCF selection is completed, the SM policy association establishment procedure or the SM policy association modification procedure is triggered. In the SM policy association establishment procedure, the H-SMF sends the Npcf interface SM policy control establishment request (Npcf_SMPolicyControl_Create Request) message to the H-PCF, which may contain one or more of the following: the user permanent identifier (SUPI) or the permanent equipment identifier (PEI) of the UE, the PDU session identifier, the data network name (DNN), the single network slice selection assistance information (S-NSSAI), the radio access technology (RAT) type, and the like. After the H-PCF receives the message, the subscription information of the UE and / or the subscription information of the session is determined according to the local configuration or obtained from the UDR, and the authorized policy is determined and sent to the H-SMF through the Npcf interface SM policy control establishment response (Npcf_SMPolicyControl_CreateResponse) message. It can be understood that the above is only an exemplary description given for ease of understanding, and is not limited thereto.

[0299] It should be noted that the H-SMF can be locally configured with the authorized policy, in which case the H-PCF can not send the authorized policy to the H-SMF.

[0300] 603, the H-SMF sends the authorized policy to the V-SMF.

[0301] The authorized policy is used to indicate that the VPLMN split is allowed.

[0302] In a possible implementation, the HR session establishment procedure is reused. For example, the H-SMF receives a session establishment request message from the V-SMF, and sends a session establishment response message to the V-SMF, where the authorization policy is carried in the session establishment response message. It can be understood that the authorization policy can be received from the H-PCF in step 602, or can also be locally configured.

[0303] Optionally, the authorization policy includes a target FQDN #1 (or FQDN range), and the target FQDN #1 can include one or more FQDNs. The target FQDN #1 includes FQDNs of services allowed to be offloaded in the VPLMN, and / or FQDNs of services not allowed to be offloaded in the VPLMN. For example, the target FQDN #1 includes FQDNs of services allowed to be offloaded in the VPLMN, and specifically, when the FQDN of a service matches the target FQDN #1, the service is allowed to be offloaded in the VPLMN.

[0304] 604. The V-SMF determines the offloading point according to the UE location and the authorization policy.

[0305] That is, in step 310 in the method 300 described above, the first session management network element determines the offloading point in the visited network, which can include that the first session management network element determines the offloading point according to the UE location and the authorization policy. For example, if the authorization policy indicates that offloading in the VPLMN is allowed, the V-SMF can insert the offloading point according to the UE location. It can be understood that if the authorization policy indicates that offloading in the VPLMN is not allowed, the V-SMF can not insert the offloading point.

[0306] The offloading point can include, for example, a UL CL or a BP. Alternatively, the offloading point can also include an L-PSA. The UL CL can be the same as or different from the V-UPF of the HR session, and is not limited.

[0307] 605. The V-SMF sends the offloading rule to the offloading point.

[0308] The V-SMF can determine the offloading rule and send the offloading rule to the offloading point. The offloading rule includes an IP range, which is used to offload packets accessing the IP range to the L-PSA.

[0309] In a possible implementation, the V-SMF determines the offloading rule according to the locally configured EAS deployment information.

[0310] In another possible implementation, if the authorization policy in step 603 includes the target FQDN #1, the V-SMF can determine the offloading rule according to the target FQDN #1.

[0311] For the two manners, reference can be made to the description in the method 300, which will not be repeated here.

[0312] The V-SMF sends the offloading rule to the offloading point, which can be implemented through an N4 session modification request or an N4 session establishment request, for example. For details, reference can be made to the description in step 506, which will not be repeated here.

[0313] Optionally, if the UL CL is different from the V-UPF of the HR session, the method 600 can further include steps 607-608.

[0314] 606. The V-SMF sends an H-EASDF address to the UE.

[0315] The step 606 is similar to the step 507, which will not be repeated here.

[0316] 607. The V-SMF sends tunnel information to the H-SMF.

[0317] The tunnel information can be the tunnel information of the UL CL, which is determined in the step 604.

[0318] In a possible implementation, the HR session establishment procedure is reused. For example, the V-SMF sends an Nsmf_PDUSession_Update Request message to the H-SMF, which carries the tunnel information.

[0319] 608. The H-SMF sends the tunnel information to the H-UPF.

[0320] In a possible implementation, the H-SMF reuses the HR session establishment procedure. That is, the H-SMF sends an N4 session modification request message to the H-UPF, which includes the tunnel information. Correspondingly, the H-UPF can send an N4 session modification response message to the H-SMF.

[0321] Based on the method 600, the V-SMF can insert the offloading point according to the authorization policy obtained from the HPLMN, and send the offloading rule to the offloading point, so as to implement the local offloading of the VPLMN in the HR roaming scenario.

[0322] Figure 7 FIG. 7 is a schematic flowchart of another method 700 of communication provided by an embodiment of the present application. The method 700 can be used to implement the scheme of the method 400, for example, the method 700 can be used in the scenario of the V-SMF inserting the offloading point in advance. The method 700 can include the following steps.

[0323] 701. The UE initiates a session establishment procedure.

[0324] In step 701, the V-SMF determines the split point based on the UE location.

[0325] 702. The V-SMF determines the split point based on the UE location.

[0326] The split point may, for example, include a UL CL or BP, and an L-PSA. The UL CL may be the same as the V-UPF of the HR session, or may be different, without limitation.

[0327] 703. The V-SMF sends a split rule to the split point.

[0328] In step 703, the V-SMF sends a split rule to the split point, which is similar to step 506, and thus will not be described here.

[0329] 704. The V-SMF sends a session establishment request message to the H-SMF.

[0330] In one possible implementation, the V-SMF sends an Nsmf_PDUSession_Create Request message to the H-SMF, reusing the HR session establishment procedure.

[0331] It should be understood that the Nsmf_PDUSession_Create Request message is only an example and is not limited in this regard.

[0332] 705. The H-PCF sends an authorization policy to the H-SMF.

[0333] The authorization policy is used to indicate (or represent, or indicate) whether the VPLMN split is allowed (or the authorization policy is used to indicate (or represent, or indicate) whether the split is allowed). For the authorization policy, refer to the description of information #A in method 300 above, which will not be described here.

[0334] In step 705, the H-PCF sends an authorization policy to the H-SMF, which is similar to step 602, and thus will not be described here.

[0335] 706. The H-SMF sends the authorization policy to the V-SMF.

[0336] For example, after receiving the session establishment request message from the V-SMF, the H-SMF sends a session establishment response message to the V-SMF, and carries the authorization policy in the session establishment response message. It can be understood that the authorization policy may be locally configured by the H-SMF, or may be received from the H-PCF in step 706. Alternatively, both the locally configured and the received authorization policies from the H-PCF exist, and the H-SMF can send any one of them, for example, the H-SMF sends the authorization policy received from the H-PCF to the V-SMF.

[0337] In one possible implementation, the HR session establishment procedure is reused, and the H-SMF sends an Nsmf interface PDU session establishment response (Nsmf_PDUSession_Create Response) message to the V-SMF.

[0338] It should be understood that the Nsmf_PDUSession_Create Response message is only an example and is not limited thereto.

[0339] In a first possible case, the authorization policy is used to indicate that splitting in the VPLMN is allowed. In this case, the V-SMF can directly send the address of the H-EASDF to the UE. That is, steps 707, 709-710 can not be performed.

[0340] In a second possible case, the authorization policy is used to indicate that splitting in the VPLMN is not allowed, or the authorization policy is used to indicate that packets corresponding to the target FQDN#2 (or FQDN range) are allowed to be split in the visited network. In this case, the method 700 can include steps 707, 709-710.

[0341] 707. The V-SMF deletes or updates the splitting point and / or deletes or updates the splitting rule according to the authorization policy.

[0342] In one example, if the authorization policy received by the V-SMF indicates that splitting in the VPLMN is not allowed, the V-SMF can delete or update the splitting point. For example, the V-SMF can delete one or more of the following: the L-PSA, the UL CL, and the splitting rule of the UL CL. As an example, in the case where the UL CL is different from the V-UPF selected by the HR session, the V-SMF can delete the UL CL. Deleting the UL CL also means deleting the splitting rule of the UL CL. As an example, in the case where the UL CL is the same as the V-UPF selected by the HR session, the V-SMF can delete the splitting rule of the UL CL.

[0343] In another example, if the authorization policy indicates that packets corresponding to the target FQDN#2 are allowed to be split in the visited network, the V-SMF can update one or more of the following: the UL CL, the L-PSA, and the splitting rule of the UL CL. Optionally, the V-SMF can perform one or more of the following: reselect the splitting point, determine and send the splitting rule to the new splitting point, and delete the splitting rule of the old splitting point. Specifically, reference can be made to the third possible case in the method 400, which will not be described here again.

[0344] 708. The V-SMF sends the H-EASDF address to the UE.

[0345] Step 708 is similar to step 507, which will not be described here again.

[0346] Optionally, if the method 700 includes step 707, i.e., the V-SMF performs the deletion or update of the split point, the method 700 can further include steps 709-710.

[0347] 709. The V-SMF sends the tunnel information to the H-SMF.

[0348] The tunnel information can be UL CL tunnel information or UPF tunnel information, etc.

[0349] In the first possible case, if the UL CL update is performed in step 707, the UL CL in step 709 is the updated UL CL, i.e., the V-SMF sends the updated tunnel information to the H-SMF.

[0350] In the second possible case, if the UL CL deletion is performed in step 707, and the UL CL is different from the original V-UPF of the HR session, the V-SMF sends the tunnel information of the original V-UPF to the H-SMF.

[0351] In a possible implementation, the V-SMF reuses the HR session establishment procedure. For example, the V-SMF sends an Nsmf interface PDU session update request (Nsmf_PDUSession_Update Request) message to the H-SMF, and the message carries the tunnel information.

[0352] 710. The H-SMF sends the tunnel information to the H-UPF.

[0353] In a possible implementation, the H-SMF reuses the HR session establishment procedure. That is, the H-SMF sends an N4 session modification request message to the H-UPF, and the N4 session modification request message includes the tunnel information. Correspondingly, the H-UPF can send an N4 session modification response message to the H-SMF.

[0354] Based on the above method 700, the V-SMF can insert the split point in advance, and then determine whether to delete or update the split point and / or delete or update the split rule according to the authorization policy obtained from the HPLMN.

[0355] Figure 8 is another schematic flowchart of a method 800 of communication provided by the embodiments of the present application. The method 800 can be used in the scenario where the V-SMF determines the split rule based on the obtained address information. The method 800 can include the following steps.

[0356] 801. The V-SMF obtains an EAS IP address #1.

[0357] The EAS IP address #1 is an EAS IP address corresponding to a service deployed in the VPLMN, which can be a certain EAS IP address determined for the terminal device. For example, the EAS IP address #1 is determined (or selected) for the UE when the UE accesses a service in the VPLMN.

[0358] As an example, the V-SMF receives the EAS IP address #1 from the H-SMF.

[0359] It should be noted that the present application does not limit the manner of obtaining the EAS IP address #1. One possible implementation is that the EAS DF sends a DNS request message to a DNS server and receives a DNS response message from the DNS server, wherein the DNS response message contains the EAS IP address #1. After receiving the DNS response message, the EAS DF sends the EAS IP address #1 contained in the DNS response message to the H-SMF. After receiving the EAS IP address #1, the H-SMF sends the EAS IP address #1 to the V-SMF.

[0360] 802. Based on the EAS IP address #1, the V-SMF determines the split point and the split rule.

[0361] As described above in the method 300, the information #A is used to represent (or indicate, or show) whether the split in the VPLMN is allowed, which can also be described as the information #A being used to represent (or indicate, or show) whether the split point in the VPLMN is determined (or selected, or inserted), or the information #A can be used to represent (or indicate, or show) whether the split point is determined (or selected, or inserted). In the method 800, at least the following two implementation manners are included.

[0362] In one possible manner, the information #A is the EAS IP address #1, that is, if the V-SMF receives the EAS IP address #1, the V-SMF determines (or inserts) the split point. For example, the V-SMF can determine (or insert) the split point according to the EAS IP address #1 and / or local configuration, wherein the local configuration can be deployment information of the EAS, etc. It can be understood that in this manner, for the sending end (such as the H-SMF), the H-SMF sends the EAS IP address #1 to the V-SMF; for the receiving end V-SMF, the EAS IP address #1 can be used to trigger the V-SMF to determine (or insert) the split point, that is, after receiving the EAS IP address #1, the V-SMF can determine (or insert) the split point according to the EAS IP address #1 and the EAS deployment information.

[0363] In another possible way, if the V-SMF receives the EAS IP address #1, the V-SMF obtains information #A (for example, the information #A is locally configured or is received from the H-SMF, which can be referred to the description in the method 300). If the information #A is used to indicate that the splitting in the VPLMN is allowed (or the splitting is allowed), the V-SMF determines (or inserts) the splitting point. For example, the V-SMF can determine (or insert) the splitting point according to one or more of the following: the EAS IP address #1, the information #A, and the local configuration. The local configuration can be the deployment information of the EAS, and the like. It can be understood that, in this way, for the sending end (for example, the H-SMF), the H-SMF sends the EAS IP address #1 to the V-SMF. For the receiving end V-SMF, the EAS IP address #1 can be used in combination with the information #A to trigger the V-SMF to determine (or insert) the splitting point. That is, after the V-SMF receives the EAS IP address #1, if the information #A is used to indicate that the splitting in the VPLMN is allowed (or the splitting is allowed), the V-SMF can determine (or insert) the splitting point according to the EAS IP #1, the information #A (for example, according to the FQDN or IP address range contained in the information #A), and the deployment information of the EAS.

[0364] The V-SMF can also determine the splitting rule. The determined splitting rule splits the service to the VPLMN. Specifically, the service can be described by one or more of the source IP, the destination IP, the source port number, and the destination port number. For example, the splitting rule can be used to split the message accessing the EAS IP address #1 to the VPLMN. Specifically, based on the splitting rule, when the destination IP of a certain message matches the EAS IP address #1, the message is locally split in the VPLMN.

[0365] In one possible way, the V-SMF can determine the splitting rule according to one or more of the following: the EAS IP address #1, the information #A, and the local configuration. The local configuration can be the deployment information of the EAS, and the like.

[0366] For example, if the V-SMF receives the EAS IP address #1, the V-SMF determines the splitting rule (for example, the V-SMF can determine the splitting rule according to the EAS IP address #1 and / or the local configuration).

[0367] For another example, if the V-SMF receives the EAS IP address #1, the V-SMF obtains the information #A (for example, the information #A is locally configured or is received from the H-SMF, which can be referred to the description in the method 300). If the information #A is used to indicate that the splitting in the VPLMN is allowed (or the splitting is allowed), the V-SMF determines the splitting rule (for example, the V-SMF can determine the splitting rule according to one or more of the following: the EAS IP address #1, the information #A, and the local configuration).

[0368] For another example, if the V-SMF performs the determination of the split point, the V-SMF can perform the action of determining the split rule (e.g., the V-SMF can determine the split rule according to one or more of the EAS IP address #1, the information #A, and the local configuration).

[0369] It can be understood that the above is only an example description, and the present application is not limited thereto. For example, if the V-SMF receives the EAS IP address #1, the V-SMF can process the split point or the split rule, and details can be referred to the description in the method 400, which will not be repeated here.

[0370] 803, the V-SMF sends the split rule to the split point.

[0371] The split rule contains the EAS IP address #1, and is used to split the packet accessing the EAS IP address #1 to the L-PSA.

[0372] The V-SMF sends the split rule to the split point, which can be implemented by the N4 session modification request or the N4 session establishment request. Details can be referred to the description in the step 506, which will not be repeated here.

[0373] Based on the above method 800, the V-SMF can determine the split point and the split rule according to the obtained address information, so as to realize the local EAS discovery and the local split of the VPLMN in the HR roaming scenario.

[0374] It can be understood that the method 800 is only a simple example description, and is not limited thereto. For example, before the step 802, the method 800 further includes that the H-PCF sends the authorization policy to the H-SMF, and the H-SMF sends the authorization policy to the V-SMF. For another example, after the step 803, the method 800 further includes that the V-SMF sends the address of the H-EASDF to the UE, and the like.

[0375] It can be understood that the examples in the embodiments of the present application Figures 5 to 8 are only for the convenience of those skilled in the art to understand the embodiments of the present application, and are not intended to limit the embodiments of the present application to the specific scenarios exemplified. Those skilled in the art can obviously make various equivalent modifications or changes according to the examples of Figures 5 to 8 . Such modifications or changes also fall within the scope of the embodiments of the present application. For example, the session establishment process in the above Figures 5 to 8 may also be replaced by the session modification process. For another example, the UL CL mentioned in the above embodiments can be replaced by the BP, or other network elements or modules that can perform the split.

[0376] It should also be understood that, in some embodiments described above, the message names, such as the Nsmf_PDUSession_Update Request message, the Nsmf_PDUSession_Context Request, and the like, are only examples and do not limit the protection scope of the embodiments of the present application.

[0377] It should also be understood that, in some embodiments described above, the FQDN is mainly exemplarily described, and the present application is not limited thereto. For example, the FQDN can be replaced by an IP address, an AppID, or any one or more thereof.

[0378] It should also be understood that the embodiments of the present application can be used in multiple scenarios, such as a scenario in which the V-UPF does not have the capability of resolving the DNS message and the VPLMN does not deploy the L-DNS server.

[0379] It should also be understood that some optional features in the embodiments of the present application can not depend on other features in some scenarios, or can be combined with other features in some scenarios, and are not limited.

[0380] It should also be understood that the solutions in the embodiments of the present application can be reasonably combined, and the explanations or descriptions of various terms appearing in the embodiments can be mutually referenced or explained in the embodiments, and this is not limited.

[0381] It should also be understood that the sizes of various serial numbers in the embodiments of the present application do not mean the order of execution, but are only distinguished for convenience of description, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0382] It should also be understood that the methods and operations implemented by the device in each of the above method embodiments can also be implemented by the constituent components (such as chips or circuits) of the device.

[0383] Corresponding to the methods given by each of the above method embodiments, the embodiments of the present application also provide corresponding devices, and the device includes a module for executing the corresponding modules of each of the above method embodiments. The module can be software, hardware, or a combination of software and hardware. It can be understood that the technical features described in the above method embodiments are also applicable to the following device embodiments.

[0384] Figure 9 is a schematic block diagram of a device for communication provided by the embodiments of the present application. The device 900 includes a transceiver unit 910 and a processing unit 920. The transceiver unit 910 can be used to implement the corresponding communication function. The transceiver unit 910 can also be referred to as a communication interface or a communication unit. The processing unit 920 can be used to implement the corresponding processing function, such as determining a shunt point.

[0385] Optionally, the apparatus 900 further includes a storage unit, which can be used to store instructions and / or data, and the processing unit 920 can read the instructions and / or data in the storage unit to enable the apparatus to implement the actions of the device or network element in each of the foregoing method embodiments.

[0386] In a first design, the apparatus 900 can be or can include a component (e.g., a chip) of the first session management network element in the foregoing embodiments. The apparatus 900 can implement the steps or procedures performed by the first session management network element in the method embodiments described above, in which the transceiver 910 can be configured to perform the transceiver-related operations of the first session management network element in the method embodiments described above, and the processing unit 920 can be configured to perform the processing-related operations of the first session management network element in the method embodiments described above.

[0387] In a first possible implementation, the processing unit 920 is configured to determine a split point in a visited network according to first information, the first information indicating that splitting is allowed in the visited network, and the first session management network element being a network element deployed in the visited network; and the transceiver 910 is configured to send a splitting rule to the split point, the splitting rule being used to split a packet to the visited network.

[0388] Optionally, the processing unit 920 is further configured to determine the splitting rule according to first traffic, and the first traffic being traffic allowed to be split in the visited network.

[0389] For example, the first information includes an identifier of the first traffic, and the first information indicates that the first traffic is allowed to be split in the visited network.

[0390] Optionally, the processing unit 920 is further configured to determine the splitting rule according to configuration information and / or the first information.

[0391] Optionally, the transceiver 910 is further configured to receive the first information from a second session management network element, the second session management network element being a network element deployed in a home network; or the first information is locally configured by the first session management network element.

[0392] For example, the split point is an uplink classifier or a branch point.

[0393] In a second possible implementation, the processing unit 920 is configured to determine a split point in a visited network, the first session management network element being a network element deployed in the visited network; the transceiver 910 is configured to send a splitting rule to the split point, the splitting rule being used to split a packet to the visited network; and the transceiver 910 is further configured to receive first information, the first information indicating whether splitting is allowed in the visited network.

[0394] Optionally, the processing unit 920 is configured to delete or update the splitting rule according to the first information.

[0395] Optionally, the processing unit 920 is configured to delete or update the offloading rule according to the first information, including: the processing unit 920 is configured to delete the offloading rule if the first information indicates that offloading is not allowed in the visited network.

[0396] Optionally, the processing unit 920 is configured to delete or update the offloading rule according to the first information, including: the processing unit 920 is configured to update the offloading rule according to the first service if the first information indicates that the first service is allowed to offload in the visited network.

[0397] Optionally, the processing unit 920 is configured to delete or update the offloading point according to the first information.

[0398] Optionally, the processing unit 920 is configured to delete or update the offloading point according to the first information, including: the processing unit 920 is configured to delete the offloading point if the first information indicates that offloading is not allowed in the visited network.

[0399] Optionally, the processing unit 920 is configured to delete or update the offloading point according to the first information, including: the processing unit 920 is configured to update the offloading point according to the first service if the first information indicates that the first service is allowed to offload in the visited network.

[0400] Optionally, the transceiver 910 is further configured to send the updated tunnel information to the second session management network element.

[0401] Optionally, the transceiver 910 is configured to receive the first information from the second session management network element, the second session management network element being a network element deployed in a home network.

[0402] Optionally, the offloading point is an uplink classifier or a branching point.

[0403] In the second design, the apparatus 900 can be a second session management network element in the foregoing embodiments, or a component (e.g., a chip) of the second session management network element. The apparatus 900 can implement steps or processes performed by the second session management network element in the foregoing method embodiments, where the transceiver 910 is configured to perform the transceiving-related operations of the second session management network element in the foregoing method embodiments, and the processing unit 920 is configured to perform the processing-related operations of the second session management network element in the foregoing method embodiments.

[0404] In one possible implementation, the transceiver 910 is configured to obtain first information indicating whether offloading is allowed in a visited network, and send the first information to a first session management network element, where the first session management network element is a network element deployed in the visited network, and the second session management network element is a network element deployed in a home network.

[0405] Optionally, the transceiver 910 is further configured to send, to the first session management network element, first service, wherein the first service is service allowed to be offloaded in the visited network.

[0406] Optionally, the first information comprises an identifier of the first service, and the first information indicates that the first service is allowed to be offloaded in the visited network.

[0407] Optionally, the transceiver 910 is configured to obtain the first information, including: the transceiver 910 is configured to receive the first information from a policy control network element, wherein the policy control network element is a network element deployed in a home network; or the second session management network element locally configures the first information.

[0408] In a third design, the apparatus 900 can be a policy control network element in the foregoing embodiments, or a component (e.g., a chip) of the policy control network element. The apparatus 900 can implement steps or processes performed by the policy control network element in the foregoing method embodiments, wherein the transceiver 910 is configured to perform operations related to transceiving of the policy control network element in the foregoing method embodiments, and the processing unit 920 is configured to perform operations related to processing of the policy control network element in the foregoing method embodiments.

[0409] In a possible implementation, the transceiver 910 is configured to obtain first information, the first information indicating whether to allow offloading in a visited network; and the transceiver 910 is further configured to send, to a second session management network element, the first information, wherein the second session management network element and the policy control network element are network elements deployed in a home network.

[0410] Optionally, the transceiver 910 is further configured to send, to the second session management network element, first service, wherein the first service is service allowed to be offloaded in the visited network.

[0411] Optionally, the first information comprises an identifier of the first service, and the first information indicates that the first service is allowed to be offloaded in the visited network.

[0412] It should be understood that the specific process by which each unit performs the corresponding steps described above has been described in detail in the foregoing method embodiments, and thus will not be described here again for the sake of brevity.

[0413] It should also be understood that the apparatus 900 herein is embodied in the form of a functional block diagram. The term "unit" herein can refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor (for example, a shared processor, a dedicated processor, or a group processor, etc.) and a memory for executing one or more software or firmware programs, a combination of logic circuitry and / or other suitable components that support the described functions. In an optional example, those skilled in the art can understand that the apparatus 900 can be embodied as the first session management network element in the above-mentioned embodiments, and can be used to execute the processes and / or steps corresponding to the first session management network element in the above-mentioned method embodiments; or the apparatus 900 can be embodied as the second session management network element in the above-mentioned embodiments, and can be used to execute the processes and / or steps corresponding to the second session management network element in the above-mentioned method embodiments; or the apparatus 900 can be embodied as the policy control network element in the above-mentioned embodiments, and can be used to execute the processes and / or steps corresponding to the policy control network element in the above-mentioned method embodiments, and details are not repeated here to avoid repetition.

[0414] The apparatus 900 of each of the above-mentioned schemes has the function of implementing the corresponding steps performed by the core network network element (such as the first session management network element, or the second session management network element, or the policy control network element) in the above-mentioned methods. The function can be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above-mentioned functions; for example, the transceiver unit can be replaced by a transceiver (for example, the transmitting unit in the transceiver unit can be replaced by a transmitter, and the receiving unit in the transceiver unit can be replaced by a receiver), and other units, such as the processing unit, can be replaced by a processor, which respectively performs the transceiving operations and related processing operations in each of the method embodiments.

[0415] In addition, the transceiver unit 910 mentioned above can also be a transceiver circuit (for example, it can include a receiving circuit and a transmitting circuit), and the processing unit can be a processing circuit.

[0416] It should be noted that, Figure 9 The apparatus in the above-mentioned embodiments can be a network element or a device, or a chip or a chip system, for example, a system on chip (SoC). Among them, the transceiver unit can be an input / output circuit, a communication interface; the processing unit is a processor or microprocessor integrated on the chip or an integrated circuit. Here, no limitation is made.

[0417] As Figure 10As shown, the embodiments of the present application provide another device 1000 for communication. The device 1000 includes a processor 1010, which is configured to execute computer program or instructions stored in a memory 1020, or read data / signaling stored in the memory 1020, to perform the methods in the above method embodiments. Optionally, the processor 1010 is one or more.

[0418] Optionally, as shown, the device 1000 further includes a memory 1020, which is configured to store computer program or instructions and / or data. The memory 1020 can be integrated with the processor 1010, or can be separately arranged. Optionally, the memory 1020 is one or more. Figure 10

[0419] Optionally, as shown, the device 1000 further includes a transceiver 1030, which is configured to receive and / or send signals. For example, the processor 1010 is configured to control the transceiver 1030 to receive and / or send signals. Figure 10

[0420] As an option, the device 1000 is configured to implement the operations performed by the core network element in the above method embodiments.

[0421] For example, the processor 1010 is configured to execute computer program or instructions stored in the memory 1020, to implement the related operations of the first session management network element in the above method embodiments. For example, Figure 3 or Figure 4 the method performed by the first session management network element in the embodiments shown in any one of Figures 5 to 8 the method performed by the V-SMF in the embodiments shown in any one of

[0422] For another example, the processor 1010 is configured to execute computer program or instructions stored in the memory 1020, to implement the related operations of the second session management network element in the above method embodiments. For example, Figure 3 or Figure 4 the method performed by the second session management network element in the embodiments shown in any one of Figures 5 to 8 the method performed by the H-SMF in the embodiments shown in any one of

[0423] For another example, the processor 1010 is configured to execute computer program or instructions stored in the memory 1020, to implement the related operations of the policy control network element in the above method embodiments. For example, Figure 3 or Figure 4 the method performed by the policy control network element in the embodiments shown in any one of Figures 5 to 8 the method performed by the H-PCF in the embodiments shown in any one of

[0424] ​​It should be appreciated that a processor as mentioned in this application can be any known or future developed processor, and more particularly, any custom made or commercially available processor series (or any other processor orders) from any manufacturer.

[0425] It should also be appreciated that a memory as mentioned in this application can be any known or future developed memory, and more particularly, a memory unit of any type including, but not limited to, a volatile memory, a non-volatile memory, or a combination thereof. For example, the non-volatile memory can be a read-only memory (ROM), a programmable ROM (PROM), an erasable PROM (EPROM), an electrically EPROM (EEPROM), a flash memory, or the like. The volatile memory can be a random access memory (RAM), which can be used as external cache memory. By way of example and not limitation, RAM is available from many commercial vendors. For example, the RAM can include a static RAM (SRAM), a dynamic RAM (DRAM), a synchronous DRAM (SDRAM), a double data rate SDRAM (DDR SDRAM), an enhanced SDRAM (ESDRAM), a synchlink DRAM (SLDRAM), and a direct rambus RAM (DR RAM), etc.

[0426] It should be noted that when the processor is a general processor, a DSP, an ASIC, a FPGA, or other programmable logic device, a discrete gate or transistor logic, a discrete hardware component, the memory (storage module) can be integrated in the processor.

[0427] It should also be noted that the memory described herein is intended to include, but not limited to, these and any other suitable type of memory.

[0428] The embodiment of the present application further provides a computer readable storage medium, which has stored computer instructions for implementing the method executed by the core network element in each method embodiment.

[0429] For example, the computer program is executed by a computer, so that the computer can implement the method executed by the first session management network element in each method embodiment.

[0430] For another example, the computer program is executed by a computer, so that the computer can implement the method executed by the second session management network element in each method embodiment.

[0431] For another example, the computer program is executed by a computer, so that the computer can implement the method executed by the policy control network element in each method embodiment.

[0432] The embodiment of the present application further provides a computer program product, which contains instructions, and the instructions are executed by a computer to implement the method executed by the core network element in each method embodiment.

[0433] The embodiment of the present application further provides a communication system, which comprises one or more of the first session management network element, the second session management network element and the policy control network element.

[0434] The explanation and beneficial effects of the related content in any of the above provided devices can refer to the corresponding method embodiments provided above, and will not be repeated here.

[0435] In several embodiments provided by the present application, it should be understood that the disclosed apparatus and method can be implemented in other ways. For example, the device embodiments described above are only schematic. The division of the units is only a logical function division. There can be another division manner in actual implementation. For example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the units shown or discussed can be indirect coupling or communication connection through some interfaces, devices or units, and can be electrical, mechanical or other forms.

[0436] In the above embodiments, all or part of the embodiments can be implemented by software, hardware, firmware or any combination thereof. When implemented by software, all or part of the embodiments can be implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable apparatus. For example, the computer can be a personal computer, a server, a network device, etc. The computer instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions can be transferred from one website, computer, server or data center to another website, computer, server or data center through wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) manner. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. integrated with one or more available media sets. The available media can be a magnetic medium (such as a floppy disk, a hard disk, a magnetic tape), an optical medium (such as a DVD), or a semiconductor medium (such as a solid state disk (SSD), etc. For example, the foregoing available media includes but is not limited to: a variety of media that can store program codes such as a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc.

[0437] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art can easily think of changes or replacements within the technical range disclosed in the present application, which should be covered within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A method of communication, comprising: The method comprises: a first session management network element of a visited network receives first information from a second session management network element of a home network, the first information indicating whether to allow offloading in the visited network; the first session management network element determines a point of offloading in the visited network according to the first information; the first session management network element determines an offloading rule according to edge application server (EAS) deployment information of the visited network and the first information; the first session management network element sends the offloading rule to the point of offloading, the offloading rule being used for offloading packets to the visited network.

2. The method of claim 1, wherein, The EAS deployment information is locally configured, or the EAS deployment information is received from an application server.

3. The method according to claim 1 or 2, characterized in that, The EAS deployment information comprises a full domain name (FQDN) range corresponding to services deployed in the visited network, and the first information comprises a FQDN range corresponding to services allowed to offload in the visited network.

4. The method of claim 3, wherein, The offloading rule is used for offloading packets corresponding to FQDNs in an intersection part of the FQDN range corresponding to services allowed to offload in the visited network and the FQDN range corresponding to services deployed in the visited network to the visited network.

5. The method according to claim 1 or 2, characterized in that, The EAS deployment information comprises an Internet protocol (IP) range corresponding to services deployed in the visited network, and the first information comprises an IP range corresponding to services allowed to offload in the visited network.

6. The method of claim 5, wherein, The offloading rule is used for offloading packets corresponding to IPs in an intersection part of the IP range corresponding to services allowed to offload in the visited network and the IP range corresponding to services deployed in the visited network to the visited network.

7. The method according to claim 1 or 2, characterized in that, The method is applied to a home routing roaming scenario.

8. The method of claim 1 or 2, wherein, The point of offloading is: an uplink classifier or a branch point.

9. The method of claim 1 or 2, wherein, The method further comprises: the second session management network element of the home network obtaining the first information; the second session management network element sending the first information to the first session management network element.

10. The method of claim 5, wherein, The method further comprises: the second session management network element of the home network obtaining the first information; the second session management network element sending the first information to the first session management network element.

11. The method of claim 9, wherein, The second session management network element obtaining the first information comprises: the second session management network element receiving the first information from a policy control network element of the home network; or the second session management network element locally configuring the first information.

12. The method of claim 11, wherein, The method further comprises: the policy control network element of the home network obtaining the first information; the policy control network element sending the first information to the second session management network element.

13. An apparatus for communication, the apparatus comprising: The apparatus is a device of a visited network, and the apparatus comprises a transceiver and a processing unit, the transceiver is configured to receive first information from a second session management network element of a home network, the first information indicating whether to allow offloading in the visited network; the processing unit is configured to determine a point of offloading in the visited network according to the first information; the processing unit is further configured to determine an offloading rule according to edge application server (EAS) deployment information of the visited network and the first information; The transceiver unit is configured to send the traffic steering rule to the traffic steering point, the traffic steering rule being used to steer packets to the visited network.

14. The apparatus of claim 13, wherein, The EAS deployment information is configured locally, or the EAS deployment information is received from an application server.

15. The apparatus of claim 13 or 14, wherein, The EAS deployment information comprises a FQDN range corresponding to services deployed in the visited network, and the first information comprises a FQDN range corresponding to services allowed to be steered by the visited network.

16. The apparatus of claim 15, wherein, The traffic steering rule is used to steer packets corresponding to FQDNs in an intersection of the FQDN range corresponding to services allowed to be steered by the visited network and the FQDN range corresponding to services deployed in the visited network to the visited network.

17. The apparatus of claim 13 or 14, wherein, The EAS deployment information comprises an IP range corresponding to services deployed in the visited network, and the first information comprises an IP range corresponding to services allowed to be steered by the visited network.

18. The apparatus of claim 17, wherein, The traffic steering rule is used to steer packets corresponding to IPs in an intersection of the IP range corresponding to services allowed to be steered by the visited network and the IP range corresponding to services deployed in the visited network to the visited network.

19. The apparatus of claim 13 or 14, wherein, The apparatus is applied to a home routing roaming scenario.

20. The apparatus of claim 13 or 14, wherein, The traffic steering point is: An uplink classifier or a branching point.

21. An apparatus for communication, the apparatus comprising: Comprises: A processor configured to execute a computer program stored in a memory to cause the apparatus to perform the method of any one of claims 1-8.

22. The apparatus of claim 21, wherein, The apparatus further comprises the memory.

23. A computer-readable storage medium, characterized in that, The computer program is stored in the computer readable storage medium, and when the computer program is run on the computer, the computer is caused to perform the method of any one of claims 1-8.

24. A computer program product, characterised in that, The computer program product comprises instructions for performing the method of any one of claims 1-8.

25. A system for communication, characterized by Comprises a first session management network element and a second session management network element; The first session management network element is configured to perform the method of any one of claims 1-8; The second session management network element is configured to perform the method of any one of claims 9-11.

26. The system of claim 25, wherein, Further comprises a policy control network element configured to perform the method of claim 12.

Images