Communication method and apparatus

Abstract

The present application relates to the technical field of communications. Provided are a communication method and apparatus. The method comprises: acquiring a request of a first service; sending a first message to a second network function, wherein the first message is used for requesting resource information of a first session of the first service; and receiving the resource information of the first session from the second network function. In the present application, a network function is split into a first network function and a second network function. The first network function is responsible for receiving a request of a first service, the request of the first service is from a terminal or other network functions, and the first network function is used for maintaining the state of a requester of the first service and the state of the first service, for example, context information regarding the state of the requester of the first service and the state of the first service. The second network function does not need to be concerned with information of the terminal or other requesters of the first service, but only needs to provide, on the basis of a request of the first network function, session resource information required by the service. On this basis, the execution of a service is decoupled from the state of a user, thereby simplifying the upgrade and maintenance of network functions.

Description

A communication method and apparatus

[0001] Cross-reference to related applications

[0002] This application claims priority to Chinese Patent Application No. 202510124932.5, filed on January 26, 2025, entitled "A Communication Method and Apparatus", the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application relates to the field of communication technology, and in particular to a communication method and apparatus. Background Technology

[0004] In current mobile networks, network functions may be responsible for both user connection management and resource allocation for services. For example, in 5G networks, the Session Management Function (SMF) is responsible for user equipment (UE) session management and user plane transmission resource configuration. The Access and Mobility Management Function (AMF) is responsible for session access management. The SMF context maintains a mapping between the AMF identifier and the UE's Protocol Data Unit (PDU) session identifier. The AMF context maintains a mapping between the SMF identifier and the UE's PDU session identifier. Different network functions are associated based on user state, and service execution is coupled with user state, which is detrimental to network function upgrades and maintenance. Summary of the Invention

[0005] This application provides a communication method and apparatus to decouple the execution of services from the user's state and reduce the complexity of network function upgrades and maintenance.

[0006] Firstly, this application provides a communication method that can be executed through a first network function. The first network function can be the first network function itself, a component within the first network function (e.g., a processor, chip, or chip system), or a logic module or software that implements all or part of the first network function. This application does not specifically limit the scope of the method.

[0007] Obtain a request for a first service; send a first message to a second network function, the first message being used to request resource information of a first session of the first service; receive a second message from the second network function, the second message including: resource information of the first session, the resource information of the first session including one or more of the following: port information of the user plane function associated with the first session, address information of the user plane function associated with the first session, or address information of the first session.

[0008] This application restructures network functions into a first network function and a second network function. The first network function is responsible for receiving requests from a first service, which originate from a terminal or other network functions. The first network function maintains the state of the requester and the first service, such as the context information of the requester and the first service. The second network function provides corresponding session resource information on demand based on different services. The second network function does not need to concern itself with the information of the terminal or other requesters of the first service; it only needs to provide the session resource information required by the service based on the request from the first network function. The first network function provides direct connection services to the user; for example, it can manage all session service requests from the terminal and manage session context. Based on this, service execution and user state are decoupled, and in service scenarios where user state does not need to be distinguished, the upgrade and maintenance of network functions are also simpler.

[0009] In one possible approach, the first message includes first information, which indicates the session parameter information that the resource information of the first session needs to support.

[0010] Based on this, the second network function can clearly provide the first network function with the corresponding session resource information.

[0011] In one possible manner, the first information includes one or more of the following: network information, session policies, or session capabilities.

[0012] In one possible approach, the first network function obtains the address of the second network function based on the request of the first service.

[0013] Within the same network, there may be one first network function and multiple second network functions. After the first network function obtains a request for the first service, it can usually obtain relevant information about the first service. Based on this, the first network function can obtain the address of the second network function that can provide the resource information of the first session required by the first service.

[0014] In one possible approach, a first network function acquires second information, which is used to indicate subscription information for a first service and / or policy information, which is used to determine the session policy associated with the resource information of the first session.

[0015] Based on the second information, obtain session resource information that meets the first business requirement.

[0016] In one possible approach, the first network function obtains the processing rules for the first session based on the session policy and the second message; sends a third message to the second network function, the third message being used to request configuration of the first session, the third message including: the processing rules for the first session; and receives a configuration response message for the first session from the second network function.

[0017] In one possible approach, the first network function sends a fourth message requesting the service resources for creating the first service; and receives information from the network function executing the first service.

[0018] The network function that meets the execution requirements of the first service is selected based on the fourth message.

[0019] In one possible manner, the fourth message may also include one or more of the following:

[0020] The processing strategy for the first service, the network information for the first service, and the capability information required for the first service.

[0021] Secondly, this application provides a communication method that can be executed through a second network function. This second network function can be the second network function itself, a component within the second network function (e.g., a processor, chip, or chip system), or a logic module or software that implements all or part of the second network function. This application does not specifically limit the scope of the method.

[0022] Receive a first message from a first network function, the first message being used to request resource information for a first session of a first service; send a second message to the first network function, the second message including: resource information of the first session, the resource information of the first session including one or more of the following: port information of the user plane function associated with the first session, address information of the user plane function associated with the first session, or address information of the first session.

[0023] In one possible approach, the first message includes first information, which indicates the session parameter information that the resource information of the first session needs to support.

[0024] In one possible approach, the first information may also include one or more of the following:

[0025] Network information, session policies, or session capabilities.

[0026] In one possible approach, the second network function receives a third message from the first network function, the third message being used to request configuration of the first session, the third message including: processing rules for the first session; and sending a configuration response message for the first session to the first network function.

[0027] Thirdly, embodiments of this application provide a communication device, which can be a first network function and a second network function. The communication device has the functions to implement the first to second aspects described above. For example, the communication device includes modules, units, or means that perform the steps involved in the first to second aspects. The functions, units, or means can be implemented by software, hardware, or hardware executing corresponding software.

[0028] In one possible design, the communication device includes a processing unit and a transceiver unit. The transceiver unit can be used to send and receive signals to enable communication between the communication device and other devices. For example, the processing unit can be used to perform some internal operations of the communication device. The transceiver unit can be called an input / output unit, a communication unit, etc., and can be a transceiver; the processing unit can be a processor. When the communication device is a module (e.g., a chip) in a communication device, the transceiver unit can be an input / output interface, input / output circuit, or input / output pins, etc., and can also be called an interface, communication interface, or interface circuit, etc.; the processing unit can be a processor, processing circuit, or logic circuit, etc.

[0029] In another possible design, the communication device includes a processor and may further include a transceiver for transmitting and receiving signals. The processor executes program instructions to perform the methods in any of the possible designs or implementations of the first to second aspects described above. The communication device may also include one or more memories coupled to the processor, which may store necessary computer programs or instructions for implementing the functions involved in the first to second aspects described above. The processor can execute the computer programs or instructions stored in the memory, and when the computer programs or instructions are executed, the communication device implements the methods in any of the possible designs or implementations of the first to second aspects described above.

