WO2022089503A1 - 应用接入网络的方法、装置及系统 - Google Patents

应用接入网络的方法、装置及系统 Download PDF

Info

Publication number
WO2022089503A1
WO2022089503A1 PCT/CN2021/126843 CN2021126843W WO2022089503A1 WO 2022089503 A1 WO2022089503 A1 WO 2022089503A1 CN 2021126843 W CN2021126843 W CN 2021126843W WO 2022089503 A1 WO2022089503 A1 WO 2022089503A1
Authority
WO
WIPO (PCT)
Prior art keywords
message
application
instance
application instance
user plane
Prior art date
Application number
PCT/CN2021/126843
Other languages
English (en)
French (fr)
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 华为技术有限公司
Priority to EP21885230.9A priority Critical patent/EP4213576A4/en
Priority to JP2023521575A priority patent/JP7547701B2/ja
Publication of WO2022089503A1 publication Critical patent/WO2022089503A1/zh
Priority to US18/310,236 priority patent/US20230319147A1/en

Links

Images

Classifications

    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/141—Setup of application sessions
    • 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/10—Flow control between communication endpoints
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/50—Service provisioning or reconfiguring
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/24—Connectivity information management, e.g. connectivity discovery or connectivity update
    • H04W40/246—Connectivity information discovery
    • 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
    • H04W40/248—Connectivity information update
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels

Definitions

  • the present application relates to the field of communication technologies, and in particular, to a method, an apparatus, and a system for an application access network.
  • the 3rd generation partnership project (3GPP) working group is responsible for the formulation of the mobile communication network standard architecture.
  • the application usually belongs to a different system to the mobile communication network.
  • MEC mobile edge computing
  • I Internet technology
  • RAN radio access network
  • I Internet technology
  • RAN radio access network
  • I user location information
  • RAN radio access network
  • MEC is managed by the European Telecommunications Standards Institute (ETSI).
  • ETSI European Telecommunications Standards Institute
  • the data interaction and management between the mobile communication network and the application need to be realized through a specific interface and deployment scheme.
  • the current 3GPP standard has a special description for the capability opening of applications, and at the same time, a network exposure function (NEF) is added to realize the capability opening of application functions (AF).
  • AF application functions
  • AF application functions
  • AF application functions
  • the embodiments of the present application provide a method, device, and system for an application to access a network, so as to incorporate an application into a mobile communication network planning to improve the flexibility of data interaction between the application and the mobile communication network.
  • a method for applying an access network may be a session management function entity; or a module applied in the session management function entity, such as a chip or a chip system.
  • the following description will be given by taking the execution subject as the session management function entity as an example.
  • the session management function entity receives a first message from the application instance access module, where the first message includes identification information of the first application instance, and the first message is used to request to establish a relationship between the first application instance and the mobile communication network for the first application instance.
  • the session management function entity determines the first user plane function entity serving the first application instance; the session management function entity sends a second message to the first user plane function entity, and the second message includes the first application instance The identification information of the instance, the second message is used to request to establish the first connection for the first application instance; the session management function entity receives the third message from the first user plane function entity, the third message includes the first connection The establishment result, wherein the establishment result includes success; the session management function entity sends a fourth message to the application instance access module, where the fourth message includes the first address allocated by the core network element for the first connection.
  • the session management function entity and the first user plane function entity in the mobile communication network establish the first connection between the first application instance and the mobile communication network for the first application instance, and after establishing the first connection It can be known from the first address allocated by the core network element for the first connection during the connection process that the address allocation and management corresponding to the first application instance and the forwarding path of the data plane are all within the control range of the mobile communication network. That is to say, in this solution, the first application instance can be accessed into the mobile communication network as a special terminal device. Since the first application instance is a specific running instance of an application, based on this solution, the flexibility of data interaction between the application and the mobile communication network can be improved.
  • the first address is used for the terminal device to perform data communication with the first application instance.
  • the terminal device may access the first application instance through the first address.
  • a self-organizing network can be formed between the terminal device and the first application instance, which can realize plug-and-play application services, so that data mutual access between the terminal device and the application server where the first application instance is located can be realized.
  • the first message and the second message further include the first path information allocated by the application instance access module for the first connection; the third message and the fourth message also include Including second path information allocated by the first user plane function entity for the first connection, wherein the first path information and the second path information are used to establish the first user plane function entity in the first connection and the application instance Access the first path between modules.
  • data transmission can be performed between the first user plane functional entity and the application instance access module through the first path.
  • the core network element is the first user plane functional entity; and the third message further includes the first address. That is, in this embodiment of the present application, the first user plane functional entity allocates the first address for the first connection.
  • the core network element is a session management function entity. That is, in this embodiment of the present application, the session management function entity allocates the first address for the first connection.
  • the second message further includes the first address, where the first address is used for the first user plane functional entity to advertise routes. Based on this solution, subsequent other network elements or entities can directly address the first user plane functional entity according to the route advertised by the first user plane functional entity.
  • the first message further includes a first parameter
  • the first parameter is used to determine the first user plane function entity or the first user plane function entity serving the first application instance
  • the parameters are used to construct a virtual local area network including the first user plane functional entity.
  • the first parameter includes at least one of the following parameters: the location information of the first application instance, the session and service continuity SSC mode, the data network name DNN corresponding to the first connection, or the data of the network slice where the first connection is located. identification information.
  • the first message further includes application information corresponding to the first application instance, where the application information is used to construct a virtual local area network including the first user plane functional entity.
  • the application information may include, for example, application name or application identifier or application domain name information.
  • the first message includes the above-mentioned first parameter and application information corresponding to the first application instance, and the first parameter and the application information corresponding to the first application instance are used for for constructing a virtual local area network including the first user plane functional entity.
  • the method further includes: the session management function entity sends a fifth message to the unified data management function entity, where the fifth message includes the identification information of the first application instance, and the fifth message includes the identification information of the first application instance.
  • the message is used to request to acquire the subscription data of the first application instance;
  • the session management function entity receives the subscription data from the unified data management function entity, wherein the subscription data is used to determine the first application instance serving the first application instance.
  • User plane functional entity; or the subscription data is used to construct a virtual local area network including the first user plane functional entity.
  • the parameter of the first user plane functional entity determined to serve the first application instance includes at least one of the above-mentioned first parameter or subscription data.
  • the parameters for constructing the virtual local area network including the first user plane functional entity include at least one of the above-mentioned first parameter, application information corresponding to the first application instance, or the above-mentioned subscription data.
  • the method further includes: the session management function entity registers with the network storage function entity that the session management function entity supports the function of establishing a connection for the application instance. Based on this solution, when a session management function entity is subsequently selected, a session management function entity that supports establishing a connection for an application instance can be obtained from the network storage function entity.
  • a method for an application to access a network may be an application instance access module; it may also be a module applied to the application instance access module, such as a chip or a chip system ; It can also be a device including the application instance access module, such as a first application instance or an application server or an application integration platform.
  • the following description takes the execution subject as the application instance access module as an example.
  • the application instance access module determines a session management function entity serving the first application instance; the application instance access module sends a first message to the session management function entity, where the first message includes identification information of the first application instance, and the first message It is used to request to establish a first connection between the first application instance and the mobile communication network for the first application instance; the application instance access module receives a fourth message from the session management function entity, and the fourth message includes the core network network The first address allocated for the first connection.
  • the session management function entity and the first user plane function entity in the mobile communication network establish the first connection between the first application instance and the mobile communication network for the first application instance, and after establishing the first connection It can be known from the first address allocated by the core network element for the first connection during the connection process that the address allocation and management corresponding to the first application instance and the forwarding path of the data plane are all within the control range of the mobile communication network. That is to say, in this solution, the first application instance can be accessed into the mobile communication network as a special terminal device. Since the first application instance is a specific running instance of an application, based on this solution, the flexibility of data interaction between the application and the mobile communication network can be improved.
  • the first address is used for the terminal device to perform data communication with the first application instance.
  • the terminal device may access the first application instance through the first address.
  • a self-organizing network can be formed between the terminal device and the first application instance, which can realize plug-and-play application services, so that data mutual access between the terminal device and the application server where the first application instance is located can be realized.
  • the first message further includes first path information allocated by the application instance access module for the first connection; the fourth message further includes the first user plane function second path information allocated by the entity for the first connection, wherein the first path information and the second path information are used to establish a first path between the first user plane functional entity and the application instance access module, and the first path information
  • a user plane function entity is a user plane function entity serving the first application instance.
  • the method further includes: after the application instance access module obtains the first data from the first application instance, sending the first data to the first user plane functional entity through the first path or, the application instance access module receives the second data from the first user plane function entity through the first path.
  • the method further includes: the application instance access module publishes a route according to the first address. Based on this solution, other network elements or entities can be directly addressed to the application instance access module according to the route advertised by the application instance access module. For example, in a possible implementation manner, the method further includes: the application instance access module receives second data from a second user plane function entity, where the second user plane function entity is accessed according to the application instance The route advertised by the module is addressed to the access module of the application instance.
  • the method before the application instance access module sends the first message to the session management function entity, the method further includes: the application instance access module receives a message from the first application instance. a sixth message, where the sixth message includes application information corresponding to the first application instance, and is used to request registration to the application instance access module; after the application instance access module receives the fourth message from the session management function entity, the The method further includes: the application instance access module sends the first address to the first application instance.
  • the core network element is a session management functional entity; or, the core network element is a first user plane functional entity serving the first application instance.
  • the first message further includes a first parameter, where the first parameter is used to determine the first user plane function entity serving the first application instance; or the The first parameter is used to construct a virtual local area network including the first user plane functional entity.
  • the first parameter includes at least one of the following parameters: the location information of the first application instance, the session and service continuity SSC mode, the data network name DNN corresponding to the first connection, or the network slice where the first connection is located. identification information.
  • the first message further includes application information corresponding to the first application instance, where the application information is used to construct a virtual local area network including the first user plane functional entity.
  • the application information may include, for example, application name or application identifier or application domain name information.
  • the first message includes the above-mentioned first parameter and application information corresponding to the first application instance, and the first parameter and the application information corresponding to the first application instance are used for For constructing a virtual local area network including a first user plane functional entity, the first user plane functional entity is a user plane functional entity serving the first application instance.
  • the application instance access module determines the session management function entity serving the first application instance, including: the application instance access module obtains support as the application instance from the network storage function entity Information of one or more session management function entities that establish a connection; the application instance access module determines a session management function entity serving the first application instance according to the information of the one or more session management function entities. That is, in the embodiment of the present application, the application instance access module may determine the session management function entity serving the first application instance through interaction with the network storage function entity.
  • a method for applying an access network is provided, and the communication device executing the power control method may be a first user plane functional entity; or a module applied in the first user plane functional entity, such as a chip or chip system.
  • the execution subject as the first user plane functional entity as an example.
  • the first user plane functional entity receives a second message from the session management functional entity, where the second message includes identification information of the first application instance, and the second message is used to request the establishment of the first application instance and the mobile communication network for the first application instance
  • the first connection between the first user plane function entity is the user plane function entity serving the first application instance; the first user plane function entity sends a third message to the session management function entity, and the third message includes the first A connection establishment result, wherein the establishment result includes success or failure.
  • the session management function entity and the first user plane function entity in the mobile communication network establish the first connection between the first application instance and the mobile communication network for the first application instance, and after establishing the first connection It can be known from the first address allocated by the core network element for the first connection during the connection process that the address allocation and management corresponding to the first application instance and the forwarding path of the data plane are all within the control range of the mobile communication network. That is to say, the solution can access the first application instance into the mobile communication network as a special terminal device. Since the first application instance is a specific running instance of an application, based on this solution, the flexibility of data interaction between the application and the mobile communication network can be improved.
  • the second message further includes first path information allocated by the application instance access module for the first connection; the third message further includes the first user plane The second path information allocated by the functional entity for the first connection, wherein the first path information and the second path information are used to establish a connection between the first user plane functional entity and the application instance access module in the first connection the first path.
  • data transmission can be performed between the first user plane functional entity and the application instance access module through the first path.
  • the third message further includes the first address allocated by the first user plane functional entity for the first connection. That is, in this embodiment of the present application, the first user plane functional entity allocates the first address for the first connection.
  • the second message further includes the first address allocated by the session management function entity for the first connection. That is, in this embodiment of the present application, the session management function entity allocates the first address for the first connection.
  • the first address is used for the terminal device to perform data communication with the first application instance.
  • the terminal device may access the first application instance through the first address.
  • a self-organizing network can be formed between the terminal device and the first application instance, which can realize plug-and-play application services, so that data mutual access between the terminal device and the application server where the first application instance is located can be realized.
  • the method further includes: the first user plane functional entity publishes a route according to the first address. Based on this solution, subsequent other network elements or entities can directly address the first user plane functional entity according to the route advertised by the first user plane functional entity.
  • the method further includes: the first user plane function entity receives the second data from the second user plane function entity, and sends the second data to the first application instance through the application instance access module Second data. Wherein, the second user plane functional entity is addressed to the first user plane functional entity according to the route advertised by the first user plane functional entity.
  • the second user plane functional entity is a user plane functional entity serving the terminal device, and the terminal device can access the first application instance through the first address. Based on this solution, data transmission from the terminal device to the first application instance can be realized.
  • the method further includes: the first user plane function entity registers with the network storage function entity that the first user plane function entity supports the function of establishing a connection for the application instance. Based on this solution, when the user plane functional entity is subsequently selected, the user plane functional entity that supports establishing a connection for the application instance can be obtained from the network storage functional entity.
  • the method further includes: the first user plane functional entity receives the first data from the first application instance through the application instance access module; the first user plane functional entity The first data is sent to a second user plane function entity, where the second user plane function entity is a user plane function entity serving terminal equipment.
  • the terminal device can access the first application instance through the first address. Based on this solution, data transmission from the first application instance to the terminal device can be implemented.
  • a communication device for implementing the above method.
  • the communication device includes corresponding modules, units, or means (means) for implementing the above method, and the modules, units, or means may be implemented by hardware, software, or hardware executing corresponding software.
  • the hardware or software includes one or more modules or units corresponding to the above functions.
  • a communication device comprising: a processor; the processor is configured to be coupled to a memory, and after reading computer instructions stored in the memory, execute the method according to any one of the preceding aspects according to the instructions.
  • the communication apparatus further includes a memory; the memory is used for storing computer instructions.
  • the communication apparatus further includes a communication interface; the communication interface is used for the communication apparatus to communicate with other devices.
  • the communication interface may be a transceiver, an input/output interface, an interface circuit, an output circuit, an input circuit, a pin or a related circuit, and the like.
  • the communication device may be a chip or a chip system.
  • the communication device when the communication device is a chip system, the communication device may be constituted by a chip, and may also include a chip and other discrete devices.
  • the above-mentioned communication interface may be an input/output interface, an interface circuit, an output circuit, an input circuit on the chip or a chip system , pins or related circuits, etc.
  • the processor described above may also be embodied as a processing circuit or a logic circuit.
  • a computer-readable storage medium is provided, and instructions are stored in the computer-readable storage medium, when the computer-readable storage medium runs on a computer, the computer can perform the method described in any one of the above aspects.
  • a computer program product comprising instructions which, when run on a computer, enable the computer to perform the method of any of the preceding aspects.
  • a communication system includes the session management functional entity described in the first aspect and the first user plane functional entity described in the third aspect.
  • the communication system further includes the application instance access module described in the foregoing second aspect.
  • Figure 1 is a schematic diagram of the existing 3GPP ULCL architecture
  • Figure 2 is a schematic diagram of the existing 3GPP BP architecture
  • FIG. 3 is a brief schematic diagram of the MEC standard architecture currently defined by ETSI;
  • FIG. 4 is a schematic diagram of a form of deploying a local (local) APP in an existing MEC solution
  • FIG. 5 is a schematic diagram of a user plane architecture of an existing 5GVN service
  • FIG. 6 is a schematic diagram of an existing user plane protocol stack based on N19 tunnel forwarding
  • FIG. 7 is a schematic structural diagram of a communication system provided by an embodiment of the present application.
  • FIG. 8 is a schematic diagram 1 of deployment of an application instance access module provided by an embodiment of the present application.
  • FIG. 9 is a second schematic diagram of deployment of an application instance access module provided by an embodiment of the present application.
  • FIG. 10 is a schematic diagram of an application of the communication system provided by the embodiment of the present application in a 5G network;
  • FIG. 11 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • FIG. 12 is an interactive schematic diagram 1 of a method for an application to access a network provided by an embodiment of the present application
  • FIG. 13 is a second interactive schematic diagram of a method for an application to access a network provided by an embodiment of the present application
  • FIG. 14 is an interactive schematic diagram 3 of a method for accessing a network by an application provided by an embodiment of the present application
  • FIG. 15 is a schematic structural diagram of a communication apparatus provided by an embodiment of the present application.
  • the APP in the embodiment of the present application refers to a certain type of application service provided, for example, a certain type of application service that provides Internet services.
  • the APP may be Taobao, for example, for providing Internet services for online shopping; or, the APP may be, for example, Tencent Video, for providing Internet services for watching videos online, and so on.
  • the APP instance in the embodiments of the present application refers to an instance of running an APP.
  • the corresponding APP instance refers to the instance running Taobao; or, when the APP is Tencent Video, the corresponding APP instance refers to the instance running Tencent Video.
  • each APP may deploy multiple APP instances to jointly provide services, that is, one APP may correspond to multiple APP instances.
  • the APP instance usually runs in the application server, which is uniformly described here, and will not be repeated below.
  • anchor user plane function (UPF) and the intermediate UPF (intermediate UPF, I-UPF):
  • the anchor UPF may be a protocol data unit (protocol data unit, PDU) session anchor (PDU session anchor, PSA)-UPF.
  • PDU protocol data unit
  • PSA session anchor
  • the anchor UPF is responsible for publishing the downlink routing policy of the Internet Protocol (IP) of the terminal device, and the packets sent to the terminal device will be based on the The downlink routing policy is forwarded to the anchor UPF for processing.
  • IP Internet Protocol
  • the I-UPF is located between the RAN device and the anchor UPF, and handover occurs continuously as the terminal device moves.
  • the 3GPP uplink-classifier (ULCL) architecture and the 3GPP branching point (branching point) architecture are 3GPP uplink-classifier (ULCL) architecture and the 3GPP branching point (branching point) architecture:
  • 3GPP formulated the 5th generation (5th generation, 5G) core network user plane service.
  • 5th generation, 5G 5th generation
  • 4G evolved packet core
  • FIG. 1 is a schematic diagram of an existing 3GPP ULCL architecture.
  • 3GPP defines the architecture of 3GPP ULCL as follows: A new UPF ULCL can be inserted between the RAN device and the anchor UPF of the PDU session.
  • ULCL acts as an upstream classifier for data streams. That is, based on the identification of the upstream characteristics of the traffic flow, the data is offloaded to the local data network (DN) through the local anchor point UPF or the data is offloaded to the remote DN through the remote anchor point UPF.
  • DN local data network
  • UPF ULCL also needs to aggregate downstream.
  • the local DN and the remote DN are the same DN.
  • the UPF ULCL in FIG. 1 can be deployed together with the local anchor UPF, or can be deployed separately, which is not specifically limited here.
  • the access and mobility management function (core access and mobility management function, AMF) in Figure 1 is used for mobility management in the mobile network, such as user location update, user registration network, user handover, etc.
  • the session management function (SMF) in FIG. 1 is used for session management in the mobile network, such as session establishment, modification or release, etc., which are described in a unified manner here, and will not be repeated below.
  • FIG. 2 is a schematic diagram of the existing 3GPP BP architecture.
  • the 3GPP BP architecture is similar to the 3GPP ULCL architecture, with the difference, for example, that UPF ULCL in Figure 1 is replaced with UPF BP.
  • UPF BP has the same function as UPF ULCL, except
  • UPF BP is a split point insertion for internet protocol version 6 (internet protocol version 6, IPV6); UPF ULCL is for internet protocol version 4 (internet protocol version 4, IPV4) or non-Multi-homed (IPV6 multi-homing, which allows a single session in multi-address) scenarios.
  • IPV6 has a little difference from IPV4 in the user plane: for IPv4 or IPv6 type PDU sessions, the PDU session anchor can be the IP anchor of the IP address/prefix assigned to the end device.
  • IPv4-type PDU sessions or non-Multi-homed IPv6 PDU sessions when multiple PDU session anchors are used (because UPF ULCL is inserted), only one PDU session anchor is the IP anchor.
  • FIG. 3 is a brief schematic diagram of the MEC standard architecture currently defined by ETSI.
  • the MEC standard architecture includes: a MEC system level (MEC system level) and a MEC host level (MEC host level).
  • the MEC system layer includes an operation support system (OSS) and a multi-access edge orchestrator.
  • OSS operation support system
  • multi-access edge orchestrator multi-access edge orchestrator
  • the MEC host layer includes: a MEC platform manager (MEC platform Manager, MEPM), a virtualisation infrastructure manager (virtualisation infrastructure manager), and one or more MEC hosts.
  • MEC host includes: MEC platform (MEC platform, MEP), virtualisation infrastructure (virtualisation infrastructure) and multiple MEC APPs.
  • MEPM performs MEC APP life cycle management, MEC APP rule and request management, and MEC platform element management through the Mm5 interface.
  • MEP is used to run the MEC service (MEC service), perform service registry (service registry), traffic rules control (traffic rules control), and domain name system (domain name system, DNS) processing, etc.
  • MEC service MEC service
  • service registry service registry
  • traffic rules control traffic rules control
  • domain name system domain name system
  • DNS domain name system
  • the MEP has the AF function in the 5G network, and the AF function in the MEP is implemented through the MEC APP.
  • the MEP and the MEC APP communicate through the Mp1 interface to realize the management of the MEC APP, and specific services are run on the MEC APP.
  • the device APP can access the MEC APP on the MEC host through the network.
  • the MEP communicates with the user plane (data plane) in the virtualized infrastructure through the Mp2 interface.
  • the data plan can be implemented by UPF, therefore, the Mp2 interface can also be understood as the interface between MEP and UPF.
  • the UPF in the MEC host refers to the UPF deployed at the edge.
  • the customer facing service (CFS) portal is connected to the OSS through the Mx1 interface.
  • the device APP device app
  • the user APP life cycle management (LCM) proxy user APP LCM proxy
  • the user APP LCM agent is connected to the OSS and the multi-access edge coordinator through the Mm8 interface and the Mm9 interface respectively.
  • the OSS and the multi-access edge coordinator are connected through the Mm1 interface, and the OSS is also connected with the MEPM through the Mm2 interface.
  • the multi-access edge coordinator is connected to the MEPM through the Mm3 interface.
  • the multi-access edge coordinator is also connected to the virtualized infrastructure through the Mm4 interface.
  • the virtualized infrastructure is connected to the MEPM through the Mm4 interface.
  • the virtualization infrastructure in the MEC host is connected to the virtualization infrastructure manager through the Mp7 interface.
  • the MEPs of the two MEC hosts communicate through the Mp3 interface.
  • the device APP here refers to an APP installed on a terminal device (or called user equipment (user equipment, UE)), which is described here uniformly and will not be repeated below.
  • the MEC APP needs to communicate with the virtualized infrastructure in the mobile communication network through the MEC platform.
  • the data interaction and management between the mobile communication network and the application need to be implemented through a specific interface and deployment scheme.
  • the data interaction between the application and the mobile communication network is not flexible enough.
  • FIG. 4 is a schematic diagram of a form of deploying a local (local) APP in the existing MEC solution.
  • the terminal device accesses the user plane processing function of the 5G network through the RAN device of the 5G network.
  • the user plane processing function may connect the content delivery website through a local IP anchor.
  • the user plane processing functions can connect to the Internet through a central IP anchor.
  • the user plane processing function in FIG. 4 may correspond to the UPF ULCL in FIG. 1 or the UPF BP in FIG. 2 .
  • the local IP anchor point in FIG. 4 may correspond to the local anchor point UPF in FIG. 1 or FIG. 2 .
  • the central IP anchor point in FIG. 4 may correspond to the remote anchor point UPF in FIG.
  • the content delivery website in FIG. 4 may correspond to the DN of the connection local anchor UPF in FIG. 1 or FIG. 2 .
  • the Internet in FIG. 4 may correspond to the DN of the UPF connected to the remote anchor point in FIG. 1 or FIG. 2 .
  • the user plane processing function in Figure 4 can be deployed in the virtualized infrastructure in Figure 3, and the content delivery website in Figure 4 can be deployed in the MEC APP in Figure 3. It can be understood that the connection between the terminal device and the user plane processing function is a wireless connection, and the connection between the user plane processing function and the content delivery website or the Internet is a wired connection.
  • 5G virtual network 5G virtual network, 5GVN:
  • 5GVN can also be called 5G local area network (5GLAN), LAN, LAN-type service (type service), LAN-VN, 5GLAN-type service, 5GLAN-VN, 5GLAN group ( group), or LAN group, etc., which are not specifically limited in this embodiment of the present application.
  • 5GLAN 5G local area network
  • LAN LAN
  • LAN-type service type service
  • LAN-VN LAN-VN
  • 5GLAN-type service 5GLAN-type service
  • 5GLAN-VN 5GLAN-VN
  • group 5GLAN group
  • LAN group 5GLAN group
  • 5GVN service is a service provided by the current 5G network, which is mainly used in home communication, corporate office, factory manufacturing, vehicle networking, power grid transformation and public security organs.
  • the service can provide private communication (ie, point-to-point data transmission) of Internet Protocol (IP) type or non-IP type (eg, Ethernet type) for two or more terminal devices in a group of terminal devices.
  • IP Internet Protocol
  • non-IP type eg, Ethernet type
  • IP Internet Protocol
  • the devices in the factory form a 5GVN group, and different devices can send Ethernet packets to each other; or, the office equipment (such as mobile phones, computers or laptops) of employees in a department in the enterprise forms a 5GVN group, different Office equipment can send IP packets to each other, and so on. If the two terminal devices are not in the same 5GVN group, they cannot communicate with each other.
  • FIG. 5 is a schematic diagram of the user plane architecture of the existing 5GVN service.
  • the terminal device establishes a session with the UPF that provides the 5GVN service, thereby accessing the UPF that provides the 5GVN service.
  • the UPF providing 5GVN service can communicate with the existing LAN in the data network (DN) through N6, for example, communicate with the personal computer (PC) in the LAN; or, the UPF providing 5GVN service
  • the UPF can also associate sessions of different terminal devices through the connection between the internal UPF and the UPF to implement private communication, which is not specifically limited in this embodiment of the present application.
  • the interface between the UPFs providing the 5GVN service is referred to as a next generation network (next generation, N) 19 interface (N19 for short).
  • N next generation network
  • the path between the UPFs providing the 5GVN service is called an N19 tunnel, which is described in a unified manner here, and will not be repeated below.
  • the interface between the UPFs providing the 5GVN service may also have other names, which are not specifically limited in this embodiment of the present application.
  • the N19 tunnel in the embodiment of the present application may be constructed in a general packet radio service (general packet radio service, GPRS) tunneling protocol user plane (GPRS tunneling protocol-user plane, GTP-U) manner.
  • the foregoing construction manner may be dynamic, or may be pre-configured in the network, which is not specifically limited in this embodiment of the present application.
  • the corresponding N19 tunnel information may be UPF ID, UPF ID+tunnel endpoint identifier (TEID), IP address+TEID, or IP address+ Port number (port)+TEID, etc., which are not specifically limited in this embodiment of the present application.
  • FIG. 6 is a schematic diagram of an existing user plane protocol stack based on N19 tunnel forwarding.
  • session 1 needs to be established for terminal device 1 and session 2 for terminal device 2.
  • the anchor UPF corresponding to session 1 is UPF1; the anchor UPF corresponding to session 2 is UPF2, then the subsequent terminal device 1 and terminal device 2 can perform data exchange through the N19 tunnel between UPF1 and UPF2.
  • the anchor UPF corresponding to session 1 is UPF1
  • the anchor UPF corresponding to session 2 is UPF2
  • the subsequent terminal device 1 and terminal device 2 can perform data exchange through the N19 tunnel between UPF1 and UPF2.
  • the 3GPP network protocol stack between the terminal device and the UPF includes a PDU session user plane protocol stack.
  • the 3GPP network protocol stack between UPF1 and UPF2 includes the PDU layer, the GTP-U layer and the lower protocol layers.
  • the lower protocol layers include the user datagram protocol (UDP) layer/IP layer, the second layer (level2 , L2) and L1.
  • UPF user datagram protocol
  • N19 tunnel in the embodiment of the present application is a tunnel between various UPFs in the 5GVN, which is uniformly described here, and will not be repeated below.
  • At least one item(s) below or similar expressions thereof refer to any combination of these items, including any combination of single item(s) or plural items(s).
  • at least one (a) of a, b, or c can represent: a, b, c, a-b, a-c, b-c, or a-b-c, where a, b, c may be single or multiple .
  • words such as "first” and "second” are used to distinguish the same or similar items with basically the same function and effect.
  • words “first”, “second” and the like do not limit the quantity and execution order, and the words “first”, “second” and the like are not necessarily different.
  • words such as “exemplary” or “for example” are used to represent examples, illustrations or illustrations. Any embodiments or designs described in the embodiments of the present application as “exemplary” or “such as” should not be construed as preferred or advantageous over other embodiments or designs. Rather, the use of words such as “exemplary” or “such as” is intended to present the related concepts in a specific manner to facilitate understanding.
  • the network architecture and service scenarios described in the embodiments of the present application are for the purpose of illustrating the technical solutions of the embodiments of the present application more clearly, and do not constitute limitations on the technical solutions provided by the embodiments of the present application.
  • the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.
  • a communication system 70 is provided in an embodiment of the present application.
  • the communication system 70 includes a session management functional entity 701 and a first user plane functional entity 702.
  • the communication system 70 further includes an application instance access module 703 .
  • the session management functional entity 701, the first user plane functional entity 702, or any two of the application instance access module 703 may communicate directly or communicate through forwarding by other devices. This embodiment of the present application does not Make specific restrictions.
  • the session management function entity 701 is configured to receive a first message from the application instance access module 703, where the first message includes identification information of the first application instance, and the first message is used to request to establish a first connection for the first application instance.
  • the session management functional entity 701 is further configured to send a second message to the first user plane functional entity 702 after determining the first user plane functional entity 702 serving the first application instance, where the second message includes the identifier of the first application instance information, the second message is used to request the establishment of the first connection for the first application instance.
  • the first user plane function entity 702 is configured to receive the second message from the session management function entity 701 and send a third message to the session management function entity 701, where the third message includes the establishment result of the first connection, wherein the establishment result includes success.
  • the session management functional entity 701 is configured to receive a third message from the first user plane functional entity 702, and send a fourth message to the application instance access module 703, where the fourth message includes the core network element allocated for the first connection 's first address.
  • the session management function entity and the first user plane function entity in the mobile communication network establish the first connection between the first application instance and the mobile communication network for the first application instance, and after establishing the first connection It can be known from the first address allocated by the core network element for the first connection during the connection process that the address allocation and management corresponding to the first application instance and the forwarding path of the data plane are all within the control range of the mobile communication network.
  • the first application instance can be accessed into the mobile communication network as a special terminal device. Since the first application instance is a specific running instance of an application, based on this solution, the flexibility of data interaction between the application and the mobile communication network can be improved. Further, based on this solution, the application can be incorporated into the mobile communication network planning to realize the plug-and-play of the application in the mobile communication system, so as to realize the dynamic arrangement and path optimization of the application service. This facilitates the realization of a new business deployment and cooperation model between operators and application service providers.
  • the application instance access module 703 is configured to assist the first application instance to access the mobile communication network.
  • the application instance access module 703 in this embodiment of the present application may be integrated in a first application instance, and the first application instance may run in an application server.
  • the application instance access module 703 in this embodiment of the present application may be deployed separately from the first application instance.
  • the application instance access module 703 may be integrated on an APP integration platform (eg, MEP in FIG. 3 ), and the first application instance may run in an application server.
  • the application server shown in FIG. 8 or FIG. 9 may also include other application instances, and the embodiment of the present application is only illustrative by taking the first application instance on the application server as an example for description. , there is no specific restriction on whether the application server runs other application instances.
  • FIG. 9 there may be multiple application servers interacting with the APP integration platform, which is not specifically limited in this embodiment of the present application.
  • the communication system 70 shown in FIG. 7 may be applied to a current 4G network, a 5G network, or other future networks, which is not specifically limited in this embodiment of the present application.
  • the network element or entity corresponding to the session management function entity 701 in the communication system 70 shown in FIG. is the SMF in the 5G network architecture; the network element or entity corresponding to the first user plane functional entity 702 in the communication system 70 shown in FIG. 7 may be the first anchor point UPF in the 5G network architecture.
  • the network element or entity corresponding to the application instance access module 703 in the communication system 70 shown in FIG. 7 may be, for example, an application as a user equipment function (APP as user equipment function, AUEF).
  • APP user equipment function
  • AUEF user equipment function
  • the AUEF may be deployed in the first application instance in the application server; or, as shown in FIG.
  • the AUEF may be deployed on the APP integration platform.
  • the AUEF may also have other deployment methods, such as being deployed on other existing functions or devices or platforms, or deployed on other newly added functions, devices or platforms, etc., which are not specifically limited in this embodiment of the present application.
  • the current 5G network can also include AMF, NEF, network exposure function repository function (NRF), unified data management (UDM), policy control function (policy control function) function, PCF) and other UPFs (such as the second anchor point UPF and the I-UPF corresponding to the terminal device in FIG. 10 ), which are not specifically limited in this embodiment of the present application.
  • AMF Access Management Function
  • NEF network exposure function repository function
  • UDM unified data management
  • policy control function policy control function
  • PCF policy control function
  • other UPFs such as the second anchor point UPF and the I-UPF corresponding to the terminal device in FIG. 10
  • the current 5G network may also include an authentication server function (authentication server function, AUSF), a network slice selection function (network slice selection function, NSSF), and the like.
  • authentication server function authentication server function
  • NSSF network slice selection function
  • the terminal device accesses the 5G network through the RAN device.
  • the terminal device communicates with the AMF through the N1 interface (N1 for short).
  • the RAN device communicates with the AMF through the N2 interface (N2 for short).
  • the RAN device communicates with the I-UPF through the N3 interface (N3 for short).
  • the I-UPF communicates with the second anchor point UPF through the N9 interface (N9 for short).
  • the second anchor point UPF communicates with the first anchor point UPF through an N19 interface (N19 for short).
  • the SMF network element communicates with the I-UPF, the second anchor point UPF and the first anchor point UPF respectively through the N4 interface (N4 for short).
  • the SMF network element communicates with the AUEF through the Nx interface (Nx for short).
  • the first anchor point UPF communicates with the AUEF through an Nd interface (Nd for short).
  • the control plane functions such as AMF, SMF, NEF, NRF, PCF, or UDM shown in FIG. 10 can also use service interfaces for interaction.
  • the service interface provided by AMF can be Namf; the service interface provided by SMF can be Nsmf; the service interface provided by NEF can be Nnef; the service interface provided by NRF can be Nnrf;
  • the service interface can be Npcf; the service interface provided by UDM externally can be Nudm.
  • the 5G system architecture diagram in the 23501 standard which will not be repeated here.
  • the terminal device in this embodiment of the present application may be a device for implementing wireless communication functions, such as a terminal or a chip that can be used in a terminal, etc., which may be deployed on land, including indoor or outdoor, Handheld or vehicle; can also be deployed on the water (such as ships, etc.); can also be deployed in the air (such as aircraft, balloons and satellites, etc.).
  • the terminal may be a UE, an access terminal, a terminal unit, a terminal station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile station in a 5G network or a public land mobile network (PLMN) evolved in the future. equipment, wireless communication equipment, terminal agent or terminal device, etc.
  • PLMN public land mobile network
  • the access terminal may be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a wireless communication Functional handheld devices, computing devices or other processing devices connected to wireless modems, in-vehicle devices or wearable devices, unmanned aerial vehicles (UAV) and UAV controllers (UAV controllers, UAVC), virtual reality ( virtual reality (VR) terminal equipment, augmented reality (AR) terminal equipment, wireless terminals in industrial control, wireless terminals in self-driving, remote medical (remote medical) Wireless terminal, wireless terminal in smart grid, wireless terminal in transportation safety, wireless terminal in smart city, wireless terminal in smart home, etc. Terminals can be mobile or stationary.
  • SIP session initiation protocol
  • WLL wireless local loop
  • PDA personal digital assistant
  • a wireless communication Functional handheld devices computing devices or other processing devices connected to wireless modems, in-vehicle devices or wearable devices, unmanned aerial vehicles (UAV) and UAV
  • the RAN device in this embodiment of the present application is a device that provides a wireless communication function for a terminal device.
  • Access network equipment includes, but is not limited to, next-generation base stations (gnodeB, gNB), evolved node B (evolved node B, eNB), radio network controller (radio network controller, RNC), node B (node B) in 5G.
  • B base station controller
  • BSC base transceiver station
  • BTS base transceiver station
  • home base station for example, home evolved nodeB, or home node B, HNB
  • baseband unit baseBand unit, BBU
  • transmission point transmitting and receiving point
  • TRP transmitting point
  • TP mobile switching center
  • the user plane network element, the access network equipment, the session management network element, the policy control network element, or the application function network element in the embodiment of the present application may also be referred to as a communication device or a communication device, which may be It is a general-purpose device or a special-purpose device, which is not specifically limited in this embodiment of the present application.
  • the session management functional entity, the first user plane functional entity, or the related functions of the application instance access module in the embodiment of the present application may be implemented by one device, or may be implemented jointly by multiple devices, or It may be implemented by one or more functional modules in a device, which is not specifically limited in this embodiment of the present application.
  • the above-mentioned functions can be either network elements in hardware devices, or software functions running on dedicated hardware, or a combination of hardware and software, or instantiated on a platform (eg, a cloud platform). Virtualization capabilities.
  • FIG. 11 is a schematic structural diagram of a communication apparatus 1100 according to an embodiment of the present application.
  • the communication device 1100 includes one or more processors 1101, a communication line 1102, and at least one communication interface (in FIG. 11, the communication interface 1104 and a processor 1101 are used as an example for illustration), a Possible implementations may also include memory 1103 .
  • the processor 1101 may be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more processors used to control the execution of the programs of the present application. integrated circuit.
  • CPU central processing unit
  • ASIC application-specific integrated circuit
  • the communication line 1102 may include a path for connecting the various components.
  • the communication interface 1104 can be a transceiver module for communicating with other devices or communication networks, such as Ethernet, RAN, wireless local area networks (wireless local area networks, WLAN) and the like.
  • the transceiver module may be a device such as a transceiver or a transceiver.
  • the communication interface 1104 may also be a transceiver circuit located in the processor 1101 to implement signal input and signal output of the processor.
  • the memory 1103 may be a device having a storage function. For example, it may be read-only memory (ROM) or other types of static storage devices that can store static information and instructions, random access memory (RAM) or other types of storage devices that can store information and instructions
  • the dynamic storage device can also be electrically erasable programmable read-only memory (electrically erasable programmable read-only memory, EEPROM), compact disc read-only memory (CD-ROM) or other optical disk storage, optical disk storage (including compact discs, laser discs, compact discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or capable of carrying or storing desired program code in the form of instructions or data structures and capable of being stored by a computer any other medium taken, but not limited to this.
  • the memory may exist independently and be connected to the processor through communication line 1102 .
  • the memory can also be integrated with the processor.
  • the memory 1103 is used for storing computer-executed instructions for executing the solution of the present application, and the execution is controlled by the processor 1101 .
  • the processor 1101 is configured to execute the computer-executed instructions stored in the memory 1103, so as to implement the method for an application to access a network provided in the embodiments of this application.
  • the processor 1101 may also perform functions related to processing in the method for accessing a network for an application provided by the following embodiments of the present application, and the communication interface 1104 is responsible for communicating with other devices or communication network communication, which is not specifically limited in this embodiment of the present application.
  • the computer-executed instructions in the embodiment of the present application may also be referred to as application code, which is not specifically limited in the embodiment of the present application.
  • the processor 1101 may include one or more CPUs, such as CPU0 and CPU1 in FIG. 11 .
  • the communication apparatus 1100 may include multiple processors, for example, the processor 1101 and the processor 1108 in FIG. 11 .
  • Each of these processors can be a single-core processor or a multi-core processor.
  • the processor here may include at least one of the following: a central processing unit (CPU), a microprocessor, a digital signal processor (DSP), a microcontroller (MCU), or an artificial intelligence processor, etc.
  • CPU central processing unit
  • DSP digital signal processor
  • MCU microcontroller
  • an artificial intelligence processor etc.
  • Various types of computing devices that run software, each computing device may include one or more cores for executing software instructions to perform operations or processing.
  • the communication apparatus 1100 may further include an output device 1105 and an input device 1106 .
  • the output device 1105 is in communication with the processor 1101 and can display information in a variety of ways.
  • the output device 1105 may be a liquid crystal display (LCD), a light emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector (projector) Wait.
  • the input device 1106 is in communication with the processor 1101 and can receive user input in a variety of ways.
  • the input device 1106 may be a mouse, a keyboard, a touch screen device, a sensor device, or the like.
  • the above-mentioned communication apparatus 1100 may also be sometimes referred to as a communication apparatus, which may be a general-purpose device or a dedicated device.
  • the communication device 1100 may be a desktop computer, a portable computer, a network server, a personal digital assistant (PDA), a mobile phone, a tablet computer, a wireless terminal device, an embedded device, the above-mentioned terminal device, the above-mentioned network device, or a 11 similarly constructed devices.
  • PDA personal digital assistant
  • This embodiment of the present application does not limit the type of the communication apparatus 1100 .
  • a method for an application access network includes the following steps:
  • the application instance access module determines a session management function entity serving the first application instance.
  • the application instance access module determines the session management function entity serving the first application instance, including: the application instance access module obtains from the network storage function entity one or more functions that support establishing a connection for the application instance. Information of the session management function entity; the application instance access module determines the session management function entity serving the first application instance according to the information of one or more session management function entities.
  • the application instance access module sends a first message to the session management function entity.
  • the session management function entity receives the first message from the application instance access module.
  • the first message includes identification information of the first application instance, and the first message is used to request to establish a first connection for the first application instance.
  • the "first connection" established for the first application instance refers to the connection between the first application instance and the mobile communication network established for the first application instance, which is used to treat the first application instance as a special
  • the terminal device is connected to the mobile communication network, so that the first application instance can subsequently perform data communication with other devices through the first connection.
  • the first connection here may be a packet data network (packet data network, PDN) connection in 4G or a PDU session in 5G, or may be other connections in other networks in the future. Repeat.
  • the identification information of the first application instance can uniquely determine the first application instance, and the identification information of the first application instance can be, for example, an APP instance permanent identifier (APP instance permanent identifier, AIPI) or an APP instance hidden identifier (APP instance concealed identifier, AICI), which is uniformly explained here, and will not be repeated below.
  • APP instance permanent identifier APP instance permanent identifier
  • AIPI APP instance hidden identifier
  • AICI APP instance concealed identifier
  • the first message may further include a first parameter and/or application information corresponding to the first application instance.
  • the first parameter includes at least one of the following parameters: location information (location information) of the first application instance, a session and service continuity (session and service continuity, SSC) mode, a first connection corresponding The data network name (DNN) or the identification information of the network slice where the first connection is located.
  • the identification information of the network slice where the first connection is located may be, for example, single network slice selection assistance information (S-NSSAI) of the network slice where the first connection is located.
  • the location information of the first application instance may be, for example, the home public land mobile network (HPLMN) subscribed by the first application instance; or, the location of the first application instance.
  • the information may be, for example, the area identifier of the tracking area served by the first application instance; or, alternatively, the location information of the first application instance may be, for example, the cell identifier of the cell served by the first application instance.
  • the application information corresponding to the first application instance includes: an application name, an application identifier, or application domain name information, and the like.
  • the session management function entity determines a first user plane function entity serving the first application instance.
  • the session management function entity may determine the first user plane function entity serving the first application instance according to the above-mentioned first parameter.
  • the session management function entity may determine the first user plane function entity serving the first application instance according to the location information of the first application instance in the first parameter and the S-NSSAI of the network slice where the first connection is located.
  • the session management functional entity may determine, among the user plane functional entities supporting the S-NSSAI of the network slice where the first connection is located, the user plane functional entity closest to the application server bearing the first application instance as the first user plane. functional entity.
  • the session management function entity may also acquire the subscription data of the first application instance from the unified data management function entity. Furthermore, the session management function entity may determine the first user plane function entity serving the first application instance according to the subscription data of the first application instance.
  • the subscription data of the first application instance includes: the allowed connection type, the location information of the first subscription application instance, the default quality of service (quality of service, QoS) parameter, the allowed SSC At least one of the mode, the subscribed DNN, or the identification information of the subscribed network slice.
  • the allowed connection type includes: the allowed connection type, the location information of the first subscription application instance, the default quality of service (quality of service, QoS) parameter, the allowed SSC At least one of the mode, the subscribed DNN, or the identification information of the subscribed network slice.
  • QoS quality of service
  • the session management function entity may determine the first user plane function entity serving the first application instance according to the location information of the contracted first application instance and the contracted DNN in the subscription data of the first application instance.
  • the session management function entity may determine the user plane function entity closest to the application server bearing the first application instance among the user plane function entities of the DNN supporting the first application instance subscription as the first user plane function entity.
  • the session management function entity obtains the subscription data of the first application instance from the unified data management function entity, which may include: the session management function entity sends a fifth message to the unified data management function entity, and the fifth message includes the first application The identification information of the instance, the fifth message is used to request to obtain the subscription data of the first application instance; the session management function entity receives the subscription data of the first application instance from the unified data management function entity.
  • the session management functional entity may further acquire the subscription data of the first application instance from the unified data management functional entity. Furthermore, the session management function entity may determine the first user plane function entity serving the first application instance according to the subscription data of the first application instance and the above-mentioned first parameter.
  • the session management function entity may determine the first user plane function entity serving the first application instance according to the location information of the first application instance in the first parameter and the DNN subscribed by the first application instance in the subscription data of the first application instance .
  • the session management function entity may determine the user plane function entity closest to the application server bearing the first application instance among the user plane function entities of the DNN supporting the first application instance subscription as the first user plane function entity.
  • the session management function entity may also determine the first user plane functional entity serving the first application instance in other ways, which is not specifically limited in this embodiment of the present application.
  • the session management function entity may further allocate a first address for the first connection.
  • the first address is used for data communication between the terminal device and the first application instance.
  • the terminal device may access the first application instance through the first address.
  • the first address in this embodiment of the present application may include, for example, an IP address (IP address), an IPv6 prefix (IPv6 Prefix), or a media access control (media access control, MAC) address, etc. Repeat.
  • IP address IP address
  • IPv6 Prefix IPv6 Prefix
  • media access control media access control
  • the session management function entity sends a second message to the first user plane function entity.
  • the first user plane functional entity receives the second message from the session management functional entity.
  • the second message includes identification information of the first application instance, and the second message is used to request to establish a first connection for the first application instance.
  • the second message may further include the first address.
  • the first address is used for the first user plane functional entity to advertise routes (route advertisement).
  • routes advertisement routes advertisement
  • other entities or modules can be directly addressed to the first user plane function entity according to the route published by the first user plane function entity.
  • the method for accessing a network by an application provided by the embodiment of the present application may further include: the first user plane function entity receives the second data from the second user plane function entity, and sends the first application instance to the first application instance through the application instance access module. Send the second data.
  • the second user plane functional entity is addressed to the second user plane functional entity according to the route advertised by the first user plane functional entity.
  • the related addressing mode may refer to the prior art, which will not be repeated here.
  • the first address may also be allocated by the first user plane functional entity. That is, the first user plane functional entity may allocate the first address for the first connection.
  • the first user plane function entity sends a third message to the session management function entity.
  • the session management function entity receives the third message from the first user plane function entity.
  • the third message includes the establishment result of the first connection, wherein the establishment result includes success or failure.
  • the third message further includes the first address.
  • the session management function entity sends a fourth message to the application instance access module.
  • the application instance access module receives the fourth message from the session management function entity.
  • the fourth message includes the first address allocated by the above-mentioned session management functional entity for the first connection, or includes the first address allocated by the above-mentioned first user plane functional entity for the first connection.
  • the application instance access module may advertise a route according to the first address.
  • other entities or modules can be directly addressed to the application instance access module according to the route published by the application instance access module.
  • the method for accessing a network by an application may further include: the application instance access module receives second data from a second user plane function entity, where the second user plane function entity is accessed according to the application instance
  • the route advertised by the module is addressed to the access module of the application instance.
  • the related addressing mode may refer to the prior art, which will not be repeated here.
  • the first message and the second message may further include first path information allocated by the application instance access module for the first connection.
  • the third message and the fourth message may further include second path information allocated by the first user plane functional entity for the first connection.
  • the first path information and the second path information are used to establish a first path between the first user plane functional entity and the application instance access module in the first connection, and the first path is used for the first user plane functional entity and the application instance access module. Data transfer between application instance access modules.
  • the application instance access module After obtaining the first data from the first application instance, the application instance access module sends the first data to the first user plane functional entity through the first path; or, the application instance access module receives data from the first user through the first path The second data of the face functional entity.
  • the "path" in the embodiment of the present application may also be called a tunnel or another name, which is not specifically limited in the embodiment of the present application.
  • the above-mentioned first path information may be replaced by first tunnel information
  • the above-mentioned second path information may be replaced by second tunnel information, and so on, which will not be repeated here.
  • the first path between the first user plane functional entity and the application instance access module may include, for example, a GTP-U tunnel, a generic routing encapsulation (GRE) tunnel, or an IP tunnel. Tunnels, etc., are not specifically limited in this embodiment of the present application.
  • the first path information and the second path information may be different.
  • the first path information may be the address of the access module of the application instance, and the second path information may be the address of the first user plane functional entity; or, the first path The information may be the endpoint identifier of the first path on the application instance access module side and the address of the application instance access module, and the second path information may be the endpoint identifier of the first path on the first user plane functional entity side and the address of the application instance access module.
  • the first path information may be the endpoint identifier of the first path on the application instance access module side, the address and port number of the application instance access module, and the second path The information may be an endpoint identifier of the first path on the side of the first user plane functional entity, an address of the first user plane functional entity, and a port number (port).
  • the first path information may be the address of the access module of the application instance, and the second path information may be the address of the first user plane functional entity; or, the first path information may be is the endpoint identifier of the first path on the application instance access module side and the address of the application instance access module, and the second path information can be the endpoint identifier of the first path on the first user plane functional entity side and the first path information
  • the address of the user plane functional entity; or, the first path information may be the endpoint identifier of the first path on the application instance access module side, the address and key of the application instance access module, and the second path information may be are the endpoint identifier of the first path on the side of the first user plane function entity, the address and key of the first user plane function entity.
  • the first path information may be the address of the access module of the application instance, and the second path information may be the address of the first user plane functional entity; or, the first path information may be is the address and port number (port) of the access module of the application instance, and the second path information may be the address and port number (port) of the first user plane functional entity.
  • the endpoint identifier in the embodiment of the present application may be, for example, a fully qualified tunnel endpoint identifier (FTEID), which is uniformly described here, and will not be repeated below.
  • FTEID fully qualified tunnel endpoint identifier
  • the session management function entity may also use the first parameter, the application information corresponding to the first application instance, or the subscription data of the first application instance. At least one constructs a virtual local area network including a first user plane functional entity.
  • the session management function entity can, according to the application information corresponding to the first application instance, A virtual local area network is constructed together with the first user plane functional entity serving the first application instance and the user plane functional entity serving the terminal equipment that subscribes to or subscribed to the service corresponding to the first application instance; alternatively, the session management functional entity may According to the application information corresponding to the first application instance and the S-NSSAI of the network slice where the first connection is located in the first parameter, the first user plane function entity serving the first application instance and the In the user plane function entity of the terminal device service of the service corresponding to the application instance, the user plane function entity of the S-NSSAI supporting the network slice where the first connection is located together builds a virtual local area network; or, the session management function entity can be based on the first connection.
  • the application information corresponding to the application instance, and the DNN subscribed by the first application instance in the subscription data of the first application instance, will correspond to the first user plane function entity serving the first application instance and the first application instance subscribed to or subscribed to.
  • a virtual local area network is constructed together with the user plane functional entities of the DNN that support the subscription of the first application instance.
  • the method of constructing a virtual network is similar to the existing method of constructing a 5GVN, and the difference is, for example, in the embodiment of the present application, when constructing a virtual local area network, the first application instance can be regarded as A special type of terminal equipment constructs a virtual local area network together with other common terminal equipment.
  • the same virtual local area network address needs to be allocated for the first connection and the second connection.
  • the first application instance is deployed in a certain area, and the goal is to provide services for terminal devices that have subscribed to the corresponding service in the area. Then, in the process of establishing the first connection for the first application instance and the process of establishing the second connection for the terminal device, it is necessary to allocate the same virtual local area network address for the first connection and the second connection.
  • the method for an application accessing a network may further include: the session management function entity registers with the network storage function entity that the session management function entity supports the function of establishing a connection for the application instance. Based on this solution, when a session management function entity is subsequently selected, a session management function entity that supports establishing a connection for an application instance can be obtained from the network storage function entity.
  • the method for an application accessing a network may further include: the first user plane function entity registers with the network storage function entity that the first user plane function entity supports the function of establishing a connection for the application instance. . Based on this solution, when the user plane functional entity is subsequently selected, the user plane functional entity that supports establishing a connection for the application instance can be obtained from the network storage functional entity.
  • the method for application access network provided by this embodiment of the present application may further include: application instance access.
  • the access module receives the sixth message from the first application instance, where the sixth message includes application information corresponding to the first application instance and is used to request registration; the application instance access module receives the fourth message from the session management function entity ( After step S1206), the method for an application accessing a network provided by the embodiment of the present application may further include: the application instance access module sends the first address to the first application instance. This solution is suitable for a scenario where the application instance access module is deployed separately from the first application instance.
  • each connection has a corresponding path and path information, which are described here uniformly, and will not be repeated below.
  • the session management function entity and the first user plane function entity in the mobile communication network establish the first connection between the first application instance and the mobile communication network for the first application instance, and after establishing the first connection It can be known from the first address allocated by the core network element for the first connection during the connection process that the address allocation and management corresponding to the first application instance and the forwarding path of the data plane are all within the control range of the mobile communication network. That is to say, in this solution, the first application instance can be accessed into the mobile communication network as a special terminal device. Since the first application instance is a specific running instance of an application, based on this solution, the flexibility of data interaction between the application and the mobile communication network can be improved.
  • the application can be incorporated into the mobile communication network planning to realize the plug-and-play of the application in the mobile communication system, so as to realize the dynamic arrangement and path optimization of the application service. This facilitates the realization of a new business deployment and cooperation model between operators and application service providers.
  • the actions of the session management functional entity, the application instance access module or the first user plane functional entity in the above steps S1201 to S1206 may be invoked by the processor 1101 in the communication device 1100 shown in FIG. 11 to the application program stored in the memory 1103
  • the code is executed by instructing the session management function entity, the application instance access module, or the first user plane function entity, which is not limited in this embodiment.
  • FIG. 13 shows an application provided by the embodiment of the present application method of accessing the network.
  • the AUEF is provided by the first APP instance in the application server (that is, the AUEF can be regarded as a functional module in the first APP instance), and the SMF/UPF supports the first APP instance as a special terminal device
  • Direct access to the 5G network supports functions such as allocating addresses and establishing paths for the session established by the first APP instance (for convenience of description, the session established by the first APP instance will be referred to as the session of the first APP instance in the following).
  • a possible implementation manner of the method for accessing a network by an application includes the following steps S1300-S1302:
  • the SMF registers with the NRF whether the SMF supports establishing a PDU session for the APP instance.
  • the SMF may register to the NRF whether it supports the NRF through the Nnrf_network function (network function, NF) management (Management)_NF registration (Register) or the Nnrf_NFManagement_NF update (Update) service operation (service operation).
  • Nnrf_network function network function, NF) management (Management)_NF registration (Register) or the Nnrf_NFManagement_NF update (Update) service operation (service operation).
  • the input parameters of the Nnrf_NFManagement_NFRegister or Nnrf_NFManagement_NFUpdate service operation at least include indication information of whether the SMF supports establishing a PDU session for the APP instance.
  • the input parameters of the Nnrf_NFManagement_NFRegister or Nnrf_NFManagement_NFUpdate service operations may also include other parameters, and details may refer to the existing 3GPP standards, which will not be repeated here.
  • the SMF that supports establishing a PDU session for an APP instance may also be referred to as an APP session management function (APP Session Management Function, ASMF).
  • ASMF APP Session Management Function
  • ASMF APP Session Management Function
  • ASMF can register itself with NRF through Nnrf_NFManagement_NFRegister or Nnrf_NFManagement_NFUpdate service operations to support the establishment of PDU sessions for APP instances.
  • the input parameters of the Nnrf_NFManagement_NFRegister or Nnrf_NFManagement_NFUpdate service operation at least include indication information that ASMF supports establishing a PDU session for the APP instance, which is not specifically limited in this embodiment of the present application.
  • the first anchor point UPF registers with the NRF whether the first anchor point UPF supports establishing a PDU session for the APP instance.
  • the first anchor UPF may register with the NRF whether it supports establishing a PDU session for the APP instance through the Nnrf_NFManagement_NFRegister or Nnrf_NFManagement_NFUpdate service operation.
  • the input parameters of the Nnrf_NFManagement_NFRegister or Nnrf_NFManagement_NFUpdate service operation at least include indication information of whether the first anchor point UPF supports establishing a PDU session for the APP instance.
  • the input parameters of the Nnrf_NFManagement_NFRegister or Nnrf_NFManagement_NFUpdate service operations may also include other parameters, and details may refer to the existing 3GPP standards, which will not be repeated here.
  • the first anchor point UPF that supports establishing a PDU session for an APP instance may also be referred to as the first anchor point APP user plane function (APP user plane function, AUPF).
  • APP user plane function APP user plane function
  • AUPF APP user plane function
  • the first anchor point AUPF may register itself with the NRF to support establishing a PDU session for the APP instance through the Nnrf_NFManagement_NFRegister or Nnrf_NFManagement_NFUpdate service operation.
  • the input parameters of the Nnrf_NFManagement_NFRegister or Nnrf_NFManagement_NFUpdate service operation include at least the indication information that the first anchor AUPF supports establishing a PDU session for the APP instance, which is not specifically limited in this embodiment of the present application.
  • the application server where the first APP instance is located obtains information from the NRF of one or more SMFs that support establishing a PDU session for the APP instance.
  • the information of the SMF includes the identification information of the SMF.
  • the identification information of the SMF may be, for example, the IP address of the SMF, or the fully qualified domain name (FQDN) of the SMF, etc., which is not specifically limited in the embodiment of the present application.
  • the information of the SMF may further include attribute information of the SMF, such as load information, etc., which is not specifically limited in the embodiment of the present application.
  • the application server where the first APP instance is located may query the NRF for information about the SMF that supports establishing a PDU session for the APP instance through the Nnrf_NF discovery request (Discovery_Request) service operation.
  • the input parameters of the Nnrf_NFDiscovery_Request service operation include the functional requirements for supporting the establishment of PDU sessions for the APP instance
  • the output parameters of the Nnrf_NFDiscovery_Request service operation include information of one or more SMFs that support the establishment of PDU sessions for the APP instance.
  • the application server where the first APP instance is located may subscribe to the NRF for information of the SMF that supports establishing a PDU session for the APP instance through the Nnrf_NFManagement_NF status subscription (StatusSubscribe) service operation.
  • the input parameters of the Nnrf_NFManagement_StatusSubscribe service operation include the functional requirements for supporting the establishment of a PDU session for the APP instance.
  • the NRF may return the information of one or more SMFs supporting the establishment of a PDU session for the APP instance to the APP instance through the Nnrf_NFManagement_StatusNotify service operation.
  • the application server where the first APP instance is located can also be configured to support The SMF for establishing a PDU session for an APP instance, for example, the application server may determine a certain SMF as an SMF that supports establishing a PDU session for an APP instance, which is not specifically limited in this embodiment of the present application.
  • the above step S1302 may not be performed, but the application server where the first APP instance is located directly configures an SMF that supports establishing a PDU session for the APP instance.
  • the SMF is determined to be an SMF that supports establishing a PDU session for an APP instance, which is not specifically limited in this embodiment of the present application.
  • the application server where the first APP instance is located may initiate a session establishment process, including the following step S1303:
  • the application server where the first APP instance is located sends an Nsmf_PDU session creation (PDU session create) request to the selected SMF that supports establishing a PDU session for the APP instance. Accordingly, the SMF receives the Nsmf_PDU session creation request from the application server.
  • the Nsmf_PDU session creation request includes identification information of the first APP instance, and is used for requesting to establish a PDU session for the first APP instance.
  • Nsmf_PDU session creation request in the embodiment of the present application is only an example of the first message in FIG. 12 , and the first message may also be other, which is not specifically limited in the embodiment of the present application.
  • the embodiment of the present application exemplarily takes the SMF in step S1300 as the selected SMF to support establishing a PDU session for the APP instance as an example for description, which is uniformly described here and will not be repeated below.
  • the application server may determine the SMF according to the attribute information (such as load information) of the SMF.
  • the SMF served by the first APP instance may also be randomly selected as the SMF served by the first APP instance, which is not specifically limited in this embodiment of the present application.
  • the Nsmf_PDU session creation request in the embodiment of the present application may further include application information corresponding to the first APP instance, and the application information may uniquely determine an APP.
  • the application information may be, for example, an APP name, an APP ID, or an APP domain name information, etc., which are described here in a unified manner, and will not be repeated below.
  • the Nsmf_PDU session creation request in this embodiment of the present application may further include first path information, where the first path information is used to establish a path between the first anchor point UPF and the AUEF, the first anchor point
  • the UPF is the anchor UPF serving the first APP instance.
  • first path information reference may be made to the embodiment shown in FIG. 12 , which will not be repeated here.
  • the Nsmf_PDU session creation request in this embodiment of the present application may further include a first parameter, and the related description of the first parameter can refer to the embodiment shown in FIG. 12 , which is not repeated here.
  • the method for application access network may further include the following steps S1304-S1305:
  • the SMF sends a subscription data management (subscriber data management, SDM)_get request (Get Request) to the UDM.
  • SDM subscriber data management
  • the UDM receives the SDM_GET request from the SMF.
  • the SDM_acquisition request includes identification information of the first APP instance, and is used to request subscription data of the first APP instance.
  • the SDM_acquisition request of the SMF in the embodiment of the present application is only an example of the fifth message in FIG. 12 , and the fifth message may also be other, which is not specifically limited in the embodiment of the present application.
  • the SDM_acquisition request may also include application information corresponding to the first APP instance, which is the same as the first APP instance.
  • Application information corresponding to an APP instance is used to construct a virtual local area network including a first anchor point UPF, where the first anchor point UPF is an anchor point UPF serving the first APP instance.
  • the SDM_acquisition request may further include the first parameter, and the first parameter is used to construct a virtual network including the first anchor UPF. local area network.
  • the UDM sends an SDM_Get Response (Get Response) to the SMF. Accordingly, the SMF receives the SDM_Get Response from the UDM.
  • the SDM_Acquire response includes subscription data for the first APP instance.
  • the default QoS parameters in the subscription data of the first APP instance may include, for example, a 5G QoS identifier (5G QoS identifier, 5QI) or an allocation and retention priority (allocation and retention priority, ARP), etc.
  • 5G QoS identifier 5QI
  • ARP allocation and retention priority
  • the method for application access network may further include the following steps S1306-S1309:
  • the SMF determines the anchor UPF serving the first APP instance.
  • the embodiment of the present application exemplarily takes the first anchor point UPF in step S1301 as the anchor point UPF selected to serve the first APP instance as an example for description. Repeat.
  • the SMF may query the NRF for information about the UPF that supports establishing a PDU session for the APP instance. Specifically, the SMF sends a query request to the NRF, where the query request includes the location information of the first APP instance obtained through step S1303 or the location information of the first APP instance obtained through step S1305. In turn, the NRF sends information to the SMF of one or more UPFs supporting the establishment of a PDU session for the APP instance.
  • the information of the UPF includes the identification information of the UPF.
  • the identification information of the UPF may be, for example, the IP address of the UPF, which is not specifically limited in this embodiment of the present application.
  • the information of the UPF may further include location information of the UPF or attribute information of the UPF (such as load information), etc., which is not specifically limited in the embodiment of the present application.
  • the SMF may, according to the location information of the UPF and the attribute information of the UPF, pass steps S1303 and S1303 and /or at least one of the location information, SSC mode, DNN, and network slice identification information of the first APP instance obtained in step S1305 is determined as the anchor UPF serving the first APP instance.
  • the anchor UPF serving the first APP instance For details, refer to the existing SMF and select as The manner of the UPF served by the terminal device will not be repeated here.
  • the SMF can also configure a UPF that supports the establishment of a PDU session for an APP instance.
  • the UPF is determined to be a UPF that supports establishing a PDU session for an APP instance, which is not specifically limited in this embodiment of the present application.
  • the SMF sends an N4 session establishment request (N4 session establishment request) to the selected first anchor point UPF.
  • the first anchor point UPF receives the N4 session establishment request from the SMF.
  • the N4 session establishment request includes identification information of the first APP instance, and is used to request to establish a PDU session for the first APP instance.
  • N4 session establishment request in the embodiment of the present application is only an example of the second message in FIG. 12 , and the second message may also be other, which is not specifically limited in the embodiment of the present application.
  • the N4 session establishment request further includes the first path information.
  • the N4 session establishment request may also include QoS policy information determined according to the QoS parameter, and the QoS policy information It is used when the first anchor point UPF sends data subsequently, which is not specifically limited in this embodiment of the present application.
  • the first anchor point UPF sends an N4 session establishment response (N4 session establishment response) to the SMF.
  • the SMF receives the N4 session establishment response from the first anchor point UPF.
  • the N4 session establishment response includes a session establishment result, and the session establishment result may be, for example, success or failure.
  • N4 session establishment response in the embodiment of the present application is only an example of the third message in FIG. 12 , and the third message may also be other, which is not specifically limited in the embodiment of the present application.
  • the first anchor point UPF may allocate second path information, where the second path information is used to establish a path between the first anchor point UPF and the AUEF.
  • the N4 session establishment response may include the second path information.
  • the second path information For the related description of the second path information, reference may be made to the embodiment shown in FIG. 12 , which will not be repeated here.
  • the first anchor point UPF in the embodiment of the present application may also support functions such as routing policy publishing and forwarding path selection for the first APP instance in the 5G network, which is not done in the embodiment of the present application. Specific restrictions.
  • the SMF or the first anchor point UPF may further allocate the first address for the session of the first APP instance.
  • the SMF or the first anchor point UPF may further allocate the first address for the session of the first APP instance.
  • the SMF or the first anchor point UPF may further allocate the first address for the session of the first APP instance.
  • the SMF After the SMF determines that the session is successfully established, the SMF sends an Nsmf_PDU session create (PDU session create) response to the application server where the first APP instance is located.
  • the application server where the first APP instance is located receives the Nsmf_PDU session creation response from the SMF.
  • the Nsmf_PDU session creation response includes the session identifier allocated by the SMF for the first APP instance and the first address allocated by the SMF or the first anchor UPF for the session of the first APP instance.
  • Nsmf_PDU session creation response in the embodiment of the present application is only an example of the fourth message in FIG. 12 , and the fourth message may also be other, which is not specifically limited in the embodiment of the present application.
  • the Nsmf_PDU session establishment response may further include the second path information.
  • the application server where the first APP instance is located may also publish a route according to the first address allocated by the SMF or the first anchor UPF for the session of the first APP instance, this embodiment of the present application. There is no specific limitation on this.
  • the above steps S1303-S1309 show the session establishment process of the first APP instance in the 5G network.
  • the session update process of the first APP instance in the 5G network can also be completed by extending the Nsmf_PDU session_update (Update) service or a new service type;
  • the session release process of the first APP instance in the 5G network can also be completed by extending the Nsmf_PDU session_release (Release) service or a new service type, which is not repeated in this embodiment of the present application.
  • the terminal device initiates a session establishment process
  • the related implementation may refer to the prior art, which will not be repeated here.
  • description is made by taking an example that the anchor UPF serving the terminal device is the second anchor UPF.
  • the UDM in the process of establishing a session between the first APP instance and the terminal device, since the first APP instance can be regarded as a special terminal device, the UDM can Or the properties of the terminal device to construct the function of the virtual local area network.
  • the UDM can dynamically construct a virtual local area network according to at least one of the first parameter, the application information corresponding to the first APP instance, or the subscription data of the first APP instance; or, the UDM can dynamically construct a virtual local area network according to the first APP instance and the terminal in the UDM
  • the virtual network identifier preset in the subscription data of the device constructs a virtual local area network.
  • a virtual local area network For a specific way of constructing a virtual local area network, reference may be made to the embodiment shown in FIG. 12 , which will not be repeated here. It should be noted that the above-mentioned method of constructing a virtual local area network by the UDM based on the attributes of the first APP instance or the terminal device is only a possible implementation. In the embodiment of the present application, a session is established between the first APP instance and the terminal device. During the process, other network functions or network entities may also implement the selection of the virtual local area network based on related attributes, which is not specifically limited in this embodiment of the present application.
  • the SMF can use the 5G network to assign the address and
  • the N19 tunnel information is added to the forwarding policy set of the same virtual local area network, and delivered to all terminal devices under the virtual local area network and the UPF corresponding to the first APP instance to implement routing query and forwarding processing at the virtual local area network level.
  • This embodiment of the present application does not specifically limit this.
  • a self-organizing network that can implement plug-and-play application services can be formed between the terminal device and the APP instance, so that the terminal device and the APP instance can be formed.
  • the method for the application to access the network includes the following steps:
  • the terminal device sends the second data to the second anchor point UPF.
  • the second anchor point UPF receives the second data from the terminal device.
  • the second data includes a source address and a destination address, the source address is the second address allocated by the core network for the session of the terminal device in the process of establishing a session for the terminal device, and the destination address is the process of establishing a session for the first APP instance.
  • the terminal device may send the second data to the second anchor point UPF through the I-UPF, or may directly send the second data to the second anchor point UPF, which is not performed in this embodiment of the present application. Specific restrictions.
  • the second anchor point UPF determines, according to the destination address, the first anchor point UPF serving the first APP instance.
  • the second anchor point UPF may query whether the destination address belongs to the address range allocated by the virtual local area network where the terminal device is located. When the destination address belongs to the address range allocated by the virtual local area network where the terminal device is located, the second anchor point UPF may further determine the first anchor point UPF serving the first APP instance according to the destination address.
  • the second anchor point UPF sends the second data to the first anchor point UPF through the N19 tunnel between the first anchor point UPF and the second anchor point UPF.
  • the first anchor point UPF receives the second data from the second anchor point UPF.
  • the second anchor point UPF when the second anchor point UPF sends the second data to the first anchor point UPF through the N19 tunnel between the first anchor point UPF and the second anchor point UPF, the corresponding N19 tunnel information may be used to pair The second data is encapsulated.
  • the first anchor point UPF sends the second data to the application server where the first APP instance is located.
  • the application server where the first APP instance is located receives the second data from the first anchor point UPF.
  • the first anchor point UPF when the first anchor point UPF sends the second data to the application server where the first APP instance integrating AUEF is located through the path between the first anchor point UPF and the AUEF, the above-mentioned first path information may be used. and the second path information to encapsulate the second data.
  • the existing data transmission mode which will not be repeated here.
  • the above steps S1311-S1314 are described by taking as an example that a virtual local area network can be constructed for the first APP instance and the terminal device.
  • the second data may not be transmitted through the N19 tunnel between the first anchor point UPF and the second anchor point UPF.
  • the application server where the first APP instance is located advertises a route according to the first address allocated by the SMF or the first anchor UPF for the session of the first APP instance
  • the embodiment of the present application after receiving the second data, the second anchor point UPF can directly address the application server according to the first address published by the application server where the first APP instance is located according to the existing routing mode, and then the second anchor point UPF can directly address the application server to the application server.
  • the application server forwards the second data, which is not specifically limited in this embodiment of the present application.
  • the first anchor UPF supports the publishing of the routing policy for the first APP instance in the 5G network
  • the second anchor point UPF After the second anchor point UPF receives the second data, it can directly address the first anchor point UPF according to the routing policy advertised by the first anchor point UPF according to the existing routing mode, and then the second anchor point UPF can directly address the first anchor point UPF to the first anchor point.
  • the UPF sends the second data, and the first anchor UPF sends the second data to the application server where the first APP instance is located after receiving the second data, which is not specifically limited in this embodiment of the present application.
  • the method for the application to access the network includes the following steps:
  • the application server where the first APP instance is located sends the first data to the first anchor point UPF.
  • the first anchor point UPF receives the first data from the application server where the first APP instance is located.
  • the first data includes a source address and a destination address, the source address is the first address allocated by the core network for the session of the first APP instance in the process of establishing a session for the first APP instance, and the destination address is the process of establishing a session for the terminal device
  • the application server where the first APP instance integrating AUEF is located sends the first data to the first anchor point UPF through the path between the first anchor point UPF and the AUEF
  • the above-mentioned first path information may be used.
  • the second path information to encapsulate the first data for details, reference may be made to the existing data transmission mode, which will not be repeated here.
  • the first anchor point UPF determines, according to the destination address, the second anchor point UPF serving the terminal device.
  • the first anchor point UPF may query whether the destination address belongs to the address range allocated by the virtual local area network where the first APP instance is located.
  • the first anchor point UPF may further determine the second anchor point UPF serving the terminal device according to the destination address.
  • the first anchor point UPF sends the first data to the second anchor point UPF through the N19 tunnel between the first anchor point UPF and the second anchor point UPF.
  • the second anchor point UPF receives the first data from the first anchor point UPF.
  • the corresponding N19 tunnel information may be used to pair the The first data is encapsulated, and for details, reference may be made to the existing data transmission mode of the N19 tunnel, which will not be repeated here.
  • the second anchor point UPF sends the first data to the terminal device.
  • the terminal device receives the first data from the second anchor point UPF.
  • the second anchor UPF may send the first data to the terminal device through the I-UPF, or may directly send the first data to the terminal device, which is not specifically limited in this embodiment of the present application.
  • the above steps S1315-S1318 are described by taking as an example that a virtual local area network can be constructed for the first APP instance and the terminal device.
  • the first data may not be transmitted through the N19 tunnel between the first anchor point UPF and the second anchor point UPF.
  • the second anchor point UPF advertises a route according to the second address allocated by the SMF or the second anchor point UPF for the session of the terminal device, then in this embodiment of the present application, the first APP instance is located
  • the application server can directly address the second anchor point UPF according to the second address published by the second anchor point UPF according to the existing routing mode, and then the second anchor point UPF can forward the first data to the terminal device.
  • This embodiment of the application There is no specific limitation on this.
  • the SMF and the first anchor UPF in the mobile communication network establish a session for the first APP instance, and in the process of establishing the session, the first address is allocated to the session of the first APP instance.
  • the address allocation and management corresponding to the application instance, and the forwarding path of the data plane are all within the control range of the mobile communication network. That is to say, in this solution, the first APP instance can be connected to the 5G network as a special terminal device. Since the first APP instance is a specific running instance of an application, based on this solution, the flexibility of data interaction between the application and the mobile communication network can be improved.
  • the application can be incorporated into the mobile communication network planning to realize the plug-and-play of the application in the mobile communication system, so as to realize the dynamic arrangement and path optimization of the application service. This facilitates the realization of a new business deployment and cooperation model between operators and application service providers.
  • the actions of the SMF, the application server or the first anchor point UPF in the above steps S1300 to S1318 can be performed by the processor 1101 in the communication device 1100 shown in FIG. 11 calling the application program code stored in the memory 1103 to instruct the SMF, the application server Or the first anchor point UPF is executed, which is not limited in this embodiment.
  • FIG. 14 shows another application connection provided by the embodiment of the present application.
  • method of accessing the network In the method for accessing a network by an application, based on the basic process of the embodiment shown in FIG. 13 , in order to avoid a large amount of adaptation work for independently developing AUEF for the first APP instance, the AUEF can be deployed separately from the first APP instance (such as FIG. 6 exemplarily takes the unified AUEF provided by the APP integration platform as an example for illustration).
  • SMF/UPF supports the first APP instance to be directly connected to the 5G network as a special terminal device through AUEF.
  • the session established by the first APP instance (for convenience of description, the session established by the first APP instance will be referred to as the session of the first APP instance hereinafter) allocates functions such as address and path establishment.
  • a possible implementation manner of the method for accessing a network by an application includes the following steps S1400-S1402:
  • the SMF registers with the NRF whether the SMF supports establishing a PDU session for the APP instance.
  • step S1400 For the specific implementation of step S1400, reference may be made to step S1300 in the embodiment shown in FIG. 13 , which will not be repeated here.
  • the first anchor point UPF registers with the NRF whether the first anchor point UPF supports establishing a PDU session for the APP instance.
  • step S1401 For the specific implementation of step S1401, reference may be made to step S1301 in the embodiment shown in FIG. 13, and details are not repeated here.
  • the APP integration platform where the AUEF is located obtains information from the NRF of one or more SMFs that support establishing a PDU session for the APP instance.
  • step S1402 the APP integration platform where the AUEF is located obtains from the NRF the information of one or more SMFs that support the establishment of a PDU session for the APP instance, reference may be made to the application where the first APP instance is located in step S1302 in the embodiment shown in FIG. 13
  • the server obtains the information of one or more SMFs that support the establishment of PDU sessions for the APP instance from the NRF, the difference is, for example, that the application server where the first APP instance in step S1302 is located is replaced by the APP integration platform where the AUEF in step S1402 is located. , and will not be repeated here.
  • the application server where the first APP instance is located may initiate a session establishment process, including the following steps S1403-S1404:
  • the application server where the first APP instance is located sends an APP registration request (APP register request) to the APP integration platform where the AUEF is located.
  • the APP integration platform where the AUEF is located receives the APP registration request from the application server where the first APP instance is located.
  • the APP registration request includes application information corresponding to the first APP instance. For the relevant description of the application information, reference may be made to the embodiment shown in FIG. 13 , which will not be repeated here.
  • the AUEF of the APP integration platform After the AUEF of the APP integration platform allocates the identification information of the first APP instance to the first APP instance, it sends an Nsmf_PDU session creation (PDU session create) request to the selected SMF that supports establishing a PDU session for the APP instance.
  • the SMF receives the Nsmf_PDU session creation request from the APP integration platform where the AUEF is located.
  • the Nsmf_PDU session creation request includes identification information of the first APP instance, and is used for requesting to establish a PDU session for the first APP instance.
  • the embodiment of the present application exemplarily takes the SMF in step S1400 as the selected SMF to support establishing a PDU session for the APP instance as an example for description, which is uniformly described here and will not be repeated below.
  • the APP integration platform where the AUEF is located can be based on the attribute information of the SMF.
  • the SMF that is determined to serve the first APP instance (such as load information) may also be randomly selected to serve the SMF of the first APP instance, which is not specifically limited in this embodiment of the present application.
  • the Nsmf_PDU session creation request in this embodiment of the present application may further include application information corresponding to the first APP instance.
  • application information corresponding to the first APP instance.
  • the Nsmf_PDU session creation request in this embodiment of the present application may further include first path information, where the first path information is used to establish a path between the first anchor point UPF and the AUEF, the first anchor point
  • the UPF is the anchor UPF serving the first APP instance.
  • first path information reference may be made to the embodiment shown in FIG. 12 , which will not be repeated here.
  • the Nsmf_PDU session creation request in this embodiment of the present application may further include a first parameter, and the related description of the first parameter can refer to the embodiment shown in FIG. 12 , which is not repeated here.
  • S1405-S1409 are the same as steps S1304-S1309 in the embodiment shown in FIG. 5, and are not repeated here.
  • the SMF After the SMF determines that the session is established successfully, the SMF sends an Nsmf_PDU session create (PDU session create) response to the APP integration platform where the AUEF is located.
  • the APP integration platform where the AUEF is located receives the Nsmf_PDU session creation response from the SMF.
  • the Nsmf_PDU session creation response includes the session identifier allocated by the SMF for the first APP instance and the first address allocated by the SMF or the first anchor UPF for the session of the first APP instance.
  • the Nsmf_PDU session establishment response may further include the second path information.
  • the APP integration platform where the AUEF is located sends an APP registration response (APP register response) to the application server where the first APP instance is located.
  • the application server where the first APP instance is located receives the APP registration response from the APP integration platform where the AUEF is located.
  • the APP registration response includes the session identifier allocated by the SMF for the first APP instance and the first address allocated by the SMF or the first anchor UPF for the session of the first APP instance.
  • the application server where the first APP instance is located may also publish a route according to the first address allocated by the SMF or the first anchor point UPF for the session of the APP instance. No specific limitation is made.
  • the above steps S1403-S1411 show the session establishment process when the first APP instance goes online on the APP integration platform and in the 5G network.
  • the application server where the first APP instance is located can send the APP registration update to the APP integration platform where the AUEF is located, and the APP integration platform where the AUEF is located can extend the Nsmf_PDU session_update (Update ) service or a new service type to complete the session update process of the first APP instance in the 5G network; or, when the first APP instance goes offline, the APP integration platform where the AUEF is located can extend the Nsmf_PDU session_release (Release) service or The new service type completes the session release process of the first APP instance in the 5G network, and details are not described herein again in this embodiment of the present application.
  • the terminal device initiates a session establishment process
  • the related implementation may refer to the prior art, which will not be repeated here.
  • description is made by taking an example that the anchor UPF serving the terminal device is the second anchor UPF.
  • UDM can The properties of the terminal device build the function of the virtual local area network. For related descriptions, reference may be made to the embodiment shown in FIG. 13 , which will not be repeated here.
  • a self-organizing network that can implement plug-and-play application services can be formed between the terminal device and the first APP instance, so that it can be Data exchange between the terminal device and the application server where the first APP instance is located is realized.
  • the following descriptions are given by respectively taking the terminal device sending the second data to the application server where the first APP instance is located and the application server where the first APP instance being sending the first data to the terminal device.
  • the method for the application to access the network includes the following steps:
  • S1413-S1415 are the same as steps S1311-S1313 in the embodiment shown in FIG. 13, and are not repeated here.
  • the first anchor point UPF sends the second data to the APP integration platform where the AUEF is located through the path between the first anchor point UPF and the AUEF.
  • the APP integration platform where the AUEF is located receives the second data from the first anchor point UPF.
  • the first anchor point UPF when the first anchor point UPF sends the second data to the APP integration platform where the AUEF is located through the path between the first anchor point UPF and the AUEF, the above-mentioned first path information and second path information may be used.
  • first path information and second path information may be used for the encapsulation of the second data.
  • the APP integration platform where the AUEF is located sends the second data to the application server where the first APP instance is located.
  • the application server where the first APP instance is located receives the second data from the APP integration platform where the AUEF is located.
  • the above steps S1413-S1417 are described by taking as an example that a virtual local area network can be constructed for the first APP instance and the terminal device.
  • the second data may not be transmitted through the N19 tunnel between the first anchor point UPF and the second anchor point UPF.
  • the application server where the first APP instance is located advertises a route according to the first address allocated by the SMF or the first anchor UPF for the session of the first APP instance
  • the embodiment of the present application after receiving the second data, the second anchor point UPF can directly address the application server according to the first address published by the application server where the first APP instance is located according to the existing routing mode, and then the second anchor point UPF can directly address the application server to the application server.
  • the application server forwards the second data, which is not specifically limited in this embodiment of the present application.
  • the first anchor UPF in the process of establishing a session for the first APP instance, supports publishing the routing policy for the first APP instance in the 5G network, then in the embodiment of the present application, the first anchor point UPF After the second anchor point UPF receives the second data, it can directly address the first anchor point UPF according to the routing policy advertised by the first anchor point UPF according to the existing routing mode, and then the second anchor point UPF sends the first anchor point UPF to the first anchor point UPF. Send the second data, after receiving the second data, the first anchor UPF sends the second data to the application server where the first APP instance is located through the APP integration platform where the AUEF is located, which is not done in this embodiment of the present application Specific restrictions.
  • the method for the application to access the network includes the following steps:
  • the application server where the first APP instance is located sends the first data to the APP integration platform where the AUEF is located.
  • the APP integration platform where the AUEF is located receives the first data from the application server where the first APP instance is located.
  • the first data includes a source address and a destination address, the source address is the first address allocated by the core network for the session of the first APP instance in the process of establishing a session for the first APP instance, and the destination address is the process of establishing a session for the terminal device The second address allocated by the core network for the session of the terminal device.
  • the APP integration platform where the AUEF is located sends the first data to the first anchor point UPF through the path between the first anchor point UPF and the AUEF.
  • the first anchor point UPF receives the first data from the APP integration platform where the AUEF is located.
  • the APP integration platform where the AUEF is located sends the first data to the first anchor point UPF through the path between the first anchor point UPF and the AUEF
  • the above-mentioned first path information and second path information may be used.
  • S1420-S1422 are the same as steps S1316-S1318 in the embodiment shown in FIG. 13, and are not repeated here.
  • the above steps S1418-S1422 are described by taking as an example that a virtual local area network can be constructed for the first APP instance and the terminal device.
  • the first data may not be transmitted through the N19 tunnel between the first anchor point UPF and the second anchor point UPF.
  • the second anchor point UPF advertises a route according to the second address allocated by the SMF or the second anchor point UPF for the session of the terminal device, then in this embodiment of the present application, the first APP instance is located
  • the application server can directly address the second anchor point UPF according to the second address published by the second anchor point UPF according to the existing routing mode, and then the second anchor point UPF can forward the first data to the terminal device.
  • This embodiment of the application There is no specific limitation on this.
  • the SMF and the first anchor UPF in the mobile communication network establish a session for the first APP instance, and in the process of establishing the session, the first address is allocated to the session of the first APP instance.
  • the address allocation and management corresponding to the application instance, and the forwarding path of the data plane are all within the control range of the mobile communication network. That is to say, in this solution, the first APP instance can be connected to the 5G network as a special terminal device. Since the first APP instance is a specific running instance of an application, based on this solution, the flexibility of data interaction between the application and the mobile communication network can be improved.
  • the application can be incorporated into the mobile communication network planning to realize the plug-and-play of the application in the mobile communication system, so as to realize the dynamic arrangement and path optimization of the application service. This facilitates the realization of a new business deployment and cooperation model between operators and application service providers.
  • the actions of the SMF, the APP integration platform or the first anchor UPF in the above steps S1400 to S1422 may be performed by the processor 1101 in the communication device 1100 shown in FIG. 11 calling the application code stored in the memory 1103 to instruct the SMF, APP
  • the integration platform or the first anchor point UPF is executed, which is not limited in this embodiment.
  • the methods and/or steps implemented by the first user plane functional entity may also be implemented by components that can be used for the first user plane functional entity;
  • the methods and/or steps implemented by the access module can also be implemented by components (such as chips or circuits) that can be used in the application instance access module;
  • the methods and/or steps implemented by the session management functional entity can also be implemented by the session management function entity.
  • a component eg, a chip or circuit that manages the implementation of a functional entity.
  • an embodiment of the present application further provides a communication device, which may be the session management functional entity in the above method embodiments, or a device including the above session management functional entity, or a component usable for the session management functional entity.
  • the communication apparatus includes corresponding hardware structures and/or software modules for executing each function.
  • the present application can be implemented in hardware or a combination of hardware and computer software with the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein. Whether a function is performed by hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each particular application, but such implementations should not be considered beyond the scope of this application.
  • FIG. 15 shows a schematic structural diagram of a communication device 150 .
  • the communication device 150 includes a processing module 1502 and a transceiver module 1501 .
  • the transceiver module 1501 may also be called a transceiver unit to implement a transceiver function, for example, a transceiver circuit, a transceiver, a transceiver or a communication interface.
  • the communication device 150 is the session management network element in the above method embodiment or a chip or other component provided in the session management network element as an example:
  • the transceiver module 1501 is configured to receive a first message from the application instance access module, where the first message includes identification information of the first application instance, and the first message is used to request to establish a first connection for the first application instance.
  • the processing module 1502 is configured to determine a first user plane functional entity serving the first application instance.
  • the transceiver module 1501 is further configured to send a second message to the first user plane functional entity, where the second message includes identification information of the first application instance, and the second message is used to request to establish a first connection for the first application instance.
  • the transceiver module 1501 is further configured to receive a third message from the first user plane functional entity, where the third message includes the establishment result of the first connection, wherein the establishment result includes success.
  • the transceiver module 1501 is further configured to send a fourth message to the application instance access module, where the fourth message includes the first address allocated by the core network element for the first connection.
  • the first message and the second message further include the first path information allocated by the application instance access module for the first connection; the third message and the fourth message also include that the first user plane functional entity is the first The second path information allocated by the connection, wherein the first path information and the second path information are used to establish the first path between the first user plane functional entity and the application instance access module in the first connection.
  • the core network element is the first user plane functional entity; the third message further includes the first address.
  • the core network element is a session management function entity.
  • the second message further includes a first address, where the first address is used for the first user plane functional entity to advertise the route.
  • the first message further includes a first parameter, and the first parameter is used to determine the first user plane function entity serving the first application instance; or the first parameter is used to construct a first user plane function entity including the first user plane function entity. virtual local area network.
  • the first parameter includes at least one of the following parameters: location information of the first application instance, SSC mode, DNN corresponding to the first connection or identification information of the network slice where the first connection is located.
  • the first message further includes application information corresponding to the first application instance, where the application information is used to construct a virtual local area network including the first user plane functional entity.
  • the transceiver module 1501 is further configured to send a fifth message to the unified data management function entity, where the fifth message includes the identification information of the first application instance, and the fifth message is used to request the acquisition of the subscription of the first application instance data.
  • the transceiver module 1501 is further configured to receive subscription data from the unified data management functional entity, wherein the subscription data is used to determine the first user plane functional entity serving the first application instance; or the subscription data is used to construct a first user plane A virtual local area network of functional entities.
  • the transceiver module 1501 is further configured to register with the network storage function entity that the communication device 150 supports the function of establishing a connection for the application instance.
  • the communication device 150 is an application instance access module in the above method embodiment or a chip or other component provided in the application instance access module as an example:
  • the processing module 1502 is configured to determine a session management function entity serving the first application instance.
  • the transceiver module 1501 is configured to send a first message to the session management function entity, where the first message includes identification information of the first application instance, and the first message is used to request to establish a first connection for the first application instance.
  • the transceiver module 1501 is further configured to receive a fourth message from the session management function entity, where the fourth message includes the first address allocated by the core network element for the first connection.
  • the first message further includes first path information allocated by the communication device for the first connection; the fourth message further includes second path information allocated by the first user plane functional entity for the first connection, wherein the first The first path information and the second path information are used to establish the first path between the first user plane functional entity and the application instance access module in the first connection, and the first user plane functional entity is the user plane serving the first application instance functional entity.
  • the transceiver module 1501 is further configured to send the first data to the first user plane functional entity through the first path after acquiring the first data from the first application instance; or, the transceiver module 1501 is further configured to The second data from the first user plane functional entity is received through the first path.
  • the processing module 1502 is further configured to publish the route according to the first address.
  • the transceiver module 1501 is further configured to receive the second data from the second user plane functional entity, wherein the second user plane functional entity is addressed to the application instance according to the route published by the application instance access module. access module.
  • the transceiver module 1501 is further configured to receive a sixth message from the first application instance before sending the first message to the session management function entity, where the sixth message includes application information corresponding to the first application instance , and the sixth message is used to request registration to the application instance access module.
  • the transceiver module 1501 is further configured to send the first address to the first application instance after receiving the fourth message from the session management function entity.
  • the core network element is a session management functional entity; or, the core network element is a first user plane functional entity serving the first application instance.
  • the first message further includes a first parameter, and the first parameter is used to determine the first user plane function entity serving the first application instance; or the first parameter is used to construct a first user plane function entity including the first user plane function entity. virtual local area network.
  • the first parameter includes at least one of the following parameters: location information of the first application instance, SSC mode, DNN corresponding to the first connection or identification information of the network slice where the first connection is located.
  • the first message further includes application information corresponding to the first application instance, and the application information is used to construct a virtual local area network including a first user plane function entity, and the first user plane function entity is the first application.
  • User plane functional entity of instance service is used to construct a virtual local area network including a first user plane function entity, and the first user plane function entity is the first application.
  • the processing module 1502 is configured to determine a session management function entity serving the first application instance, including: obtaining from the network storage function entity one or more session management functions that support establishing a connection for the application instance Information of the entity; according to the information of one or more session management function entities, determine the session management function entity serving the first application instance.
  • the communication device 150 is the first user plane functional entity in the above method embodiments or a chip or other component provided in the first user plane functional entity as an example:
  • the transceiver module 1501 is configured to receive a second message from the session management function entity, where the second message includes identification information of the first application instance, and the second message is used to request to establish a first connection for the first application instance.
  • the transceiver module 1501 is further configured to send a third message to the session management function entity, where the third message includes the establishment result of the first connection, wherein the establishment result includes success or failure.
  • the second message further includes first path information allocated by the application instance access module for the first connection;
  • the third message further includes second path information allocated by the communication device for the first connection, wherein the first The path information and the second path information are used to establish a first path between the first user plane functional entity and the application instance access module in the first connection.
  • the third message further includes the first address allocated by the communication apparatus for the first connection.
  • the second message further includes the first address allocated by the session management function entity for the first connection.
  • the processing module 1502 is configured to publish the route according to the first address.
  • the transceiver module 1501 is further configured to register with the network storage function entity that the communication device 150 supports the function of establishing a connection for the application instance.
  • the transceiver module 1501 is further configured to receive the first data from the first application instance through the application instance access module; the transceiver module 1501 is further configured to send the first data to the second user plane functional entity,
  • the second user plane functional entity is a user plane functional entity serving the terminal device.
  • the transceiver module 1501 is further configured to receive second data from a second user plane function entity, where the second user plane function entity is a user plane function entity serving the terminal device.
  • the transceiver module 1501 is further configured to send the second data to the first application instance through the application instance access module.
  • the second user plane functional entity is addressed to the first user plane functional entity according to a route advertised by the first user plane functional entity.
  • the communication apparatus 150 is presented in the form of dividing each functional module in an integrated manner.
  • Module herein may refer to a specific ASIC, circuit, processor and memory executing one or more software or firmware programs, integrated logic circuit, and/or other device that may provide the functions described above.
  • the communication device 150 may take the form of the communication device 1100 shown in FIG. 11 .
  • the processor 1101 in the communication device 1100 shown in FIG. 11 may call the computer stored in the memory 1103 to execute the instructions, so that the communication device 1100 executes the method for accessing the network by the application in the above method embodiments.
  • the functions/implementation process of the transceiver module 1501 and the processing module 1502 in FIG. 15 can be implemented by the processor 1101 in the communication apparatus 1100 shown in FIG. 11 calling the computer execution instructions stored in the memory 1103 .
  • the function/implementation process of the processing module 1502 in FIG. 15 may be implemented by the processor 1101 in the communication device 1100 shown in FIG. 11 calling the computer-executed instructions stored in the memory 1103, and the function of the transceiver module 1501 in FIG. 15
  • the implementation process can be implemented through the communication interface 1104 in the communication device 1100 shown in FIG. 11 .
  • the communication device 150 provided in this embodiment can execute the above method for accessing a network by an application, the technical effect that can be obtained by the communication device 150 can refer to the above method embodiments, and details are not repeated here.
  • one or more of the above modules or units may be implemented by software, hardware or a combination of both.
  • the software exists in the form of computer program instructions and is stored in the memory, and the processor can be used to execute the program instructions and implement the above method flow.
  • the processor can be built into a SoC (system on chip) or an ASIC, or it can be an independent semiconductor chip.
  • SoC system on chip
  • ASIC application specific integrated circuit
  • the internal processing of the processor may further include necessary hardware accelerators, such as field programmable gate array (FPGA), PLD (Programmable Logic Device) , or a logic circuit that implements dedicated logic operations.
  • FPGA field programmable gate array
  • PLD Programmable Logic Device
  • the hardware can be CPU, microprocessor, digital signal processing (DSP) chip, microcontroller unit (MCU), artificial intelligence processor, ASIC, Any or any combination of SoCs, FPGAs, PLDs, dedicated digital circuits, hardware accelerators, or non-integrated discrete devices that may or may not run the necessary software to perform the above method flows.
  • DSP digital signal processing
  • MCU microcontroller unit
  • ASIC any or any combination of SoCs, FPGAs, PLDs, dedicated digital circuits, hardware accelerators, or non-integrated discrete devices that may or may not run the necessary software to perform the above method flows.
  • an embodiment of the present application further provides a communication device (for example, the communication device may be a chip or a chip system), where the communication device includes a processor for implementing any of the above method embodiments. method.
  • the communication device further includes a memory.
  • the memory is used to store necessary program instructions and data, and the processor can call the program code stored in the memory to instruct the communication apparatus to execute the method in any of the above method embodiments.
  • the memory may also not be in the communication device.
  • the communication device is a chip system, it may be composed of a chip, or may include a chip and other discrete devices, which is not specifically limited in this embodiment of the present application.
  • the above-mentioned embodiments it may be implemented in whole or in part by software, hardware, firmware or any combination thereof.
  • a software program it can be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on the computer, all or part of the processes or functions described in the embodiments of the present application are generated.
  • the computer may be a general purpose computer, special purpose computer, computer network, or other programmable device.
  • the computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be downloaded from a website site, computer, server, or data center Transmission to another website site, computer, server, or data center by wire (eg, coaxial cable, optical fiber, digital subscriber line, DSL) or wireless (eg, infrared, wireless, microwave, etc.).
  • the computer-readable storage medium can be any available medium that can be accessed by a computer or data storage devices including one or more servers, data centers, etc. that can be integrated with the medium.
  • the usable media may be magnetic media (eg, floppy disks, hard disks, magnetic tapes), optical media (eg, DVDs), or semiconductor media (eg, solid state disks (SSDs)), and the like.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Computer Security & Cryptography (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请实施例提供应用接入网络的方法、装置及系统，用于将应用纳入移动通信网络规划中以提升应用与移动通信网络之间数据交互的灵活性。方法包括：会话管理功能实体接收来自应用实例接入模块的第一消息，第一消息用于请求为第一应用实例建立第一连接；会话管理功能实体确定为第一应用实例服务的第一用户面功能实体；会话管理功能实体向第一用户面功能实体发送第二消息，第二消息包括第一应用实例的标识信息；会话管理功能实体接收来自第一用户面功能实体的第三消息，第三消息包括第一连接的建立结果；当建立结果为成功时，会话管理功能实体向应用实例接入模块发送第四消息，第四消息包括核心网网元为第一连接分配的第一地址。

Description

应用接入网络的方法、装置及系统
本申请要求于2020年10月31日提交国家知识产权局、申请号为202011197417.3、申请名称为“应用接入网络的方法、装置及系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及应用接入网络的方法、装置及系统。
背景技术
目前，第三代合作伙伴项目(3rd generation partnership project，3GPP)工作组负责移动通信网络标准架构的制定。而在终端设备通过移动通信网络访问应用的场景中，应用对于移动通信网络而言，通常属于不同的体系。
比如，移动边缘计算(mobile edge computing，MEC)在位于网络边缘的无线接入网(radio access network，RAN)设备中部署互联网技术(internet technology，IT)和云计算能力，可实时获取网络信息，如用户位置信息、小区负载信息等，并被各种应用实例利用，以提供基于内容的业务以及提供差异化的移动宽带的用户体验。然而，MEC由欧洲电信标准化协会(European Telecommunications Standards Institute，ETSI)管理。在MEC标准架构中，需要通过特定的接口和部署方案来实现移动通信网络与应用的数据交互和管理。或者，比如，当前3GPP标准中针对应用的能力开放有专门的描述，同时还增加了网络开放功能(network exposure function，NEF)来实现对应用功能(application function，AF)的能力开放，如AF可以通过NEF实现对流量路由的影响。然而，该架构下，需要通过针对应用的能力开放来影响终端设备访问应用的用户面路径转发策略和业务策略。
综上，目前应用与移动通信网络之间的数据交互不够灵活。
发明内容
本申请实施例提供应用接入网络的方法、装置及系统，用于将应用纳入移动通信网络规划中以提升应用与移动通信网络之间数据交互的灵活性。
为达到上述目的，本申请的实施例采用如下技术方案：
第一方面，提供了一种应用接入网络的方法，执行该功率控制方法的通信装置可以为会话管理功能实体；也可以为应用于会话管理功能实体中的模块，例如芯片或芯片系统。下面以执行主体为会话管理功能实体为例进行描述。会话管理功能实体接收来自应用实例接入模块的第一消息，第一消息包括第一应用实例的标识信息，第一消息用于请求为该第一应用实例建立第一应用实例与移动通信网络之间的第一连接；会话管理功能实体确定为该第一应用实例服务的第一用户面功能实体；会话管理功能实体向第一用户面功能实体发送第二消息，第二消息包括该第一应用实例的标识信息，第二消息用于请求为该第一应用实例建立该第一连接；会话管理功能实体接收来自第一用户面功能实体的第三消息，该第三消息包括该第一连接的建立结果，其中，该建立结果包括成功；会话管理功能实体向应用实例接入模块发送第四消息，该第四消息包括核心网网元为第一连接分配的第一地址。在本申请实施例中，由移动通信网络中的会话管理功能实体和第一用户面功能实体为第一应用实例建立第一应用实例与移动通信网络之间的第一连接，并在建立第一连接的过程中 核心网网元为第一连接分配的第一地址可知，第一应用实例对应的地址分配和管理、数据面的转发路径均在移动通信网络的控制范围内。也就是说，该方案可以将第一应用实例作为特殊的终端设备接入到移动通信网络中。由于第一应用实例为某个应用的具体运行实例，因此基于该方案，可以提升应用与移动通信网络之间数据交互的灵活性。
结合上述第一方面，在一种可能的实现方式中，第一地址用于终端设备与第一应用实例进行数据通信。比如，终端设备可以通过第一地址访问第一应用实例。基于该方案，可以使得终端设备与第一应用实例之间构成一个可以实现应用业务即插即用的自组织网络，从而可以实现终端设备与第一应用实例所在的应用服务器之间的数据互访。
结合上述第一方面，在一种可能的实现方式中，第一消息和第二消息还包括该应用实例接入模块为该第一连接分配的第一路径信息；第三消息和第四消息还包括该第一用户面功能实体为该第一连接分配的第二路径信息，其中，该第一路径信息和该第二路径信息用于建立第一连接中第一用户面功能实体和该应用实例接入模块之间的第一路径。基于该方案，可以使得第一用户面功能实体和应用实例接入模块之间通过第一路径进行数据传输。
结合上述第一方面，在一种可能的实现方式中，核心网网元为所述第一用户面功能实体；第三消息还包括第一地址。即，本申请实施例中，由第一用户面功能实体为第一连接分配第一地址。
结合上述第一方面，在一种可能的实现方式中，核心网网元为会话管理功能实体。即，本申请实施例中，由会话管理功能实体为第一连接分配第一地址。
结合上述第一方面，在一种可能的实现方式中，该第二消息还包括该第一地址，该第一地址用于该第一用户面功能实体发布路由。基于该方案，后续其他网元或实体可以根据第一用户面功能实体发布的路由直接寻址到该第一用户面功能实体。
结合上述第一方面，在一种可能的实现方式中，该第一消息还包括第一参数，该第一参数用于确定为该第一应用实例服务的该第一用户面功能实体或者第一参数用于构建包括第一用户面功能实体的虚拟局域网络。示例性的，该第一参数包括以下至少一个参数：第一应用实例的位置信息、会话和业务连续性SSC模式、该第一连接对应的数据网络名称DNN或者该第一连接所在的网络切片的标识信息。
结合上述第一方面，在一种可能的实现方式中，该第一消息还包括与该第一应用实例对应的应用信息，该应用信息用于构建包括第一用户面功能实体的虚拟局域网络。示例性的，该应用信息例如可以包括应用名称或应用标识或应用域名信息。
结合上述第一方面，在一种可能的实现方式中，第一消息包括上述第一参数以及与该第一应用实例对应的应用信息，第一参数以及与该第一应用实例对应的应用信息用于构建包括第一用户面功能实体的虚拟局域网络。
结合上述第一方面，在一种可能的实现方式中，该方法还包括：会话管理功能实体向统一数据管理功能实体发送第五消息，第五消息包括该第一应用实例的标识信息，第五消息用于请求获取该第一应用实例的签约数据；会话管理功能实体接收来自该统一数据管理功能实体的该签约数据，其中，该签约数据用于确定为该第一应用实例服务的该第一用户面功能实体；或者该签约数据用于构建包括第一用户面功能实体的虚拟局域网络。
可以理解的是，本申请实施例中，确定为该第一应用实例服务的第一用户面功能实体的参数包括上述第一参数或者签约数据中的至少一个。用于构建包括第一用户面功能实体的虚拟局域网络的参数包括上述第一参数、与该第一应用实例对应的应用信息或者上述签约数据中的至少一个。
结合上述第一方面，在一种可能的实现方式中，该方法还包括：会话管理功能实体向网络存储功能实体注册该会话管理功能实体支持为应用实例建立连接的功能。基于该方案，后续选择会话管理功能实体时，可以从网络存储功能实体获取支持为应用实例建立连接的会话管理功能实体。
第二方面，提供了一种应用接入网络的方法，执行该功率控制方法的通信装置可以为应用实例接入模块；也可以为应用于应用实例接入模块中的模块，例如芯片或芯片系统；还可以为包含该应用实例接入模块的装置，例如第一应用实例或者应用服务器或者应用集成平台。下面以执行主体为应用实例接入模块为例进行描述。应用实例接入模块确定为第一应用实例服务的会话管理功能实体；应用实例接入模块向该会话管理功能实体发送第一消息，该第一消息包括第一应用实例的标识信息，第一消息用于请求为该第一应用实例建立第一应用实例与移动通信网络之间的第一连接；应用实例接入模块接收来自该会话管理功能实体的第四消息，该第四消息包括核心网网元为该第一连接分配的第一地址。在本申请实施例中，由移动通信网络中的会话管理功能实体和第一用户面功能实体为第一应用实例建立第一应用实例与移动通信网络之间的第一连接，并在建立第一连接的过程中核心网网元为第一连接分配的第一地址可知，第一应用实例对应的地址分配和管理、数据面的转发路径均在移动通信网络的控制范围内。也就是说，该方案可以将第一应用实例作为特殊的终端设备接入到移动通信网络中。由于第一应用实例为某个应用的具体运行实例，因此基于该方案，可以提升应用与移动通信网络之间数据交互的灵活性。
结合上述第二方面，在一种可能的实现方式中，第一地址用于终端设备与第一应用实例进行数据通信。比如，终端设备可以通过第一地址访问第一应用实例。基于该方案，可以使得终端设备与第一应用实例之间构成一个可以实现应用业务即插即用的自组织网络，从而可以实现终端设备与第一应用实例所在的应用服务器之间的数据互访。
结合上述第二方面，在一种可能的实现方式中，该第一消息还包括该应用实例接入模块为该第一连接分配的第一路径信息；该第四消息还包括第一用户面功能实体为该第一连接分配的第二路径信息，其中，该第一路径信息和该第二路径信息用于建立第一用户面功能实体和该应用实例接入模块之间的第一路径，第一用户面功能实体是为该第一应用实例服务的用户面功能实体。基于该方案，可以使得第一用户面功能实体和应用实例接入模块之间通过第一路径进行数据传输。比如，在一种可能的实现方式中，该方法还包括：应用实例接入模块从第一应用实例获取第一数据后，通过该第一路径向该第一用户面功能实体发送该第一数据；或者，该应用实例接入模块通过该第一路径接收来自该第一用户面功能实体的第二数据。
结合上述第二方面，在一种可能的实现方式中，该方法还包括：应用实例接入模块根据该第一地址发布路由。基于该方案，后续其他网元或实体可以根据应用实例接入模块发布的路由直接寻址到该应用实例接入模块。比如，在一种可能的实现方式中，该方法还包括：应用实例接入模块接收来自第二用户面功能实体的第二数据，其中， 该第二用户面功能实体是根据该应用实例接入模块发布的路由寻址到该应用实例接入模块的。
结合上述第二方面，在一种可能的实现方式中，在应用实例接入模块向会话管理功能实体发送第一消息之前，该方法还包括：应用实例接入模块接收来自该第一应用实例的第六消息，该第六消息包括与该第一应用实例对应的应用信息，用于请求注册到应用实例接入模块；在应用实例接入模块接收来自会话管理功能实体的第四消息之后，该方法还包括：应用实例接入模块向该第一应用实例发送该第一地址。
结合上述第二方面，在一种可能的实现方式中，核心网网元为会话管理功能实体；或者，核心网网元为为第一应用实例服务的第一用户面功能实体。
结合上述第二方面，在一种可能的实现方式中，该第一消息还包括第一参数，该第一参数用于确定为该第一应用实例服务的该第一用户面功能实体；或者该第一参数用于构建包括第一用户面功能实体的虚拟局域网络。示例性的，该第一参数包括以下至少一个参数：该第一应用实例的位置信息、会话和业务连续性SSC模式、该第一连接对应的数据网络名称DNN或者该第一连接所在的网络切片的标识信息。
结合上述第二方面，在一种可能的实现方式中，该第一消息还包括与该第一应用实例对应的应用信息，该应用信息用于构建包括第一用户面功能实体的虚拟局域网络。示例性的，该应用信息例如可以包括应用名称或应用标识或应用域名信息。
结合上述第二方面，在一种可能的实现方式中，第一消息包括上述第一参数以及与该第一应用实例对应的应用信息，第一参数以及与该第一应用实例对应的应用信息用于构建包括第一用户面功能实体的虚拟局域网络，第一用户面功能实体是为第一应用实例服务的用户面功能实体。
结合上述第二方面，在一种可能的实现方式中，应用实例接入模块确定为第一应用实例服务的会话管理功能实体，包括：应用实例接入模块从网络存储功能实体获取支持为应用实例建立连接的一个或多个会话管理功能实体的信息；应用实例接入模块根据该一个或多个会话管理功能实体的信息，确定为该第一应用实例服务的会话管理功能实体。即，本申请实施例中，应用实例接入模块可以通过与网络存储功能实体的交互确定为第一应用实例服务的会话管理功能实体。
第三方面，提供了一种应用接入网络的方法，执行该功率控制方法的通信装置可以为第一用户面功能实体；也可以为应用于第一用户面功能实体中的模块，例如芯片或芯片系统。下面以执行主体为第一用户面功能实体为例进行描述。第一用户面功能实体接收来自会话管理功能实体的第二消息，第二消息包括第一应用实例的标识信息，第二消息用于请求为该第一应用实例建立第一应用实例与移动通信网络之间的第一连接，第一用户面功能实体是为第一应用实例服务的用户面功能实体；第一用户面功能实体向该会话管理功能实体发送第三消息，该第三消息包括该第一连接的建立结果，其中，该建立结果包括成功或失败。在本申请实施例中，由移动通信网络中的会话管理功能实体和第一用户面功能实体为第一应用实例建立第一应用实例与移动通信网络之间的第一连接，并在建立第一连接的过程中核心网网元为第一连接分配的第一地址可知，第一应用实例对应的地址分配和管理、数据面的转发路径均在移动通信网络的控制范围内。也就是说，该方案可以将第一应用实例作为特殊的终端设备接入到移动 通信网络中。由于第一应用实例为某个应用的具体运行实例，因此基于该方案，可以提升应用与移动通信网络之间数据交互的灵活性。
结合上述第三方面，在一种可能的实现方式中，该第二消息还包括该应用实例接入模块为该第一连接分配的第一路径信息；该第三消息还包括该第一用户面功能实体为该第一连接分配的第二路径信息，其中，该第一路径信息和该第二路径信息用于建立第一连接中该第一用户面功能实体和该应用实例接入模块之间的第一路径。基于该方案，可以使得第一用户面功能实体和应用实例接入模块之间通过第一路径进行数据传输。
结合上述第三方面，在一种可能的实现方式中，该第三消息还包括该第一用户面功能实体为该第一连接分配的第一地址。即，本申请实施例中，由第一用户面功能实体为第一连接分配第一地址。
结合上述第三方面，在一种可能的实现方式中，该第二消息还包括该会话管理功能实体为该第一连接分配的第一地址。即，本申请实施例中，由会话管理功能实体为第一连接分配第一地址。
结合上述第三方面，在一种可能的实现方式中，第一地址用于终端设备与第一应用实例进行数据通信。比如，终端设备可以通过第一地址访问第一应用实例。基于该方案，可以使得终端设备与第一应用实例之间构成一个可以实现应用业务即插即用的自组织网络，从而可以实现终端设备与第一应用实例所在的应用服务器之间的数据互访。
结合上述第三方面，在一种可能的实现方式中，该方法还包括：第一用户面功能实体根据该第一地址发布路由。基于该方案，后续其他网元或实体可以根据第一用户面功能实体发布的路由直接寻址到该第一用户面功能实体。比如，在一种可能的实现方式中，该方法还包括：第一用户面功能实体接收来自第二用户面功能实体的第二数据，并通过应用实例接入模块向该第一应用实例发送该第二数据。其中，该第二用户面功能实体是根据该第一用户面功能实体发布的路由寻址到该第一用户面功能实体的。一种可能的实现方式，该第二用户面功能实体是为终端设备服务的用户面功能实体，该终端设备可以通过第一地址访问第一应用实例。基于该方案，可以实现终端设备到第一应用实例的数据传输。
结合上述第三方面，在一种可能的实现方式中，该方法还包括：第一用户面功能实体向网络存储功能实体注册第一用户面功能实体支持为应用实例建立连接的功能。基于该方案，后续选择用户面功能实体时，可以从网络存储功能实体获取支持为应用实例建立连接的用户面功能实体。
结合上述第三方面，在一种可能的实现方式中，该方法还包括：第一用户面功能实体通过应用实例接入模块接收来自该第一应用实例的第一数据；第一用户面功能实体向第二用户面功能实体发送该第一数据，该第二用户面功能实体是为终端设备服务的用户面功能实体。该终端设备可以通过第一地址访问第一应用实例。基于该方案，可以实现第一应用实例到终端设备的数据传输。
第四方面，提供了一种通信装置用于实现上述方法。该通信装置包括实现上述方法相应的模块、单元、或手段(means)，该模块、单元、或means可以通过硬件实现，软件实现，或者通过硬件执行相应的软件实现。该硬件或软件包括一个或多个与上述 功能相对应的模块或单元。
第五方面，提供了一种通信装置，包括：处理器；该处理器用于与存储器耦合，并读取存储器中存储的计算机指令之后，根据该指令执行如上述任一方面所述的方法。
结合上述第五方面，在一种可能的实现方式中，通信装置还包括存储器；该存储器用于存储计算机指令。
结合上述第五方面，在一种可能的实现方式中，通信装置还包括通信接口；该通信接口用于该通信装置与其它设备进行通信。示例性的，该通信接口可以为收发器、输入/输出接口、接口电路、输出电路、输入电路、管脚或相关电路等。
结合上述第五方面，在一种可能的实现方式中，该通信装置可以是芯片或芯片系统。其中，当该通信装置是芯片系统时，该通信装置可以由芯片构成，也可以包含芯片和其他分立器件。
结合上述第五方面，在一种可能的实现方式中，当通信装置为芯片或芯片系统时，上述通信接口可以是该芯片或芯片系统上的输入/输出接口、接口电路、输出电路、输入电路、管脚或相关电路等。上述处理器也可以体现为处理电路或逻辑电路。
第六方面，提供了一种计算机可读存储介质，该计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机可以执行上述任一方面所述的方法。
第七方面，提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机可以执行上述任一方面所述的方法。
其中，第四方面至第七方面中任一种可能的实现方式所带来的技术效果可参见上述第一方面或第二方面或第三方面中不同实现方式所带来的技术效果，此处不再赘述。
第八方面，提供一种通信系统，该通信系统包括上述第一方面所述的会话管理功能实体和上述第三方面所述的第一用户面功能实体。
结合上述第八方面，在一种可能的实现方式中，该通信系统还包括上述第二方面所述的应用实例接入模块。
附图说明
图1为现有的3GPP ULCL架构示意图；
图2为现有的3GPP BP架构示意图；
图3为目前ETSI定义的MEC标准架构的简要示意图；
图4为现有的MEC解决方案中部署本地(local)APP的一种形态示意图；
图5为现有的5GVN服务的用户面架构示意图；
图6为现有的基于N19隧道转发的用户面协议栈示意图；
图7为本申请实施例提供的通信系统的架构示意图；
图8为本申请实施例提供的应用实例接入模块的部署示意图一；
图9为本申请实施例提供的应用实例接入模块的部署示意图二；
图10为本申请实施例提供的通信系统在5G网络的应用示意图；
图11为本申请实施例提供的通信装置的结构示意图；
图12为本申请实施例提供的应用接入网络的方法的交互示意图一；
图13为本申请实施例提供的应用接入网络的方法的交互示意图二；
图14为本申请实施例提供的应用接入网络的方法的交互示意图三；
图15为本申请实施例提供的通信装置的结构示意图。
具体实施方式
为了方便理解本申请实施例的技术方案，首先给出本申请相关技术的简要介绍如下。
第一，应用(application，APP)与APP实例：
本申请实施例中的APP是指提供的某一类应用服务，例如：提供互联网业务的某一类应用服务。示例性的，APP例如可以为淘宝，用于提供上网购物的互联网业务；或者，APP例如可以为腾讯视频，用于提供上网看视频的互联网业务，等等。
本申请实施例中的APP实例是指运行APP的实例。例如，当APP为淘宝时，对应的APP实例是指运行淘宝的实例；或者，当APP为腾讯视频时，对应的APP实例是指运行腾讯视频的实例。
本申请实施例中，每个APP可以部署多个APP实例来共同提供服务，即一个APP可以对应多个APP实例。APP实例通常运行在应用服务器内，在此统一说明，以下不再赘述。
第二，锚点用户面功能(user plane function，UPF)与中间UPF(intermediate UPF，I-UPF)：
本申请实施例中，锚点UPF可以为协议数据单元(protocol data unit，PDU)会话锚点(PDU session anchor，PSA)-UPF。其中，在终端设备移动过程中，整个会话的锚点UPF是不会变化的，锚点UPF负责发布终端设备互联网协议(internet protocol，IP)的下行路由策略，发送给终端设备的报文都会基于该下行路由策略转发到锚点UPF进行处理。
在一种可能的实现方式中，I-UPF位于RAN设备与锚点UPF之间，会随着终端设备的移动不停的发生切换。
第三，3GPP上行分类器(uplink-classifier，ULCL)架构与3GPP分叉点(branching point)架构：
为了使得应用能够更加灵活的选择部署位置，不会因为核心网位置过高而导致部署在边缘的业务流量出现迂回，3GPP在制定第五代(5th generation，5G)核心网用户面业务时，新增了第四代(4th generation，4G)演进分组核心网(evolved packet core，EPC)不支持的用户面ULCL/BP功能。
图1为现有的3GPP ULCL架构示意图。如图1所示，3GPP对3GPP ULCL的架构定义如下：在RAN设备与PDU会话的锚点UPF之间可以插入一个新的UPF ULCL。如同其名字所定义，ULCL的作用是数据流的上行分类器。即，基于对业务流上行特征的识别，通过本地锚点UPF分流数据到本地数据网络(data network，DN)或者通过远端锚点UPF分流数据到远端DN。同时，UPF ULCL还需要对下行流进行聚合处理。其中，本地DN与远端DN是相同的DN。
需要说明的是，图1中的UPF ULCL可以与本地锚点UPF合一部署，也可以分开部署，在此不做具体限定。此外，图1中的接入和移动性管理功能(core access and mobility management function，AMF)用于移动网络中的移动性管理，如用户位置更新、用户注册网络、用户切换等。图1中的会话管理功能(session management function， SMF)用于移动网络中的会话管理，如会话建立、修改或释放等，在此统一说明，以下不再赘述。
图2为现有的3GPP BP架构示意图。3GPP BP架构与3GPP ULCL架构类似，区别比如在于将图1中的UPF ULCL替换为UPF BP。其中，UPF BP与UPF ULCL的功能相同，只是
UPF BP是针对互联网协议版本6(internet protocol version 6，IPV6)的分流点插入；UPF ULCL是针对互联网协议版本4(internet protocol version 4，IPV4)或者非Multi-homed(IPV6多归属，即允许单个会话多地址)场景下的会话。IPV6在用户面和IPV4有一点差异：对于IPv4或者IPv6类型的PDU会话，PDU会话锚点可以是分配给终端设备的IP地址/前缀的IP锚点。其中，对于IPv4类型的PDU会话或者非Multi-homed的IPv6的PDU会话，当多个PDU会话锚点被使用(由于UPF ULCL被插入)时，仅有一个PDU会话锚点是IP锚点。但是，对于一个IPv6的Multi-homed的PDU会话，则可以有多个IP锚点。
第三，MEC标准架构：
图3为目前ETSI定义的MEC标准架构的简要示意图。如图3所示，该MEC标准架构包括：MEC系统层(MEC system level)和MEC主机层(MEC host level)。
MEC系统层包括运营支持系统(operation support system，OSS)和多路访问边缘协调器(multi-access edge orchestrator)。
MEC主机层包括：MEC平台管理器(MEC platform Manager，MEPM)、虚拟化基础架构管理器(virtualisation infrastructure manager)、以及一个或者多个MEC主机。MEC主机包括：MEC平台(MEC platform，MEP)、虚拟化基础架构(virtualisation infrastructure)以及多个MEC APP。
具体的，MEPM通过Mm5接口进行MEC APP的生命周期管理、MEC APP的规则和请求管理以及MEC平台元素管理。MEP用于运行MEC服务(MEC service)，进行服务注册(service registry)、分流规则控制(traffic rules control)以及域名系统(domain name system，DNS)处理等。MEP具有5G网络中AF的功能，MEP中的AF功能通过MEC APP实现。MEP和MEC APP之间通过Mp1接口通信，实现对MEC APP的管理，MEC APP上运行具体的服务。设备APP可以通过网络访问MEC主机上的MEC APP。此外，MEP通过Mp2接口与虚拟化基础架构中的用户面(data plane)进行通信。该data plan可以通过UPF实现，因此，Mp2接口也可以理解为MEP和UPF之间的接口。需要说明的是，MEC主机中的UPF指部署在边缘位置的UPF。
此外，如图3所示，面向客户的业务(customer facing service，CFS)门户网站(portal)通过Mx1接口与OSS连接。设备APP(device app)通过Mx2接口与用户APP生命周期管理(life cycle management，LCM)代理(user APP LCM proxy)连接。用户APP LCM代理分别通过Mm8接口、Mm9接口与OSS和多路访问边缘协调器连接。OSS和多路访问边缘协调器之间通过Mm1接口连接，OSS还通过Mm2接口与MEPM连接。多路访问边缘协调器通过Mm3接口与MEPM连接。多路访问边缘协调器还通过Mm4接口与虚拟化基础设施连接。虚拟化基础设施通过Mm4接口与MEPM连接。
MEC主机中的虚拟化基础架构通过Mp7接口与虚拟化基础架构管理器连接。两个 MEC主机的MEP之间通过Mp3接口通信。需要说明的是，这里的设备APP是指终端设备(或者称为用户设备(user equipment，UE))上安装的APP，在此统一说明，以下不再赘述。
由上述MEC标准架构的描述可知，本申请实施例中，MEC APP需要通过MEC平台与移动通信网络中的虚拟化基础设施进行通信。换言之，在MEC标准架构中，需要通过特定的接口和部署方案来实现移动通信网络与应用的数据交互和管理。显然，该方案中，应用与移动通信网络之间数据交互不够灵活。
图4所示为现有的MEC解决方案中部署本地(local)APP的一种形态示意图。如图4所示，终端设备通过5G网络的RAN设备接入5G网络的用户面处理功能。一方面，用户面处理功能可能通过本地IP锚点连接内容交付网站。另一方面，用户面处理功能可以通过中心IP锚点连接互联网。其中，图4中的用户面处理功能可以对应图1中的UPF ULCL或者图2中的UPF BP。图4中的本地IP锚点可以对应图1或图2中的本地锚点UPF。图4中的中心IP锚点可以对应图1或图2中的远端锚点UPF。图4中的内容交付网站可以对应图1或图2中连接本地锚点UPF的DN。图4中的互联网可以对应图1或图2中连接远端锚点UPF的DN。此外，图4中的用户面处理功能可以部署在图3中的虚拟化基础设施中，图4中的内容交付网站可以部署在图3中的MEC APP中。可以理解的是，终端设备与用户面处理功能之间的连接为无线连接，用户面处理功能与内容交付网站或互联网之间的连接为有线连接。
第四，5G虚拟网络(5G virtual network，5GVN)：
从表达方式上看，5GVN也可以称之为5G本地局域网(local area network，5GLAN)，LAN，LAN-类型服务(type service)，LAN-VN，5GLAN-type service，5GLAN-VN，5GLAN组(group)，或者LAN group等，本申请实施例对此不作具体限定。
5GVN服务是目前的5G网络提供的一个服务，主要应用于家庭通信，企业办公，工厂制造，车联网，电网改造和公安机关等。该服务能够为一组终端设备中的两个或者多个终端设备提供互联网协议(internet protocol，IP)类型或者非IP类型(如以太类型)的私有通信(即点对点的数据传输)。比如，工厂中的设备组成一个5GVN组，不同设备之间可以相互发送以太数据包；或者，企业中一个部门中的雇员的办公设备(如手机，计算机或笔记本电脑等)组成一个5GVN组，不同办公设备之间可以互相发送IP数据包，等等。若两个终端设备不在同一个5GVN组内，则相互之间不能够通信。
图5所示为现有的5GVN服务的用户面架构示意图。其中，终端设备建立到提供5GVN服务的UPF的会话，从而接入到提供5GVN服务的UPF。如图5所示，提供5GVN服务的UPF可以通过N6与数据网络(data network，DN)中现存的LAN互通，例如和LAN中的个人计算机(personal computer，PC)通信；或者，提供5GVN服务的UPF也可以通过内部UPF与UPF之间的连接关联不同终端设备的会话，实现私有通信，本申请实施例对此不作具体限定。其中，本申请实施例中，将提供5GVN服务的UPF之间的接口称之为下一代网络(next generation，N)19接口(简称N19)。将提供5GVN服务的UPF之间的路径称之为N19隧道，在此统一说明，以下不再赘述。当然，提供5GVN服务的UPF之间的接口还可以是其他名称，本申请实施例对此不作具体限定。
示例性的，本申请实施例中的N19隧道可以采用通用分组无线业务(general packet radio  service，GPRS)隧道协议用户面(GPRS tunneling protocol-user plane，GTP-U)方式来构建。上述构建方式可以是动态的，也可以在网络中预配置好的，本申请实施例对此不作具体限定。此外，本申请实施例中，采用GTP-U方式构建N19隧道时，相应的N19隧道信息可以是UPF ID、UPF ID+隧道端点标识(tunnel endpoint identifier，TEID)、IP地址+TEID、或者IP地址+端口号(port)+TEID等，本申请实施例对此不做具体限定。
图6为现有的基于N19隧道转发的用户面协议栈示意图。其中，以属于同一5GVN的终端设备1与终端设备2通信为例，则在终端设备1与终端设备2进行数据交互之前，需要为终端设备1建立会话1，为终端设备2建立会话2。假设会话1对应的锚点UPF为UPF1；会话2对应的锚点UPF为UPF2，则后续终端设备1与终端设备2可以通过UPF1与UPF2之间的N19隧道进行数据交互。具体的，如图6所示，终端设备与UPF之间(如终端设备1与UPF1之间或者终端设备2与UPF2之间)的3GPP网络协议栈包括PDU会话用户面协议栈。终端设备1与终端设备2的PDU会话用户面协议栈之上为应用(application，APP)层。UPF1与UPF2之间的3GPP网络协议栈包括PDU层、GTP-U层以及下层各协议层，该下层各协议层包括用户数据报协议(user datagram protocol，UDP)层/IP层，二层(level2，L2)和L1。此外，本申请实施例中，对于业务报文，UPF不感知APP层，因此如图6所示，APP层在UPF侧对应的是中继(relay)，在此统一说明，以下不在赘述。
需要说明的是，本申请实施例中的N19隧道是5GVN中各个UPF之间的隧道，在此统一说明，以下不再赘述。
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行描述。其中，在本申请的描述中，除非另有说明，“/”表示前后关联的对象是一种“或”的关系，例如，A/B可以表示A或B；本申请中的“和/或”仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况，其中A,B可以是单数或者复数。并且，在本申请的描述中，除非另有说明，“多个”是指两个或多于两个。“以下至少一项(个)”或其类似表达，是指的这些项中的任意组合，包括单项(个)或复数项(个)的任意组合。例如，a，b，或c中的至少一项(个)，可以表示：a，b，c，a-b，a-c，b-c，或a-b-c，其中a，b，c可以是单个，也可以是多个。另外，为了便于清楚描述本申请实施例的技术方案，在本申请的实施例中，采用了“第一”、“第二”等字样对功能和作用基本相同的相同项或相似项进行区分。本领域技术人员可以理解“第一”、“第二”等字样并不对数量和执行次序进行限定，并且“第一”、“第二”等字样也并不限定一定不同。同时，在本申请实施例中，“示例性的”或者“例如”等词用于表示作例子、例证或说明。本申请实施例中被描述为“示例性的”或者“例如”的任何实施例或设计方案不应被解释为比其它实施例或设计方案更优选或更具优势。确切而言，使用“示例性的”或者“例如”等词旨在以具体方式呈现相关概念，便于理解。
此外，本申请实施例描述的网络架构以及业务场景是为了更加清楚的说明本申请实施例的技术方案，并不构成对于本申请实施例提供的技术方案的限定，本领域普通技术人员可知，随着网络架构的演变和新业务场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
如图7所示，为本申请实施例提供的一种通信系统70。该通信系统70包括会话管理功 能实体701和第一用户面功能实体702。一种可能的实现方式，该通信系统70还包括应用实例接入模块703。其中，会话管理功能实体701、第一用户面功能实体702或者应用实例接入模块703中的任意二者之间可以直接通信，也可以通过其他设备的转发进行通信，本申请实施例对此不做具体限定。
会话管理功能实体701，用于接收来自应用实例接入模块703的第一消息，第一消息包括第一应用实例的标识信息，第一消息用于请求为第一应用实例建立第一连接。会话管理功能实体701，还用于在确定为第一应用实例服务的第一用户面功能实体702之后，向第一用户面功能实体702发送第二消息，第二消息包括第一应用实例的标识信息，第二消息用于请求为第一应用实例建立第一连接。第一用户面功能实体702，用于接收来自会话管理功能实体701的第二消息，并向会话管理功能实体701发送第三消息，第三消息包括第一连接的建立结果，其中，建立结果包括成功。会话管理功能实体701，用于接收来自所述第一用户面功能实体702的第三消息，并向应用实例接入模块703发送第四消息，第四消息包括核心网网元为第一连接分配的第一地址。上述方案的具体实现将在后续方法实施例中详细阐述，在此不予赘述。在本申请实施例中，由移动通信网络中的会话管理功能实体和第一用户面功能实体为第一应用实例建立第一应用实例与移动通信网络之间的第一连接，并在建立第一连接的过程中核心网网元为第一连接分配的第一地址可知，第一应用实例对应的地址分配和管理、数据面的转发路径均在移动通信网络的控制范围内。也就是说，该方案可以将第一应用实例作为特殊的终端设备接入到移动通信网络中。由于第一应用实例为某个应用的具体运行实例，因此基于该方案，可以提升应用与移动通信网络之间数据交互的灵活性。进一步的，基于该方案，可以将应用纳入移动通信网络规划中以实现应用在移动通信系统中的即插即用，从而实现对应用业务的动态编排和路径寻优。这样有利于实现运营商和应用服务提供商之间的一种新的商业部署和合作模式。
本申请实施例中，应用实例接入模块703用于辅助第一应用实例接入到移动通信网络。
一种可能的实现方式中，如图8所示，本申请实施例中的应用实例接入模块703可以集成在第一应用实例中，该第一应用实例可以运行在应用服务器中。
另一种可能的实现方式中，如图9所示，本申请实施例中的应用实例接入模块703可以与第一应用实例分开部署。示例性的，如图9所示，该应用实例接入模块703可以集成在APP集成平台(例如图3中的MEP)上，第一应用实例可以运行在应用服务器中。
需要说明的，虽然未示意出，但是图8或者图9所示的应用服务器中还可能包括其他应用实例，本申请实施例仅是示例性的以应用服务器上的第一应用实例为例进行说明，对于应用服务器是否运行其他应用实例对此不做具体限定。此外，在图9中，可能存在多个应用服务器与APP集成平台交互，本申请实施例对此不做具体限定。
一种可能的实现方式，图7所示的通信系统70可以应用于目前的4G网络、5G网络或者未来的其他网络，本申请实施例对此不作具体限定。
示例性的，如图10所示，若图7所示的通信系统70应用于目前的5G网络，则图7所示的通信系统70中的会话管理功能实体701所对应的网元或者实体可以为5G网络架构中的SMF；图7所示的通信系统70中的第一用户面功能实体702所对应的网元或者实体可以为5G网络架构中的第一锚点UPF。此外，图7所示的通信系统70中的应用实例接入模块703所对应的 网元或者实体例如可以为应用作为用户设备功能(APP as user equipment function，AUEF)。如图8所示，AUEF可以部署在应用服务器内的第一应用实例中；或者，如图9所示，AUEF可以部署在APP集成平台上。当然，AUEF还可能有其他部署方式，比如部署在现有的其他功能或者设备或平台上，或者部署在其他新增的功能或设备或平台上等，本申请实施例对此不做具体限定。
此外，如图10所示，目前的5G网络还可以包括AMF、NEF、网络功能存储功能(network exposure function repository function，NRF)、统一数据管理(unified data management，UDM)、策略控制功能(policy control function，PCF)以及其他UPF(如图10中终端设备对应的第二锚点UPF以及I-UPF)，本申请实施例对此不作具体限定。
虽然未示出，目前的5G网络还可以包括认证服务器功能(authentication server function，AUSF)以及网络切片选择功能(network slice selection function，NSSF)等。相关描述可以参考23501标准中的5G系统架构(5G system architecture)图，在此不予赘述。
其中，如图10所示，终端设备通过RAN设备接入5G网络。终端设备通过N1接口(简称N1)与AMF通信。RAN设备通过N2接口(简称N2)与AMF通信。RAN设备通过N3接口(简称N3)与I-UPF通信。I-UPF通过N9接口(简称N9)与第二锚点UPF通信。第二锚点UPF通过N19接口(简称N19)与第一锚点UPF通信。SMF网元通过N4接口(简称N4)分别与I-UPF、第二锚点UPF以及第一锚点UPF通信。SMF网元通过Nx接口(简称Nx)与AUEF通信。第一锚点UPF通过Nd接口(简称Nd)与AUEF通信。此外，图10所示的AMF、SMF、NEF、NRF、PCF或者UDM等控制面功能也可以采用服务化接口进行交互。比如，AMF对外提供的服务化接口可以为Namf；SMF对外提供的服务化接口可以为Nsmf；NEF对外提供的服务化接口可以为Nnef；NRF对外提供的服务化接口可以为Nnrf；PCF对外提供的服务化接口可以为Npcf；UDM对外提供的服务化接口可以为Nudm。相关描述可以参考23501标准中的5G系统架构(5G system architecture)图，在此不予赘述。
一种可能的实现方式，本申请实施例中的终端设备，可以是用于实现无线通信功能的设备，例如终端或者可用于终端中的芯片等，其可以部署在陆地上，包括室内或室外、手持或车载；也可以部署在水面上(如轮船等)；还可以部署在空中(例如飞机、气球和卫星上等)。其中，终端可以是5G网络或者未来演进的公共陆地移动网(public land mobile network，PLMN)中的UE、接入终端、终端单元、终端站、移动站、移动台、远方站、远程终端、移动设备、无线通信设备、终端代理或终端装置等。接入终端可以是蜂窝电话、无绳电话、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless local loop，WLL)站、个人数字助理(personal digital assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备或可穿戴设备，无人机(unmanned aerial vehicle，UAV)和无人机控制器(UAV controller，UAVC)，虚拟现实(virtual reality，VR)终端设备、增强现实(augmented reality，AR)终端设备、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程医疗(remote medical)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端等。终端可以是移动的，也可以是固定的。
一种可能的实现方式，本申请实施例中的RAN设备，是一种为终端设备提供无线通信 功能的设备。接入网设备例如包括但不限于：5G中的下一代基站(gnodeB，gNB)、演进型节点B(evolved node B，eNB)、无线网络控制器(radio network controller，RNC)、节点B(node B，NB)、基站控制器(base station controller，BSC)、基站收发台(base transceiver station，BTS)、家庭基站(例如，home evolved nodeB，或home node B，HNB)、基带单元(baseBand unit，BBU)、传输点(transmitting and receiving point，TRP)、发射点(transmitting point，TP)、移动交换中心等。
一种可能的实现方式，本申请实施例中的用户面网元、接入网设备、会话管理网元、策略控制网元或者应用功能网元也可以称之为通信装置或通信设备，其可以是一个通用设备或者是一个专用设备，本申请实施例对此不作具体限定。
一种可能的实现方式，本申请实施例中的会话管理功能实体、第一用户面功能实体、或者应用实例接入模块的相关功能可以由一个设备实现，也可以由多个设备共同实现，还可以是由一个设备内的一个或多个功能模块实现，本申请实施例对此不作具体限定。可以理解的是，上述功能既可以是硬件设备中的网络元件，也可以是在专用硬件上运行的软件功能，或者是硬件与软件的结合，或者是平台(例如，云平台)上实例化的虚拟化功能。
例如，本申请实施例中的会话管理功能实体、第一用户面功能实体、或者应用实例接入模块的相关功能可以通过图11中的通信装置1100来实现。图11所示为本申请实施例提供的通信装置1100的结构示意图。该通信装置1100包括一个或多个处理器1101，通信线路1102，以及至少一个通信接口(图11中仅是示例性的以包括通信接口1104，以及一个处理器1101为例进行说明)，一种可能的实现方式还可以包括存储器1103。
处理器1101可以是一个通用中央处理器(central processing unit，CPU)，微处理器，特定应用集成电路(application-specific integrated circuit，ASIC)，或一个或多个用于控制本申请方案程序执行的集成电路。
通信线路1102可包括一通路，用于连接不同组件之间。
通信接口1104，可以是收发模块用于与其他设备或通信网络通信，如以太网，RAN，无线局域网(wireless local area networks，WLAN)等。例如，所述收发模块可以是收发器、收发机一类的装置。一种可能的实现方式，所述通信接口1104也可以是位于处理器1101内的收发电路，用以实现处理器的信号输入和信号输出。
存储器1103可以是具有存储功能的装置。例如可以是只读存储器(read-only memory，ROM)或可存储静态信息和指令的其他类型的静态存储设备，随机存取存储器(random access memory，RAM)或者可存储信息和指令的其他类型的动态存储设备，也可以是电可擦可编程只读存储器(electrically erasable programmable read-only memory，EEPROM)、只读光盘(compact disc read-only memory，CD-ROM)或其他光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其他磁存储设备、或者能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其他介质，但不限于此。存储器可以是独立存在，通过通信线路1102与处理器相连接。存储器也可以和处理器集成在一起。
其中，存储器1103用于存储执行本申请方案的计算机执行指令，并由处理器1101来控制执行。处理器1101用于执行存储器1103中存储的计算机执行指令，从而实现本申请实施例中提供的应用接入网络的方法。
或者，一种可能的实现方式，本申请实施例中，也可以是处理器1101执行本申请下述实施例提供的应用接入网络的方法中的处理相关的功能，通信接口1104负责与其他设备或通信网络通信，本申请实施例对此不作具体限定。
一种可能的实现方式，本申请实施例中的计算机执行指令也可以称之为应用程序代码，本申请实施例对此不作具体限定。
在具体实现中，作为一种实施例，处理器1101可以包括一个或多个CPU，例如图11中的CPU0和CPU1。
在具体实现中，作为一种实施例，通信装置1100可以包括多个处理器，例如图11中的处理器1101和处理器1108。这些处理器中的每一个可以是一个单核(single-core)处理器，也可以是一个多核(multi-core)处理器。这里的处理器可以包括以下至少一种：中央处理单元(central processing unit，CPU)、微处理器、数字信号处理器(DSP)、微控制器(microcontroller unit，MCU)、或人工智能处理器等各类运行软件的计算设备，每种计算设备可包括一个或多个用于执行软件指令以进行运算或处理的核。
在具体实现中，作为一种实施例，通信装置1100还可以包括输出设备1105和输入设备1106。输出设备1105和处理器1101通信，可以以多种方式来显示信息。例如，输出设备1105可以是液晶显示器(liquid crystal display，LCD)，发光二级管(light emitting diode，LED)显示设备，阴极射线管(cathode ray tube，CRT)显示设备，或投影仪(projector)等。输入设备1106和处理器1101通信，可以以多种方式接收用户的输入。例如，输入设备1106可以是鼠标、键盘、触摸屏设备或传感设备等。
上述的通信装置1100有时也可以称为通信装置，其可以是一个通用设备或者是一个专用设备。例如通信装置1100可以是台式机、便携式电脑、网络服务器、掌上电脑(personal digital assistant，PDA)、移动手机、平板电脑、无线终端设备、嵌入式设备、上述终端设备，上述网络设备、或具有图11中类似结构的设备。本申请实施例不限定通信装置1100的类型。
如图12所示，为本申请实施例提供的一种应用接入网络的方法，包括如下步骤：
S1201、应用实例接入模块确定为第一应用实例服务的会话管理功能实体。
一种可能的实现方式中，应用实例接入模块确定为第一应用实例服务的会话管理功能实体，包括：应用实例接入模块从网络存储功能实体获取支持为应用实例建立连接的一个或多个会话管理功能实体的信息；应用实例接入模块根据一个或多个会话管理功能实体的信息，确定为第一应用实例服务的会话管理功能实体。
S1202、应用实例接入模块向会话管理功能实体发送第一消息。相应的，会话管理功能实体接收来自应用实例接入模块的第一消息。第一消息包括第一应用实例的标识信息，第一消息用于请求为第一应用实例建立第一连接。
本申请实施例中，为第一应用实例建立的“第一连接”是指，为第一应用实例建立的第一应用实例与移动通信网络之间的连接，用于将第一应用实例作为特殊的终端设备接入到移动通信网络中，从而可以使得第一应用实例后续可以通过该第一连接与其他设备进行数据通信。示例性的，这里的第一连接可以为4G中的分组数据网络(packet data network，PDN)连接或5G中的PDU会话，还可以为未来其他网络中的其他连接，在此统一说明，以下不再赘述。
在本申请实施例中，第一应用实例的标识信息可唯一确定第一应用实例，该第一应用实例的标识信息例如可以为APP实例永久标识(APP instance permanent identifier，AIPI)或者APP实例隐藏标识(APP instance concealed identifier，AICI)，在此统一说明，以下不再赘述。
一种可能的实现方式，本申请实施例中，第一消息还可以包括第一参数和/或与第一应用实例对应的应用信息。
示例性的，本申请实施例中，第一参数包括以下至少一个参数：第一应用实例的位置信息(location information)、会话和业务连续性(session and service continuity，SSC)模式、第一连接对应的数据网络名称(data network name，DNN)或者第一连接所在的网络切片的标识信息。示例性的，本申请实施例中，第一连接所在的网络切片的标识信息例如可以为第一连接所在的网络切片的单网络切片选择辅助信息(single network slice selection assistance information，S-NSSAI)。示例性的，本申请实施例中，第一应用实例的位置信息例如可以为该第一应用实例签约的归属公共陆地移动网(home public land mobile network，HPLMN)；或者，第一应用实例的位置信息例如可以为该第一应用实例所服务的跟踪区的区域标识；或者，或者，第一应用实例的位置信息例如可以为该第一应用实例所服务的小区的小区标识等。
示例性的，本申请实施例中，第一应用实例对应的应用信息包括：应用名称或应用标识或应用域名信息等。
S1203、会话管理功能实体确定为第一应用实例服务的第一用户面功能实体。
一种可能的实现方式中，本申请实施例中，会话管理功能实体可以根据上述第一参数确定为第一应用实例服务的第一用户面功能实体。
比如，会话管理功能实体可以根据第一参数中的第一应用实例的位置信息以及第一连接所在的网络切片的S-NSSAI确定为第一应用实例服务的第一用户面功能实体。示例性的，会话管理功能实体可以将支持第一连接所在的网络切片的S-NSSAI的用户面功能实体中，距离承载第一应用实例的应用服务器最近的用户面功能实体确定为第一用户面功能实体。
另一种可能的实现方式中，本申请实施例中，会话管理功能实体还可以从统一数据管理功能实体获取第一应用实例的签约数据。进而，会话管理功能实体可以根据第一应用实例的签约数据确定为第一应用实例服务的第一用户面功能实体。
示例性的，本申请实施例中，第一应用实例的签约数据包括：允许的连接类型、签约的第一应用实例的位置信息、默认的服务质量(quality of service，QoS)参数、允许的SSC模式、签约的DNN或者签约的网络切片的标识信息中的至少一个。
比如，会话管理功能实体可以根据第一应用实例的签约数据中的签约的第一应用实例的位置信息以及签约的DNN确定为第一应用实例服务的第一用户面功能实体。示例性的，会话管理功能实体可以将支持第一应用实例签约的DNN的用户面功能实体中，距离承载第一应用实例的应用服务器最近的户面功能实体确定为第一用户面功能实体。
本申请实施例中，会话管理功能实体从统一数据管理功能实体获取第一应用实例的签约数据，可以包括：会话管理功能实体向统一数据管理功能实体发送第五消息，第五消息包括第一应用实例的标识信息，第五消息用于请求获取所述第一应用实例的签约数据；会 话管理功能实体接收来自统一数据管理功能实体的第一应用实例的签约数据。
又一种可能的实现方式中，本申请实施例中，会话管理功能实体还可以从统一数据管理功能实体获取第一应用实例的签约数据。进而，会话管理功能实体可以根据第一应用实例的签约数据和上述第一参数确定为第一应用实例服务的第一用户面功能实体。
比如，会话管理功能实体可以根据第一参数中的第一应用实例的位置信息以及第一应用实例的签约数据中第一应用实例签约的DNN确定为第一应用实例服务的第一用户面功能实体。示例性的，会话管理功能实体可以将支持第一应用实例签约的DNN的用户面功能实体中，距离承载第一应用实例的应用服务器最近的户面功能实体确定为第一用户面功能实体。
需要说明的是，上述示例仅是示例性提供会话管理功能实体确定为第一应用实例服务的第一用户面功能实体的几种方式。当然，会话管理功能实体还可以通过其他方式确定为第一应用实例服务的第一用户面功能实体，本申请实施例对此不做具体限定。
一种可能的实现方式，本申请实施例中，会话管理功能实体还可以为第一连接分配第一地址。第一地址用于终端设备与第一应用实例进行数据通信。比如，终端设备可以通过第一地址访问第一应用实例。
示例性的，本申请实施例中的第一地址例如可以包括IP地址(IP address)或者IPv6前缀(IPv6Prefix)或者媒体访问控制(media access control，MAC)地址等，在此统一说明，以下不再赘述。
S1204、会话管理功能实体向第一用户面功能实体发送第二消息。相应的，第一用户面功能实体接收来自会话管理功能实体的第二消息。第二消息包括第一应用实例的标识信息，第二消息用于请求为第一应用实例建立第一连接。
一种可能的实现方式，本申请实施例中，若会话管理功能实体为第一连接分配第一地址，则第二消息中还可以包括第一地址。该第一地址用于第一用户面功能实体发布路由(route advertisement)。这样，后续数据通信的过程中，其他实体或模块可以根据第一用户面功能实体发布的路由直接寻址到第一用户面功能实体。比如，本申请实施例提供的应用接入网络的方法还可以包括：第一用户面功能实体接收来自第二用户面功能实体的第二数据，并通过应用实例接入模块向该第一应用实例发送该第二数据。其中，第二用户面功能实体是根据第一用户面功能实体发布的路由寻址到第二用户面功能实体的。相关寻址方式可参考现有技术，在此不予赘述。
一种可能的实现方式，本申请实施例中，第一地址也可以是由第一用户面功能实体分配的。即，第一用户面功能实体可以为第一连接分配第一地址。
S1205、第一用户面功能实体向会话管理功能实体发送第三消息。相应的，会话管理功能实体接收来自第一用户面功能实体的第三消息。第三消息包括第一连接的建立结果，其中，建立结果包括成功或失败。
一种可能的实现方式，本申请实施例中，当上述第一地址是由第一用户面功能实体分配时，第三消息还包括第一地址。
S1206、当建立结果为成功时，会话管理功能实体向应用实例接入模块发送第四消息。相应的，应用实例接入模块接收来自会话管理功能实体的第四消息。
其中，第四消息包括上述会话管理功能实体为第一连接分配的第一地址，或者包括上 述第一用户面功能实体为第一连接分配的第一地址。
一种可能的实现方式，本申请实施例中，应用实例接入模块获取第一地址后，可以根据第一地址发布路由。这样，后续数据通信的过程中，其他实体或模块可以根据应用实例接入模块发布的路由直接寻址到应用实例接入模块。比如，本申请实施例提供的应用接入网络的方法还可以包括：应用实例接入模块接收来自第二用户面功能实体的第二数据，其中，第二用户面功能实体是根据应用实例接入模块发布的路由寻址到应用实例接入模块的。相关寻址方式可参考现有技术，在此不予赘述。
一种可能的实现方式，在图12所示的应用接入网络的方法中，第一消息和第二消息还可以包括应用实例接入模块为第一连接分配的第一路径信息。第三消息和第四消息还可以包括第一用户面功能实体为第一连接分配的第二路径信息。其中，第一路径信息和第二路径信息用于建立第一连接中第一用户面功能实体和应用实例接入模块之间的第一路径，该第一路径用于第一用户面功能实体和应用实例接入模块之间的数据传输。比如，应用实例接入模块从第一应用实例获取第一数据后，通过第一路径向第一用户面功能实体发送第一数据；或者，应用实例接入模块通过第一路径接收来自第一用户面功能实体的第二数据。
需要说明的是，本申请实施例中的“路径”还可以称之为隧道(tunnel)或者其他名字，本申请实施例对此不做具体限定。例如，上述第一路径信息可以替换为第一隧道信息，上述第二路径信息可以替换为第二隧道信息，等等，在此不再一一赘述。
示例性的，本申请实施例中，第一用户面功能实体和应用实例接入模块之间的第一路径例如可以包括GTP-U隧道、通用路由封装协议(generic routing encapsulation，GRE)隧道或者IP隧道等，本申请实施例对此不作具体限定。
其中，本申请实施例中，对应不同类型的路径，第一路径信息和第二路径信息可能不同。
示例性的，假设第一路径为GTP-U隧道，则第一路径信息可以是该应用实例接入模块的地址，第二路径信息可以是第一用户面功能实体的地址；或者，第一路径信息可以是第一路径在该应用实例接入模块侧的端点标识以及该应用实例接入模块的地址，第二路径信息可以是第一路径在该第一用户面功能实体侧的端点标识以及该第一用户面功能实体的地址；或者，第一路径信息可以是第一路径在该应用实例接入模块侧的端点标识、该应用实例接入模块的地址以及端口号(port)，第二路径信息可以是第一路径在该第一用户面功能实体侧的端点标识、该第一用户面功能实体的地址以及端口号(port)。
示例性的，假设第一路径为GRE隧道，则第一路径信息可以是该应用实例接入模块的地址，第二路径信息可以是第一用户面功能实体的地址；或者，第一路径信息可以是第一路径在该应用实例接入模块侧的端点标识以及该应用实例接入模块的地址，第二路径信息可以是第一路径在该第一用户面功能实体侧的端点标识以及该第一用户面功能实体的地址；或者，第一路径信息可以是第一路径在该应用实例接入模块侧的端点标识、该应用实例接入模块的地址以及密钥(key)，第二路径信息可以是第一路径在该第一用户面功能实体侧的端点标识、该第一用户面功能实体的地址以及密钥(key)。
示例性的，假设第一路径为IP隧道，则第一路径信息可以是该应用实例接入模块的地址，第二路径信息可以是第一用户面功能实体的地址；或者，第一路径信息可以是该应用实例接入模块的地址以及端口号(port)，第二路径信息可以是该第一用户面功能实体的地 址以及端口号(port)。
其中，本申请实施例中的端点标识例如可以为全称隧道端点标识符(fully qualified tunnel endpoint identifier，FTEID)，在此统一说明，以下不再赘述。
一种可能的实现方式，在图12所示的应用接入网络的方法中，会话管理功能实体还可以根据上述第一参数、第一应用实例对应的应用信息或者第一应用实例的签约数据中的至少一个构建包括第一用户面功能实体的虚拟局域网络。
比如，第一应用实例上线时会注册第一应用实例对应的应用信息，而终端设备可以订阅和签约第一应用实例对应的业务，则会话管理功能实体可以根据第一应用实例对应的应用信息，将为第一应用实例服务的第一用户面功能实体与为订阅或签约了第一应用实例对应的业务的终端设备服务的用户面功能实体一起构建一个虚拟局域网络；或者，会话管理功能实体可以根据第一应用实例对应的应用信息，以及第一参数中的第一连接所在的网络切片的S-NSSAI，将为第一应用实例服务的第一用户面功能实体与为订阅或签约了第一应用实例对应的业务的终端设备服务的用户面功能实体中，支持第一连接所在的网络切片的S-NSSAI的用户面功能实体一起构建一个虚拟局域网络；或者，会话管理功能实体可以根据第一应用实例对应的应用信息，以及第一应用实例的签约数据中的第一应用实例签约的DNN，将为第一应用实例服务的第一用户面功能实体与为订阅或签约了第一应用实例对应的业务的终端设备服务的用户面功能实体中，支持第一应用实例签约的DNN的用户面功能实体一起构建一个虚拟局域网络。
需要说明的是，本申请实施例中，构建虚拟网络的方式与现有的构建5GVN方式类似，区别比如在于：本申请实施例中，在构建虚拟局域网络时，可以将第一应用实例视为一类特殊的终端设备与其他普通终端设备一起构建虚拟局域网络。此外，本申请实施例中，如果可以为第一应用实例和终端设备构建虚拟局域网络，则在为第一应用实例建立第一连接的流程中，以及在为终端设备建立第二连接的流程中，需要为第一连接和第二连接分配同一个虚拟局域网的地址。比如，假设第一应用实例部署在某个区域，目标是为该区域签约了对应业务的终端设备提供服务。则在为第一应用实例建立第一连接的流程中，以及在为终端设备建立第二连接的流程，需要为第一连接和第二连接分配同一个虚拟局域网的地址。
一种可能的实现方式，本申请实施例提供的应用接入网络的方法还可以包括：会话管理功能实体向网络存储功能实体注册该会话管理功能实体支持为应用实例建立连接的功能。基于该方案，后续选择会话管理功能实体时，可以从网络存储功能实体获取支持为应用实例建立连接的会话管理功能实体。
一种可能的实现方式，本申请实施例提供的应用接入网络的方法还可以包括：第一用户面功能实体向网络存储功能实体注册该第一用户面功能实体支持为应用实例建立连接的功能。基于该方案，后续选择用户面功能实体时，可以从网络存储功能实体获取支持为应用实例建立连接的用户面功能实体。
一种可能的实现方式，在应用实例接入模块确定为第一应用实例服务的会话管理功能实体(步骤S1201)之前，本申请实施例提供的应用接入网络的方法还可以包括：应用实例接入模块接收来自第一应用实例的第六消息，第六消息包括与第一应用实例对应的应用信息，用于请求进行注册；在应用实例接入模块接收来自会话管理功能实体的第四消息(步骤S1206)之后，本申请实施例提供的应用接入网络的方法还可以包括：应用实例接入模 块向第一应用实例发送第一地址。该方案适用于应用实例接入模块与第一应用实例分开部署的场景下。
可以理解的是，本申请实施例示例性的以为第一应用实例建立第一连接为例进行说明，不限定第一应用实例只能对应一个连接，可以为第一应用实例建立一个或多个连接，每个连接均有对应的路径和路径信息，在此统一说明，以下不再赘述。
在本申请实施例中，由移动通信网络中的会话管理功能实体和第一用户面功能实体为第一应用实例建立第一应用实例与移动通信网络之间的第一连接，并在建立第一连接的过程中核心网网元为第一连接分配的第一地址可知，第一应用实例对应的地址分配和管理、数据面的转发路径均在移动通信网络的控制范围内。也就是说，该方案可以将第一应用实例作为特殊的终端设备接入到移动通信网络中。由于第一应用实例为某个应用的具体运行实例，因此基于该方案，可以提升应用与移动通信网络之间数据交互的灵活性。进一步的，基于该方案，可以将应用纳入移动通信网络规划中以实现应用在移动通信系统中的即插即用，从而实现对应用业务的动态编排和路径寻优。这样有利于实现运营商和应用服务提供商之间的一种新的商业部署和合作模式。
其中，上述步骤S1201至S1206中会话管理功能实体、应用实例接入模块或者第一用户面功能实体的动作可以由图11所示的通信装置1100中的处理器1101调用存储器1103中存储的应用程序代码以指令会话管理功能实体、应用实例接入模块或者第一用户面功能实体执行，本实施例对此不作任何限制。
下面将结合具体示例对本申请实施例提供的应用接入网络的方法进行具体阐述。
需要说明的是，本申请下述实施例中各个实体或者模块之间的消息名字或消息中各参数的名字等只是一个示例，具体实现中也可以是其他的名字，本申请实施例对此不作具体限定。
首先，以图7所示所示的通信系统应用于如图10所示的5G网络为例，在图12所示实施例的基础上，图13所示为本申请实施例提供的一种应用接入网络的方法。该应用接入网络的方法中，由应用服务器内的第一APP实例提供AUEF(即AUEF可以视为第一APP实例中的一个功能模块)，SMF/UPF支持将第一APP实例作为特殊终端设备直接接入到5G网络，支持为第一APP实例建立的会话(为方便说明，以下将为第一APP实例建立的会话简称为第一APP实例的会话)分配地址、建立路径等功能。示例性的，该应用接入网络的方法一种可能的实现方式包括如下步骤S1300-S1302：
S1300、SMF向NRF注册SMF是否支持为APP实例建立PDU会话。
示例性的，本申请实施例中，SMF可以通过Nnrf_网络功能(network function，NF)管理(Management)_NF注册(Register)或者Nnrf_NFManagement_NF更新(Update)服务操作(service operation)向NRF注册自己是否支持为APP实例建立PDU会话。其中，Nnrf_NFManagement_NFRegister或者Nnrf_NFManagement_NFUpdate服务操作的输入参数中至少包括SMF是否支持为APP实例建立PDU会话的指示信息。当然，Nnrf_NFManagement_NFRegister或者Nnrf_NFManagement_NFUpdate服务操作的输入参数中还可能包含其他参数，具体可参考现有的3GPP标准，在此不予赘述。
一种可能的实现方式，本申请实施例中，支持为APP实例建立PDU会话的SMF也可以称之为APP会话管理功能(APP Session Management Function，ASMF)。其中，ASMF向NRF 注册自己支持为APP实例建立PDU会话时，需要扩展新的信元(information element，IE)来支持对该功能的描述。比如，ASMF可以通过Nnrf_NFManagement_NFRegister或者Nnrf_NFManagement_NFUpdate服务操作向NRF注册自己支持为APP实例建立PDU会话。其中，Nnrf_NFManagement_NFRegister或者Nnrf_NFManagement_NFUpdate服务操作的输入参数中至少包括ASMF支持为APP实例建立PDU会话的指示信息，本申请实施例对此不做具体限定。
S1301、第一锚点UPF向NRF注册第一锚点UPF是否支持为APP实例建立PDU会话。
示例性的，本申请实施例中，第一锚点UPF可以通过Nnrf_NFManagement_NFRegister或者Nnrf_NFManagement_NFUpdate服务操作向NRF注册自己是否支持为APP实例建立PDU会话。其中，Nnrf_NFManagement_NFRegister或者Nnrf_NFManagement_NFUpdate服务操作的输入参数中至少包括第一锚点UPF是否支持为APP实例建立PDU会话的指示信息。当然，Nnrf_NFManagement_NFRegister或者Nnrf_NFManagement_NFUpdate服务操作的输入参数中还可能包含其他参数，具体可参考现有的3GPP标准，在此不予赘述。
一种可能的实现方式，本申请实施例中，支持为APP实例建立PDU会话的第一锚点UPF也可以称之为第一锚点APP用户面功能(APP user plane function，AUPF)。其中，第一锚点AUPF向NRF注册自己支持为APP实例建立PDU会话时，需要扩展新的IE来支持对该功能的描述。比如，第一锚点AUPF可以通过Nnrf_NFManagement_NFRegister或者Nnrf_NFManagement_NFUpdate服务操作向NRF注册自己支持为APP实例建立PDU会话。其中，Nnrf_NFManagement_NFRegister或者Nnrf_NFManagement_NFUpdate服务操作的输入参数中至少包括第一锚点AUPF支持为APP实例建立PDU会话的指示信息，本申请实施例对此不做具体限定。
S1302、第一APP实例所在的应用服务器从NRF获取支持为APP实例建立PDU会话的一个或多个SMF的信息。
本申请实施例中，SMF的信息包括SMF的标识信息。示例性的，本申请实施例中，SMF的标识信息例如可以是SMF的IP地址，或者SMF的全量域名(fully qualified domain name，FQDN)等，本申请实施例对此不做具体限定。
一种可能的实现方式，本申请实施例中，SMF的信息还可以包括SMF的属性信息，如负荷信息(load information)等，本申请实施例对此不做具体限定。
一种可能的实现方式中，第一APP实例所在的应用服务器可以通过Nnrf_NF发现请求(Discovery_Request)服务操作向NRF查询支持为APP实例建立PDU会话的SMF的信息。此时，Nnrf_NFDiscovery_Request服务操作的输入参数中包括支持为APP实例建立PDU会话的功能要求，Nnrf_NFDiscovery_Request服务操作的输出参数中包括支持为APP实例建立PDU会话的一个或多个SMF的信息。
另一种可能的实现方式中，第一APP实例所在的应用服务器可以通过Nnrf_NFManagement_NF状态订阅(StatusSubscribe)服务操作向NRF订阅支持为APP实例建立PDU会话的SMF的信息。此时，Nnrf_NFManagement_StatusSubscribe服务操作的输入参数中包括支持为APP实例建立PDU会话的功能要求。进一步的，NRF可以通过Nnrf_NFManagement_状态通知(StatusNotify)服务操作向APP实例返回支持为APP实例建立PDU会话的一个或多个SMF的信息。
当然，本申请实施例中，若第一APP实例所在的应用服务器无法从NRF获取支持为APP实例建立PDU会话的一个或多个SMF的信息，第一APP实例所在的应用服务器也可以配置支持为APP实例建立PDU会话的SMF，如该应用服务器可以将某个SMF确定为支持为APP实例建立PDU会话的SMF，本申请实施例对此不做具体限定。或者，本申请实施例中，可以不执行上述步骤S1302，而是第一APP实例所在的应用服务器直接配置支持为APP实例建立PDU会话的SMF，如第一APP实例所在的应用服务器可以将某个SMF确定为支持为APP实例建立PDU会话的SMF，本申请实施例对此不做具体限定。
进一步的，本申请实施例中，第一APP实例所在的应用服务器可以发起会话建立流程，包括如下步骤S1303：
S1303、第一APP实例所在的应用服务器向选定的支持为APP实例建立PDU会话的SMF发送Nsmf_PDU会话创建(PDU session create)请求。相应的，SMF接收来自应用服务器的Nsmf_PDU会话创建请求。该Nsmf_PDU会话创建请求包括第一APP实例的标识信息，用于请求为该第一APP实例建立PDU会话。
其中，第一APP实例的标识信息的相关描述可参考图12所示的实施例，在此不再赘述。
需要说明的是，本申请实施例中的Nsmf_PDU会话创建请求仅是图12中第一消息的一种示例，第一消息还可以为其他，本申请实施例对此不做具体限定。
需要说明的是，本申请实施例示例性的以步骤S1300中的SMF为选定的支持为APP实例建立PDU会话的SMF为例进行说明，在此统一说明，以下不再赘述。
一种可能的实现方式，本申请实施例中，当NRF向应用服务器返回多个支持为APP实例建立PDU会话的SMF的信息时，应用服务器可以根据SMF的属性信息(如负荷信息)确定为该第一APP实例服务的SMF，也可以随机选择为该第一APP实例服务的SMF，本申请实施例对此不做具体限定。
一种可能的实现方式，本申请实施例中的Nsmf_PDU会话创建请求还可以包括与第一APP实例对应的应用信息，该应用信息可唯一确定一个APP。示例性的，该应用信息例如可以为APP名称或APP ID或APP域名信息等，在此统一说明，以下不再赘述。
一种可能的实现方式，本申请实施例中的Nsmf_PDU会话创建请求还可以包括第一路径信息，该第一路径信息用于建立第一锚点UPF与AUEF之间的路径，该第一锚点UPF是为该第一APP实例服务的锚点UPF。其中，第一路径信息的相关描述可参考图12所示的实施例，在此不再赘述。
一种可能的实现方式，本申请实施例中的Nsmf_PDU会话创建请求还可以包括第一参数，第一参数的相关描述可参考图12所述的实施例，在此不再赘述。
一种可能的实现方式，本申请实施例提供的应用接入网络的方法还可以包括如下步骤S1304-S1305：
S1304、SMF向UDM发送签约数据管理(subscriber data management，SDM)_获取请求(Get Request)。相应的，UDM接收来自SMF的SDM_获取请求。该SDM_获取请求包括第一APP实例的标识信息，用于请求该第一APP实例的签约数据。
需要说明的是，本申请实施例中的SMF的SDM_获取请求仅是图12中第五消息的一种示例，第五消息还可以为其他，本申请实施例对此不做具体限定。
一种可能的实现方式，本申请实施例中，当Nsmf_PDU会话创建请求包括与第一APP 实例对应的应用信息时，该SDM_获取请求还可以包括与第一APP实例对应的应用信息，与第一APP实例对应的应用信息用于包括第一锚点UPF构建虚拟局域网络，该第一锚点UPF是为该第一APP实例服务的锚点UPF。
一种可能的实现方式，本申请实施例中，当Nsmf_PDU会话创建请求包括第一参数时，该SDM_获取请求还可以包括第一参数，第一参数用于构建包括第一锚点UPF的虚拟局域网络。
S1305、UDM向SMF发送SDM_获取响应(Get Response)。相应的，SMF接收来自UDM的SDM_获取响应。该SDM_获取响应包括第一APP实例的签约数据。
其中，第一APP实例的签约数据的相关描述可参考图12所述的实施例，在此不再赘述。
本申请实施例中，第一APP实例的签约数据中的默认的QoS参数例如可以包括5G QoS标识(5G QoS identifier，5QI)或者分配保持优先级(allocation and retention priority，ARP)等，本申请实施例对此不做具体限定。
进一步的，本申请实施例提供的应用接入网络的方法还可以包括如下步骤S1306-S1309：
S1306、SMF确定为该第一APP实例服务的锚点UPF。
需要说明的是，本申请实施例示例性的以步骤S1301中的第一锚点UPF为选定的为该第一APP实例服务的锚点UPF为例进行说明，在此统一说明，以下不再赘述。
一种可能的实现方式，本申请实施例中，SMF可以向NRF查询支持为APP实例建立PDU会话的UPF的信息。具体的，SMF向NRF发送查询请求，该查询请求中包括通过步骤S1303获取的第一APP实例的位置信息或者通过步骤S1305获取的第一APP实例的位置信息。进而，NRF向SMF发送支持为APP实例建立PDU会话的一个或多个UPF的信息。
其中，本申请实施例中，UPF的信息包括UPF的标识信息。示例性的，本申请实施例，UPF的标识信息例如可以是UPF的IP地址，本申请实施例对此不做具体限定。
一种可能的实现方式，本申请实施例中，UPF的信息还可以包括UPF的位置信息或者UPF的属性信息(如负荷信息)等，本申请实施例对此不做具体限定。
一种可能的实现方式，本申请实施例中，当NRF向SMF返回多个支持为APP实例建立PDU会话的UPF的信息时，SMF可以根据UPF的位置信息、UPF的属性信息、通过步骤S1303和/或步骤S1305获取的第一APP实例的位置信息、SSC模式、DNN、网络切片的标识信息中的至少一个确定为该第一APP实例服务的锚点UPF，具体可参考现有的SMF选择为终端设备服务的UPF的方式，在此不再赘述。
当然，本申请实施例中，若SMF无法从NRF获取支持为APP实例建立PDU会话的一个或多个UPF的信息，SMF也可以配置支持为APP实例建立PDU会话的UPF，如SMF可以将某个UPF确定为支持为APP实例建立PDU会话的UPF，本申请实施例对此不做具体限定。
S1307、SMF向选定的第一锚点UPF发送N4会话建立请求(N4session establishment request)。相应的，第一锚点UPF接收来自SMF的N4会话建立请求。该N4会话建立请求包括第一APP实例的标识信息，用于请求为第一APP实例建立PDU会话。
需要说明的是，本申请实施例中的N4会话建立请求仅是图12中第二消息的一种示例，第二消息还可以为其他，本申请实施例对此不做具体限定。
一种可能的实现方式，本申请实施例中，当步骤S1303中的Nsmf_PDU会话创建请求包括第一路径信息时，该N4会话建立请求还包括该第一路径信息。
一种可能的实现方式，本申请实施例中，当第一APP实例的签约数据包括默认的QoS参数时，该N4会话建立请求还可以包括根据该QoS参数确定的QoS策略信息，该QoS策略信息用于第一锚点UPF后续发送数据时使用，本申请实施例对此不做具体限定。
S1308、第一锚点UPF向SMF发送N4会话建立响应(N4session establishment response)。相应的，SMF接收来自第一锚点UPF的N4会话建立响应。其中，该N4会话建立响应包括会话建立结果，会话建立结果例如可以为成功或失败。
需要说明的是，本申请实施例中的N4会话建立响应仅是图12中第三消息的一种示例，第三消息还可以为其他，本申请实施例对此不做具体限定。
一种可能的实现方式，本申请实施例中，第一锚点UPF可以分配第二路径信息，该第二路径信息用于建立第一锚点UPF与AUEF之间的路径。进而，N4会话建立响应中可以包括第二路径信息。其中，第二路径信息的相关描述可参考图12所示的实施例，在此不再赘述。
一种可能的实现方式，本申请实施例中的第一锚点UPF还可以支持对该第一APP实例在5G网络内的路由策略发布和转发路径选择功能等，本申请实施例对此不做具体限定。
此外，本申请实施例中，SMF或者第一锚点UPF还可以为第一APP实例的会话分配第一地址。第一地址的相关描述可参考图12所示的实施例，在此不再赘述。
S1309、当SMF确定会话建立成功之后，SMF向第一APP实例所在的应用服务器发送Nsmf_PDU会话创建(PDU session create)响应。相应的，第一APP实例所在的应用服务器接收来自SMF的Nsmf_PDU会话创建响应。其中，该Nsmf_PDU会话创建响应包括SMF为第一APP实例分配的会话标识以及SMF或第一锚点UPF为第一APP实例的会话分配的第一地址。
需要说明的是，本申请实施例中的Nsmf_PDU会话创建响应仅是图12中第四消息的一种示例，第四消息还可以为其他，本申请实施例对此不做具体限定。
一种可能的实现方式，本申请实施例中，若步骤S1308中的N4会话建立响应中包括第二路径信息，则该Nsmf_PDU会话创建响应还可以包括第二路径信息。
一种可能的实现方式，本申请实施例中，在第一APP实例获取到第二路径信息，第一锚点UPF获取到第一路径信息的情况下，可以认为第一锚点UPF与第一APP实例内的AUEF之间的路径建立完成。
一种可能的实现方式，本申请实施例中，第一APP实例所在的应用服务器还可以根据SMF或第一锚点UPF为第一APP实例的会话分配的第一地址发布路由，本申请实施例对此不做具体限定。
上述步骤S1303-S1309给出了第一APP实例在5G网络中的会话建立流程。当然，在第一APP实例的状态发生变更时，也可以通过扩展Nsmf_PDU会话_更新(Update)服务或新的服务类型完成第一APP实例在5G网络中的会话更新流程；或者，在第一APP实例下线时，也可以通过扩展Nsmf_PDU会话_释放(Release)服务或新的服务类型完成第一APP实例在5G网络中的会话释放流程，本申请实施例在此不再赘述。
S1310、终端设备发起会话建立流程，相关实现可参考现有技术，在此不再赘述。本申请实施例中，以为终端设备服务的锚点UPF为第二锚点UPF为例进行说明。
一种可能的实现方式，本申请实施例中，在为第一APP实例和终端设备建立会话的过 程中，由于第一APP实例可以视为特殊的终端设备，因此UDM可以增加基于第一APP实例或终端设备的属性构建虚拟局域网络的功能。比如，UDM可以根据上述第一参数、与第一APP实例对应的应用信息或者第一APP实例的签约数据中的至少一个动态构建虚拟局域网络；或者，UDM可以根据UDM中第一APP实例和终端设备的签约数据中预置的虚拟网络标识构建虚拟局域网络。具体的虚拟局域网络的构建方式可参考图12所示的实施例，在此不再赘述。需要说明的是，上述由UDM基于第一APP实例或终端设备的属性构建虚拟局域网络的方式仅是一种可能的实现方式，本申请实施例中，在为第一APP实例和终端设备建立会话的过程中，也可以由其他网络功能或者网络实体基于相关属性实现虚拟局域网络的选择，本申请实施例对此不做具体限定。
其中，本申请实施例中，如果可以为第一APP实例和终端设备构建虚拟局域网络，则SMF可以将5G网络为属于同一个虚拟局域网络的终端设备与第一APP实例的会话分配的地址和N19隧道信息添加到同一个虚拟局域网络的转发策略集下，并下发到该虚拟局域网络下所有终端设备和第一APP实例所对应的UPF以实现虚拟局域网络层面的路由查询和转发处理，本申请实施例对此不作具体限定。N19隧道信息的相关描述可参考具体实施方式前序部分，在此不予赘述。
进一步的，当完成为终端设备建立会话以及为第一APP实例建立会话的流程之后，终端设备与APP实例之间即可构成一个可以实现应用业务即插即用的自组织网络，从而可以实现终端设备与第一APP实例所在的应用服务器之间的数据互访。下面分别以终端设备向第一APP实例所在的应用服务器发送第二数据、以及第一APP实例所在的应用服务器向终端设备发送第一数据为例进行说明。
其中，以可以为第一APP实例和终端设备构建虚拟局域网络，且终端设备向第一APP实例所在的应用服务器发送第二数据为例，则该应用接入网络的方法包括如下步骤：
S1311、终端设备向第二锚点UPF发送第二数据。相应的，第二锚点UPF接收来自终端设备的第二数据。其中，该第二数据包括源地址和目的地址，源地址是为终端设备建立会话的流程中核心网为终端设备的会话分配的第二地址，目的地址是为第一APP实例建立会话的流程中核心网为第一APP实例的会话分配的第一地址。
需要说明的是，本申请实施例中，终端设备可以通过I-UPF向第二锚点UPF发送第二数据，也可以直接向第二锚点UPF发送第二数据，本申请实施例对此不作具体限定。
S1312、第二锚点UPF根据目的地址，确定为第一APP实例服务的第一锚点UPF。
其中，本申请实施例中，第二锚点UPF可以查询目的地址是否属于终端设备所在的虚拟局域网络分配的地址范围内。当目的地址属于终端设备所在的虚拟局域网络分配的地址范围内时，第二锚点UPF可以进一步的根据目的地址确定为第一APP实例服务的第一锚点UPF。
S1313、第二锚点UPF通过第一锚点UPF与第二锚点UPF之间的N19隧道向第一锚点UPF发送第二数据。相应的，第一锚点UPF接收来自第二锚点UPF的第二数据。
其中，本申请实施例中，第二锚点UPF通过第一锚点UPF与第二锚点UPF之间的N19隧道向第一锚点UPF发送第二数据时，可以使用相应的N19隧道信息对第二数据进行封装，具体可参考现有的N19隧道的数据传输方式，在此不予赘述。
S1314、第一锚点UPF向第一APP实例所在的应用服务器发送第二数据。相应的，第一 APP实例所在的应用服务器接收来自第一锚点UPF的第二数据。
其中，本申请实施例中，第一锚点UPF通过第一锚点UPF与AUEF之间的路径向集成AUEF的第一APP实例所在的应用服务器发送第二数据时，可以使用上述第一路径信息和第二路径信息对第二数据进行封装，具体可参考现有数据传输方式，在此不再赘述。
需要说明的时，上述步骤S1311-S1314以可以为第一APP实例和终端设备构建虚拟局域网络为例进行说明。一种可能的实现方式，本申请实施例中，第二数据也可以不通过第一锚点UPF与第二锚点UPF之间的N19隧道进行传输。比如，当为第一APP实例建立会话的流程中，第一APP实例所在的应用服务器根据SMF或第一锚点UPF为第一APP实例的会话分配的第一地址发布路由，则本申请实施例中，第二锚点UPF接收第二数据之后，可以根据第一APP实例所在的应用服务器发布的第一地址按照现有的路由方式直接寻址到该应用服务器，进而第二锚点UPF可以向该应用服务器转发第二数据，本申请实施例对此不做具体限定。或者，比如，本申请实施例中，当为第一APP实例建立会话的流程中，第一锚点UPF支持对该第一APP实例在5G网络内的路由策略发布，则本申请实施例中，第二锚点UPF接收第二数据之后，可以根据第一锚点UPF对外发布的路由策略按照现有的路由方式直接寻址到第一锚点UPF，进而第二锚点UPF向第一锚点UPF发送该第二数据，由第一锚点UPF在接收到该第二数据之后向第一APP实例所在的应用服务器发送该第二数据，本申请实施例对此不做具体限定。
其中，以可以为第一APP实例和终端设备构建虚拟局域网络，且第一APP实例所在的应用服务器向终端设备发送第一数据为例，则该应用接入网络的方法包括如下步骤：
S1315、第一APP实例所在的应用服务器向第一锚点UPF发送第一数据。相应的，第一锚点UPF接收来自第一APP实例所在的应用服务器的第一数据。其中，该第一数据包括源地址和目的地址，源地址是为第一APP实例建立会话的流程中核心网为第一APP实例的会话分配的第一地址，目的地址是终端设备建立会话的流程中核心网为终端设备的会话分配的第二地址。
其中，本申请实施例中，集成AUEF的第一APP实例所在的应用服务器通过第一锚点UPF与AUEF之间的路径向第一锚点UPF发送第一数据时，可以使用上述第一路径信息和第二路径信息对第一数据进行封装，具体可参考现有的数据传输方式，在此不再赘述。
S1316、第一锚点UPF根据目的地址，确定为终端设备服务的第二锚点UPF。
其中，本申请实施例中，第一锚点UPF可以查询目的地址是否属于第一APP实例所在的虚拟局域网络分配的地址范围内。当目的地址属于第一APP实例所在的虚拟局域网络分配的地址范围内时，第一锚点UPF可以进一步的根据目的地址确定为终端设备服务的第二锚点UPF。
S1317、第一锚点UPF通过第一锚点UPF与第二锚点UPF之间的N19隧道向第二锚点UPF发送第一数据。相应的，第二锚点UPF接收来自第一锚点UPF的第一数据。
其中，本申请实施例中，第一锚点UPF通过第一锚点UPF与第二锚点UPF之间的N19隧道向第二锚点UPF发送第一数据时，可以使用相应的N19隧道信息对第一数据进行封装，具体可参考现有的N19隧道的数据传输方式，在此不予赘述。
S1318、第二锚点UPF向终端设备发送第一数据。相应的，终端设备接收来自第二锚点UPF的第一数据。
需要说明的是，本申请实施例中，第二锚点UPF可以通过I-UPF向终端设备发送第一数据，也可以直接向终端设备发送第一数据，本申请实施例对此不作具体限定。
需要说明的是，上述步骤S1315-S1318以可以为第一APP实例和终端设备构建虚拟局域网络为例进行说明。一种可能的实现方式，本申请实施例中，第一数据也可以不通过第一锚点UPF与第二锚点UPF之间的N19隧道进行传输。比如，当为终端设备建立会话的流程中，第二锚点UPF根据SMF或第二锚点UPF为终端设备的会话分配的第二地址发布路由，则本申请实施例中，第一APP实例所在的应用服务器可以根据第二锚点UPF发布的第二地址按照现有的路由方式直接寻址到第二锚点UPF，进而第二锚点UPF可以向终端设备转发第一数据，本申请实施例对此不做具体限定。
在本申请实施例中，由移动通信网络中的SMF和第一锚点UPF为第一APP实例建立会话，并在建立会话的过程中为第一APP实例的会话分配第一地址可知，第一应用实例对应的地址分配和管理、数据面的转发路径均在移动通信网络的控制范围内。也就是说，该方案可以将第一APP实例作为特殊的终端设备接入到5G网络中。由于第一APP实例为某个应用的具体运行实例，因此基于该方案，可以提升应用与移动通信网络之间数据交互的灵活性。进一步的，基于该方案，可以将应用纳入移动通信网络规划中以实现应用在移动通信系统中的即插即用，从而实现对应用业务的动态编排和路径寻优。这样有利于实现运营商和应用服务提供商之间的一种新的商业部署和合作模式。
其中，上述步骤S1300至S1318中SMF、应用服务器或者第一锚点UPF的动作可以由图11所示的通信装置1100中的处理器1101调用存储器1103中存储的应用程序代码以指令SMF、应用服务器或者第一锚点UPF执行，本实施例对此不作任何限制。
其次，以图7所示的通信系统应用于如图10所示的5G网络为例，在图12所示实施例的基础上，图14所示为本申请实施例提供的另一种应用接入网络的方法。该应用接入网络的方法中，在图13所示的实施例的基础流程上，为了避免对第一APP实例独立开发AUEF的大量适配工作，可以将AUEF与第一APP实例分开部署(如图6示例性的以由APP集成平台提供统一的AUEF为例进行示意)。同时结合原有的第一APP实例上线和下线流程，在第一APP实例上线或下线时，SMF/UPF支持通过AUEF将第一APP实例作为特殊终端设备直接接入到5G网络，支持为第一APP实例建立的会话(为方便说明，以下将为第一APP实例建立的会话简称为第一APP实例的会话)分配地址、建立路径等功能。示例性的，该应用接入网络的方法一种可能的实现方式包括如下步骤S1400-S1402：
S1400、SMF向NRF注册SMF是否支持为APP实例建立PDU会话。
步骤S1400的具体实现可参考图13所示的实施例中的步骤S1300，在此不再赘述。
S1401、第一锚点UPF向NRF注册第一锚点UPF是否支持为APP实例建立PDU会话。
步骤S1401的具体实现可参考图13所示的实施例中的步骤S1301，在此不再赘述。
S1402、AUEF所在的APP集成平台从NRF获取支持为APP实例建立PDU会话的一个或多个SMF的信息。
步骤S1402中AUEF所在的APP集成平台从NRF获取支持为APP实例建立PDU会话的一个或多个SMF的信息的方式可参考图13所示的实施例中的步骤S1302中第一APP实例所在的应用服务器从NRF获取支持为APP实例建立PDU会话的一个或多个SMF的信息的方式，区别比如在于将步骤S1302中的第一APP实例所在的应用服务器替换为步骤S1402中的 AUEF所在的APP集成平台，在此不再赘述。
进一步的，本申请实施例中，第一APP实例所在的应用服务器可以发起会话建立流程，包括如下步骤S1403-S1404：
S1403、第一APP实例在APP集成平台上线时，第一APP实例所在的应用服务器向AUEF所在的APP集成平台发送APP注册请求(APP register request)。相应的，AUEF所在的APP集成平台接收来自第一APP实例所在的应用服务器的APP注册请求。该APP注册请求包括与第一APP实例对应的应用信息。其中，应用信息的相关描述可参考图13所示的实施例，在此不再赘述。
S1404、APP集成平台的AUEF为第一APP实例分配第一APP实例的标识信息之后，向选定的支持为APP实例建立PDU会话的SMF发送Nsmf_PDU会话创建(PDU session create)请求。相应的，SMF接收来自AUEF所在的APP集成平台的Nsmf_PDU会话创建请求。该Nsmf_PDU会话创建请求包括第一APP实例的标识信息，用于请求为该第一APP实例建立PDU会话。
其中，第一APP实例的标识信息的相关描述可参考图12所示的实施例，在此不再赘述。
需要说明的是，本申请实施例示例性的以步骤S1400中的SMF为选定的支持为APP实例建立PDU会话的SMF为例进行说明，在此统一说明，以下不再赘述。
一种可能的实现方式，本申请实施例中，当NRF向AUEF所在的APP集成平台返回多个支持为APP实例建立PDU会话的SMF的信息时，AUEF所在的APP集成平台可以根据SMF的属性信息(如负荷信息)确定为该第一APP实例服务的SMF，也可以随机选择为该第一APP实例服务的SMF，本申请实施例对此不做具体限定。
一种可能的实现方式，本申请实施例中的Nsmf_PDU会话创建请求还可以包括与第一APP实例对应的应用信息。其中，应用信息的相关描述可参考图13所示的实施例，在此不再赘述。
一种可能的实现方式，本申请实施例中的Nsmf_PDU会话创建请求还可以包括第一路径信息，该第一路径信息用于建立第一锚点UPF与AUEF之间的路径，该第一锚点UPF是为该第一APP实例服务的锚点UPF。其中，第一路径信息的相关描述可参考图12所示的实施例，在此不再赘述。
一种可能的实现方式，本申请实施例中的Nsmf_PDU会话创建请求还可以包括第一参数，第一参数的相关描述可参考图12所述的实施例，在此不再赘述。
S1405-S1409、同图5所示的实施例中的步骤S1304-S1309，在此不再赘述。
S1410、当SMF确定会话建立成功之后，SMF向AUEF所在的APP集成平台发送Nsmf_PDU会话创建(PDU session create)响应。相应的，AUEF所在的APP集成平台接收来自SMF的Nsmf_PDU会话创建响应。其中，该Nsmf_PDU会话创建响应包括SMF为第一APP实例分配的会话标识以及SMF或第一锚点UPF为第一APP实例的会话分配的第一地址。
一种可能的实现方式，本申请实施例中，若步骤S1409中的N4会话建立响应中包括第二路径信息，则该Nsmf_PDU会话创建响应还可以包括第二路径信息。
一种可能的实现方式，本申请实施例中，在APP集成平台获取到第二路径信息，第一锚点UPF获取到第一路径信息的情况下，可以认为第一锚点UPF与APP集成平台内的AUEF之间的路径建立完成。
S1411、AUEF所在的APP集成平台向第一APP实例所在的应用服务器发送APP注册响应(APP register response)。相应的，第一APP实例所在的应用服务器接收来自AUEF所在的APP集成平台的APP注册响应。该APP注册响应包括SMF为第一APP实例分配的会话标识以及SMF或第一锚点UPF为第一APP实例的会话分配的第一地址。
一种可能的实现方式，本申请实施例中，第一APP实例所在的应用服务器还可以根据SMF或第一锚点UPF为APP实例的会话分配的第一地址发布路由，本申请实施例对此不做具体限定。
上述步骤S1403-S1411给出了第一APP实例在APP集成平台上线并且在5G网络中的会话建立流程。当然，在第一APP实例的状态发生变更时，第一APP实例所在的应用服务器可以向AUEF所在的APP集成平台发送APP注册更新，进而AUEF所在的APP集成平台可以通过扩展Nsmf_PDU会话_更新(Update)服务或新的服务类型完成第一APP实例在5G网络中的会话更新流程；或者，在第一APP实例下线时，AUEF所在的APP集成平台可以通过扩展Nsmf_PDU会话_释放(Release)服务或新的服务类型完成第一APP实例在5G网络中的会话释放流程，本申请实施例在此不再赘述。
S1412、终端设备发起会话建立流程，相关实现可参考现有技术，在此不再赘述。本申请实施例中，以为终端设备服务的锚点UPF为第二锚点UPF为例进行说明。
一种可能的实现方式，本申请实施例中，在为第一APP实例和终端设备建立会话的过程中，由于第一APP可以视为特殊的终端设备，因此UDM可以增加基于第一APP实例或终端设备的属性构建虚拟局域网络的功能。相关描述可参考图13所示的实施例，在此不再赘述。
进一步的，当完成为终端设备建立会话以及为第一APP实例建立会话的流程之后，终端设备与第一APP实例之间即可构成一个可以实现应用业务即插即用的自组织网络，从而可以实现终端设备与第一APP实例所在的应用服务器之间的数据互访。下面分别以终端设备向第一APP实例所在的应用服务器发送第二数据、以及第一APP实例所在的应用服务器向终端设备发送第一数据为例进行说明。
其中，以可以为第一APP实例和终端设备构建虚拟局域网络，且终端设备向第一APP实例所在的应用服务器发送第二数据为例，则该应用接入网络的方法包括如下步骤：
S1413-S1415、同图13所示的实施例中的步骤S1311-S1313，在此不再赘述。
S1416、第一锚点UPF通过第一锚点UPF与AUEF之间的路径向AUEF所在的APP集成平台发送第二数据。相应的，AUEF所在的APP集成平台接收来自第一锚点UPF的第二数据。
其中，本申请实施例中，第一锚点UPF通过第一锚点UPF与AUEF之间的路径向AUEF所在的APP集成平台发送第二数据时，可以使用上述第一路径信息和第二路径信息对第二数据进行封装，具体可参考现有的数据传输方式，在此不再赘述。
S1417、AUEF所在的APP集成平台向第一APP实例所在的应用服务器发送第二数据。相应的，第一APP实例所在的应用服务器接收来自AUEF所在的APP集成平台的第二数据。
需要说明的是，上述步骤S1413-S1417以可以为第一APP实例和终端设备构建虚拟局域网络为例进行说明。一种可能的实现方式，本申请实施例中，第二数据也可以不通过第一锚点UPF与第二锚点UPF之间的N19隧道进行传输。比如，当为第一APP实例建立会话的流程中，第一APP实例所在的应用服务器根据SMF或第一锚点UPF为第一APP实例的会话分 配的第一地址发布路由，则本申请实施例中，第二锚点UPF接收第二数据之后，可以根据第一APP实例所在的应用服务器发布的第一地址按照现有的路由方式直接寻址到该应用服务器，进而第二锚点UPF可以向该应用服务器转发第二数据，本申请实施例对此不做具体限定。或者，比如，本申请实施例中，当为第一APP实例建立会话的流程中，第一锚点UPF支持对第一APP实例在5G网络内的路由策略发布，则本申请实施例中，第二锚点UPF接收第二数据之后，可以根据第一锚点UPF对外发布的路由策略按照现有的路由方式直接寻址到第一锚点UPF，进而第二锚点UPF向第一锚点UPF发送该第二数据，由第一锚点UPF在接收到该第二数据之后通过AUEF所在的APP集成平台向第一APP实例所在的应用服务器发送该第二数据，本申请实施例对此不做具体限定。
其中，以可以为第一APP实例和终端设备构建虚拟局域网络，且第一APP实例所在的应用服务器向终端设备发送第一数据为例，则该应用接入网络的方法包括如下步骤：
S1418、第一APP实例所在的应用服务器向AUEF所在的APP集成平台发送第一数据。相应的，AUEF所在的APP集成平台接收来自第一APP实例所在的应用服务器的第一数据。其中，该第一数据包括源地址和目的地址，源地址是为第一APP实例建立会话的流程中核心网为第一APP实例的会话分配的第一地址，目的地址是终端设备建立会话的流程中核心网为终端设备的会话分配的第二地址。
S1419、AUEF所在的APP集成平台通过第一锚点UPF与AUEF之间的路径向第一锚点UPF发送第一数据。相应的，第一锚点UPF接收来自AUEF所在的APP集成平台的第一数据。
其中，本申请实施例中，AUEF所在的APP集成平台通过第一锚点UPF与AUEF之间的路径向第一锚点UPF发送第一数据时，可以使用上述第一路径信息和第二路径信息对第一数据进行封装，具体可参考现有的数据传输方式，在此不再赘述。
S1420-S1422、同图13所示的实施例中的步骤S1316-S1318，在此不再赘述。
需要说明的时，上述步骤S1418-S1422以可以为第一APP实例和终端设备构建虚拟局域网络为例进行说明。一种可能的实现方式，本申请实施例中，第一数据也可以不通过第一锚点UPF与第二锚点UPF之间的N19隧道进行传输。比如，当为终端设备建立会话的流程中，第二锚点UPF根据SMF或第二锚点UPF为终端设备的会话分配的第二地址发布路由，则本申请实施例中，第一APP实例所在的应用服务器可以根据第二锚点UPF发布的第二地址按照现有的路由方式直接寻址到第二锚点UPF，进而第二锚点UPF可以向终端设备转发第一数据，本申请实施例对此不做具体限定。
在本申请实施例中，由移动通信网络中的SMF和第一锚点UPF为第一APP实例建立会话，并在建立会话的过程中为第一APP实例的会话分配第一地址可知，第一应用实例对应的地址分配和管理、数据面的转发路径均在移动通信网络的控制范围内。也就是说，该方案可以将第一APP实例作为特殊的终端设备接入到5G网络中。由于第一APP实例为某个应用的具体运行实例，因此基于该方案，可以提升应用与移动通信网络之间数据交互的灵活性。进一步的，基于该方案，可以将应用纳入移动通信网络规划中以实现应用在移动通信系统中的即插即用，从而实现对应用业务的动态编排和路径寻优。这样有利于实现运营商和应用服务提供商之间的一种新的商业部署和合作模式。
其中，上述步骤S1400至S1422中SMF、APP集成平台或者第一锚点UPF的动作可以由图11所示的通信装置1100中的处理器1101调用存储器1103中存储的应用程序代码以指令 SMF、APP集成平台或者第一锚点UPF执行，本实施例对此不作任何限制。
可以理解的是，图12至图14所示的实施例中，由第一用户面功能实体实现的方法和/或步骤，也可以由可用于第一用户面功能实体的部件实现；由应用实例接入模块实现的方法和/或步骤，也可以由可用于应用实例接入模块的部件(例如芯片或者电路)实现；由会话管理功能实体实现的方法和/或步骤，也可以由可用于会话管理功能实体的部件(例如芯片或者电路)实现。
上述主要从各个网元之间交互的角度对本申请实施例提供的方案进行了介绍。相应的，本申请实施例还提供了通信装置，该通信装置可以为上述方法实施例中的会话管理功能实体，或者包含上述会话管理功能实体的装置，或者为可用于会话管理功能实体的部件。可以理解的是，该通信装置为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
图15示出了一种通信装置150的结构示意图。该通信装置150包括处理模块1502和收发模块1501。所述收发模块1501，也可以称为收发单元用以实现收发功能，例如可以是收发电路，收发机，收发器或者通信接口。
以通信装置150为上述方法实施例中的会话管理网元或者设置在该会话管理网元中的芯片或其他部件为例：
其中，收发模块1501，用于接收来自应用实例接入模块的第一消息，第一消息包括第一应用实例的标识信息，第一消息用于请求为第一应用实例建立第一连接。处理模块1502，用于确定为第一应用实例服务的第一用户面功能实体。收发模块1501，还用于向第一用户面功能实体发送第二消息，第二消息包括第一应用实例的标识信息，第二消息用于请求为第一应用实例建立第一连接。收发模块1501，还用于接收来自第一用户面功能实体的第三消息，第三消息包括第一连接的建立结果，其中，建立结果包括成功。收发模块1501，还用于向应用实例接入模块发送第四消息，第四消息包括核心网网元为第一连接分配的第一地址。
一种可能的实现方式，第一消息和第二消息还包括应用实例接入模块为第一连接分配的第一路径信息；第三消息和第四消息还包括第一用户面功能实体为第一连接分配的第二路径信息，其中，第一路径信息和第二路径信息用于建立第一连接中第一用户面功能实体和应用实例接入模块之间的第一路径。
一种可能的实现方式，核心网网元为第一用户面功能实体；第三消息还包括第一地址。
一种可能的实现方式，核心网网元为会话管理功能实体。
一种可能的实现方式，第二消息还包括第一地址，第一地址用于第一用户面功能实体发布路由。
一种可能的实现方式，第一消息还包括第一参数，第一参数用于确定为第一应用实例服务的第一用户面功能实体；或者第一参数用于构建包括第一用户面功能实体的 虚拟局域网络。
一种可能的实现方式，第一参数包括以下至少一个参数：第一应用实例的位置信息、SSC模式、第一连接对应的DNN或者第一连接所在的网络切片的标识信息。
一种可能的实现方式，第一消息还包括与第一应用实例对应的应用信息，应用信息用于构建包括第一用户面功能实体的虚拟局域网络。
一种可能的实现方式，收发模块1501，还用于向统一数据管理功能实体发送第五消息，第五消息包括第一应用实例的标识信息，第五消息用于请求获取第一应用实例的签约数据。收发模块1501，还用于接收来自统一数据管理功能实体的签约数据，其中，签约数据用于确定为第一应用实例服务的第一用户面功能实体；或者签约数据用于构建包括第一用户面功能实体的虚拟局域网络。
一种可能的实现方式，收发模块1501，还用于向网络存储功能实体注册该通信装置150支持为应用实例建立连接的功能。
以通信装置150为上述方法实施例中的应用实例接入模块或者设置在该应用实例接入模块中的芯片或其他部件为例：
其中，处理模块1502，用于确定为第一应用实例服务的会话管理功能实体。收发模块1501，用于向会话管理功能实体发送第一消息，第一消息包括第一应用实例的标识信息，第一消息用于请求为第一应用实例建立第一连接。收发模块1501，还用于接收来自会话管理功能实体的第四消息，第四消息包括核心网网元为第一连接分配的第一地址。
一种可能的实现方式，第一消息还包括通信装置为第一连接分配的第一路径信息；第四消息还包括第一用户面功能实体为第一连接分配的第二路径信息，其中，第一路径信息和第二路径信息用于建立第一连接中第一用户面功能实体和应用实例接入模块之间的第一路径，第一用户面功能实体是为第一应用实例服务的用户面功能实体。
一种可能的实现方式，收发模块1501，还用于从第一应用实例获取第一数据后，通过第一路径向第一用户面功能实体发送第一数据；或者，收发模块1501，还用于通过第一路径接收来自第一用户面功能实体的第二数据。
一种可能的实现方式，处理模块1502，还用于根据第一地址发布路由。
一种可能的实现方式，收发模块1501，还用于接收来自第二用户面功能实体的第二数据，其中，第二用户面功能实体是根据应用实例接入模块发布的路由寻址到应用实例接入模块的。
一种可能的实现方式，收发模块1501，还用于在向会话管理功能实体发送第一消息之前，接收来自第一应用实例的第六消息，第六消息包括与第一应用实例对应的应用信息，第六消息用于请求注册到应用实例接入模块。收发模块1501，还用于在接收来自会话管理功能实体的第四消息之后，向第一应用实例发送第一地址。
一种可能的实现方式，核心网网元为会话管理功能实体；或者，核心网网元为为第一应用实例服务的第一用户面功能实体。
一种可能的实现方式，第一消息还包括第一参数，第一参数用于确定为第一应用实例服务的第一用户面功能实体；或者第一参数用于构建包括第一用户面功能实体的虚拟局域网络。
一种可能的实现方式，第一参数包括以下至少一个参数：第一应用实例的位置信息、SSC模式、第一连接对应的DNN或者第一连接所在的网络切片的标识信息。
一种可能的实现方式，第一消息还包括与第一应用实例对应的应用信息，应用信息用于构建包括第一用户面功能实体的虚拟局域网络，第一用户面功能实体是为第一应用实例服务的用户面功能实体。
一种可能的实现方式，处理模块1502，用于确定为第一应用实例服务的会话管理功能实体，包括：用于从网络存储功能实体获取支持为应用实例建立连接的一个或多个会话管理功能实体的信息；根据一个或多个会话管理功能实体的信息，确定为第一应用实例服务的会话管理功能实体。
以通信装置150为上述方法实施例中的第一用户面功能实体或者设置在该第一用户面功能实体中的芯片或其他部件为例：
其中，收发模块1501，用于接收来自会话管理功能实体的第二消息，第二消息包括第一应用实例的标识信息，第二消息用于请求为第一应用实例建立第一连接。收发模块1501，还用于向会话管理功能实体发送第三消息，第三消息包括第一连接的建立结果，其中，建立结果包括成功或失败。
一种可能的实现方式，第二消息还包括应用实例接入模块为第一连接分配的第一路径信息；第三消息还包括通信装置为第一连接分配的第二路径信息，其中，第一路径信息和第二路径信息用于建立第一连接中第一用户面功能实体和应用实例接入模块之间的第一路径。
一种可能的实现方式，第三消息还包括通信装置为第一连接分配的第一地址。
一种可能的实现方式，第二消息还包括会话管理功能实体为第一连接分配的第一地址。
一种可能的实现方式，处理模块1502，用于根据第一地址发布路由。
一种可能的实现方式，收发模块1501，还用于向网络存储功能实体注册该通信装置150支持为应用实例建立连接的功能。
一种可能的实现方式，收发模块1501，还用于通过应用实例接入模块接收来自第一应用实例的第一数据；收发模块1501，还用于向第二用户面功能实体发送第一数据，第二用户面功能实体是为终端设备服务的用户面功能实体。
一种可能的实现方式，收发模块1501，还用于接收来自第二用户面功能实体的第二数据，第二用户面功能实体是为终端设备服务的用户面功能实体。收发模块1501，还用于通过应用实例接入模块向第一应用实例发送第二数据。一种可能的实现方式，第二用户面功能实体是根据第一用户面功能实体发布的路由寻址到该第一用户面功能实体的。
其中，上述方法实施例涉及的各步骤的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
在本实施例中，该通信装置150以采用集成的方式划分各个功能模块的形式来呈现。这里的“模块”可以指特定ASIC，电路，执行一个或多个软件或固件程序的处理器和存储器，集成逻辑电路，和/或其他可以提供上述功能的器件。在一个简单的实施例中，本领域的技术人员可以想到该通信装置150可以采用图11所示的通信装置1100的形式。
比如，图11所示的通信装置1100中的处理器1101可以通过调用存储器1103中存储的计算机执行指令，使得通信装置1100执行上述方法实施例中的应用接入网络的方法。
具体的，图15中的收发模块1501和处理模块1502的功能/实现过程可以通过图11所示的通信装置1100中的处理器1101调用存储器1103中存储的计算机执行指令来实现。或者，图15中的处理模块1502的功能/实现过程可以通过图11所示的通信装置1100中的处理器1101调用存储器1103中存储的计算机执行指令来实现，图15中的收发模块1501的功能/实现过程可以通过图11中所示的通信装置1100中的通信接口1104来实现。
由于本实施例提供的通信装置150可执行上述应用接入网络的方法，因此其所能获得的技术效果可参考上述方法实施例，在此不再赘述。
需要说明的是，以上模块或单元的一个或多个可以软件、硬件或二者结合来实现。当以上任一模块或单元以软件实现的时候，所述软件以计算机程序指令的方式存在，并被存储在存储器中，处理器可以用于执行所述程序指令并实现以上方法流程。该处理器可以内置于SoC(片上系统)或ASIC，也可是一个独立的半导体芯片。该处理器内处理用于执行软件指令以进行运算或处理的核外，还可进一步包括必要的硬件加速器，如现场可编程门阵列(field programmable gate array，FPGA)、PLD(可编程逻辑器件)、或者实现专用逻辑运算的逻辑电路。
当以上模块或单元以硬件实现的时候，该硬件可以是CPU、微处理器、数字信号处理(digital signal processing，DSP)芯片、微控制单元(microcontroller unit，MCU)、人工智能处理器、ASIC、SoC、FPGA、PLD、专用数字电路、硬件加速器或非集成的分立器件中的任一个或任一组合，其可以运行必要的软件或不依赖于软件以执行以上方法流程。
一种可能的实现方式，本申请实施例还提供了一种通信装置(例如，该通信装置可以是芯片或芯片系统)，该通信装置包括处理器，用于实现上述任一方法实施例中的方法。在一种可能的实现方式中，该通信装置还包括存储器。该存储器，用于保存必要的程序指令和数据，处理器可以调用存储器中存储的程序代码以指令该通信装置执行上述任一方法实施例中的方法。当然，存储器也可以不在该通信装置中。该通信装置是芯片系统时，可以由芯片构成，也可以包含芯片和其他分立器件，本申请实施例对此不作具体限定。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件程序实现时，可以全部或部分地以计算机程序产品的形式来实现。该计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或者数据中心通过有线(例如同轴电缆、光纤、数字用户线(digital subscriber line，DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可以用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)，光介质(例如，DVD)、或者半导体介质(例如固态硬盘(solid state disk，SSD))等。
尽管在此结合各实施例对本申请进行了描述，然而，在实施所要求保护的本申请过程中，本领域技术人员通过查看所述附图、公开内容、以及所附权利要求书，可理解并实现所述公开实施例的其他变化。在权利要求中，“包括”(comprising)一词不排除其他组成部 分或步骤，“一”或“一个”不排除多个的情况。单个处理器或其他单元可以实现权利要求中列举的若干项功能。相互不同的从属权利要求中记载了某些措施，但这并不表示这些措施不能组合起来产生良好的效果。
尽管结合具体特征及其实施例对本申请进行了描述，显而易见的，在不脱离本申请的精神和范围的情况下，可对其进行各种修改和组合。相应地，本说明书和附图仅仅是所附权利要求所界定的本申请的示例性说明，且视为已覆盖本申请范围内的任意和所有修改、变化、组合或等同物。显然，本领域的技术人员可以对本申请进行各种改动和变型而不脱离本申请的精神和范围。这样，倘若本申请的这些修改和变型属于本申请权利要求及其等同技术的范围之内，则本申请也意图包含这些改动和变型在内。

Claims (28)

  1. 一种应用接入网络的方法，其特征在于，所述方法包括：
    会话管理功能实体接收来自应用实例接入模块的第一消息，所述第一消息包括第一应用实例的标识信息，所述第一消息用于请求为所述第一应用实例建立第一连接；
    所述会话管理功能实体确定为所述第一应用实例服务的第一用户面功能实体；
    所述会话管理功能实体向所述第一用户面功能实体发送第二消息，所述第二消息包括所述第一应用实例的标识信息，所述第二消息用于请求为所述第一应用实例建立所述第一连接；
    所述会话管理功能实体接收来自所述第一用户面功能实体的第三消息，所述第三消息包括所述第一连接的建立结果，其中，所述建立结果包括成功；
    所述会话管理功能实体向所述应用实例接入模块发送第四消息，所述第四消息包括核心网网元为所述第一连接分配的第一地址。
  2. 根据权利要求1所述的方法，其特征在于，所述第一消息和所述第二消息还包括所述应用实例接入模块为所述第一连接分配的第一路径信息；所述第三消息和所述第四消息还包括所述第一用户面功能实体为所述第一连接分配的第二路径信息，其中，所述第一路径信息和所述第二路径信息用于建立所述第一连接中所述第一用户面功能实体和所述应用实例接入模块之间的第一路径。
  3. 根据权利要求1或2所述的方法，其特征在于，所述核心网网元为所述第一用户面功能实体；所述第三消息还包括所述第一地址。
  4. 根据权利要求1或2所述的方法，其特征在于，所述核心网网元为所述会话管理功能实体。
  5. 根据权利要求4所述的方法，其特征在于，所述第二消息还包括所述第一地址，所述第一地址用于所述第一用户面功能实体发布路由。
  6. 根据权利要求1-5任一项所述的方法，其特征在于，所述第一消息还包括第一参数，所述第一参数用于确定为所述第一应用实例服务的所述第一用户面功能实体；或者所述第一参数用于构建包括所述第一用户面功能实体的虚拟局域网络。
  7. 根据权利要求6所述的方法，其特征在于，所述第一参数包括以下至少一个参数：
    所述第一应用实例的位置信息、会话和业务连续性SSC模式、所述第一连接对应的数据网络名称DNN或者所述第一连接所在的网络切片的标识信息。
  8. 根据权利要求1-7任一项所述的方法，其特征在于，所述第一消息还包括与所述第一应用实例对应的应用信息，所述应用信息用于构建包括所述第一用户面功能实体的虚拟局域网络。
  9. 根据权利要求1-8任一项所述的方法，其特征在于，所述方法还包括：
    所述会话管理功能实体向统一数据管理功能实体发送第五消息，所述第五消息包括所述第一应用实例的标识信息，所述第五消息用于请求获取所述第一应用实例的签约数据；
    所述会话管理功能实体接收来自所述统一数据管理功能实体的所述签约数据，其中，所述签约数据用于确定为所述第一应用实例服务的所述第一用户面功能实体；或 者所述签约数据用于构建包括所述第一用户面功能实体的虚拟局域网络。
  10. 根据权利要求1-9任一项所述的方法，其特征在于，所述方法还包括：
    所述会话管理功能实体向网络存储功能实体注册所述会话管理功能实体支持为应用实例建立连接的功能。
  11. 一种通信装置，所述通信装置为会话管理功能实体或者应用于所述会话管理功能实体中的模块，其特征在于，所述通信装置包括：收发模块和处理模块；
    所述收发模块，用于接收来自应用实例接入模块的第一消息，所述第一消息包括第一应用实例的标识信息，所述第一消息用于请求为所述第一应用实例建立第一连接；
    所述处理模块，用于确定为所述第一应用实例服务的第一用户面功能实体；
    所述收发模块，还用于向所述第一用户面功能实体发送第二消息，所述第二消息包括所述第一应用实例的标识信息，所述第二消息用于请求为所述第一应用实例建立所述第一连接；
    所述收发模块，还用于接收来自所述第一用户面功能实体的第三消息，所述第三消息包括所述第一连接的建立结果，其中，所述建立结果包括成功；
    所述收发模块，还用于向所述应用实例接入模块发送第四消息，所述第四消息包括核心网网元为所述第一连接分配的第一地址。
  12. 根据权利要求11所述的通信装置，其特征在于，所述第一消息和所述第二消息还包括所述应用实例接入模块为所述第一连接分配的第一路径信息；所述第三消息和所述第四消息还包括所述第一用户面功能实体为所述第一连接分配的第二路径信息，其中，所述第一路径信息和所述第二路径信息用于建立所述第一连接中所述第一用户面功能实体和所述应用实例接入模块之间的第一路径。
  13. 根据权利要求11或12所述的通信装置，其特征在于，所述核心网网元为所述第一用户面功能实体；所述第三消息还包括所述第一地址。
  14. 根据权利要求11或12所述的通信装置，其特征在于，所述核心网网元为所述会话管理功能实体。
  15. 根据权利要求14所述的通信装置，其特征在于，所述第二消息还包括所述第一地址，所述第一地址用于所述第一用户面功能实体发布路由。
  16. 根据权利要求11-15任一项所述的通信装置，其特征在于，所述第一消息还包括第一参数，所述第一参数用于确定为所述第一应用实例服务的所述第一用户面功能实体；或者所述第一参数用于构建包括所述第一用户面功能实体的虚拟局域网络。
  17. 根据权利要求16所述的通信装置，其特征在于，所述第一参数包括以下至少一个参数：
    所述第一应用实例的位置信息、会话和业务连续性SSC模式、所述第一连接对应的数据网络名称DNN或者所述第一连接所在的网络切片的标识信息。
  18. 根据权利要求11-17任一项所述的通信装置，其特征在于，所述第一消息还包括与所述第一应用实例对应的应用信息，所述应用信息用于构建包括所述第一用户面功能实体的虚拟局域网络。
  19. 根据权利要求11-18任一项所述的通信装置，其特征在于，
    所述收发模块，还用于向统一数据管理功能实体发送第五消息，所述第五消息包 括所述第一应用实例的标识信息，所述第五消息用于请求获取所述第一应用实例的签约数据；
    所述收发模块，还用于接收来自所述统一数据管理功能实体的所述签约数据，其中，所述签约数据用于确定为所述第一应用实例服务的所述第一用户面功能实体；或者所述签约数据用于构建包括所述第一用户面功能实体的虚拟局域网络。
  20. 根据权利要求11-19任一项所述的通信装置，其特征在于，
    所述收发模块，还用于向网络存储功能实体注册所述通信装置支持为应用实例建立连接的功能。
  21. 一种通信装置，其特征在于，包括至少一个处理器；
    所述处理器用于与存储器耦合，并读取所述存储器中存储的计算机指令之后，根据所述计算机指令执行权利要求1-10中任一项所述的方法。
  22. 根据权利要求21所述的通信装置，其特征在于，所述通信装置还包括通信接口；
    所述通信接口，用于与其他通信装置进行通信。
  23. 根据权利要求21或22所述的通信装置，其特征在于，所述通信装置还包括存储器；
    所述存储器，用于存储所述计算机指令。
  24. 根据权利要求21或22所述的通信装置，其特征在于，所述通信装置为芯片或芯片系统。
  25. 一种计算机可读存储介质，其特征在于，其上存储有计算机程序，当所述计算机程序被计算机执行时使得所述计算机执行权利要求1-10中任一项所述的方法。
  26. 一种计算机程序产品，其特征在于，包括：指令，当所述计算机程序产品在计算机上运行时，使得计算机执行权利要求1-10中任一项所述的方法。
  27. 一种通信系统，其特征在于，所述通信系统包括会话管理功能实体和第一用户面功能实体；
    所述会话管理功能实体，用于接收来自应用实例接入模块的第一消息，所述第一消息包括第一应用实例的标识信息，所述第一消息用于请求为所述第一应用实例建立第一连接；
    所述会话管理功能实体，还用于向所述第一用户面功能实体发送第二消息，所述第二消息包括所述第一应用实例的标识信息，所述第二消息用于请求为所述第一应用实例建立所述第一连接；
    所述第一用户面功能实体，用于接收来自所述会话管理功能实体的所述第二消息，并向所述会话管理功能实体发送第三消息，所述第三消息包括所述第一连接的建立结果，其中，所述建立结果包括成功；
    所述会话管理功能实体，还用于向所述应用实例接入模块发送第四消息，所述第四消息包括核心网网元为所述第一连接分配的第一地址。
  28. 根据权利要求27所述的通信系统，其特征在于，所述通信系统还包括所述应用实例接入模块；
    所述应用实例接入模块，用于向所述会话管理功能实体发送所述第一消息；
    所述应用实例接入模块，还用于接收来自所述会话管理功能实体的所述第四消息。
PCT/CN2021/126843 2020-10-31 2021-10-27 应用接入网络的方法、装置及系统 WO2022089503A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP21885230.9A EP4213576A4 (en) 2020-10-31 2021-10-27 METHOD, APPARATUS AND SYSTEM FOR ALLOWING AN APPLICATION TO ACCESS A NETWORK
JP2023521575A JP7547701B2 (ja) 2020-10-31 2021-10-27 アプリケーションがネットワーク、装置、およびシステムにアクセスするための方法
US18/310,236 US20230319147A1 (en) 2020-10-31 2023-05-01 Method for application to access network, apparatus, and system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202011197417.3A CN114449585A (zh) 2020-10-31 2020-10-31 应用接入网络的方法、装置及系统
CN202011197417.3 2020-10-31

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/310,236 Continuation US20230319147A1 (en) 2020-10-31 2023-05-01 Method for application to access network, apparatus, and system

Publications (1)

Publication Number Publication Date
WO2022089503A1 true WO2022089503A1 (zh) 2022-05-05

Family

ID=81357756

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/126843 WO2022089503A1 (zh) 2020-10-31 2021-10-27 应用接入网络的方法、装置及系统

Country Status (5)

Country Link
US (1) US20230319147A1 (zh)
EP (1) EP4213576A4 (zh)
JP (1) JP7547701B2 (zh)
CN (1) CN114449585A (zh)
WO (1) WO2022089503A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115550288B (zh) * 2022-11-29 2023-02-28 广东省新一代通信与网络创新研究院 一种以太网数据流转发的方法及系统

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110612742A (zh) * 2017-05-08 2019-12-24 三星电子株式会社 用于支持5g蜂窝网络的会话连续性的方法和装置
CN110636639A (zh) * 2018-06-25 2019-12-31 大唐移动通信设备有限公司 一种会话管理方法及装置
US20200092423A1 (en) * 2018-09-13 2020-03-19 Weihua QIAO Charging Control with SMF
US20200120446A1 (en) * 2018-10-16 2020-04-16 Cisco Technology, Inc. Methods and apparatus for selecting network resources for ue sessions based on locations of multi-access edge computing (mec) resources and applications
US10638400B1 (en) * 2018-10-24 2020-04-28 Syniverse Technologies, Llc Systems and methods of optimal wireless traffic routing

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111837371A (zh) 2018-01-26 2020-10-27 Idac控股公司 基于增强mptcp的应用移动性
WO2019179634A1 (en) 2018-03-23 2019-09-26 Nokia Solutions And Networks Oy Method and apparatus for dynamic network address translation
WO2019210966A1 (en) 2018-05-03 2019-11-07 Huawei Technologies Co., Ltd. Client device, network control node and upf for transmission and reception of streams of data packets in multi-connectivity
US10931586B2 (en) 2018-10-30 2021-02-23 Verizon Patent And Licensing Inc. Method and system for predictive edge resources

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110612742A (zh) * 2017-05-08 2019-12-24 三星电子株式会社 用于支持5g蜂窝网络的会话连续性的方法和装置
CN110636639A (zh) * 2018-06-25 2019-12-31 大唐移动通信设备有限公司 一种会话管理方法及装置
US20200092423A1 (en) * 2018-09-13 2020-03-19 Weihua QIAO Charging Control with SMF
US20200120446A1 (en) * 2018-10-16 2020-04-16 Cisco Technology, Inc. Methods and apparatus for selecting network resources for ue sessions based on locations of multi-access edge computing (mec) resources and applications
US10638400B1 (en) * 2018-10-24 2020-04-28 Syniverse Technologies, Llc Systems and methods of optimal wireless traffic routing

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
HUAWEI, CATT, CHINA MOBILE, LGE: "KI #16: Evaluation Update", 3GPP DRAFT; S2-2006917, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. e-meeting; 20201012 - 20201023, 2 October 2020 (2020-10-02), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051938022 *
HUAWEI, CATT, CHINA MOBILE: "KI #16, Sol# 31: Update Sol# 31 merging with Sol# 48, 49, 50 and 51", 3GPP DRAFT; S2-2006915, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. SA WG2, no. e-meeting; 20201012 - 20201023, 2 October 2020 (2020-10-02), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051938020 *
See also references of EP4213576A4

Also Published As

Publication number Publication date
EP4213576A1 (en) 2023-07-19
JP2023547051A (ja) 2023-11-09
US20230319147A1 (en) 2023-10-05
EP4213576A4 (en) 2024-04-03
JP7547701B2 (ja) 2024-09-10
CN114449585A (zh) 2022-05-06

Similar Documents

Publication Publication Date Title
US12015503B2 (en) Virtual network communication method, device, and system
JP6995189B2 (ja) データ伝送方法、デバイス、およびシステム
US11432366B2 (en) Session management method, device, and system
US12041516B2 (en) Multicast communication method, and apparatus and system
US11812496B2 (en) User group session management method and apparatus
US20220346190A1 (en) Session Management Method, Device, and System
US20200329514A1 (en) Session establishment method and system, and device
US11818641B2 (en) Local area network communication method, device, and system
WO2023011217A1 (zh) 一种通信方法及装置
WO2019120073A1 (zh) 数据传输方法、设备及系统
WO2022021435A1 (zh) 数据传输方法、设备及存储介质
US20220263879A1 (en) Multicast session establishment method and network device
WO2020001319A1 (zh) 动态组网方法、设备及系统
US20230319147A1 (en) Method for application to access network, apparatus, and system
WO2022022322A1 (zh) 访问本地网络的方法和装置
WO2021169683A1 (zh) 一种通信的方法及装置
JP2023541662A (ja) データステアリング方法および装置
RU2783350C2 (ru) Способ управления сеансом группы пользователей и устройство
WO2023050781A1 (zh) 一种通信方法及通信装置

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: 21885230

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2023521575

Country of ref document: JP

ENP Entry into the national phase

Ref document number: 2021885230

Country of ref document: EP

Effective date: 20230414

NENP Non-entry into the national phase

Ref country code: DE