CN116709291A

CN116709291A - Communication method and device

Info

Publication number: CN116709291A
Application number: CN202210187084.9A
Authority: CN
Inventors: 朱方园; 李岩
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2022-02-28
Filing date: 2022-02-28
Publication date: 2023-09-05
Also published as: WO2023160394A1

Abstract

The application provides a communication method and device. The method may include: a session management network element in a home network receives first information corresponding to terminal equipment from a session management network element in a visited network, wherein the first information is used for indicating the deployment position of an Edge Application Server (EAS) in the visited network; and the session management network element in the home network acquires the EAS deployment information corresponding to the first information according to the first information. In the application, the VPLMN opens the EAS deployment information of the VPLMN to the HPLMN, thereby realizing the discovery of the EAS in the VPLMN in the HR roaming scene.

Description

Communication method and device

Technical Field

The present application relates to the field of communications, and more particularly, to a method and apparatus for communication.

Background

In an Edge Computing (EC) deployment scenario, some traffic may be served by multiple edge application servers (edge application server, EAS) deployed at the edge of the network. The multiple EAS may provide the same service and content, and most have different internet protocol (internet protocol, IP) addresses. When a User Equipment (UE) requests access to the service, the EC scenario requires it to access the available EAS that is close to the UE. Thus, the IP address of the appropriate EAS is important.

In some cases, the UE may leave the coverage of a home public land mobile network (public land mobile network, PLMN) (home PLMN, HPLMN), access a Visited Public Land Mobile Network (VPLMN) by Home Routing (HR) roaming, and be served by the VPLMN.

Disclosure of Invention

The application provides a communication method and a communication device, which are used for opening the EAS deployment information of a VPLMN to an HPLMN through the VPLMN so as to realize the discovery of the EAS in the VPLMN in an HR roaming scene.

In a first aspect, a method of communication is provided, which may be performed by a session management network element, or may also be performed by a component (e.g. a chip or a circuit) of the session management network element, which is not limited, and for convenience of description, will be described below with reference to a case where the method is performed by the session management network element in the home network.

The method may include: a session management network element in a home network receives first information corresponding to terminal equipment from a session management network element in a visited network, wherein the first information is used for indicating the deployment position of an Edge Application Server (EAS) in the visited network; and the session management network element in the home network acquires the EAS deployment information corresponding to the first information according to the first information.

Illustratively, the session management network element in the home network and the session management network element in the visited network serve the session of the terminal device. The session type of the terminal device is, for example, HR type.

The first information corresponding to the terminal device may be understood as the first information is determined according to the terminal device.

Based on the technical scheme, the session management network element in the home network receives first information corresponding to the terminal equipment from the session management network element in the visiting network, the first information can be used for indicating the deployment position of the EAS in the visiting network, and the session management network element in the home network acquires the EAS deployment information corresponding to the first information according to the first information. In this way, the session management network element in the home network can learn, based on the acquired EAS deployment information corresponding to the first information, which locations in the visited network are deployed with the edge application server that the terminal device may access (or can access). After the terminal equipment accesses the visiting network in the HR roaming mode, the session management network element in the home network knows which positions in the visiting network are provided with the edge application server which the terminal equipment can possibly access (or can access), so that the terminal equipment can be assisted to access the edge application service in the visiting network, the success rate of the terminal equipment accessing the edge application service in the visiting network is improved, and the discovery of the local EAS (namely the EAS in the VPLMN) in the HR roaming scene is realized. In addition, the session management network element in the home network receives the first information corresponding to the terminal device, so that the session management network element in the home network can not receive the first information corresponding to other terminal devices (such as terminal devices not served by the session management network element in the home network), signaling overhead caused by transmitting the first information can be reduced, and security of the EAS deployment information sent to the session management network element in the home network can be improved.

With reference to the first aspect, in some implementations of the first aspect, the first information corresponding to the terminal device includes: the first information is determined based on the location of the terminal device.

Based on the above technical solution, the session management network element in the home network may determine the first information corresponding to the terminal device according to the location of the terminal device. In this way, by considering the location of the terminal device, the session management network element in the visited network can be prevented from sending first information (such as the deployment location of EAS which is used for indicating by the first information and is the deployment location of EAS which is almost impossible to be accessed by the terminal device) which is not needed by some terminal devices to the session management network element in the home network, or sending first information corresponding to other terminal devices to the session management network element in the home network, which not only can assist the terminal device to access the edge application service in the visited network, but also can save signaling overhead and improve the security of the EAS deployment information sent to the session management network element in the home network.

With reference to the first aspect, in certain implementation manners of the first aspect, the first information is determined according to a location of the terminal device, including: the first information is used for indicating: of the deployment locations of EAS determined from the location of the terminal device, the deployment location of EAS that the terminal device is allowed to access.

Based on the above technical solution, the first information corresponding to the terminal device is used for indicating the deployment location of the EAS which allows the terminal device to access, among the deployment locations of the EAS determined according to the location of the terminal device. Thus, not only the position of the terminal equipment is considered, so that the signaling overhead can be saved and the security of the EAS deployment information sent to the session management network element in the home network can be improved, but also the authorization condition of the visiting network (such as providing the first information allowed by the visiting network to the session management network element in the home network) is considered, so that the requirement of the visiting network itself can be considered, and the network security can be improved.

With reference to the first aspect, in some implementations of the first aspect, the acquiring, by a session management network element in a home network, EAS deployment information corresponding to the first information according to the first information includes: a session management network element in a home network sends a request message to a data management network element in a visiting network, wherein the request message comprises first information, and the request message is used for requesting to acquire EAS deployment information corresponding to the first information; the session management network element in the home network receives the EAS deployment information corresponding to the first information from the data management network element in the visited network.

Based on the technical scheme, the session management network element in the home network can acquire the EAS deployment information corresponding to the first information from the data management network element in the visiting network, so that the session management network element in the home network can acquire the EAS deployment information corresponding to the first information, and the data management network element in the visiting network stores the EAS deployment information corresponding to the first information, thereby having high safety. For example, the session management network element in the home network may request EAS deployment information corresponding to the first information from the data management network element in the visited network through network release network elements (e.g., network release network elements in the home network and network release network elements in the visited network).

With reference to the first aspect, in some implementations of the first aspect, the acquiring, by a session management network element in a home network, EAS deployment information corresponding to the first information according to the first information includes: a session management network element in a home network sends a request message to a data management network element in the home network, wherein the request message comprises first information, and the request message is used for requesting to acquire EAS deployment information corresponding to the first information; a session management network element in the home network receives EAS deployment information corresponding to the first information from a data management network element in the home network.

Based on the technical scheme, the session management network element in the home network can acquire the EAS deployment information corresponding to the first information from the data management network element in the home network, so that the data management network element in the home network can store the EAS deployment information corresponding to the first information, the session management network element in the home network can directly acquire the EAS deployment information corresponding to the first information from the network element in the home network quickly, and signaling overhead can be saved. For example, the session management network element in the home network may request EAS deployment information corresponding to the first information from the data management network element in the home network through a network deployment network element in the home network.

With reference to the first aspect, in certain implementations of the first aspect, the request message further includes an identification of the visited network.

Based on the technical scheme, when the session management network element in the home network requests the EAS deployment information corresponding to the first information, the session management network element in the home network can carry the identification of the visited network, so that the visited network or the network element in the visited network can be conveniently identified, and the EAS deployment information in which visited network is requested is obtained.

With reference to the first aspect, in certain implementations of the first aspect, the method further includes: and the session management network element in the home network determines a Domain Name System (DNS) processing rule according to the EAS deployment information corresponding to the first information, wherein the DNS processing rule is used for processing the DNS message.

Based on the above technical solution, the session management network element in the home network determines a DNS processing rule according to the EAS deployment information corresponding to the first information, where the DNS processing rule may be used to process the DNS message.

With reference to the first aspect, in certain implementations of the first aspect, the method further includes: a session management network element in the home network receives an identification of the visited network from a session management network element in the visited network.

Based on the above technical solution, the session management network element in the home network may also receive the identifier of the visited network from the session management network element in the visited network, where the identifier of the visited network and the first information may be carried in the same signaling, or may also be carried in different signaling, without limitation.

With reference to the first aspect, in certain implementations of the first aspect, the method further includes: a session management network element in a home network discovers that the network element receives an IP address corresponding to the EAS and/or a domain name corresponding to the EAS from an edge application server, wherein the IP address corresponding to the EAS is the IP address of the EAS accessed by terminal equipment in a visiting network, and the domain name corresponding to the EAS is the domain name of the EAS accessed by the terminal equipment in the visiting network; the session management network element in the home network sends the IP address corresponding to the EAS and/or the domain name corresponding to the EAS to the session management network element in the visiting network.

Based on the technical scheme, the session management network element in the home network sends the IP address corresponding to the EAS and/or the domain name corresponding to the EAS to the session management network element in the visiting network, so that the session management network element in the visiting network can be triggered to execute flow guiding on the session roaming to the terminal equipment in the visiting network.

In a second aspect, a method of communication is provided, which may be performed by a session management network element, or may also be performed by a component (e.g. a chip or a circuit) of the session management network element, which is not limited, and for convenience of description, will be described below by taking a session management network element in a visited network as an example.

The method may include: the method comprises the steps that a session management network element in a visiting network determines first information corresponding to terminal equipment according to the position of the terminal equipment, wherein the first information is used for indicating the deployment position of an Edge Application Server (EAS) in the visiting network; the session management network element in the visited network sends the first information to the session management network element in the home network.

Based on the technical scheme, the session management network element in the visiting network sends first information corresponding to the terminal equipment to the session management network element in the home network, and the first information can be used for indicating the deployment position of the EAS in the visiting network. The session management network element in the visited network sends the first information corresponding to the terminal equipment to the session management network element in the home network, so that the session management network element in the visited network can not send the first information corresponding to other terminal equipment (such as terminal equipment not served by the session management network element in the home network) to the session management network element in the home network, signaling overhead caused by the transmission of the first information can be reduced, and security of the EAS deployment information sent to the session management network element in the home network can be improved. In addition, by sending the first information to the session management network element in the home network, if necessary, the session management network element in the home network may obtain EAS deployment information corresponding to the first information according to the first information. Therefore, the session management network element in the home network can learn which positions in the visited network are deployed with the edge application server which the terminal equipment may access (or can access) based on the acquired EAS deployment information corresponding to the first information. After the terminal equipment accesses the visiting network in the HR roaming mode, the session management network element in the home network knows which positions in the visiting network are provided with the edge application server which the terminal equipment can possibly access (or can access), so that the terminal equipment can be assisted to access the edge application service in the visiting network, the success rate of the terminal equipment accessing the edge application service in the visiting network is improved, and the discovery of the local EAS in the HR roaming scene is realized.

With reference to the second aspect, in some implementations of the second aspect, the first information is used to obtain EAS deployment information corresponding to the first information.

Based on the technical scheme, the session management network element in the home network can acquire the EAS deployment information corresponding to the first information according to the first information. Therefore, the session management network element in the home network can acquire which positions in the visited network are provided with the edge application server based on the acquired EAS deployment information corresponding to the first information, so that the terminal equipment is assisted to access the edge application service in the visited network, and the discovery of the local EAS in the HR roaming scene is realized.

With reference to the second aspect, in certain implementations of the second aspect, the first information is used to indicate: the deployment location of the EAS which allows the terminal device to access, among the deployment locations of EAS determined from the location of the terminal device; the session management network element in the visiting network determines first information corresponding to the terminal equipment according to the position of the terminal equipment, and the method comprises the following steps: the session management network element in the visiting network determines first information corresponding to the terminal equipment according to the position of the terminal equipment and policy information, wherein the policy information is used for indicating the deployment position of the EAS (electronic article surveillance) which is allowed to be sent to the home network by the visiting network.

With reference to the second aspect, in certain implementations of the second aspect, the first information is used to indicate: the deployment location of the EAS which allows the terminal device to access, among the deployment locations of EAS determined from the location of the terminal device; the session management network element in the visiting network determines first information corresponding to the terminal equipment according to the position of the terminal equipment, and the method comprises the following steps: a session management network element in the visiting network determines second information corresponding to the terminal equipment according to the position of the terminal equipment; a session management network element in a visiting network sends a request message to a policy control network element in the visiting network, wherein the request message comprises second information, and the request message is used for requesting the deployment position of the EAS (electronic article surveillance) which is allowed to be sent to a home network by the visiting network; the session management network element in the visited network receives first information from the policy control network element in the visited network, the first information being determined from the second information.

Wherein the second information and the first information may be the same, or the first information may be a subset of the second information.

Illustratively, the request message includes an identification of the home network.

With reference to the second aspect, in certain implementations of the second aspect, the method further includes: the session management network element in the visited network sends the identity of the visited network to the session management network element in the home network.

The second aspect and the advantageous effects of each possible design may refer to the description related to the first aspect, and are not repeated here.

In a third aspect, a method of communication is provided, which may be performed by a data management network element, or may also be performed by a component (e.g. a chip or a circuit) of the data management network element, which is not limited, and for convenience of description, will be described below by taking, as an example, the data management network element in the home network.

The method may include: the method comprises the steps that a data management network element in a home network receives a request message from a session management network element in the home network, wherein the request message comprises first information corresponding to terminal equipment, the first information is used for indicating the deployment position of an Edge Application Server (EAS) in a visiting network, and the request message is used for requesting to acquire the EAS deployment information corresponding to the first information; the data management network element in the home network sends the EAS deployment information corresponding to the first information to the session management network element in the home network.

Based on the technical scheme, the session management network element in the home network can acquire the EAS deployment information corresponding to the first information from the data management network element in the home network, so that the data management network element in the home network can store (or manage or can acquire) the EAS deployment information corresponding to the first information, and the session management network element in the home network can directly acquire the EAS deployment information corresponding to the first information from the network element in the home network quickly, thereby saving signaling overhead. For example, the session management network element in the home network may request EAS deployment information corresponding to the first information from the data management network element in the home network through a network deployment network element in the home network.

With reference to the third aspect, in some implementations of the third aspect, the request message further includes an identifier of the visited network, and the method further includes: and the data management network element in the home network determines the EAS deployment information corresponding to the first information according to the identification of the visiting network and the first information.

With reference to the third aspect, in certain implementations of the third aspect, the method further includes: the data management network element in the home network locally stores EAS deployment information corresponding to the first information.

Based on the technical scheme, the data management network element in the home network can store the EAS deployment information corresponding to the first information, so that the session management network element in the home network can directly acquire the EAS deployment information corresponding to the first information from the network element in the home network.

In a fourth aspect, a method of communication is provided, which may be performed by a core network element, or may also be performed by a component (such as a chip or a circuit) of the core network element, which is not limited, and for convenience of description, the following description will be given with an example in which the component is controlled by a policy in a visited network.