[0030] In another possible design, the communication device includes a processor that can be coupled to a memory. The memory can store necessary computer programs or instructions for implementing the functions described in the first to second aspects above. The processor can execute the computer programs or instructions stored in the memory, causing the communication device to implement the methods in any possible design or implementation of the first to second aspects above, when the computer programs or instructions are executed.

[0031] In another possible design, the communication device includes a processor and an interface circuit, wherein the processor is used to communicate with other devices through the interface circuit and to perform the methods in any possible design or implementation of the first to second aspects described above.

[0032] In one possible design, the communication device is a chip or chip system.

[0033] Understandably, in the third aspect described above, the processor can be implemented in hardware or software. When implemented in hardware, the processor can be a logic circuit, integrated circuit, etc.; when implemented in software, the processor can be a general-purpose processor that reads software code stored in memory. Furthermore, there can be one or more processors, and one or more memories. The memory can be integrated with the processor or separated from it. In specific implementations, the memory can be integrated with the processor on the same chip or disposed on different chips. This application does not limit the type of memory or the arrangement of the memory and processor.

[0034] Fourthly, embodiments of this application provide a communication system including the aforementioned first network function and second network function. The first network function is used to execute the method in the first aspect, and the second network function is used to execute the method in the second aspect. Furthermore, it should be noted that in each aspect, there may be processes executed interactively by multiple devices or network elements; the corresponding processes cannot be executed by a single device or network element. Instead, they are mainly executed through the interaction of corresponding devices or network elements, which will not be elaborated upon here.

[0035] Fifthly, this application provides a chip system including a processor and potentially a memory, for implementing the methods described in the first to second aspects above. The chip system may be composed of chips or may include chips and other discrete devices.

[0036] Sixthly, this application also provides a computer-readable storage medium storing computer-readable instructions that, when executed on a computer, cause the computer to perform the methods described in the first to second aspects.

[0037] In a seventh aspect, this application provides a computer program product comprising a computer program or instructions, which, when run on a computer, causes the computer to perform the methods of the embodiments of the first to second aspects described above. Attached Figure Description

[0038] Figure 1 shows a schematic diagram of a communication system provided in an embodiment of this application;

[0039] Figure 2 shows a schematic diagram of a network function provided in an embodiment of this application;

[0040] Figure 3 shows a flowchart of a communication method provided in an embodiment of this application;

[0041] Figures 4 to 6 show schematic flowcharts of a communication method provided in an embodiment of this application;

[0042] Figure 7 shows a schematic diagram of the communication device provided in an embodiment of this application;

[0043] Figure 8 shows a schematic diagram of the communication device provided in an embodiment of this application;

[0044] Figure 9 shows a schematic diagram of the structure of the communication device provided in an embodiment of this application. Detailed Implementation

[0045] To make the objectives, technical solutions, and advantages of this application clearer, a further detailed description of this application will be provided below in conjunction with the accompanying drawings. The specific operational methods in the method embodiments can also be applied to the device embodiments or system embodiments. In the description of this application, unless otherwise stated, "multiple" means two or more. Therefore, implementations of the device and method can be referred to mutually, and repeated details will not be repeated.

[0046] To address the challenges of wireless broadband technology and maintain the leading edge of the 3rd Generation Partnership Project (3GPP) network, the 3GPP standards group developed the 5G standard. th This architecture supports not only radio access technologies defined by the 3GPP standards group (such as Long Term Evolution (LTE) and 5G Radio Access Network (RAN)) to access the 5G core network (CN), but also supports access to the core network using non-3GPP access technologies through non-3GPP interworking functions (N3IWF) or next-generation packet data gateways (ngPDG).

[0047] Figure 1 illustrates a schematic diagram of a mobile communication network architecture, which includes access network equipment (Figure 1 uses an (R)AN device as an example), a first network function, a second network function, a third network function, a service network function, a user plane function, and a data network (DN) connecting to the operator's network. Optionally, the network architecture may also include a service requester, which can be a user, enterprise, individual, operation requester, etc., which are not specifically limited herein. Users, enterprises, and individuals can be terminals, and operation requesters can be application servers, such as application (APP) servers, etc., which are not specifically limited herein.

[0048] The terminal can be a device capable of receiving scheduling and instruction information from access network equipment, providing voice and / or data connectivity to users, or a handheld device with wireless connectivity, or other processing devices connected to a wireless modem. The terminal device can communicate with one or more core networks or the Internet via the RAN. For example, the terminal device can be a portable, pocket-sized, handheld, computer-embedded, or vehicle-mounted mobile device. The terminal device can also be referred to as a subscriber unit (SS), subscriber station (MS), mobile station, remote station, access point (AP), remote terminal, access terminal, user agent, customer premises equipment (CPE), terminal, UE, mobile terminal (MT), etc. The terminal device can also be a wearable device. The terminal device can also be equipment in next-generation communication systems. For example, terminal devices in 5G networks, or terminal devices in future evolved public land mobile networks (PLMNs), or terminal devices in New Radio (NR) communication systems.Currently, terminal devices can include: mobile phones, tablets, laptops, PDAs, customer-premises equipment (CPE), point-of-sale (POS) machines, light user equipment (UE), reduced capability UE (REDCAP UE), mobile internet devices (MID), wearable devices (e.g., smartwatches, smart bracelets, pedometers), in-vehicle equipment (e.g., cars, bicycles, electric vehicles, airplanes, ships, trains, high-speed trains), virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, smart home devices (e.g., refrigerators, televisions, air conditioners, electricity meters), smart robots, workshop equipment, wireless terminals in self-driving vehicles, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, and smart city devices. Wireless terminals in a city, or wireless terminals in a smart home, or flying devices (e.g., intelligent robots, hot air balloons, drones, airplanes), etc. Terminals can also be other devices with terminal functions; for example, a terminal device can also be a device that performs terminal functions in D2D communication.

