CN113630749B - Method and device for acquiring edge service - Google Patents

Method and device for acquiring edge service Download PDF

Info

Publication number
CN113630749B
CN113630749B CN202110769700.7A CN202110769700A CN113630749B CN 113630749 B CN113630749 B CN 113630749B CN 202110769700 A CN202110769700 A CN 202110769700A CN 113630749 B CN113630749 B CN 113630749B
Authority
CN
China
Prior art keywords
information
edge configuration
configuration server
ecs
edge
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN202110769700.7A
Other languages
Chinese (zh)
Other versions
CN113630749A (en
Inventor
姚琦
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to CN202110769700.7A priority Critical patent/CN113630749B/en
Publication of CN113630749A publication Critical patent/CN113630749A/en
Priority to PCT/CN2022/103724 priority patent/WO2023280121A1/en
Application granted granted Critical
Publication of CN113630749B publication Critical patent/CN113630749B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/50—Service provisioning or reconfiguring
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition

Abstract

The application provides a method and a device for acquiring edge services, wherein the method comprises the following steps: the User Equipment (UE) receives strategy information corresponding to at least two edge configuration servers from the network equipment, wherein the strategy information comprises one or more of the following information: and determining the target edge configuration server in at least two edge configuration servers by the UE according to the strategy information. Therefore, the UE can determine the target edge configuration server to be accessed in the scene of a plurality of edge configuration servers, and the experience of the user edge service is ensured.

Description

Method and device for acquiring edge service
Technical Field
The present application relates to the field of communications, and more particularly, to a method and apparatus for acquiring an edge service.
Background
Currently, the following schemes are generally adopted for a User Equipment (UE) to obtain address information of an edge configuration server (edge configuration server, ECS): the ECS may send its address information to the unified data management network element (unified data management, UDM), and when the UE requests the session management function network element (session management function, SMF) to acquire the address information of the ECS, the SMF may determine the address of the ECS according to the local configuration or the subscription data of the UE acquired from the UDM, and then the SMF sends the address information of the ECS to the UE.
As can be seen from the above, the network side can only determine one ECS address and send the ECS address to the UE. However, in the multi-ECS address scenario, if the SMF obtains multiple ECS addresses from the UDM according to a local configuration, the SMF cannot determine which ECS(s) to send to the UE; even if the UE receives address information of a plurality of ECSs sent by the SMF, the UE cannot determine which ECS to access to obtain the edge configuration information, which results in poor UE edge service experience.
Disclosure of Invention
The application provides a method and a device for acquiring edge service, which enable UE or a network side to determine ECS by enhancing URSP mechanism under a multi-ECS scene, thereby guaranteeing the experience of user edge service.
In a first aspect, a method for acquiring an edge service is provided, where the method includes: the User Equipment (UE) receives strategy information corresponding to at least two edge configuration servers from a first network element, wherein the strategy information comprises first type information of each edge configuration server, and the first type information comprises one or more of the following information: information of a service range, information of priority and identification information corresponding to each edge configuration server; and the UE determines a first edge configuration server from at least two edge configuration servers according to the first type of information in the strategy information.
According to the technical scheme, under the multi-ECS scene, the UE can receive the strategy information, wherein the strategy information comprises the information of the service range corresponding to each ECS, the information of the priority or the identification information, so that the UE can determine the target ECS to be accessed in the ECSs, and the experience of the edge business of the user is ensured. The method and the device solve the problem that in the prior art, the UE in the multi-ECS scene cannot determine the target ECS.
The policy information in the present application may be a user routing policy urs p.
The policy information in the present application at least includes information corresponding to two edge configuration servers. For example, the policy information may include: information of service range, information of priority, identification information of each edge configuration server.
In the application, the first type of information in the policy information can be used for the UE to determine the target ECS to be accessed later. Therefore, the content of the first type of information in the policy information can be flexibly determined, and each of the above cases is merely exemplary and not limited thereto.
With reference to the first aspect, in certain implementation manners of the first aspect, the policy information further includes second class information of each edge configuration server, where the second class information includes information of a data network name and/or single network slice selection auxiliary information corresponding to each edge configuration server, and the method further includes: the UE requests to establish a protocol data unit PDU session corresponding to the first edge configuration server according to the second type information in the strategy information; the UE accesses the first edge configuration server through the PDU session.
Based on the technical scheme, the policy information can also comprise second-class information, and the UE can assist in establishing the PDU session according to the second-class information in the policy information, so that the UE can access the target edge configuration server, and the experience of the edge service of the user is ensured.
In the application, the second type of information in the policy information may be used for the UE to subsequently establish a PDU session for determining the target ECS. Therefore, the content of the second type of information in the policy information can be flexibly determined, and each of the above cases is merely exemplary and not limiting.
With reference to the first aspect, in certain implementation manners of the first aspect, the policy information includes priority information of each edge configuration server, and the UE determines, according to second class information in the policy information, a first edge configuration server from the at least two edge configuration servers, including: if the priorities of the plurality of edge configuration servers are different, the UE determines the edge configuration server with the highest priority as the first edge configuration server.
Based on the technical scheme, the UE can determine the first ECS in the ECSs according to the priority information of each edge configuration server, and the experience of the edge service of the user is ensured.
With reference to the first aspect, in certain implementation manners of the first aspect, the policy information includes priority information and service range information of each edge configuration server, and the UE determines the first edge configuration server from the at least two edge configuration servers according to first type information in the policy information, including: if the priorities of the plurality of edge configuration servers are the same, the UE determines a first edge configuration server according to the service range of the edge configuration server and the position information of the UE.
Based on the technical scheme, the UE can determine the first ECS in the ECSs according to the priority information of each edge configuration server and the service range information, so that the experience of the edge service of the user is ensured.
With reference to the first aspect, in some implementations of the first aspect, the UE requesting to establish a protocol data unit PDU session corresponding to the first edge configuration server according to the second type of information in the policy information includes: and the UE sends a session establishment request to a second network element, wherein the session establishment request comprises a data network name and/or single network slice selection auxiliary information corresponding to the first edge configuration server.
Based on the above technical scheme, the UE may send a session establishment request to the AMF, so as to establish a PDU of the first edge configuration server, thereby accessing the first edge configuration server through the PDU session, and ensuring experience of the user edge service.
With reference to the first aspect, in certain implementation manners of the first aspect, the session establishment request further includes: first indication information, wherein the first indication information is used for indicating the capability of the UE and/or; and the second indication information is used for indicating the UE to request configuration information from the first edge configuration server.
Based on the above technical scheme, the session establishment request sent by the UE to the AMF may include the first indication information and/or the second indication information, so that the AMF may determine the SMF according to the first indication information and/or the second indication information, where the SMF supports the UE to access the first edge configuration server, and ensures the experience of the user edge service.
With reference to the first aspect, in certain implementation manners of the first aspect, after the UE establishes a protocol data unit PDU session corresponding to the first edge configuration server, the method further includes: the UE accesses the first edge configuration server via a session modification request.
Based on the technical scheme, the UE can access the first edge configuration server through the session modification request, so that the experience of the user edge service is ensured.
With reference to the first aspect, in some implementations of the first aspect, the first network element is a policy control network element, and the second network element is a mobility management network element.
In a second aspect, a method for acquiring an edge service is provided, where the method includes: the second network element receives a session establishment request from the user equipment UE, the session establishment request comprising: information of a data network name of a first edge configuration server and/or indication information, wherein the indication information comprises first indication information and/or second indication information, the first indication information is used for indicating the capability of the UE, the second indication information is used for indicating the UE to request configuration information from the first edge configuration server, the first edge configuration server is determined by the UE in at least two edge configuration servers according to strategy information, the strategy information comprises second type information of each edge configuration server, and the second type information comprises information of the data network name corresponding to each edge configuration server and/or single network slice selection auxiliary information; and the second network element determines a third network element according to the second type information and/or the indication information, and the third network element supports the UE to access the first edge configuration server.
According to the technical scheme, the second network element can determine the third network element according to the data network name of the first edge configuration server, or the single network slice selection auxiliary information, or the indication information, so that the third network element supports the UE to access the first edge configuration server, and the experience of the user edge service is guaranteed.
With reference to the second aspect, in certain implementations of the second aspect, the policy information further includes a first type of information of each edge configuration server, the first type of information including one or more of the following information: and configuring the information of the service range, the information of the priority and the identification information corresponding to the server by each edge.
Based on the technical scheme, the policy information in the application can also comprise the service range information, the priority information, the identification information and the like corresponding to the edge configuration server, so that the UE can determine the target ECS in a plurality of ECSs, and the user edge service experience is ensured.
With reference to the second aspect, in certain implementation manners of the second aspect, the policy information includes priority information of each edge configuration server, and the first edge configuration server is determined by the UE in at least two edge configuration servers according to the policy information, including: if the priorities of the plurality of edge configuration servers are different, the first edge configuration server is the edge configuration server with the highest priority.
With reference to the second aspect, in certain implementation manners of the second aspect, the policy information includes priority information and service range information of each edge configuration server, and the first edge configuration server is determined by the UE in at least two edge configuration servers according to the policy information, including: and if the priorities of the plurality of edge configuration servers are the same, determining the first edge configuration server for the UE according to the service range of the edge configuration server and the position information of the UE.
With reference to the second aspect, in certain implementations of the second aspect, the method further includes: the second network element receives a session modification request from the UE, the session modification request comprising a first request for the UE to request configuration information from the first edge configuration server; the second network element sends the session modification request to the third network element.
Based on the technical scheme, the second network element can establish a session modification request, and access the first edge configuration server through the PDU session modification flow, so that the experience of the user edge service is ensured.
With reference to the second aspect, in certain implementations of the second aspect, the method further includes: the second network element receives strategy information corresponding to at least two edge configuration servers from the first network element; and the second network element sends the strategy information to the UE.
In a third aspect, a method for acquiring an edge service is provided, where the method includes: the method comprises the steps that User Equipment (UE) sends a session establishment request to a third network element, wherein the session establishment request comprises a data network name of an edge configuration server and second indication information, and the second indication information is used for indicating the UE to request the edge configuration server for configuration information; the UE receives policy information from a first network element, wherein the policy information comprises identification information and a data network name of a second edge configuration server, the policy information is used for indicating the UE to access the second edge configuration server through the session, and the second edge configuration server is determined by a third network element according to the second indication information; and the UE determines to access the second edge configuration server through the session according to the strategy information.
In the present application, the third network element may determine, according to the second indication information, that the UE needs to access the edge configuration server, and then the third network element may determine, according to local configuration and/or obtaining subscription information from the UDM, a target ECS, for example, the second ECS.
Under the scene of multiple ECSs, according to the method, the network equipment can determine the target ECS which the UE needs to access in the multiple ECSs through the corresponding relation between each ECS and each DNN, so that the experience of the edge service of the user is ensured. Therefore, the problem that the network equipment in the multi-ECS scene cannot determine the target ECS in the prior art is solved.
With reference to the third aspect, in some implementations of the third aspect, the session establishment request further includes: and the first indication information is used for indicating the capability of the UE.
Based on the above technical solution, the session establishment request sent by the UE to the AMF may include the first indication information, so that the AMF may determine the SMF according to the first indication information or the second indication information or the data network name, where the SMF supports the UE to access the first edge configuration server, and ensures the experience of the user edge service.
With reference to the third aspect, in some implementations of the third aspect, the first network element is a policy control network element, the second network element is a mobility management network element, and the third network element is a session management network element.
In a fourth aspect, a method for acquiring an edge service is provided, where the method includes: the second network element receives a session establishment request from User Equipment (UE), wherein the session establishment request comprises a data network name and/or indication information of an edge configuration server, the indication information comprises first indication information and/or second indication information, the first indication information is used for indicating the capability of the UE, and the second indication information is used for indicating the UE to request configuration information from the edge configuration server; the second network element determines a third network element according to the data network name and/or the indication information, the third network element supports the UE to access a second edge configuration server, and the second edge configuration server is determined by the third network element according to the indication information.
According to the technical scheme, the second network element can determine the third network element according to the data network name and/or the indication information of the second edge configuration server, so that the third network element supports the UE to access the first edge configuration server, and the experience of the edge service of the user is guaranteed.
With reference to the fourth aspect, in certain implementations of the fourth aspect, the method further includes: the second network element receives a session modification request from the UE, the session modification request comprising a first request for the UE to request configuration information from the second edge configuration server; the second network element sends the session modification request to the third network element.
With reference to the fourth aspect, in certain implementations of the fourth aspect, the method further includes: the second network element receives policy information from the first network element, wherein the policy information comprises identification information of a second edge configuration server and a data network name, and the policy information is used for indicating the UE to access the second edge configuration server through the session; and the second network element sends the strategy information to the UE.
With reference to the fourth aspect, in some implementations of the fourth aspect, the first network element is a policy control network element, the second network element is a mobility management network element, and the third network element is a session management network element.
In a fifth aspect, an apparatus for acquiring an edge service is provided, where the apparatus may be a terminal device, for example, a user equipment UE. The device may also be a chip. The apparatus has functionality to implement a user equipment, UE, in any of the above first aspect or any of the third aspects or any of the possible implementations thereof. The functions can be realized by hardware, and can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules or units corresponding to the functions described above.
In a sixth aspect, an apparatus for acquiring an edge service is provided, where the apparatus may be a second network element, e.g. a mobility management network element. The device may also be a chip. The apparatus has the functionality to implement the second network element in any of the second or fourth aspects or any of the possible implementations of any of the above aspects. The functions can be realized by hardware, and can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules or units corresponding to the functions described above.
In a seventh aspect, an apparatus for acquiring an edge service is provided, including a processor. The processor is coupled to the memory and operable to execute instructions in the memory to implement the functionality of the terminal device, which may be, for example, the user equipment UE, in any of the possible implementations of any of the above first aspect or third aspect. Optionally, the apparatus further comprises a memory. Optionally, the apparatus further comprises a communication interface, the processor being coupled to the communication interface.
In one implementation, the apparatus is a terminal device. When the apparatus is a terminal device, the communication interface may be a transceiver, or an input/output interface.
In another implementation, the apparatus is a chip configured in a terminal device. When the apparatus is a chip configured in a terminal device, the communication interface may be an input/output interface.
Alternatively, the transceiver may be a transceiver circuit. Alternatively, the input/output interface may be an input/output circuit.
In an eighth aspect, an apparatus for acquiring an edge service is provided, including a processor. The processor is coupled to the memory and operable to execute instructions in the memory to implement the functionality of a second network element, which may be, for example, a mobility management network element, in any of the above second or fourth aspects or any of the possible implementations of any of the above second or fourth aspects. Optionally, the apparatus further comprises a memory. Optionally, the apparatus further comprises a communication interface, the processor being coupled to the communication interface.
In one implementation, the apparatus is a second network element, such as an AMF. When the apparatus is a terminal device, the communication interface may be a transceiver, or an input/output interface.
In another implementation, the apparatus is a chip configured in the second network element. When the apparatus is a chip configured in a terminal device, the communication interface may be an input/output interface.
Alternatively, the transceiver may be a transceiver circuit. Alternatively, the input/output interface may be an input/output circuit.
In a ninth aspect, there is provided a processor comprising: input circuit, output circuit and processing circuit. The processing circuit is configured to receive a signal via the input circuit and transmit a signal via the output circuit, such that the processor performs the method of any one of the first to fourth aspects or any one of the possible implementations of any one of the first to fourth aspects.
In a specific implementation process, the processor may be a chip, the input circuit may be an input pin, the output circuit may be an output pin, and the processing circuit may be a transistor, a gate circuit, a trigger, various logic circuits, and the like. The input signal received by the input circuit may be received and input by, for example and without limitation, a receiver, the output signal may be output by, for example and without limitation, a transmitter and transmitted by a transmitter, and the input circuit and the output circuit may be the same circuit, which functions as the input circuit and the output circuit, respectively, at different times. The embodiments of the present application do not limit the specific implementation manner of the processor and the various circuits.
In a tenth aspect, an apparatus is provided that includes a processor and a memory. The processor is configured to read instructions stored in the memory and is configured to receive a signal via the receiver and to transmit a signal via the transmitter to perform the method of any one of the first to fourth aspects or any one of the possible implementations of any one of the first to fourth aspects.
Optionally, the processor is one or more, and the memory is one or more.
Alternatively, the memory may be integrated with the processor or the memory may be separate from the processor.
In a specific implementation process, the memory may be a non-transient (non-transitory) memory, for example, a Read Only Memory (ROM), which may be integrated on the same chip as the processor, or may be separately disposed on different chips.
It should be appreciated that the related data interaction process, for example, transmitting the indication information, may be a process of outputting the indication information from the processor, and the receiving the capability information may be a process of receiving the input capability information by the processor. Specifically, the data output by the processing may be output to the transmitter, and the input data received by the processor may be from the receiver. Wherein the transmitter and receiver may be collectively referred to as a transceiver.
The apparatus in the tenth aspect may be a chip, the processor may be implemented by hardware or may be implemented by software, and when implemented by hardware, the processor may be a logic circuit, an integrated circuit, or the like; when implemented in software, the processor may be a general-purpose processor, implemented by reading software code stored in a memory, which may be integrated in the processor, or may reside outside the processor, and exist separately.
In an eleventh aspect, there is provided a computer program product comprising: a computer program (which may also be referred to as code, or instructions) which, when executed, causes a computer to perform the method of any one of the first to fourth aspects or any one of the possible implementations of any one of the first to fourth aspects.
In a twelfth aspect, there is provided a computer readable medium storing a computer program (which may also be referred to as code, or instructions) which, when run on a computer, causes the computer to perform the method of any one of the first to fourth aspects or any one of the possible implementations of any one of the first to fourth aspects.
In a thirteenth aspect, a chip system is provided, comprising a processor for calling and running a computer program from a memory, so that a device in which the chip system is installed performs the method of any one of the above-mentioned first to fourth aspects or any one of the possible implementation manners of any one of the above-mentioned aspects.
In a fourteenth aspect, there is provided a system comprising the apparatus of the fifth aspect, the apparatus of the sixth aspect.
Drawings
Fig. 1 is a diagram of a system architecture to which embodiments of the present application are applicable.
Fig. 2 is a schematic diagram of an edge service architecture according to an embodiment of the present application.
Fig. 3 is a schematic flow chart of a method 300 of acquiring edge services provided herein.
Fig. 4 is a schematic flow chart of a method 400 of acquiring edge services provided herein.
Fig. 5 is a schematic flow chart diagram of a method 500 for acquiring edge services provided herein.
Fig. 6 is a schematic block diagram of an apparatus 100 for acquiring an edge service provided herein.
Fig. 7 is a schematic block diagram of an apparatus 200 for acquiring an edge service provided herein.
Detailed Description
The technical solutions in the present application will be described below with reference to the accompanying drawings.
Wireless communication systems mentioned in embodiments of the present application include, but are not limited to: global system for mobile communications (global system of mobile communication, GSM), long term evolution (long term evolution, LTE) frequency division duplex (frequency division duplex, FDD) system, LTE time division duplex (time division duplex, TDD), LTE system, long term evolution-Advanced (LTE-a) system, next generation communication system (e.g., 6G communication system), a converged system of multiple access systems, or evolved system.
The technical solutions provided herein may also be applied to machine-type communication (machine type communication, MTC), inter-machine communication long term evolution technology (Long Term Evolution-machine, LTE-M), device-to-device (D2D) networks, machine-to-machine (machine to machine, M2M) networks, internet of things (internet of things, ioT) networks, or other networks. The IoT network may include, for example, an internet of vehicles. The communication modes in the internet of vehicles system are generally called as vehicle to other devices (V2X, X may represent anything), for example, the V2X may include: vehicle-to-vehicle (vehicle to vehicle, V2V) communication, vehicle-to-infrastructure (vehicle to infrastructure, V2I) communication, vehicle-to-pedestrian communication (vehicle to pedestrian, V2P) or vehicle-to-network (vehicle to network, V2N) communication, etc.
The terminal device referred to in the embodiments of the present application may include various access terminals, mobile devices, user terminals, or user apparatuses having a wireless communication function. For example, the terminal device may be a User Equipment (UE), such as a mobile phone (mobile phone), a tablet (Pad), a computer with wireless transceiving function, a Virtual Reality (VR) terminal device, an augmented reality (augmented reality, AR) terminal device, and the like. The terminal devices may also be wireless terminals in industrial control (industrial control), machine type communication (machine type communication, MTC) terminals, customer terminal devices (customer premise equipment, CPE), wireless terminals in self-driving (self-driving), wireless terminals in telemedicine (remote media), wireless terminals in smart grid (smart grid), wireless terminals in transportation security (transportation safety), wireless terminals in smart city (smart home), smart home (smart home), cellular phones, cordless phones, session initiation protocol (session initiation protocol, SIP) phones, wireless local loop (wireless local loop, WLL) stations, personal digital assistants (personal digital assistant, PDA), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, vehicle devices, wearable devices, terminal devices in 5G networks or terminal devices in future evolving public land mobile communication networks (public land mobile network, PLMN), etc.
Embodiments of the present application relate to a network system architecture and an edge traffic architecture under the architecture, as described in detail below with reference to fig. 1 and 2.
Fig. 1 is a system architecture diagram applicable to the embodiment of the present application, and as shown in the figure, the network architecture may specifically include the following network elements:
1. radio access network (radio access network, RAN): an access network implementing access network functions based on wireless communication technology may be referred to as a radio access network. The radio access network can manage radio resources, provide access service for the terminal, and further complete the forwarding of control signals and user data between the terminal and the core network.
The radio access network device according to the present application may be a device having a radio transceiver function. The radio access network device may be a device that provides wireless communication functionality services, typically located on the network side, including but not limited to: next generation base stations (gndeb, gNB) in the fifth generation (5th generation,5G) communication system, next generation base stations in the sixth generation (6th generation,6G) mobile communication system, base stations in the future mobile communication system, access nodes in the WiFi system, and the like, evolved Node bs (enbs) in the LTE system, radio network controllers (radio network controller, RNC), node Bs (NB), base station controllers (base station controller, BSC), home base stations (e.g., home evolved NodeB, or home Node bs, HNBs), base Band Units (BBU), transmission reception points (transmission reception point, TRP), transmission points (transmitting point, TP), base transceiver stations (base transceiver station, BTS), and the like. In one network architecture, the access network device may include a Centralized Unit (CU) node, or a Distributed Unit (DU) node, or a RAN device including a CU node and a DU node, or a control plane CU node and a user plane CU node, and a RAN device of a DU node. The access network device provides services for a cell, and the user equipment communicates with the base station through transmission resources (e.g., frequency domain resources, or spectrum resources) used by the cell, where the cell may be a cell corresponding to the base station (e.g., a base station), and the cell may belong to a macro base station or a base station corresponding to a small cell (small cell), where the small cell may include: urban cells (metro cells), micro cells (micro cells), pico cells (pico cells), femto cells (femto cells) and the like, and the small cells have the characteristics of small coverage area and low transmitting power and are suitable for providing high-rate data transmission services. The wireless access network device may be a macro base station, a micro base station or an indoor station, a relay node or a donor node, a device in the V2X communication system for providing wireless communication service for the user device, a wireless controller in a cloud wireless access network (cloud radio access network, CRAN) scenario, a relay station, a vehicle-mounted device, a wearable device, a network device in a future evolution network, and the like. The embodiment of the application does not limit the specific technology and the specific equipment form adopted by the wireless access network equipment.
2. Authentication service function (authentication server function, AUSF) network element: the method is mainly used for user authentication and the like.
3. Access and mobility management function network element (access and mobility management function, AMF): the method is mainly used for mobility management, access management and the like, and can be used for realizing other functions besides session management in the functions of a mobility management entity (mobility management entity, MME), such as legal interception, access authorization (or authentication) and the like. In the embodiment of the application, the method and the device can be used for realizing the functions of the access and mobile management network elements.
4. Session management function network element (session management function, SMF): the method is mainly used for session management, IP address allocation and management of terminal equipment, selection and management of a user plane function, policy control, or a terminal node of a charging function interface, downlink data notification and the like. In the embodiment of the application, the method and the device can be used for realizing the function of the session management network element.
5. Policy control network element (policy control function, PCF): a unified policy framework for guiding network behavior, providing policy rule information for control plane function network elements (e.g., AMF, SMF network elements, etc.), and the like.
6. -application function network element (application function, AF): the method is used for carrying out data routing of application influence, accessing network elements with open functions of the network, or carrying out strategy control and the like in interaction with a strategy framework.
7. Unified data management network element (unified data management, UDM): for unified data management, 5G user data management, handling user identification, access authentication, registration, or mobility management, etc.
8. User plane function network element (user plane function, UPF): quality of service (quality of service, qoS) handling, etc. for packet routing and forwarding, or user plane data. User data may be accessed to a Data Network (DN) through the network element. In the embodiment of the application, the method and the device can be used for realizing the functions of the user plane network element.
9. Network slice selection function network element (network slice selection function, NSSF): for managing network slice related information.
10. Data Network (DN): for providing a network for transmitting data. Such as a network of operator services, internet network, third party service network, etc.
The network architecture further includes a network storage function element ((networkrepository function, NRF)) for storing the description information of the network function entity and its service provided, and supporting functions such as service discovery and network element entity discovery, a network opening function element (network exposure function, NEF) for safely opening services and capabilities provided by a third generation partnership project (3 GPP) network function to the outside, and the like, a unified data storage function element (unified data repository, UDR) for UDM storing subscription data or reading subscription data and PCF storing policy data or reading policy data.
In the network architecture, an N2 interface is an interface of RAN and AMF network elements, and is used for sending non-access stratum (NAS) messages and the like; the N3 interface is an interface between the RAN and the UPF network element and is used for transmitting data of a user plane and the like; the N4 interface is an interface between the SMF network element and the UPF network element, and is used for transmitting information such as tunnel identification information, data buffer indication information, downlink data notification message, and the like of the N3 connection.
It should be understood that the network architecture applied to the embodiments of the present application is merely an exemplary network architecture described from the perspective of a conventional point-to-point architecture and a service architecture, and the network architecture to which the embodiments of the present application are applicable is not limited thereto, and any network architecture capable of implementing the functions of the respective network elements described above is applicable to the embodiments of the present application.
It should be understood that the names of interfaces between the network elements in fig. 1 are only an example, and the names of interfaces in the specific implementation may be other names, which are not specifically limited in this application. Furthermore, the names of the transmitted messages (or signaling) between the various network elements described above are also merely an example, and do not constitute any limitation on the function of the message itself.
Fig. 2 is a schematic diagram of an edge service architecture according to an embodiment of the present application, and as shown in the drawing, the network architecture may specifically include: an edge data network (edge data network, EDN) (including an edge enablement server (edge enabler server, EES) edge application server (edge application server, EAS)), an edge configuration server (edge configuration server, ECS), and a User Equipment (UE).
The EDNs may be local data centers, among others, and comprise one or more EESs and EAS's, each with a particular service area.
The User Equipment (UE) may include: an edge enabled client (edge enabler client, EEC) and an application client, wherein the EEC provides necessary support for the application client on the terminal, the functionality of the EEC comprising: EDN information is retrieved by EDGE-4, the UE registers with the EES, available EAS is retrieved, EAS availability changes, EAS migration notification to the EEC.
The ECS network element (also referred to as an edge data network configuration server (edge data network configuration server, EDNCS)) may be a global management network element, maintaining information for each EDN, including the service scope of the edge data network and the edge enable server EES address in the edge data network, etc. The service range of the edge data network may be topology address information (for example, cell ID, TAI (Track area ID), etc.) or geometric address information (for example, information of province, city, district, longitude and latitude, etc.), and the service range may be a set of address information. In one implementation, the ECS network elements are distributed, i.e., each ECS can manage the edge data network for a different area. It should be understood that the ECS network element may be co-located with other network elements or may be a separate network element, and the application does not limit the deployment of the ECS network element in the network architecture.
The EES network element, which may be a control network element or a management network element in the MEC node, is responsible for managing each EAS deployed in the EDN, such as registration, DNS resolution content routing, upper layer application registration management, wireless information interaction, and other basic functions. Furthermore, EES may invoke capability opening function network elements in the 3GPP network. It should be understood that the EES network element may be co-located with other network elements or may be an independent network element, and the present application does not limit the deployment of the EES network element in the network architecture.
The EES, EAS, ECS, etc. may be referred to as AF (application function), and will not be described in detail.
The function of each reference point in fig. 2 is briefly described below.
The EDGE-8 reference point in fig. 2 supports interactions between the EDGE configuration server and the core network, which supports: (1) Accessing core network functions and application program interfaces (application programming interface, API) for retrieving network capability information; (2) The core network (e.g., SMF) is provided with a service delivery notification. EDGE-1: an interface between the EES and the EECs supporting registration/de-registration of the EECs in the EES; edge application server discovery in an edge data network. EDGE-2: an interface between the EES and the 3GPP core network for the EES to acquire 3GPP network capabilities. EDGE-3: an interface between the EES and EAS, supporting EES registration/de-registration of EAS, including availability information, service range information, address information, etc. of EAS; EES provides 3GPP network capability information (e.g., location information) to EAS. EDGE-4: the interface between the EEC and the ECS supports the ECS to provide/push configuration information to the EEC. EDGE-5: the interface between the AC and the EEC supports the AC to obtain access to the EAS information from the EEC. EDGE-6: the interface between the ECS and the EES supports the configuration of EES information on the ECS. EDGE-7: the interface between EAS and the 3GPP core network supports EAS acquisition 3GPP network capabilities. EDGE-8: and an interface between the ECS and the 3GPP core network supports the ECS to acquire the capability of the 3GPP network. EDGE-9: and the interfaces between different EESs in the same MEC node are crossed to support the application migration.
The foregoing briefly describes a system architecture and possible application scenarios of the embodiments of the present application, and in order to better understand the technical solutions of the embodiments of the present application, before beginning to introduce the embodiments of the present application, a brief description is first given of terms or terms involved in the present application.
1) Data network name (data network name, DNN): the data network name DNN may be used to select the SMF and UPF that establish a protocol data unit (protocol data unit, PDU) session, and may also be used to determine the policy to apply to the PDU session. The composition of DNN is two: 1) A network Identification (ID), which represents an external network, optionally; 2) The operator ID, which in part indicates which operator it belongs to, is optional.
2) Single network slice selection assistance information (single network slice selection assistance information, S-NSSAI): a network slice may be uniquely identified, possibly containing one or more data network names DNN, for selection by the AMF. Wherein the SMF selected for the PDU session is specified in the DNN. NSSAI is a collection of S-NSSAI that can identify a set of network slices. The UE can select the corresponding slice group (including AMF/SMF/UPF) through S-NSSAI when doing business. When the UE performs attachment (attach), the UE provides S-NSSAI information, and the gNB selects a 5G core network (5G Core Network,5GC) according to the S-NSSAI information; if the UE does not provide relevant S-nsai information, the gNB will route the NAS information of the UE to a default 5GC.
3) UE routing policy (UE route selection policy, urs): is a list containing one or more urs rules (rule). Each urs rule in the urs consists of a rule priority (precedence), traffic descriptor (traffic descriptor) and routing descriptor (route selection descriptor, RSD) list of that rule. The priority of each rule is different, and the rules are ordered from high to low according to priority. The priority determines the order in which the UEs use the urs rules.
The traffic descriptor is composed of one or more components (components) and may include: application descriptor (application descriptor), internet protocol (Internet protocol, IP) descriptor (IP descriptor), such as: destination IP, domain descriptors (domain descriptor), e.g., fully qualified domain name (fully qualified domain name, FQDN), non-IP descriptor (non-IP descriptor), DNN descriptor, and connectivity capability (connection capabilities). The traffic descriptor may be used by the UE for application matching.
The routing descriptor RSD list contains one or more RSDs, each RSD consisting of a respective RSD priority (RSD preference), a routing component (route selection components) and a routing check criterion (route selection verification criteria). The RSD priority determines the order of RSDs, and other RSDs are used when RSDs with high priority cannot be used. The routing component describes various network resources that an application can use, which is made up of one or more components, which can include traffic and session continuity (SSC) mode selection (SSC mode selection), network slice selection (network slice selection), DNN selection (DNN selection), PDU session type selection (PDU session type selection), slotted offload indication (non-seamless offload indication), access type priority (access type preference). The routing verification criteria describes corresponding validation conditions including a time window (time window) and a location criterion (location criteria), and RSD is considered invalid if the current time is not within the time window or the UE location does not match the location criterion.
For each application, the UE sequentially inquires whether a certain rule is applicable or not according to the priority of the rule from high to low, and if so, the rule is used; if none of the rules except the priority is applicable, the rule with the lowest priority is used, which corresponds to the default rule and is applicable to all applications. Wherein each rule corresponds to a particular PDU session (including: session type, SSC mode, slice, DNN, etc.), which is used by the application when the corresponding session exists; when a session does not exist, a new satisfactory session is established.
It will also be appreciated that the urs p may be used to let the terminal select (or set up) a PDU session (or slice). The UE may determine whether the detected application may be associated with an established PDU session, may offload non-3 GPP access outside of the PDU session, or may trigger establishment of a new PDU session, according to a urs policy. The urs rule is applicable when each component in the service descriptor matches the corresponding information from the application. The urs rule does not apply when the corresponding information from the application does not match any value in the traffic descriptor component or no corresponding information from the application is available. Specifically, the usage rules and procedures of the urs p may refer to the protocol TS 24.526, which is not described herein.
Currently, the following scheme is generally adopted for the UE to acquire address information of the ECS of the edge configuration server: the ECS may send its address information to the UDM network element first, and when the UE requests to the SMF to obtain the address information of the ECS, the SMF may determine the ECS address according to local configuration or obtain the subscription data of the UE from the UDM, and then the SMF sends the address information of the ECS to the UE. As can be seen from the above, the network side can only determine one ECS address and send the ECS address to the UE. However, in the multi-ECS address scenario, if the SMF obtains multiple ECS addresses from the UDM according to a local configuration, the SMF cannot determine which ECS(s) to send to the UE; for the UE, even if the address information of a plurality of ECSs sent by the SMF is received, the UE cannot determine which ECS to access to obtain the edge network configuration information, which results in poor UE edge service experience.
In view of this, the present application provides a method for obtaining edge services, by enhancing the urs p mechanism, so that the network side and the UE can determine the ECS, thereby guaranteeing the experience of the user edge service.
The method provided by the embodiment of the present application will be described in detail below with reference to the accompanying drawings. It should be noted that, in the following description of the embodiments with reference to the drawings, the drawings are only schematic for understanding, and should not be construed as limiting the present application. The names of the network elements are defined only for distinguishing different functions, and should not constitute any limitation to the present application. The present application does not exclude the possibility of defining other network elements to perform the same or similar functions.
The identification message in the embodiment of the present application may refer to address information, that is, the identification information in the embodiment of the present application may include address information of an edge server (for example, ECS). In addition, an identification (e.g., ECS ID) of the edge server may be further included, for example, a uniform resource identifier (uniform resource identifier, URI) of the edge server, IP address information of the edge server, an instance identifier (instance ID) of the edge server may be further included, and FQDN of the edge server may be further included. In other words, in the present application, address information of the edge server may be obtained according to the identification message.
It should be noted that the foregoing is merely an example of the identification information, and should not be construed as limiting the application, and the application does not exclude the identification information from any other information that may obtain the address information of the edge server.
Fig. 3 is a schematic block diagram of a method 300 of acquiring edge services provided herein. The method comprises the following steps:
in step 301, the ue receives policy information corresponding to at least two edge configuration servers from a first network element.
The policy information includes a first type of information for each edge configuration server, the first type of information including one or more of: and configuring the information of the service range, the information of the priority and the identification information corresponding to the server by each edge.
In one possible implementation manner, the UE may receive policy information corresponding to a plurality of ECSs from the PCF, where the policy information corresponding to each ECS is a first type of information of each edge configuration server, and the first type of information includes one or more of the following information: and configuring the information of the service range, the information of the priority and the identification information corresponding to the server by each edge.
As one example, the UE may receive the urs (an example of policy information) corresponding to the 3 ECSs from the PCF, e.g., the UE may receive policy information of ecs#1, ecs#2, and ecs#3. If the UE only needs the information of the ECS priority, the policy information can only contain the information of each ECS priority; if the UE needs ECS service range information in addition to ECS priority information, the policy information may include each ECS priority information and ECS service range information. If the UE needs the identification information of the ECS, the policy information may further include the identification information of the ECS.
In this application, the content of the first type of information in the policy information may be flexibly determined, and the above cases are merely examples, and are not limited thereto.
In this application, one ECS may correspond to one urs, and at this time, the UE may receive multiple urs corresponding to multiple ECSs. For example, the UE may receive the urs corresponding to ecs#1, ecs#2, and ecs#3. In this application, there may be one urs corresponding to a plurality of ECSs, where the UE only needs to receive one urs, and the one urs includes 3 ECSs.
In step 302, the ue determines a first edge configuration server from at least two edge configuration servers according to the first type of information in the policy information.
In this embodiment, taking UE receiving the urs corresponding to 3 ECSs as an example, for example: take ecs#1, ecs#2, and ecs#3 as examples of the urs p.
As an example, if only the ECS priority information is included in the urs, the UE may determine the ECS with the highest priority among ecs#1, ecs#2, and ecs#3 as the first ECS, e.g., the ecs#2 with the highest priority, and the UE determines ecs#2 as the first ECS.
As an example, if only the information of the service range of the ECS is included in the urs, the UE may determine the first ECS together according to its own location information and the information of the service ranges of ecs#1, ecs#2, and ecs#3. For example, the service area of ecs#1 just covers the location where the UE is currently located, at which time the UE may determine ecs#1 as the first ECS. For another example, the service areas of ecs#1, ecs#2, and ecs#3 all cover the current location of the UE, and ecs#1 is nearest to the UE, at which time the UE may also determine ecs#1 as the first ECS, and so on.
As another example, if priority information of each ECS and information of service ranges of the ECS are included in the urs, the UE may determine the first ECS according to the service ranges of the edge configuration servers and the location information of the UE if priorities of the plurality of edge configuration servers are the same.
In the application, in a multi-ECS scenario, if a plurality of pieces of information are included in the urs corresponding to the ECSs received by the UE, the UE may flexibly determine the first ECS.
Optionally, the policy information in the present application may further include second class information of each edge configuration server, where the second class information includes information of a data network name and/or single network slice selection auxiliary information corresponding to each edge configuration server.
In some embodiments, the UE may further request to establish a protocol data unit PDU session corresponding to the first edge configuration server according to the second type of information in the policy information. In one possible implementation, the UE may create a session of DNN and S-NSSAI corresponding to ECS#1. For example, the UE may request to the AMF to establish a protocol data unit PDU session corresponding to a first ECS (e.g., ecs#1). The session includes DNN and/or S-NSSAI corresponding to ECS#1. The UE may then access the first edge configuration server via the PDU session.
In a multi-ECS scene, according to the method, the UE determines the target ECS to be accessed according to the corresponding relation between each ECS in the received URSP and the respective service range and priority in the multi-ECS, and establishes PDU session of the target ECS according to DNN and N-SSAI, and accesses the edge service through the session, so that the experience of the edge service of the user is ensured. That is, by enhancing the existing urs p mechanism, the technical effect that the UE determines the target ECS to be accessed from among the multiple ECSs is achieved under the condition of small modification to the prior art, and the experience of the edge service of the user is ensured.
Fig. 4 is a schematic flow chart of a method 400 for obtaining an edge service provided in the present application, where the method 400 shown in fig. 4 may be performed by network elements such as AMF, SMF, NEF, UDM, PCF and ECS in the system shown in fig. 1. As shown in fig. 4, the method includes steps 401 to 412, which are described in detail below, taking ue#1 as an example in this embodiment.
In step 401, the ecs sends its own configuration information to the UDM.
The configuration information of the ECS includes: data network name DNN information of the ECS, ECS service scope information, ECS priority information, ECS identification information (it will also be understood that the ECS corresponds to or is associated with identification information), single network slice selection assistance information S-NSSAI of the ECS, and the like.
In one possible implementation, the ECS may invoke a parameter provisioning service of the NEF, e.g., parameter provisionservice sends the configuration information to the NEF, which in turn sends the configuration information to the UDM or UDR.
In this application, there may be one or more ECSs in step 401, and when there are multiple ECSs, each ECS may send its various configuration information to the UDM.
Alternatively, the UDM may also send configuration information to the UDR, which is stored by the UDR.
In step 402, the udm or UDR sends notification information to the PCF to notify the UE that the subscription data has changed. Correspondingly, the PCF receives the notification information.
Wherein the PCF may be the PCF serving the UE, e.g., UE # 1.
In one possible implementation, the PCF may subscribe to the UDM or UDR for notification of a subscription data change event for the UE, and may send notification information to the PCF subsequently when the UDM or UDR detects a change in the subscription data for the UE.
As an example, the notification information may include ECS configuration information, for example, one or more of ECS data network name DNN information, ECS service range information, and ECS priority information. As another example, the notification information may further include ECS identification information (it may also be understood that the ECS corresponds to or is associated with the ECS), S-NSSAI of the ECS, and the like.
In step 403, the pcf generates a user routing policy urs p (an example of policy information).
The urs p may include a first type of information for each edge configuration server, wherein the first type of information includes one or more of the following: and configuring the information of the service range, the information of the priority and the identification information corresponding to the server by each edge.
In some embodiments, the urs p may further include second class information of each edge configuration server, where the second class information includes information of a data network name and/or single network slice selection auxiliary information corresponding to each edge configuration server.
In one possible implementation, the PCF may generate the user routing policy urs p after receiving a notification message from the UDM or UDR.
Wherein the DNN information and S-NSSAI information of the ECS may be contained in a routing component (route selection components) field of a routing descriptor in the urs p. The service scope information of the ECS may be included in a location criteria (location criteria) field of the routing descriptor in the urs p. The ECS identification information may be included in an IP descriptor (IP descriptor) or a domain descriptor (domain descriptor) of the traffic descriptor in the urs p. The priority information of the ECS may be contained in a priority value (priority value) field in the urs.
In some scenarios, the PCF may also re-prioritize the ECSs according to local configuration or policy information or subscribed service layer agreements (service layer agreement, SLA), i.e. the PCF may adjust the priority of the ECS in step 401.
In the present application, one ECS may correspond to one urs, and a plurality of ECSs may correspond to a plurality of urs, or a plurality of ECSs may correspond to one urs, which is not limited.
In step 404, the pcf sends the urs to ue#1. Correspondingly, ue#1 may receive and save the urs.
In step 405, the ue#1 determines a first ECS according to the first type of information in the urs.
In one possible implementation, if the priorities corresponding to the ECSs are different, UE #1 may select the ECS with the highest priority. For example, the ECS with the highest priority is ecs#1 (the determined ECS is denoted as ecs#1 in this embodiment for convenience of description), and at this time, ue#1 determines to acquire edge configuration information through ecs#1. The edge configuration information may include, for example, identification information of EES, etc.
In another possible implementation, if there are multiple ECSs with highest priority, ue#1 may also determine the ECS according to the service range of the ECS and the ue#1 location, that is, select the ECS with the service range including the ue#1 location for communication. For example, ECSs with highest priority are ecs#1, ecs#2, and ecs#5, and at this time, ue#1 may determine to acquire edge configuration information through ecs#1 by the service ranges of the respective ECSs and its own location information. The edge configuration information may include, for example, identification information of EES, etc.
Specifically, reference may be made to step 302 in method 300, which is not described herein.
Case one: if the ue#1 has established a session of DNN and S-nsai corresponding to the ecs#1, the UE may directly transmit a first request through the session, the first request being for requesting configuration information from the first ECS, and the subsequent steps need not be performed.
By way of example and not limitation, the first request may be, for example: service configuration request (service provisioning request), service subscription request (service provisioning subscription request), service subscription update request (service provisioning subscription update request), service unsubscribe request (service provisioning unsubscribe request). Service provisioning requestinformation element (service provisioning requestIE) appears in the following description, but may also be the individual requests here.
And a second case: if the UE has not established a session between DNN and S-nsai corresponding to ecs#1, steps 406 to 410 also need to be performed at this time.
Mode one:
in step 406, the UE#1 creates a session of DNN and S-NSSAI corresponding to ECS#1.
In one possible implementation, the ue#1 may request to establish a protocol data unit PDU session corresponding to the ecs#1 according to the second type of information in the policy information. For example, ue#1 may send a session establishment request to the AFM, where the session establishment request includes DNN and/or S-nsai corresponding to ecs#1.
Optionally, the session establishment request may further include indication information #1, where the indication information #1 is used to indicate the UE #1 capability. In this application, the capability of ue#1 may refer to the capability that ue#1 (or EEC as well) supports reception of ECS configuration information.
Optionally, the session establishment request may further include indication information #2, where the indication information #2 is used to instruct the UE #1 to request the configuration information (e.g., service provisioning request IE) from the first ECS (e.g., ECS # 1). The requested configuration information may include, for example, identification information of EES, etc.
Optionally, the session establishment request further includes ecs#1 identification information.
In step 407, the amf determines the SMF according to the DNN and/or the indication information.
The present application contemplates that not all SMFs have the ability to (and may also be understood as "support") send service provisioning request IE to the ECS, and thus, a need exists to determine an appropriate SMF.
As an example, if the UE accesses ecs#1 through a default (default) DNN or a common (common) DNN, for example, an internet access point name (internet access point name, APN). At this time, the AMF may select (or may be understood as determining) a specific SMF according to the indication information (e.g., indication information #1 and/or indication information # 2) in step 406, that is, select one SMF having the capability of transmitting service provisioning request IE to the ECS. As another example, if ecs#1 belongs to a particular DNN, the AMF may select an SMF based on the DNN, i.e., the particular SMF can only serve the DNN.
The amf sends a create session context request to the SMF, step 408. Correspondingly, the SMF may receive a create session context request from the AMF.
Optionally, the create session context request may also include the first request (e.g., service provisioning request IE) and the identification information of ecs#1.
Optionally, in some embodiments, the method may further include step 409, where the SMF receives a request for creating a session context from the AMF, and if the request does not carry the identification information of ecs#1, at this time, the SMF may obtain the identification information of ecs#1 from the UDM or the PCF; alternatively, the SMF may determine ecs#1 identification information according to a local configuration and/or subscription information, etc. This is because each ECS has sent respective configuration information to the UDM in step 401, and thus the SMF can determine which ECS is based on the DNN and S-NSSAI information corresponding to the create session context request.
At step 410, the smf sends a first request (e.g., service provisioning request IE) to ECS #1. Correspondingly, ecs#1 receives the first request.
In this application, in steps 406 to 410, it is described that ue#1 transmits service provisioning request in the session establishment procedure. Other steps of the session establishment procedure also include establishing a session of the user plane path between the UE and the UPF, which is not described in detail in the prior art.
Mode two:
in another implementation, ue#1 may also access ecs#1 through the session modification request after completion of session establishment. As one example, ue#1 may send a session modification request to the AMF, the session modification request including a first request (e.g., service provisioning request). Alternatively, the session modification request may contain identification information of ecs#1. The AMF may then send the session modification request to the SMF, which upon receipt of service provisioning request may proceed to step 409 and step 410, sending service provisioning request to ECS #1.
In step 411, the ecs#1 determines to send a first response to the ue#1, where the first response includes configuration information that the ecs#1 needs to send to the ue#1.
In one possible implementation, the first response may be identification information of the EES, e.g., identification information of ees#1.
In step 412, the ecs#1 transmits a first response to the ue#1, the first response including identification information of the EES.
In one possible implementation, ecs#1 may send service provisioning response to ue#1 through SMF; alternatively, ECS #1 may send service provisioning response to the SMF via the PCF and then service provisioning response to UE #1 via the SMF.
In another possible implementation, ecs#1 may send service provisioning response to ue#1 over a user plane path between UE to UPF. Similar to step 405, the first response may be: service configuration response (service provisioning response), service subscription response (service provisioning subscription response), service subscription update response (service provisioning subscription update response), or service unsubscribe request (service provisioning unsubscribe response)
In a multi-ECS scene, according to the method, the UE determines the target ECS to be accessed according to the corresponding relation between each ECS in the received URSP and the priority and service range in the multi-ECS, and establishes PDU session of the target ECS according to DNN and N-SSAI, and accesses the edge service through the session, so that the experience of the edge service of the user is ensured. That is, by enhancing the existing urs p mechanism, the technical effect that the UE determines the target ECS to be accessed from among the multiple ECSs is achieved under the condition of small modification to the prior art, and the experience of the edge service of the user is ensured.
Fig. 5 is a schematic flow chart of a method 500 for acquiring an edge service provided in the present application, where the method 500 shown in fig. 5 may be performed by network elements such as AMF, SMF, NEF, UDM, PCF and ECS in the system shown in fig. 1. As shown in fig. 5, the method includes steps 501 to 512, and this embodiment is illustrated by taking ue#2 as an example, and each step is described in detail below.
In step 501, the ecs sends its own configuration information to the UDM.
The configuration information of the ECS includes: data network name DNN information of ECS, ECS service scope information, ECS priority information. ECS identification information (it will also be appreciated that the ECS corresponds to or is associated with identification information), ECS single network slice selection assistance information S-NSSAI, and the like.
In one possible implementation, the ECS may invoke a parameter provisioning service of the NEF, e.g., parameter provision service sends the configuration information to the NEF, which in turn sends the configuration information to the UDM or UDR.
In step 502, the ue#2 may send a session establishment request to the AFM, where the session establishment request includes DNN and indication information #2.
Wherein the indication information #2 is used to indicate that the UE #1 requests configuration information (e.g., service provisioning request IE) from the ECS. The configuration information may include, for example, identification information of EES, etc.
Optionally, the session establishment request may further include indication information #1, where the indication information #1 is used to indicate the UE #1 capability. In this application, the capability of ue#1 may refer to the capability that ue#1 supports reception of ECS.
In step 503, the amf determines the SMF according to the DNN and/or the indication information.
The present application contemplates that not all SMFs have the ability to (and may also be understood as "support") send service provisioning request IE to the ECS, and thus, a need exists to determine an appropriate SMF.
As an example, if the UE accesses ecs#1 through a default (default) DNN or a common (common) DNN, for example, an internet access point name (internet access point name, APN). At this time, the AMF may select (or may be understood as determining) a specific SMF according to the indication information (e.g., indication information #1 and/or indication information # 2) in the required step 406, that is, select an SMF capable of transmitting service provisioning request IE to the ECS. As another example, if ecs#1 belongs to a particular DNN, the AMF may select the SMF based only on the DNN, i.e., the particular SMF can service the DNN.
At step 504, the AMF sends a create session context request to the SMF. Correspondingly, the SMF may receive a create session context request from the AMF.
In step 505, the smf determines the identification information of the ECS.
In this embodiment, the description will be given taking as an example that the SMF determines that the identification information of the ECS is ecs#2 (an example of the second edge configuration service).
In the application, the SMF may determine that the UE needs to access the edge configuration server according to the indication information #2, and then the SMFSMF may determine the ecs#2 identification information according to the local configuration and/or acquiring subscription information from the UDM, etc. This is because each ECS has sent respective configuration information to the UDM in step 501, and the subscription information of the UE in the UDM or the configuration information of each ECS has been stored in the local configuration. The configuration information includes, for example, priority information of the ECS, service scope information, DNN information, S-nsai information, and the like. Thus, the SMF can determine which ECS is based on the DNN and S-NSSAI information corresponding to the create session context request.
The smf sends the determined configuration information of ECS #2 to the PCF, step 506.
As one example, the SMF may send the determined ecs#2 identification information and DNN to the PCF.
In step 507, the pcf generates a urs related to ecs#2 from the configuration information of ecs#2, where the urs includes identification information and data network name corresponding to ecs#2.
In one possible implementation, once the SMF sends the determined identification information and data network name of ecs#2 to the PCF, the PCF may be triggered to generate a urs for ecs#2. For example, once the SMF sends the determined DNN and identification information for ecs#2 to the PCF, the PCF may be triggered to generate a urs for ecs#2, where the urs include the corresponding DNN and identification information for ecs#2.
The urs in this implementation may instruct ue#2 to access the determined ecs#2 through the session to which the DNN corresponds (i.e., the session the UE currently requests to establish).
Specifically, in one possible implementation, the DNN information and S-nsai information for ecs#2 may be contained in a routing component (route selection components) field of a routing descriptor in the urs p. The service scope information of ECS #2 may be contained in the location criteria (location criteria) field of the routing descriptor in the urs p. The ECS #2 identification information may be included in an IP descriptor (IP descriptor) or a domain descriptor (domain descriptor) of the traffic descriptor in the urs p. The priority information of ecs#2 may be contained in a priority value (priority value) field in the urs p.
In some embodiments, step 508 may be further included, where the smf stores the determined identification information of ecs#2.
In step 509, the pcf sends the urs for ECS #2 to UE #2. Correspondingly, ue#2 may receive the urs.
Note that, step 509 in the present application may be performed in the session establishment procedure of ue#2, or may be performed after the session establishment of ue#2 is completed, which is not limited to the time of performing step 509 in the present application.
In step 510, the ue#2 determines to send a first request to the ecs#2 through the currently established session according to the urs.
Wherein the first request is for ue#2 to request configuration information from ecs#2, e.g. ue#2 to request identification information of EES from ecs#2.
By way of example and not limitation, the first request in this application may be, for example: service configuration request (service provisioning request), service subscription request (service provisioning subscription request), service subscription update request (service provisioning subscription update request), service unsubscribe request (service provisioning unsubscribe request). Service provisioning request IE (information element) appears in the following description, but may also be the individual requests here.
In another possible implementation, ue#2 may also access ecs#2 through session modification after session establishment is completed. As one example, ue#2 may send a session modification request to the AMF, the session modification request including the first request, (e.g., service provisioning request). Optionally, the session modification request may further include identification information of ecs#2. It should be appreciated that if the smf holds the determined ecs#2 identification information in step 508, the ue#2 may not need to carry the ecs#2 identification information at this time. The AMF then sends the session modification request to the SMF, which may send the first request (e.g., service provisioning request) directly to the address corresponding to the saved ECS #2. That is, at this time, the SMF may directly send the first request to ecs#2.
In step 511, the ecs#2 determines to send a first response to the ue#2, where the first response includes configuration information sent by the ecs#2 to the UE.
In one possible implementation, the first response may be identification information of the EES.
In step 512, the ecs#2 transmits a first response to the ue#2, the first response including identification information of the EES.
In one possible implementation, ecs#2 may send service provisioning response to ue#2 through SMF; alternatively, ECS #2 may send service provisioning response to the SMF via PCF and then service provisioning response to UE #1 via SMF.
In another possible implementation, ecs#2 may send service provisioning response to ue#1 over a user plane path between UE to UPF. Similar to step 510, the first response may be: service configuration response (service provisioning response), service subscription response (service provisioning subscription response), service subscription update response (service provisioning subscription update response), or service unsubscribe request (service provisioning unsubscribe response)
In the multi-ECS scenario, according to the method of the embodiment, the network device can determine the target ECS that the UE needs to access in the multi-ECS through the corresponding relation between each ECS and the respective service range, priority and identification information. And the network device can send the determined policy information of the ECS to the UE, and instruct the UE to access the ECS through the PDU session which is currently established, thereby guaranteeing the experience of the edge service of the user. That is, by enhancing the existing urs p mechanism, the technical effect that the network device determines the target ECS to be accessed in the multiple ECSs is achieved under the condition of small modification to the prior art, and the experience of the edge service of the user is ensured.
It should be noted that, in the embodiments of the present application, the words "first", "second", and the like are used to distinguish identical items or similar items having substantially identical functions and actions for the sake of clarity in describing the embodiments of the present application. For example, the first information and the second information are merely for distinguishing different information, and the order thereof is not limited. It will be appreciated by those of skill in the art that the words "first," "second," and the like do not limit the amount and order of execution, and that the words "first," "second," and the like do not necessarily differ.
In the embodiments of the present application, "one or more of the following" or the like means any combination of these items, including any combination of single items or plural items. For example, one or more of a, b, or c may represent: a, b, c; a and b; a and c; b and c; or a and b and c. Wherein a, b and c can be single or multiple.
It is to be understood that in this application, the terms "if …" and "if" are used to indicate that the device is performing the corresponding process under some objective condition, and are not intended to limit the time, nor are the device required to perform the action of determining, nor are other limitations intended to be implied.
The method for acquiring the edge service provided in the embodiment of the present application is described in detail above with reference to fig. 3 to 5. The following describes a device according to an embodiment of the present application with reference to fig. 6 and 7. It should be understood that the descriptions of the apparatus embodiments and the descriptions of the method embodiments correspond to each other, and thus, descriptions of details not described may be referred to the above method embodiments, which are not repeated herein for brevity.
The above description has been presented mainly from the point of interaction between the nodes. It will be appreciated that each node, such as a terminal device or a network device, for implementing the above-mentioned functions, includes corresponding hardware structures and/or software modules for performing each function. Those of skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as hardware or combinations of hardware and computer software. Whether a function is implemented as hardware or computer software driven hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
The embodiment of the present application may divide a terminal device or a functional module of the terminal device according to the above method example, for example, each functional module may be divided corresponding to each function, or two or more functions may be integrated into one processing module. The integrated modules may be implemented in hardware or in software functional modules. It should be noted that, in the embodiment of the present application, the division of the modules is schematic, which is merely a logic function division, and other division manners may be implemented in actual implementation. The following description will take an example of dividing each functional module into corresponding functions.
Fig. 6 is a schematic block diagram of an apparatus 100 provided in an embodiment of the present application. As shown, the apparatus 100 may include: a transceiver unit 110 and a processing unit 120.
In one possible design, the apparatus 100 may be a terminal device in the above method embodiment, for example, a user equipment UE, or may be a chip for implementing the functions of the terminal device in the above method embodiment. It should be understood that the apparatus 100 may correspond to a UE in the methods 300, 400, 500 according to the embodiments of the present application, and the apparatus 100 may perform the steps corresponding to the UE in the methods 300, 400, 500 according to the embodiments of the present application. It should be understood that the specific process of each unit performing the corresponding steps has been described in detail in the above method embodiments, and is not described herein for brevity.
Specifically, the transceiver unit is configured to receive policy information corresponding to at least two edge configuration servers, where the policy information includes first type information of each edge configuration server, and the first type information includes one or more of the following information: information of a service range, information of priority and identification information corresponding to each edge configuration server; the processing unit is used for determining a first edge configuration server from the at least two edge configuration servers according to first type information in the strategy information.
In some embodiments, the policy information further includes second class information of each edge configuration server, where the second class information includes information of a data network name corresponding to each edge configuration server and/or single network slice selection auxiliary information, and the processing unit is further configured to request to establish a protocol data unit PDU session corresponding to the first edge configuration server according to the second class information in the policy information; the apparatus accesses the first edge configuration server over the PDU session.
In some embodiments, the transceiver unit is configured to send a session establishment request, where the session establishment request includes a data network name and second indication information, where the second indication information is used to instruct the device to request configuration information from an edge configuration server; the receiving and transmitting unit is used for receiving strategy information, the strategy information comprises identification information and data network names of a second edge configuration server, the strategy information is used for indicating the device to access the second edge configuration server through the session, and the second edge configuration server is determined by a third network element according to the second indication information; the device determines to access the second edge configuration server through the session according to the policy information.
In one possible design, the apparatus 100 may be the second network element in the above method embodiment, for example, an AMF, or may be a chip for implementing the function of the second network element in the above method embodiment. It should be understood that the apparatus 100 may correspond to the AMFs in the methods 400 and 500 according to the embodiments of the present application, and the apparatus 100 may perform the steps corresponding to the AMFs in the methods 500 and 700 according to the embodiments of the present application. It should be understood that the specific process of each unit performing the corresponding steps has been described in detail in the above method embodiments, and is not described herein for brevity.
Specifically, the transceiver unit is configured to receive a session establishment request, where the session establishment request includes: the method comprises the steps that information of a data network name of a first edge configuration server and/or indication information are/is provided, the indication information comprises first indication information and/or second indication information, the first indication information is used for indicating the capability of user equipment, the second indication information is used for indicating the user equipment to request configuration information from the first edge configuration server, the first edge configuration server is determined in at least two edge configuration servers according to strategy information by the user equipment, the strategy information comprises second type information of each edge configuration server, and the second type information comprises information of the data network name corresponding to each edge configuration server and/or single network slice selection auxiliary information; the receiving and transmitting unit is configured to determine a third network element according to the second type information and/or the indication information, where the third network element supports the device to access the first edge configuration server.
In some embodiments, the transceiver unit is further configured to receive a session modification request, where the session modification request includes a first request for the user equipment to request configuration information from the first edge configuration server; the receiving and transmitting unit is used for sending the session modification request.
In some embodiments, the transceiver unit is further configured to receive policy information corresponding to at least two edge configuration servers; the receiving and transmitting unit is used for transmitting the strategy information.
Fig. 7 is a schematic block diagram of an apparatus 200 provided in an embodiment of the present application. As shown, the apparatus 200 includes: at least one processor 220. The processor 220 is coupled to the memory for executing instructions stored in the memory to transmit signals and/or receive signals. Optionally, the apparatus 200 further comprises a memory 230 for storing instructions. Optionally, the apparatus 200 further comprises a transceiver 210, and the processor 220 controls the transceiver 210 to transmit signals and/or to receive signals.
It should be appreciated that the processor 220 and the memory 230 may be combined into one processing device, and that the processor 220 is configured to execute program codes stored in the memory 230 to implement the functions described above. In particular implementations, the memory 230 may also be integrated into the processor 220 or may be separate from the processor 220.
It should also be appreciated that transceiver 210 may include a transceiver (or receiver) and a transmitter (or transmitter). The transceiver may further include antennas, the number of which may be one or more. Transceiver 210 may be a communication interface or interface circuit.
Specifically, the transceiver 210 in the apparatus 200 may correspond to the transceiver unit 110 in the apparatus 100, and the processor 220 in the apparatus 200 may correspond to the processing unit 120 in the apparatus 200.
It should be understood that the specific process of each transceiver processor executing the corresponding steps has been described in detail in the above method embodiments, and will not be described herein for brevity.
In implementation, the steps of the above method may be performed by integrated logic circuits of hardware in a processor or by instructions in the form of software. The steps of a method disclosed in connection with the embodiments of the present application may be embodied directly in a hardware processor for execution, or in a combination of hardware and software modules in the processor for execution. The software modules may be located in a random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers, etc. as well known in the art. The storage medium is located in a memory, and the processor reads the information in the memory and, in combination with its hardware, performs the steps of the above method. To avoid repetition, a detailed description is not provided herein.
It should be noted that the processor in the embodiments of the present application may be an integrated circuit chip with signal processing capability. In implementation, the steps of the above method embodiments may be implemented by integrated logic circuits of hardware in a processor or instructions in software form. The processor may be a general purpose processor, a digital signal processor (digital signal processor, DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (field-programmable gate array) or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component. The disclosed methods, steps, and logic blocks in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of a method disclosed in connection with the embodiments of the present application may be embodied directly in hardware, in a decoded processor, or in a combination of hardware and software modules in a decoded processor. The software modules may be located in a random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers, etc. as well known in the art. The storage medium is located in a memory, and the processor reads the information in the memory and, in combination with its hardware, performs the steps of the above method.
It will be appreciated that the memory in embodiments of the present application may be either volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an electrically Erasable EPROM (EEPROM), or a flash memory. The volatile memory may be random access memory (random access memory, RAM) which acts as an external cache. By way of example, and not limitation, many forms of RAM are available, such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous Link DRAM (SLDRAM), and direct memory bus RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.
According to the method provided in the embodiments of the present application, the present application further provides a computer program product having a computer program code stored thereon, which when run on a computer causes the computer to perform the method of any of the method 300, method 400, method 500 embodiments.
According to the method provided in the embodiments of the present application, the present application further provides a computer readable medium storing a program code, which when executed on a computer, causes the computer to perform the method of any one of the embodiments of the method 300, the method 400, and the method 500.
According to the method provided by the embodiment of the application, the application further provides a system which comprises the device or equipment.
In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present application are produced in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by a wired (e.g., coaxial cable, fiber optic, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains an integration of one or more available media. The usable medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a high-density digital video disc (digital video disc, DVD)), or a semiconductor medium (e.g., a Solid State Disk (SSD)), or the like.
The network side device in the above-mentioned respective apparatus embodiments corresponds to the terminal device and the network side device or the terminal device in the method embodiments, and the respective steps are performed by respective modules or units, for example, the communication unit (transceiver) performs the steps of receiving or transmitting in the method embodiments, and other steps except for transmitting and receiving may be performed by the processing unit (processor). Reference may be made to corresponding method embodiments for the function of a specific unit. Wherein the processor may be one or more.
As used in this specification, the terms "component," "module," "system," and the like are intended to refer to a computer-related entity, either hardware, firmware, a combination of hardware and software, or software in execution. For example, a component may be, but is not limited to being, a process running on a processor, an object, an executable, a thread of execution, a program, and/or a computer. By way of illustration, both an application running on a computing device and the computing device can be a component. One or more components may reside within a process and/or thread of execution and a component may be localized on one computer and/or distributed between 2 or more computers. Furthermore, these components can execute from various computer readable media having various data structures stored thereon. The components may communicate by way of local and/or remote processes such as in accordance with a signal having one or more data packets (e.g., data from two components interacting with one another in a local system, distributed system, and/or across a network such as the internet with other systems by way of the signal).
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
It will be clearly understood by those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, which are not repeated herein.
In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.
The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in each embodiment of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a read-only memory (ROM), a random access memory (random access memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
The foregoing is merely specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily think about changes or substitutions within the technical scope of the present application, and the changes and substitutions are intended to be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims (12)

1. A method for acquiring edge service is characterized in that,
the User Equipment (UE) receives strategy information corresponding to at least two edge configuration servers from a first network element, wherein the strategy information comprises first type information of each edge configuration server, and the first type information comprises one or more of the following information: the first network element is a strategy control network element;
the UE determines a first edge configuration server from the at least two edge configuration servers according to first type information in the strategy information;
the policy information further includes second class information of each edge configuration server, where the second class information includes information of a data network name and/or single network slice selection auxiliary information corresponding to each edge configuration server, and the method further includes:
The UE requests to establish a protocol data unit PDU session corresponding to the first edge configuration server according to the second type information in the strategy information;
the UE accesses the first edge configuration server through the PDU session.
2. The method of claim 1, wherein the first type of information comprises priority information for each edge configuration server, and wherein the UE determines a first edge configuration server from the at least two edge configuration servers based on the first type of information in the policy information, comprising:
if the priorities of the plurality of edge configuration servers are different, the UE determines the edge configuration server with the highest priority as the first edge configuration server.
3. The method of claim 1, wherein the policy information includes priority information and service scope information of each edge configuration server, and wherein the UE determines the first edge configuration server from the at least two edge configuration servers according to a first type of information in the policy information, comprising:
if the priorities of the plurality of edge configuration servers are the same, the UE determines a first edge configuration server according to the service range of the edge configuration server and the position information of the UE.
4. A method according to any one of claims 1 to 3, wherein the UE requests to establish a protocol data unit PDU session corresponding to the first edge configuration server according to the second type of information in the policy information, comprising:
the UE sends a session establishment request to a second network element, wherein the session establishment request comprises a data network name and/or single network slice selection auxiliary information corresponding to the first edge configuration server, and the second network element is a mobile management network element.
5. The method of claim 4, wherein the session establishment request further comprises:
first indication information, wherein the first indication information is used for indicating the capability of the UE and/or;
and the second indication information is used for indicating the UE to request configuration information from the first edge configuration server.
6. An apparatus for acquiring edge services, comprising: a receiving and transmitting unit and a processing unit,
the receiving and transmitting unit is configured to receive policy information corresponding to at least two edge configuration servers from a policy control network element, where the policy information includes first type information of each edge configuration server, and the first type information includes one or more of the following information: information of a service range, information of priority and identification information corresponding to each edge configuration server;
The processing unit is used for determining a first edge configuration server from the at least two edge configuration servers according to first type information in the strategy information;
the policy information further includes a second class of information for each edge configuration server, the second class of information including information for a data network name and/or single network slice selection assistance information corresponding to each edge configuration server,
the processing unit is further configured to request to establish a protocol data unit PDU session corresponding to the first edge configuration server according to the second type information in the policy information;
the apparatus accesses the first edge configuration server over the PDU session.
7. The apparatus of claim 6, wherein the first type of information comprises priority information for each edge configuration server, wherein the processing unit determines a first edge configuration server from the at least two edge configuration servers based on the first type of information in the policy information, comprising:
if the priorities of the plurality of edge configuration servers are different, the processing unit determines the edge configuration server with the highest priority as the first edge configuration server.
8. The apparatus of claim 6, wherein the first type of information comprises priority information and service scope information for each edge configuration server, wherein the processing unit determines the first edge configuration server from the at least two edge configuration servers based on the first type of information in the policy information, comprising:
if the priorities of the plurality of edge configuration servers are the same, the processing unit determines a first edge configuration server according to the service range of the edge configuration server and the position information of the device.
9. The apparatus according to any one of claims 6 to 8, wherein the processing unit is specifically configured to:
and controlling the receiving and transmitting unit to transmit a session establishment request, wherein the session establishment request comprises a data network name and/or single network slice selection auxiliary information corresponding to the first edge configuration server.
10. The apparatus of claim 9, wherein the session establishment request further comprises:
first indication information for indicating capabilities of the device, and/or;
and second indication information, wherein the second indication information is used for indicating the device to request configuration information from the first edge configuration server.
11. An apparatus for acquiring edge services, comprising: a processor coupled to a memory for storing a program or instructions that, when executed by the processor, cause the apparatus to perform the method of any one of claims 1 to 5.
12. A computer readable medium storing a computer program which, when run on a computer, causes the computer to perform the method of any one of the possible implementations of claims 1 to 5.
CN202110769700.7A 2021-07-07 2021-07-07 Method and device for acquiring edge service Active CN113630749B (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202110769700.7A CN113630749B (en) 2021-07-07 2021-07-07 Method and device for acquiring edge service
PCT/CN2022/103724 WO2023280121A1 (en) 2021-07-07 2022-07-04 Method and apparatus for obtaining edge service

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110769700.7A CN113630749B (en) 2021-07-07 2021-07-07 Method and device for acquiring edge service

Publications (2)

Publication Number Publication Date
CN113630749A CN113630749A (en) 2021-11-09
CN113630749B true CN113630749B (en) 2023-05-16

Family

ID=78379231

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110769700.7A Active CN113630749B (en) 2021-07-07 2021-07-07 Method and device for acquiring edge service

Country Status (2)

Country Link
CN (1) CN113630749B (en)
WO (1) WO2023280121A1 (en)

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115185669A (en) * 2021-04-06 2022-10-14 中国移动通信有限公司研究院 Edge configuration server information processing method and device and communication equipment
CN113630749B (en) * 2021-07-07 2023-05-16 华为技术有限公司 Method and device for acquiring edge service
CN114363173A (en) * 2021-12-01 2022-04-15 华为技术有限公司 Communication method, device and readable storage medium
CN114302428B (en) * 2021-12-24 2023-06-23 中国联合网络通信集团有限公司 MEC node determination method and device
CN116471219A (en) * 2022-01-11 2023-07-21 腾讯科技（深圳）有限公司 Data transmission method and related equipment
CN116867032A (en) * 2022-03-28 2023-10-10 华为技术有限公司 Communication method and device
CN116939009A (en) * 2022-03-29 2023-10-24 华为技术有限公司 Communication method, device and equipment
CN114884819B (en) * 2022-05-31 2023-08-22 中国联合网络通信集团有限公司 Capability opening system, method, device and storage medium

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019200346A1 (en) * 2018-04-13 2019-10-17 General Electric Company Systems and methods for synchronization of imaging systems and an edge computing system
CN112583880B (en) * 2019-09-30 2022-02-25 大唐移动通信设备有限公司 Server discovery method and related equipment
WO2021064717A1 (en) * 2019-10-04 2021-04-08 Telefonaktiebolaget Lm Ericsson (Publ) Method for identification of traffic suitable for edge breakout and for traffic steering in a mobile network
CN111586114A (en) * 2020-04-24 2020-08-25 腾讯科技（深圳）有限公司 Business cooperative processing method and related equipment
CN113630749B (en) * 2021-07-07 2023-05-16 华为技术有限公司 Method and device for acquiring edge service

Also Published As

Publication number Publication date
CN113630749A (en) 2021-11-09
WO2023280121A1 (en) 2023-01-12

Similar Documents

Publication Publication Date Title
CN113630749B (en) Method and device for acquiring edge service
CN113691969B (en) Communication method and device
CN113133085B (en) Method and communication device for establishing connection and acquiring relay service code
US11057865B1 (en) Apparatus and methods for enhanced paging in wireless networks
CN111010744A (en) Method and device for establishing session and method and device for sending message
AU2021221761B2 (en) Selection of ip version
CN111615844B (en) Method and apparatus for selecting a session management entity serving a wireless communication device
CN115766657A (en) Method and device for acquiring edge service
KR102509333B1 (en) Method and Apparatus for Session Management
CN115299127A (en) Apparatus and method for providing low-latency location information service in wireless communication system
WO2019196680A1 (en) Communication method and communication apparatus
US20230156513A1 (en) Proximity service communication method, management network element, terminal device, and communication system
CN110557846B (en) Data transmission method, terminal equipment and network equipment
EP4021030A1 (en) Method and device for providing direct communication in wireless communication system
US20230132454A1 (en) Method and apparatus for supporting edge computing service for roaming ue in wireless communication system
CN116868603A (en) New method for external parameter provisioning for AF sessions
CN115884153A (en) Communication method and device
CN115484582A (en) Communication method and communication device
JP7473001B2 (en) Core network node, terminal, and method thereof
WO2022170798A1 (en) Strategy determining method and communication apparatus
EP4344307A1 (en) Method and apparatus for relocating context
WO2022100197A1 (en) Method and apparatus for obtaining edge service
CN116546479A (en) Communication method and device
CN115707062A (en) Network slice admission control method and device
CN117641472A (en) Communication method and device

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant