A communication method and apparatus
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-01-26
- Publication Date
- 2026-08-11
AI Technical Summary
在归属路由(Home-Route,HR)的漫游(roaming)场景中访问拜访域的MEC业务,按照当前HR漫游的流程,漫游接入过程中所建立的会话的锚点在归属域公共陆地移动网络(home public land mobile network,HPLMN)部署的用户面网元,从而无法向拜访域路由
[0044]上述第七方面至第十三方面及其实现方式的有益效果可以参考对第一方面至第六方面,或第一方面至第六方面及其实现方式的有益效果的描述。
Smart Images

Figure CN116546479B_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of roaming technology, and more particularly to a communication method and apparatus for home route roaming. Background Technology
[0002] Multi-access edge computing (MEC) refers to providing users with faster services and better network performance by deploying MEC computing capabilities close to the device. In a Home-Route (HR) roaming scenario, when accessing MEC services in the visited domain, according to the current HR roaming process, the anchor point of the session established during roaming access is the user plane network element deployed in the home public land mobile network (HPLMN), thus preventing routing to the visited domain. Summary of the Invention
[0003] This application provides a communication method and apparatus for implementing routing to a visited domain.
[0004] Firstly, a first communication method is provided, which can be executed by a first communication device. The first communication device can be a communication equipment or a communication device capable of supporting the functions required for the method to be implemented, such as a chip system. For example, the communication equipment is an edge configuration server. The following description uses the example of an edge configuration server as the communication equipment. The method includes: the first edge configuration server receiving a first request message, sending an application function request message to a policy control function network element, and sending a response message to the first request message. The first request message includes configuration information of the application client. The application function request message is used to request a data forwarding path from the terminal to the first visited domain edge enable server and / or the first visited domain edge configuration server.
[0005] This scheme involves the first edge configuration server sending an application function request message to the policy control function, requesting configuration of the data forwarding path from the terminal to the first visited domain edge enabling server and / or the first visited domain edge configuration server. Consequently, messages sent by the roaming terminal to the edge enabling server and / or edge configuration server in the visited domain can be routed to the visited domain, rather than being forwarded to the user plane function network elements of the home domain. This facilitates interaction between the roaming terminal and the visited domain edge enabling server and / or the visited domain edge configuration server. For example, a request sent by the roaming terminal to query an edge application server can be routed to the visited domain edge enabling server and / or visited domain edge configuration server, thereby enabling edge application server discovery and supporting the roaming terminal's access to edge application services in the visited domain's public terrestrial mobile network.
[0006] In one possible implementation, the application function request message may include the address information of the first visited domain edge enabling server and / or the address information of the first visited domain edge configuration server. That is, the application function request message enables the policy control function network element to explicitly configure the data forwarding path of the terminal to which visited domain edge configuration server or which visited domain edge enabling server.
[0007] In one possible implementation, before sending the response message, the first edge configuration server also receives a user plane path change notification from the visited domain session management function. It is understood that the user plane path of the session established by the roaming terminal may change, for example, the data forwarding path from the terminal to the visited domain edge enabling server V-EES and / or the visited domain edge configuration server V-ECS may be configured. Through this scheme, the visited domain session management function can inform the first edge configuration server when the user plane path of the session established by the roaming terminal changes. The first edge configuration server receives the user plane path change notification from the visited domain session management function and then sends a response message. That is, the first edge configuration server determines that the data forwarding path from the terminal to the edge enabling server and / or edge configuration server in the visited domain is configured and then sends back a response message for the first request message. For the roaming terminal, it can be guaranteed that the user plane path has been configured when the response message is received, thus enabling subsequent data to be sent (e.g., requests to query the edge application server) to be successfully sent to the edge enabling server and / or edge configuration server in the visited domain.
[0008] In one possible implementation, the response message includes configuration information for a first visited domain edge configuration server and / or configuration information for a second visited domain edge enabling server. The configuration information for the first visited domain edge configuration server can indicate the first visited domain edge configuration server, and the configuration information for the first visited domain edge enabling server can indicate the first visited domain edge enabling server. For example, after determining the first visited domain edge enabling server and / or the first visited domain edge configuration server, the terminal can be notified so that the terminal can request the discovery of edge application servers from the first visited domain edge configuration server, reducing the failure rate of requesting the discovery of edge application servers.
[0009] In one possible implementation, the first edge configuration server determines the first visited domain edge enabling server and / or the first visited domain edge configuration server based on the application client's configuration information. For example, the application client's configuration information may include roaming identifiers, terminal device information, etc. The first edge configuration server can clearly identify the first visited domain edge enabling server and / or the first visited domain edge configuration server based on the application client's configuration information. The first visited domain edge enabling server can also be considered as the visited domain edge enabling server that supports the services requested by the terminal. Similarly, the first visited domain edge configuration server is the visited domain edge configuration server for the services requested by the terminal. Through this scheme, the first edge configuration server can select appropriate visited domain edge configuration servers and visited domain edge enabling servers according to application requirements, avoiding failures in discovering edge application servers.
[0010] In one possible implementation, if the first edge configuration server is a first visited domain edge configuration server or a second visited domain edge configuration server, the first edge configuration server receiving the first request message includes the first edge configuration server receiving the first request message from the home domain edge configuration server; the first edge configuration server sending a response message to the first request message includes the first edge configuration server sending the response message to the home domain edge configuration server.
[0011] In one possible implementation, if the first edge configuration server is a first visited domain edge configuration server or a second visited domain edge configuration server, the first edge configuration server receiving the first request message includes the first edge configuration server receiving the first request message from the terminal; the first edge configuration server sending a response message in response to the first request message includes the first edge configuration server sending the response message to the terminal.
[0012] In one possible implementation, the first edge configuration server is either a first visited domain edge configuration server or a second visited domain edge configuration server, and the policy control function network element is a visited domain policy control function network element.
[0013] In another possible implementation, the first edge configuration server is a home domain edge configuration server, and the policy control function network element is a home domain policy control function network element. The edge configuration server and the policy control function network element interact either in the visited domain or in the home domain, reducing the number of information exchanges and simplifying the interaction process.
[0014] In one possible implementation, the first edge configuration server is a home domain edge configuration server, which obtains the first visited domain edge enabling server and / or first visited domain edge configuration server information from the third visited domain edge configuration server.
[0015] Secondly, a second communication method is provided, which can be executed by a second communication device. The second communication device can be a communication equipment or a communication device capable of supporting the functions required for the method, such as a chip system. For example, the communication equipment is a policy control function network element. The following description uses the policy control function network element as an example. The method includes: the policy control function network element receiving an application function request and sending a second request message to a visited domain session management function network element according to the application function request. The application function request configures the data forwarding path from the terminal to a first visited domain edge enabling server and / or a first visited domain edge configuration server. The second request message includes the address information of the first visited domain edge enabling server and / or the address information of the first visited domain edge configuration server.
[0016] In one possible implementation, the AF request includes the address information of the first visited domain edge enabling server and / or the address information of the first visited domain edge configuration server.
[0017] For the technical effects of the second aspect or its various implementations, please refer to the introduction of the technical effects of the first aspect or its corresponding implementations.
[0018] Thirdly, a third communication method is provided, which can be executed by a third communication device. This third communication device can be a communication equipment or a communication device capable of supporting the functions required for the method to be implemented, such as a chip system. For example, the communication equipment is a visited domain session management function network element. The following description uses the visited domain session management function network element as an example. The method includes: the visited domain session management function network element receiving a second request message from a policy control function network element, and configuring a data forwarding path to the visited domain user plane function network element. The second request message is used to configure the data forwarding path from the terminal to the first visited domain edge enable server and / or the first visited domain edge configuration server.
[0019] In a possible implementation, the second request message includes the address information of the first visited domain edge enabling server and / or the address information of the first visited domain edge configuration server.
[0020] For the technical effects of the third aspect or its various implementations, please refer to the introduction of the technical effects of the first aspect or its corresponding implementations.
[0021] Fourthly, a fourth communication method is provided, which can be executed by a first communication device. The first communication device can be a communication equipment or a communication device capable of supporting the functions required for the method to be implemented, such as a chip system. For example, the communication equipment is a data management network element. The following description uses the example of the communication equipment being a visitor domain policy control function network element. The method includes:
[0022] The data management network element receives an application function request from the edge configuration server and stores the address information of the first visited domain edge configuration server and / or the address information of the first visited domain edge enabling server according to the application function request. The application function request includes one or more of the following: the address information of the first visited domain edge configuration server and / or the address information of the first visited domain edge enabling server, a roaming identifier, a terminal identifier, or a session identifier. The roaming identifier indicates whether the terminal is a roaming terminal. The terminal identifier includes one or more of the following: a generic public subscription identifier (GPSI), a subscription permanent identifier (SUPI), a data network name (DNN), or single network slice selection assistance information (S-NSSAI), or the terminal's application descriptor. The session identifier includes the terminal's corresponding DNN, S-NSSAI, and / or application descriptor, etc. In this scheme, the edge configuration server can send the address information of the visited domain edge configuration server and / or the address information of the visited domain edge enabling server that supports roaming edge computing to the data management network element for storage via application function requests. This enables the visited domain policy control function network element to provide the visited domain edge configuration server and / or visited domain edge enabling server corresponding to the roaming terminal, allowing the visited domain policy control function network element to clearly define which visited domain edge configuration server or which visited domain edge enabling server the requested terminal should use for data forwarding. This facilitates subsequent interaction between the roaming terminal and the first visited domain edge enabling server and / or the first visited domain edge configuration server. For example, a request sent by the roaming terminal to query the edge application server can be routed to the first visited domain edge enabling server and / or the first visited domain edge configuration server, thereby achieving edge application server discovery and enabling the roaming terminal to access edge application services in the visited domain public terrestrial mobile network.
[0023] In a possible implementation, the method further includes: a data management network element receiving a subscription request message from a visited domain policy control function network element, and sending a notification message to the visited domain policy control function network element. The subscription request message is used to request subscription to a notification message for an application function request associated with the terminal's first home routing session. The notification message includes the address information of the first visited domain edge configuration server and / or the address information of the first visited domain edge enable server associated with the first home routing session.
[0024] Fifthly, a fifth communication method is provided, which can be executed by a fifth communication device. This fifth communication device can be a communication equipment or a communication device capable of supporting the functions required for the method to be implemented, such as a chip system. For example, the communication equipment is a policy control function network element. The following description uses the example of the communication equipment being a visited domain policy control function network element. The method includes:
[0025] The visited domain policy control function network element receives a first request message from the visited domain session management function network element, obtains the address information of the first visited domain edge configuration server and / or the address information of the first visited domain edge enabling server associated with the first home routing session from the data management network element, and sends a first response message to the visited domain session management function network element. The first request message instructs the terminal's first home routing session to request the use of the edge computing function of the visited domain's public terrestrial mobile network. The first response message includes the address information of the first visited domain edge configuration server and / or the address information of the first visited domain edge enabling server. It is understood that the first visited domain edge configuration server and / or the first visited domain edge enabling server associated with the first home routing session enables the terminal to be routed to the visited domain. In this scheme, the data management network element can store the correspondence between the roaming terminal and the address information of the first visited domain edge configuration server and / or the first visited domain edge enabling server based on the application function request. The visited domain policy control function network element can query the data management network element for the visited domain edge configuration server and / or visited domain edge enable server associated with the first home routing session, and notify the visited domain session management function network element. This allows the visited domain session management function network element to subsequently request configuration of the terminal to the visited domain edge configuration server and / or visited domain edge enable server associated with the first home routing session, thereby ensuring that the terminal is routed to the visited domain as much as possible.
[0026] In possible implementations, the first request message includes one or more of the following corresponding to the terminal: a general public user identifier, a user permanent identifier, a data network name, or single network slice selection auxiliary information, or an identifier of the first home routing session.
[0027] In a possible implementation, the visited domain policy control function network element obtains the address information of the first visited domain edge configuration server and / or the address information of the first visited domain edge enabling server from the data management network element. This includes: the visited domain policy control function network element sending a subscription request message to the data management network element and receiving a notification message from the data management network element. The subscription request message is used to request subscription to a notification message for an application function request associated with the first visited route session. The notification message includes the address information of the first visited domain edge configuration server and / or the address information of the first visited domain edge enabling server.
[0028] In a possible implementation, the address information of the first visited domain edge configuration server and / or the address information of the first visited domain edge enable server are stored in the data management network element by the edge configuration server through an application function request.
[0029] In a possible implementation, the edge configuration server is either a first visited domain edge configuration server or a second visited domain edge configuration server, and the data management network element is a visited domain data management network element.
[0030] Sixthly, a sixth communication method is provided, which can be executed by a third communication device. The third communication device can be a communication equipment or a communication device capable of supporting the functions required for the method to be implemented, such as a chip system. For example, the communication equipment is a visitor domain session management function network element. The following description uses the example of the communication equipment being a visitor domain session management function network element. The method includes:
[0031] The visited domain session management function network element receives first indication information and sends a first request message to the visited domain policy control function network element, and receives a first response message from the visited domain policy control function network element. The first indication information instructs the terminal's first home routing session to use the edge computing function of the visited domain public land mobile network. The first request message instructs the terminal's first home routing session to use the edge computing function of the visited domain public land mobile network. The first response message includes the address information of the first visited domain edge configuration server associated with the first home route and / or the address information of the first visited domain edge enabling server.
[0032] In a possible implementation, the visited domain session management function network element receives first instruction information, including:
[0033] The visited domain session management function network element receives a session establishment request message from the terminal, the session establishment request including the first indication information; or, the visited domain session management function network element receives a session modification request message from the terminal, the session modification request message including the first indication information.
[0034] In a possible implementation, the method further includes: the visited domain session management function network element configuring rules for forwarding data to the visited domain user plane function network element for forwarding data to the first visited domain edge configuration server and / or the first visited domain edge enable server.
[0035] For the technical effects of the fifth and sixth aspects, please refer to the introduction of the technical effects of the fourth aspect.
[0036] A seventh aspect provides a communication device. The communication device may be any of the communication devices described in the first to sixth aspects. The communication device possesses the functions of the aforementioned communication device. The communication device may be, for example, an edge configuration server (e.g., a visited domain edge configuration server, or a home domain edge configuration server) as described in any of the first to sixth aspects. Alternatively, the communication device may be, for example, a policy control function network element (e.g., a visited domain policy control function network element, or a home domain policy control function network element) as described in any of the first to sixth aspects. Alternatively, the communication device may be, for example, a session management function network element (e.g., a visited domain session management function network element, or a home domain session management function network element) as described in any of the first to sixth aspects. Alternatively, the communication device may be, for example, a data management network element as described in any of the fourth to sixth aspects.
[0037] In one optional implementation, the communication device includes a processing unit (sometimes also called a processing module) and a transceiver unit (sometimes also called a transceiver module). The transceiver unit is capable of both sending and receiving functions. When the transceiver unit performs the sending function, it can be called a sending unit (sometimes also called a sending module); when the transceiver unit performs the receiving function, it can be called a receiving unit (sometimes also called a receiving module). The sending unit and the receiving unit can be the same functional module, which is called the transceiver unit and can perform both sending and receiving functions; alternatively, the sending unit and the receiving unit can be different functional modules, and the transceiver unit is a collective term for these functional modules. These units (modules) can perform the corresponding functions in the method examples described in any of the first to sixth aspects above, as detailed in the method examples, and will not be repeated here.
[0038] Eighthly, embodiments of this application provide a communication device, which may be the communication device described in the eighth aspect of the above embodiments, or a chip or chip system disposed in the communication device described in the eighth aspect. The communication device includes a communication interface and a processor, and optionally, a memory. The memory is used to store computer programs, instructions, or data. The processor is coupled to the memory and the communication interface. When the processor reads the computer program, instructions, or data, it causes the communication device to perform the function of the method described in any one of the first to sixth aspects.
[0039] In a ninth aspect, embodiments of this application provide a communication device including an input / output interface and logic circuitry. The input / output interface is used for inputting and / or outputting information. The logic circuitry is used to execute the methods described in any one of the first to sixth aspects.
[0040] In a tenth aspect, embodiments of this application provide a chip system including a processor, and may further include a memory and / or a communication interface for implementing the methods described in any of the first to sixth aspects. In one possible implementation, the chip system further includes a memory for storing a computer program. The chip system may be composed of chips or may include chips and other discrete devices.
[0041] Eleventhly, embodiments of this application provide a communication system comprising at least two types of communication devices: a communication device capable of implementing the edge configuration server function described in any one of the first to sixth aspects, a communication device capable of implementing the policy control function network element function described in any one of the first to sixth aspects, a communication device capable of implementing the session management function network element function described in any one of the first to sixth aspects, and a communication device capable of implementing the user plane function network element function described in any one of the first to sixth aspects. Optionally, the communication system further includes a communication device capable of implementing the data management network element function described in any one of the fourth to sixth aspects.
[0042] In a twelfth aspect, this application provides a computer-readable storage medium storing a computer program that, when run, implements the methods of any one of the first to sixth aspects described above.
[0043] In a thirteenth aspect, a computer program product is provided, the computer program product comprising: computer program code, which, when run, causes the methods of any one of the first to sixth aspects to be executed.
[0044] The beneficial effects of the seventh to thirteenth aspects and their implementation methods can be referred to the description of the beneficial effects of the first to sixth aspects, or the first to sixth aspects and their implementation methods. Attached Figure Description
[0045] Figure 1 A schematic diagram of the network architecture for a local offloading roaming scenario;
[0046] Figure 2 This is a schematic diagram of the MEC application layer architecture;
[0047] Figure 3 This is a schematic diagram of the EAS discovery process;
[0048] Figure 4 A flowchart illustrating the first communication method provided in an embodiment of this application;
[0049] Figure 5 A flowchart illustrating an example of the first communication method provided in an embodiment of this application;
[0050] Figure 6 A flowchart illustrating another example of the first communication method provided in the embodiments of this application;
[0051] Figure 7 A flowchart illustrating the second communication method provided in an embodiment of this application;
[0052] Figure 8 A schematic diagram of the structure of a communication device provided in an embodiment of this application;
[0053] Figure 9 This is another schematic diagram of the communication device provided in the embodiments of this application. Detailed Implementation
[0054] The technical solutions provided in this application can be applied to various communication systems, such as 5th generation (5G) systems, including new radio (NR) systems. The technical solutions provided in this application can also be applied to future communication systems, such as 6th generation mobile communication systems. Furthermore, the technical solutions provided in this application can be applied to device-to-device (D2D) communication, vehicle-to-everything (V2X) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), and Internet of Things (IoT) communication systems or other communication systems.
[0055] As an example, please see Figure 1 This is a schematic diagram of a network architecture applicable to embodiments of this application. The network architecture includes two parts: a home domain public land mobile network (PLN) and a visited domain PPN. The home domain PPN is the public land mobile network subscribed to by the user equipment (UE), representing the subscriber's home operator. The visited domain PPN is the public land mobile network the UE accesses after leaving the coverage area of the home domain PPN. It can be understood that when a UE leaves the coverage area of its home domain PPN due to movement or other reasons, if a public land mobile network meets the following conditions: 1) it can cover the UE's current location, and 2) its operator has signed a roaming agreement with the operator of the UE's home domain PPN, then the UE can access that public land mobile network, which is the visited domain PPN. The UE's access to the visited domain PPN is called roaming. Roaming scenarios can be divided into local breakout (LBO) roaming and HR roaming. Figure 1 Take the HR roaming architecture as an example.
[0056] The visited domain public terrestrial mobile network includes network slice selection elements, policy control elements, access management elements, and session management elements. These elements can communicate with each other using a service-based approach. Furthermore, access management elements can communicate with the UE via the N1 interface, access management elements can communicate with the access network via the N2 interface, session management elements can communicate with user plane elements via the N4 interface, the UE can communicate with the access network, the access network and user plane elements can communicate via the N3 interface, and user plane elements can communicate with the data network via the N6 interface.
[0057] The home domain public land mobile network includes unified data management network elements, session management network elements, policy control network elements, and application network elements. These network elements can communicate with each other based on service methods. The authentication service network element and the unified data management network element can communicate through the N13 interface, the unified data management network element and the session management network element can communicate through the N10 interface, the session management network element and the policy control network element can communicate through the N7 interface, the policy control network element and the AF (Automatic Access Controller) can communicate through the N5 interface, and the session management network element and the user plane network element can communicate through the N4 interface. During roaming, the UE accesses the visited domain public land mobile network. The visited domain public land mobile network and the access management network elements and session management network elements within the home domain public land mobile network communicate with each other, enabling network elements within the visited domain public land mobile network to communicate with network elements within the home domain public land mobile network.
[0058] It is understandable that the visited domain public land mobile network and the home domain public land mobile network may both have the same functional network elements. For example, the visited domain public land mobile network includes a session management function (SMF), and the home domain public land mobile network also includes an SMF. To distinguish between the visited domain public land mobile network and the home domain public land mobile network, network elements in the visited domain public land mobile network are denoted as visited network elements, and network elements in the home domain public land mobile network are denoted as home network elements. For example, the SMF included in the visited domain public land mobile network is denoted as the visited domain SMF (V-SMF), and the SMF included in the home domain public land mobile network is denoted as the home domain SMF (H-SMF).
[0059] The following is about Figure 1 A brief introduction to each device shown in the image is provided.
[0060] 1) UE, possessing wireless transceiver capabilities, can send signals to or receive signals from network devices. User equipment, sometimes also called terminal equipment, includes terms like terminal, access station, UE station, remote station, wireless communication device, or user device. In this application embodiment, the terminal device is used to connect people, things, machines, etc., and can be widely used in various scenarios, including but not limited to the following: cellular communication, device-to-device (D2D), V2X, machine-to-machine / machine-type communications (M2M / MTC), Internet of Things (IoT), virtual reality (VR), augmented reality (AR), industrial control, self-driving, remote medical, smart grid, smart furniture, smart office, smart wearables, smart transportation, smart city, drones, robots, etc. As an example and not a limitation, in the embodiments of this application, the terminal device can also be a wearable device. In addition, in this application embodiment, the terminal device can refer to a device for implementing the functions of a terminal, or a device that supports the terminal device in implementing those functions, such as a chip system, which can be installed in the terminal device. For example, the terminal device can also be a vehicle detector. In this application embodiment, the chip system can be composed of chips, or it can include chips and other discrete devices. In the technical solutions provided in this application embodiment, the terminal device is used as an example to describe the technical solutions provided in this application embodiment. It should be noted that in this application embodiment, the terminal or terminal device is described using UE as an example, but the user equipment can also have other names, and this application embodiment does not limit it.
[0061] 2) Access network equipment, including access network equipment and / or core network equipment through which terminal equipment wirelessly accesses the mobile communication system. Access network equipment includes, for example, radio access network (RAN) equipment. Access network equipment includes, but is not limited to, evolved Node Bs (eNBs or e-NodeBs) in LTE systems or Long Term Evolution-Advanced (LTE-A) systems. An eNB is a device deployed in a radio access network that meets the fourth-generation (4G) standard to provide wireless communication functions for terminal equipment. Network equipment can also be a new radio controller (NR controller), which can be a gNodeB (gNB) in a 5G system, a centralized unit, a new radio base station, a remote radio module, a micro base station (also known as a small cell), a relay, a distributed unit, various forms of macro base stations, a transmission reception point (TRP), a transmission measurement function (TMF), a transmission point (TP), or any other wireless access device. Network equipment can also include a radio network controller (RNC), a wireless fidelity (Wi-Fi) access point (AP), or a baseband unit (BBU) pool and RRU in a cloud radio access network (CRAN). The embodiments of this application do not limit the specific technologies or equipment forms used in the network equipment. In a 4G system, network equipment can correspond to an eNB, and in a 5G system, it can correspond to a gNB. Furthermore, the base station in this embodiment may include a centralized unit (CU) and a distributed unit (DU), and multiple DUs can be centrally controlled by a single CU.In some embodiments, the control plane (CP) and user plane (UP) of the CU can be separated and implemented as different entities, namely the control plane CU entity (CU-CP entity) and the user plane CU entity (CU-UP entity). Taking a 5G system as an example, the core network equipment includes: access and mobility management function (AMF), unified data management (UDM), or UPF, etc.
[0062] 3) The access management network element is mainly used for terminal attachment, mobility management, and tracking area update procedures in mobile networks. It terminates non-access stratum (NAS) messages, completes registration management, connection management, reachability management, allocates tracking area lists (TA lists), and performs mobility management, and transparently routes session management (SM) messages to the session management network element. In 5G communication systems, the access management network element can be the access and mobility management function (AMF). In future communication systems (such as 6G communication systems), the access and mobility management network element can still be the AMF element, or it can have other names; this application is not limited to these.
[0063] 4) Session management network elements are mainly used for session management in mobile networks, such as session establishment, modification, and release. Specific functions include allocating Internet Protocol (IP) addresses to terminals and selecting user plane network elements that provide packet forwarding functions. In 5G communication systems, session management network elements can be SMF network elements. In future communication systems (such as 6G communication systems), session management network elements can still be SMF network elements, or they can have other names; this application does not limit this.
[0064] 5) User plane network elements are mainly used for processing user packets, such as forwarding, billing, and lawful interception. User plane network elements can also be called protocol data unit (PDU) session anchors (PSA). In 5G communication systems, user plane network elements can be user plane functions (UPFs). In future communication systems (such as 6G communication systems), user plane network elements can still be UPF network elements, or they can have other names; this application does not limit this.
[0065] 6) The policy control network element has functions such as user subscription data management, policy control, billing policy control, and quality of service (QoS) control. In 5G communication systems, the policy control network element can be a PCF (Policy Control Function). In future communication systems (such as 6G communication systems), the policy control network element can still be a PCF network element, or it can have other names; this application is not limited to these.
[0066] 7) Authentication service network element, mainly used for security authentication of terminal devices. In 5G communication systems, the authentication service network element can be an authentication server function (AUSF). In future communication systems (such as 6G communication systems), the authentication service network element can still be an AUSF network element, or it can have other names. This application does not limit it.
[0067] 8) A data management network element, primarily used for storing and / or managing subscription information, policy information, etc., of terminal devices. This data management network element can be a unified data management network element and / or a unified data storage network element. For example, in a 5G communication system, the unified data management network element can be a unified data management (UDM) network element. In future communication systems (such as 6G communication systems), this unified data management network element may still be a UDM network element, or it may have other names; this application is not limited to this. Similarly, in a 5G communication system, the unified data storage network element can be a unified data repository (UDR) network element. In future communication systems (such as 6G communication systems), this unified data storage network element may still be a UDR network element, or it may have other names; this application is not limited to this.
[0068] 9) Network capability open elements can expose some network functions to applications in a controlled manner. In 5G communication systems, network capability open elements can be NEF. In future communication systems (such as 6G communication systems), network capability open elements can still be NEF elements, or they can have other names. This application does not limit this.
[0069] 10) Data network (DN) is primarily used by carrier networks to provide data services to UEs. Examples include the Internet, third-party service networks, and IP Multimedia Service (IMS) networks.
[0070] It should be understood that the aforementioned network elements may be network components in hardware devices, software functions running on dedicated hardware, or virtualization functions instantiated on a platform (e.g., a cloud platform).
[0071] For ease of explanation, this application uses the following examples: Access Management Network Element (AMF), Session Management Network Element (SMF), Unified Data Storage Network Element (UDR), Unified Data Management Network Element (UDM), and Policy Control Network Element (PCF). Further, AMF, SMF, UDR, UDM, and PCF will be abbreviated as AMF, SMF, UDR, UDM, and PCF, respectively. That is, in the following descriptions, AMF can be replaced with Access Management Network Element, SMF with Session Management Network Element, UDR with Unified Data Storage Network Element, UDM with Unified Data Management Network Element, and PCF with Policy Control Network Element.
[0072] To facilitate understanding of the technical solutions provided in the embodiments of this application by those skilled in the art, the technical solutions related to the embodiments of this application are described below. First, the content related to MEC is introduced.
[0073] MEC can be understood as an edge-based big data processing platform. It involves breaking down traditional data centers into smaller, more manageable nodes (servers) and placing them at the network's edge to be closer to users, providing faster service and better network performance. In other words, MEC offloads the computing load from the endpoint to computing servers at the network edge, providing near-cloud-level computing, storage, and processing capabilities.
[0074] Please see Figure 2This is a schematic diagram of the MEC architecture. The UE side includes one or more application clients (ACs) and one or more edge enabler clients (EECs). An application client can be considered an application residing on the terminal, used to perform client functions. The network edge side includes the edge data network (EDN) and the edge configuration server (ECS). The EDN is a local data network, including the edge application server (EAS) and the edge enabler server (EES). The EES supports the invocation and open functions of the application programming interface (API) specified in 3GPP TS 23.222, and can be used to provide the support functions required by the EAS and EEC. For example, the EES can provide EAS configuration information to the AC through the EEC, so that the AC can interact with the EAS to exchange application layer data traffic. For another example, the EES can also receive EAS registration information. The EEC can be used to provide the support functions required by the application client and discover available EAS in the EDN. For example, the EEC is used to obtain and provide configuration information to interact with the EAS to exchange application layer data traffic. ECS provides the support functions required for EEC to connect to EES, such as providing Edge configuration information to EEC. This configuration information may include information needed for EEC to connect to EES, such as service area information applicable to local area data networks (LADNs). This configuration information may also include information for establishing a connection between ECS and EES, such as uniform resource identifiers (URIs). EAS is an application server deployed in EDN, used to perform server functions. EAS may use core network capabilities in different ways. For example, if EAS is a trusted entity of the core network, it can directly call core network function APIs; or EAS can call core network capabilities through EES; or EAS can call core network capabilities through capability exposure functions (such as SCEF or NEF network elements).
[0075] It should be noted that, Figure 2Taking a UE including at least one edge-enabled client as an example, that is, at least one edge-enabled client is deployed in the UE. Interactions between other devices and the edge-enabled client can also be considered as interactions between other devices and the UE. Therefore, in the description of message interaction, etc., in this application, the edge-enabled client can also be replaced by the UE. The embodiments of this application do not limit the deployment location of the edge-enabled client. For example, in the embodiments of this application, the edge-enabled client and the UE can be independent, that is, the edge-enabled client is not deployed within the UE. When the edge-enabled client and the UE are deployed independently, the edge-enabled server can exchange information with the UE, for example, the edge-enabled server can obtain the application client's configuration information (AC profile) from the UE. In the embodiments of this application, unless otherwise specified, the edge-enabled client and the UE are interchangeable.
[0076] This application does not limit the specific names of edge-enabled clients, edge data networks, edge configuration servers, edge application servers, and edge-enabled servers. For example, in a 5G communication system, the edge-enabled client can be an EEC. In future communication systems (such as 6G communication systems), the edge-enabled client can also have other names. For ease of explanation, this application uses the example of an edge-enabled client being an EEC, an edge data network being an EDN, an edge configuration server being an ECS, an edge application server being an EAS, and an edge-enabled server being an EES. That is, in the following descriptions of this application, EEC can be replaced with an edge-enabled client, EDN can be replaced with an edge data network, ECS can be replaced with an edge configuration server, EAS can be replaced with an edge application server, and EES can be replaced with an edge-enabled server.
[0077] The UE can interact with the edge data network through the core network. For example, when an application client connects to the EAS, it can transmit application layer data traffic (which can also be considered as computing tasks) to the EAS, thus leveraging the advantages of edge computing to use application services. When the UE accesses a service, it can request an available EAS to transmit service data packets with the requested EAS. Figure 2 Taking the architecture shown as an example, the EAS discovery process can be referenced. Figure 3 .
[0078] S30 and EEC perform ECS discovery and selection.
[0079] For example, operators can configure ECS addresses in the EEC, allowing the EEC to determine which ECS instances are available. Another example is that the SMF sends a Protocol Configuration Option (PCO) message to the UE, which indicates ECS information. The UE then provides this ECS information to the EEC, enabling the EEC to determine which ECS instances are available.
[0080] S31, EEC sends a service activation request to ECS.
[0081] For example, the EEC sends a service activation request to the ECS after the session is established, based on the ECS's address.
[0082] S32, ECS sends a service activation response to EEC.
[0083] For example, the ECS can send a service activation response to the EEC based on the UE's location information. This service activation response may include a list of available EESs.
[0084] S33, ECS sends an EAS discovery request to EES.
[0085] For example, ECS selects an EES based on the EES list carried in the service activation response and sends an EES discovery request to that EES.
[0086] S34, EES sends an EAS discovery response to EEC.
[0087] In response to the EAS discovery request, the EES sends an EAS discovery response to the EEC. This EAS discovery response includes the available EAS addresses.
[0088] S35. The EES influences traffic routing via AF (Affected AF) to enable core network elements to establish traffic routing rules. These traffic routing rules indicate the data forwarding path from the UE to the EAS. In this embodiment, data routing can also be referred to as service routing, traffic routing, transmission routing, etc. Influence can also be understood as guidance; for example, influencing data routing can also be called guiding data routing.
[0089] S36. The UE transmits service data packets with the EAS based on the traffic splitting rules.
[0090] As mentioned above Figure 3The illustrated process discovers the EAS the UE wants to use and transmits service data packets with it. However, in HR roaming scenarios, the anchor point of the session established during roaming is at the H-UPF. Therefore, the V-UPF does not send data to visited domain network elements (such as V-ECS and / or V-EES). In this case, the data sent by the UE may not be routed to the visited domain. However, the EAS the UE wants to use is located in the visited public land mobile network (VPLMN). The EAS discovery and selection process requires the participation of V-ECS and / or V-EES. Therefore, according to the current HR roaming process, the EAS cannot be discovered for the UE.
[0091] Therefore, the technical solutions of the embodiments of this application are provided. The solutions provided by the embodiments of this application are described below with reference to the accompanying drawings. In the accompanying drawings corresponding to the various embodiments of this application, all steps indicated by dashed lines are optional steps. The various embodiments described below are all applied to... Figure 1 The network architecture shown is an example. It should be noted that the following text uses only this network architecture as an example. Figure 1 The network architecture shown is an example, and the network architecture applicable to the embodiments of this application is not limited to this one. Figure 1 Any network architecture capable of implementing the functions of the aforementioned network elements is applicable to the embodiments of this application. Furthermore, the network architecture shown above may also include other network elements, such as network function (NF) repository function (NRF). The roaming terminal mentioned below may include a terminal located in an HR scenario.
[0092] Please see Figure 4 This is a flowchart illustrating the first communication method provided in this application embodiment, applied to the aforementioned HR scenario. The specific flow of this communication method is described below.
[0093] S401. The first ECS receives a first request message, which includes the application client's configuration information (AC profile).
[0094] When a UE (or EEC) needs to use the MEC function of a VPLMN, it can send a first request message to the first ECS. Correspondingly, the first ECS can receive the first request message from the UE or EEC. This first request message can be used to request the use of the VPLMN's MEC function, or it can be understood as a request to access the VPLMN's MEC service. It is understood that different MEC services correspond to different V-ECS and / or V-EES; that is, V-ECS and MEC services can have a corresponding relationship, and / or V-EES and MEC services can also have a corresponding relationship. From this perspective, the first request message can also be considered as a request to a V-ECS and / or V-EES that supports MEC services. A V-ECS that supports MEC services can also be understood as an available V-ECS. Similarly, a V-EES that supports MEC services can also be understood as an available V-ECS. From this perspective, the first request message can also be used to request an available V-ECS and / or V-EES. It should be understood that an available V-ECS can be a specific V-ECS, a V-ECS determined by the UE, a V-ECS corresponding to the UE, or a V-ECS supporting the service requested by the UE, etc. Similarly, an available V-EES can be a specific V-EES, a V-EES determined by the UE, a V-EES corresponding to the UE, or a V-EES supporting the service requested by the UE, etc. For ease of description, this document refers to the available V-ECS as the first V-ECS and the available V-EES as the first V-EES. It should be noted that the first V-ECS may include one or more V-ECS, and the first V-EES may include one or more V-EES.
[0095] The embodiments of this application do not limit the specific name of the first request message. For example, the first request message may also be called a business request message, or a service provisioning request message. As another example, the first request message may be called an availability request message.
[0096] As an example, the first request message may include application client configuration information (AC profile), based on which the first ECS can determine the first V-EES and / or the first V-ECS. The AC profile may include one or more of the following: roaming identifier, AC ID, a list of EAS that meet the application client's key performance indicators (KPIs), AC type, or expected AC geographical service area, etc. The roaming identifier can be a VPLMN ID or indication information used to indicate roaming. For example, the roaming identifier can be a 1-bit information; if the 1-bit value is "0", it indicates that the UE is a roaming UE, and conversely, if the 1-bit value is "1", it indicates that the UE is not a roaming UE; or, if the 1-bit value is "1", it indicates that the UE is a roaming UE, and conversely, if the 1-bit value is "0", it indicates that the UE is not a roaming UE. Alternatively, the roaming identifier may occupy more bits, without limitation.
[0097] In another example, the first request message may also include UE information, such as UE location information. The first ECS can determine the first V-EES and / or the first V-ECS based on the AC profile and the UE's location information. It should be noted that the embodiments of this application do not limit the specific method of determining the first V-EES and / or the first V-ECS. For example, the first ECS may also obtain the information of the first V-EES and / or the first V-ECS from other network elements to determine the first V-EES and / or the first V-ECS.
[0098] S402, the first ECS sends an AF request to the PCF, and the corresponding PCF receives the AF request from the first ECS. The AF request is used to request the configuration of the data forwarding path from the UE to the first V-EES and / or the first V-ECS.
[0099] AF requests, also known as AF transactions, can influence the routing decisions of session traffic. For example, an AF request is used to request the configuration of a data forwarding path from the UE to a target network element. The target network element may be, for example, the first V-EES and / or the first V-ECS. The data forwarding path from the UE to the first V-EES and / or the first V-ECS can include: a data forwarding path from the UE to the first V-EES, and / or a data forwarding path from the UE to the first V-ECS. A data forwarding path can also be called a data transmission path, data forwarding channel, data transmission channel, or data channel, etc. It should be understood that a data forwarding path is a specific implementation of a traffic splitting rule; from this perspective, a data forwarding path can also be called a traffic splitting rule, forwarding rule, data splitting rule, or data forwarding rule, etc.
[0100] Configuring the data forwarding path from the UE to the target network element can also be understood as controlling the routing of the UE's traffic to the target network element. Therefore, an AF request can be understood as a request to control the routing of the UE's traffic to the target network element, or an AF request can indicate the target network element to which the UE's traffic should be routed. For example, an AF request is used to request that traffic from the UE be routed to the first V-EES and / or the first V-ECS, meaning the destination address of the UE's traffic is the address of the first V-EES and / or the address of the first V-ECS. Here, traffic can also be referred to as data, data packets, or information, etc.
[0101] The target network element is the network element corresponding to the destination address. Accordingly, the AF request may include information about the first V-EES and / or the first V-ECS. Specifically, the information about the first V-EES includes the identifier of the first V-EES and / or the address information of the first V-EES, etc. Similarly, the information about the first V-ECS includes the identifier of the first V-ECS and / or the address information of the first V-ECS, etc. For ease of description, the following example uses the address information of the first V-EES and the address information of the first V-ECS as the example. It should be understood that the address information of the first V-EES can be replaced with the identifier of the first V-EES. The address information of the first V-ECS can be replaced with the identifier of the first V-ECS. It should be noted that the first V-ECS can be the first ECS or other V-ECS besides the first ECS. In other words, the first ECS and the first V-ECS can be the same V-ECS or different V-ECS; this embodiment does not limit this. To facilitate differentiation, when the first ECS and the first V-ECS are different V-ECS, the first ECS is referred to as the second V-ECS.
[0102] After receiving the first request message, the first ECS can send an AF request to the core network, enabling the core network to perform path configuration, or in other words, to configure a data forwarding path for the UE. For example, the first ECS sends an AF request to the PCF. Optionally, the first ECS can directly send the AF request to the PCF, or the first ECS can also send the AF request to the PCF through the NEF. It should be understood that the core network can use various methods to perform path configuration, which are illustrated below.
[0103] S403, PCF sends a second request message to V-SMF.
[0104] The second request message is used to request the configuration of the data forwarding path from the UE to the first V-ECS and / or the first V-EES. The function of the second request message is similar to that of the AF request mentioned earlier, and will not be repeated here. Accordingly, for example, the second request message may include the address information of the first V-EES and / or the address information of the first V-ECS. Furthermore, since the second request message is sent by the PCF, it can also be considered as being used to configure / update policy and charging control (PCC) rules, or to configure / update session policies, etc. Alternatively, it can be considered as being used to configure traffic splitting rules or data forwarding rules, etc.
[0105] This application does not limit the specific name of the second request message in its embodiments. For example, the second request message may also be called a traffic splitting rule request message, a traffic splitting rule configuration message, a traffic splitting rule update message, a session management policy update message, or a policy and charging control rule update message, etc.
[0106] S404, V-SMF configures data forwarding rules to V-UPF.
[0107] After obtaining the address information of the first V-EES and / or the first V-ECS, the V-SMF configures data forwarding rules for the V-UPF. Configuring data forwarding rules can also be considered configuring data forwarding paths. Data forwarding rules can be rules by which the UE forwards data to the first V-EES and / or the first V-ECS. The V-SMF configuring data forwarding rules for the V-UPF can also be understood as requesting the V-UPF to route traffic destined for the first V-EES to the first V-EES, and / or to route traffic destined for the first V-ECS to the first V-ECS.
[0108] For example, the V-SMF can send a first message to the V-UPF. This first message may include the address information of the first V-EES and / or the address information of the first V-ECS. Correspondingly, after receiving the first message, the V-UPF can obtain the address information of the first V-EES and / or the first V-ECS from the first message, thereby enabling the V-UPF to configure data forwarding rules from the UE to the first V-EES and / or the first V-ECS. Subsequently, the V-UPF can send data destined for the address of the first V-EES to the first V-EES, and / or send data destined for the address of the first V-ECS to the first V-ECS. This application embodiment does not limit the specific implementation of the first message. For example, the first message may be an interface message between the V-SMF and the V-UPF, such as an N4 message, or it may be other types of messages.
[0109] Optionally, the V-SMF sends a packet detection rule (PDR) and a corresponding forwarding action rule (FAR) to the V-UPF via a first message. The PDR includes the address information of the first V-EES and / or the first V-ECS. The V-UPF then performs address matching on the received packets based on the address information of the first V-EES and / or the first V-ECS. It can be understood that if the destination address of a packet matches an address included in the PDR, the packet is considered a successful match. Data matching the address of the first V-ECS is sent to the first V-ECS, and data matching the address of the first V-EES is sent to the first V-EES. Alternatively, the V-UPF can be considered to obtain the PDR and FAR from the first message, perform data detection based on the PDR to form a data forwarding path, and forward data according to the FAR.
[0110] S405 and V-UPF send configuration response messages to V-SMF.
[0111] After configuring the data forwarding rules for the UE to the first V-EES and / or the first V-ECS, the V-UPF can send a configuration response message to the V-SMF to indicate that the configuration is complete. Alternatively, the V-UPF can indicate configuration completion via a configuration response message. For example, the configuration response message can indicate that the configuration is complete. Specifically, the configuration response message instructs the V-UPF to configure the data forwarding rule, or instructs the V-UPF to configure the data forwarding path for the UE to the first V-EES and / or the first V-ECS.
[0112] S406, V-SMF sends a user plane path change notification, which can indicate that the data forwarding path configuration from the UE to the first V-EES and / or the first V-ECS is complete.
[0113] The user plane path may include a data forwarding path. In other words, the data forwarding path is a segment of the user plane path. If the data forwarding path from the UE to the first V-EES and / or the first V-ECS is configured, the user plane path of the session established by the UE changes. Therefore, after determining that the data forwarding path from the UE to the first V-EES and / or the first V-ECS is configured (or in other words, after determining that the data forwarding rule is configured), the V-SMF can send a user plane path change notification to the first ECS. Upon receiving the user plane path change notification, the first ECS then sends a response message to the UE for the first request message. For the UE, it can be guaranteed that the user plane path has been configured when the response message to the first request message is received, so that subsequent data packets sent by the UE (e.g., requests to query the edge application server, etc.) can be successfully sent to the first V-EES and / or the first V-ECS. It should be noted that S406 is an optional step, therefore... Figure 4 The diagram is illustrated using dashed lines. Specifically, the user plane path change notification indicates that the data forwarding path configuration from the UE to the first V-EES and / or the first V-ECS is complete.
[0114] This application does not limit the specific implementation of the user plane path change notification. For example, the user plane path change notification may include a reason value for the user plane path change, which indicates the reason for the change. Therefore, this reason value implicitly indicates that the user plane path has changed. In this application embodiment, the reason for the user plane path change is, for example, that the data forwarding path configuration from the UE to the first V-EES and / or the first V-ECS has been completed.
[0115] S407, The first ECS sends the first response message to the UE.
[0116] In response to the first request message, the first ECS can send a first response message to the UE. That is, the response message to the first request message is the first response message. This first response message may include the configuration information of the first V-ECS and / or the configuration information of the first V-EES. The configuration information of the first V-ECS may include the address information of the first V-ECS, the provider information of the first V-ECS, etc. The address information of the first V-ECS may include the URI, fully qualified domain name (FQDN), IP address, etc. The provider information of the first V-ECS may include the identification information of the provider deploying the first V-ECS. The configuration information of the first V-EES may include the address information, identification information, service area, the direct network access company (DNAI) to which it belongs, and the information of the EAS it manages. Since the UE can determine the first V-ECS based on the configuration information of the first V-ECS, and can also determine the first V-EES based on the configuration information of the first V-EES, the UE can subsequently discover the EAS through the first V-EES and / or the first V-ECS.
[0117] It is understandable that the first ECS can feed back the configuration information of the first V-EES by feeding back the configuration information of the EDN to the UE. That is, the first ECS sending the first response message to the UE can be the first ECS sending the configuration information of the EDN to the UE. This EDN configuration information includes the configuration information of the first V-EES. Optionally, this EDN configuration information may also include the DNN S-NSSAI to which the END belongs.
[0118] The embodiments of this application do not limit the specific name of the first response message. For example, the first response message may be called a business response message, a service provisioning response message, or an availability response message, etc.
[0119] In this embodiment, the first ECS sends an AF request to the core network to request configuration of a path from the UE to the first V-EES and / or the first V-ECS. This ensures that subsequent data sent by the UE to the first V-EES and / or the first V-ECS can be routed to the visited domain's V-EES and / or V-ECS, instead of being directly forwarded to the home domain. For example, if the UE sends a service activation request with the destination address of the first V-ECS, the V-UPF, upon receiving the request, forwards it to the first V-ECS according to the configured data forwarding rules, instead of directly sending it to the H-UPF. This establishes a data forwarding path from the UE to the first V-ECS. For example, if a UE sends an EAS discovery request with the destination address of the first V-EES, the V-UPF, upon receiving the request, will forward it to the first V-EES according to the configured data forwarding rules, instead of directly sending it to the H-UPF. This effectively establishes a data forwarding path from the UE to the first V-EES. For detailed service discovery procedures, please refer to [link to relevant documentation]. Figure 3 .
[0120] Figure 4 In the illustrated process, the first ECS can be either a V-ECS or an H-ECS, and the PCF can be either a V-PCF or an H-PCF, depending on the specific implementation of the first ECS and the PCF. Figure 4 The processes shown also differ. For ease of understanding, the communication methods provided in this application embodiment are illustrated by taking V-ECS and H-ECS as examples, respectively.
[0121] Please see Figure 5 This is an exemplary flowchart of a first communication method provided in the embodiments of this application. Figure 5 Take V-ECS as an example, where the first ECS is V-ECS.
[0122] S501, EEC's discovery of V-ECS.
[0123] The EEC itself can discover V-ECS, as detailed in S30 above. For example, the ECS in S30 is a V-ECS, which will not be elaborated here. Alternatively, the EEC can also discover V-ECS through the H-ECS. When the EEC discovers a V-ECS, it can directly send a first request message to the discovered V-ECS. That is, the V-ECS can receive the first request message sent by the EEC. The EEC can also discover a V-ECS through the H-ECS and send a first request message to the discovered V-ECS through the H-ECS. In this case, the V-ECS can receive the first request message sent by the EEC through the H-ECS. In the following text, the method of the EEC sending a first request message to the V-ECS through the H-ECS will be referred to as sending method 1, and the method of the EEC directly sending a first request message to the V-ECS will be referred to as sending method 2.
[0124] Sending method 1 can be achieved through S502a-S502b.
[0125] S502a and EEC send a third request message to H-ECS, which may include roaming identification and application client configuration information.
[0126] The third request message can be used to request the use of the MEC function of VPLMN. Its function is similar to that of the first request message described above, and will not be repeated here. The third request message may include the AC profile and roaming identifier; for details, please refer to the relevant content of the first request message mentioned above, which will not be repeated here.
[0127] It is understandable that when a UE needs to access the MEC service of a VPLMN, the UE can send a third request message to the H-ECS. Specifically, if the EEC is deployed within the UE, the UE can send the third request message to the H-ECS through the EEC. Therefore, S502a can also be understood as the UE sending a third request message to the H-ECS, and the H-ECS receiving the third request message from the UE. If the UE and EEC are deployed independently, then S502a represents the EEC sending a third request message to the H-ECS, and the H-ECS receiving the third request message from the EEC.
[0128] S502b and H-ECS send the first request message to V-ECS.
[0129] After receiving the third request message, the H-ECS can determine that the UE requesting access to the MEC function is a roaming UE based on the roaming identifier included in the third request message. Therefore, the H-ECS can send a first request message to the V-ECS corresponding to that roaming identifier. This can also be understood as the H-ECS sending the first request message to the V-ECS under the triggering of the EEC (or, under the triggering of the UE).
[0130] Sending method 2 can be achieved through S502c.
[0131] S502c and EEC send the first request message to V-ECS.
[0132] If the EEC is deployed within the UE, the UE can send a first request message to the V-ECS via the EEC. Therefore, S502c can be understood as the UE sending a first request message to the V-ECS, and the V-ECS receiving the first request message from the UE. If the UE and EEC are deployed independently, then S502c represents the EEC sending a first request message to the V-ECS, and the V-ECS receiving the first request message from the EEC.
[0133] In practice, sending method 1 can be executed without sending method 2; alternatively, sending method 2 can be executed without sending method 1; or both sending methods 1 and 2 can be executed. Furthermore, sending methods 1 and 2 are optional. In practice, EEC may also send request messages to V-ECS through other methods, without any restrictions.
[0134] It should be noted that the specific implementation of S502a-S502c can be found in the relevant content of S401 mentioned above, and will not be repeated here.
[0135] V-ECS receives a first request message from H-ECS and can query information about the first V-EES and / or the first V-ECS based on the AC profile in the first request message.
[0136] Upon receiving the first request message, the V-ECS can query information about the first V-EES and / or the first V-ECS based on the AC profile in the first request message. For details, please refer to the relevant content in S401 above; it will not be repeated here.
[0137] In S503, the V-ECS sends an AF request to the V-PCF. This AF request can be used to request the configuration of the data forwarding path from the UE to the first V-EES and / or the first V-ECS. For details, please refer to the relevant content in S402 above. For example, the PCF in S402 is the V-PCF, which will not be repeated here.
[0138] S504, V-PCF sends a second request message to V-SMF, which is used to request the configuration of the data forwarding path of the UE to the first V-EES and / or the first V-ECS.
[0139] There are several ways for V-PCF to send the second request message to V-SMF. For example, V-PCF sends the second request message to H-PCF, which then sends it to H-SMF, and finally H-SMF sends it to V-SMF. Alternatively, V-PCF can send the second request message to H-PCF, which then sends it back to V-PCF, and finally V-PCF sends it to V-SMF.
[0140] S505, V-SMF configures data forwarding rules to V-UPF. These data forwarding rules include the data forwarding path from the UE to the first V-EES and / or the first V-ECS. For details on data forwarding rules and how to configure them, please refer to the relevant content in S404 above; it will not be repeated here.
[0141] S506, V-UPF sends a configuration response message to V-SMF, which is the response message to the first message.
[0142] The configuration response message indicates that the V-UPF has configured the data forwarding path from the UE to the first V-EES and / or the first V-ECS, meaning the configuration is complete.
[0143] S507a: V-SMF sends a user plane path change notification to V-ECS. For details, please refer to the relevant content of S406 above; it will not be repeated here.
[0144] When V-ECS receives a user plane path change notification, it can send a response message to the EEC in response to the first request message, for example, called a first response message. The process of sending the first response message to the EEC differs depending on the two methods of sending the first request message. Specifically, it can include the following implementation method 1 and implementation method 2. It is understood that implementation method 1 corresponds to the aforementioned sending method 1, and implementation method 2 corresponds to the aforementioned sending method 2.
[0145] Implementation method 1 can be achieved through S508a-S509a. V-ECS sends the first response message to EEC through H-ECS.
[0146] S508a and V-ECS send the first response message to H-ECS.
[0147] S509a and H-ECS send the first response message to EEC.
[0148] Implementation method 2 can be achieved using S508b. V-ECS directly sends the first response message to EEC.
[0149] S508b, V-ECS sends the first response message to EEC.
[0150] For details on the implementation of the first response message, please refer to the aforementioned S407 content, which will not be repeated here.
[0151] It is understandable that if the aforementioned sending method 1 is executed, then implementation method 1 will be executed; if the aforementioned sending method 2 is executed, then implementation method 2 will be executed.
[0152] It should be noted that, Figure 5 For details regarding the messages, steps, and other implementation details, please refer to [link / reference]. Figure 4 The relevant content will not be repeated here.
[0153] Please see Figure 6 This is an exemplary flowchart of a first communication method provided in the embodiments of this application. Figure 6 Taking H-ECS as an example, the first ECS is H-ECS.
[0154] S601, EEC's discovery of H-ECS.
[0155] EEC can perform H-ECS discovery to obtain the address of H-ECS, and then query V-ECS through H-ECS. For details on EECS discovery, please refer to the relevant content in S30 above; for example, the ECS in S30 is H-ECS, which will not be elaborated here.
[0156] In S602, the EEC sends a first request message to the H-ECS. For details, please refer to the relevant content in the aforementioned S401. For example, the first ECS in S401 is the H-ECS, which will not be elaborated upon here.
[0157] S603, H-ECS determines the address of V-ECS.
[0158] After receiving the first request message, the H-ECS can determine that the current UE is a roaming UE using the roaming identifier carried in the first request message, such as the VPLMN ID. Alternatively, the H-ECS can determine that the service currently requested by the UE is a roaming service using the roaming identifier carried in the first request message, such as information indicating roaming. In this case, the H-ECS can query the UE's roaming information and registered local information to determine the V-ECS corresponding to the roaming UE. This V-ECS can be the first V-ECS or another V-ECS besides the first V-ECS. For ease of distinction, this V-ECS is referred to as the third V-ECS. If the H-ECS can communicate with the third V-ECS, the H-ECS requests the V-EES corresponding to the roaming UE from the third V-ECS. This can also be understood as the H-ECS obtaining the address information of the first V-ECS and / or the address information of the first V-EES from the third V-ECS. The UE's roaming information may include the roaming identifier, such as the VPLMN ID. The local information registered by the UE can include the address information of the V-ECS corresponding to the PLMN ID. That is, there can be a correspondence between the roaming identifier and the V-ECS address information.
[0159] S604, H-ECS sends a first request message to the third V-ECS. For details, please refer to the relevant content in S502b above; it will not be repeated here.
[0160] S605, the third V-ECS sends a first response message to the H-ECS, which includes the configuration information of the first V-EES. For details on the implementation of the first response message, please refer to the relevant content in S407 above; it will not be repeated here.
[0161] S606, H-ECS sends an AF request to H-PCF, which can be used to request the configuration of the data forwarding path from the UE to the first V-EES and / or the first V-ECS.
[0162] The AF request may include the address information of the first V-EES and / or the address information of the first V-ECS. For details, please refer to the relevant content in S402 above; for example, in S402, the first ECS is H-ECS and the PCF is H-PCF, which will not be repeated here. It should be understood that if S604 and S605 are executed, the AF request may include the address information of the first V-EES. If S604 and S605 are not executed, the AF request may include the address information of the first V-ECS.
[0163] S607, H-PCF sends a second request message to V-SMF, the second request message including the address information of the first V-EES and / or the address information of the first V-ECS.
[0164] Optionally, the H-PCF sends the second request message to the H-SMF, which then forwards it to the V-SMF. Alternatively, the H-PCF sends the second request message to the V-PCF, which then forwards it to the V-SMF.
[0165] S608, V-SMF configures data forwarding rules to V-UPF, which include the data forwarding path from UE to the first V-EES and / or the first V-ECS. For details, please refer to the relevant content in S404 above, which will not be repeated here.
[0166] S609, V-UPF sends a configuration response message to V-SMF. For details, please refer to the relevant content in S405 above; it will not be repeated here.
[0167] S610 and V-SMF send user plane path change notifications to H-ECS.
[0168] S611 and H-ECS send the first response message to the UE.
[0169] Upon receiving a user plane path change notification, the H-ECS can send a first response message to the UE. This first response message includes the address information of the first V-ECS and / or the address information of the first V-EES. For details, please refer to the relevant content in S407 above; for example, the first ECS in S407 is the H-ECS, which will not be elaborated upon here.
[0170] It should be noted that, Figure 6 For details regarding the messages, steps, and other implementation details, please refer to [link / reference]. Figure 4 The relevant content will not be repeated here.
[0171] pass Figure 6 The illustrated process involves configuring the V-UPF data forwarding path by sending an AF request from the H-ECS to the H-PCF after the session is established. This allows service flows from the UE to the first V-ECS and / or the first V-EES to be routed through the V-UPF instead of being forwarded to the H-UPF. For roaming UEs, although the session anchor is at the H-PCF, the V-UPF-based data forwarding path enables requests for EAS queries to be routed to the corresponding first V-EES and / or the first V-ECS, thus achieving EAS discovery and supporting roaming UEs accessing edge application services in the VPLMN.
[0172] Figures 4-6The illustrated embodiment configures V-UPF data forwarding rules after the session is established so that the service flow from the terminal device to V-ECS and / or V-EES can be offloaded through V-UPF, thereby enabling roaming terminals to access edge application services in VPLMN.
[0173] As an alternative implementation, a V-UPF data forwarding path can be generated during roaming session establishment, allowing service flows from the terminal device to V-ECS and / or V-EES to be offloaded through V-UPF instead of being forwarded to H-UPF. The alternative solution is described below.
[0174] Please see Figure 7 This is a flowchart of a second communication method provided in an embodiment of this application. This communication method is applicable to the HR scenario described above. The flowchart of this communication method is described below.
[0175] S701, V-SMF receives first indication information, which is used to indicate that the UE's first HR session uses the MEC function of VPLMN.
[0176] Using the MEC function of a VPLMN can be understood as using the VPLMN's MEC services, or accessing the VPLMN's MEC services. When a UE needs to use MEC services, it can instruct the V-SMF via a first indication message to use the VPLMN's MEC function for its first HR session. This first indication message can be implicit or explicit. For example, the first indication message can be a 1-bit message. If the value of this 1-bit is "0", it instructs the UE's first HR session to use the VPLMN's MEC function; or, if the value of this 1-bit is "1", it instructs the UE's first HR session to use the VPLMN's MEC function. That is, the first indication message explicitly instructs the UE's first HR session to use the MEC service. Alternatively, the first indication message can be a roaming identifier, such as the VPLMN's ID. Instructing the UE's first HR session to use the VPLMN's MEC service via the roaming identifier implicitly instructs the use of the MEC service.
[0177] This application does not limit the timing of sending the first indication information. For example, the first indication information can be sent when a session establishment request is made, or it can be sent during the session establishment process. Specific examples are given below.
[0178] Example 1: The first indication information is sent during a session establishment request. For example, the UE sends the first indication information during a session establishment request.
[0179] S701a, the UE sends a session establishment request message to the V-SMF, which includes first indication information.
[0180] A session establishment request message can be used to request the establishment of a session, such as a first HR session. This application embodiment does not limit the name of the session establishment request message; for example, it can also be called a session modification request message. The session establishment request message may include first indication information to indicate the use of VPLMN MEC services.
[0181] Example 2: The first indication message is sent during the session establishment process. For example, the first indication message is carried in the messages exchanged between H-SMF and V-SMF during the session establishment process.
[0182] S701b, H-SMF sends a first message to V-SMF, the first message including first instruction information.
[0183] The first message can be an interface message between H-SMF and V-SMF, for example, the first message is the N16 message.
[0184] It should be noted that S701a and S701b are not both mandatory. For example, S701a can be executed but S701b can be omitted, or S701b can be executed but S701a can be omitted.
[0185] S702, V-SMF sends a first request message to V-PCF, which is used to instruct the UE's first HR session to use the MEC function of VPLMN.
[0186] The first request message can be used to request the use of the MEC function of the VPLMN, or it can be understood as a request to access the MEC service of the VPLMN. Alternatively, the first request message can be used to request a session management policy related to the roaming UE, or a session management policy related to the first HR session established by the UE. This application embodiment does not limit the specific name of the first request message. For example, the first request message can be called a service request message, or a service provisioning request message. As another example, the first request message can also be called an availability request message.
[0187] The first request message may include first indication information, or it may include one or more of the following corresponding to the UE: a generic public subscription identifier (GPSI), a subscription permanent identifier (SUPI), a data network name (DNN), or single network slice selection assistance information (S-NSSAI), or an identifier for the first HR session. It is understood that the GPSI can be used to indicate the UE. Similarly, the SUPI can also be used to indicate the UE. Alternatively, the DNN and S-NSSAI can be used to indicate the first HR session or the UE that established the first HR session.
[0188] S703, V-PCF obtains the address information of the first V-ECS and / or the first V-EES associated with the first HR session from the V-UDR network element.
[0189] Upon receiving the first request message, the PCF can request a V-ECS and / or V-EES that supports the first HR session from the data management network element, or request to obtain a V-ECS and / or V-EES associated with the first HR session. A V-ECS that supports the first HR session can also be understood as an available V-ECS. Similarly, a V-EES that supports the first HR session is an available V-EES. From this perspective, the first request message can also be used to request available V-ECS and / or V-EES. Similar to the content of S401 above, this embodiment of the application refers to the available V-ECS as the first V-ECS and the available V-EES as the first V-EES.
[0190] As an example, the V-PCF can send a subscription request message to the V-UDR network element. This subscription request message is used to request subscription to the notification message of the AF request associated with the first HR session. Alternatively, the V-PCF can be considered to request the V-UDR to subscribe to the AF request notification. This subscription request message may include an index for obtaining the AF request corresponding to the UE or the first HR session. For example, the subscription request message may include the UE's identifier and / or the identifier of the UE's first HR session. That is, the UE's identifier and / or the identifier of the UE's first HR session are the index used to obtain the AF request. The UE's identifier can be one or more of GPSI, DNN, or S-NSSAI, and may also include the group ID of the group to which the UE belongs, or the UE's application descriptor. The subscription request message may also include the identifier of the UE's first HR session, etc. For example, the UE's identifier can be the UE's SUPI or GPSI, or the UE's identifier can be the DNN and S-NSSAI corresponding to the UE. By sending the UE's identifier to the V-UDR, the V-PCF indicates the need to obtain the AF request corresponding to the UE's identifier, without needing to send a separate message for obtaining the AF request, thus reducing signaling interaction. The identifier of the first HR session may include the DNN and S-NSSAI corresponding to the UE. V-PCF indicates the need to obtain the AF request corresponding to the first HR session by sending the identifier of the first HR session to V-UDR, without having to send a separate message for obtaining the AF request, thus reducing signaling interaction.
[0191] The V-UDR network element can store the address information of the first V-ECS and / or the first V-EES associated with the UE or the first HR session based on the AF request. When the V-UDR network element receives a subscription request message, it can query the AF request associated with the first HR session based on the content included in the subscription request message, such as the identifier of the first HR session, and then obtain the address information of the first V-ECS and / or the first V-EES associated with the first HR session. Afterwards, the V-UDR sends a notification message to the V-PCF, which includes the address information of the first V-ECS and / or the first V-EES.
[0192] It should be noted that the address information of the first V-ECS and / or the address information of the first V-EES can be stored in the data management network element by the first ECS through an AF request. The data management network element can be a UDM or a UDR. This application embodiment takes a UDR as the data management network element as an example. The first ECS can be a visited domain ECS, such as the first V-ECS or the second V-ECS, and this application embodiment does not limit this. Taking a V-UDR as an example, the first ECS can execute S700.
[0193] S700, the first ECS can send an AF request to the V-UDR, and the V-UDR receives the AF request from the first ECS accordingly.
[0194] The first ECS can instruct the V-UDR to store the address information of the first V-ECS and / or the address information of the first V-EES via an AF request, facilitating subsequent EAS discovery. The AF request may include the address information of the first V-ECS and / or the first V-EES. It is understood that the AF request can be an AF request related to a roaming UE or an AF request related to a session established by the roaming UE. Accordingly, the AF request may include a roaming identifier, which indicates whether the UE is a roaming UE. For example, the roaming identifier may be a VPLMN ID, or indication information used to indicate roaming. The AF request may also include an index for querying the address information of the first V-ECS and / or the address information of the first V-EES, such as the UE's identifier and / or the identifier of the first HR session. The UE's identifier may include one or more of GPSI, DNN, or S-NSSAI, and may also include the group ID of the UE's group, the UE's application descriptor, etc. The identifier of the first HR session, such as the DNN, S-NSSAI, and / or application identifier corresponding to the UE, can be used to indicate the first HR session or the UE that established the first HR session.
[0195] The V-UDR receives an AF request and can store the address information of the first V-EES and / or the address information of the first V-ECS corresponding to the roaming identifier of the UE carried in the AF request. Optionally, the first ECS can also send an AF request to the V-UDR through the Network Open Functions (LOF) element to store the address information of the first V-ECS and / or the first V-EES corresponding to the roaming UE in the V-UDR, facilitating subsequent EAS discovery. It should be noted that if the first ECS sends an AF request to the V-UDR through the LEF element, the AF request also includes the UE's GPSI. The LEF element then uses the UE's GPSI to query other information of the terminal device, such as SUPI. Therefore, the LEF element can store the address information of the first V-ECS and / or the first V-EES corresponding to the UE in the V-UDR.
[0196] It should be noted that the execution timing of S700 in this embodiment is not limited, as long as the address information of the first V-ECS and / or the address information of the first V-EES corresponding to the UE is stored in the V-UDR. Alternatively, the execution of S700 can be considered independent of S701-S703, or the execution order of S700 and S701-S703 is not limited. In specific execution, if the V-DUR has already stored the address information of the first V-ECS and / or the address information of the first V-EES corresponding to the UE, then S700 may not be executed. Figure 7 The image is indicated by a dashed line.
[0197] S704, V-UDR sends a notification message to V-PCF, and correspondingly, V-PCF receives a notification message from V-UDR, which includes the address information of the first V-EES and / or the address information of the first V-ECS.
[0198] The V-UDR stores the address information of the first V-EES and / or the first V-ECS corresponding to the UE or the first HR session. Therefore, based on the content included in the subscription request message, such as the identifier of the UE's first HR session, the V-UDR can determine the address information of the first V-EES and / or the first V-ECS corresponding to the first HR session. After determining the address information of the first V-EES and / or the first V-ECS corresponding to the first HR session, the V-UDR sends a notification message to the V-PCF, which includes the address information of the first V-EES and / or the first V-ECS.
[0199] S705, V-PCF sends a first response message to V-SMF, and correspondingly, V-SMF receives the first response message from V-PCF, which includes the address information of the first V-ECS and / or the address information of the first V-EES.
[0200] V-PCF can send the first response message directly to V-SMF. Alternatively, V-PCF can send the first response message to H-PCF, which will then forward it to H-SMF, and finally to V-SMF. Or, V-PCF can send the first response message to H-PCF, which will then forward it to V-PCF, and finally to V-SMF.
[0201] S706, V-SMF configures data forwarding rules to V-UPF.
[0202] After obtaining the address information of the first V-EES and / or the first V-ECS, the V-SMF configures data forwarding rules for the V-UPF. These data forwarding rules can be rules for the UE to forward data to the first V-EES and / or the first V-ECS. For details, please refer to the relevant content in S404 above; it will not be repeated here.
[0203] S707 and V-UPF send configuration response messages to V-SMF. Refer to the relevant content of S405 above for details, which will not be repeated here.
[0204] This application embodiment allows configuring the data forwarding path from the roaming UE to the first V-ECS and / or the first V-EES via V-UPF during session establishment. This ensures that subsequent data sent by the UE to the first V-EES and / or the first V-ECS can be routed to the visited domain's first V-EES and / or first V-ECS, instead of being directly forwarded to the home domain. This enables messages sent by the roaming UE to the V-ECS and / or V-EES to be routed to the VPLMN. Consequently, requests sent by the roaming terminal to query the EAS can be routed to the visited domain's ECS and / or visited domain's EES, achieving EAS discovery and supporting roaming UE access to edge application services within the VPLMN.
[0205] The embodiments provided in this application describe the methods from the perspectives of HLPMN and VPLMN, including the interaction between network elements. To implement the functions of the methods provided in the embodiments of this application, corresponding communication devices are also provided. These communication devices may include hardware structures and / or software modules, implementing the above functions in the form of hardware structures, software modules, or a combination of hardware structures and software modules. Whether a particular function is executed in the form of hardware structures, software modules, or a combination of hardware structures and software modules depends on the specific application and design constraints of the technical solution.
[0206] This application also provides a communication device. The communication device used to implement the above method in this application embodiment is described below with reference to the accompanying drawings.
[0207] Figure 8 This is a schematic block diagram of a communication device 800 provided in an embodiment of this application. The communication device 800 may include a processing module 810 and a transceiver module 820. Optionally, it may also include a storage unit, which can be used to store instructions (code or program) and / or data. The processing module 810 and the transceiver module 820 may be coupled to the storage unit. For example, the processing module 810 may read instructions (code or program) and / or data from the storage unit to implement a corresponding method. The aforementioned units may be set independently, or partially or completely integrated.
[0208] It should be understood that the processing module 810 may be a processor or controller, such as a general-purpose central processing unit (CPU), a general-purpose processor, a digital signal processing unit (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It may implement or execute the various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. The processor may also be a combination that implements computing functions, such as including one or more microprocessor combinations, a combination of a DSP and a microprocessor, etc. The transceiver module 820 is an interface circuit of the device for receiving signals from other devices. For example, when the device is implemented as a chip, the transceiver module 820 is an interface circuit of the chip for receiving signals from other chips or devices, or an interface circuit of the chip for sending signals to other chips or devices.
[0209] The communication device 800 can be an edge configuration server, a policy control function network element, or a session management network element as described in the above embodiments. It can also be a chip used for an edge configuration server, policy control function network element, or session management network element. For example, when the communication device 800 is an edge configuration server, a policy control function network element, or a session management network element, the processing module 810 can be a processor, and the transceiver module 820 can be a transceiver. Optionally, the transceiver may include radio frequency circuitry, and the storage unit may be a memory. For example, when the communication device 800 is a chip used for an edge configuration server, a policy control function network element, or a session management network element, the processing module 810 can be a processor, and the transceiver module 820 can be an input / output interface, pins, or circuits. The processing module 810 can execute computer execution instructions stored in the storage unit. Optionally, the storage unit is a storage unit inside the chip, such as a register or cache. The storage unit can also be a storage unit located outside the chip in the network device, terminal, or location management device, such as read-only memory (ROM) or other types of static storage devices that can store static information and instructions, random access memory (RAM), etc.
[0210] In one possible implementation, the communication device 800 can correspondingly implement the behavior and functions of the ECS (e.g., V-ECS or H-ECS) in the above method embodiments. The communication device 800 can be an ECS, a component (e.g., a chip or circuit) applied in the ECS, or a chip or chipset in the ECS, or a part of a chip used to perform the relevant method functions. The transceiver module 820 can be used to support communication between the ECS and other network entities, such as supporting communication between the ECS and other network entities. Figures 4 to 7 Communication between any of the PCFs shown. Processing module 810 is used to control and manage the actions of the ECS; for example, processing module 810 is used to support ECS execution. Figures 4 to 7 All operations of ECS in any embodiment except for sending and receiving.
[0211] For example, the transceiver module 820 is used to receive a first request message, send an AF request to the policy control function network element, and send a first response message. The first request message includes configuration information of the application client. The AF request is used to request configuration of the data forwarding path from the terminal to the first V-EES and / or the first V-ECS. The first response message is a response message to the first request message.
[0212] As an optional implementation, the AF request may include the address information of the first V-EES and / or the address information of the first V-ECS.
[0213] As an optional implementation, the transceiver module 820 is also used to receive a user plane path change notification from V-SMF before sending the first response message.
[0214] As an optional implementation, the first response message includes configuration information of the first V-EES and / or configuration information of the first V-ECS.
[0215] As an optional implementation, the processing module 810 is used to determine the first V-EES and / or the first V-ECS based on the configuration information of the application client.
[0216] As an optional implementation, if the communication device 800 is a first V-ECS or a second V-ECS, the transceiver module 820 is used to receive a first request message from the H-ECS and send a first response message to the H-ECS. Alternatively, if the communication device 800 is a first V-ECS or a second V-ECS, the transceiver module 820 is used to receive a first request message from the EEC and send a response message to the EEC in response to the first request message.
[0217] As an optional implementation, the communication device 800 can be a first V-ECS or a second V-ECS, with the policy control function network element being a V-PCF; or the communication device 800 can be an H-ECS, with the policy control function network element being an H-PCF.
[0218] As an optional implementation, the communication device 800 is an H-ECS, and the processing module 810 is used to obtain the first V-EES and / or the first V-ECS from the third V-ECS.
[0219] In another possible implementation, the communication device 800 can correspondingly implement the behavior and functions of the policy control function network element (e.g., including V-PCF or H-PCF) in the above method embodiments. The communication device 800 can be a policy control function network element, a component (e.g., a chip or circuit) applied in the policy control function network element, or a chip or chipset in the policy control function network element, or a part of a chip used to perform related method functions. The transceiver module 820 can be used to support communication between the policy control function network element and other network entities, such as supporting communication between the policy control function network element and other network entities. Figures 4 to 7 Communication between V-ECS, etc., as shown in any embodiment. Processing module 810 is used to control and manage the actions of policy control function network elements; for example, processing module 810 is used to support the execution of policy control function network elements. Figures 4 to 7 All operations of the policy control function network element in any embodiment, except for sending and receiving.
[0220] For example, the transceiver module 820 is used to receive an AF request and send a second request message to the V-SMF based on the AF request. The AF request is used to request configuration of the data forwarding path from the terminal to the first V-EES and / or the first V-ECS. The second request message includes the address information of the first V-EES and / or the address information of the first V-ECS.
[0221] As an optional implementation, the AF request includes the address information of the first V-EES and / or the address information of the first V-ECS.
[0222] For example, the transceiver module 820 is used to receive a first request message from the session management function network element, obtain the address information of the first V-EES and / or the address of the first V-ECS associated with the first HR session of the UE from the data management network element, and send a first response message to the session management function network element. The first request message is used to instruct the UE's first HR session to request the use of the VPLMN's edge computing function. The first response message includes the address information of the first V-EES and / or the address information of the first V-ECS.
[0223] As an optional implementation, the first request message includes one or more of the following for the UE: GPSI, SUPI, DNN, or S-NSSAI, or the identifier of the first HR session.
[0224] As an optional implementation, the transceiver module 820 is specifically used to send a subscription request message to the data management network element and receive a notification message from the data management network element. The subscription request message is used to request subscription to a notification message for an AF request associated with the UE's first HR session. The notification message includes the address information of the first V-EES and / or the address information of the first V-ECS associated with the first HR session.
[0225] As an optional implementation, the address information of the first V-EES and / or the address information of the first V-ECS are stored in the data management network element by the first edge configuration server ECS through an AF request.
[0226] Optionally, the edge configuration server is the first visited domain edge configuration server, and the data management network element is the visited domain data management network element.
[0227] In another possible implementation, the communication device 800 can correspondingly implement the behavior and functions of the session management function network element (e.g., including H-SMF or V-SMF) in the above method embodiments. The communication device 800 can be a session management function network element, a component (e.g., a chip or circuit) applied in the session management function network element, or a chip or chipset in the session management function network element, or a part of a chip used to perform related method functions. The transceiver module 820 can be used to support communication between the session management function network element and other network entities, such as supporting communication between the session management function network element and other network entities. Figures 4 to 7 Communication between network elements such as the visitor domain policy control function shown in any embodiment. Processing module 810 is used to control and manage the actions of the session management function network elements; for example, processing module 810 is used to support the execution of the session management function network elements. Figures 4 to 7 In any embodiment, the session management function network element performs all operations except for sending and receiving.
[0228] For example, the transceiver module 820 is used to receive a second request message from the policy control function to configure rules for forwarding data to the first V-EES and / or the first V-ECS to the visited domain user plane function. The second request message includes the address information of the first V-EES and / or the address information of the first V-ECS.
[0229] For example, the transceiver module 820 is used to receive first indication information, send a first request message to the visited domain policy control function network element, and receive a first response message from the V-PCF. The first indication information is used to instruct the UE's first HR session to use the VPLMN's edge computing function. The first request message is used to instruct the UE's first HR session to use the VPLMN's edge computing function. The first response message includes the address information of the first V-EES and / or the address information of the first V-ECS.
[0230] As an optional method, the transceiver module 820 receives the first indication information including:
[0231] The transceiver module 820 is used to receive a session establishment request message from the UE, the session establishment request message including first indication information; or, the transceiver module 820 is used to receive a session modification request message from the UE, the session modification request message including first indication information.
[0232] As an optional approach, the transceiver module 820 is also configured to configure rules for forwarding data to the first V-ECS and / or the first V-EES to the visited domain policy control function network element.
[0233] In another possible implementation, the communication device 800 can correspondingly implement the behavior and functions of the data management network element in the above method embodiments. The communication device 800 can be a data management network element, a component (e.g., a chip or circuit) applied in the data management network element, or a chip or chipset in the data management network element, or a part of a chip used to perform related method functions. The transceiver module 820 can be used to support communication between the data management network element and other network entities, such as supporting communication between the data management network element and other network entities. Figures 4 to 7 Communication between policy control functions, etc., as shown in any embodiment. Processing module 810 is used to control and manage the actions of data management network elements; for example, processing module 810 is used to support data management network elements in performing... Figures 4 to 7 All operations of the data management network element in any embodiment, except for sending and receiving.
[0234] For example, the transceiver module 820 is used to receive an AF request from the edge configuration server and store the address information of the first V-ECS and / or the address information of the first V-EES according to the AF request. The AF request includes one or more of the following: the address information of the first V-ECS and / or the address information of the first V-EES, a roaming identifier, a UE identifier, or a session identifier, wherein the roaming identifier is used to indicate whether the UE is a roaming UE, and the UE identifier includes one or more of the following: GPSI, SUPI, DNN, S-NSSAI, or the UE's application descriptor. The session identifier includes the UE's corresponding DNN, S-NSSAI, and / or application descriptor.
[0235] As an optional implementation, the transceiver module 820 is also used to receive subscription request messages from the policy control function network element and send notification messages to the visited domain policy control function network element. The subscription request message is used to request subscription to a notification message for an AF request associated with the first HR session. This notification message includes the address information of the first V-ECS and / or the address information of the first V-EES associated with the first HR session.
[0236] It should be understood that the processing module 810 in the embodiments of this application can be implemented by a processor or processor-related circuit components, and the transceiver module 820 can be implemented by a transceiver or transceiver-related circuit components.
[0237] like Figure 9 The diagram shows a communication device 900 provided in an embodiment of this application. The communication device 900 can be an edge configuration server, capable of implementing the functions of the edge configuration server in the method provided in this application; or, the communication device 900 can be a session management network element, capable of implementing the functions of the session management network element in the method provided in this application; or, the communication device 900 can be a policy control function network element, capable of implementing the functions of the policy control function network element in the method provided in this application; or, the communication device 900 can also be a device capable of supporting the policy control function network element, session management network element, or edge configuration server to implement the corresponding functions in the method provided in this application. The communication device 900 can be a chip system. In this embodiment, the chip system can be composed of chips or can include chips and other discrete devices.
[0238] In terms of hardware implementation, the transceiver module 820 can be a transceiver, which is integrated into the communication device 900 to form the communication interface 910.
[0239] The communication device 900 includes at least one processor 920. The processor 920 may be a CPU, microprocessor, ASIC, or one or more integrated circuits for controlling the execution of the program in this application, for implementing or supporting the communication device 900 in implementing the functions of the policy control function network element, session management network element, or edge configuration server in the methods provided in the embodiments of this application. See the detailed description in the method examples for specific details, which will not be repeated here.
[0240] The communication device 900 may further include at least one memory 930 for storing program instructions and / or data. The memory 930 is coupled to the processor 920. The coupling in this embodiment is an indirect coupling or communication connection between devices, units, or modules, and may be electrical, mechanical, or other forms, for information exchange between devices, units, or modules. The processor 920 may operate in conjunction with the memory 930. The processor 920 may execute the program instructions and / or data stored in the memory 930 to cause the communication device 900 to implement a corresponding method. At least one of the at least one memory may be included in the processor 920.
[0241] The communication device 900 may further include a communication interface 910, using any transceiver-like device, for communicating with other devices or communication networks, such as radio access networks (RAN), wireless local area networks (WLAN), wired access networks, etc. The communication interface 910 is used to communicate with other devices via a transmission medium, thereby enabling the devices in the communication device 900 to communicate with other devices. For example, when the communication device 900 is an edge configuration server, the other device is a policy control function network element or a session management network element; or, when the communication device is a policy control function network element, the other device is a session management network element or an edge configuration server. The processor 920 can use the communication interface 910 to send and receive data. Specifically, the communication interface 910 may be a transceiver.
[0242] This application embodiment does not limit the specific connection medium between the communication interface 910, processor 920, and memory 930. This application embodiment... Figure 9 The memory 930, processor 920, and communication interface 910 are connected via a bus 940. Figure 9 The connections between other components are shown in bold and are for illustrative purposes only, not as limiting information. The bus can be divided into address bus, data bus, control bus, etc. For ease of illustration, Figure 9 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.
[0243] In the embodiments of this application, the processor 920 may be a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components, and may implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly manifested as being executed by a hardware processor, or executed by a combination of hardware and software modules within the processor.
[0244] The memory 930 may be ROM or other types of static storage devices capable of storing static information and instructions, RAM or other types of dynamic storage devices capable of storing information and instructions, or electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but not limited thereto. The memory may exist independently and be connected to the processor via communication line 940. The memory may also be integrated with the processor.
[0245] The memory 930 stores computer execution instructions for implementing the scheme of this application, and its execution is controlled by the processor 920. The processor 920 executes the computer execution instructions stored in the memory 930 to implement the method provided in the above embodiments of this application.
[0246] Optionally, the computer execution instructions in the embodiments of this application may also be referred to as application code, and the embodiments of this application do not specifically limit this.
[0247] It should be noted that the communication device in the above embodiments can be a terminal, a circuit, a chip used in a terminal, or other combined devices or components with the aforementioned terminal functions. When the communication device is a terminal, the transceiver module can be a transceiver, which may include an antenna and radio frequency circuits, etc., and the processing module can be a processor, such as a central processing unit (CPU). When the communication device is a component with the aforementioned terminal functions, the transceiver module can be a radio frequency unit, and the processing module can be a processor. When the communication device is a chip or a chip system, the transceiver module can be the input / output interface of the chip or chip system, and the processing module can be the processor of the chip or chip system.
[0248] This application also provides a communication system. Specifically, the communication system includes a policy control function network element, an edge configuration server, and a session management network element, or it may further include more policy control function network elements, multiple session management network elements, and more edge configuration servers. It is understood that the communication system may also include one or more of AF, NEF, UDR, or BSF. Exemplarily, the communication system includes components for implementing the above... Figures 4 to 7 The policy control function network element, session management network element, and edge configuration server of any of the embodiments shown.
[0249] The edge configuration servers are respectively used to implement the functions of the relevant edge configuration server parts in the embodiments of this application, such as to implement the above. Figures 4 to 7 The functions of the visited domain edge configuration server or the home domain edge configuration server in any of the illustrated embodiments are described. The policy control function network element is used to implement the functions of the policy control function network element in the embodiments of this application, for example, to implement the above-described functions. Figures 4 to 7 The functions of the relevant policy control network element in any of the illustrated embodiments. The session management network element is used to implement the above. Figures 4 to 7 The functions of any relevant session management network element. Please refer to the relevant descriptions in the above method embodiments for details, which will not be repeated here.
[0250] This application also provides a computer-readable storage medium, including instructions that, when executed on a computer, cause the computer to perform... Figures 4 to 7 The method executed by the policy control function network element, session management network element, or edge configuration server in any of the embodiments shown.
[0251] This application also provides a computer program product, including instructions that, when run on a computer, cause the computer to perform... Figures 4 to 7 The method executed by the policy control function network element, session management network element, or edge configuration server in any of the embodiments shown.
[0252] This application provides a chip system including a processor and potentially a memory, for implementing the functions of the policy control network element, session management network element, and edge configuration server described in the aforementioned methods. The chip system can be composed of a single chip or may include chips and other discrete components.
[0253] The methods provided in this application can be implemented entirely or partially through software, hardware, firmware, or any combination thereof. When implemented in software, they can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this invention are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user equipment, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be magnetic media (e.g., floppy disk, hard disk, magnetic tape), optical media (e.g., digital video disc (DVD)), or semiconductor media (e.g., SSD), etc.
[0254] In this application embodiment, the number of nouns, unless otherwise specified, refers to "singular nouns or plural nouns," that is, "one or more." "At least one" means one or more, and "more than one" means two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, or B exists alone, where A and B can be singular or plural. The character " / " generally indicates that the related objects before and after are in an "or" relationship. For example, A / B means: A or B. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c means: a, b, c, a and b, a and c, b and c, or a and b and c, where a, b, and c can be single or multiple.
[0255] Those skilled in the art can make various modifications and variations to this application without departing from the scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.
Claims
1. A communication method, characterized in that, include: The first edge configuration server (ECS) receives a first request message, which includes configuration information of the application client (AC). The first ECS sends an Application Function (AF) request to the Policy Control Function (PCF). The AF request is used to request the configuration of the data forwarding path from the terminal to the first Visited Domain Edge Enable Server (V-EES) and / or the first Visited Domain Edge Configuration Server (V-ECS). The first ECS sends a response message to the first request message.
2. The method as described in claim 1, characterized in that, The AF request includes the address information of the first V-EES and / or the address information of the first V-ECS.
3. The method as described in claim 1 or 2, characterized in that, Before the first ECS sends the response message, the method further includes: The first ECS receives a user plane path change notification from the Visited Domain Session Management Function (V-SMF).
4. The method according to any one of claims 1-3, characterized in that, The response message includes the configuration information of the first V-EES and / or the configuration information of the first V-ECS.
5. The method according to any one of claims 1-4, characterized in that, The method further includes: The first ECS determines the first V-EES and / or the first V-ECS based on the configuration information of the AC.
6. The method according to any one of claims 1-5, characterized in that, The first ECS is either the first V-ECS or the second V-ECS. The first ECS receives the first request message, including the first ECS receiving the first request message from the home domain ECS. The first ECS sends a response message to the first request message, including the first ECS sending the response message to the home domain ECS.
7. The method according to any one of claims 1-5, characterized in that, The first ECS is either the first V-ECS or the second V-ECS. The first ECS receives a first request message, including the first ECS receiving a first request message from an edge-enabled client (EEC). The first ECS sends a response message to the first request message, including the first ECS sending the response message to the EEC.
8. The method according to any one of claims 1-7, characterized in that, The first ECS is either the first V-ECS or the second V-ECS, and the PCF is the visited domain PCF.
9. The method according to any one of claims 1-5, characterized in that, The first ECS is the home domain ECS, and the PCF is the home domain PCF.
10. The method according to any one of claims 1-5 or 9, characterized in that, The first ECS is the home domain ECS, and the method further includes: The home domain ECS obtains information about the first V-EES and / or information about the first V-ECS from the third V-ECS.
11. A communication method, characterized in that, include: The Policy Control Function (PCF) receives an Application Function (AF) request, which is used to request a data forwarding path from the terminal to the First Visited Domain Edge Enable Server (V-EES) and / or the First Visited Domain Edge Configuration Server (V-ECS). The PCF sends a second request message to the Visited Domain Session Management Function (V-SMF) based on the AF request. The second request message includes the address information of the first V-EES and / or the address information of the first V-ECS.
12. The method as described in claim 11, characterized in that, The AF request message includes the address information of the first V-EES and / or the address information of the first V-ECS.
13. A communication method, characterized in that, include: The Visiting Domain Session Management Function (V-SMF) receives a second request message from the Policy Control Function (PCF). The second request message includes the address information of the first Visiting Domain Edge Enable Server (V-EES) and / or the address information of the first Visiting Domain Edge Configuration Server (V-ECS). The V-SMF configures rules for forwarding data to the first V-EES and / or the first V-ECS in the Visited Domain User Plane Function (V-UPF).
14. A communication device, characterized in that, include: A processor and an interface circuit, the interface circuit being configured to receive signals from other communication devices besides the communication device and transmit them to the processor, or to send signals from the processor to other communication devices besides the communication device, the processor being configured to implement the method as described in any one of claims 1-10 via logic circuits or execution code instructions.
15. A communication device, characterized in that, include: A processor and an interface circuit, the interface circuit being configured to receive signals from other communication devices besides the communication device and transmit them to the processor, or to send signals from the processor to other communication devices besides the communication device, the processor being configured to implement the method as described in any one of claims 11-12 via logic circuits or execution code instructions.
16. A communication device, characterized in that, include: The processor and interface circuitry, wherein the interface circuitry is configured to receive signals from other communication devices besides the communication device and transmit them to the processor, or to send signals from the processor to other communication devices besides the communication device, wherein the processor is configured to implement the method as described in claim 13 via logic circuitry or execution code instructions.
17. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions that, when executed, cause the computer to perform the method as described in any one of claims 1-10, or the method as described in any one of claims 11-12, or the method as described in claim 13.
18. A computer program product, characterized in that, The computer program product includes a computer program that, when executed, causes the method of any one of claims 1-12 to be performed, or causes the method of any one of claims 11-13 to be performed, or causes the method of claim 13 to be performed.
19. A communication system, characterized in that, It includes an edge configuration server, a policy control function network element, and a visited domain session management function network element, wherein the edge configuration server is used to perform the method as described in any one of claims 1-10, the policy control function network element is used to perform the method as described in any one of claims 11-12, and the visited domain session management function network element is used to perform the method as described in claim 13.
Citation Information
Patent Citations
Data distribution method and device in edge MEC
CN111083737A
Application relocation method and device, electronic equipment and storage medium
CN113676977A