[0049] Access network equipment is an entity on the network side used to transmit or receive signals. Examples include transmission reception points (TRPs) and gNBs. Network equipment can be access points (APs) in wireless local area networks (WLANs), evolved Node Bs (eNBs or eNodeBs) in LTE, relay stations or access points, or network equipment in vehicular devices, wearable devices, and 5G networks, or network equipment in future PLMNs, or gNodeBs / gNBs in NR systems. In some deployments, a gNB may include a central unit (CU) and a distributed unit (DU). The CU implements some of the gNB's functions, and the DU implements some of the gNB's functions. For example, the CU is responsible for handling non-real-time protocols and services. For example, it implements radio resource control (RRC), service data adaptation protocol (SDAP) functions, and packet data convergence protocol (PDCP) layer functions. The DU is responsible for handling physical layer protocols and real-time services. For example, it can implement the functions of the radio link control (RLC) layer, medium access control (MAC) layer, and physical (PHY) layer. The gNB can also include an active antenna unit (AAU). The AAU implements some physical layer processing functions, radio frequency processing, and related functions of the active antenna. Since the information from the RRC layer ultimately becomes information from the PHY layer, or is derived from information from the PHY layer, in this architecture, higher-layer signaling (e.g., RRC layer signaling) can also be considered as being sent by the DU, or by the DU and AAU. It is understood that the network device can be one or more of the following: CU node, DU node, and AAU node. Furthermore, the CU can be a network device in the RAN, or a network device in the core network (CN); this application does not limit this. Additionally, in the embodiments of this application, the network device provides services to a cell, and the terminal device communicates with the network device through the transmission resources (e.g., frequency domain resources, or spectrum resources) used by the cell. This cell can be the cell corresponding to the network device (e.g., a base station). A cell can belong to a macro base station or to a base station corresponding to a small cell.For example, small cells may include: metro cells, micro cells, pico cells, femto cells, etc. Because small cells have small coverage areas and low transmission power, they can provide high-speed data transmission services. Furthermore, in other possible cases, the network device can be other devices that provide wireless communication functions for terminal devices. The embodiments of this application do not limit the specific technology or device form used in the network device. For example, in an open radio access network (ORAN) system, a CU can also be called an O-CU (open CU), a DU can also be called an O-DU, a CU-CP can also be called an O-CU-CP, a CU-UP can also be called an O-CU-UP, and a radio unit (RU) can also be called an O-RU. For ease of description, this application uses CU, CU-CP, CU-UP, DU, and RU as examples. Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software and hardware modules. Figure 1 uses (R)AN as an example of an access network device to illustrate this.

[0050] The first network function can directly interact with the service requester, requesting the necessary resources for the service, such as connectivity services (session creation or modification). It can also provide other service requests, such as computing and data services. Based on the service requester's request, the first network function can request service resources from other network functions, such as user plane function (UPF) resources for connectivity and computing power resources for computation. If the first service is complex, the first network function may need to request corresponding service execution resources from multiple network functions. For example, when a perception task involves connectivity, computing, AI, and data services, the TCF will initiate network resource requests to the management functions of these services accordingly.

[0051] For example, the first network function can be used for terminal connection management. This first network function integrates some functions from access and mobility management functions (e.g., access and mobility management function, AMF), session management functions (e.g., session management function, SMF), and policy management functions (e.g., policy control function, PCF). Alternatively, the first network function can be co-located with existing connection management network functions (e.g., AMF). For various services in the future network, the first network function is used to uniformly schedule the execution of various different types of services, such as task control. The execution of a task may involve computation, data acquisition and processing, algorithm acquisition, and connection services that transmit the aforementioned data involved in the task execution process through connection resources. For example, a task control function (TCF). This is only an example and does not specifically limit the first network function. For another example, in the future network, the first network function can be a function specifically for terminal management, handling any network service initiated by the terminal. Furthermore, the terminal's status information and all requested service information are also managed by the first network function. For example, the first network function could be a service management function provided to the application server, such as the Network Exposure Function (NEF), used to process service requests from the application server.

[0052] The second network function is used for business resource management. The third network function is used to request resource information for executing business operations.

[0053] Referring to Figure 2, the existing SMF in a 5G mobile network architecture is used as an example. It integrates PDU session creation, PDU session authorization and authentication, N4 session creation, UPF selection and connection, and other processing functions. In this application, the SMF can be divided into a connection function (CF) and a user plane control function (UPCF), where CF is equivalent to the first network function and UPCF is equivalent to the second network function. The CF integrates NGAP (Next Generation Application Protocol, an application protocol between the 5G core network (5GC) and the radio access network (NG-RAN)) management, non-access-stratum (NAS) management, PDU session creation, session context management, and other processing functions. NGAP management is used to transmit UE or service-related messages with RAN nodes, and NAS management is used for NAS signaling interaction with terminals. Optionally, the CF also integrates N4 session management functions, including N4 session creation, modification, and deletion. Correspondingly, when N4 session management functionality is integrated into CF, UPCF can perform N4 session execution. CF sends the created N4 session rules to UPCF, which then selects UPFs based on the rules and configures these rules for the UPFs. UPCF integrates UPF selection and connection, N4 session execution, and other processing functions. Optionally, if N4 session management functionality is not integrated into CF, it can be integrated into UPCF.

[0054] The third network function registration includes various business network functions.

[0055] Service network functions are network functions that perform various services in the future network, such as sensing network functions that perform sensing tasks, computing network functions that perform computing services, and registration network functions that perform data registration services, etc., without being specifically limited here.

[0056] User plane functions are primarily used for processing user packets, such as forwarding and billing. In 5G communication systems, user plane functions can be UPF. In future communication systems, user plane functions may still be called UPF, or they may have other names; this application is not limited to any particular name.

[0057] Data networks are primarily used to provide data transmission services to terminals. Data networks can be private networks, such as local area networks (LANs), public data networks (PDNs), such as the Internet, or dedicated networks deployed by carriers, such as configured IP multimedia core network subsystems (IMS) services.

[0058] N2, N3, N4, N6, and N9 are interface serial numbers, and their meanings are as follows:

[0059] 1) N2: The interface between the first network function and the access network equipment, which can be used to transmit radio bearer control information from the core network side to the access network equipment.

[0060] 2) N3: The interface between the access network equipment and the UPF, mainly used to transmit uplink and downlink user plane data between the access network equipment and the UPF.

[0061] 3) N4: The interface between the second network function and the UPF, which can be used to transmit information between the control plane and the user plane, including the distribution of forwarding rules, QoS rules, traffic statistics rules, etc. from the control plane to the user plane, as well as the reporting of information from the user plane.

[0062] 4) N6: Interface between A-UPF and DN or service network functions.

[0063] 5) N9: User plane interface between A-UPF network elements and I-UPF network elements, used to transmit uplink and downlink user data streams between UPF network elements.

[0064] In the architecture shown in Figure 1, the various network functional elements are connected via a service-oriented bus and interact through service-oriented interfaces. The advantages of a service-oriented bus include improved network flexibility, openness, scalability, and intelligence, enabling support for diverse service scenarios and requirements. The service-oriented bus can be used to transmit various types of data and signaling. For example, it can be used to transmit latency-sensitive real-time signaling (e.g., service-oriented interface call signaling between network functional elements), latency-sensitive real-time data (e.g., real-time AI inference data), and non-real-time data (e.g., offline AI training data). Furthermore, when transmitting this data or signaling, the service-oriented bus couples the data or signaling together; that is, the service-oriented bus can simultaneously transmit real-time signaling, real-time data, and non-real-time data.

[0065] It is understood that the aforementioned network element or function can be a network component in a hardware device, a software function running on dedicated hardware, or a virtualized function instantiated on a platform (e.g., a cloud platform). Optionally, the aforementioned network element or function can be implemented by one device, multiple devices working together, or a functional module within a single device; this application embodiment does not specifically limit this.