The method may include: the policy control network element in the visiting network receives a request message from a session management network element in the visiting network, wherein the request message comprises second information corresponding to the terminal equipment, and the request message is used for requesting the deployment position of the EAS (electronic article surveillance) which is allowed to be sent to the home network by the visiting network; the strategy control network element in the visit network determines the first information corresponding to the terminal equipment according to the second information; the policy control network element in the visited network sends first information from the policy control network element in the visited network to the session management network element in the visited network.

Based on the above technical solution, the session management network element in the visited network may determine the second information corresponding to the terminal device, and inquire (or request or query) the policy control network element in the visited network about the first information corresponding to the terminal device; the policy control network element in the visited network may determine the first information based on the second information (e.g., the second information is the same as the first information or the first information is a subset of the second information). Thus, not only the position of the terminal equipment is considered, so that the signaling overhead can be saved and the security of the EAS deployment information can be improved, but also the authorization condition of the visiting network is considered, so that the requirement of the visiting network can be considered, and the network security can be improved. In addition, the session management network element in the visiting network can dynamically send the first information to the policy control network element in the visiting network according to the actual situation, and the scheme is flexible.

With reference to the fourth aspect, in some implementations of the fourth aspect, the first information is used to obtain EAS deployment information corresponding to the first information.

With reference to the fourth aspect, in certain implementations of the fourth aspect, the first information is used to indicate: of the deployment locations of EAS determined from the location of the terminal device, the deployment location of EAS that the terminal device is allowed to access.

With reference to the fourth aspect, in certain implementations of the fourth aspect, the request message includes an identification of the home network.

In a fifth aspect, there is provided a communication apparatus for performing the method of any one of the possible implementations of the first to fourth aspects. In particular, the apparatus may comprise means and/or modules, such as a processing unit and/or a communication unit, for performing the method in any of the possible implementations of the first to fourth aspects.

In one implementation, the apparatus is a core network element (e.g., a session management element, a data management element, a network deployment element, and a policy control element). When the device is a core network element, the communication unit may be a transceiver, or an input/output interface; the processing unit may be at least one processor. Alternatively, the transceiver may be a transceiver circuit. Alternatively, the input/output interface may be an input/output circuit.

In another implementation, the apparatus is a chip, a system-on-chip, or a circuit for a core network element (e.g., a session management element, a data management element, a network deployment element, a policy control element). When the device is a chip, a system-on-chip or a circuit for a core network element, the communication unit may be an input/output interface, an interface circuit, an output circuit, an input circuit, a pin or a related circuit on the chip, the system-on-chip or the circuit; the processing unit may be at least one processor, processing circuit or logic circuit, etc.

In a sixth aspect, there is provided an apparatus for communication, the apparatus comprising: at least one processor configured to execute a computer program or instructions stored in a memory to perform a method according to any one of the possible implementations of the first to fourth aspects. Optionally, the apparatus further comprises a memory for storing a computer program or instructions. Optionally, the apparatus further comprises a communication interface through which the processor reads the computer program or instructions stored in the memory.

In one implementation, the apparatus is a core network element (e.g., a session management element, a data management element, a network deployment element, and a policy control element).

In another implementation, the apparatus is a chip, a system-on-chip, or a circuit for a core network element (e.g., a session management element, a data management element, a network deployment element, a policy control element).

In a seventh aspect, the present application provides a processor configured to perform the method provided in the above aspects.

The operations such as transmitting and acquiring/receiving, etc. related to the processor may be understood as operations such as outputting and receiving, inputting, etc. by the processor, or may be understood as operations such as transmitting and receiving by the radio frequency circuit and the antenna, if not specifically stated, or if not contradicted by actual function or inherent logic in the related description, which is not limited by the present application.

In an eighth aspect, a computer readable storage medium is provided, the computer readable storage medium storing program code for execution by a device, the program code comprising instructions for performing the method of any one of the possible implementations of the first to fourth aspects.

In a ninth aspect, there is provided a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of any one of the possible implementations of the first to fourth aspects.

In a tenth aspect, a communication system is provided, including one or more of the session management element in the home network, the session management element in the visited network, the policy control element in the visited network, the network deployment element in the home network, or the data management element (e.g., the data management element in the home network, and the data management element in the visited network) described above.

Drawings

Fig. 1 is a schematic diagram of a network architecture suitable for use with embodiments of the present application.

Fig. 2 is a schematic diagram of another network architecture suitable for use with embodiments of the present application.

Fig. 3 is a schematic diagram of a method 300 of communication provided by an embodiment of the present application.

Fig. 4 is a schematic diagram of a network architecture suitable for scheme a according to an embodiment of the present application.

Fig. 5 is a schematic diagram of a network architecture suitable for scheme B according to an embodiment of the present application.

Fig. 6 is a schematic diagram of another method 600 of communication provided by an embodiment of the present application.

Fig. 7 is a schematic flow chart diagram of a method 700 of communication provided by an embodiment of the present application.

Fig. 8 is a schematic flow chart diagram of another method 800 of communication provided by an embodiment of the present application.

Fig. 9 is a schematic flow chart diagram of another method 900 of communication provided by an embodiment of the present application.

Fig. 10 is a schematic diagram of a communication device 1000 according to an embodiment of the present application.

Fig. 11 is a schematic diagram of another communication apparatus 1100 according to an embodiment of the present application.

Fig. 12 is a schematic diagram of a chip system 1200 according to an embodiment of the present application.

Detailed Description

The technical scheme of the application will be described below with reference to the accompanying drawings.

The technical scheme provided by the application can be applied to various communication systems, such as: fifth generation (5th generation,5G) or New Radio (NR) systems, long term evolution (long term evolution, LTE) systems, LTE frequency division duplex (frequency division duplex, FDD) systems, LTE time division duplex (time division duplex, TDD) systems, and the like. The technical scheme provided by the application can also be applied to future communication systems, such as a sixth generation mobile communication system. The technical solution provided by the present application may also be applied to device-to-device (D2D) communication, vehicle-to-everything (V2X) communication, machine-to-machine (machine to machine, M2M) communication, machine type communication (machine type communication, MTC), and internet of things (internet of things, ioT) communication systems or other communication systems.

A network architecture suitable for the present application will be briefly described first with reference to fig. 1 and 2, as follows.

Fig. 1 is a schematic diagram of a network architecture suitable for use with embodiments of the present application. As shown in fig. 1, the network architecture is exemplified by Home Routing (HR) roaming.

A cellular mobile communication network of a certain standard of a certain operator may be referred to as public land mobile network (public land mobile network, PLMN). A PLMN subscribed to a User Equipment (UE) may be referred to as a home public land mobile network (public land mobile network, PLMN) (home PLMN, HPLMN) that characterizes a subscriber's home operator. When the UE leaves the coverage of the HPLMN for mobile or other reasons, the following conditions are met if a certain PLMN is present: 1) May cover the current location of the UE, 2) its operator has signed a roaming agreement with the operator of the HPLMN of the UE (roaming agreement, meaning some agreement between operators, content may include, for example: service and billing methods provided for subscribers of the opposite operator network, without limitation), the UE may access the PLMN, and the PLMN may be referred to as a Visited Public Land Mobile Network (VPLMN). The behavior of the UE to access the VPLMN may be referred to as roaming. Generally, roaming scenarios can be classified into local break-through (LBO) roaming and Home Routed (HR) roaming, which differ mainly in whether a session is to be connected to a user plane function (user plane function, UPF) of the home network. In the HR roaming scenario, a session (e.g., referred to as HR session) is connected to the UPF of the home network. HR session refers to a session of a UPF established when a user is located in a visited network and connected to a home network, in which traffic flow (traffic) carried in the HR session is sent from a UE to the UPF of the home network and then to a receiving end.

As shown in fig. 1, the network architecture may include, but is not limited to: based on network slice specific authentication and authorization functions (network slice specific authentication and authorization function, NSSAAF), network slice selection functions (network slice selection function, NSSF), authentication server functions (authentication server function, AUSF), unified data management (unified data management, UDM), policy control functions (policy control function, PCF), application functions (application function, AF), access and mobility management functions (access and mobility management function, AMF), session management functions (session management function, SMF), UE, radio access network devices, UPF, data Network (DN), etc.

The following briefly describes the network elements shown in fig. 1.

1. UE: a terminal device, access terminal, subscriber unit, subscriber station, mobile station, remote terminal, mobile device, user terminal, wireless communication device, user agent, or user equipment may be referred to as a terminal device.

The terminal device may be a device that provides voice/data to a user, e.g., a handheld device with wireless connection, an in-vehicle device, etc. Currently, some examples of terminals are: a mobile phone, tablet, laptop, palmtop, mobile internet device (mobile internet device, MID), wearable device, virtual Reality (VR) device, augmented reality (augmented reality, AR) device, wireless terminal in industrial control (industrial control), wireless terminal in unmanned (self driving), wireless terminal in teleoperation (remote medical surgery), wireless terminal in smart grid (smart grid), wireless terminal in transportation security (transportation safety), wireless terminal in smart city (smart city), wireless terminal in smart home (smart home), cellular phone, cordless phone, session initiation protocol (session initiation protocol, SIP) phone, wireless local loop (wireless local loop, WLL) station, personal digital assistant (personal digital assistant, PDA), handheld device with wireless communication function, computing device or other processing device connected to wireless modem, wearable device, terminal device in 5G network or terminal in future evolved land mobile communication network (public land mobile network), and the like, without limiting the application.

By way of example, and not limitation, in embodiments of the present application, the terminal device may also be a wearable device. The wearable device can also be called as a wearable intelligent device, and is a generic name for intelligently designing daily wear by applying wearable technology and developing wearable devices, such as glasses, gloves, watches, clothes, shoes and the like. The wearable device is a portable device that is worn directly on the body or integrated into the clothing or accessories of the user. The wearable device is not only a hardware device, but also can realize a powerful function through software support, data interaction and cloud interaction. The generalized wearable intelligent device includes full functionality, large size, and may not rely on the smart phone to implement complete or partial functionality, such as: smart watches or smart glasses, etc., and focus on only certain types of application functions, and need to be used in combination with other devices, such as smart phones, for example, various smart bracelets, smart jewelry, etc. for physical sign monitoring.

In addition, in the embodiment of the application, the terminal equipment can also be terminal equipment in an IoT system, and the IoT is an important component of the development of future information technology, and the main technical characteristics of the terminal equipment are that the articles are connected with a network through a communication technology, so that the man-machine interconnection and the intelligent network for the interconnection of the articles are realized.

It should be noted that, some air interface technology (such as NR or LTE technology) may be used to communicate between the terminal device and the access network device. The terminal equipment and the terminal equipment can also communicate with each other by adopting a certain air interface technology (such as NR or LTE technology).

In the embodiment of the present application, the device for implementing the function of the terminal device may be the terminal device, or may be a device capable of supporting the terminal device to implement the function, for example, a chip system or a chip, and the device may be installed in the terminal device. In the embodiment of the application, the chip system can be composed of chips, and can also comprise chips and other discrete devices.

2. (radio) access network (R) AN) device: the authorized users of the specific area may be provided with the functionality to access the communication network, which may specifically include wireless network devices in a third generation partnership project (3rd generation partnership project,3GPP) network or may include access points in a non-3GPP (non-3 GPP) network. The following description will be presented using AN apparatus for convenience of description.

AN device may employ different radio access technologies. There are two types of current radio access technologies: 3GPP access technologies (e.g., third generation (3rd generation,3G), fourth generation (4th generation,4G), or wireless access technologies employed in 5G systems) and non-3GPP (non-3 GPP) access technologies. The 3GPP access technology refers to an access technology conforming to the 3GPP standard specification, for example, access network devices in a 5G system are referred to as next generation base station nodes (next generation Node Base station, gNB) or RAN devices. Non-3GPP access technologies can include air interface technologies typified by an Access Point (AP) in Wireless Fidelity (wireless fidelity, wiFi), worldwide interoperability for microwave Access (worldwide interoperability for microwave access, wiMAX), code division multiple Access (code division multiple access, CDMA), and so forth. The AN device may allow interworking between the terminal device and the 3GPP core network using non-3GPP technology.

The AN device can be responsible for radio resource management, quality of service (quality of service, qoS) management, data compression, encryption, and other functions on the air interface side. The AN equipment provides access service for the terminal equipment, and further, the forwarding of control signals and user data between the terminal equipment and the core network is completed.

AN devices may include, for example, but are not limited to: macro base stations, micro base stations (also called small stations), radio network controllers (radio network controller, RNC), node bs (Node bs, NB), base station controllers (base station controller, BSC), base transceiver stations (base transceiver station, BTS), home base stations (e.g., home evolved NodeB, or home Node bs, HNB), base Band Units (BBU), APs in WiFi systems, wireless relay nodes, wireless backhaul nodes, transmission points (transmission point, TP), or transmission reception points (transmission and reception point, TRP), etc., as well as a gNB or transmission points (TRP or TP) in 5G (e.g., NR) systems, an antenna panel of one or a group (including multiple antenna panels) of base stations in 5G systems, or as well as network nodes constituting a gNB or transmission point, such as a Distributed Unit (DU), or a base station in next generation communication 6G systems, etc. The embodiment of the application does not limit the specific technology and the specific equipment form adopted by the AN equipment.

3. AMF: the method is mainly used for the functions of access control, mobility management, attachment and detachment and the like.

4. SMF: the method is mainly used for user plane network element selection, user plane network element redirection, internet protocol (internet protocol, IP) address allocation of terminal equipment and session management in a mobile network, such as session establishment, modification and release and quality of service (quality of service, qoS) control.

In the present application, for distinction, the SMF in the HPLMN is denoted as home SMF (H-SMF), and the SMF in the VPLMN is denoted as visited SMF (V-SMF).

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

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

6. PCF: the unified policy framework is mainly used for guiding network behaviors, and provides policy rule information and the like for control plane network elements (such as AMF, SMF and the like).

7. AF: the method is mainly used for providing services to the 3GPP network, such as interaction with PCF for policy control and the like.

8. Network slice selection function (network slice selection function, NSSF): the method is mainly used for network slice selection.

9. UDM: the method is mainly used for subscription data management of the UE, and comprises storage and management of the UE identification, access authorization of the UE and the like.

10. DN: the method is mainly used for an operator network for providing data services for the UE. Such as the Internet, a third party's service network, an IP Multimedia Services (IMS) network, etc.

11. AUSF: the method is mainly used for user authentication and the like.

As shown in fig. 2, the network architecture may include, but is not limited to: SMF (e.g., V-SMF and H-SMF), UE, UPF (e.g., V-UPF and H-UPF), PSA (e.g., L-PSA), domain name system (domain name system, DNS), PCF (e.g., H-PCF), edge application server discovery network element (edge application server discovery function, EASDF). In this architecture, domain name system (domain name system, DNS) messages may terminate at the EASDF of the HPLMN. Wherein the DNS message may terminate at the EASDF of the HPLMN, may indicate that the DNS message is processed by the EASDF of the HPLMN, or may indicate that the DNS message is destined for the EASDF of the HPLMN, or may indicate that the EASDF of the HPLMN receives the DNS message. The edge application server discovers network elements, which may also be called, for example, an edge application (service) discovery function, an application instance discovery function, an edge application instance discovery function, a multi-access edge computing (MEC) application (server) discovery function, and the like, without limitation.

