WO2023185657A1 - Procédé de communication et appareil de communication - Google Patents

Procédé de communication et appareil de communication Download PDF

Info

Publication number
WO2023185657A1
WO2023185657A1 PCT/CN2023/083566 CN2023083566W WO2023185657A1 WO 2023185657 A1 WO2023185657 A1 WO 2023185657A1 CN 2023083566 W CN2023083566 W CN 2023083566W WO 2023185657 A1 WO2023185657 A1 WO 2023185657A1
Authority
WO
WIPO (PCT)
Prior art keywords
network element
target
information
source
core network
Prior art date
Application number
PCT/CN2023/083566
Other languages
English (en)
Chinese (zh)
Inventor
陈泽昊
李永翠
倪慧
Original Assignee
华为技术有限公司
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 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2023185657A1 publication Critical patent/WO2023185657A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0033—Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/08—Access security
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/08—Load balancing or load distribution
    • H04W28/084—Load balancing or load distribution among network function virtualisation [NFV] entities; among edge computing entities, e.g. multi-access edge computing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/08—Load balancing or load distribution
    • H04W28/09—Management thereof
    • H04W28/0925—Management thereof using policies
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/08—Load balancing or load distribution
    • H04W28/09—Management thereof
    • H04W28/0958—Management thereof based on metrics or performance parameters
    • H04W28/0967—Quality of Service [QoS] parameters
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/24—Reselection being triggered by specific parameters
    • H04W36/32—Reselection being triggered by specific parameters by location or mobility data, e.g. speed data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/24—Connectivity information management, e.g. connectivity discovery or connectivity update