[0066] The functions in the embodiments of this application may also be referred to as network elements, network functions, functional entities, devices, etc. For example, access and mobility management functions may also be referred to as access and mobility management network elements, or access and mobility management network functions, or access and mobility management functional entities, etc. The names of each function are not limited in this application. Those skilled in the art can replace the names of the above functions with other names to perform the same function, and all such replacements are within the scope of protection of this application.

[0067] The network functions in Figure 1 above are examples of 5G network functions. In the future, network functions may have other names. The name of the network function is not limited here, as long as it can achieve the corresponding function.

[0068] In current mobile networks, network functions may be responsible for both user connection management and resource allocation for services. For example, in a 5G network, the SMF (Service Provider Function) is responsible for UE session management and user plane transmission resource configuration, while the AMF (Access Provider Function) is responsible for session access management. The SMF context maintains a mapping between the AMF identifier and the UE's PDU session identifier. Different network functions are associated based on user state, and service execution is coupled with user state. Because different network elements maintain UE information and are interconnected by service information, changes to a single network element (such as upgrades or downtime) often affect the service operation of other network elements. For example, if an AMF needs to be upgraded, all SMFs associated with the AMF will be affected. This approach is detrimental to network function upgrades and maintenance.

[0069] Based on this, this application provides a communication method to decouple service execution from user state and reduce the complexity of network function upgrades and maintenance. This communication method can be executed based on the interaction between a first network function and a second network function. The first network function can be the first network function itself, a component within the first network function (e.g., a processor, chip, or chip system), or a logical module or software implementing all or part of the first network function. The second network function can be the second network function itself, a component within the second network function (e.g., a processor, chip, or chip system), or a logical module or software implementing all or part of the second network function. This application does not specifically limit the scope of the application.

[0070] This method can be applied to 5G communication systems or future communication systems, and also to non-terrestrial communication systems; this application does not specifically limit its application. In this application, the number of the first network function and the second network function is not specifically limited; one is used as an example for illustration. In specific applications, under the same network, such as the same PLMN, there may be one first network function and multiple second network functions; this is not limited here. Referring to Figure 3, the following steps are performed:

[0071] Step 301: The first network function obtains the request for the first service.

[0072] The first service can be a terminal service or a future network service. For example, the terminal service is the creation of a PDU session. Typically, the network function performing PDU session creation is fixed, such as a user plane network function. The future network service is a service provided by the network through multi-service fusion. For example, a sensing service, which performs environmental sensing of a certain area, combines sensing data collection (data service), sensing image processing (computing service), sensing target recognition (Artificial Intelligence (AI) service), and sensing data and result transmission (connectivity service) within the network. The future network service must be executed according to the specific service requirements and matched with the corresponding network function. For example, the first network function can send a fourth message, which requests the service resources for creating the first service; and receive information about the network function executing the first service. Specifically, the first network function can send the fourth message to the network function managing the service, so that the network function managing the service can select a network function that meets the execution requirements of the first service based on the fourth message. The fourth message may include the processing strategy of the first service, the network information of the first service (identification of the public terrestrial network, etc.), and the capability information required by the first service (such as the computing algorithm used by the computing service, the data compression algorithm used by the data service, and the AI ​​model used by the AI ​​service). The first network function can initiate service requests to the corresponding resource management function based on the configuration of the task or the network resources involved in the task. For example, when the perception task involves connection services, computing services, AI services, and data services, the first network function will initiate network resource requests to the management functions of these services accordingly. For example, if the first service is a connection service, then the processing strategy of the first service is a session management strategy, including transmission service quality (QoS) parameters (bandwidth, priority, etc.), billing rules, etc. If the first service is a computing service, then the processing strategy of the first service is a computing-related strategy, such as computing power parameters, computing time limits, etc. For AI services, it may be model information, processing latency, accuracy of results, etc. No specific limitations are specified here.

[0073] In one possible implementation, the first service is a timed service, and the service parameters required by the first service may differ at different times. The first network function determines when the execution of the first service will occur, and the first network function may proactively request the service parameters required by the first service.

[0074] In another possible implementation, the first network function receives a request message for a first service. The request message includes the requester of the first service and the service parameters (or service resources, etc.) required by the first service. This request message can be a new type of message associated with the first service, and the execution of the first service can be determined based on this request message. Alternatively, the request message can reuse an existing NAS message, carrying the execution request message for the first service within the NAS message, so that the network elements of the core network can determine the execution of the first service. This is not specifically limited here. The request message for the first service can originate from the requester of the first service, who can be a user, enterprise, individual, operation requester, etc., which is not specifically limited here. Users, enterprises, and individuals can be terminals, and operation requesters can be application servers, such as APP servers, etc. This is not specifically limited here. For example, if the first service is a connection service, the service parameters required by the first service may include session-related parameters, including session type (Internet Protocol (IP) session, non-IP session, etc.), data network name (DNN), and slice information, etc. If the first service is a connectionless service, a specific task (e.g., a sensing task, a computing task, etc.), the service parameters required for the first service may include a task identifier (used to indicate the task), and various service parameters required by the task, such as connection service (session parameters), computing service (computing power parameters), etc. If the first service is a customized service, the service parameters required for the first service may include the identification information of the first service. Based on this, it can be seen that the parameters required for the first service are to enable the network side to provide the corresponding service to the service requester based on these parameters, such as information to identify the service, network resources required to execute the service (e.g., QoS parameters), and location information corresponding to the service (e.g., access device information, geographical location of the service requester, etc.).

[0075] After obtaining a request for a first service, the first network function typically requests a session policy (e.g., QoS flow information required to execute the first service) from a network function or policy management network function that stores subscription information, so as to create session resource information that meets the requirements of the first service based on the session policy. For example, the first network function obtains second information, which indicates the subscription information and / or policy information of the first service. The second information is used to determine the session policy associated with the resource information of the first session (wherein, the first session is the session used to execute the first service). Specifically, the first network function may send a subscription data request message (which may include the identifier of the requester of the first service) to the network function that stores the subscription information of the first service (hereinafter referred to as the data management network function) to obtain the subscription information of the first service. If the subscription information includes the identifier of the requester of the first service, it is determined that the requester of the first service has the authority to execute the first service. After the data management network function determines that the requester of the first service has the authority to execute the first service, and the subscription information includes the session policy associated with the resource information of the first session, the data management network function feeds back the subscription information to the first network function. After determining that the requester of the first service has the authority to execute the first service, and if the subscription information does not include the session policy associated with the resource information of the first session, the data management network function may request the session policy associated with the resource information of the first session from the policy management network function. Alternatively, after the data management network function feeds back the subscription information of the first service to the first network function, the first network function requests the session policy associated with the resource information of the first session from the policy management network function. This is merely an example.

[0076] Step 302: The first network function sends a first message to the second network function. The first message is used to request resource information for creating the first session of the first service.