EASDF, mainly used for assisting edge application server (edge application server, EAS) discovery, mainly functions include: the DNS message is processed according to the indication of the SMF. Among other things, processing DNS messages may include, but is not limited to: reporting the DNS message to the SMF, adding EDNS client-subnet option (ECS option) to the DNS query (DNS query), forwarding the DNS query to the DNS server (server), forwarding the DNS response (DNS response) to the UE, and the like. Among them, EDNS is a DNS extension mechanism (extended mechanisms for DNS, EDNS). In the present application, for distinction, a centralized DNS server deployed in the HPLMN is denoted as C-DNS server (centralize DNS server), and a local DNS server deployed in the VPLMN is denoted as L-DNS server (local DNS server).

The description of other network elements may be referred to in fig. 1, and will not be repeated here.

In the network architecture shown in fig. 1 or fig. 2, the network elements may communicate with each other through AN interface, for example, the UE connects to the AN device through a radio resource control (radio resource control, RRC) protocol, and the UE and the AN device communicate with each other through a Uu interface. Or may refer to the interface shown in fig. 1, and will not be described again here.

It should be understood that the network architecture shown above is merely illustrative, and the network architecture to which the embodiments of the present application are applied is not limited, and any network architecture capable of implementing the functions of the respective network elements described above is applicable to the embodiments of the present application. In addition, other network elements, such as network opening functions (network exposure function, NEF), may be included in the network architecture shown above, and the unified data storage network element (unified data repository, UDR) is not limited thereto. Among them, the NEF is mainly used to safely open services and capabilities provided by 3GPP network functions, etc., to the outside. In the present application, for distinction, the NEF in the HPLMN is designated as the home NEF (H-NEF), and the NEF in the VPLMN is designated as the visited NEF (V-NEF). In the present application, for distinction, the UDR in the HPLMN is denoted home UDR (H-UDR) and the UDR in the VPLMN is denoted visited UDR (V-UDR).

It should also be understood that the functions or network elements shown in fig. 1 or fig. 2, such as AMF, SMF, UPF, PCF, UDM, NSSF, AUSF, may be understood as network elements for implementing different functions, for example, may be combined into network slices as needed. The network elements may be independent devices, may be integrated in the same device to implement different functions, or may be network elements in hardware devices, or may be software functions running on dedicated hardware, or may be virtualized functions instantiated on a platform (for example, a cloud platform), where the specific form of the network elements is not limited by the present application.

It should also be understood that the above designations are merely intended to facilitate distinguishing between different functions and should not be construed as limiting the application in any way. The application does not exclude the possibility of using other designations in 6G networks as well as other networks in the future. For example, in a 6G network, some or all of the individual network elements may follow the terminology in 5G, possibly by other names, etc.

To facilitate an understanding of the embodiments of the present application, several basic concepts involved in the embodiments of the present application are briefly described. It should be understood that the basic concepts described below are described in the example of the basic concepts specified in the present protocol, but the embodiments of the present application are not limited to be applied to the existing systems. Therefore, the names appearing in the description of the existing system are all functional descriptions, and specific names are not limited, only indicate functions, and can be correspondingly extended to other systems, such as 6G or future communication systems.

1. EAS: an application may be represented, or a server application (e.g., social media software, AR, VR, etc.) may be deployed to run on an instance (instance) of a data network. EAS may also be referred to as any of the following: edge applications (servers), application instances, edge application instances, MEC applications (servers), or EAS functions, etc.

In an Edge Computing (EC) deployment scenario, some traffic may be serviced by multiple EAS deployed at the edge of the network. The multiple EAS's may provide the same service and content, and most have different IP addresses. In the EC scenario, when a UE accesses the service, it may be requested to access an available EAS that is close to the UE.

EAS can be deployed in a local data network (local DN) that ensures that the UE can access edge traffic normally by selecting a UPF closer to the local DN to establish a transmission path for the UE.

2. EAS deployment information (EAS deployment information): including information about the deployment of EAS in the edge network.

As an example, the EAS deployment information may include one or more of the following: DNN, single-network-slice selection assistance information (single-network slice selection assistance information, S-nsai), external group identifier (external group identifier)/internal group identifier (internal group identifier), application identification (application ID, appID), full domain name (full qualified domain name, FQDN), DNS server information (DNS Server Information), EAS IP address range information (EAS IP address range information). For a description of the parameters, reference may be made to table 1.

TABLE 1

The terms related to the present application are briefly described above, and will not be repeated in the following examples.

As described above, the UE may access the VPLMN by means of HR roaming and be served by the VPLMN. If the UE accesses through HR roaming, for the edge application service, on one hand, since the session anchor point is in the HPLMN, the distance between the application server (application server, AS) IP (e.g. EAS IP) returned by the DNS server deployed in the HPLMN and the H-UPF is short, but the distance between the application server and the UE is possibly long, which causes the UE to access the path detour of the EAS, and the user experience is poor; on the other hand, if EAS deployed in the VPLMN is used, it is difficult for the UE to acquire EAS information deployed in the VPLMN according to the existing edge service discovery mechanism.

The application provides a scheme, which realizes the discovery of the EAS in the VPLMN in the HR roaming scene by opening the EAS deployment information of the VPLMN to the HPLMN (or V-SMF to H-SMF). For example, a session management network element in the HPLMN receives first information corresponding to the terminal device from the VPLMN, the first information being used to indicate a deployment location of EAS in the VPLMN; the HPLMN acquires the EAS deployment information corresponding to the first information, so that the HPLMN can know which positions in the VPLMN are deployed with the edge application server. The HPLMN obtains deployment information of EAS that the terminal device may access (or may access) based on the first information corresponding to the terminal device, so, after the terminal device accesses the VPLMN through the HR roaming mode, the session management network element in the HPLMN knows which locations in the VPLMN are deployed with the edge application server that the terminal device may access, so that the terminal device may be assisted to access the edge application service in the VPLMN, and discovery of local EAS (i.e. EAS in the VPLMN) in the HR roaming scenario is achieved. In addition, the HPLMN receives the first information corresponding to the terminal device, and may not need to receive the first information corresponding to other terminal devices (such as the terminal device not served by the session management network element in the HPLMN), which not only reduces signaling overhead caused by transmitting the first information, but also improves security of EAS deployment information sent to the session management network element in the home network. Therefore, the application can be used for well solving the discovery of the local EAS in the HR roaming scene.

In embodiments of the present application, reference is made to local EAS discovery many times, it being understood that local EAS discovery means discovery of EAS of a visited network (e.g., VPLMN) unless specifically indicated.

It will be appreciated that the term "and/or" is merely one association relationship describing the associated object, and means that three relationships may exist, for example, a and/or B may mean: a exists alone, A and B exist together, and B exists alone. In addition, the character "/" herein generally indicates that the front and rear associated objects are an "or" relationship.

The method of communication provided by the embodiment of the present application will be described in detail below with reference to the accompanying drawings. The embodiments provided in the present application may be applied to the network architecture shown in fig. 1 or fig. 2, and are not limited thereto.

Fig. 3 is a schematic diagram of a method 300 of communication provided by an embodiment of the present application. The method 300 may include the following steps.

The session management network element in the home network receives first information corresponding to the terminal device from the session management network element in the visited network, the first information being used to indicate a deployment location of EAS in the visited network 310.

A visited network indicates a network, such as a VPLMN, to which the terminal device has access after leaving the home network. Home network, representing a network subscribed to by the terminal device, such as the HPLMN. The following description will mainly take the visited network as VPLMN and the home network as HPLMN as an example.

A session management network element in the home network represents a session management network element deployed in the home network, such as a session management network element deployed in the HPLMN. Similarly, a session management network element in the visited network means a session management network element deployed in the visited network, such as a session management network element deployed in the VPLMN. For simplicity and ease of understanding, the following description will be given by taking a session management network element in the home network as an H-SMF and a session management network element in the visited network as a V-SMF as an example.

The first information corresponding to the terminal device may be used to indicate: the deployment location of the EAS visited by the terminal device in the visited network. As an example, the first information may be in the form of a data network access identifier (DN access identifier, DNAI). For example, the first information corresponding to the terminal device is N DNAIs, where N is an integer greater than 1 or equal to 1. For example, in step 310, the H-SMF receives N DNAI from the V-SMF. The manner of determining the first information corresponding to the terminal device will be described in detail later.

And 320, the session management network element in the home network acquires the EAS deployment information corresponding to the first information according to the first information.

For example, in step 310, the H-SMF receives N DNAI from the V-SMF, and in step 320, the H-SMF obtains the EAS deployment information corresponding to the N DNAI according to the N DNAI.

Based on the technical scheme, the session management network element in the home network receives first information corresponding to the terminal equipment from the session management network element in the visiting network, the first information can be used for indicating the deployment position of the EAS allowed to access in the visiting network, and the session management network element in the home network acquires the EAS deployment information corresponding to the first information based on the first information. In this way, the session management network element in the home network can learn which locations in the visited network have edge application servers deployed that the terminal device is likely to access (or can access). After the terminal equipment accesses the visiting network in the HR roaming mode, the session management network element in the home network knows which positions in the visiting network are provided with the edge application servers which the terminal equipment possibly accesses, so that the terminal equipment can be assisted to access the edge application service in the visiting network, the success rate of the terminal equipment accessing the edge application service in the visiting network is improved, and the discovery of the local EAS in the HR roaming scene is realized. In addition, the session management network element in the home network may not need to receive the first information corresponding to other terminal devices (such as the terminal devices not served by the session management network element in the home network), so that not only signaling overhead caused by transmitting the first information can be reduced, but also security of EAS deployment information sent to the session management network element in the home network can be improved.

For brevity and convenience of description, the first information corresponding to the terminal device will be hereinafter referred to as information #a.

As previously described, information #a may be used to indicate the deployment location of EAS visited by the terminal device in the visited network. In one possible implementation, the information #a is determined according to the location of the terminal device. The position of the terminal equipment is used for reflecting the position of the terminal equipment. For example, the location of the terminal device may be represented by a tracking area identity (tracking area identify, TAI). As another example, the location of the terminal device may be represented by a cell identification (cell ID). As another example, the location of the terminal device may be represented by the geographic location of the terminal device (e.g., as represented by a coordinate system such as latitude and longitude). For ease of understanding and description, the following is mainly described by way of example with the location of the terminal device being denoted by TAI. It will be appreciated that the TAI below may be replaced by other information that is capable of reflecting the location of the terminal device.

Optionally, before step 310, the method 300 further comprises: the session management network element in the visited network determines the information #a. In one possible implementation, the V-SMF determines the information #a according to the location of the terminal device. For example, the information #A is N DNAI, and the V-SMF may determine the N DNAI according to the location (e.g., TAI) of the terminal equipment.

The manner of determining the N DNAIs by using the session management network element in the visited network as V-SMF and the information #a as N DNAIs, which may include the following several implementations.

In a first possible implementation, the V-SMF determines N DNAIs according to the location of the terminal device.

For example, the V-SMF may determine, according to the S-nsai and DNN corresponding to the session, that the DNAI that the current location of the terminal device may (or can, or will, or is likely to) access is N DNAIs. The V-SMF determines the N DNAIs and sends the N DNAIs to the H-SMF.

Based on the first possible implementation manner described above, the V-SMF may determine the information #a (i.e., N DNAIs) according to the location of the terminal device. Thus, by considering the location of the terminal device, it is possible to avoid sending some unnecessary information #a (such as deployment location of EAS which the terminal device is almost unlikely to access) of the terminal device to the H-SMF, or to avoid sending information #a corresponding to other terminal devices to the H-SMF, which not only saves signaling overhead, but also improves security of EAS deployment information sent to the H-SMF.

In a second possible implementation, the V-SMF determines N DNAIs according to the location of the terminal device and policy information.

For example, the V-SMF may configure and store the policy information, which the V-SMF may directly read locally when using the policy information; for another example, the V-SMF may configure the policy information and store the policy information by other core network elements (e.g., V-PCFs) in the VPLMN, and when using the policy information, the V-SMF may obtain the policy information from the other core network elements.

Wherein the policy information may be used to indicate a deployment location of EAS that allows the VPLMN to transmit to the HPLMN. For example, policy information may be used to indicate which DNAIs within the VPLMN may be open (or transmittable) to other PLMNs. The present invention may be embodied in the form of DNAI list (list) and/or PLMN list, or may be embodied in other manners, without limitation.

One possible scenario, the policy information includes DNAI that the VPLMN allows (or authorizes) to be opened to other PLMNs. Through the policy information, it is directly known which DNAIs within the VPLMN may be opened to other PLMNs. As an example, tables 2 and 3 show forms of policy information applicable to this case.

TABLE 2

PLMN ID	VPLMN allows open DNAI
		PLMN#1	DNAI#1，DNAI#2
PLMN#2	DNAI#2，DNAI#3
		PLMN#3	DNAI#1

TABLE 3 Table 3

Taking Table 2 as an example, the VPLMN may open DNAI#1 and DNAI#2 to PLMN#1, the VPLMN may open DNAI#2 and DNAI#3 to PLMN#2, and the VPLMN may open DNAI#1 to PLMN#3. The PLMN ID in table 2 may be, for example, the ID of the HPLMN. For example, if the V-SMF knows that the HPLMN is plmn#1, it can be known based on table 2 that the VPLMN can open dnai#1 and dnai#2 to the HPLMN, i.e., N DNAIs including dnai#1 and dnai#2.

Taking table 3 as an example, VPLMN may be open to plmn#1, plmn#2, plmn#3: dnai#1, dnai#2, dnai#3. The PLMN ID in table 3 may be, for example, the ID of the HPLMN. For example, if the V-SMF knows that the HPLMN is PLMN #3, then based on table 3 it can be known that the VPLMN can be opened to the HPLMN: dnai#1, dnai#2, and dnai#3, i.e., N DNAIs include: dnai#1, dnai#2, and dnai#3.

The application is not limited in the manner in which the V-SMF determines the HPLMN. As an example, the V-SMF may identify the HPLMN based on the identity of the network element deployed in the HPLMN (e.g., the identity of the H-SMF, or the identity of other network elements, etc.). In one possible way, the V-SMF receives an identification of the H-SMF (e.g., the H-SMF ID, without limitation of the application) from the AMF, and the V-SMF determines the identification of the HPLMN, i.e., determines the HPLMN, based on the identification of the H-SMF. In this regard, the description thereof will not be repeated.

It will be appreciated that tables 2 and 3 are merely illustrative and not limiting in this regard, and that any variations belonging to tables 2 or 3 are applicable to the present application. For example, the PLMN IDs in table 2 or table 3 may be replaced with SMF IDs, for example, plmn#1 may be replaced with one or more SMF IDs (i.e., the IDs of one or more SMFs corresponding to plmn#1). As another example, PLMN IDs in table 2 or table 3 above correspond to a greater number of DNAIs.