Definitions

  • the embodiments of the present application relate to the field of communication, and more specifically, to a communication method and a communication device.
  • EHE edge computing
  • UE user equipment
  • AS application service
  • AF application function
  • This application provides a communication method and communication device to enable the network side to determine the information of the target AF network element based on the data network access identifier (DNAI) and deliver it to the source AF network element, which is beneficial to The source AF network element discovers the target AF network element and migrates the application context to the target AF network element.
  • DNAI data network access identifier
  • a communication method is provided.
  • the method may be executed by the first core network element (for example, network exposure function (NEF)/session management function (SMF)), or may also be performed by the first core network element.
  • the first core network element for example, network exposure function (NEF)/session management function (SMF)
  • PEF session management function
  • chip or circuit execution this application does not limit this.
  • the following description takes the execution by the first core network element as an example.
  • the method includes: the first core network element obtains the data network access identifier DNAI corresponding to the current location of the terminal device, the first core network element determines the information of the target application function AF network element based on the DNAI, and the first core network element Send the information of the target AF network element to the source AF network element, which is the network element currently serving the terminal device.
  • AF network element serves terminal equipment
  • AS corresponding to the AF network element serves terminal equipment.
  • corresponding can also be described as control/management, etc.
  • the source AF is currently "Network element served by the terminal device” can be understood as the AS corresponding to the source AF network element (including edge application server (EAS)) serving the terminal device.
  • EAS edge application server
  • the current location of the terminal device may be the location after movement, and the DNAI corresponding to the current location of the terminal device may be one or more, which is not specifically limited in this application. Among them, corresponds to the current location of the terminal device
  • the DNAI can be understood as the DNAI that is closer to the current location of the terminal device, or the DNAI that is closer to the user plane function (UPF) that serves the current location of the terminal device, or the DNAI that serves the current location of the terminal device. UPF can access or is suitable for accessing DNAI, etc.
  • UPF user plane function
  • application context includes AF context and AS context.
  • Application context migration refers to migrating application context from source AF and/or AS to target AF and/or AS.
  • the AF context refers to data related to the control plane, such as the AF subscription to the fifth generation core network (5th generation core network, 5GC) with a certain/certain UE, and/or with a certain/certain application. , and/or information associated with a certain/some DNN, and/or a certain/some single network slice selection assistance information (single network slice selection assistance information, S-NSSAI), for example, AF subscribes to 5GC for a certain User plane change information or location change information associated with each UE.
  • AS context refers to data related to the user plane, such as certain/certain UEs, and/or data information related to certain/certain applications, such as the points/ranks/game status of a certain UE using a certain account to play a certain game. wait.
  • application context migration can also be described as AF/AS context migration, or context migration, or AF/AS migration, etc., where “migration” can also be described as “relocation” ( relocation).
  • the first core network element can determine the information of the target AF network element based on DNAI and send it to the source AF network element, so that the source AF network element can discover the target AF network element, which is conducive to the smooth progress of the migration application context. .
  • the source AF network element needs to migrate the application context to the target AF network element.
  • the source AF network element can obtain the information of the target AF network element through the network side. , to determine the target AF network element in different scenarios, and then migrate the application context to the target AF network element.
  • the target AF network element is a network element that serves the terminal device after application context migration.
  • the target AF network element is the network element that serves the terminal device after the application context is migrated
  • the AS including EAS
  • correspondence can also be described as control/management, etc.
  • the information of the target AF network element includes identification information or address information of the target AF network element.
  • the target AF network element information may be an ID, an address, a service ID, a domain name, etc.
  • the address may be an Internet protocol (Internet protocol, IP) address, a media access control (media access control, MAC) address, etc. This application does not specifically limit this.
  • the method before the first core network element determines the information of the target AF network element based on DNAI, the method further includes: the first core network element receives the information from the source AF network element.
  • the first request message is used to request to obtain information about the target AF network element, and the first request message includes DNAI.
  • the first core network element can determine the information of the target AF network element based on the first request information sent by the source AF network element and based on the DNAI corresponding to the terminal device, and then discover the target AF network element and realize the source AF network Even if the target AF network element cannot be determined locally, the application context can still be successfully migrated to the target AF network element.
  • the first request message further includes first indication information
  • the first instruction information is used to instruct to obtain the information of the target AF network element.
  • the first core network element can determine the information of the target AF network element based on the first request message, or the DNAI corresponding to the terminal device, or the first instruction information, which can help the source AF network element fail to respond based on the DNAI.
  • the application context can still be migrated to the target AF network element.
  • the first core network element determines the information of the target AF network element based on the DNAI, including: the first core network element determines the target AF based on the DNAI and the first indication information. Network element information.
  • the first core network element can locally obtain the information of the target AF network element based on DNAI and the first indication information. Especially for the scenario where the first core network element locally stores the target AF network element information, to a certain extent It can reduce signaling overhead and improve the efficiency of obtaining target AF network element information.
  • the first core network element determines the information of the target AF network element based on DNAI, including: the first core network element sends the second core network element to the second core network element. request message, the second request message is used to request to obtain the information of the target AF network element, the second request message includes DNAI, the first core network network element receives a response message from the second core network network element, the response message includes the target AF information.
  • the second core network element may be a unified data storage UDR network element, a unified data management (unified data management, UDM) network element or a network storage function (NF repository function, NRF) network element.
  • UDM unified data management
  • NRF network storage function
  • the first core network element can obtain the target AF information by requesting the second core network element, especially for the scenario where the first core network element does not store the target AF network element information locally.
  • the first core network element receives second indication information from the source AF network element, and the second indication information is used to indicate that the first core network element is allowed to send data to the source AF network element.
  • the AF network element sends information about the target AF network element.
  • the second indication information is also used to indicate that the first core network element is allowed to use the AF network element as the target AF network element and send it to other AF network elements.
  • each AF network element can send the second indication information to the first core network element. That is to say, each of these AF network elements can serve as either a target AF network element or a source AF network element. That is, it can not only receive application contexts from other AF network elements, but also migrate application contexts to other AF network elements.
  • the first core network element can send the target AF network element information to the source AF network element, thereby determining the target AF network element and successfully migrating the application context to the target AF network element.
  • the first core network element is a network opening function NEF network element or a session management function SMF network element.
  • the first core network element when the first core network element is an SMF network element, the first core network element receives the second indication information from the source AF network element, including the SMF network element. The element receives the second indication information from the source AF network element through the second core network element.
  • the source AF network element can also forward the second indication information to the first core network element through the second core network element, which provides other possible implementation methods.
  • the second aspect provides a communication method.
  • This method may be executed by the source AF network element, or may be executed by a chip or circuit used for the source AF network element, which is not limited in this application.
  • the following description takes the execution by the source AF network element as an example.
  • the method includes: a source application function AF network element receiving information from a target AF network element of a first core network element, The source AF network element migrates the application context to the target AF network element according to the information of the target AF network element.
  • the source AF network element is the network element currently serving the terminal device.
  • the first core network element can determine the information of the target AF network element based on DNAI and send it to the source AF network element, so that the source AF network element can discover the target AF network element, which is conducive to the smooth progress of the migration application context. .
  • the source AF network element needs to migrate the application context to the target AF network element.
  • the source AF network element can obtain the information of the target AF network element through the network side. , to determine the target AF network element in different scenarios, and then migrate the application context to the target AF network element.
  • the target AF network element is a network element that serves the terminal device after application context migration.
  • the information of the target AF network element includes identification information or address information of the target AF network element.
  • the source AF network element sends a first request message to the first core network element, and the first request message is used to request to obtain information of the target AF network element.
  • the request message includes the target data network access identifier DNAI.
  • the source AF network element can request to obtain the information of the target AF network element from the network side through the first request information, and then determine the target AF network element, which is beneficial to the smooth operation when the target AF network element cannot be determined locally. Migrate the application context to the target AF network element.
  • the first request message further includes first indication information, and the first indication information is used to instruct to obtain the information of the target AF network element.
  • the source AF network element can also request to obtain the information of the target AF network element from the network side through the first indication information, thereby determining the target AF network element and migrating the application context to the target AF network element.
  • the source AF network element sends a first request message to the first core network element, including: when the source AF network element cannot determine the information of the target AF network element based on DNAI When , the source AF network element sends a first request message to the first core network element.
  • the source AF network element when it cannot determine the target AF network element locally, it sends a first request message to the first core network element to obtain the information of the target AF network element, thereby completing the migration of the application context.
  • the source AF network element sends second indication information to the first core network element, and the second indication information is used to indicate that the first core network element is allowed to send data to the source AF.
  • the network element sends information about the target AF network element.
  • the first core network element can send the target AF network element information to the source AF network element, thereby determining the target AF network element and successfully migrating the application context to the target AF network element.
  • the second indication information is also used to indicate that the first core network element is allowed to use the AF network element as the target AF network element and send it to other AF network elements.
  • the first core network element is a network opening function NEF network element or a session management function SMF network element.
  • the source AF network element when the first core network element is an SMF network element, sends the second indication information to the first core network element, including: the source AF network element element through the second core network element to The SMF network element sends the second indication information.
  • the first core network element can send the target AF network element information to the source AF network element, thereby determining the target AF network element and successfully migrating the application context to the target AF network element.
  • the second core network element may be a unified data storage UDR network element, a unified data management UDM network element or a network storage function NRF network element.
  • a communication device in a third aspect, includes: a processing unit, used to obtain the data network access identifier DNAI corresponding to the current location of the terminal device, and also used to determine the information of the target application function AF network element based on the DNAI.
  • the transceiver unit is used to send the information of the target AF network element to the source AF network element.
  • the source AF network element is the network element currently serving the terminal equipment.
  • the target AF network element is a network element that serves the terminal device after application context migration.
  • the information of the target AF network element includes identification information or address information of the target AF network element.
  • the transceiver unit is also used to receive a first request message from the source AF network element.
  • the first request message is used to request to obtain information of the target AF network element.
  • a request message includes DNAI.
  • the first request message further includes first indication information, and the first indication information is used to instruct acquisition of the information of the target AF network element.
  • the processing unit is further configured to determine the information of the target AF network element based on the DNAI and the first indication information.
  • the transceiver unit is also used to send a second request message to the second core network element, and the second request message is used to request to obtain information of the target AF network element,
  • the second request message includes the DNAI and is also used to receive a response message from the second core network element, where the response message includes the information of the target AF.
  • the transceiver unit is further configured to receive second indication information from the source AF network element, and the second indication information is used to indicate that the first core network element is allowed to send data to the source AF network element.
  • the AF network element sends information about the target AF network element.
  • the first core network element is a network opening function NEF network element or a session management function SMF network element.
  • the second core network element includes: a unified data storage UDR network element, a unified data management UDM network element or a network storage function NRF network element.
  • a communication device in a fourth aspect, includes: a transceiver unit, used for the source application function AF network element to receive the information of the target AF network element from the first core network element, and also used for the source AF network element to send information to the target AF network element according to the information of the target AF network element.
  • the source AF network element is the network element currently serving the terminal device.
  • the target AF network element is a network element that serves the terminal device after application context migration.
  • the information of the target AF network element includes identification information or address information of the target AF network element.
  • the transceiver unit is also used to send a first request message to the first core network element, and the first request message is used to request to obtain information of the target AF network element,
  • the first request message includes Target data network access identifier DNAI.
  • the first request message further includes first indication information, and the first indication information is used to instruct acquisition of the information of the target AF network element.
  • the transceiver unit is also used to send a first request to the first core network element when the source AF network element cannot determine the information of the target AF network element based on DNAI. information.
  • the transceiver unit is further configured to send second indication information to the first core network element, and the second indication information is used to indicate that the first core network element is allowed to send The source AF network element sends information about the target AF network element.
  • the first core network element is a network opening function NEF network element or a session management function SMF network element.
  • a communication device including a transceiver, a processor and a memory.
  • the processor is used to control the transceiver to send and receive signals.
  • the memory is used to store a computer program.
  • the processor is used to call and run the computer from the memory.
  • the program enables the communication device to execute the method in any possible implementation manner of the first aspect or the second aspect.
  • processors there are one or more processors and one or more memories.
  • the memory may be integrated with the processor, or the memory may be provided separately from the processor.
  • the communication device further includes a transmitter (transmitter) and a receiver (receiver).
  • a communication system including a first core network element and a source AF network element.
  • the communication system also includes a second core network element.
  • a computer-readable storage medium stores a computer program or code.
  • the computer program or code When the computer program or code is run on a computer, it causes the computer to execute the above-mentioned first aspect or Methods in any possible implementation of the second aspect.
  • a chip including at least one processor, the at least one processor is coupled to a memory, the memory is used to store a computer program, the processor is used to call and run the computer program from the memory, so that the installation
  • the communication device with the chip system performs the method in any possible implementation manner of the first aspect or the second aspect.
  • the chip may include an input circuit or interface for sending information or data, and an output circuit or interface for receiving information or data.
  • a computer program product includes: computer program code.
  • the first core network element causes the first core network element to execute the above first aspect or The method in any possible implementation of the first aspect, and causing the source AF network element to perform the method in the above second aspect or any possible implementation of the second aspect.
  • Figure 1 shows a schematic diagram of a network architecture.
  • Figure 2 shows a schematic diagram of another network architecture.
  • Figure 3 is a schematic flowchart of the method for AF to affect traffic routing.
  • Figure 4 is a flow chart of the subscription event change notification method.
  • Figure 5 is a schematic flowchart of the first communication method provided by the embodiment of the present application.
  • FIG. 6 is a schematic flowchart of the second communication method provided by the embodiment of the present application.
  • FIG. 7 is a schematic flowchart of the third communication method provided by the embodiment of the present application.
  • Figure 8 is a schematic flowchart of the fourth communication method provided by the embodiment of the present application.
  • Figure 9 is a schematic flowchart of the fifth communication method provided by the embodiment of the present application.
  • Figure 10 shows a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • Figure 11 shows a schematic structural diagram of another communication device provided by an embodiment of the present application.
  • the technical solution provided by this application can be applied to various communication systems, such as: 5G or new radio (NR) system, long term evolution (LTE) system, LTE frequency division duplex (FDD) ) system, LTE time division duplex (TDD) system, etc.
  • the technical solution provided by this application can also be applied to future communication systems, such as the sixth generation mobile communication system.
  • the technical solution provided by this application can also be applied to device-to-device (D2D) communication, vehicle-to-everything (V2X) communication, machine-to-machine (M2M) communication, machine type Communication (machine type communication, MTC), and Internet of Things (Internet of things, IoT) communication systems or other communication systems.
  • D2D device-to-device
  • V2X vehicle-to-everything
  • M2M machine-to-machine
  • MTC machine type Communication
  • Internet of Things Internet of things, IoT
  • Figure 1 shows a schematic diagram of a network architecture 100.
  • the network architecture takes the 5G system (the 5th generation system, 5GS) as an example.
  • the network architecture may include but is not limited to: network slice specific authentication and authorization function (NSSAAF), network slice selection function (NSSF), authentication server function, AUSF), unified data management (UDM), network exposure function (NEF), network storage function (NF repository function, NRF), policy control function (PCF), AF, interface Access and mobility management function (AMF), session management function (SMF), service communication proxy (SCP), network slice admission control function , NSACF), UE, wireless access network equipment, user plane function (UPF), data network (data network, DN), etc.
  • NSSAAF network slice specific authentication and authorization function
  • NSSF network slice selection function
  • authentication server function authentication server function
  • AUSF unified data management
  • UDM network exposure function
  • NRF network storage function
  • PCF policy control function
  • AF interface Access and mobility management function
  • SCP service communication proxy
  • NSACF network slice admission control function
  • UE wireless access network equipment
  • UE It can be called terminal equipment, access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent or user device.
  • the terminal device may be a device that provides voice/data to users, for example, a handheld device with wireless connection function, a vehicle-mounted device, etc.
  • terminals are: mobile phones, tablets, laptops, PDAs, mobile internet devices (MID), wearable devices, virtual reality (VR) devices, augmented reality (augmented reality, AR) equipment, wireless terminals in industrial control (industrial control), wireless terminals in self-driving (self driving), remote surgery (remote medical) Wireless terminals in surgery, wireless terminals in smart grid, wireless terminals in transportation safety, wireless terminals in smart city, and wireless terminals in smart home , cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (personal digital assistants, PDAs), handheld devices with wireless communication capabilities , computing devices or other processing devices connected to wireless modems, wearable devices, terminal devices in 5G networks or terminal devices in future evolved public land mobile communication networks (public land mobile network, PLMN), etc., embodiments of the present
  • the terminal device may also be a wearable device.
  • Wearable devices can also be called wearable smart devices. It is a general term for applying wearable technology to intelligently design daily wear and develop wearable devices, such as glasses, gloves, watches, clothing and shoes, etc.
  • a wearable device is a portable device that is worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not just hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction.
  • wearable smart devices include full-featured, large-sized devices that can achieve complete or partial functions without relying on smartphones, such as smart watches or smart glasses, and those that only focus on a certain type of application function and need to cooperate with other devices such as smartphones.
  • the terminal device may also be a terminal device in the IoT system.
  • IoT is an important part of the future development of information technology. Its main technical feature is to connect objects to the network through communication technology, thereby realizing human-machine Interconnection, an intelligent network that interconnects things.
  • terminal equipment and access network equipment can communicate with each other using certain air interface technology (such as NR or LTE technology, etc.).
  • Terminal devices can also communicate with each other using some air interface technology (such as NR or LTE technology, etc.).
  • the device used to implement the functions of the terminal device may be a terminal device, or may be a device capable of supporting the terminal device to implement the function, such as a chip system or a chip, and the device may be installed in the terminal device.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • (Radio) access network (R)AN) equipment It can provide authorized users in a specific area with the function of accessing the communication network. Specifically, it can include the 3rd generation partnership program (3rd generation partnership) Wireless network devices in project, 3GPP) networks may also include access points in non-3GPP (non-3GPP) networks. The following uses AN equipment representation for convenience of description.
  • AN equipment can adopt different wireless access technologies.
  • 3GPP access technologies for example, wireless access technologies used in third generation (3G), fourth generation (4G) or 5G systems
  • non-3GPP non- 3GPP (non-3GPP) access technology.
  • 3GPP access technology refers to access technology that complies with 3GPP standard specifications.
  • the access network equipment in the 5G system is called next generation Node Base station (gNB) or RAN equipment.
  • Non-3GPP access technologies can include air interface technology represented by access point (AP) in wireless fidelity (WiFi), global interoperability for microwave access (WiMAX), code Code division multiple access (CDMA), etc.
  • AP access point
  • WiFi wireless fidelity
  • WiMAX global interoperability for microwave access
  • CDMA code Code division multiple access
  • AN equipment can allow interconnection and interworking between terminal equipment and the 3GPP core network using non-3GPP technologies.
  • AN equipment can be responsible for functions such as wireless resource management, quality of service (QoS) management, data compression and encryption on the air interface side.
  • AN equipment provides access services to terminal equipment, thereby completing control signals and user number Data is forwarded between the terminal device and the core network.
  • QoS quality of service
  • AN equipment may include, for example, but is not limited to: macro base station, micro base station (also known as small station), radio network controller (radio network controller, RNC), Node B (Node B, NB), base station controller (base station controller) , BSC), base transceiver station (BTS), home base station (for example, home evolved NodeB, or home Node B, HNB), baseband unit (baseband unit, BBU), AP in WiFi system, wireless relay Node, wireless backhaul node, transmission point (TP) or transmission and reception point (TRP), etc., can also be a gNB or transmission point (TRP or TP) in the 5G (such as NR) system , one or a group (including multiple antenna panels) antenna panels of a base station in a 5G system, or it can also be a network node that constitutes a gNB or transmission point, such as a distributed unit (DU), or next-generation communications Base stations in 6G systems, etc.
  • RNC radio network controller
  • AMF Mainly used for functions such as access control, mobility management, attachment and detachment.
  • SMF Mainly used for user plane network element selection, user plane network element redirection, Internet protocol (IP) address allocation for terminal equipment, and session management in mobile networks, such as session establishment, modification and release. and quality of service (QoS) control.
  • IP Internet protocol
  • QoS quality of service
  • UPF Mainly used for receiving and forwarding user plane data.
  • the UPF can receive user plane data from the DN and send the user plane data to the terminal device through the AN device.
  • UPF can also receive user plane data from the terminal device through the AN device and forward it to the DN.
  • the UPF directly connected to the DN through the N6 interface in the session can be called the protocol data unit (PDU) session anchor (PDU session anchor, PSA).
  • PDU protocol data unit
  • PSA protocol data unit
  • PCF A unified policy framework mainly used to guide network behavior and provide policy rule information for control plane network elements (such as AMF, SMF, etc.).
  • AF Mainly used to provide services to the 3GPP network, such as interacting with PCF for policy control, etc.
  • NSSF Network slice selection function
  • UDM Mainly used for UE subscription data management, including storage and management of UE identification, UE access authorization, etc.
  • DN Operator network mainly used to provide data services to UE.
  • UE For example, the Internet, third-party business networks, IP multimedia service (IMS) networks, etc.
  • IMS IP multimedia service
  • AUSF Mainly used for user authentication, etc.
  • NEF Mainly used to safely open services and capabilities provided by 3GPP network functions to the outside world.
  • NRF Mainly used to save network functional entities and description information of the services they provide.
  • Figure 2 shows a schematic diagram of another network architecture 200.
  • this network architecture can be understood as the system architecture or scenario for deploying edge computing services in the 5G network architecture.
  • the network architecture may include but is not limited to: NEF, PCF, AF, SMF, AMF, UE, UPF, DN, AN, EAS.
  • EAS can also be called edge applications (servers), application instances, edge application instances, multi-access edge computing (MEC) applications (servers), EAS functions, etc.
  • EAS is deployed in the local DN (local DN), and the network establishes a transmission path for the UE by selecting a UPF that is close to the local DN to ensure that the UE can normally access edge services.
  • the local DN can be represented by the data network access identifier (data network access identifier (DNAI), or the local DN can also be identified by a data network name (DNN).
  • DNAI data network access identifier
  • DNN data network name
  • SMF can control the data routing of PDU so that this PDU session can have multiple N6 interfaces at the same time.
  • the UPF connecting each N6 interface is called a PSA.
  • PSA The UPF connecting each N6 interface
  • Each PAS provides a different path to the same DN.
  • SMF can insert an uplink classifier (UL CL) in the data transmission path of the PDU session.
  • the UL CL function is provided by UPF and is used to forward data packets that meet business filtering rules to the specified path.
  • the function of UL CL can be to transmit uplink data to different PSA and merge downlink data to UE.
  • the data corresponding to each PSA can also be aggregated into a common UPF.
  • This common UPF has the function of a branching point (BP).
  • the branch point forwards uplink data to different PSA upwards and merges downlink data from PSA downwards.
  • UPF (UL CL/BP) can represent a UPF that provides UL CL functions or a public UPF, that is, the UPF can transmit uplink data to different PSA, for example, UPF (PSA2) and UPF(PSA1) and merge the downlink data to the UE.
  • each network element can communicate with each other through interfaces.
  • the UE is connected to the AN device through the radio resource control (RRC) protocol, and Uu is used between the UE and the AN device. interface for communication.
  • RRC radio resource control
  • the network architecture shown above is only an illustrative description, and the network architecture applicable to the embodiments of the present application is not limited thereto. Any network architecture that can realize the functions of each of the above network elements is applicable to the embodiments of the present application.
  • the network architecture shown above may also include other more network elements without limitation.
  • the architecture shown in Figure 2 also includes edge application server discovery function (EASDF).
  • EASDF edge application server discovery function
  • the edge application server discovery function which may also be called edge application (service) discovery function, application instance discovery function, edge application instance discovery function, MEC application (server) discovery function, etc., is not limited.
  • functions or network elements such as AMF, SMF, UPF, PCF, UDM, NSSF, AUSF, etc. shown in Figure 1 or Figure 2 can be understood as network elements used to implement different functions, for example, they can be combined as needed.
  • Network slicing These network elements can be independent devices, or they can be integrated into the same device to implement different functions, or they can be network elements in hardware devices, software functions running on dedicated hardware, or platforms (for example, cloud The virtualization function instantiated on the platform), this application does not limit the specific form of the above network elements.
  • EHE can manage deployed edge applications or services.
  • EHE can manage context.
  • UE movement causes the currently accessed EAS and EHE to not be optimized (for example, the path is long or the delay is large), or there is a better EAS and EHE ( For example, the path is shorter or the delay is smaller), or the load of the currently accessed EAS is large, and the UE needs to access other EAS and EHE for load balancing reasons, etc.
  • application context migration is required. It should be understood that application context migration is performed through interaction between AFs.
  • Figure 3 is a schematic flowchart of a method 300 for AF influencing traffic routing, which specifically includes the following steps.
  • AF request is used to subscribe to events or affect traffic routing.
  • the AF sends an AF request to the 5GC to subscribe to the UE's DNAI change event.
  • NEF receives request message #1 from AF.
  • the request message #1 is used to request to subscribe to the 5GC for the DNAI change event of the UE, and the request message #1 includes the subscription information.
  • the subscription information includes identification information of the AF, identification information of at least one UE and subscription events.
  • the identification information of the AF can be the AF ID or address
  • the subscription event information can be a DNAI change event indicating the subscription of the UE
  • the identification information of the UE can be the UE ID and group ID, or it can be DNN, S-NSSAI and DNAI. etc., that is, one or more UEs that access the DNN, use the S-NSSAI, and associate the DNAI.
  • the request message #1 may be the Nnef_TrafficInfluence_Create/Update/Delete message, that is, AF calls the Nudr_DM_Notify message to send a request to subscribe to the DNAI change event to NEF.
  • AF calls the Nnef_TrafficInfluence_Create service and sends an AF request to NEF to request subscription to the UE's DNAI change event.
  • NEF sends response message #1 (response) to AF.
  • UDR sends notification message #1 to PCF(s).
  • PCF(s) receives notification message #1 from UDR.
  • the notification message #1 includes the subscription information in step S320.
  • the notification message #1 may be a Nudr_DM_Notify message, that is, the UDR sends the above subscription information to the PCF(s) through the Nudr_DM_Notify message.
  • the UDR may continue to store subscription information or may no longer store subscription information. This application does not specifically limit this.
  • PCF(s) sends notification message #2 to SMF.
  • SMF receives notification message #2 from PCF(s).
  • the notification message #2 includes the subscription information in step S320.
  • the notification message #2 may be an Npcf_SMPolicyControl_UpdateNotify message, that is, the PCF(s) sends the above subscription information to the SMF through the Npcf_SMPolicyControl_UpdateNotify message.
  • S370, SMF and UPF/EASDF perform traffic routing reconfiguration.
  • S380 SMF sends notification message #3 to AMF.
  • AMF receives notification message #3 from SMF.
  • the notification message #3 includes context status information.
  • a trusted AF for example, an AF deployed by a 5GC operator
  • the event notification process is triggered. That is, SMF notifies AF of DNAI change events and can perform edge migration.
  • edge migration refers to migration on the network side (for example, UPF reselection or user plane path update, etc.), and/or application context migration, etc. It should also be understood that if AF subscribes to the DNAI change event, then the occurrence of the DNAI change event will trigger the event notification process, but will not necessarily trigger edge migration.
  • FIG. 4 is a schematic flowchart of a subscription event change notification method 400, which specifically includes the following steps.
  • DNAI change event subscribed by AF occurs.
  • specific implementation methods please refer to the existing technology and will not be described again here.
  • S421 SMF sends notification message #a to NEF.
  • NEF receives notification message #a from SMF.
  • the notification message #a is used to notify that a DNAI change event occurs, and the notification message #a includes the target DNAI, that is, the DNAI corresponding to the current (changed) location of the UE.
  • the notification message #a may be the Nsmf_EventExposure_Notify message, which is not specifically limited in this application.
  • NEF sends notification message #b to AF.
  • AF receives notification message #b from NEF.
  • the notification message #b is used to notify the occurrence of a DNAI change event, and the notification message #b includes the DNAI corresponding to the current location of the UE.
  • the notification message #b may be the Nnef_TrafficInfluence_Notify message, which is not specifically limited in this application.
  • SMF sends notification message #a to NEF through Nsmf_EventExposure_Notify message, and NEF sends notification message #b to AF through Nnef_TrafficInfluence_Notify message.
  • S423, SMF sends notification message #c to AF.
  • AF receives notification message #c from SMF.
  • the notification message #c is used to notify the occurrence of a DNAI change event, and the notification message #c includes the DNAI corresponding to the current location of the UE.
  • the Nsmf_EventExposure_Notify message is sent directly to AF.
  • the information contains the DNAI corresponding to the current location of the UE.
  • the AF determines the target AF based on the DNAI corresponding to the current location of the UE.
  • the AF may be called source AF.
  • the target AF can be understood as an AF that is currently better or suitable for serving the UE.
  • the specific implementation method of AF determining the target AF based on DNAI can be found in the existing technology, and will not be described again here.
  • NEF receives message #a from AF.
  • the notification message #a includes the target AF.
  • the notification message #a may be the Nnef_TrafficInfluence_AppRelocationInfo message, which is not specifically limited in this application.
  • NEF sends message #b to SMF.
  • SMF receives message #b from NEF.
  • the notification message #b includes the target AF.
  • the notification message #b may be the Nsmf_EventExposure_AppRelocationInfo message, which is not specifically limited in this application.
  • AF first sends notification message #a to NEF through the Nnef_TrafficInfluence_AppRelocationInfo message, and then NEF sends notification message #b to AF through the Nsmf_EventExposure_AppRelocationInfo message.
  • SMF receives message #c from AF.
  • the notification message #c includes the target AF.
  • the notification message #c may be the Nsmf_EventExposure_AppRelocationInfo message, which is not specifically limited in this application.
  • AF sends the notification message #c to SMF through the Nsmf_EventExposure_AppRelocationInfo message.
  • the AF illustrates two possible implementation methods of sending a message to the PCF through steps S441 and S422, and step S445 to provide policy rule information for control plane network elements (such as AMF, SMF, etc.).
  • control plane network elements such as AMF, SMF, etc.
  • NEF sends message #d to PCF.
  • PCF receives message #d from NEF.
  • the notification message #d may be an Npcf_PolicyAuthorization_Update message, which is not specifically limited in this application.
  • AF first sends notification message #a to NEF through the Nnef_TrafficInfluence_AppRelocationInfo message, and then NEF sends notification message #d to PCF through the Npcf_PolicyAuthorization_Update message.
  • PCF receives message #e from AF.
  • the notification message #e may be an Npcf_PolicyAuthorization_Update message, which is not specifically limited in this application.
  • the AF sends the notification message #e to the PCF through the Npcf_PolicyAuthorization_Update message.
  • S450, SMF and UPF perform migration on the network side.
  • network side migration includes reselecting UPF, inserting new UPF, etc.
  • network side migration includes reselecting UPF, inserting new UPF, etc.
  • S461 SMF sends notification message #a’ to NEF.
  • NEF receives notification message #a’ from SMF.
  • the notification message #a' is used to notify the occurrence of a DNAI change event, and the notification message #a' includes the DNAI corresponding to the current location of the UE.
  • the notification message #a' may be an Nsmf_EventExposure_Notify message, which is not specifically limited in this application.
  • NEF sends notification message #b’ to AF.
  • AF receives the notification message #b’ from NEF.
  • the notification message #b' is used to notify the occurrence of a DNAI change event, and the notification message #b' includes the DNAI corresponding to the current location of the UE.
  • the notification message #b' may be the Nnef_TrafficInfluence_Notify message, which is not specifically limited in this application.
  • S463 SMF sends notification message #c’ to AF.
  • AF receives notification message #c’ from SMF.
  • the notification message #c' is used to notify the occurrence of a DNAI change event, and the notification message #c' includes the DNAI corresponding to the current location of the UE.
  • S470 The AF determines the target AF based on the DNAI corresponding to the current location of the UE.
  • the AF may be called source AF.
  • the target AF can be understood as an AF that is currently better or suitable for serving the UE.
  • NEF receives message #a’ from AF.
  • the notification message #a' includes the target AF.
  • the notification message #a' may be the Nnef_TrafficInfluence_AppRelocationInfo message, which is not specifically limited in this application.
  • NEF sends message #b’ to SMF.
  • SMF receives message #b’ from NEF.
  • the notification message #b' includes the target AF.
  • the notification message #b' may be the Nsmf_EventExposure_AppRelocationInfo message, which is not specifically limited in this application.
  • SMF receives message #c' from AF.
  • the notification message #c' includes the target AF.
  • the notification message #c' may be the Nsmf_EventExposure_AppRelocationInfo message, which is not specifically limited in this application.
  • NEF sends message #d’ to PCF.
  • PCF receives message #d’ from NEF.
  • the notification message #d' may be an Npcf_PolicyAuthorization_Update message, which is not specifically limited in this application.
  • PCF receives message #e’ from AF.
  • the notification message #e' may be an Npcf_PolicyAuthorization_Update message, which is not specifically limited in this application.
  • steps S461-S463 are similar to steps S421-S423, step S470 is similar to step S430, and steps S481-S485 are similar to steps S441-S445. For the sake of simplicity, they will not be described in detail.
  • steps S421-S445 are the first possible implementation, that is, application context migration is completed before the network side performs migration
  • steps S461-S485 are the second possible implementation, that is, application context migration is performed. It is completed after network-side migration is performed, and there is no specific limit on this.
  • the source AF can determine the target AF based on the DNAI corresponding to the current location of the UE.
  • the EHEs corresponding to the source AF and the target AF are deployed by different parties, that is, the source AF and the target AF are deployed by different operators/third parties respectively, and the two may not open deployment information to each other, then the source AF It is impossible to determine the target AF locally based on the DNAI corresponding to the current location of the UE, which brings many difficulties to the migration of the application context.
  • this application proposes a communication method that determines the information of the target AF network element based on the DNAI corresponding to the current location of the UE based on the network side (for example, SMF or NEF), and sends it to the source AF network element, so that the source AF network element, so that the source AF network element.
  • the application context can still be migrated to the target AF network element.
  • At least one refers to one or more, and “multiple” refers to two or more.
  • “And/or” describes the association of associated objects, indicating that there can be three relationships, for example, A and/or B, which can mean: A exists alone, A and B exist simultaneously, and B exists alone, where A, B can be singular or plural.
  • the character “/” generally indicates that the related objects are in an "or” relationship.
  • “At least one of the following” or similar expressions thereof refers to any combination of these items, including any combination of a single item (items) or a plurality of items (items).
  • At least one of a, b and c can mean: a, or, b, or, c, or, a and b, or, a and c, or, b and c, or, a , b and c.
  • a, b and c can be single or multiple respectively.
  • the protocol definition can be implemented by pre-saving corresponding codes, tables or other methods that can be used to indicate relevant information in the device (for example, the initiating device and the responding device).
  • This application will focus on its specific implementation. No restrictions.
  • the "protocol” involved in the embodiments of this application may refer to standard protocols in the communication field, and may include, for example, LTE protocols, NR protocols, WLAN protocols, and related protocols applied in future communication systems. This application does not limit this.
  • used for indicating may include used for direct indicating and used for indirect indicating.
  • the indication information may include that the indication information directly indicates A or indirectly indicates A, but it does not mean that the indication information must carry A.
  • the instruction methods involved in the embodiments of this application should be understood to cover various methods that can enable the party to be instructed to obtain the information to be instructed.
  • the information to be instructed can be sent together as a whole, or can be divided into multiple sub-information and sent separately, and the sending cycle and/or sending timing of these sub-information can be the same or different. This application does not limit the specific sending method.
  • the "instruction information" in the embodiment of this application may be an explicit indication, that is, a direct indication through signaling, or may be obtained based on parameters indicated by signaling, combined with other rules or other parameters, or obtained through derivation. It can also be an implicit indication, that is, obtained based on rules or relationships, or based on other parameters, or derivation. This application does not specifically limit this.
  • radio resource control signaling includes radio resource control (RRC) signaling
  • MAC layer signaling includes MAC control element (MAC control element, MAC CE) signaling
  • “communication” may refer to “wireless communication”.
  • “Communication” can also be described as “data transmission”, “information transmission”, “data processing”, etc.
  • “Transmission” includes “sending” and “receiving”. This application does not specifically limit this.
  • Figure 5 is a schematic flowchart of the first method 500 provided by the embodiment of this application. Specifically, it includes the following steps.
  • the first core network element obtains the data network access identifier DNAI corresponding to the current location of the terminal device.
  • the first core network element may be an NEF network element or an SMF network element, which is not specifically limited in this application.
  • the current position of the terminal device may be the position after movement/change, and the DNAI corresponding to the current position of the terminal device may be one or more, which is not specifically limited in this application.
  • the first core network element can determine the DNAI based on the location of the terminal device.
  • the first core network element may also determine the DNAI based on the network topology or EAS deployment information.
  • the first core network element determines the information of the target application function AF network element based on DNAI.
  • the information of the target AF network element includes the identification (for example, ID) or address information of the target AF network element.
  • the identification information of the target AF network element also includes the service ID or domain name of the target AF network element, etc., which is not limited in this application.
  • the DNAI corresponding to the current location of the terminal device corresponds to the information of the target AF network element, that is, the terminal device can access the target AF network element through the DNAI, or access services deployed/managed by the target AF network element. That is, the target AF network element determined based on the DNAI can be used as the service network element after the terminal device migrates the application context.
  • the following possible implementation methods are included for the first core network element to obtain the information of the target AF network element.
  • One possible implementation method is that the first core network element locally saves the information of the target AF network element based on the AF request sent by the source AF network element and/or the target AF network element, and then can obtain it locally.
  • Another possible implementation method is that after the first core network element obtains the information of the target AF network element based on the AF request, it can send a request to the second core network element to save the information of the target AF network element, and at the same time delete it locally or not delete it. Furthermore, the first core network element can be obtained from the second core network element.
  • Another possible implementation method is that after the first core network element obtains the information of the target AF network element based on the AF request, it does not need to send the target AF information to the second core network element, and the second core network element obtains the information through other networks. Obtain and store the information of the target AF network element through the network element or other methods (for example, local configuration of the second core network element, or obtaining the information of the AF network element in other processes). Therefore, the first core network element can also obtain the information of the target AF network element from the second core network element.
  • the second core network element includes a UDR network element, a UDM network element or an NRF network element, which is not specifically limited in this application.
  • the first core network element sends a second request message to the second core network element, and receives a response message from the second core network element.
  • the second request message is used to request to obtain information about the target AF network element.
  • the second request message includes the DNAI corresponding to the current location of the terminal device.
  • the response message includes the information about the target AF.
  • the source AF network element before the first core network element determines the information of the target AF network element according to the DNAI, the source AF network element sends the first request message to the first core network element.
  • the first core network element receives the first request message from the source AF network element.
  • the first request message is used to request to obtain information about the target AF network element, and the first request message includes the DNAI corresponding to the current location of the terminal device.
  • One possible implementation manner is that when the source AF network element cannot determine the information of the target AF network element based on DNAI, the source AF network element sends the first request message to the first core network element.
  • AF1 cannot locally determine the target AF network element based on the DNAI. This may be because AF1 and the target AF are deployed by different parties, causing AF1 to be unable to sense the DNAI. Alternatively, it may be that AF1 fails to determine the target AF based on the DNAI. Alternatively, it may be that AF1 is actively unwilling to determine the target AF through the DNAI, etc. This application does not specifically limit this.
  • the first request message also includes first indication information, where the first indication information is used to instruct to obtain the information of the target AF network element.
  • the first core network element determines the information of the target AF network element based on the DNAI corresponding to the current location of the terminal device and the first indication information.
  • the first core network element can determine the information of the target AF network element based on the received first request message and/or the DNAI carried in the first request message, it means that the first core network element has internal logic. That is, the first request message itself is used to indicate a request to obtain the target AF network element. Alternatively, the DNAI carried in the first request message is used to indicate a request to acquire the target AF network element. Or, when the first core network element does not have internal logic, it can be based on the first The indication information determines the information of the target AF network element.
  • this application does not specifically limit the internal logic of the first core network element.
  • the first core network element sends the information of the target AF network element to the source AF network element.
  • the source AF network element receives the information of the target AF network element from the first core network element.
  • the source AF network element is the network element that currently serves the terminal device
  • the target AF is the network element that serves the terminal device after application context migration.
  • the source AF network element sends the second indication information to the first core network element.
  • the first core network element receives the second indication information from the source AF network element.
  • the second indication information is used to indicate that the first core network element is allowed to send the information of the target AF network element to the AF network element.
  • the second indication information is also used to indicate that the first core network element is allowed to use the AF network element as the target AF network element and send it to other AF network elements.
  • each AF network element can send the second indication information to the first core network element.
  • Each AF network element can serve as either a target AF network element or a source AF network element, which is beneficial to the network side. Determine the network elements that serve the terminal device after application context migration.
  • the source AF network element may send the second indication information to the SMF network element through the UDR network element.
  • the SMF network element can receive the second indication information from the source AF network element through the UDR network element.
  • the source AF network element migrates the application context to the target AF network element according to the information of the target AF network element.
  • the first core network element can also send the DNAI corresponding to the current location of the terminal device to the source AF.
  • the source AF network element receives the DNAI from the first core network element. Further, the source AF can determine the information of the target AF network element based on the DNAI, thereby completing the application context migration to the target AF network element.
  • the information of the target AF network element determined locally by the source AF network element and the information of the target AF network element received from the first core network element may be the same or different, and this application does not specifically limit this.
  • the solution disclosed in this application determines the information of the target AF network element through the network side and sends it to the source AF network element, so that the source AF network element can discover the target AF network element, which is beneficial to the source AF network.
  • element migrates the application context to the target AF network element. Especially for situations where the target AF does not open deployment information to the source AF due to different deployment parties, or there is information isolation between the source AF and the target AF and cannot interact normally, etc., it is ensured that the source AF network element can provide information to the target AF network element in different scenarios. Migrate application context.
  • the following takes the DNAI change event of the AF subscribing to the UE as an example to illustrate the technical solution provided by the present application.
  • FIG. 6 is a schematic flowchart of the second communication method 600 provided by the embodiment of the present application.
  • AF1 is the source AF network element
  • AF2 is the target AF network element
  • NEF is the first core network element
  • UDR is the second core network element.
  • AF1 sends request message #1 to NEF.
  • NEF receives request message #1 from AF1.
  • the request message #1 includes information about AF1, such as the AF1 identifier, and at least one DNAI#1.
  • the AF1 identifier may be AF1ID or the address of AF1, which is not limited in this application.
  • At least one DNAI#1 refers to all or part of the DNAI#1 corresponding to the AF1.
  • “corresponding” can be understood as “managed, controlled, serviceable”, etc. That is, the UE can access the AF1 through any one of the at least one DNAI#1, or access the services deployed/managed by the AFl, or the UE can access the AF1 according to any one of the at least one DNAI#1.
  • any one of the at least one DNAI#1 is determined to be the DNAI corresponding to the current location of the UE, then the AF1 can be used as a candidate target AF.
  • the request message #1 also includes indication information #1 (that is, an example of the second indication information).
  • the indication information #1 is used to indicate that the network side is allowed to send target AF information (for example, target AF ID and address, etc.). This also means that the network side is allowed to use the AFl as the target AF and send the AFl information (for example, the AFl identifier, and at least one DNAI#1) to other AFs.
  • the request message #1 may be an AF request, indicating that AF1 opens AF1 information to NEF, or requests registration or online, etc., which is not specifically limited in this application.
  • request message #1 can be a newly defined message or a message already defined in the standard, such as the Nnef_TrafficInfluence_Create/Update message, etc. This application does not specifically limit this.
  • each AF can send the request message #1 to the network side.
  • the AF sending time may be after the AF is deployed or powered on, or at any time, which is not limited in this application.
  • the AF information for example, the AF identifier, and at least one DNAI
  • the AF may send updated AF information to the network side.
  • the "target AF” can be understood as an AF that is currently better or suitable for serving the UE.
  • “Target AF” refers to information of target AF.
  • the information of the target AF may be the identification of the target AF, such as target AF ID, address, etc.
  • target AF may also refer to a target AF identifier, such as an address.
  • identity can also be extended to "information", such as service ID, domain name, etc. This application does not specifically limit this. Therefore, in the embodiment of the present application, "determining/requesting/returning/sending (target) AF” actually refers to determining/requesting/returning/sending (target) AF information.
  • the features of “Target AF” mentioned later will not be described again.
  • AF2 sends request message #11 to NEF.
  • NEF receives request message #11 from AF2.
  • the request message #11 includes AF2 information, such as the AF2 identifier, and at least one DNAI #11.
  • the AF2 identifier may be AF2ID or the address of AF2, which is not limited in this application.
  • the request message #11 also includes indication information #11, which is used to indicate that the network side is allowed to send target AF information (for example, target AF ID and address, etc.) to the AF2.
  • indication information #11 is used to indicate that the network side is allowed to send target AF information (for example, target AF ID and address, etc.) to the AF2.
  • target AF information for example, target AF ID and address, etc.
  • the network side is allowed to use the AF2 as the target AF and send the information of the AF2 (for example, the AF2 identifier, and at least one DNAI#11) to other AFs.
  • NEF can save the information of AF1 in the above request message #1 in the UDR.
  • NEF sends AF1 information to UDR.
  • UDR receives information from AF1 of NEF.
  • the AF1 information includes the AF1 identifier and at least one DNAI#1.
  • the NEF can send the AF1 information by calling the Nudr_DM_Create/Update message, that is, the NEF sends the AF1 identifier to the UDR through the Nudr_DM_Create/Update message, and at least one DNAI#1.
  • NEF can also save the AF2 information in the above request message #11 in the UDR.
  • NEF sends AF2 information to UDR.
  • UDR receives information from NEF's AF2.
  • the AF2 information includes an AF2 identifier and at least one DNAI#11.
  • the NEF can send the AF2 information by calling the Nudr_DM_Create/Update message, that is, the NEF sends the AF2 identifier and at least one DNAI#11 to the UDR through the Nudr_DM_Create/Update message.
  • NEF receives the subscription message #a from AF1.
  • the subscription message #a includes the UE identity (or UE address information), and the subscription event (for example, subscribing to the UE's DNAI change event).
  • the UE identification can be a UE ID, IP address or other identification, etc., which is not specifically limited in this application.
  • the technical solution of this application may be targeted at a certain UE or session. For example, at least one UE or session. If you subscribe to the DNAI change event of multiple UEs or sessions, the subscription message #a may include a group ID, or an identifier such as DNN/S-NSSAI.
  • the subscription message #a may be the Nnef_TrafficInfluence_Create/Update message, that is, AF1 sends the subscription message #a to NEF through the Nnef_TrafficInfluence_Create/Update message.
  • NEF sends subscription message #b to SMF.
  • SMF receives subscription message #b from NEF.
  • the subscription message #b includes the UE identity and subscription event.
  • steps S621-S622 can refer to steps S320-S360 in the above-mentioned method 300.
  • steps S621-S622 can refer to steps S320-S360 in the above-mentioned method 300.
  • steps S320-S360 in the above-mentioned method 300.
  • S630 SMF determines that the subscription event occurs.
  • the SMF determines that the DNAI of the UE has changed.
  • the SMF determines that the DNAI of the UE has changed.
  • SMF sends notification message #1 to NEF.
  • NEF receives notification message #1 from SMF.
  • the notification message #1 is used to notify that the DNAI of the UE changes.
  • the notification message #1 includes the DNAI corresponding to the current location of the UE, that is, the DNAI corresponding to the current (changed) location of the UE.
  • the notification message #1 may be an Nsmf_EventExposure Notify message, that is, the SMF sends the DNAI to the NEF through the Nsmf_EventExposure Notify message.
  • NEF sends notification message #2 to AF1.
  • AF1 receives notification message #2 from NEF.
  • the notification message #2 is used to notify that the UE's DNAI changes, and the notification message #2 includes the DNAI corresponding to the current location of the UE.
  • the notification message #2 may be the Nnef_TrafficInfluence_Notify message, that is, the NEF sends the DNAI to the AF through the Nnef_TrafficInfluence_Notify message.
  • AF1 cannot determine the target AF based on the DNAI corresponding to the current position of the UE.
  • AF1 determines to trigger subsequent steps, that is, AF1 determines to request the target AF from the network side.
  • NEF receives request message #2 from AF1.
  • the request message #2 is used to request the NEF to obtain the target AF, and the request message #2 includes the DNAI corresponding to the current location of the UE.
  • the request message #2 may be an Nnef_TrafficInfluence_Update message, that is, AF1 sends the DNAI to NEF through the Nnef_TrafficInfluence_Update message.
  • the request message #2 also includes indication information #2 (that is, an example of the first indication message), and the indication information #2 is used to request acquisition of the target AF.
  • indication information #2 that is, an example of the first indication message
  • NEF determines the target AF according to request message #2.
  • NEF determines the target AF based on the DNAI corresponding to the current location of the UE.
  • NEF needs to have internal logic. That is, NEF determines the target AF based on internal logic.
  • the request message #2 itself is used to indicate a request to obtain the target AF, that is, if NEF receives the request message #2, the NEF needs to determine and send the target AF to AF1.
  • the DNAI corresponding to the current location of the UE carried in the request message #2 is used to indicate a request to obtain the target AF. That is, when NEF receives the DNAI from AFl, NEF needs to determine and send the target to AFl.
  • NEF determines the target AF based on the DNAI corresponding to the current location of the UE and indication information #2. For example, NEF receives the request message #2, determines the target AF based on the DNAI, and returns the target AF to AF1 based on the indication information #2.
  • the way NEF obtains the target AF includes the following two implementation methods.
  • NEF can obtain the target AF locally.
  • NEF can save AF1 information and AF2 information. Then, NEF can locally determine the target AF, namely AF2, based on the request message #2 sent by AF1.
  • Another possible implementation method illustrates that UDR saves AF1 information and AF2 information. Then, NEF can also obtain the target AF from the UDR, which specifically includes the following steps S671 and S672.
  • NEF sends request message #3 (that is, an example of the second request message) to UDR.
  • UDR receives request message #3 from NEF.
  • the request message #3 is used to request to obtain the target AF, and the request message #3 includes the UE identifier and the DNAI corresponding to the current location of the UE.
  • the request message #3 may be a Nudr_DM_Query Request message, that is, NEF sends the UE identity and the DNAI to the UDR through the Nudr_DM_Query Request/Response message.
  • UDR sends response message #1 to NEF.
  • NEF receives response message #1 from UDR.
  • the response message #1 includes the target AF.
  • the response message #1 may be a Nudr_DM_Query Response message, that is, the UDR sends the target AF to the NEF through the Nudr_DM_Query Response message.
  • steps S613, S614, S671 and S672 are executed in NRF
  • steps S613 and S614 can be executed by calling the Nnrf_NFManagement_NFRegister message
  • steps S671 and S672 can be executed by calling the Nnrf_NFDiscovery Request/Response message; or, the above steps S613 and S614 is executed in UDR, S671 and S672 are executed in NRF, etc.
  • steps S613 and S614 is executed in UDR, S671 and S672 are executed in NRF, etc. This application does not specifically limit this.
  • NEF sends notification message #3 to AF1.
  • AF1 receives notification message #3 from NEF.
  • the notification message #3 includes target AF.
  • the notification message #3 may be the Nnef_TrafficInfluence Notify message, that is, NEF sends the target AF to AF1 through the Nnef_TrafficInfluence Notify message.
  • the source AF for example, AF1
  • the target AF for example, AF2
  • the source AF for example, AF1
  • the target AF for example, AF2
  • steps S441-S445 or steps S481-S485 in the above-mentioned method 400 for the sake of brevity, no further details will be given here.
  • AF2 as the target AF is only an example.
  • the target AF can also be other AF (for example, AF3).
  • AF3 is similar to AF2.
  • the specific method of determining the target AF please refer to the above step S670.
  • this implementation sends request message #2 to NEF through the source AF (for example, AF1) and obtains the target AF (for example, AF2) to achieve the technical effect of determining the target AF.
  • the source AF for example, AF1
  • the target AF for example, AF2
  • FIG. 7 is a schematic flowchart of the third communication method 700 provided by the embodiment of the present application.
  • AF1 is the source AF network element
  • AF2 is the target AF network element
  • SMF is the first core network element
  • UDR is the second core network element.
  • AF1 sends request message #A to SMF.
  • SMF receives the request message #A from AF1.
  • UDR receives request message #B from AF1.
  • UDR sends request message #C to SMF.
  • SMF receives the request message #C from UDR.
  • the request message #A, the request message #B and the request message #C all include the AF1 identifier (for example, ID or address, etc.), and at least one DNAI #A.
  • the request message #A, the request message #B, and the request message #C all further include indication information #A (that is, an example of the second indication information).
  • the indication information #A is used to indicate that the network is allowed to side-direct the AF1 sends target AF information.
  • AF2 sends request message #AA to SMF.
  • SMF receives the request message #AA from AF2.
  • UDR receives the request message #BB from AF1.
  • UDR sends request message #CC to SMF.
  • SMF receives the request message #CC from UDR.
  • the request message #AA, the request message #BB and the request message #CC all include the AF2 identifier (for example, ID or address, etc.), and at least one DNAI #AA.
  • the request message #AA, the request message #BB and the request message #CC also include indication information #B, which is used to indicate that the network side is allowed to send target AF information to the AF2.
  • steps S711 and steps S712-S713 are two possible implementation methods for AF1 to send a request message (for example, AF request) to SMF.
  • steps S714 and S715-S716 are two possible implementation methods for AF2 to send a request message (for example, AF request) to SMF.
  • AF1 and AF2 execute steps S711 and S714 respectively, it means that the UDR does not store AF information (for example, AF ID, address, and at least one DNAI, etc.). If AF1 and AF2 execute steps S712-S713 and S715-S716 respectively, it means that the UDR may or may not store AF information, and this application does not specifically limit this.
  • AF information for example, AF ID, address, and at least one DNAI, etc.
  • AF1 and AF2 execute steps S712-S713 and S715-S716 respectively, it means that the UDR may or may not store AF information, and this application does not specifically limit this.
  • request message #A, request message #B and request message #C have similar meanings to the request message #1 in step S611 in method 600, and the request message #AA, request message #B and request message #CC are similar to The meaning of request message #11 in step S612 in method 600 is similar. For the sake of brevity, no further details will be given here.
  • SMF receives the subscription message #A from AF1.
  • the subscription message #A includes the UE identity and subscription event.
  • step S720 is similar to the implementation of S621-S622 in the above-mentioned method 600, and will not be described again here for the sake of brevity.
  • SMF determines that the subscription event occurs.
  • the SMF determines that the DNAI of the UE has changed.
  • S630 in the above method 600, which will not be described again here.
  • SMF sends notification message #A to AF1.
  • AF1 receives notification message #A from SMF.
  • the notification message #A is used to notify that the UE's DNAI changes, and the notification message #A includes the DNAI corresponding to the current location of the UE.
  • step S740 is similar to the implementation of S641-S642 in the above method 600, and will not be described again here for the sake of brevity.
  • AF1 cannot determine the target AF based on the DNAI corresponding to the current position of the UE.
  • step S650 in the above method 600, which will not be described again here.
  • AF1 determines to trigger subsequent steps, that is, AF1 determines to request the target AF from the network side.
  • S760 AF1 sends request message #D (that is, an example of the first request message) to SMF.
  • request message #D that is, an example of the first request message
  • SMF receives the request message #D from AF1.
  • the request message #D is used to request the SMF to obtain the target AF, and the request message #D includes the DNAI corresponding to the current location of the UE.
  • the request message #D also includes indication information #C (that is, an example of the first indication message), and the indication information #C is used to request acquisition of the target AF.
  • indication information #C that is, an example of the first indication message
  • step S760 can refer to steps S320-S360 in the above-mentioned method 300.
  • steps S320-S360 in the above-mentioned method 300.
  • the SMF determines the target AF according to the request message #C.
  • the SMF determines the target AF based on the DNAI corresponding to the current location of the UE. That is, SMF needs to have internal logic.
  • the request message #C itself is used to indicate a request to acquire the target AF.
  • the DNAI corresponding to the current location of the UE carried in the request message #C is used to indicate a request to obtain the target AF.
  • the SMF determines the target AF based on the DNAI and indication information #C corresponding to the current location of the UE.
  • the way in which SMF obtains the target AF includes the following two implementation methods.
  • SMF can obtain the target AF locally.
  • the SMF can save the AF1 information and AF2 information.
  • the UDR can save AF1 information and AF2 information. Then, the SMF can also obtain the target AF from the UDR, which specifically includes the following steps S771 and S772.
  • S771 SMF sends request message #E (that is, an example of the second request message) to UDR.
  • UDR receives request message #E from SMF.
  • the request message #E is used to request to obtain the target AF, and the request message #E includes the UE identifier and the DNAI corresponding to the current location of the UE.
  • UDR sends response message #A to SMF.
  • SMF receives response message #A from UDR.
  • the response message #A includes the target AF.
  • steps S712, S715, S771 and S772 are executed in other centralized network elements, such as UDM and NRF, which is not specifically limited in this application.
  • steps S770-S772 are similar to the above-mentioned steps S670-S671 in the method 600, and for the sake of simplicity, they will not be described again here.
  • SMF sends notification message #B to AF1.
  • AF1 receives notification message #B from SMF.
  • the notification message #B includes the target AF.
  • AF2 as the target AF is only an example.
  • the target AF can also be other AF (for example, AF3).
  • AF3 is similar to AF2.
  • the specific method of determining the target AF please refer to the above step S770.
  • this implementation sends request message #2 to the SMF through the source AF (for example, AF1), and obtains the target AF (for example, AF2), to achieve the technical effect of determining the target AF.
  • the source AF for example, AF1
  • the target AF for example, AF2
  • FIG 8 is a schematic flowchart of the fourth communication method 800 provided by the embodiment of the present application.
  • AF1 is the source AF network element
  • AF2 is the target AF network element
  • NEF is the first core network element
  • UDR is the second core network element.
  • the NEF actively determines and delivers the target AF to the source AF. Specifically, it includes the following steps.
  • NEF receives the request message # ⁇ from AF1.
  • the request message # ⁇ includes information of AF1, such as AF1 identification (eg, ID or address), and at least one DNAI# ⁇ .
  • the request message # ⁇ also includes indication information # ⁇ (that is, an example of the second indication information).
  • the indication information # ⁇ is used to indicate that the network side is allowed to send target AF information (for example, target AF ID) to the AFl. and address, etc.).
  • NEF receives the request message # ⁇ from AF2.
  • the request message # ⁇ includes information of AF2, such as AF2 identification (eg, ID or address), and at least one DNAI # ⁇ .
  • the request message # ⁇ also includes indication information # ⁇ , which is used to indicate that the network side is allowed to send target AF information (for example, target AF ID and address, etc.) to the AF2.
  • indication information # ⁇ is used to indicate that the network side is allowed to send target AF information (for example, target AF ID and address, etc.) to the AF2.
  • NEF can save the AF1 information in the above request message # ⁇ in the UDR.
  • NEF sends AF1 information to UDR.
  • UDR receives information from AF1 of NEF.
  • the AF1 information includes the AF1 identifier and at least one DNAI# ⁇ .
  • NEF can also save the AF2 information in the above request message # ⁇ in the UDR.
  • NEF sends AF2 information to UDR.
  • UDR receives information from AF1 of NEF.
  • the AF1 information includes the AF2 identifier and at least one DNAI# ⁇ .
  • NEF receives the subscription message # ⁇ from AF1.
  • the subscription message # ⁇ includes the UE identity and subscription event.
  • NEF sends subscription message # ⁇ to SMF.
  • SMF receives the subscription message # ⁇ from NEF.
  • the subscription message # ⁇ includes the UE identity and subscription event.
  • SMF determines that the subscription event occurs.
  • S840 SMF sends notification message # ⁇ to NEF.
  • NEF receives notification message # ⁇ from SMF.
  • the notification message # ⁇ is used to notify that the DNAI of the UE changes, and the notification message # ⁇ includes the DNAI corresponding to the current location of the UE.
  • steps S811-S840 is similar to steps S611-S614 in the above method 600.
  • steps S811-S840 are similar to steps S611-S614 in the above method 600.
  • NEF determines the target AF according to the notification message # ⁇ .
  • NEF determines the target AF based on the DNAI corresponding to the current location of the UE. That is, NEF needs to have internal logic.
  • the notification message # ⁇ itself is used to indicate a request to acquire the target AF.
  • the DNAI corresponding to the current location of the UE carried in the notification message # ⁇ is used to indicate a request to obtain the target AF.
  • NEF determines the target AF based on the DNAI and indication information # ⁇ corresponding to the current location of the UE.
  • the way NEF obtains the target AF includes the following two implementation methods.
  • NEF can obtain the target AF locally.
  • NEF can obtain the target AF from the UDR, which specifically includes the following steps S851 and S852.
  • NEF sends request message # ⁇ (that is, an example of the second request message) to UDR.
  • UDR receives the request message # ⁇ from NEF.
  • the request message # ⁇ is used to request to obtain the target AF, and the request message # ⁇ includes the UE identity and the DNAI corresponding to the current location of the UE.
  • UDR sends response message # ⁇ to NEF.
  • NEF receives the response message # ⁇ from UDR.
  • the response message # ⁇ includes the target AF.
  • steps S850-S852 is similar to steps S670-S672 in the above method 600.
  • steps S670-S672 are similar to steps S670-S672 in the above method 600.
  • NEF sends notification message # ⁇ to AF1.
  • AF1 receives the notification message # ⁇ from NEF.
  • the notification message # ⁇ includes the target AF.
  • the notification message # ⁇ also includes the DNAI corresponding to the current location of the UE.
  • AF1 determines the target AF according to the notification message # ⁇ .
  • the notification message # ⁇ carries the target AF (for example, AF2). Then, AF1 determines AF2 as the target AF.
  • the notification message # ⁇ carries the DNAI corresponding to the target AF (for example, AF2) and the current location of the UE. Then, AF1 can determine AF2 as the target AF. Alternatively, AF1 may also determine the target AF based on the DNAI corresponding to the current location of the UE. If AF1 determines AF3 based on the DNAI corresponding to the current location of the UE, AF3 can be determined as the target AF. Among them, AF3 can be the same as or different from AF2. If AF1 cannot determine the target AF based on the DNAI corresponding to the current location of the UE, AF2 is determined as the target AF, which is not specifically limited in this application.
  • AF1 cannot determine the target AF based on the DNAI corresponding to the current location of the UE
  • AF2 is determined as the target AF, which is not specifically limited in this application.
  • AF2 as the target AF is only an example.
  • the target AF can also be other AF (for example, AF3).
  • AF3 is similar to AF2.
  • the specific method of determining the target AF please refer to the above step S850.
  • this implementation actively determines the target AF through NEF and sends the target AF to the source AF (for example, AF1) to achieve the technical effect of determining the target AF.
  • the source AF for example, AF1
  • FIG. 9 is a schematic flowchart of the fifth communication method 900 provided by the embodiment of the present application.
  • AF1 is the source AF network element
  • AF2 is the target AF network element
  • SMF is the first core network element
  • UDR is the second core network element.
  • the SMF actively determines and delivers the target AF to the source AF. Specifically, it includes the following steps.
  • AF1 sends request message #a to SMF.
  • SMF receives the request message #a from AF1.
  • UDR receives the request message #b from AF1.
  • UDR sends request message #c to SMF.
  • SMF receives the request message #c from UDR.
  • the request message #a, the request message #b and the request message #c all include the AF1 identifier (for example, ID or address, etc.), and at least one DNAI #A.
  • the request message #a, the request message #b and the request message #c all further include indication information #a (that is, an example of the second indication information), the indication information #a is used to indicate that the network is allowed to side AF1 sends target AF information.
  • indication information #a that is, an example of the second indication information
  • AF2 sends request message #aa to SMF.
  • SMF receives the request message #aa from AF2.
  • UDR receives the request message #bb from AF1.
  • UDR sends request message #cc to SMF.
  • SMF receives the request message #cc from UDR.
  • the request message #aa, the request message #bb and the request message #cc all include an AF2 identifier (for example, ID or address, etc.), and at least one DNAI #AA.
  • the request message #aa, the request message #bb and the request message #cc also include indication information #b, where the indication information #b is used to indicate that the network side is allowed to send target AF information to the AF2.
  • SMF receives the subscription message #a from AF1.
  • the subscription message #a includes the UE identity and subscription event.
  • SMF determines that the subscription event occurs.
  • the SMF determines that the DNAI of the UE changes.
  • steps S911-S930 are similar to the implementation of S711-S730 in the above-mentioned method 700, and will not be described again here for the sake of brevity.
  • SMF determines the target AF according to the subscription message #a.
  • the SMF determines the target AF based on the DNAI corresponding to the current location of the UE. That is, SMF needs to have internal logic.
  • the subscription message #a itself is used to indicate a request to acquire the target AF.
  • the DNAI corresponding to the current location of the UE carried in the subscription message #a is used to indicate a request to obtain the target AF.
  • the SMF determines the target AF based on the DNAI and indication information #a corresponding to the current location of the UE.
  • the way in which SMF obtains the target AF includes the following two implementation methods.
  • SMF can obtain the target AF locally.
  • the SMF can save the AF1 information and AF2 information.
  • the UDR can save AF1 information and AF2 information. Then, the SMF can also obtain the target AF from the UDR, which specifically includes the following steps S971 and S972.
  • S941 SMF sends request message #d (that is, an example of the second request message) to UDR.
  • UDR receives request message #d from SMF.
  • the request message #d is used to request to obtain the target AF, and the query request message #d includes the UE identifier and the DNAI corresponding to the current location of the UE.
  • UDR sends response message #a to SMF.
  • SMF receives response message #a from UDR.
  • the response message #a includes the target AF.
  • steps S940-S942 are similar to the above-mentioned steps S770-S772 in the method 600, and for the sake of simplicity, they will not be described again here.
  • SMF sends notification message #1 to AF1.
  • AF1 receives notification message #1 from SMF.
  • the notification message #1 includes target AF.
  • the notification message #1 also includes the DNAI corresponding to the current location of the UE.
  • AF1 determines the target AF according to notification message #1.
  • the notification message #1 carries the target AF (for example, AF2). Then, AF1 determines AF2 as the target AF.
  • the notification message #1 carries the DNAI corresponding to the target AF (for example, AF2) and the current location of the UE. Then, AF1 can determine AF2 as the target AF. Alternatively, AF1 may also determine the target AF based on the DNAI corresponding to the current location of the UE, which is not specifically limited in this application.
  • the target AF for example, AF2
  • AF1 may also determine the target AF based on the DNAI corresponding to the current location of the UE, which is not specifically limited in this application.
  • steps S960-S970 are similar to steps S870-S880 in the above-mentioned method 800, and will not be described again here.
  • AF2 as the target AF is only an example.
  • the target AF can also be other AF (for example, AF3).
  • AF3 is similar to AF2.
  • the specific method of determining the target AF please refer to the above step S940.
  • this implementation actively determines the target AF through SMF and sends the target AF to the source AF (for example, AF1) to achieve the technical effect of determining the target AF.
  • the source AF for example, AF1
  • the network side determines the target AF based on the DNAI corresponding to the current location of the UE and sends it to the source AF to realize the discovery of the target AF.
  • the communication method embodiment of the present application is described in detail above with reference to FIGS. 1 to 9 .
  • the communication device side embodiment of the present application will be described in detail with reference to FIGS. 10 and 11 . It should be understood that the description of the device embodiments corresponds to the description of the method embodiments. Therefore, the parts not described in detail can be referred to the previous method embodiments.
  • FIG 10 is a schematic block diagram of a communication device provided by an embodiment of the present application.
  • the device 1000 may include a transceiver unit 1010 and a processing unit 1020.
  • the transceiver unit 1010 can communicate with the outside, and the processing unit 1020 is used for data processing.
  • the transceiver unit 1010 may also be called a communication interface or a transceiver unit.
  • the device 1000 can implement steps or processes corresponding to those executed by the first core network element (for example, NEF/SMF) in the above method embodiment, wherein the processing unit 1020 is used to execute the above.
  • the transceiver unit 1010 is configured to perform operations related to the processing of the first core network element in the above method embodiment.
  • the device 1000 can implement steps or processes corresponding to those performed by the source AF network element (for example, source AF) in the above method embodiment, wherein the transceiver unit 1010 is used to perform the above method.
  • the processing unit 1020 is used to perform the processing of the source AF network element in the above method embodiment. management related operations.
  • the device 1000 here is embodied in the form of a functional unit.
  • the term "unit” as used herein may refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor (such as a shared processor, a proprietary processor, or a group of processors) used to execute one or more software or firmware programs. processor, etc.) and memory, merged logic circuitry, and/or other suitable components to support the described functionality.
  • ASIC application specific integrated circuit
  • the device 1000 can be specifically the first core network element in the above embodiment, and can be used to perform various steps corresponding to the first core network element in the above method embodiment.
  • Processes and/or steps, or the device 1000 can be specifically the source AF network element in the above embodiment, and can be used to execute various processes and/or steps corresponding to the source AF network element in the above method embodiment. To avoid duplication, I won’t go into details here.
  • the device 1000 of each of the above solutions has the function of realizing the corresponding steps performed by the first core network element in the above method, or the device 1000 of each of the above solutions has the function of realizing the corresponding steps of the source AF network element in the above method.
  • the functions described can be implemented by hardware, or can be implemented by hardware executing corresponding software.
  • the hardware or software includes one or more modules corresponding to the above functions; for example, the transceiver unit can be replaced by a transceiver (for example, the sending unit in the transceiver unit can be replaced by a transmitter, and the receiving unit in the transceiver unit can be replaced by a receiving unit. (machine replacement), other units, such as processing units, etc., can be replaced by processors to respectively perform the sending and receiving operations and related processing operations in each method embodiment.
  • the above-mentioned transceiver unit may also be a transceiver circuit (for example, it may include a receiving circuit and a transmitting circuit), and the processing unit may be a processing circuit.
  • the device in Figure 10 can be the source AF network element or the first core network element in the previous embodiment, or it can be a chip or chip system, such as: system on chip (SoC) .
  • SoC system on chip
  • the transceiver unit may be an input-output circuit or a communication interface.
  • the processing unit is a processor or microprocessor or integrated circuit integrated on the chip. No limitation is made here.
  • FIG 11 shows a communication device 2000 provided by an embodiment of the present application.
  • the device 2000 includes a processor 2010 and a transceiver 2020.
  • the processor 2010 and the transceiver 2020 communicate with each other through an internal connection path, and the processor 2010 is used to execute instructions to control the transceiver 2020 to send signals and/or receive signals.
  • the device 2000 may also include a memory 2030, which communicates with the processor 2010 and the transceiver 2020 through internal connection paths.
  • the memory 2030 is used to store instructions, and the processor 2010 can execute the instructions stored in the memory 2030.
  • the device 2000 is configured to implement various processes and steps corresponding to the first core network element in the above method embodiment.
  • the device 2000 is configured to implement various processes and steps corresponding to the source AF network element in the above method embodiment.
  • the device 2000 may be specifically the first core network element or the source AF network element in the above embodiment, or may be a chip or a chip system.
  • the transceiver 2020 may be the transceiver circuit of the chip, which is not limited here.
  • the device 2000 may be used to execute various steps and/or processes corresponding to the first core network element or the source AF network element in the above method embodiment.
  • the memory 2030 may include read-only memory and random access memory and provide instructions and data to the processor.
  • a portion of the memory may also include non-volatile random access memory.
  • the memory may also store device type information.
  • the processor 2010 may be configured to execute instructions stored in the memory, and when the processor 2010 executes the instructions stored in the memory, the processor 2010 is configured to execute the above-mentioned steps with the first core network element or the source AF. Each step and/or process of the method embodiment corresponding to the network element.
  • each step of the above method can be completed by instructions in the form of hardware integrated logic circuits or software in the processor.
  • the steps of the methods disclosed in conjunction with the embodiments of the present application can be directly implemented by a hardware processor for execution, or can be executed by a combination of hardware and software modules in the processor.
  • the software module can be located in random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, registers and other mature storage media in this field.
  • the storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware. To avoid repetition, it will not be described in detail here.
  • the processor in the embodiment of the present application may be an integrated circuit chip with signal processing capabilities. During the implementation process, each step of the above method embodiment can be completed through an integrated logic circuit of hardware in the processor or instructions in the form of software.
  • the above-mentioned processor may be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components.
  • DSP digital signal processor
  • ASIC application-specific integrated circuit
  • FPGA field programmable gate array
  • the processor in the embodiment of the present application can implement or execute the various methods, steps and logical block diagrams disclosed in the embodiment of the present application.
  • a general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.
  • the steps of the method disclosed in conjunction with the embodiments of the present application can be directly implemented by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, registers and other mature storage media in this field.
  • the storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.
  • non-volatile memory can be read-only memory (ROM), programmable ROM (PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrically removable memory. Erase electrically programmable read-only memory (EPROM, EEPROM) or flash memory. Volatile memory can be random access memory (RAM), which is used as an external cache.
  • RAM random access memory
  • RAM static random access memory
  • DRAM dynamic random access memory
  • SDRAM synchronous dynamic random access memory
  • double data rate SDRAM double data rate SDRAM
  • DDR SDRAM double data rate SDRAM
  • ESDRAM enhanced synchronous dynamic random access memory
  • SLDRAM synchronous link dynamic random access memory
  • direct rambus RAM direct rambus RAM
  • the present application also provides a computer program product.
  • the computer program product includes: computer program code.
  • the computer program code When the computer program code is run on a computer, it causes the computer to execute the steps shown in Figures 5 to 9 The method in any of the illustrated embodiments.
  • the present application also provides a computer-readable medium.
  • the computer-readable medium stores program code.
  • the program code When the program code is run on a computer, it causes the computer to execute the steps shown in Figures 5 to 9 The method in any of the illustrated embodiments.
  • this application also provides a system, which includes the aforementioned one or more sites and one or more access points.
  • the disclosed systems, devices and methods can be implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of the units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components may be combined or can be integrated into another system, or some features can be ignored, or not implemented.
  • the coupling or direct coupling or communication connection between each other shown or discussed may be through some interfaces, and the indirect coupling or communication connection of the devices or units may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place, or they may be distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.
  • each functional unit in each embodiment of the present application can be integrated into one processing unit, each unit can exist physically alone, or two or more units can be integrated into one unit.
  • the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium.
  • the technical solution of the present application is essentially or the part that contributes to the existing technology or the part of the technical solution can be embodied in the form of a software product.
  • the computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in various embodiments of this application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk and other media that can store program code. .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Physics & Mathematics (AREA)
  • Mathematical Physics (AREA)
  • Theoretical Computer Science (AREA)
  • Quality & Reliability (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

La présente demande concerne un procédé et un appareil de communication, qui peuvent réaliser la découverte d'un élément de réseau AF cible, ce qui facilite ainsi la migration d'un contexte d'application d'un élément de réseau AF source à l'élément de réseau AF cible. Le procédé comprend les étapes suivantes : un premier élément de réseau central acquiert un DNAI correspondant à l'emplacement courant d'un dispositif terminal ; le premier élément de réseau central détermine des informations d'un élément de réseau AF cible selon le DNAI ; et le premier élément de réseau central envoie des informations de l'élément de réseau AF cible à un élément de réseau AF source, l'élément de réseau AF source représentant un élément de réseau desservant actuellement le dispositif terminal. Le procédé vise principalement un scénario dans lequel un contexte d'application doit être migré d'une AF source à une AF cible en raison d'un déplacement d'UE ou d'une surcharge d'un AS ayant fait l'objet d'un accès par l'UE ou similaire, mais à cause du fait que l'AF source et l'AF cible appartiennent à différents dispositifs de déploiement, ou à cause de l'isolation d''informations (ou d'autres motifs) entre l'AF source et l'AF cible ou similaire, un élément de réseau AF source ne peut pas déterminer un élément de réseau AF cible.
PCT/CN2023/083566 2022-03-28 2023-03-24 Procédé de communication et appareil de communication WO2023185657A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210313610.1A CN116887259A (zh) 2022-03-28 2022-03-28 通信方法和通信装置
CN202210313610.1 2022-03-28

Publications (1)

Publication Number Publication Date
WO2023185657A1 true WO2023185657A1 (fr) 2023-10-05

Family

ID=88199302

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/083566 WO2023185657A1 (fr) 2022-03-28 2023-03-24 Procédé de communication et appareil de communication

Country Status (2)

Country Link
CN (1) CN116887259A (fr)
WO (1) WO2023185657A1 (fr)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109547513A (zh) * 2017-09-22 2019-03-29 华为技术有限公司 应用上下文的处理方法和装置
CN109756937A (zh) * 2017-11-01 2019-05-14 中国移动通信有限公司研究院 业务连续性保障方法、功能网元及存储介质
CN112437435A (zh) * 2020-12-07 2021-03-02 腾讯科技（深圳）有限公司 一种数据信息获取方法、装置、相关设备及介质
US20210195554A1 (en) * 2018-08-16 2021-06-24 NEC Corporation Limited System and Method of Multiple Application Functions influence in 5G Networks
CN113660703A (zh) * 2020-05-12 2021-11-16 苹果公司 根据应用功能请求朝向局域数据网络的流量路由
WO2021260420A1 (fr) * 2020-06-25 2021-12-30 Nokia Solutions And Networks Oy Procédure de relocalisation de fonction d'application

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109547513A (zh) * 2017-09-22 2019-03-29 华为技术有限公司 应用上下文的处理方法和装置
CN109756937A (zh) * 2017-11-01 2019-05-14 中国移动通信有限公司研究院 业务连续性保障方法、功能网元及存储介质
US20210195554A1 (en) * 2018-08-16 2021-06-24 NEC Corporation Limited System and Method of Multiple Application Functions influence in 5G Networks
CN113660703A (zh) * 2020-05-12 2021-11-16 苹果公司 根据应用功能请求朝向局域数据网络的流量路由
WO2021260420A1 (fr) * 2020-06-25 2021-12-30 Nokia Solutions And Networks Oy Procédure de relocalisation de fonction d'application
CN112437435A (zh) * 2020-12-07 2021-03-02 腾讯科技（深圳）有限公司 一种数据信息获取方法、装置、相关设备及介质

Also Published As

Publication number Publication date
CN116887259A (zh) 2023-10-13

Similar Documents

Publication Publication Date Title
WO2021057794A1 (fr) Procédé de configuration de service, dispositif de communication et système de communication
WO2022048394A1 (fr) Procédé de connexion réseau, procédé de déconnexion réseau et appareil de communication
US20230199550A1 (en) Relay Management Method and Communication Apparatus
US20230189188A1 (en) Method for terminal to access public and private networks and communications apparatus
US20230112588A1 (en) Communication method and related device
US20210007172A1 (en) Capability exposure method, related apparatus, and system
EP4185009A1 (fr) Procédé, appareil et système d'acheminement de paquets
US20240172084A1 (en) Data transmission method and apparatus
US20230189054A1 (en) Relay communication method, and communication apparatus
WO2022199451A1 (fr) Procédé et appareil de commutation de session
US20240107417A1 (en) Communication method and apparatus
KR20240060670A (ko) 통신 방법 및 장치
WO2023185657A1 (fr) Procédé de communication et appareil de communication
EP4280682A1 (fr) Procédé de communication sans fil, appareil de communication et système de communication
CN115696468A (zh) 通信的方法和通信装置
WO2023185561A1 (fr) Procédé de communication et appareil de communication
WO2023142717A1 (fr) Procédé et appareil pour déterminer une politique de sélection d'itinéraire d'équipement utilisateur
WO2023185620A1 (fr) Procédé et appareil de communication
WO2023116556A1 (fr) Procédé et appareil de commutation de session
WO2023133871A1 (fr) Procédé et appareil de communication
WO2022170798A1 (fr) Procédé de détermination de stratégie et appareil de communication
WO2023207958A1 (fr) Procédé de transmission de politique, et appareil et système de communication
WO2024027320A1 (fr) Procédé, dispositif et système de communication sans fil
WO2023197737A1 (fr) Procédé d'envoi de message, procédé de gestion de pin, appareil de communication et système de communication
WO2023160394A1 (fr) Procédé et appareil de communication

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23778026

Country of ref document: EP

Kind code of ref document: A1