[0077] Within the same network, after a first network function receives a request for a first service, it can typically obtain relevant information about the first service. Based on this, the first network function can retrieve the address of a second network function that can provide the resource information for the first session required by the first service. For example, different second network functions are responsible for providing the session resource information required by different services (e.g., selecting the appropriate second network function based on DNN and / or slice information, or selecting the second network function based on the service's location). The context of the first network function stores the correspondence between different services and second network functions (this could be instance information of the second network function, such as its identifier or address, or the type of the second network function; i.e., each interaction only requires selecting an instance of the same type of second network function, without needing to bind it to a specific second network function). After receiving a request for the first service, the first network function can search for the corresponding second network function for the first service based on its stored context and obtain the address of the second network function. This is merely an illustrative example and not a specific limitation.

[0078] The first message includes first information, which indicates the session parameter information required for the resource information of the first session. Based on this, the second network function can explicitly provide the first network function with the corresponding session resource information. The first information may include one or more of the following: network information, session policy, or session capabilities. The network information in the first information includes slice information, sub-network information, etc., that the first session needs to satisfy. The session policy refers to the QoS parameters, billing methods, etc., involved in the session. The session capabilities refer to the processing capabilities supported by the session, such as supporting service offloading, supporting multiple access points, and supporting data processing along the way. Uplink service offloading is based on the different regions where the APP server is located, selecting the nearest suitable APP server to send the corresponding data packets. Downlink service offloading involves the terminal accessing the network through multiple access nodes, sending data packets to the terminal through different access points, such as selecting an access node with better service quality for downlink packet forwarding, or copying the data packets and sending them to the terminal through multiple access nodes simultaneously to improve reliability. Multiple access points refer to supporting the terminal to access the network simultaneously through multiple access points. In this context, "data processing along the way" refers to the data transmitted by the terminal during uplink or downlink transmission, including data that may undergo encryption, compression, or other processing. This can be understood by referring to the current user plane data forwarding capabilities supported by 3GPP, and will not be elaborated upon here.

[0079] For example, the first message may also include an identifier for the first service, a first identifier, and user plane transmission endpoint information (such as information about the access network device to which the UE is connected, DNN, and processing node information within the network), etc., which will not be elaborated here. The first identifier is assigned by the first network function to the first session and is used to identify the connection channel between the first network function and the second network function. This first identifier can reuse an existing PDU session identifier or a new identifier can be used to identify the first session. There is a one-to-one correspondence between this new identifier and the PDU session identifier, which is not limited here. If the UE needs to establish a session, the information on the UE side is the RAN-side port information connected to the UE. Then, the DN-side port information is determined based on the DNN and / or slice information, based on which the user plane transmission endpoint information can be determined. The specific content of the first message is not specifically limited here.

[0080] Step 303: The second network function sends a second message to the first network function. The second message includes: resource information of the first session.

[0081] The resource information of the first session includes one or more of the following: port information of the user plane function associated with the first session, address information of the user plane function associated with the first session, or address information of the first session (e.g., N3 Tunnel info). For example, the second message may also include the aforementioned first identifier, the terminal address assigned to the terminal by the second network function or user plane function, and service parameters supported by the user plane function. The first identifier is used to indicate the first service and is used to identify the first service during subsequent interactions. The terminal address is used to mark the terminal's address information during terminal communication. The service parameters supported by the user plane function represent the transmission parameters of the first session, such as bandwidth, QoS flow information, and supported session capabilities (e.g., traffic splitting capability, packet in-path processing capability, etc.).

[0082] In one possible implementation, the second network function supports N4 session management. After receiving a first message from the first network function, the second network function can select a user plane function that can provide resource information for the first session, generate corresponding session processing rules, and configure these rules to the selected user plane function. Subsequently, the second network function sends back to the first network function the address or port information of the selected user plane function, as well as the address information of the first session.

[0083] In another possible implementation, the second network function does not support N4 session management. The second network function obtains the processing rules for the first session based on the session policy associated with the resource information of the first session and a second message. For example, the resource information of the first session includes address information for multiple user plane functions. The second network function feeds back the addresses of the multiple user plane functions to the first network function. The first network function generates the corresponding session processing rules, i.e., the processing rules for the first session, based on the selection of a user plane function. Then, the first network function sends a third message to the second network function, which requests configuration of the first session. The third message includes the processing rules for the first session. For example, the third message also includes a first identifier. The second network function configures the session processing rules to the selected user plane function. The second network function then sends a configuration response message for the first session to the first network function.

[0084] This application refactors a network function (e.g., SMF) into a first network function and a second network function. The first network function receives requests for a first service, which originate from a terminal or other network functions. This first network function maintains the state of the requester and the first service, such as contextual information about their states. The second network function does not need to concern itself with information about the terminal or other first service requesters; it only needs to provide the session resource information required by the service based on the requests from the first network function. The first network function provides direct connection services to the user; for example, it can manage all session service requests from the terminal and manage session context. Based on this, service execution is decoupled from the user's state, and in service scenarios where user state distinction is not required, network function upgrades and maintenance are also simplified.

[0085] To better illustrate the technical solution of this application, specific examples are provided below. Figures 4 and 5 illustrate the data interaction between the UE, RAN device, CF (i.e., the first network function), unified data management (UDM) function / unified data repository (UDR) function, UPCF (i.e., the second network function), and UPF. In Figure 4, the UPCF supports N4 session creation. In Figure 5, the UPCF does not support N4 session management, but the CF does. Figures 4 and 5 use only one UPCF as an example; in actual applications, multiple UPCFs may be involved.

[0086] Referring to Figure 4, execute the following:

[0087] Step 401: The UE sends a session establishment request to the CF.

[0088] Specifically, referring to existing technologies, the session establishment request can carry the user identifier (UE ID), session identifier (Session ID), and session parameters, such as session type (IP session, non-IP session, etc.), DNN, slice information, etc.

[0089] The session establishment request can also be understood as the request for the first business function.

[0090] Step 402: The CF requests the UE's session subscription information from the UDM or UDR based on the session establishment request.

[0091] For example, the CF can send the UE ID and session parameters to the UDM or UDR to request the UE's session subscription information.

[0092] The CF creates a context for the UE for the session and assigns a user plane service identifier (i.e., the first identifier mentioned above) to identify the session.

[0093] Step 403: CF obtains the session policy.

[0094] For example, CF can query the corresponding local session policy based on the session parameters carried in the session establishment request, or obtain the session policy corresponding to the session parameters from PCF, or obtain the session policy based on the subscription information. No specific limitations are specified here.

[0095] Step 404: CF sends the first message to UPCF.

[0096] The first message is used to request resource information for creating a first session of the first service. The first message includes first information, which indicates the session parameter information required to support the resource information of the first session. The first information may include one or more of the following: network information, session policy, or session capabilities. Optionally, the first message may also include a user plane service identifier and user plane transport endpoint information. These will not be elaborated upon here.

[0097] Step 405: Based on the first message, UPCF selects a User Plane Function (UPF) that can provide user plane services, generates corresponding session processing rules, and sends them to the selected User Plane Function.

[0098] For example, the UPCF sends N4 session configuration information to the UPF, which includes an N4 session identifier and N4 rules.

[0099] Step 406: The UPCF sends a second message to the CF, which includes the resource information of the first session (i.e., the address information, identification information, or port information of the UPF, etc.).

[0100] For example, the second message may include the UE's address information (the UE's address is assigned by UPF or UPCF), user plane service identifier, service parameters supported by UPF (such as QoS information, supported session capabilities and corresponding parameters, etc.), and the address of the first session (N3 Tunnel info).