It will also be appreciated that the above description is mainly given by way of example of policy information including DNAI that the VPLMN allows to be opened to other PLMNs, and embodiments of the present application are not limited thereto. For example, the policy information includes DNAI that the VPLMN prohibits opening to other PLMNs, so that by using the policy information, it can be known which DNAI in the VPLMN prohibits opening to other PLMNs, and further it can be known that DNAI in the VPLMN other than the above-mentioned DNAI that prohibits opening can be opened to other PLMNs.

Based on a second possible implementation manner, the V-SMF may determine second information corresponding to the terminal device according to the location of the terminal device, and further determine the first information according to the second information and the policy information. For brevity and convenience of description, the second information corresponding to the terminal device will be hereinafter referred to as information #b.

Information #b indicating a deployment location of EAS that the determined terminal device may (or is capable of, or is about to, or is likely to) access in the visited network based on the location of the terminal device. As an example, the form of information #b may be DNAI. For example, the information #b is M DNAIs, M is an integer greater than or equal to 1, and M is greater than or equal to N. Where N DNAIs may be all DNAIs of the M DNAIs (i.e., M is equal to N), or N DNAIs may be part of the M DNAIs (i.e., M is greater than N).

The following is an exemplary explanation taking DNAI as an example in the form of information #a and information #b.

For example, the V-SMF may determine, according to the S-nsai and DNN corresponding to the session, that DNAI accessible to the current location of the terminal device is M DNAIs; further, the V-SMF determines N DNAIs from the M DNAIs according to the policy information described above.

Assuming that V-SMF knows that HPLMN is PLMN #1, V-SMF determines M DNAIs as: dnai#1, dnai#2, and dnai#3. For example, taking table 2 as an example, the PLMN ID in table 2 may be the ID of the HPLMN, and it can be known based on table 2 that the VPLMN may open dnai#1 and dnai#2 to plmn#1, and thus, the V-SMF determines that N DNAIs including part of DNAI in M DNAIs, i.e., N DNAIs including dnai#1 and dnai#2, and does not include dnai#3 in M DNAIs. For another example, taking table 3 as an example, the PLMN ID in table 3 may be the ID of the HPLMN, and based on table 3, it can be known that the VPLMN may be opened to PLMN # 1: dnai#1, dnai#2, dnai#3, the V-SMF thus determines that N DNAIs are the M DNAIs, i.e., the N DNAIs include: dnai#1, dnai#2, dnai#3.

Based on the second possible implementation manner, the V-SMF may determine the information #a (i.e., N DNAIs) according to the location of the terminal device and policy information. Thus, not only the position of the terminal equipment is considered, so that the signaling overhead can be saved and the security of the EAS deployment information sent to the H-SMF can be improved, but also the authorization condition of the VPLMN (such as providing the VPLMN-allowed DNAI to the H-SMF) is considered, so that the requirement of the VPLMN itself can be considered, and the network security can be improved.