[0101] Step 407: CF generates the corresponding session parameter configuration, N1 SM parameter and N2 SM parameter, based on the resource information of the first session.

[0102] The session parameter configuration includes N2 SM parameters for RAN equipment to manage air interface resources and N1 SM parameters for user data packet transmission. The CF updates the UE's session context based on the session parameter configuration. The UE's session context includes session QoS parameters, user plane function information, UE address information, session capabilities and parameters, etc. Specifically, the N1 SM parameters indicate how the UE should use the first session for data transmission and reception after the first session is established. For example, when using the first session to transmit uplink data packets, it specifies which QoS flow the data packets should be bound to, the available transmission bandwidth, and the data packet priority. The N2 SM parameters indicate how the RAN equipment should perform air interface resource scheduling to provide services to the UE after the first session is established, such as QoS flow information and corresponding QoS parameters (e.g., bandwidth, packet priority, latency).

[0103] Step 408: The CF sends the N2 SM parameters to the RAN device.

[0104] Step 409: The CF sends the N1 SM parameter to the UE.

[0105] This approach reduces the number of SMFs (Service Formatting Functions) for user services by splitting session management functions, simplifies signaling interactions, and facilitates the design of integrated functions for future networks.

[0106] Referring to Figure 5, execute the following:

[0107] Step 501: The UE sends a session establishment request to the CF.

[0108] Specifically, referring to existing technologies, the session establishment request can carry the user identifier (UE ID), session identifier (Session ID), and session parameters, such as session type (IP session, non-IP session, etc.), DNN, slice information, etc.

[0109] The session establishment request can also be understood as the request for the first business function.

[0110] Step 502: The CF requests the UE's session subscription information from the UDM or UDR based on the session establishment request.

[0111] For example, the CF can send the UE ID and session parameters to the UDM or UDR to request the UE's session subscription information.

[0112] The CF creates a context for the UE for the session and assigns a user plane service identifier (i.e., the first identifier mentioned above) to identify the session.

[0113] Step 503: CF obtains the session policy.

[0114] For example, CF can query the corresponding local session policy based on the session parameters carried in the session establishment request, or obtain the session policy corresponding to the session parameters from PCF, or obtain the session policy based on the subscription information. No specific limitations are specified here.

[0115] Step 504: CF sends the first message to UPCF.

[0116] The first message is used to request resource information for creating a first session of the first service. The first message includes first information, which indicates the session parameter information required to support the resource information of the first session. The first information may include one or more of the following: network information, session policy, or session capabilities. Optionally, the first message may also include a user plane service identifier and user plane transport endpoint information. These will not be elaborated upon here.

[0117] Step 505: The UPCF sends a second message to the CF, which includes the resource information of the first session (i.e., the address information, identification information, or port information of all UPFs that meet the requirements of the first session).

[0118] Step 506: CF selects the User Plane Function (UPF) that provides user plane services and generates the corresponding session processing rules.

[0119] The session processing rules include user plane transmission rules corresponding to UPF information, such as packet identification rules, QoS execution rules corresponding to packets, forwarding rules, and calculation or data processing rules for packets.

[0120] Step 507: CF sends a third message to UPCF.

[0121] The third message is used to request configuration for the first session. The third message includes: the processing rules for the first session and the user plane service identifier.

[0122] Step 508: UPCF sends the session processing rules to the selected user plane function based on the third message.

[0123] For example, the UPCF sends N4 session configuration information to the UPF, which includes an N4 session identifier and N4 rules.

[0124] Step 509: UPCF sends the configuration response message for the first session to CF.

[0125] For example, the configuration response message of the first session may include the UE's address information (the UE's address is assigned by UPF or UPCF), user plane service identifier, service parameters supported by UPF (such as QoS information, supported session capabilities and corresponding parameters, etc.) and the address of the first session (N3 Tunnel info).

[0126] Step 510: CF generates the corresponding session parameter configuration, N1 SM parameter and N2 SM parameter, based on the resource information of the first session.

[0127] The session parameter configuration includes N2 SM parameters for managing air interface resources on the RAN device side and N1 SM parameters for user data packet transmission. The CF updates the UE's session context based on the session parameter configuration. The UE's session context includes session QoS parameters, user plane function information, UE address information, session capabilities and parameters, etc.

[0128] Step 511: The CF sends the N2 SM parameters to the RAN device.

[0129] Step 512, the CF sends the N1 SM parameter to the UE.

[0130] This approach reduces the number of SMFs (Service Formatting Functions) for user services by splitting session management functions, simplifies signaling interactions, and facilitates the design of integrated functions for future networks.

[0131] To better illustrate the technical solution of this application, specific examples are provided below. Figure 6 illustrates the data interaction between AF, RAN equipment, TCF (i.e., the first network function), UDM / UDR, UPCF (i.e., the second network function), UPF, XPCF (i.e., the third network function), and XPF. Figure 6 uses only one UPCF as an example; in actual applications, multiple UPCFs may be involved. XPCF corresponds to the control function of a new service plane, such as compute plane control function (CPCF), data plane control function (DPCF), etc., where X stands for any, a general term. In the process of Figure 6, the first service can be a customized service provided by the network through multi-service fusion. For example, a sensing service, which performs environmental sensing of a certain area, requires combining sensing data collection (data service), sensing image processing (computation service), sensing target recognition (AI service), and sensing data and result transmission (connectivity service) within the network. No specific limitations are specified here. The execution is as follows:

[0132] Step 601: AF sends a request for the first service to TCF.

[0133] The request for the first service can be either a creation request or a modification request for the first service. The request for the first service includes an identifier for the first service.

[0134] Step 602: TCF requests the contract information for the first service from UDM or UDR.

[0135] The contract information for the first service includes the scope of authorization for the first service (e.g., whether the service requester has permission to use the first service) and the corresponding service parameters.

[0136] Step 603: TCF obtains the processing strategy and rules for the first service.

[0137] Since a single business operation requires the collaboration of multiple services on the network side, the processing strategies and rules for that business operation correspond to the strategies and rules for the multiple services involved.

[0138] Step 604: TCF sends the fourth message to XPCF.

[0139] The fourth message is used to request the business resources for creating the first service. The fourth message may include the processing strategy of the first service, the network information of the first service (such as the identifier of the public terrestrial network), and the capability information required by the first service (such as the computing algorithm used by the computing service, the data compression algorithm used by the data service, and the AI ​​model used by the AI ​​service). These are not specifically limited here.

[0140] Step 605: XPCF selects the business plane function (XPF) that can support the service based on the fourth message and configures the service execution parameters to XPF.

[0141] Step 606: XPCF sends a service plane resource feedback message to TCF.

[0142] The resource feedback message for this business plane includes XPF information about the XPF that XPCF selected to execute the service.

[0143] Step 607: TCF sends the first message to UPCF.

[0144] The first message is used to request resource information for creating the first session of the first service. The first message includes first information, which indicates the session parameter information required to support the resource information of the first session. The first information may include one or more of the following: network information, session policy, or session capabilities. Optionally, the first message may also include the identifier of the first service and user plane transport endpoint information. These will not be elaborated upon here.

[0145] Step 608: UPCF selects a User Plane Function (UPF) that can provide user plane services based on the first message, generates corresponding session processing rules, and sends them to the selected User Plane Function.

[0146] For example, the UPCF sends N4 session configuration information to the UPF, which includes an N4 session identifier and N4 rules.

[0147] Step 609: UPCF sends a second message to TCF, which includes the resource information of the first session (i.e., the address information, identification information, or port information of UPF, etc.).

[0148] For example, the second message may include the UE's address information (the UE's address is assigned by UPF or UPCF), the identifier of the first service, the service parameters supported by UPF (such as QoS information, supported session capabilities and corresponding parameters, etc.), and the address of the first session (N3 Tunnel info).

[0149] In step 610, the TCF configures the connection service-related parameters to the RAN device. Simultaneously, it can send the connection node (UPF information) to the XPCF to establish a connection between the UPF and XPF.

[0150] Step 611: TCF updates XPF's configuration and notifies XPF to establish a connection with UPF.

[0151] Step 612: TCF sends the service configuration parameters to AF along with the feedback message of the service request.

[0152] This method can more flexibly adapt to customized services in future mobile networks and reduce the need to update service control capabilities due to new features.

[0153] The foregoing primarily describes the solutions provided by the embodiments of this application from the perspective of device interaction. It is understood that, in order to achieve the above functions, each device may include corresponding hardware structures and / or software modules for executing each function. Those skilled in the art should readily recognize that, in conjunction with the units and algorithm steps of the various examples described in the embodiments disclosed herein, the embodiments of this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0154] The embodiments of this application can divide the device into functional units according to the above method examples. For example, each function can be divided into a separate functional unit, or two or more functions can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0155] In the case of using integrated units, FIG7 shows a possible exemplary block diagram of the communication device involved in the embodiments of this application. As shown in FIG7, the communication device 700 may include: a processing unit 701 and a transceiver unit 702. The processing unit 701 is used to control and manage the operation of the communication device 700. The transceiver unit 702 is used to support communication between the communication device 700 and other devices. Optionally, the transceiver unit 702 may include a receiving unit and / or a transmitting unit, respectively used to perform receiving and transmitting operations. Optionally, the communication device 700 may also include a storage unit for storing the program code and / or data of the communication device 700. The transceiver unit may be referred to as an input / output unit, a communication unit, etc., and the transceiver unit may be a transceiver; the processing unit may be a processor. When the communication device is a module (e.g., a chip) in a communication device, the transceiver unit may be an input / output interface, an input / output circuit, or an input / output pin, etc., and may also be referred to as an interface, a communication interface, or an interface circuit, etc.; the processing unit may be a processor, a processing circuit, or a logic circuit, etc. Exemplarily, the device may be the first network function and the second network function described above.

[0156] More detailed descriptions of the processing unit 701 and the transceiver unit 702 can be obtained directly from the relevant descriptions in the above method embodiments, and will not be repeated here.

[0157] In one example, the communication device 700 is a first network function, and the transceiver unit 702 can be used to obtain a request for a first service. The transceiver unit 702 is also used to send a first message to a second network function, the first message being used to request resource information of a first session of the first service; and to receive a second message from the second network function, the second message including: resource information of the first session, the resource information of the first session including one or more of the following: port information of the user plane function associated with the first session, address information of the user plane function associated with the first session, or address information of the first session.

[0158] In one possible approach, the first message includes first information, which indicates the session parameter information that the resource information of the first session needs to support.

[0159] In one possible manner, the first information includes one or more of the following: network information, session policies, or session capabilities.

[0160] In one possible approach, the processing unit 701 is used to obtain the address of the second network function according to the request of the first service.

[0161] In one possible approach, the processing unit 701 is used to acquire second information, which indicates the subscription information of the first service and / or policy information, and the second information is used to determine the session policy associated with the resource information of the first session.

[0162] In one possible approach, processing unit 701 is used to obtain the processing rules of the first session according to the session policy and the second message; transceiver unit 702 is used to send a third message to the second network function, the third message being used to request configuration of the first session, the third message including: the processing rules of the first session; and to receive a configuration response message of the first session from the second network function.

[0163] In one possible configuration, transceiver unit 702 is used to send a fourth message, which requests the creation of service resources for the first service; and to receive information on the network functions for executing the first service.

[0164] In one possible manner, the fourth message may also include one or more of the following: the processing strategy of the first service, the network information of the first service, and the capability information required by the first service.

[0165] In another example, the communication device 700 is a second network function, and the transceiver unit 702 can be used to receive a first message from the first network function, the first message being used to request resource information of a first session of a first service; the transceiver unit 702 is also used to send a second message to the first network function, the second message including: resource information of the first session, the resource information of the first session including one or more of the following: port information of the user plane function associated with the first session, address information of the user plane function associated with the first session, or address information of the first session.

[0166] In one possible approach, the first message includes first information, which indicates the session parameter information that the resource information of the first session needs to support.

[0167] In one possible approach, the first information may also include one or more of the following:

[0168] Network information, session policies, or session capabilities.

[0169] In one possible manner, the transceiver unit 702 is used to receive a third message from a first network function, the third message being used to request configuration of a first session, the third message including: processing rules for the first session; and sending a configuration response message for the first session to the first network function.

[0170] Figure 8 shows a communication device 800 provided in this application. The communication device 800 can be a chip or a chip system. The communication device can be located in the device involved in any of the above method embodiments, such as a first network function, a second network function, etc., to perform the actions corresponding to the device.

[0171] Optionally, a chip system can consist of chips or include chips and other discrete components.

[0172] The communication device 800 includes a processor 810.

[0173] The processor 810 is configured to execute a computer program stored in the memory 820 to implement the operation of the various devices in any of the above method embodiments.

[0174] Optionally, the communication device 800 may also include a memory 820 for storing computer programs.

[0175] Optionally, the memory 820 and the processor 810 are coupled. Coupling is an indirect coupling or communication connection between devices, units, or modules, which can be electrical, mechanical, or other forms, for information exchange between devices, units, or modules. Optionally, the memory 820 and the processor 810 are integrated together.