In a third possible implementation, the V-SMF determines M DNAIs (i.e., information #b) from the location of the terminal device, and queries N DNAIs from the V-PCF based on the M DNAIs.

For example, the V-PCF may store DNAI (as in the form shown in table 2 or table 3) that is allowed to be opened to other PLMNs, which may be directly read locally when needed for use; for another example, other core network elements (e.g., V-UDR) in the VPLMN store DNAI that are allowed to be opened to other PLMNs, and the V-PCF may obtain from the other core network elements when needed for use.

For example, V-SMF determines M DNAIs based on the location of the terminal device; the V-SMF sends a request message to the V-PCF, the request message including M DNAIs, the request message requesting a deployment location of EAS that allows the VPLMN to send to the HPLMN. Specifically, the request message is used to request DNAI of the M DNAIs that may be opened to the HPLMN (or H-SMF).

Assuming that the HPLMN is PLMN #1, the v-SMF determines M DNAIs as: dnai#1, dnai#2, and dnai#3, the V-SMF sends a request message to the V-PCF, the request message including M DNAIs (i.e., dnai#1, dnai#2, and dnai#3). For example, taking table 2 as an example, the PLMN ID in table 2 may be the ID of the HPLMN, and based on table 2, it can be known that the VPLMN may open dnai#1 and dnai#2 to plmn#1, and thus the V-PCF determines that N DNAIs to include part of DNAI in M DNAIs, i.e., N DNAIs to include dnai#1 and dnai#2, and does not include dnai#3 in M DNAIs; the V-PCF may send dnai#1 and dnai#2 to the V-SMF. For another example, taking table 3 as an example, the PLMN ID in table 3 may be the ID of the HPLMN, and based on table 3, it can be known that the VPLMN may be opened to PLMN # 1: dnai#1, dnai#2, dnai#3, the V-PCF determines that N DNAIs are the M DNAIs, i.e., the N DNAIs include: dnai#1, dnai#2, dnai#3; the V-PCF may send to the V-SMF: dnai#1, dnai#2, dnai#3, or V-PCF may send acknowledgement information to V-SMF indicating that M DNAIs in the request message are all allowed to be open (i.e., N DNAIs M DNAIs). As an example, if N DNAIs the same as M DNAIs, the V-PCF may send smaller bits of acknowledgement information (e.g., 1 bit of acknowledgement information) to the V-SMF, which may save signaling overhead.

Optionally, the query message also includes an HPLMN ID (or H-SMF ID) that identifies the HPLMN. In a possible scenario, the V-PCF stores DNAI that is allowed to be opened to other PLMNs and DNAI that is allowed to be opened to other PLMNs is the same (example shown in table 3); the V-PCF receives the request message from the V-SMF, wherein the request message comprises M DNAI, the V-PCF determines DNAI (namely N DNAI) allowed to be opened to other PLMN in the M DNAI, and sends the N DNAI to the V-SMF. Another possible scenario is that the V-PCF stores DNAIs allowed to be opened to other PLMNs, and that the DNAIs allowed to be opened to other PLMNs are not exactly the same (as in the example shown in table 2); the V-PCF receives a request message from the V-SMF, wherein the request message comprises M DNAI and HPLMN IDs; the V-PCF determines the HPLMN from the HPLMN ID in the request message and determines the DNAI (i.e., N DNAIs) of the M DNAIs allowed to be opened to the HPLMN and sends the N DNAIs to the V-SMF.

Based on the third possible implementation manner, the V-SMF may determine the information #b (i.e., M DNAIs) according to the location of the terminal device, and query (or request, or query) the V-PCF as to which DNAIs of the M DNAIs openable (or transmittable) to the HPLMN. Thus, not only the position of the terminal equipment is considered, so that the signaling overhead can be saved and the security of the EAS deployment information sent to the H-SMF can be improved, but also the authorization condition of the VPLMN (such as providing the VPLMN-allowed DNAI to the H-SMF) is considered, so that the requirement of the VPLMN itself can be considered, and the network security can be improved. In addition, the V-SMF may dynamically send a request to the V-PCF for which DNAIs of the M DNAIs openable (or transmittable) to the HPLMN according to the actual situation, and the scheme is flexible.

The manner in which the V-SMF determines the N DNAIs is described above in connection with three implementations, it being understood that the implementations described above are exemplary illustrations, and any variations falling within the three implementations described above are applicable to embodiments of the present application. The scheme of H-SMF acquiring the deployment information of the EAS corresponding to the information #A is described below.

Taking a session management network element in a home network as an H-SMF, optionally, the H-SMF acquires the EAS deployment information corresponding to the information #A, which can comprise the following two schemes:

scheme a: the H-SMF acquires the EAS deployment information corresponding to the information #A from the VPLMN;

scheme B: the H-SMF obtains the EAS deployment information corresponding to the information #A from the HPLMN.

These two schemes are described in detail below.

Scheme a, H-SMF obtains EAS deployment information corresponding to information #a from VPLMN.

Under this scenario a, a possible scenario, a data management network element in the VPLMN stores EAS deployment information in the VPLMN (EAS deployment information in the VPLMN). Thus, after the H-SMF receives the information #A, the data management network element in the VPLMN can inquire and acquire the EAS deployment information corresponding to the information #A.

In the embodiment of the application, the data management network element represents a network element which can be used for managing and/or storing the EAS deployment information corresponding to the information #a, or a network element which is used for providing the EAS deployment information corresponding to the information #a. As an example, the data management network element comprises for example UDR and/or UDM. It will be appreciated that the naming of the data management network element does not limit the scope of the embodiments of the present application, for example, when the data management network element is a UDR, the data management network element may also be referred to as a data storage network element or a unified data storage network element. The data management network element in the VPLMN means a data management network element deployed in the VPLMN, such as a UDR (i.e. V-UDR) deployed in the VPLMN and/or a UDM (i.e. V-UDM) deployed in the VPLMN.

Taking the example of the information #a in the form of DNAI, EAS deployment information in a VPLMN (e.g., a data management network element in the VPLMN) may exist in the form of table 4, as an example.

TABLE 4 Table 4

DNAI	EAS deployment information
		DNAI#1	EAS deployment information #1
DNAI#2	EAS deployment information #2
		DNAI#3	EAS deployment information #3

Taking Table 4 as an example, DNAI in Table 4 is DNAI in VPLMN. For example, the information #a includes dnai#1, dnai#2, and dnai#3, and it can be known from table 4 that EAS deployment information of dnai#1 is EAS deployment information#1, EAS deployment information of dnai#2 is EAS deployment information#2, and EAS deployment information of dnai#3 is EAS deployment information#3.

It should be understood that table 4 is merely illustrative, and not limiting, and any variations belonging to table 4 are applicable to the present application. For example, a list of PLMN IDs may be added to table 4 to indicate PLMNs corresponding to the DANI. For another example, a greater number of DNAIs may also be included in table 4.

Based on scheme a, in one possible implementation manner, the H-SMF may query the data management network element in the VPLMN for EAS deployment information corresponding to the acquired information #a through interaction between the H-NEF and the V-NEF.

Taking the data management network element in the VPLMN as V-UDR, for example, after the H-SMF receives N DNAI, the H-NEF can send a request message, wherein the request message comprises N DNAI; the H-NEF forwards the request message to the V-NEF; the V-UDR stores the EAS deployment information in the VPLMN (as shown in table 4), and the V-NEF inquires the EAS deployment information corresponding to the N DNAI from the V-UDR; further, the V-NEF transmits the EAS deployment information corresponding to the N DNAI to the H-NEF; the H-NEF forwards the EAS deployment information corresponding to the N DNAI to the H-SMF, and the H-SMF inquires and acquires the EAS deployment information corresponding to the N DNAI from the V-UDR.

Optionally, the request message also includes a VPLMN ID, which may be used to identify the VPLMN, or may be used to determine to identify the NEF (i.e., V-NEF) in the VPLMN. For example, upon receipt of a request message from the H-SMF, the H-NEF may identify the VPLMN based on the VPLMN ID in the request message, and determine the V-NEF of the VPLMN, thereby forwarding the request message to the V-NEF. It will be appreciated that the VPLMN ID may no longer be carried when the H-NEF sends the request message to the V-NEF, in order to save signalling overhead.

It is to be understood that the above-described implementations are illustrative and that embodiments of the present application are not limited thereto. For example, the H-SMF may query the data management network element in the VPLMN for EAS deployment information corresponding to the acquisition information #a through other network elements, or the H-SMF may query the data management network element in the VPLMN directly for EAS deployment information corresponding to the acquisition information #a.

Scheme B, H-SMF obtains the EAS deployment information corresponding to information #A from HPLMN.

Under this scenario B, a data management network element in the HPLMN stores EAS deployment information in the VPLMN, as a possible scenario. Thus, after the H-SMF receives the information #A, the H-UDR can inquire and acquire the EAS deployment information corresponding to the information #A. The data management network element in the HPLMN means a data management network element deployed in the HPLMN, such as a UDR (i.e. H-UDR) deployed in the HPLMN and/or a UDM (i.e. H-UDM) deployed in the HPLMN.

Taking the example of information #a in the form of DNAI, EAS deployment information in the HPLMN (e.g., a data management network element in the HPLMN) may exist in the form of table 5, as an example.

TABLE 5

Taking table 5 as an example, the PLMN IDs in table 5 may be IDs of VPLMNs and the DNAIs may be DNAIs in the corresponding VPLMNs. For example, the information #a includes dnai#1, dnai#2, and dnai#3, and it can be known from table 5 that EAS deployment information of dnai#1 is EAS deployment information#1, EAS deployment information of dnai#2 is EAS deployment information#2, and EAS deployment information of dnai#3 is EAS deployment information#3. For another example, the information #a includes dnai#4, dnai#5, and dnai#6, and it can be known from table 5 that EAS deployment information of dnai#4 is EAS deployment information#4, EAS deployment information of dnai#5 is EAS deployment information#5, and EAS deployment information of dnai#6 is EAS deployment information#6.

It should be understood that table 5 is merely exemplary, and is not limited in this regard, and any variations belonging to table 5 are applicable to the present application. For example, the DNAI in table 5 may be DNAI that the corresponding PLMN allows to be opened to other PLMNs, for example, PLMN #1 allows to be opened to other PLMNs includes: dnai#1, dnai#2, and dnai#3. For another example, a greater number of DNAIs may also be included in table 5. For another example, table 5 may also include adding a list of PLMN IDs to indicate which PLMNs the corresponding PLMNs are allowed to open to DNAI.

Based on scheme B, in one possible implementation manner, the H-SMF may query and obtain EAS deployment information corresponding to the information #a from the data management network element in the HPLMN through the H-NEF.

Taking the data management network element in the HPLMN as H-UDR, for example, after the H-SMF receives N DNAI, it can send a request message to the H-NEF, where the request message includes N DNAI; the H-UDR stores the EAS deployment information corresponding to N DNAI (as shown in table 5), and the H-NEF inquires the EAS deployment information corresponding to the N DNAI from the H-UDR; further, the H-NEF returns the EAS deployment information corresponding to the N DNAI to the H-SMF, and the H-SMF inquires and acquires the EAS deployment information corresponding to the N DNAI from the H-UDR.

Optionally, the request message further comprises a VPLMN ID, which may be used to identify the VPLMN. For example, the H-UDR stores EAS deployment information in multiple PLMNs (e.g., table 5), and the H-UDR may identify the VPLMN based on the VPLMN ID in the request message, thereby determining EAS deployment information corresponding to N DNAIs in the VPLMN.

It is to be understood that the above-described implementations are illustrative and that embodiments of the present application are not limited thereto. For example, the H-SMF may query the data management network element in the HPLMN for EAS deployment information corresponding to the acquisition information #a through other network elements, or the H-SMF may query the data management network element in the HPLMN directly for EAS deployment information corresponding to the acquisition information #a.

As an example, scheme B may be used in a scenario where there is a strong trust relationship between the HPLMN and the VPLMN.

The above description has been made of two schemes related to the EAS deployment information corresponding to the H-SMF acquisition information #a.

Optionally, the method 300 further comprises: the H-SMF determines a DNS processing rule (DNS handling rule) based on the EAS deployment information corresponding to the first information (e.g., N DNAI).

Wherein DNS processing rules can be used to process DNS messages, such as DNS messages associated with a terminal device. For example, DNS processing rules may be used to process DNS query messages.

As an example, DNS processing rules may include one or more of the following information: FQDN range, ECS option, local DNS (L-DNS) server address, DNS forwarding rules.

Wherein ECS option can be used to characterize the location information of the UE.

The DNS forwarding rule may also be referred to as a forwarding rule, or a data plane forwarding rule, may be used by the EASDF to perform corresponding processing on a DNS message from the UE. For example, when the FQDN contained in the DNS query sent by the UE matches the FQDN range in the DNS processing rule, the EASDF adds ECS option to the DNS query based on the DNS forwarding rule. For another example, when the FQDN included in the DNS query sent by the UE matches the FQDN range in the DNS processing rule, the EASDF forwards the DNS query (e.g., the DNS query after adding the ECS option) to the DNS server based on the DNS forwarding rule.

With respect to the related schemes of DNS processing rules, reference may be made to the prior art, which is not limited by embodiments of the present application.

Optionally, the method 300 further comprises: the H-SMF sends an IP address and/or domain name (e.g., FQDN) to the V-SMF, triggering the V-SMF to perform traffic steering (traffic steering) on the HR session within the VPLMN. The IP address is an IP address corresponding to EAS, and represents an IP address of EAS accessed by the terminal device in the VPLMN. The domain name, which is the domain name corresponding to EAS, represents the domain name of EAS accessed by the terminal device in the VPLMN.

For example, the H-SMF receives an EAS IP address and/or FQDN from the EASDF; the H-SMF sends the EAS IP address and/or FQDN to the V-SMF; the V-SMF selects a splitting point located in the visited network and/or an anchor UPF deployed in the VPLMN for a session of the terminal device (e.g., an HR session of the terminal device) according to the EAS IP address and/or FQDN. The splitting point can be used for splitting the message to the VPLMN, for example, splitting the service message corresponding to the EAS deployed in the VPLMN to the VPLMN, so that although the session of the current terminal equipment is the HR session, the EAS deployed in the VPLMN can be directly accessed through the UPF deployed in the VPLMN without passing through the UPF of the HPLMN, thereby greatly improving service access efficiency and reducing service access delay.

Optionally, the splitting point is an uplink classifier (uplink classifier, UL CL) or a Branching Point (BP). When the terminal device needs to perform service transmission, multiple PDU sessions (sessions) to the same DN or different DNs can be established through the SMF. The SMF can control the data routing of the PDU so that this PDU session can have multiple N6 interfaces at the same time, the UPF connecting each N6 interface is called a PSA, each PSA providing a different path to the same DN. Thus, in one possible way, the V-SMF may determine the UL CL in the VPLMN, e.g. for different types of PDU sessions, the SMF may insert one UL CL in the data transmission path of the PDU session. The UL CL function is provided by the UPF for forwarding packets that meet traffic filtering rules to a specified path. When a UL CL is inserted into a PDU session data channel, the PDU session may have multiple PDU session anchors providing multiple different paths to access the same DN. That is, the UL CL may function to transmit uplink data to different PSAs and to combine downlink data to the UE. In another possible way, the V-SMF may determine a branching point in the VPLMN, and in particular, data corresponding to each PSA may be aggregated into a common UPF, which has the function of the branching point. The branching point forwards upstream data up to a different PSA and merges downstream data from the PSA down. It will be appreciated that the nature of the split point may be considered a UPF, in other words, the split point is one of the split functions that the UPF described above may implement.

It is to be understood that the foregoing is merely illustrative and that no limitation is thereby intended.

For ease of understanding, embodiments of the present application are described below in conjunction with fig. 4 to 9, and in the following examples, it is assumed that the information #a is N DNAIs, and the data management network element in the VPLMN is exemplified by V-UDR. The steps involved therein may be referred to in particular as described above.

First, the implementation of the above-described scheme a and scheme B will be briefly described in connection with the architecture shown in fig. 4 and 5.

Fig. 4 is a schematic diagram of a network architecture suitable for scheme a according to an embodiment of the present application. Under this architecture, as shown in fig. 4, V-UDR may store EAS deployment information in VPLMN, and H-SMF may obtain EAS deployment information corresponding to N DNAIs from VPLMN (e.g., V-UDR). As an example, under this architecture, to enable discovery of local EAS in HR roaming scenarios, the following steps may be included.

401, the V-SMF sends N DNAI's to the H-SMF.

In one possible way, the V-SMF determines the N DNAIs according to local policy information and sends the N DNAIs to the H-SMF. In another possible way, the V-SMF queries the N DNAIs from the V-PCF and sends the N DNAIs to the H-SMF. Regarding the manner in which V-SMF determines N DNAIs, reference may be made to the relevant description in method 300, which is not repeated here.

402, the H-SMF requests the EAS deployment information corresponding to N DNAI from the V-UDR through the H-NEF.

After the H-SMF receives the N DNAI, the H-NEF can request the EAS deployment information corresponding to the N DNAI; further, the H-NEF may request N DNAI-corresponding EAS deployment information from the V-UDR.

The H-NEF requests N DNAI corresponding EAS deployment information from the V-UDR, which may include, for example: the H-NEF sends a request message to the V-NEF, the V-NEF forwards the request message to the V-UDR, the request message comprises N DNAI, and the request message is used for requesting the EAS deployment information corresponding to the N DNAI. Optionally, the request message further includes a VPLMN ID, which may be used to identify the VPLMN, i.e. the VPLMN where the UE is currently located.

After receiving the request of H-NEF, V-UDR can inquire the EAS deployment information corresponding to N DNAI from the stored EAS deployment information in VPLMN according to the request of H-NEF, and send the EAS deployment information corresponding to N DNAI to H-NEF. Further, the H-NEF sends the EAS deployment information corresponding to the N DNAI to the H-SMF, so that the H-SMF obtains the EAS deployment information corresponding to the N DNAI.

Through the steps, the H-SMF can acquire the EAS deployment information corresponding to N DNAI from the VPLMN (such as V-UDR).

After receiving the EAS deployment information corresponding to the N DNAIs, the H-SMF may determine a DNS handling rule and send the DNS handling rule to the EASDF, i.e. step 403.

403, the H-SMF sends DNS processing rules to the EASDF.

In the architecture shown in fig. 4, EASDF is located at the HPLMN and can be used to assist in EAS discovery in the VPLMN.

Regarding DNS processing rules, reference may be made to the related description in the foregoing method 300, which is not repeated here. The EAS server corresponding to the domain name contained in the DNS processing rule may be deployed in the VPLMN.

After the EASDF obtains the DNS processing rule from the H-SMF, the DNS message sent by the UE can be correspondingly processed. For example, when the UE accesses a certain edge service or requests an edge service (or requests an address of an edge server), a DNS query may be initiated, where the DNS query includes a domain name corresponding to the edge service. I.e. step 404.

404, the UE sends a DNS query to the EASDF.

One possible implementation, the UE sends DNS queries to the EASDF via the RAN and UPF (i.e., V-UPF and H-UPF) over the user plane.

After the EASDF receives the DNS query from the UE, the DNS query can be processed according to the DNS processing rule received from the H-SMF. For example, when the EASDF detects according to the DNS processing rule that a domain name (such as a FQDN) included in the DNS query of the UE may be matched with a domain name included in the DNS processing rule, or it may be understood that an EAS server corresponding to the domain name included in the DNS query is deployed in the VPLMN, the EASDF adds an ECS option to the DNS query according to the DNS processing rule, and then sends the DNS query after adding the ECS option to the C-DNS server. Or when the domain name (such as FQDN) contained in the DNS query sent by the UE is matched with the domain name in the DNS processing rule, the EASDF determines the address of the L-DNS server positioned in the VPLMN according to the DNS processing rule, and sends the DNS query of the UE to the L-DNS server. As shown in fig. 4, the EASDF may determine the L-DNS server according to DNS processing rules, and may forward DNS messages to the L-DNS server, thereby letting the L-DNS server determine EAS.

In the embodiment of the application, when the domain name contained in the DNS query of the UE is matched with the domain name in the DNS processing rule, after the ECS option is added to the DNS query by the EASDF, the DNS query added with the ECS option can be forwarded to the C-DNS server. Further, the C-DNS server can send a response (response), such as a DNS response, to the EASDF. Address information, such as EAS IP address and/or FQDN, etc., may be included in the DNS response. After the EASDF receives the DNS response, the EASDF may report address information, such as an EAS IP address and/or FQDN, included in the DNS response to the H-SMF.

The easdf sends a DNS report request to the H-SMF 405.

Wherein the DNS report request includes an EAS IP address and/or FQDN. Upon receipt of the DNS report request, the H-SMF may send an EAS IP address and/or FQDN to the V-SMF to trigger the V-SMF to traffic steer (traffic steering) the HR session of the UE.

406, the H-SMF sends a notify message to the V-SMF.

The notification message carries an EAS IP address and/or FQDN, which may be used to trigger a traffic scheduling of the HR session for the UE.

It is to be appreciated that the above steps are merely exemplary, and embodiments of the present application are not limited in this respect, as further processing steps may be included in actual communications, such as may be described with reference to method 600 and method 700.

Through the scheme, the H-SMF acquires N DNAI which can be accessed by the UE from the VPLMN, and further acquires the EAS deployment information corresponding to the N DNAI from the VPLMN, so that the H-SMF can know which positions of the VPLMN are deployed with the edge application server, and the EASDF can be assisted to realize the discovery of the local EAS. Further, the H-SMF can determine DNS processing rules according to the EAS deployment information corresponding to the N DNAI, and the EASDF is responsible for processing DNS query messages from the UE, so that the discovery of the local EAS in the HR roaming scene can be realized.

Fig. 5 is a schematic diagram of a network architecture suitable for scheme B according to an embodiment of the present application. Under this architecture, as shown in FIG. 5, the H-UDR may store the EAS deployment information in the VPLMN, and the H-SMF may obtain the EAS deployment information corresponding to N DNAI from the HPLMN (e.g., H-UDR). As an example, under this architecture, to enable discovery of local EAS in HR roaming scenarios, the following steps may be included.

501, the v-SMF sends N DNAIs to the H-SMF.

502, the H-SMF requests the EAS deployment information corresponding to N DNAI from the H-UDR through the H-NEF.

After the H-SMF receives the N DNAI, the H-NEF can request the EAS deployment information corresponding to the N DNAI; further, the H-NEF may request N DNAI-corresponding EAS deployment information from the H-UDR.

The H-NEF requests N DNAI corresponding EAS deployment information from the H-UDR, which may include, for example: the H-NEF sends a request message to the H-UDR, wherein the request message comprises N DNAI, and the request message is used for requesting the EAS deployment information corresponding to the N DNAI. Optionally, the request message further includes a VPLMN ID, which may be used to identify the VPLMN, i.e. the VPLMN where the UE is currently located.

After the H-UDR receives the request of the H-NEF, the H-UDR can inquire the EAS deployment information corresponding to N DNAI from the stored EAS deployment information in the VPLMN according to the request of the H-NEF, and send the EAS deployment information corresponding to N DNAI to the H-NEF. Further, the H-NEF sends the EAS deployment information corresponding to the N DNAI to the H-SMF, so that the H-SMF obtains the EAS deployment information corresponding to the N DNAI.

Through the steps, the H-SMF can acquire the EAS deployment information corresponding to N DNAI from the HPLMN (such as H-UDR).

After receiving the EAS deployment information corresponding to the N DNAIs, the H-SMF may determine a DNS handling rule and send the DNS handling rule to the EASDF, step 503.

503, the H-SMF sends DNS processing rules to the EASDF.

At 504, the ue sends a DNS query to the EASDF.

505, the easdf sends a DNS report request to the H-SMF.

The h-SMF sends 506 a notification message to the V-SMF.

Steps 503 to 506 are similar to steps 403 to 406, and will not be described here.

It is to be appreciated that the above steps are merely exemplary, and embodiments of the present application are not limited in this respect, and that more processing steps may be included in actual communications, for example, as described with reference to method 800 and method 900 below.

Through the scheme, the H-SMF acquires N DNAI which can be accessed by the UE from the VPLMN, and further acquires the EAS deployment information corresponding to the N DNAI from the HPLMN, so that the H-SMF can know which positions of the VPLMN are deployed with the edge application server, and the EASDF can be assisted to realize the discovery of the local EAS. Further, the H-SMF can determine DNS processing rules according to the EAS deployment information corresponding to the N DNAI, and the EASDF is responsible for processing DNS query messages from the UE, so that the discovery of the local EAS in the HR roaming scene can be realized.

The following describes the possible processes described above in connection with fig. 6 to 9.

Fig. 6 is a schematic flow chart diagram of a method 600 of communication provided by an embodiment of the present application. This method 600 may be used to implement a scheme such as method 300, for example, method 600 may be used in a scenario where a V-SMF determines N DNAIs according to a local policy, and an H-SMF obtains EAS deployment information corresponding to the N DNAIs from a VPLMN. The method 600 may be implemented by the architecture shown in fig. 4. As an example, the method 600 may include the following steps.

601, v-SMF configures policy information.

Wherein policy information may be used to indicate which DNAIs within the VPLMN may be open to other PLMNs. For policy information, reference may be made to the relevant description in method 300 above, which is not repeated here.

The v-UDR stores EAS deployment information in the VPLMN 602.

With respect to EAS deployment information, reference may be made to the preceding terminology explanation, which is not repeated here.

In the embodiment of the application, the V-UDR can store the EAS deployment information in the VPLMN, such as the EAS deployment information corresponding to each DNAI in the VPLMN, and the EAS deployment information corresponding to DNAI allowed to be opened to other PLMNs in the VPLMN, without limitation.

603, the ue sends a session establishment request message to the V-SMF.

Optionally, the session establishment request message includes: S-NSSAI, DNN, PDU session ID.

In HR roaming scenarios, the UE may initiate HR session establishment procedures. For example, the UE may send a session establishment request message to the V-SMF via the V-AMF. For example, the UE sends a PDU session establishment request to the V-AMF (PDU session establishment request); the V-AMF sends an Nsmf interface PDU session establishment Request (Nsmf_PDUSion_Create Request) to the V-SMF; after the V-SMF receives the NSmf_PDUSion_Create Request, a session context is established. The specific session establishment procedure may refer to the prior art or the manner in which the session establishment occurs later, and is not limited thereto.

The v-SMF determines N DNAIs based on the policy information and the location of the UE 604.

Where N DNAIs represent DNAIs that the VPLMN allows to be opened to the HPLMN.

One possible implementation manner, the V-SMF judges M DNAI which can be accessed by the current position (expressed by TAI) of the UE according to the S-NSSAI and DNN corresponding to the session; based on the policy information, N DNAI's that can be opened to the HPLMN (or H-SMF) are then determined from the M DNAI's. Specifically, reference may be made to the second possible implementation manner in the foregoing method 300, which is not described herein.

605, the V-SMF sends N DNAI's to the H-SMF. Optionally, the V-SMF also sends a VPLMN ID or V-SMF ID to the H-SMF, which may be used to determine the VPLMN where the UE is currently located. Specifically, if the V-SMF sends the VPLMN ID to the H-SMF, the H-SMF may directly acquire the VPLMN ID; if the V-SMF sends a V-SMF ID to the H-SMF, the H-SMF may determine the VPLMN ID from the V-SMF ID. The N DNAIs and VPLMN IDs or V-SMF IDs may be carried in the same signaling, or may be transmitted separately, which is not limited.

In one possible implementation, the V-SMF sends an Nsmf interface PDU session establishment Request (nsmf_pduse_create Request) to the H-SMF, the nsmf_pduse_create Request including N DNAIs and VPLMN IDs. According to this implementation, the H-SMF may obtain the VPLMN ID directly from the PDU session establishment request.

In another possible implementation, the V-SMF sends an nsmf_pduse_create Request to the H-SMF, where the nsmf_pduse_create Request includes N DNAIs and V-SMF IDs, where the V-SMF IDs may include VPLMN IDs. According to this implementation, the H-SMF may obtain the VPLMN ID from the V-SMF ID. The H-SMF sends a request message to the H-NEF 606.

607, the h-NEF sends a request message to the V-NEF.

For example, if the request message in step 606 carries a VPLMN ID, the H-NEF selects a NEF (i.e., V-NEF) in the VPLMN according to the VPLMN ID carried in the request message, and sends the request message to the V-NEF. The H-NEF sends a request message to the V-NEF, wherein the request message comprises N DNAI used for triggering the V-NEF to inquire the EAS deployment information corresponding to the N DNAI. Optionally, the H-NEF also includes HPLMN ID or H-NEF ID in the request message sent to the V-NEF. Specifically, if the request message sent by the H-NEF to the V-NEF further includes the HPLMN ID, the V-NEF may directly acquire the HPLMN ID; if the H-NEF also includes an H-NEF ID in the request message sent by the H-NEF to the V-NEF, the V-NEF can determine the HPLMN ID according to the H-NEF ID.

In one possible implementation, the H-NEF sends nnef_easliploymet_ Subscribe Request to the V-NEF, where the nnef_easliploymet_ Subscribe Request includes N DNAIs and HPLMN IDs, and the nnef_easliploymet_subscnibe is used to trigger the V-NEF to query the EAS deployment information corresponding to the N DNAIs. According to this implementation, the V-NEF can directly acquire the HPLMN ID.

In another possible implementation, the H-NEF sends nnef_easliploymet_ Subscribe Request to the V-NEF, where the nnef_easliploymet_ Subscribe Request includes N DNAIs and an H-NEF ID, and the nnef_easliploymet_subscnube is used to trigger the V-NEF to query the EAS deployment information corresponding to the N DNAIs. Wherein the H-NEF ID can comprise an HPLMN ID. According to this implementation, the V-NEF may obtain the HPLMN ID from the H-NEF ID.

608, the V-NEF obtains EAS deployment information corresponding to the N DNAIs from the V-UDR.

For example, the V-NEF uses N DNAIs as index values, and queries the V-UDR for EAS deployment information corresponding to the N DNAIs, so as to obtain the V-UDR from the EAS deployment information corresponding to the N DNAIs.

Optionally, the V-NEF may also send an HPLMN ID to the V-UDR indicating which PLMN of the V-UDR requested to acquire the EAS deployment information. At this time, the V-UDR may further determine, according to the HPLMN ID, whether to return EAS deployment information corresponding to the N DNAIs.

609, the v-NEF sends a response message to the H-NEF.

The response message includes EAS deployment information corresponding to the N DNAIs.

In one possible implementation, the V-NEF sends an Nnef interface EAS deployment notification response (nnef_easidoymet_notify response) to the H-NEF, where the nnef_easidoymet_notify response includes N DNAI-corresponding EAS deployment information.

The H-NEF forwards the response message to the H-SMF 610.

In one possible implementation, the H-NEF sends an nnef_easidoymet_notify response to the H-SMF, where the nnef_easidoymet_notify response includes EAS deployment information corresponding to N DNAIs.

611, the H-SMF determines DNS processing rules according to the EAS deployment information corresponding to the N DNAI.

After the H-SMF receives the EAS deployment information corresponding to the N DNAIs, DNS processing rules may be determined based on the EAS deployment information corresponding to the N DNAIs.

As an example, DNS processing rules may include one or more of the following information: FQDN range, ECS option, L-DNS server address, DNS forwarding rules.

The DNS forwarding rule may also be referred to as a forwarding rule, or a data plane forwarding rule, may be used for the H-EASDF to process DNS messages from the UE accordingly. For example, when the FQDN contained in the DNS query sent by the UE matches the FQDN range in the DNS processing rule, the H-EASDF adds ECS option to the DNS query based on the DNS forwarding rule. For another example, when the FQDN included in the DNS query sent by the UE matches the FQDN range in the DNS processing rule, the H-EASDF forwards the DNS query (e.g., the DNS query after adding the ECS option) to the L-DNS server based on the DNS forwarding rule.

Optionally, the method 600 further comprises: the H-SMF selects the H-EASDF and sends DNS processing rules to the H-EASDF. Specifically, reference may be made to the existing procedure, which is not limited.

Through the above steps and other steps (refer specifically to the existing session establishment procedure), the UE may complete session establishment.

612, the UE sends a DNS query to the H-EASDF.

For example, the UE sends a DNS query message to the H-EASDF via the RAN and UPF via the user plane.

The DNS query includes an FQDN corresponding to an application that the UE wants to access.

613, H-EASDF processes the DNS query according to DNS processing rules.

After the H-EASDF receives the DNS query, the DNS query can be processed according to the DNS processing rules received from the H-SMF. For example, if the H-EASDF detects according to the DNS processing rule that the FQDN included in the DNS query of the UE may be matched with the FQDN included in the DNS processing rule, or it may be understood that an EAS server corresponding to the FQDN included in the DNS query is deployed in the VPLMN, the H-EASDF adds the ECS option to the DNS query according to the DNS processing rule, and then sends the DNS query after adding the ECS option to the C-DNS server. Or when the FQDN contained in the DNS query sent by the UE is matched with the FQDN range in the DNS processing rule, the H-EASDF determines the address of the L-DNS server positioned in the VPLMN according to the DNS processing rule, and sends the DNS query of the UE to the L-DNS server, so that the L-DNS server determines the EAS.

In the embodiment of the application, when the FQDN contained in the DNS query of the UE is matched with the FQDN range in the DNS processing rule, after the ECS option is added to the DNS query, the H-EASDF can forward the DNS query added with the ECS option to the C-DNS server. Further, the C-DNS server can send a response (e.g., DNS response) to the H-EASDF. Address information, such as EAS IP address and/or FQDN, etc., may be included in the DNS response. After the H-EASDF receives the DNS response, address information, such as an EAS IP address and/or FQDN, contained in the DNS response can be reported to the H-SMF.

614, the H-EASDF sends a DNS report request to the H-SMF (DNS reporting request).

Wherein the DNS report request includes an EAS IP address and/or FQDN.

615, the h-SMF sends the EAS IP address and/or FQDN to the V-SMF.

In one possible implementation, the H-SMF sends a notification message to the V-SMF, which carries the EAS IP address and/or FQDN.

616, V-SMF selects UL CL or BP, and L-PSA.

Taking EAS IP address as an example, for example, V-SMF may determine DNAI from the received EAS IP address and determine whether the DNAI allows insertion of UL CL or BP; if insertion of the UL CL or BP is allowed, the V-SMF selects the UL CL or BP, and the L-PSA for the session.

617, the v-SMF returns an acknowledgement message to the H-SMF.

One possible implementation, the H-SMF sends a notification acknowledgement (notify ack) message to the V-SMF.

618, the H-SMF sends a DNS report response to the H-EASDF (DNS reporting response).

619, the H-EASDF sends a DNS response to the UE.

The H-EASDF may send a DNS response to the UE after receiving DNS reporting response from the H-SMF.

Based on the above method 600, in the hr session establishment procedure, the V-SMF may determine DNAI that the current UE may access according to the UE location, and determine to open N DNAIs to the H-SMF in combination with policy information configured locally; after the H-SMF acquires the N DNAI, the EAS deployment information corresponding to the N DNAI can be acquired from the V-UDR inquiry through the interaction between the H-NEF and the V-NEF; further, the H-SMF may determine DNS processing rules according to the EAS deployment information corresponding to the N DNAI, and the H-EASDF is responsible for processing DNS query messages from the UE. Thus, discovery of local EAS in HR roaming scenarios may be achieved. In addition, the V-SMF and H-SMF delivered information (N DNAI) is for the UE (per UE), with less modification to the interface between SMFs.

Fig. 7 is a schematic flow chart diagram of another method 700 of communication provided by an embodiment of the present application. This method 700 may be used to implement an aspect as method 300, for example, method 700 may be used in a scenario where a V-SMF queries N DNAIs from a V-PCF and an H-SMF obtains EAS deployment information corresponding to the N DNAIs from a VPLMN. The method 700 may be implemented by the architecture shown in fig. 4. As an example, method 700 may include the following steps.

701, the V-UDR stores EAS deployment information in the VPLMN.

The ue sends a session establishment request message to the V-SMF 702.

Step 702 is similar to step 603, and will not be described herein.

703, v-SMF determines M DNAIs.

In one possible implementation, the V-SMF determines M DNAIs that the current location (denoted by TAI) of the UE can access, based on the S-nsai and DNN.

704, the V-SMF sends a query message to the V-PCF.

Wherein the query message includes M DNAIs, and the query message is used to query the M DNAIs to determine DNAIs that can be opened to the HPLMN (or H-SMF). Optionally, the query message further includes an HPLMN ID, where the HPLMN ID is used to identify the HPLMN.

In one possible implementation, the V-SMF sends an EAS policy request (EAS Policy Request) to the V-PCF, including the HPLMN ID and M DNAIs in EAS Policy Request, and EAS Policy Request is for requesting the V-PCF to determine which DNAIs can be opened to the HPLMN. In particular, reference may be made to a description of a third possible implementation of the method 300, which is not repeated here.

705, the V-PCF sends a query response message to the V-SMF.

In one possible implementation, the V-PCF sends an EAS policy response (EAS Policy Response) to the V-SMF, including N DNAIs in EAS Policy Response, which are DNAIs open to the HPLMN in M DNAIs.

706, the v-SMF sends N DNAIs to the H-SMF.

707, the H-SMF sends a request message to the H-NEF.

708, the H-NEF sends a request message to the V-NEF.

709, the V-NEF obtains the EAS deployment information corresponding to the N DNAIs from the V-UDR.

The v-NEF sends a response message to the H-NEF 710.

711, the H-NEF forwards the response message to the H-SMF.

And 712, the H-SMF determines DNS processing rules according to the EAS deployment information corresponding to the N DNAI.

713, the ue sends a DNS query to the H-EASDF.

714, the H-EASDF processes the DNS query according to a DNS processing rule.

715, the H-EASDF sends a DNS report request to the H-SMF.

716, the h-SMF sends the EAS IP address and/or FQDN to the V-SMF.

717, V-SMF selects UL CL or BP, and L-PSA.

718, the v-SMF returns an acknowledgement message to the H-SMF.

719, the H-SMF sends a DNS report response to the H-EASDF.

The H-EASDF sends a DNS response to the UE 720.

Steps 706 to 720 are similar to steps 605 to 619, and will not be described here.

Based on the above method 700, in the hr session establishment procedure, the V-SMF may determine DNAI that the current UE may access according to the UE location, and request the V-PCF to determine which DNAI of the DNAIs that the current UE may access may be opened to the H-SMF; after the H-SMF acquires N DNAI, the N DNAI corresponding EAS deployment information can be acquired from the V-UDR inquiry through the interaction between the H-NEF and the V-NEF; further, the H-SMF can determine DNS processing rules according to the EAS deployment information corresponding to the N DNAI, and the H-EASDF is responsible for processing DNS query messages from the UE, so that the discovery of local EAS in the HR roaming scene can be realized. In addition, the information (N DNAI) conveyed by V-SMF and H-SMF is per UE, and the interface between SMF is changed less.

Fig. 8 is a schematic flow chart diagram of another method 800 of communication provided by an embodiment of the present application. This method 800 may be used to implement an aspect as method 300, for example, method 800 may be used in a scenario where a V-SMF determines N DNAIs according to a local policy, and an H-SMF obtains EAS deployment information corresponding to the N DNAIs from an HPLMN. The method 800 may be implemented by the architecture shown in fig. 5. As an example, the method 800 may include the following steps.

801, v-SMF locally configures policy information.

802, H-UDR stores EAS deployment information in the VPLMN.

One possible implementation, the AF in the VPLMN sends the EAS deployment information in the VPLMN to the H-UDR; the H-UDR receives the EAS deployment information in the VPLMN and stores the EAS deployment information in the VPLMN. For example, the AF in the VPLMN sends the EAS deployment information in the VPLMN to the V-NEF; after receiving the EAS deployment information in the VPLMN, the V-NEF sends the EAS deployment information in the VPLMN to the H-NEF; after receiving the EAS deployment information in the VPLMN, the H-NEF sends the EAS deployment information in the VPLMN to the H-UDR; the H-UDR receives the EAS deployment information in the VPLMN and stores the EAS deployment information in the VPLMN

In the embodiment of the application, the H-UDR can store the EAS deployment information in the VPLMN, such as the EAS deployment information corresponding to each DNAI in the VPLMN, and the EAS deployment information corresponding to DNAI allowed to be opened to other PLMNs in the VPLMN, without limitation.

803, the ue sends a session establishment request message to the V-SMF.

At 804, the v-SMF determines N DNAIs based on the policy information and the location of the UE.

805, the v-SMF sends N DNAIs to the H-SMF.

806, the H-SMF sends a request message to the H-NEF.

Steps 803 to 806 are similar to steps 603 to 606, and will not be described here.

807, the H-NEF sends a query message to the H-UDR.

The query message includes N DNAIs, and the query message is used for querying EAS deployment information corresponding to the N DNAIs.

Optionally, the query message further comprises a VPLMN ID from which the H-UDR can identify the VPLMN.

In the embodiment of the application, the H-UDR can store the EAS deployment information of the VPLMN, so that the H-NEF can directly inquire the H-UDR about the EAS deployment information corresponding to N DNAI.

808, the H-UDR sends a query response message to the H-NEF.

The inquiry response message comprises EAS deployment information corresponding to the N DNAIs.

809, the H-NEF sends N EAS deployment information corresponding to DNAI to the H-SMF.

810, the H-SMF determines DNS processing rules according to the EAS deployment information corresponding to the N DNAI.

811, the ue sends a DNS query to the H-EASDF.

812, the H-EASDF processes the DNS query according to a DNS processing rule.

813, the H-EASDF sends a DNS report request to the H-SMF.

814, the h-SMF sends the EAS IP address and/or FQDN to the V-SMF.

815, V-SMF selects UL CL or BP, and L-PSA.

816, the v-SMF returns an acknowledgement message to the H-SMF.

817 the H-SMF sends a DNS report response to the H-EASDF.

818, the h-EASDF sends a DNS response to the UE.

Steps 810-818 are similar to steps 611-619 and are not described in detail herein.

Based on the above method 800, in the hr session establishment procedure, the V-SMF may determine DNAI that the current UE may access according to the UE location, and determine to open N DNAIs to the H-SMF in combination with policy information configured locally; after the H-SMF acquires the N DNAI, the EAS deployment information corresponding to the N DNAI can be inquired and acquired from the H-UDR; further, the H-SMF can determine DNS processing rules according to the EAS deployment information corresponding to the N DNAI, and the H-EASDF is responsible for processing DNS query messages from the UE, so that the discovery of local EAS in the HR roaming scene can be realized. In addition, the information (N DNAI) conveyed by V-SMF and H-SMF is per UE, and the interface between SMF is changed less.

Fig. 9 is a schematic flow chart diagram of another method 900 of communication provided by an embodiment of the present application. This method 900 may be used to implement an aspect as method 300, for example, method 900 may be used in a scenario where a V-SMF queries N DNAIs from a V-PCF and an H-SMF obtains EAS deployment information corresponding to the N DNAIs from an HPLMN. The method 900 may be implemented by the architecture shown in fig. 5. The method 900 may include the following steps.

901, h-UDR stores EAS deployment information in VPLMN.

The ue sends a session establishment request message to the V-SMF 902.

Steps 901-902 are similar to steps 802-803, and are not described here.

903, v-SMF determines M DNAIs.

904, the V-SMF sends a query message to the V-PCF.

905, the V-PCF sends a query response message to the V-SMF.

Steps 904-905 are similar to steps 704-705 and are not described here.

906, the v-SMF sends N DNAIs to the H-SMF.

907, the H-SMF sends a request message to the H-NEF.

908, the H-NEF sends a query message to the H-UDR.

909, the H-UDR sends a query response message to the H-NEF.

910, the H-NEF sends the EAS deployment information corresponding to the N DNAIs to the H-SMF.

911, H-SMF determines DNS processing rules according to the EAS deployment information corresponding to N DNAI.

The UE sends 912 a DNS query to the H-EASDF.

913, H-EASDF processes the DNS query according to the DNS processing rules.

914, the H-EASDF sends a DNS report request to the H-SMF.

915, h-SMF sends EAS IP address and/or FQDN to V-SMF.

916, V-SMF selects UL CL or BP, as well as L-PSA.

917, v-SMF returns an acknowledgement message to H-SMF.

918, the H-SMF sends a DNS report response to the H-EASDF.

919, H-EASDF sends DNS response to the UE.

Steps 906-919 are similar to steps 805-818 and are not described here.

Based on the above method 900, in the hr session establishment procedure, the V-SMF may determine DNAI that the current UE may access according to the UE location, and request the V-PCF to determine which DNAI of the DNAIs that the current UE may access may be opened to the H-SMF; after the H-SMF acquires N DNAI, the EAS deployment information corresponding to the N DNAI can be inquired and acquired from the H-UDR; further, the H-SMF can determine DNS processing rules according to the EAS deployment information corresponding to the N DNAI, and the H-EASDF is responsible for processing DNS query messages from the UE, so that the discovery of local EAS in the HR roaming scene can be realized. In addition, the information (N DNAI) conveyed by V-SMF and H-SMF is per UE, and the interface between SMF is changed less.

It will be appreciated that the examples of fig. 4 to 9 in the embodiments of the present application are merely for facilitating understanding of the embodiments of the present application by those skilled in the art, and are not intended to limit the embodiments of the present application to the specific scenarios illustrated. It will be apparent to those skilled in the art from the examples of fig. 4-9 that various equivalent modifications or variations may be made, and such modifications or variations are intended to be within the scope of the embodiments of the present application. For example, the session establishment procedure in fig. 6 to 9 described above may be replaced with a session modification procedure. For another example, the ECS option in FIGS. 4-9 described above may be replaced with an L-DNS server address, and accordingly, the act of adding the ECS option to the DNS query may be replaced with an act of forwarding the DNS query to the L-DNS server. As another example, more network elements or devices may be included in fig. 4-9 described above.

It should also be understood that, in some embodiments described above, the message names, such as nsmf_pdustion_update Request message, nsmf_pdustion_create Request, query message, etc., are only examples, and do not limit the protection scope of the embodiments of the present application. For example, the query message may be replaced with the request message.

It will also be appreciated that in some of the embodiments described above, the message is sent multiple times. Taking the example of sending the message from a to B, the message from a to B may include sending the message from a directly to B, or may include sending the message from a to B through other devices or network elements, which is not limited.

It will also be appreciated that in embodiments of the present application, reference is made to local EAS discovery multiple times, and that local EAS discovery is understood to mean discovery of EAS of a visited network (e.g., VPLMN) unless specifically indicated otherwise.

It will also be appreciated that in some of the above embodiments, the location of the terminal device is mainly exemplified by TAI, which is not limited thereto. The TAI may be replaced with other information capable of representing (or reflecting) the location of the terminal device.

It will also be appreciated that some optional features of the various embodiments of the application may, in some circumstances, be independent of other features or may, in some circumstances, be combined with other features, without limitation.

It is also to be understood that the aspects of the embodiments of the application may be used in any reasonable combination, and that the explanation or illustration of the various terms presented in the embodiments may be referred to or explained in the various embodiments without limitation.

It should be further understood that the magnitude of the various numerical numbers in the embodiments of the present application does not mean the order of execution, but merely serves to distinguish between the convenience of description and the implementation of the embodiments of the present application, and should not constitute any limitation.

It is also to be understood that in the foregoing embodiments of the method and operations performed by the apparatus may also be performed by component parts (e.g., chips or circuits) of the apparatus.

Corresponding to the methods given by the above method embodiments, the embodiments of the present application also provide corresponding apparatuses, where the apparatuses include corresponding modules for executing the above method embodiments. The module may be software, hardware, or a combination of software and hardware. It will be appreciated that the technical features described in the method embodiments described above are equally applicable to the device embodiments described below.

Fig. 10 is a schematic diagram of a communication device 1000 according to an embodiment of the present application. The apparatus 1000 comprises a transceiver unit 1010 and a processing unit 1020. The transceiver unit 1010 may be used to implement corresponding communication functions. The transceiver unit 1010 may also be referred to as a communication interface or a communication unit. The processing unit 1020 may be configured to implement a corresponding processing function, e.g., determining the first information, and further, e.g., determining deployment information of EAS corresponding to the first information.

Optionally, the apparatus 1000 further includes a storage unit, where the storage unit may be configured to store instructions and/or data, and the processing unit 1020 may read the instructions and/or data in the storage unit, so that the apparatus implements the actions of the device or the network element in the foregoing method embodiments.

In a first design, the apparatus 1000 may be a session management network element (e.g., H-SMF) in the home network in the foregoing embodiment, or may be a component (e.g., a chip) of a session management network element in the home network. The apparatus 1000 may implement steps or procedures performed corresponding to session management network elements in the home network in the above method embodiment, where the transceiving unit 1010 may be configured to perform transceiving related operations of session management network elements in the home network in the above method embodiment, and the processing unit 1020 may be configured to perform processing related operations of session management network elements in the home network in the above method embodiment.

A possible implementation manner, the transceiver unit 1010 is configured to receive, from a session management network element in the visited network, first information corresponding to a terminal device, where the first information is used to indicate a deployment location of an edge application server EAS in the visited network; the receiving unit 1010 is further configured to obtain EAS deployment information corresponding to the first information according to the first information.

The first information corresponding to the terminal device includes: the first information is determined based on the location of the terminal device.

The first information is illustratively determined from a location of the terminal device, comprising: the first information is used for indicating: of the deployment locations of EAS determined from the location of the terminal device, the deployment location of EAS that the terminal device is allowed to access.

Optionally, the transceiver 1010 is specifically configured to send a request message to a data management network element in the home network, where the request message includes first information, and the request message is used to request to obtain EAS deployment information corresponding to the first information; and receiving the EAS deployment information corresponding to the first information from a data management network element in the home network.

Optionally, the transceiver 1010 is specifically configured to send a request message to a data management network element in the visited network, where the request message includes first information, and the request message is used to request to obtain EAS deployment information corresponding to the first information; and receiving the EAS deployment information corresponding to the first information from the data management network element in the visited network.

The request message also illustratively includes an identification of the visited network.

Optionally, the processing unit 1020 is configured to determine a DNS processing rule of a domain name system according to the EAS deployment information corresponding to the first information, where the DNS processing rule is used to process the DNS message.

Optionally, the transceiver unit 1010 is further configured to receive an identification of the visited network from a session management network element in the visited network.

In a second design, the apparatus 1000 may be a session management network element (e.g., V-SMF) in the visited network in the foregoing embodiment, or may be a component (e.g., a chip) of a session management network element in the visited network. The apparatus 1000 may implement steps or procedures performed by a session management network element in a visited network in the above method embodiment, where the transceiving unit 1010 may be configured to perform transceiving related operations of the session management network element in the visited network in the above method embodiment, and the processing unit 1020 may be configured to perform processing related operations of the session management network element in the visited network in the above method embodiment.

A possible implementation manner, the processing unit 1020 is configured to determine, according to a location of the terminal device, first information corresponding to the terminal device, where the first information is used to indicate a deployment location of an edge application server EAS in the visited network; the transceiver unit 1010 is configured to send the first information to a session management network element in the home network.

Illustratively, the first information is used to obtain EAS deployment information corresponding to the first information.

Optionally, the first information is used to indicate: the deployment location of the EAS which allows the terminal device to access, among the deployment locations of EAS determined from the location of the terminal device; the processing unit 1020 is specifically configured to determine first information corresponding to the terminal device according to a location of the terminal device and policy information, where the policy information is used to indicate a deployment location of EAS that allows the visited network to send to the home network.

Optionally, the first information is used to indicate: the deployment location of the EAS which allows the terminal device to access, among the deployment locations of EAS determined from the location of the terminal device; the processing unit 1020 is specifically configured to determine, according to the location of the terminal device, second information corresponding to the terminal device; the transceiver unit 1010 is further configured to send a request message to a session management network element in the visited network to a policy control network element in the visited network, where the request message includes second information, and the request message is used to request a deployment location of EAS that allows the visited network to send to the home network; first information is received from a policy control network element in the visited network, the first information being determined from the second information.

Optionally, the transceiver unit 1010 is further configured to send an identifier of the visited network to a session management network element in the home network.

In a third design, the apparatus 1000 may be a data management network element (e.g., H-UDR) in the home network in the foregoing embodiment, or may be a component (e.g., a chip) of a data management network element in the home network in the visited network. The apparatus 1000 may implement steps or procedures performed corresponding to data management network elements in the home network in the above method embodiment, where the transceiving unit 1010 may be configured to perform transceiving related operations of the data management network elements in the home network in the above method embodiment, and the processing unit 1020 may be configured to perform processing related operations of the data management network elements in the home network in the above method embodiment.

A possible implementation manner, the transceiver unit 1010 is configured to receive a request message from a session management network element in a home network, where the request message includes first information corresponding to a terminal device, where the first information is used to indicate a deployment location of an edge application server EAS in a visited network, and the request message is used to request to obtain EAS deployment information corresponding to the first information; the transceiver 1010 is further configured to send EAS deployment information corresponding to the first information to a session management network element in the home network.

Optionally, the request message further includes an identification of the visited network; the processing unit 1020 is configured to determine EAS deployment information corresponding to the first information according to the identifier of the visited network and the first information.

Optionally, the processing unit 1020 is configured to locally store EAS deployment information corresponding to the first information.

It should be understood that the specific process of each unit performing the corresponding steps has been described in detail in the above method embodiments, and is not described herein for brevity.

It should also be appreciated that the apparatus 1000 herein is embodied in the form of functional units. The term "unit" herein may refer to an application specific integrated circuit (application specific integrated circuit, ASIC), an electronic circuit, a processor (e.g., a shared, dedicated, or group processor, etc.) and memory that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable components that support the described functionality. In an alternative example, it will be understood by those skilled in the art that the apparatus 1000 may be specifically configured as a session management network element in the foregoing embodiments (such as a session management network element in a home network, and a session management network element in a visited network, for example), and may be configured to perform each flow and/or step corresponding to the session management network element in the foregoing method embodiments; alternatively, the apparatus 1000 may be specifically configured as a network element in the foregoing embodiment (such as a network element in a home network), and may be configured to perform each flow and/or step corresponding to the network element in the foregoing method embodiments; alternatively, the apparatus 1000 may be specifically a data management network element in the foregoing embodiment (such as a data management network element in a home network), and may be configured to execute each flow and/or step corresponding to the data management network element in the foregoing method embodiments, which is not described herein for avoiding repetition.

The apparatus 1000 of each of the above embodiments has a function of implementing the corresponding steps performed in the above method (e.g., a session management element in a home network (e.g., a session management element in a visited network), or a network deployment element, or a data management element). The functions may be implemented by hardware, or may be implemented by hardware executing corresponding software. The hardware or software comprises one or more modules corresponding to the functions; for example, the transceiver unit may be replaced by a transceiver (e.g., a transmitting unit in the transceiver unit may be replaced by a transmitter, a receiving unit in the transceiver unit may be replaced by a receiver), and other units, such as a processing unit, etc., may be replaced by a processor, to perform the transceiver operations and related processing operations in the various method embodiments, respectively.

The transceiver 1010 may be a transceiver circuit (e.g., may include a receiving circuit and a transmitting circuit), and the processing unit may be a processing circuit.

It should be noted that the apparatus in fig. 10 may be a network element or a device in the foregoing embodiment, or may be a chip or a chip system, for example: system on chip (SoC). The receiving and transmitting unit can be an input and output circuit and a communication interface; the processing unit is an integrated processor or microprocessor or integrated circuit on the chip. And are not limited herein.

Fig. 11 is a schematic diagram of an apparatus 1100 for providing another communication according to an embodiment of the present application. The apparatus 1100 comprises a processor 1110, the processor 1110 being configured to execute computer programs or instructions stored in a memory 1120 or to read data/signaling stored in the memory 1120 to perform the methods in the method embodiments above. Optionally, the processor 1110 is one or more.

Optionally, as shown in fig. 11, the apparatus 1100 further comprises a memory 1120, the memory 1120 for storing computer programs or instructions and/or data. The memory 1120 may be integral with the processor 1110 or may be separate. Optionally, the memory 1120 is one or more.

Optionally, as shown in fig. 11, the apparatus 1100 further comprises a transceiver 1130, the transceiver 1130 being for receiving and/or transmitting signals. For example, the processor 1110 is configured to control the transceiver 1130 to receive and/or transmit signals.

As an option, the apparatus 1100 is configured to implement the operations performed by the session management network element in the above method embodiments.

For example, the processor 1110 is configured to execute a computer program or instructions stored in the memory 1120 to implement the relevant operations of the session management network element in the home network in the above method embodiments. For example, the method performed by a session management network element in the home network in the embodiment shown in fig. 3, or the method performed by the H-SMF in any of the embodiments shown in fig. 4 to 9.

As another example, the processor 1110 is configured to execute a computer program or instructions stored in the memory 1120 to implement the relevant operations of the session management network element in the visited network in the above method embodiments. For example, the method performed by a session management network element in the visited network in the embodiment shown in fig. 3, or the method performed by the V-SMF in any of the embodiments shown in fig. 4 to 9.

Alternatively, the apparatus 1100 is configured to implement the operations performed by the network element in the method embodiments above.

For example, the processor 1110 is configured to execute computer programs or instructions stored in the memory 1120 to implement the relevant operations of the network-opening network element in the home network in the above method embodiments. For example, the method performed by a network-open network element in the home network in the embodiment shown in fig. 3, or the method performed by the H-NEF in any of the embodiments shown in fig. 4 to 9.

Alternatively, the apparatus 1100 is configured to implement the operations performed by the data management network element in the method embodiments above.

For example, the processor 1110 is configured to execute computer programs or instructions stored in the memory 1120 to implement the relevant operations of the data management network element in the home network in the above method embodiments. For example, the method performed by a data management network element in the home network in the embodiment shown in fig. 3, or the method performed by the H-UDR in any of the embodiments shown in fig. 4 to 9.

It should be appreciated that the processors referred to in embodiments of the present application may be central processing units (central processing unit, CPU), but may also be other general purpose processors, digital signal processors (digital signal processor, DSP), application specific integrated circuits (application specific integrated circuit, ASIC), off-the-shelf programmable gate arrays (field programmable gate array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

It should also be understood that the memory referred to in embodiments of the present application may be volatile memory and/or nonvolatile memory. The nonvolatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an electrically Erasable EPROM (EEPROM), or a flash memory. The volatile memory may be random access memory (random access memory, RAM). For example, RAM may be used as an external cache. By way of example, and not limitation, RAM includes the following forms: static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous DRAM (SLDRAM), and direct memory bus RAM (DR RAM).

It should be noted that when the processor is a general purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, the memory (storage module) may be integrated into the processor.

It should also be noted that the memory described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

Fig. 12 is a schematic diagram of a chip system 1200 according to an embodiment of the application. The system-on-chip 1200 (or may also be referred to as a processing system) includes logic 1210 and input/output interface 1220.

Logic 1210 may be a processing circuit in system-on-chip 1200, among other things. Logic 1210 may be coupled to the memory unit to invoke instructions in the memory unit so that system-on-chip 1200 can implement the methods and functions of embodiments of the present application. The input/output interface 1220 may be an input/output circuit in the chip system 1200, and outputs information processed by the chip system 1200, or inputs data or signaling information to be processed into the chip system 1200 for processing.

Specifically, for example, if the H-SMF is installed in the chip system 1200, the logic circuit 1210 is coupled to the input/output interface 1220, and the logic circuit 1210 may send a request message through the input/output interface 1220, where the request message may be generated by the logic circuit 1210 according to the first information; or the input/output interface 1220 may input the first information from the V-SMF to the logic circuit 1210 for processing. For another example, if the V-SMF is installed with the system-on-chip 1200, the logic 1210 is coupled to the input/output interface 1220, and the logic 1210 may send first information to the H-SMF through the input/output interface 1220, where the first information may be generated by the logic 1210.

As an aspect, the chip system 1200 is configured to implement the operations performed by the session management network element in the method embodiments above.

For example, the logic 1210 is configured to implement the operations related to processing performed by the session management network element in the home network in the above method embodiment, e.g., the operations related to processing performed by the session management network element in the home network in the embodiment shown in fig. 3, or the operations related to processing performed by the H-SMF in any of the embodiments shown in fig. 4 to 9; the input/output interface 1220 is configured to implement the operations related to transmission and/or reception performed by the session management network element in the home network in the above method embodiment, for example, the operations related to transmission and/or reception performed by the session management network element in the home network in the embodiment shown in fig. 3, or the operations related to transmission and/or reception performed by the H-SMF in the embodiment shown in any of fig. 4 to 9.

As another example, the logic 1210 is configured to implement the operations related to the processing performed by the session management network element in the visited network in the method embodiment, for example, the operations related to the processing performed by the session management network element in the visited network in the embodiment shown in fig. 3, or the operations related to the processing performed by the V-SMF in the embodiment shown in any of fig. 4 to 9; the input/output interface 1220 is configured to implement the operations related to transmission and/or reception performed by the session management network element in the visited network in the above method embodiment, for example, the operations related to transmission and/or reception performed by the session management network element in the visited network in the embodiment shown in fig. 3, or the operations related to transmission and/or reception performed by the V-SMF in the embodiment shown in any of fig. 4 to 9.

Alternatively, the chip system 1200 is configured to implement the operations performed by the network element in the method embodiments above.

For example, the logic 1210 is configured to implement the operations related to the processing performed by the network-open network element in the home network in the above method embodiment, e.g., the operations related to the processing performed by the network-open network element in the home network in the embodiment shown in fig. 3, or the operations related to the processing performed by the H-NEF in the embodiment shown in any of fig. 4 to 9; the input/output interface 1220 is configured to implement the operations related to transmission and/or reception performed by a network-wide network element in the home network in the above method embodiment, e.g., the operations related to transmission and/or reception performed by a network-wide network element in the home network in the embodiment shown in fig. 3, or the operations related to transmission and/or reception performed by the H-NEF in the embodiment shown in any of fig. 4 to 9.

Alternatively, the chip system 1200 is configured to implement the operations performed by the data management network element in the method embodiments above.

For example, the logic 1210 is configured to implement the operations related to processing performed by the data management network element in the home network in the above method embodiment, e.g., the operations related to processing performed by the data management network element in the home network in the embodiment shown in fig. 3, or the operations related to processing performed by the H-UDR in any of the embodiments shown in fig. 4 to 9; the input/output interface 1220 is configured to implement the operations related to transmission and/or reception performed by a data management network element in the home network in the above method embodiment, for example, the operations related to transmission and/or reception performed by a data management network element in the home network in the embodiment shown in fig. 3, or the operations related to transmission and/or reception performed by the H-UDR in the embodiment shown in any one of fig. 4 to 9.

The embodiments of the present application further provide a computer readable storage medium having stored thereon computer instructions for implementing the method performed by the network element in the above method embodiments.

For example, the computer program when executed by a computer, enables the computer to implement the method performed by a session management network element (e.g. a session management network element in a home network, and a session management network element in a visited network) in the embodiments of the method described above.

As another example, the computer program when executed by a computer may enable the computer to implement the method performed by a network-opening network element (e.g., a network-opening network element in a home network) in the above-described method embodiments.

As another example, the computer program when executed by a computer may enable the computer to implement the method performed by a data management network element (e.g., a data management network element in a home network) in the embodiments of the method described above.

Embodiments of the present application also provide a computer program product comprising instructions which, when executed by a computer, implement a method performed by a network element (e.g., a session management network element in a home network (e.g., a session management network element in a visited network), or a network deployment network element, or a data management network element) in the above method embodiments.

The embodiment of the application also provides a communication system, which comprises one or more of the session management network element in the home network, the session management network element in the visit network, the network opening network element in the home network, the strategy control network element or the data management network element (such as the data management network element in the home network and the data management network element in the visit network). Optionally, the system further includes a device that communicates with one or more network elements. For example, at least one of the following may be included in the system: terminal equipment, EASDF (e.g., EASDF in the home network), etc.

The explanation and beneficial effects of the related content in any of the above-mentioned devices can refer to the corresponding method embodiments provided above, and are not repeated here.

In the several embodiments provided by the present application, it should be understood that the disclosed apparatus and method may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Furthermore, the coupling or direct coupling or communication connection shown or discussed with each other may be through some interface, device or unit indirect coupling or communication connection, which may be in electrical, mechanical or other form.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, produces a flow or function in accordance with embodiments of the present application, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. For example, the computer may be a personal computer, a server, or a network device, etc. The computer instructions may be stored in or transmitted from one computer-readable storage medium to another, for example, by wired (e.g., coaxial cable, optical fiber, digital Subscriber Line (DSL)), or wireless (e.g., infrared, wireless, microwave, etc.). The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains an integration of one or more available media. For example, the aforementioned usable media include, but are not limited to, U disk, removable hard disk, read-only memory (ROM), random access memory (random access memory, RAM), magnetic disk or optical disk and other various media that can store program code.

The foregoing is merely illustrative of the present application, and the present application is not limited thereto, and any person skilled in the art will readily recognize that variations or substitutions are within the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method of communication, comprising:

a session management network element in a home network receives first information corresponding to terminal equipment from a session management network element in a visited network, wherein the first information is used for indicating the deployment position of an Edge Application Server (EAS) in the visited network;

and the session management network element in the home network acquires the EAS deployment information corresponding to the first information according to the first information.

2. The method according to claim 1, wherein the first information corresponding to the terminal device includes: the first information is determined from the location of the terminal device.

3. The method of claim 2, wherein the first information is determined based on a location of the terminal device, comprising: the first information is used for indicating: and allowing the terminal equipment to access the deployment position of the EAS in the deployment position of the EAS determined according to the position of the terminal equipment.

4. A method according to any one of claims 1 to 3, wherein the session management network element in the home network obtains EAS deployment information corresponding to the first information according to the first information, comprising:

a session management network element in the home network sends a request message to a data management network element in the home network, wherein the request message comprises the first information, and the request message is used for requesting to acquire the EAS deployment information corresponding to the first information;

the session management network element in the home network receives EAS deployment information corresponding to the first information from a data management network element in the home network.

5. A method according to any one of claims 1 to 3, wherein the session management network element in the home network obtains EAS deployment information corresponding to the first information according to the first information, comprising:

a session management network element in the home network sends a request message to a data management network element in the visit network, wherein the request message comprises the first information, and the request message is used for requesting to acquire the EAS deployment information corresponding to the first information;

and the session management network element in the home network receives the EAS deployment information corresponding to the first information from the data management network element in the visited network.

6. The method according to claim 4 or 5, characterized in that the request message further comprises an identification of the visited network.

7. The method according to any one of claims 1 to 6, further comprising:

and the session management network element in the home network determines a Domain Name System (DNS) processing rule according to the EAS deployment information corresponding to the first information, wherein the DNS processing rule is used for processing DNS messages.

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

a session management network element in the home network receives an identification of the visited network from a session management network element in the visited network.

9. A method of communication, comprising:

a session management network element in a visiting network determines first information corresponding to terminal equipment according to the position of the terminal equipment, wherein the first information is used for indicating the deployment position of an Edge Application Server (EAS) in the visiting network;

and the session management network element in the visiting network sends the first information to the session management network element in the home network.

10. The method of claim 9, wherein the first information is used to obtain EAS deployment information corresponding to the first information.

11. The method according to claim 9 or 10, wherein the first information is used to indicate: a deployment location of the EAS that allows the terminal device to access, from among deployment locations of EAS determined from the location of the terminal device;

the session management network element in the visiting network determines first information corresponding to the terminal equipment according to the position of the terminal equipment, and the method comprises the following steps:

and the session management network element in the visiting network determines first information corresponding to the terminal equipment according to the position of the terminal equipment and policy information, wherein the policy information is used for indicating the deployment position of the EAS (electronic article surveillance) which is allowed to be sent to the home network by the visiting network.

12. The method according to claim 9 or 10, wherein the first information is used to indicate: a deployment location of the EAS that allows the terminal device to access, from among deployment locations of EAS determined from the location of the terminal device;

the session management network element in the visiting network determines second information corresponding to the terminal equipment according to the position of the terminal equipment;

A session management network element in the visiting network sends a request message to a policy control network element in the visiting network, wherein the request message comprises the second information, and the request message is used for requesting a deployment position of an EAS (EAS) which allows the visiting network to send to the home network;

the session management network element in the visited network receives the first information from the policy control network element in the visited network, the first information being determined from the second information.

13. The method according to any one of claims 9 to 12, further comprising:

and the session management network element in the visiting network sends the identification of the visiting network to the session management network element in the home network.

14. A method of communication, comprising:

a data management network element in a home network receives a request message from a session management network element in the home network, wherein the request message comprises first information corresponding to terminal equipment, the first information is used for indicating the deployment position of an Edge Application Server (EAS) in a visiting network, and the request message is used for requesting to acquire the EAS deployment information corresponding to the first information;

And the data management network element in the home network sends the EAS deployment information corresponding to the first information to the session management network element in the home network.

15. The method of claim 14 wherein the request message further comprises an identification of the visited network, the method further comprising:

and the data management network element in the home network determines the EAS deployment information corresponding to the first information according to the identification of the visiting network and the first information.

16. The method according to claim 14 or 15, characterized in that the method further comprises:

and the data management network element in the home network locally stores the EAS deployment information corresponding to the first information.

17. An apparatus for communication, the apparatus comprising: means for performing the method of any one of claims 1 to 8, or means for performing the method of any one of claims 9 to 13, or means for performing the method of any one of claims 14 to 16.

18. An apparatus for communication, comprising:

a processor for executing a computer program stored in a memory to cause the apparatus to perform the method of any one of claims 1 to 8 or to cause the apparatus to perform the method of any one of claims 9 to 13 or to cause the apparatus to perform the method of any one of claims 14 to 16.

19. The apparatus of claim 18, further comprising the memory.

20. A computer readable storage medium, characterized in that the computer readable storage medium has stored thereon a computer program which, when run on a computer, causes the computer to perform the method of any of claims 1 to 8, or to cause the computer to perform the method of any of claims 9 to 13, or to cause the computer to perform the method of any of claims 14 to 16.

21. A computer program product comprising instructions for performing the method of any one of claims 1 to 8, or for performing the method of any one of claims 9 to 13, or for performing the method of any one of claims 14 to 16.

22. A system for communication, comprising any one of:

a session management network element in a home network for communicating with the session management network element in the home network, one or more of: a data management network element in the home network, a session management network element in a visiting network and a data management network element in the visiting network; or alternatively, the process may be performed,

A session management network element in a visited network, one or more of the following for communicating with the session management network element in the visited network: a session management network element in a home network and a policy control network element in the visited network;

wherein the session management network element in the home network is for performing the method according to any of claims 1 to 8, the session management network element in the visited network is for performing the method according to any of claims 9 to 13, and the data management network element in the home network is for performing the method according to any of claims 14 to 16.