[0176] There can be one or more processors 810 and memory 820, without limitation.

[0177] Optionally, in practical applications, the communication device 800 may or may not include a transceiver 830, as illustrated by the dashed box in the figure. The communication device 800 can exchange information with other devices through the transceiver 830. The transceiver 830 can be a circuit, a bus, a transceiver, or any other device that can be used for information exchange.

[0178] In one possible implementation, the communication device 800 may be a first network function, a second network function, etc., in the above-described methods.

[0179] This application embodiment does not limit the specific connection medium between the transceiver 830, processor 810, and memory 820. In Figure 8, the memory 820, processor 810, and transceiver 830 are connected via a bus, indicated by a thick line. The connection methods between other components are merely illustrative and not intended to be limiting. The bus can be an address bus, data bus, control bus, etc. For ease of illustration, only one thick line is used in Figure 8, but this does not indicate that there is only one bus or one type of bus. In this application embodiment, the processor can be a general-purpose processor, digital signal processor, application-specific integrated circuit, field-programmable gate array, or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component, capable of implementing or executing the methods, steps, and logic block diagrams disclosed in this application embodiment. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in this application embodiment can be directly manifested as execution by a hardware processor, or execution by a combination of hardware and software modules within the processor. For example, the processor may include one or more of the following: a central processing unit (CPU), an application-specific integrated circuit (ASIC), a digital signal processor (DSP), a microprocessor unit (MPU), a microcontroller unit (MCU), a graphics processing unit (GPU), a field-programmable gate array (FPGA), an artificial intelligence processor (AI processor), or a neural processing unit (NPU).

[0180] In the embodiments of this application, the memory can be non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD), or it can be volatile memory, such as random-access memory (RAM). The memory can also be any other medium capable of carrying or storing desired program code in the form of instructions or data structures, and accessible by a computer, but is not limited thereto. The memory in the embodiments of this application can also be a circuit or any other device capable of implementing storage functions for storing computer programs, program instructions, and / or data. Exemplarily, the memory can include, but is not limited to, cache, read-only memory (ROM), RAM, synchronous dynamic random access memory (SDRAM), hard disk drive (HDD) or solid-state drive (SSD), erasable programmable read-only memory (EPROM), or compact disc read-only memory (CD-ROM), etc. A memory is any medium capable of carrying or storing desired program code in the form of instructions or data structures, and accessible by a computer, but is not limited thereto. The memory in the embodiments of this application may also be a circuit or any other means capable of implementing storage functions for storing computer programs or instructions, and / or data.

[0181] Based on the above embodiments, referring to Figure 9, this application embodiment also provides another communication device 900, including: an interface circuit 910 and a logic circuit 920; the interface circuit 910 can be understood as an input / output interface, which can be used to execute the transmission and reception steps of each device in any of the above method embodiments, and the logic circuit 920 can be used to run code or instructions to execute the methods executed by each device in any of the above embodiments, which will not be described in detail here.

[0182] Based on the above embodiments, this application also provides a computer-readable storage medium storing instructions that, when executed, cause the methods executed by the devices in any of the above method embodiments to be implemented. The computer-readable storage medium may include various media capable of storing program code, such as a USB flash drive, portable hard drive, read-only memory, random access memory, magnetic disk, or optical disk.

[0183] Based on the above embodiments, this application also provides a computer program product containing a computer program or instructions, which, when run on a computer, causes the computer to execute the methods executed by the various devices in any of the above method embodiments.

[0184] Based on the above embodiments, this application provides a communication system, which includes the first network function, second network function, etc. mentioned in any of the above method embodiments, and can be used to execute the methods executed by each device in any of the above method embodiments.

[0185] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0186] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to this application. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in one or more flowchart illustrations and / or one or more block diagrams.

[0187] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means that implement the functions specified in one or more flowcharts and / or one or more block diagrams.

[0188] These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process, such that the instructions, which execute on the computer or other programmable apparatus, provide steps for implementing the functions specified in one or more flowcharts and / or one or more block diagrams.

Claims

1. A communication method, characterized in that, Applied to the first network function, including: Request to obtain the first service; Send a first message to the second network function, the first message being used to request resource information for the first session of the first service; Receive a second message from the second network function, the second message including: resource information of the first session, the resource information of the first session including one or more of the following: port information of the user plane function associated with the first session, address information of the user plane function associated with the first session, or address information of the first session.

2. The method according to claim 1, characterized in that, The first message includes first information, which indicates the session parameter information that the resource information of the first session needs to support.

3. The method according to claim 2, characterized in that, The first information includes one or more of the following: Network information, session policies, or session capabilities.

4. The method according to any one of claims 1-3, characterized in that, The method further includes: Obtain the address of the second network function according to the request of the first service.

5. The method according to any one of claims 1-4, characterized in that, The method further includes: Obtain second information, which is used to indicate the subscription information of the first service and / or policy information, and the second information is used to determine the session policy associated with the resource information of the first session.

6. The method according to claim 5, characterized in that, The method further includes: The processing rules for the first session are obtained according to the session policy and the second message; Send a third message to the second network function, the third message being used to request configuration of the first session, the third message including: the processing rules of the first session; Receive a configuration response message from the first session of the second network function.

7. The method according to any one of claims 1-6, characterized in that, The method further includes: Send a fourth message, which is used to request the creation of the service resources for the first service; Receive information about the network functions that perform the first service.

8. The method according to claim 7, characterized in that, The fourth message also includes one or more of the following: The processing strategy for the first service, the network information for the first service, and the capability information required for the first service.

9. A communication method, characterized in that, Applications to the second network function include: Receive a first message from a first network function, the first message being used to request resource information for a first session of a first service; Send a second message to the first network function, the second message including: resource information of the first session, the resource information of the first session including one or more of the following: port information of the user plane function associated with the first session, address information of the user plane function associated with the first session, or address information of the first session.

10. The method according to claim 9, characterized in that, The first message includes first information, which indicates the session parameter information that the resource information of the first session needs to support.

11. The method according to claim 10, characterized in that, The first information also includes one or more of the following: Network information, session policies, or session capabilities.

12. The method according to any one of claims 9-11, characterized in that, The method further includes: Receive a third message from the first network function, the third message being used to request configuration of the first session, the third message including: the processing rules of the first session; Send the configuration response message for the first session to the first network function.

13. A communication device, characterized in that, include: At least one processor, said processor being coupled to a memory for storing a computer program; The at least one processor is configured to run part or all of the computer program to cause the method of any one of claims 1-8 or any one of claims 9-12 to be performed.

14. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores instructions that, when executed by a computer, cause the method as described in any one of claims 1-12 to be performed.

15. A computer program product comprising a computer program or instructions, characterized in that, When the computer program or instructions are run on a computer, the method as described in any one of claims 1-12 is performed.

Images