Device, method and apparatus for communication, and computer readable medium

Abstract

The embodiment of the invention provides equipment, a method and a device for communication and a computer readable medium. In the method, a first network device receives a request message associated with a native service, where the native service includes a service other than a connection service deployed by an operator of a communication network. Based on the request message, the first network device determines decision information about the native service. The first network device generates a response message associated with the native service. And the first network device sends the response message.

Description

Technical Field

[0001] Various example embodiments relate to the field of communications, and more specifically to devices, methods, apparatuses, and computer-readable media for communications. Background Technology

[0002] A communication network can be viewed as a facility that enables communication between two or more communication devices or provides communication devices with access to a data network. Mobile or wireless communication networks are an example of communication networks.

[0003] Such communication networks operate according to standards, such as those issued by 3GPP (3rd Generation Partnership Project) or ETSI (European Telecommunications Standards Institute). Examples of such standards include the so-called 5G (fifth generation) standard, or other standards issued by 3GPP. Summary of the Invention

[0004] In general, the exemplary embodiments of this disclosure provide a technical solution for communication, and in particular a technical solution for implementing native service control between user equipment and core network.

[0005] In a first aspect, a first network device is provided. The first network device includes at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the first network device to at least: receive a request message associated with a native service, wherein the native service includes services other than connectivity services deployed by an operator of a communication network; determine decision information about the native service based on the request message; generate a response message associated with the native service; and send the response message.

[0006] In a second aspect, a second network device is provided. The second network device includes at least one processor and at least one memory, the at least one memory storing instructions that, when executed by the at least one processor, cause the second network device to at least: send a decision request message about a native service to a first network device based on a native service request message received from a terminal device, wherein the native service includes services other than connectivity services deployed by an operator of a communication network; receive a decision response message about the native service from the first network device, the decision response message including decision information about the native service determined by the first network device; and send a native service response message to the terminal device based on the decision response message.

[0007] In a third aspect, a third network device is provided. The third network device includes at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the third network device to at least: forward a native service request message to a first network device based on receiving a native service request message from a terminal device, wherein the native service includes services other than connectivity services deployed by the operator of the communication network; and send a native service response message to the terminal device based on receiving a native service response message from the first network device.

[0008] In a fourth aspect, a terminal device is provided. The terminal device includes at least one processor and at least one memory, the at least one memory storing instructions that, when executed by the at least one processor, cause the terminal device to at least: send a native service request message, wherein the native service includes services other than connectivity services deployed by an operator of a communication network; and receive a native service response message.

[0009] In a fifth aspect, a method is provided. The method includes: receiving a request message associated with a native service, wherein the native service includes services other than connectivity services deployed by an operator of a communication network; determining decision information about the native service based on the request message; generating a response message associated with the native service; and sending the response message.

[0010] In a sixth aspect, a method is provided. The method includes: sending a decision request message about a native service to a first network device based on a native service request message received from a terminal device, wherein the native service includes services other than connectivity services deployed by an operator of a communication network; receiving a decision response message about the native service from the first network device, the decision response message including decision information about the native service determined by the first network device; and sending a native service response message to the terminal device based on the decision response message.

[0011] In a seventh aspect, a method is provided. The method includes: forwarding a native service request message received from a terminal device to a first network device, wherein the native service includes services other than connectivity services deployed by the operator of the communication network; and sending a native service response message received from the first network device to the terminal device.

[0012] In an eighth aspect, a method is provided. The method includes: sending a native service request message, wherein the native service includes services other than connectivity services deployed by an operator of a communication network; and receiving a native service response message.

[0013] In a ninth aspect, an apparatus is provided. The apparatus includes: components for receiving a request message associated with a native service, wherein the native service includes services other than connectivity services deployed by an operator of a communication network; components for determining decision information about the native service based on the request message; components for generating a response message associated with the native service; and components for sending the response message.

[0014] In a tenth aspect, an apparatus is provided. The apparatus includes: components for sending a decision request message about a native service to a first network device based on receiving a native service request message from a terminal device, wherein the native service includes services other than connectivity services deployed by an operator of a communication network; components for receiving a decision response message about the native service from the first network device, the decision response message including decision information about the native service determined by the first network device; and components for sending a native service response message to the terminal device based on the decision response message.

[0015] In an eleventh aspect, an apparatus is provided. The apparatus includes: components for forwarding a native service request message to a first network device based on receiving a native service request message from a terminal device, wherein the native service includes services other than connectivity services deployed by an operator of a communication network; and components for sending a native service response message to the terminal device based on receiving a native service response message from the first network device.

[0016] In a twelfth aspect, an apparatus is provided. The apparatus includes: components for sending a native service request message, wherein the native service includes services other than connectivity services deployed by an operator of a communication network; and components for receiving a native service response message.

[0017] In a thirteenth aspect, a computer-readable medium is provided. The computer-readable medium includes program instructions stored thereon for performing at least the methods of the fifth, sixth, seventh, or eighth aspects.

[0018] In a fourteenth aspect, a computer program is provided. The computer program includes instructions. When executed by a device, the instructions cause the device to perform at least the methods of the fifth, sixth, seventh, or eighth aspects.

[0019] In a fifteenth aspect, a first network device is provided. The first network device includes: a receiving circuit system configured to receive a request message associated with a native service, wherein the native service includes services other than connectivity services deployed by an operator of a communication network; a determining circuit system configured to determine decision information about the native service based on the request message; a generating circuit system configured to generate a response message associated with the native service; and a transmitting circuit system configured to transmit the response message.

[0020] In a sixteenth aspect, a second network device is provided. The second network device includes: a first transmitting circuitry configured to send a decision request message about a native service to the first network device based on a native service request message received from a terminal device, wherein the native service includes services other than connectivity services deployed by an operator of a communication network; a receiving circuitry configured to receive a decision response message about the native service from the first network device, the decision response message including decision information about the native service determined by the first network device; and a second transmitting circuitry configured to send a native service response message to the terminal device based on the decision response message.

[0021] In a seventeenth aspect, a third network device is provided. The third network device includes: a first transmitting circuit system configured to forward a native service request message received from a terminal device to the first network device, wherein the native service includes services other than connectivity services deployed by an operator of a communication network; and a second transmitting circuit system configured to send a native service response message received from the first network device to the terminal device.

[0022] In an eighteenth aspect, a terminal device is provided. The terminal device includes: a transmitting circuit system configured to transmit a native service request message, wherein the native service includes services other than connectivity services deployed by an operator of a communication network; and a receiving circuit system configured to receive a native service response message.

[0023] It should be understood that the summary portion is not intended to identify key or essential features of the embodiments of this disclosure, nor is it intended to limit the scope of this disclosure. Other features of this disclosure will become readily apparent from the following description. Attached Figure Description

[0024] Some exemplary embodiments will now be described with reference to the accompanying drawings, in which:

[0025] Figure 1A The illustration shows an example communication environment in which example embodiments of this disclosure can be implemented;

[0026] Figure 1BThe diagram illustrates the basic network architecture for the convergence of computing and networking.

[0027] Figure 1C The illustration shows a schematic diagram of a computing network architecture supporting native services according to an exemplary embodiment of the present disclosure;

[0028] Figure 2 The diagram illustrates a signaling diagram of an example communication process according to an example embodiment of the present disclosure;

[0029] Figure 3 The illustration shows a schematic diagram of an end-to-end native service session according to an example embodiment of the present disclosure;

[0030] Figure 4 The diagram illustrates a schematic network architecture for supporting native services according to an example embodiment of the present disclosure;

[0031] Figure 5 The illustration shows a schematic diagram of the protocol stack in various network elements according to an exemplary embodiment of the present disclosure;

[0032] Figure 6 The illustration shows the format of the PDU session message "Extended Protocol Configuration Options" according to an embodiment of the present disclosure;

[0033] Figure 7 The illustration depicts a schematic process for establishing a native service according to an example embodiment of the present disclosure;

[0034] Figure 8 The illustration depicts a schematic process of native service update according to an example embodiment of the present disclosure;

[0035] Figure 9 The illustration depicts a schematic process of native service release according to an example embodiment of the present disclosure;

[0036] Figure 10 The diagram illustrates a signaling diagram of an example communication process according to another example embodiment of the present disclosure;

[0037] Figure 11A The diagram illustrates the non-access stratum configuration in the current 5G network.

[0038] Figure 11B The illustration shows a schematic diagram of the configuration of native services in the non-access layer according to another exemplary embodiment of the present disclosure;

[0039] Figure 12 The illustration shows a schematic diagram of the protocol stack in various network elements according to another exemplary embodiment of the present disclosure;

[0040] Figure 13 The illustration shows a schematic network architecture diagram for supporting native services according to another exemplary embodiment of the present disclosure;

[0041] Figure 14 The diagram illustrates an example of the NAS message format and extended protocol identifiers;

[0042] Figure 15 The illustration depicts a schematic process of native service provision according to another exemplary embodiment of this disclosure;

[0043] Figure 16 The illustration shows a flowchart of an example method implemented at a network device according to some embodiments of the present disclosure;

[0044] Figure 17 The illustration shows a flowchart of an example method implemented at a network device according to some embodiments of the present disclosure;

[0045] Figure 18 The illustration shows a flowchart of an example method implemented at a network device according to some embodiments of the present disclosure;

[0046] Figure 19 The illustration shows a flowchart of an example method implemented at a terminal device according to some embodiments of the present disclosure;

[0047] Figure 20 The illustration shows a simplified block diagram of a device suitable for implementing some example embodiments of the present disclosure; and

[0048] Figure 21 A block diagram illustrating an example of a computer-readable medium according to some exemplary embodiments of the present disclosure is shown.

[0049] In all the accompanying drawings, the same or similar reference numerals denote the same or similar elements. Detailed Implementation

[0050] The principles of this disclosure will now be described with reference to some exemplary embodiments. It should be understood that these embodiments are described for illustrative purposes only and to assist those skilled in the art in understanding and implementing this disclosure, and do not imply any limitation on the scope of this disclosure. The disclosure described herein can be implemented in various ways other than those described below.

[0051] In the following description and claims, unless otherwise defined, all technical terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains.

[0052] References to "an embodiment," "embodiment," "example embodiment," etc., in this disclosure indicate that the described embodiment may include a particular feature, structure, or characteristic, but not every embodiment must include that particular feature, structure, or characteristic. Furthermore, these phrases do not necessarily refer to the same embodiment. Moreover, when a particular feature, structure, or characteristic is described in connection with an embodiment, it should be understood that, whether or not it is explicitly described, its impact on other embodiments is within the knowledge of those skilled in the art.

[0053] It should be understood that although the terms "first" and "second," etc., can be used to describe various elements, these elements should not be limited by these terms. These terms are used only to distinguish one element from another. For example, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element without departing from the scope of the exemplary embodiments. The term "and / or" as used herein includes any and all combinations of one or more of the listed terms.

[0054] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the exemplary embodiments. As used herein, unless the context clearly indicates otherwise, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well. It should also be understood that the terms “comprising,” “including,” “having,” “with,” “containing,” and / or “comprising” as used herein indicate the presence of the described features, elements, and / or components, but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof. As used herein, “at least one of the following: ” and “at least one of ” and similar wording (where the list of two or more elements is connected by “and” or “or”) refers to at least any one of the elements, or at least any two or more of the elements, or at least all of the elements.

[0055] As used in this application, the term "circuit system" may refer to one or more or all of the following:

[0056] (a) Hardware circuit-only implementation (e.g., implementation in analog and / or digital circuit systems only)

[0057] (b) A combination of hardware circuitry and software, such as (if applicable):

[0058] (i) A combination of (multiple) analog and / or digital hardware circuits with software / firmware; and

[0059] (ii) Any part of the (multiple) hardware processors having software (including (multiple) digital signal processors), software, and (multiple) memories, which work together to enable a device (such as a mobile phone or server) to perform various functions; and

[0060] (c) Multiple hardware circuits and / or multiple processors, such as multiple microprocessors or a portion thereof, that require software (e.g., firmware) to operate, but which may be absent when operation does not require software.

[0061] This definition of "circuit system" applies to all uses of the term in this application (including in any claim). As another example, as used herein, the term "circuit system" also covers implementations of hardware circuitry or processors (or processors), or a portion thereof, and its (or their) accompanying software and / or firmware. For example, and if applicable to a particular claim element, the term "circuit system" also covers baseband integrated circuits or processor integrated circuits for mobile devices, or similar integrated circuits in servers, cellular network devices, or other computing or network devices.

[0062] As used herein, the term "communication network" refers to a network conforming to any suitable communication standard, such as Long Term Evolution (LTE), LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), Narrowband Internet of Things (NB-IoT), etc. Furthermore, communication between terminal devices and network devices in a communication network can be performed according to any suitable generation of communication protocol, including but not limited to first-generation (1G), second-generation (2G), 2.5G, 2.75G, third-generation (3G), fourth-generation (4G), 4.5G, future fifth-generation (5G) communication protocols, and / or any other currently known or future-developed protocols. Embodiments of this disclosure can be applied to various communication systems. Given the rapid development of communications, there will naturally be future types of communication technologies and systems that can embody this disclosure. This disclosure should not be construed as limiting its scope to the aforementioned systems.

[0063] As used herein, the term "network device" refers to a node in a communications network through which terminal devices access the network and receive services. Depending on the terminology and technology applied, network device can refer to a base station (BS) or access point (AP), such as a Node B (NodeB or NB), an evolved Node B (eNodeB or eNB), an NR NB (also known as a gNB), a Remote Radio Unit (RRU), a Radio Header Terminal (RH), a Remote Radio Header Terminal (RRH), a relay, or a low-power node (such as a femtonode, piconode, etc.). Network device can also refer to Radio Access Network (RAN) equipment, Core Network (CN) equipment, User Plane Function (UPF), Data Network (DN), or a server.

[0064] The term "terminal device" refers to any terminal device capable of wireless communication. As an example and not a limitation, a terminal device may also be referred to as a communication device, user equipment, user station, portable user station, mobile station, or access terminal. Terminal devices may include, but are not limited to, mobile phones, cellular phones, smartphones, Voice over IP (VoIP) phones, wireless local loop phones, tablets, wearable terminal devices, personal digital assistants (PDAs), portable computers, desktop computers, image capture terminal devices (such as digital cameras), gaming terminal devices, music storage and playback devices, in-vehicle wireless terminal devices, wireless endpoints, mobile stations, laptop embedded devices (LEEs), laptop mounted devices (LMEs), USB dongles, smart devices, wireless customer premises equipment (CPEs), Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, unmanned aerial vehicles, medical devices and applications (such as remote surgery), industrial devices and applications (such as robots and / or other wireless devices operating in industrial and / or automated processing chain environments), consumer electronics devices, devices operating on commercial and / or industrial wireless networks, etc. In the following description, the terms “terminal equipment”, “communication equipment”, “terminal”, “user equipment” and “UE” may be used interchangeably.

[0065] Integration of Network and Compute (INC) is a new paradigm adapting to the computing resource requirements of diverse emerging use cases, such as Edge Application Server (EAS) selection. The Integration of Network and Compute Function (INCF) is defined as an internal control plane (CP) network function (NF) or external application function (AF) entity that possesses metrics information obtained from both network and computing domains, enabling it to coordinate and make scheduling decisions for network and computing optimization. The optimization process is based on the combination of network and computing metrics information. Deep integration of network and computing resources can provide competitive advantages compared to providing them independently and can enhance the network operator's position in the future service value chain.

[0066] Figure 1A An example communication environment 100 is illustrated, which can implement exemplary embodiments of the present disclosure. Communication environment 100 can be part of a communication network. Figure 1A As shown, the communication environment 100 may include a first network device 110, a second network device 120, a third network device 130, a radio access network (RAN) device, and a terminal device 140. In embodiments of this disclosure, the first network device 110 may be an Integrated Network and Computing Function (INCF) or a Computing and Network Convergence (CNC) function for providing native services, the second network device 130 may be a Session Management Function (SMF), and the third network device 150 may be an Access and Mobility Management Function (AMF).

[0067] It should be noted that, Figure 1A The wireless communication network 100 shown is merely illustrative and may include [interconnection / connection / etc.]. Figure 1A The number of devices and equipment shown may vary, for example, including more or fewer terminal devices. This disclosure is not limited in this respect.

[0068] Figure 1B The diagram illustrates the integrated computing and network infrastructure architecture 101. Figure 1B As shown in the diagram, this architecture connects to user equipment via the Radio Access Network (RAN) domain to ensure wireless signal coverage and transmission. Simultaneously, IP and computing domains are utilized to process and store data, achieving efficient data processing and storage. This entire architecture tightly integrates computing and networking, providing users with convenient and efficient network services such as virtual reality and autonomous driving.

[0069] Computing and network convergence (CNC) is one of the future trends in network development and a crucial issue for 6G networks. Full-service operators with both network and computing infrastructure have made significant efforts in computing and network convergence and have proposed the concept of 6G distributed computing. Other traditional operators also consider CNC a strategic direction. Major international standardization organizations have begun work on computing and network convergence. It is anticipated that tighter integration between communications and computing will enable wide-area distributed clouds across mobile device computing, network computing, and data centers. Currently, the INC / CNC enablement procedure (i.e., the selection of Instance of Services (EAS) based on a combination of network and computing metrics) for 3GPP (R19) is under preparation. Simultaneously, dynamic device offloading has been proposed as a 6G service, aiming to allow applications on constrained devices to seamlessly utilize the network's computing power, thereby improving user experience.

[0070] Most traditional mobile network operators are network connectivity providers who aim to become full-service providers, possessing not only network infrastructure but also numerous distributed computing resources, thereby offering a variety of value-added services beyond connectivity. These value-added services can be computing services or native AI services built upon their computing network infrastructure. Currently, to achieve convergence between mobile networks and computing domains, a service selection method based on the Domain Name System (DNS) can be used.

[0071] Service selection based on DNS can be achieved without significant modifications to the mobile core network by utilizing DNS to obtain the IP address of the URI. However, this approach has several limitations. First, DNS needs to be modified to interact with decision points (such as the compute and network convergence (CNC) controller) to obtain the IP addresses of service instances deployed in the compute site. Second, due to reasons such as security, only limited network metrics are available, and detailed information about the mobile network topology cannot be obtained, thus preventing the derivation of the optimal solution. Third, service selection occurs after the connection is established, which can lead to changing the new UPF to the optimal UPF, introducing longer service latency. In this approach, since no detailed information is publicly available between the mobile network and the compute domain, it is not optimal for mobile network operators, as they cannot guarantee that the solution is the best end-to-end solution.

[0072] Furthermore, computing services must encompass not only service selection but also service deployment and compute offloading (offloading some modules from the UE to the network, and also offloading some modules from the application server in the ASP to reduce latency between the UE and the offloaded modules). DNS-based service selection methods cannot meet this requirement. As deep integration of computing and network convergence becomes possible, operators seek end-to-end optimization solutions to comprehensively optimize computing and network resources. Based on near-user characteristics and a dual infrastructure of network computing, more value-added services with converged end-to-end optimization can be provided. These services can be computing services or native AI services based on their computing network infrastructure. Here, we consider such services as native services of the mobile network.

[0073] Some embodiments of this disclosure aim to treat computing services as native services in mobile networks and to achieve integrated control and management of connectivity and computing services in mobile networks within their control plane by defining an efficient native service control mechanism between the terminal device and the mobile core. This control mechanism can effectively support service selection, service deployment, and compute offloading.

[0074] Figure 1C The illustration shows a schematic diagram of a computing network architecture 102 supporting native services according to an embodiment of the present disclosure. Figure 1C As shown, some embodiments of this disclosure introduce the concept of native services, namely services and / or applications deployed by the operator on its own computing network infrastructure. Native services can be owned by the network operator or provided by a third party with an agreement with the network operator. Simultaneously, new functional modules (i.e., Integrated Network and Computing Functions (INCF) or Computing and Network Convergence (CNC) functions, abbreviated as CNC / INCF, where CNC and INCF can refer to the same functional entity) are added to the mobile core to support native service management, such as enabling native service decision-making, including service selection, service deployment, and offloading decisions. Furthermore, native service functions may also include artificial intelligence (AI) functions, sensing functions, and computing management functions (CMF), etc. At the same time, new functions are added to the Access and Mobility Management Function (AMF) and Session Management Function (SMF) in the core network to support native services in the operator's network. Furthermore, Figure 1C The example architecture may also include User Plane Functions (UPF), Data Network (DN), or servers.

[0075] Traditional mobile networks focus on mobility and connectivity management, defining only two categories at the Non-Access Stratum (NAS): Mobility Management (MM) and Session Management (SM). Since most mobile network operators are currently merely network connectivity providers, they cannot benefit from higher-layer services and applications. There are no other services based on the operator's network infrastructure and computing resources.

[0076] In view of this, some embodiments of this disclosure, based on the addition of the CNC / INCF functional module, introduce the following two mechanisms to support native service session management. First, the first mechanism extends the existing Session Management (SM) function to support native service session management and adds new functionality to the Session Management Function (SMF) to request native service decision-making from the CNC / INCF function. Optionally, the second mechanism defines a new category on the NAS, namely the Native Service Management (NSM) function, and adds functionality to the terminal device, Access and Mobility Management Function (AMF), and the new functional entity CNC / INCF to support native services in the operator's network.

[0077] The two mechanisms will be described in detail below.

[0078] In the first mechanism, the CNC / INCF module is added to the mobile core to manage and control native service session selection. The CNC / INCF module can perform the following functions.

[0079] The first function is to maintain or acquire resource information, which includes: network topology, available bandwidth on each link, latency of each link; computing information (e.g., available CPU, memory); distribution information of deployed service instances and available capabilities of each instance.

[0080] The second function is decision-making, such as selecting the best service instance for a UE's native service request based on service requirements and available information. A new optimal compute node is selected to deploy the required service instance if: the requested service is not yet deployed on any compute node; or if the deployed service instances in the network cannot meet the UE's requirements (e.g., insufficient available CPU resources of the service instance, or end-to-end latency between the UE and the deployed service instance exceeds the requirement). Alternatively, the request is rejected if the network (including the RAN) cannot guarantee the required QoS.

[0081] The third function is to return the decision (i.e. the selected result) to SMF. If the native service request can be satisfied, the IP address of the selected service instance will be included (here, the selected service instance can be an already deployed service instance or a newly deployed service instance).

[0082] The fourth function is that it can trigger path settings on the N6 network segment if needed.

[0083] In the first mechanism, some embodiments of this disclosure add functionality related to native services to the SMF.

[0084] The SMF identifies requests related to native services in PDU session management messages and forwards these requests to the CNC / INCF module for decision-making. For PDU-related request messages with native service requests (i.e., PDU session establishment requests and PDU session modification requests), the SMF will not initiate subsequent corresponding operations until it receives a decision response from the CNC / INCF module. Based on the CNC / INCF's decision, the corresponding operation will be triggered. For example, if a specified UPF is selected as the anchor UPF for the PDU session, the IP address of the native service instance will be included in the PDU response message returned to the UE (PDU session establishment acceptance, PDU session modification command). Of course, if the native service request cannot be satisfied, a PDU session establishment rejection or PDU session modification rejection will be sent to the UE. The UE performs the relevant PDU session management operations based on the CNC / INCF's decision.

[0085] Optionally, some embodiments of this disclosure may also add a CMF module to the mobile core to control and manage distributed computing resources in the network, including: maintaining distributed computing resources; directly managing the module lifecycle; or acting as a proxy for the lifecycle management of other computing controllers (defining interfaces for interacting with computing controllers, such as Kubernetes).

[0086] Optionally, some embodiments of this disclosure may also add other specific service functions to the mobile core, such as AIF (AI-related functions) for controlling and managing native AI functions in the network; and SensingF (sensing functions) for controlling and managing sensing functions in the network.

[0087] Furthermore, in the first mechanism, some embodiments of this disclosure also propose an architecture and process for implementing native services by extending session management, as well as a related protocol stack and detailed implementation methods.

[0088] Figure 2 A signaling diagram of an example communication process 200 according to an example embodiment of the present disclosure is illustrated. For discussion purposes, reference will be made to... Figure 1A The communication process 200 is described below. The communication process 200 may involve the interaction between the first network device 110, the second network device 120, and the terminal device 140.

[0089] like Figure 2As shown, at 210, terminal device 140 sends native service request message 212 to second network device 120, wherein the native service includes services other than connectivity services deployed by the operator of the communication network, such as computing, artificial intelligence (AI), data services, and sensing services.

[0090] In some embodiments, terminal device 140 includes a third native service management (NSM) function module, the third NSM function module and the second NSM function module included in the second network device 120 are configured to communicate with each other about native services, and wherein the second NSM function module is located in the SM function module of the second network device 120, and the third NSM function module is located in the SM function module of the terminal device 140.

[0091] In some embodiments, the native service request message 212 is included in the protocol data unit (PDU) session establishment request message.

[0092] Alternatively, in some embodiments, the native service request message 212 is included in the PDU session modification request message.

[0093] In some embodiments, a PDU session establishment request message or a PDU session modification request message includes a first "Extended Protocol Configuration Options" information element (IE), which includes a first native service container for native services.

[0094] At 220, the second network device 120 sends a decision request message 222 about the native service to the first network device 110 based on the native service request message 222 received at 214.

[0095] At point 230, the second network device 120 suspends the execution of PDU session operations associated with the native service based on sending a decision request message 222 to the first network device 110. For example, PDU session operations associated with the native service include native service establishment, native service update, and native service release.

[0096] At 240, the first network device 110 determines decision information about the native service based on the decision request message 222 received at 224.

[0097] In some embodiments, the decision information may instruct: selecting at least one deployed service instance to provide the native service; deploying at least one service instance for the native service; offloading at least one module of the terminal device 140 for the native service to at least one computing service node; rejecting requests regarding the native service; or a combination of one or more of the foregoing.

[0098] In some embodiments, during the process of determining decision information, the first network device 110 may select at least one service instance from the deployed service instances for the native service based on the service requirements of the native service.

[0099] Alternatively, in some embodiments, when determining decision information, the first network device 110 may determine to deploy at least one service instance for the native service based on the determination that the native service has not been deployed or that the deployed service instance cannot meet the service requirements of the native service.

[0100] Alternatively, in some embodiments, during the determination of decision information, the first network device 110 may determine to reject a request for the native service based on the determination that the radio access network (RAN) cannot guarantee the quality of service (QoS) of the native service.

[0101] In some embodiments, the first network device 110 may also store or obtain resource information associated with the native service. In such embodiments, during the process of determining decision information for the native service, the first network device 110 may also determine the decision information based on the resource information.

[0102] In some embodiments, the resource information may include: network topology information; available bandwidth information of links; latency information of links; computing information; distribution information of deployed service instances; or available capability information of service instances.

[0103] In some embodiments, control and management of resource information can be achieved through a Computational Management Function (CMF) module added to the mobile core.

[0104] In some embodiments, the first network device 110 may also send deployment information of service instances to the computing controller node based on decision information, so as to deploy at least one service instance for native services on at least one computing service node.

[0105] In some embodiments, the first network device 110 may also trigger the establishment of an N6 path for native services or a path between computing service nodes for native services based on decision information.

[0106] At point 250, the first network device 110 generates a decision response message 262, in which the decision information determined at point 240 is included in the decision response message 262.

[0107] At point 260, the first network device 110 sends the generated decision response message 262 to the second network device 120.

[0108] At point 270, the second network device 120 resumes execution of PDU session operations associated with the native service based on the decision response message received from the first network device. For example, PDU session operations associated with the native service include native service establishment, native service update, and native service release.

[0109] At point 280, the second network device 120 sends a native service response message 282 to the terminal device based on the decision response message.

[0110] In some embodiments, the native service response message 282 is included in the PDU session establishment accept message or the PDU session establishment reject message.

[0111] Alternatively, in some embodiments, the native service response message 282 is included in the PDU session modification command message or the PDU session modification rejection message.

[0112] In some embodiments, the PDU session establishment accept message or PDU session modification command message includes a second "Extended Protocol Configuration Options" information element (IE), which includes a second native service container for native services.

[0113] In some embodiments, the first native service container or the second native service container includes at least one of the following: the identifier (ID) of the first native service container or the second native service container; the length of the first native service container or the second native service container; the length of the service parameter list associated with the native service; or the service parameter list associated with the native service.

[0114] At point 284, terminal device 140 receives native service response message 282, and subsequently uses the information in native service response message 282 to configure itself and directly access the service instance indicated in the message.

[0115] Figure 3 The illustration depicts an end-to-end native service session according to an example embodiment of this disclosure. Figure 3 As shown in this embodiment, the native service session encompasses the air interface segment, the N3 network segment, the N6 network segment, and the compute instance in the compute domain. Since the PDU session consists of the air interface segment and the N3 network segment, the native service session can be considered an extension of the PDU session, adding the N6 network segment between the UPF and the selected service instance.

[0116] Figure 4 A schematic network architecture diagram 400 for supporting native services is illustrated according to an example embodiment of this disclosure. Figure 4The new module includes a CNC / INCF module for decision-making regarding service selection, deployment, and offloading. The SMF module's functionality will be enhanced to support native service session management based on PDU session management and CNC / INCF module decisions. User equipment (UE) will also be enhanced to support functions related to native service sessions. Native service requests are transmitted within PDU session establishment requests or PDU session modification requests, depending on when the request is triggered. Furthermore, native service response messages are implemented in PDU session establishment acceptance and PDU session modification commands.

[0117] like Figure 4 As shown, the workflow for native services is as follows:

[0118] In step 401, the UE generates native service requests to the mobile network via Session Management (SM) messages, such as PDU session establishment requests and PDU session modification requests. These messages will contain native service identifiers and related parameters, such as latency and bandwidth.

[0119] In step 402, once the SMF receives the PDU session establishment request and the PDU session modification request, if the SMF finds that this is a native service request, it will send a decision request message about the native service request to the CNC / INCF. At the same time, it will suspend the execution of operations related to the PDU session and wait for the decision returned by the CNC / INCF.

[0120] The following steps (steps 403 to 406) focus on decision-making and service instance preparation.

[0121] In step 403, CNC / INCF can periodically or on-demand acquire distributed computing resource information, i.e., a computing power resource metric retrieval operation. Note that distributed computing information can be acquired in any feasible manner, and the embodiments of this disclosure are not limited thereto.

[0122] In step 404, CNC / INCF may make a decision on how to provide the requested native service, which may be: selecting the service from the deployed service instances; a deployment decision on the best compute node (i.e., deploying a new service instance); an offloading decision (e.g., how many modules will be offloaded to certain selected compute nodes); or rejecting the native service request because the compute network cannot meet the service requirements.

[0123] In some embodiments, the CNC / INCF may make decisions based on the following information: selecting the best service instance for a native service request from the UE based on service requirements and availability; or selecting a new best compute node to deploy the required service instance; or rejecting the request if the RAN cannot guarantee the required QoS.

[0124] In the following situations, CNC / INCF may select a new optimal compute node to deploy the required service instance: if the requested service has not yet been deployed on any compute node; or if the deployed service instances in the network cannot meet the UE's requirements (e.g., insufficient available CPU resources for the service instance, end-to-end latency between the UE and the deployed service instance is greater than required), etc.

[0125] In step 405, the unloading module instantiation occurs. CNC / INCF first contacts the compute controller and, based on the decision in step 404, deploys the relevant service instance modules on the selected compute node. Each deployed module will be configured with an IP address, and these IP addresses will then be communicated to the application's peer component modules.

[0126] In step 406, the CNC / INCF sends a decision response message to the SMF, which includes the decision made by the CNC / INCF in step 404.

[0127] In step 407, the SMF resumes the execution of the corresponding PDU session operation (establishment or modification process), and the corresponding IP address of the native service instance will be included in the downlink NAS-SM message (i.e., native service response message).

[0128] In step 408, the path between the N6 path and the relevant modules of the service will be set.

[0129] In step 409, after receiving the native service response message, the UE will use the information in the message to configure itself and directly access the service instance indicated in the message.

[0130] After these steps, the compute offloading service is successfully deployed in the network, and the UE can enjoy these native services.

[0131] Figure 5 The illustration shows a schematic diagram of the protocol stack in various network elements according to an exemplary embodiment of the present disclosure.

[0132] like Figure 5 As shown, the CNC / INCF is primarily responsible for native service decision-making. Native Service Management (NSM) functionality is added to both the UE and SMF; therefore, the NSM functions in the UE and SMF are referred to as peer entities. The SMF identifies NSM-related messages and implements them according to... Figure 2 or Figure 4 The relevant functionalities described in [the document]. In this implementation, only NAS-SM will be enhanced to support functionalities related to native services.

[0133] In the above implementation, native service management is achieved through tight integration of session management and native service management. Tables 1(a) and 1(b) respectively show the message formats of PDU session establishment requests and PDU session modification requests in 3GPP after applying some embodiments of this disclosure. In both message formats, the "Extended Protocol Configuration Options" information element, used to convey specific parameters of protocol configuration, is shown in bold.

[0134] Table 1(a) PDU Session Establishment Request Message Format

[0135]

[0136]

[0137]

[0138] Table 1(b) PDU Session Modification Request Message Format

[0139]

[0140]

[0141] When it is necessary to transmit special parameters and / or (PDP context-related) requests between the UE and the network, a list of additional parameters can be included in the extended protocol configuration options. This list of additional parameters contains a list of special parameters, each configured in a separate container. The type of parameter carried in the container is identified by a specific container identifier.

[0142] This mechanism can be extended to support Native Service Management (NSM). Figure 6 The illustration shows the format of the PDU session message "Extended Protocol Configuration Options" according to some embodiments of this disclosure. In this implementation, a new container, namely the native service container, is defined to enable SM functionality to support native services.

[0143] In the existing "Extended Protocol Configuration Options," assign a new value to the native service as its container ID. For example... Figure 6 As shown, the extended native service container may include at least the following information: the identifier (ID) of the native service container, the length of the native service container, the length of the service parameter list associated with the native service, and the service parameter list associated with the native service.

[0144] Through this container, native service requests can be sent from the UE to the network (i.e., the CNC / INCF module), and the corresponding native service parameters (such as latency and bandwidth) will be included in the native service parameter list field.

[0145] Accordingly, native service responses can be sent from the network to the UE, and the corresponding parameters (e.g., the IP address of the selected / deployed native service instance) can be included in the container.

[0146] Figures 7 to 9 The illustrations depict the illustrative processes of native service creation, native service update, and native service release according to exemplary embodiments of the present disclosure.

[0147] Figure 7 The illustration shows a schematic process 700 for establishing a native service according to an example embodiment of the present disclosure.

[0148] like Figure 7 As shown, in step 701, the UE generates native service requests to the mobile network via Session Management (SM) messages, such as PDU session establishment requests. These messages will contain native service identifiers and related parameters, such as latency and bandwidth.

[0149] In step 702, once the SMF receives a PDU session establishment request, if the SMF finds that it is a native service request, it will send a decision request message about the native service request to the CNC / INCF. At the same time, it will suspend the execution of operations related to the PDU session and wait for the decision returned by the CNC / INCF.

[0150] In step 703, the CNC / INCF can make decisions on how to provide the requested native service, such as service selection, service deployment, and multi-module unloading. Furthermore, the IP address of the target native service instance will be determined, and the UPF used as the PDU session anchor will be selected.

[0151] In step 704a, CNC / INCF triggers path configuration for native services.

[0152] Optionally, in step 704b, CNC / INCF can trigger CMF to deploy services.

[0153] In step 705, SMF resumes the execution of the corresponding PDU session operation (native service establishment process), and the corresponding IP address of the native service instance will be included in the native service response message.

[0154] In step 706, control related to the corresponding PDU session is initiated to the selected UPF.

[0155] In step 707, the UE receives a native service response message from the SMF, which carries the IP address of the service instance.

[0156] Figure 8The illustration depicts a schematic process 800 of native service update according to an example embodiment of the present disclosure.

[0157] like Figure 8 As shown, in step 801, the UE generates native service update requests to the mobile network, such as PDU session modification requests, via Session Management (SM) messages. These messages will contain native service identifiers and related parameters, such as latency and bandwidth.

[0158] In step 802, once the SMF receives a PDU session modification request, if the SMF finds that it is a native service request, it will send a decision request message about the native service update request to the CNC / INCF. At the same time, it will suspend the execution of operations related to the PDU session and wait for the decision returned by the CNC / INCF.

[0159] In step 803, CNC / INCF can make a decision on native service updates (modifications).

[0160] Optionally, in step 804a, CNC / INCF can trigger a native service instance update.

[0161] In step 804b, the CNC / INCF can trigger the SMF to perform the corresponding PDU session update (modification).

[0162] Optionally, in step 804c, CNC / INCF triggers a path update for the native service.

[0163] In step 805, the SMF initiates the corresponding PDU session update.

[0164] In step 806, the UE receives a native service update response message from the SMF.

[0165] Figure 9 The illustration depicts a schematic process 900 of native service release according to an example embodiment of the present disclosure.

[0166] like Figure 9 As shown, in step 901, the UE generates a native service release request to the mobile network, such as a PDU session release request, via a session management (SM) message.

[0167] In step 902, once the SMF receives a PDU session release request, if the SMF finds that it is a native service request, it will send a decision request message about the native service request to the CNC / INCF. At the same time, it will suspend the execution of operations related to the PDU session and wait for the decision returned by the CNC / INCF.

[0168] In step 903a, CNC / INCF can make a decision to release the native service. For example, CNC / INCF can clear any established paths associated with the native service.

[0169] Optionally, in step 903b, CNC / INCF can clear the service instance associated with the native service.

[0170] In step 904, CNC / INCF can trigger SMF to perform the corresponding PDU session update (modification, deletion).

[0171] In step 905, the SMF initiates control related to the corresponding PDU session.

[0172] In step 906, the UE receives a native service release response message from the SMF.

[0173] It should be noted that it will be obvious to those skilled in the art that this implementation can be detected by several techniques, particularly for the following aspects: (a) the addition of new functional modules, namely CNC / INCF, to the mobile core; (b) extensions to NAS-SM, such as defining native service containers in the "Extended Protocol Configuration Options" of PDU session establishment requests or PDU session modification commands; and (c) the addition of functions to the relevant entities (UE, SMF) to support native services.

[0174] In the second mechanism described above, Native Service Management (NSM) is defined as the third type of NAS, namely NAS-NSM, and is added to both the UE and the CNC / INCF in the core network, responsible for native service management between the UE and the CNC / INCF function. The CNC / INCF module is added to the mobile core to manage and control native service session selection. It is important to note that compared to the first mechanism, the second mechanism has the following characteristics:

[0175] First, in addition to maintaining or acquiring resource information and making decisions related to native services, CNC / INCF also has the following different functions: after receiving native service request messages from the UE via AMF and making a decision, it triggers SMF to establish a corresponding PDU session, constructs a native service response message based on the result, and sends the native service response message to the UE via AMF.

[0176] Secondly, add NSM relay functionality and an interface with CNC / INCF to the AMF for relay communication between CNC / INCF and UE.

[0177] Third, no new features have been added for SMF.

[0178] Fourth, the newly added NAS-NSM function is no longer part of the original NAS-SM function, and therefore will not affect PDU session operations.

[0179] Figure 10 A signaling diagram of an example communication process 1000 according to another exemplary embodiment of this disclosure is illustrated. For discussion purposes, reference will be made to... Figure 1A The communication process 1000 is described below. The communication process 1000 may involve the interaction between a first network device 110, a second network device 120, a third network device 130, and a terminal device 140.

[0180] like Figure 10 As shown, at 1010, terminal device 140 sends native service request message 1012 to third network device 130, wherein the native service includes services other than connectivity services deployed by the operator of the communication network, such as computing, artificial intelligence (AI), data services, and sensing services.

[0181] In some embodiments, terminal device 140 includes a third native service management (NSM) function module, the third NSM function module and the first NSM function module included in the first network device 110 are configured to communicate with each other via the third network device 130 regarding native services, and wherein the third NSM function is independent of the SM function of the terminal device.

[0182] In some embodiments, the native service request message 1012 may include: the identifier of the native service, or the parameters of the native service.

[0183] In some embodiments, the native service request message 1012 is used to create, update, or release a native service.

[0184] In some embodiments, the native service request message 1012 includes a first non-access stratum (NAS) message.

[0185] In some embodiments, the first NAS message includes an "Extended Protocol Authentication" field, the value of which indicates that the first NAS message is a native service management message.

[0186] At 1020, the third network device 130 forwards the native service request message 1012 to the first network device 110 based on the native service request message 1012 received at 1014.

[0187] At 1030, the first network device 110 determines decision information about the native service based on the native service request message 1012 received at 1024.

[0188] In some embodiments, the decision information may instruct: selecting at least one deployed service instance to provide the native service; deploying at least one service instance for the native service; offloading at least one module of the terminal device 140 for the native service to at least one computing service node; or rejecting the request for the native service.

[0189] In some embodiments, the first network device 110 determines decision information by: selecting at least one service instance from the deployed service instances for the native service based on the service requirements of the native service.

[0190] Alternatively, in some embodiments, the first network device 110 determines decision information by: determining that at least one service instance is deployed for the native service based on the fact that the native service has not been deployed or the deployed service instance cannot meet the service requirements of the native service.

[0191] Alternatively, in some embodiments, the first network device 110 determines decision information by: determining to reject a request for the native service based on the fact that the radio access network (RAN) cannot guarantee the quality of service (QoS) of the native service.

[0192] In some embodiments, the first network device 110 may also store or obtain resource information associated with the native service, wherein decision information regarding the native service is determined based on the resource information.

[0193] In some embodiments, the resource information may include: network topology information; available bandwidth information of links; latency information of links; computing information; distribution information of deployed service instances; or available capability information of service instances.

[0194] In some embodiments, control and management of resource information can be achieved through a Computational Management Function (CMF) module added to the mobile core.

[0195] In some embodiments, the first network device 110 may also send deployment information of service instances to the computing controller node based on decision information, so as to deploy at least one service instance for native services on at least one computing service node.

[0196] In some embodiments, the first network device 110 may also trigger the establishment of an N6 path for native services or a path between computing service nodes for native services based on decision information.

[0197] In some embodiments, the first network device 110 may also trigger the second network device 120 to establish a path for native services between the terminal device 140 and the User Plane Function (UPF).

[0198] At 1040, the first network device 110 sends a PDU session operation request message 1042 to the second network device 120, requesting the second network device 120 to perform a PDU session operation associated with the native service.

[0199] At 1050, the second network device 120 performs a PDU session operation associated with the native service based on the PDU session operation request message 1042 received at 1044.

[0200] At 1060, the second network device 120 sends a PDU session operation response message 1062 to the first network device 110. The PDU session operation response message 1062 includes the execution result of the PDU session operation.

[0201] At position 1070, the first network device 110 generates a native service response message based on the execution result of the PDU session operation.

[0202] In some embodiments, the native service response message includes a second NAS message.

[0203] In some embodiments, the second NAS message includes an "Extended Protocol Authentication" field, the value of which indicates that the second NAS message is a native service management message.

[0204] In some embodiments, the native service response message includes address information for at least one service instance of the native service.

[0205] At 1080, the first network device 110 sends the native service response message 1082 to the third network device 130.

[0206] At 1090, the third network device 130 sends the native service response message 1082 to the terminal device 140 based on the native service response message 1082 received from the first network device 110 at 1084.

[0207] At 1094, terminal device 140 receives native service response message 1082, and subsequently uses the information in native service response message 1082 to configure itself and directly access the service instance indicated in the message.

[0208] Traditional mobile networks focus on mobility management and connection management, defining only two categories at the non-access stratum (NAS): mobility management (MM) and session management (SM). Figure 11A The diagram illustrates the non-access stratum configuration in a current 5G network. Figure 11AIn this process, NAS-MM is transmitted between the UE and AMF; NAS-SM is encapsulated in NAS-MM, and AMF is configured to forward NAS-MM between the UE and SMF.

[0209] Figure 11B The illustration shows a schematic diagram of the configuration of native services in the non-access layer according to another example embodiment of this disclosure. For example... Figure 11B As shown, a new category for native service management is defined on the NAS. Specifically, native service management (NSM) is defined as the third category of the NAS (called NAS-NSM), which is responsible for the native service management between the UE and the CNC / INCF function in the core. The newly added NAS-NSM function is no longer subordinate to the original NAS-SM function, so it will not affect the PDU session operation.

[0210] Figure 12 The illustration shows a schematic diagram of the protocol stack in various network elements according to another exemplary embodiment of the present disclosure.

[0211] like Figure 12 As shown, the NSM module is added to both the UE and the CNC / INCF in the mobile core to implement NSM-related functions. Therefore, the NSM functions in the UE and CNC / INCF are referred to as peer entities. Furthermore, a relay function is added to the AMF to enable NSM-related message exchange between the UE and the CNC / INCF module in the mobile core. Additionally, the CNC / INCF module triggers the SMF to execute PDU session operations associated with native services.

[0212] Figure 13 A schematic network architecture diagram 1300 for supporting native services is illustrated according to another example embodiment of this disclosure. Figure 13 This describes the network architecture and workflow for supporting NSM directly by defining new NAS messages (i.e., NAS-NSM). (Compared to...) Figure 4 Similarly, in Figure 13 In this update, a new CNC / INCF module has been added to enable decision-making functions for service selection, deployment, and offloading. Furthermore, AMF has been expanded to serve as a relay function point for NSM-related messages between the UE and the INCF / CNC functions in the mobile core.

[0213] like Figure 13 As shown, the workflow for native services is as follows:

[0214] In step 1301, the UE generates a Native Service Request message, which is encapsulated in a NAS-NSM message and sent to the AMF. These messages will contain a native service identifier and related parameters (such as latency and bandwidth).

[0215] In step 1302, once the AMF receives the NAS-NSM message, the AMF will forward the message directly to the CNC / INCF.

[0216] In step 1303, the CNC / INCF may make a decision on how to provide the requested native service, which may be: selecting the service from the deployed service instances; a deployment decision on the best compute node (i.e., deploying a new service instance); an offloading decision (e.g., how many modules will be offloaded to certain selected compute nodes); or rejecting the native service request because the compute network cannot meet the service requirements.

[0217] In some embodiments, the CNC / INCF may make decisions based on the following information: selecting the best service instance for a native service request from the UE based on service requirements and availability; or selecting a new best compute node to deploy the required service instance; or rejecting the request if the RAN cannot guarantee the required QoS.

[0218] In the following situations, CNC / INCF may select a new optimal compute node to deploy the required service instance: if the requested service has not yet been deployed on any compute node; or if the deployed service instances in the network cannot meet the UE's requirements (e.g., insufficient available CPU resources for the service instance, end-to-end latency between the UE and the deployed service instance is greater than required), etc.

[0219] Furthermore, CNC / INCF can periodically or on-demand acquire distributed network computing information, i.e., resource metric retrieval operations. Note that distributed network computing information can be acquired in any feasible manner, and the embodiments disclosed herein are not limited thereto.

[0220] Optionally, in step 1304, the CNC / INCF contacts the compute controller and, based on the decision in step 1303, deploys the relevant service instance modules on the selected compute node. Each deployed module will be configured with an IP address, and then these IP addresses will be notified to the peer component modules of this application.

[0221] In step 1305, the CNC / INCF triggers the SMF to establish a corresponding network connection between the UE and the selected UPF based on the decision made in step 1303.

[0222] In step 1306, the SMF triggers the corresponding PDU session operation (establishment or modification process).

[0223] Optionally, in step 1307, the N6 path and the connection path between the service modules related to the native service will be set.

[0224] In step 1308, the CNC / INCF generates a native service response message, which includes the IP address of the selected / deployed native service instance. The CNC / INCF then sends this native service response message to the UE. Once the UE receives the native service response message, it will use the information in the message for configuration and directly access the service instance indicated in the message.

[0225] Following these steps, the native service was successfully configured from the operator's dual computing network infrastructure to the UE.

[0226] Figure 14 The diagram illustrates the NAS message format and an example of the extended protocol identifier.

[0227] like Figure 14 As shown, in the current NAS message format, only two values ​​from the Extended Protocol Authentication field (i.e., 5GS Session Management Message and 5GS Mobility Management Message) are used; the remaining values ​​are reserved. Therefore, a value (e.g., 14) can be assigned to the Native Service Management Message from these reserved values. Thus, the AMF can directly recognize this type of message and forward it to the CNC / INCF function for further processing.

[0228] Figure 15 The illustration depicts a schematic process 1500 for providing native services according to another example embodiment of this disclosure.

[0229] like Figure 15 As shown, in step 1501, the UE generates a native service request message, which is encapsulated in a NAS-NSM message and sent to the AMF. These messages will contain a native service identifier and related parameters (such as latency and bandwidth).

[0230] Once the AMF receives the NAS-NSM message, it will forward the message directly to the CNC / INCF.

[0231] In step 1502, the CNC / INCF can make decisions on how to provide the requested native service, such as service selection, service deployment, and multi-module unloading. Furthermore, the IP address of the target native service instance will be determined, and the UPF used as the PDU session anchor will be selected.

[0232] In step 1503, CNC / INCF triggers path configuration for native services and service instance deployment.

[0233] In step 1504, the CNC / INCF sends a PDU session operation request message to the AMF, which may include the selected UPF, service instance IP address, etc.

[0234] In step 1505, control related to the corresponding PDU session is initiated to the selected UPF.

[0235] In step 1506, the UE receives a native service response message from the AMF, which carries the IP address of the service instance.

[0236] It should be noted that it will be obvious to those skilled in the art that this implementation can be detected by several techniques, particularly for the following aspects: (a) the addition of a new functional module, namely CNC / INCF, to the mobile core; (b) the definition of a new functional category, namely NAS-NSM, on NAS messages; and (c) the addition of functions to the relevant entities (UE, CNC / INCF, AMF) to support native services.

[0237] Figure 16 The illustrations depict network devices (e.g., according to some embodiments of the present disclosure) Figure 1A The flowchart shows an example method 1600 implemented at the first network device 110 shown. For discussion purposes, reference will be made to... Figure 1A Method 1600 is described from the perspective of the first network device 110.

[0238] like Figure 16 As shown, at box 1610, the first network device receives a request message associated with a native service, wherein the native service includes services other than connectivity services deployed by the operator of the communication network. At box 1620, the first network device determines decision information about the native service based on the request message. At box 1630, the first network device generates a response message associated with the native service. At box 1640, the first network device sends the response message.

[0239] In some embodiments, the decision information instructs at least one of the following: selecting at least one deployed service instance to provide the native service; deploying at least one service instance for the native service; offloading at least one module of the terminal device for the native service to at least one compute service node; or rejecting the request message regarding the native service.

[0240] In some embodiments, the first network device determines decision information by: selecting at least one service instance from the deployed service instances for the native service based on the service requirements of the native service.

[0241] In some embodiments, the first network device determines decision information by: determining that at least one service instance is deployed for the native service based on the determination that the native service is not deployed or that the deployed service instance cannot meet the service requirements of the native service.

[0242] In some embodiments, the first network device determines decision information by: determining to reject the request message regarding the native service based on the determination that the radio access network (RAN) cannot guarantee the quality of service (QoS) of the native service.

[0243] In some embodiments, the first network device is further configured to: store or obtain resource information associated with the native service, wherein decision information regarding the native service is also determined based on the resource information.

[0244] In some embodiments, the resource information includes at least one of the following: network topology information; available bandwidth information of the links; latency information of the links; computing information; distribution information of deployed service instances; or available capacity information of service instances.

[0245] In some embodiments, the first network device is further configured to: send deployment information of service instances to the compute controller node based on the decision information, so as to deploy at least one service instance for native services on at least one compute service node.

[0246] In some embodiments, the first network device is further configured to: trigger the establishment of at least one of the following based on the decision information: an N6 path for native services, or a path between compute service nodes for native services.

[0247] In some embodiments, the request message associated with the native service is a decision request message about the native service received from a second network device, such as... Figure 2 As described at point 222; and the response message associated with the native service is a decision response message about the native service generated by the first network device and sent to the second network device, wherein the determined decision information is included in the decision response message, such as Figure 2 It is depicted in 262 places.

[0248] In this embodiment, the second network device includes a second native service management (NSM) function module, and the terminal device includes a third NSM function module. The second NSM function module and the third NSM function module are configured to communicate with each other regarding native services, wherein the second NSM function module is located in the session management (SM) function module of the second network device, and the third NSM function module is located in the SM function module of the terminal device.

[0249] In some embodiments, the request message associated with the native service is a native service request message received from the terminal device via a third network device, such as... Figure 10As described at point 1012; and the response message associated with the native service is a native service response message generated by the first network device and sent to the terminal device via the third network device, such as... Figure 10 It is depicted in 1082 places.

[0250] In this embodiment, the first network device includes a first NSM function module, and the terminal device includes a third NSM function module. The first NSM function module and the third NSM function module are configured to communicate with each other via the third network device regarding native services, and wherein the third NSM function is independent of the SM function of the terminal device.

[0251] In some embodiments, the native service request message includes at least one of the following: the identifier of the native service, or the parameters of the native service.

[0252] In some embodiments, native service request messages are used to create, update, or release native services.

[0253] In some embodiments, the native service response message includes address information for at least one service instance of the native service.

[0254] In some embodiments, the native service request message includes a first non-access stratum (NAS) message, and the native service response message includes a second NAS message.

[0255] In some embodiments, the first NAS message and the second NAS message include an "Extended Protocol Authentication" field, the value of which indicates that the first NAS message and the second NAS message are native service management messages.

[0256] In some embodiments, the first network device is further configured to: trigger the second network device to establish a path for native services between the terminal device and the User Plane Function (UPF); send a PDU session operation request message to the second network device to request the second network device to perform a PDU session operation associated with the native service; and receive a PDU session operation response message from the second network device, the PDU session operation response message including the execution result of the PDU session operation, the native service response message being sent by the first network device to the terminal device based on receiving the PDU session operation response message.

[0257] In some embodiments, native services include at least one of the following: computing services; artificial intelligence (AI) services; data services; or perception services.

[0258] In some embodiments, at least one of the following is included: a first network device includes an integrated network and computing function (INCF) or a computing and network convergence (CNC) function; a second network device includes a session management function (SMF); or a third network device includes an access and mobility management function (AMF).

[0259] Figure 17 The illustrations depict network devices (e.g., according to some embodiments of the present disclosure) Figure 1A The flowchart shows an example method 1700 implemented at the second network device 120 shown. For discussion purposes, reference will be made to... Figure 1A Method 1700 is described from the perspective of the second network device 120.

[0260] like Figure 17 As shown, in block 1710, the second network device sends a decision request message about a native service to the first network device based on a native service request message received from the terminal device. This native service includes services other than connectivity services deployed by the operator of the communication network. In block 1720, the second network device receives a decision response message about the native service from the first network device. This decision response message includes decision information about the native service determined by the first network device. In block 1730, the second network device sends a native service response message to the terminal device based on this decision response message.

[0261] In some embodiments, the decision information instructs at least one of the following: selecting at least one deployed service instance to provide the native service; deploying at least one service instance for the native service; offloading at least one module of the terminal device for the native service to at least one compute service node; or rejecting the request message regarding the native service.

[0262] In some embodiments, a native service request message is included in a Protocol Data Unit (PDU) session establishment request message; and a native service response message is included in a PDU session establishment accept message or a PDU session establishment reject message.

[0263] In some embodiments, a native service request message is included in a PDU session modification request message; and a native service response message is included in a PDU session modification command message or a PDU session modification rejection message.

[0264] In some embodiments, a PDU session establishment request message or a PDU session modification request message includes a first "Extended Protocol Configuration Options" information element (IE), which includes a first native service container for native services.

[0265] In some embodiments, the PDU session establishment accept message or PDU session modification command message includes a second "Extended Protocol Configuration Options" information element (IE), which includes a second native service container for native services.

[0266] In some embodiments, the first native service container or the second native service container includes at least one of the following: the identifier (ID) of the first native service container or the second native service container; the length of the first native service container or the second native service container; the length of the service parameter list associated with the native service; or the service parameter list associated with the native service.

[0267] In some embodiments, the second network device is further configured to: suspend PDU session operations associated with the native service based on sending a decision request message to the first network device; and, in response to receiving decision response information from the first network device, resume execution of the suspended PDU session operations associated with the native service based on the decision information.

[0268] In some embodiments, the second network device includes a second native service management (NSM) functional module, and the terminal device includes a third NSM functional module. The second NSM functional module and the third NSM functional module are configured to communicate with each other regarding native services, wherein the second NSM functional module is located in the SM functional module of the second network device, and the third NSM functional module is located in the SM functional module of the terminal device.

[0269] In some embodiments, the native service request message includes at least one of the following: the identifier of the native service, or the parameters of the native service.

[0270] In some embodiments, the native service response message includes address information for at least one service instance of the native service.

[0271] In some embodiments, native service request messages are used to create, update, or release native services.

[0272] In some embodiments, native services include at least one of the following: computing services; artificial intelligence (AI) services; data services; or perception services.

[0273] In some embodiments, at least one of the following is included: a first network device includes an integrated network and computing function (INCF) or a computing and network convergence (CNC) function; a second network device includes a session management function (SMF); or a third network device includes an access and mobility management function (AMF).

[0274] Figure 18The illustrations depict network devices (e.g., according to some embodiments of the present disclosure) Figure 1A The flowchart shows the example method 1800 implemented at the third network device 130 shown. For discussion purposes, reference will be made to... Figure 1A Method 1800 is described from the perspective of the third network device 130.

[0275] like Figure 18 As shown in the diagram, at box 1810, the third network device forwards a native service request message received from the terminal device to the first network device, where the native service includes services other than connectivity services deployed by the operator of the communication network. At box 1820, the third network device sends a native service response message received from the first network device to the terminal device.

[0276] In some embodiments, the third network device is configured to perform relay between a first native service management (NSM) function module of the first network device and a third NSM function module in the terminal device.

[0277] In some embodiments, the native service request message includes a first non-access stratum (NAS) message, and the native service response message includes a second NAS message.

[0278] In some embodiments, the first NAS message and the second NAS message include an "Extended Protocol Authentication" field, the value of which indicates that the first NAS message and the second NAS message are native service management messages.

[0279] In some embodiments, the native service request message includes at least one of the following: the identifier of the native service, or the parameters of the native service.

[0280] In some embodiments, the native service response message includes address information for at least one service instance of the native service.

[0281] In some embodiments, native service request messages are used to create, update, or release native services.

[0282] In some embodiments, native services include at least one of the following: computing services; artificial intelligence (AI) services; data services; or perception services.

[0283] In some embodiments, at least one of the following is true: a first network device includes an integrated network and computing function (INCF) or a computing and network convergence (CNC) function; or a third network device includes an access and mobility management function (AMF).

[0284] Figure 19The illustrations depict some embodiments of the present disclosure in a terminal device (e.g., Figure 1A The flowchart shows an example method 1900 implemented at the terminal device 140 shown. For discussion purposes, reference will be made to... Figure 1A Method 1900 is described from the perspective of terminal device 140.

[0285] like Figure 19 As shown, in box 1910, the terminal device sends a native service request message, wherein the native service includes services other than connectivity services deployed by the operator of the communication network. In box 1920, the terminal device receives a native service response message.

[0286] In some embodiments, a native service request message is sent to a second network device, and a native service response message is received from the second network device.

[0287] In some embodiments, the terminal device includes a third native service management (NSM) function module, the third NSM function module and the second NSM function module included in the second network device are configured to communicate with each other about native services, and wherein the second NSM function module is located in the SM function module of the second network device and the third NSM function module is located in the SM function module of the terminal device.

[0288] In some embodiments, a native service request message is included in a Protocol Data Unit (PDU) session establishment request message; and a native service response message is included in a PDU session establishment accept message or a PDU session establishment reject message.

[0289] In some embodiments, a native service request message is included in a PDU session modification request message; and a native service response message is included in a PDU session modification command message or a PDU session modification rejection message.

[0290] In some embodiments, a PDU session establishment request message or a PDU session modification request message includes a first "Extended Protocol Configuration Options" information element (IE), which includes a first native service container for native services.

[0291] In some embodiments, the PDU session establishment accept message or PDU session modification command message includes a second "Extended Protocol Configuration Options" information element (IE), which includes a second native service container for native services.

[0292] In some embodiments, the first native service container or the second native service container includes at least one of the following: the identifier (ID) of the first native service container or the second native service container; the length of the first native service container or the second native service container; the length of the service parameter list associated with the native service; or the service parameter list associated with the native service.

[0293] In some embodiments, a native service request message is sent to a first network device via a third network device, and a native service response message is received from a first network device via a third network device.

[0294] In some embodiments, the terminal device includes a third native service management (NSM) function module, the third NSM function module and a first NSM function module included in the first network device are configured to communicate with each other via the third network device regarding native services, and wherein the third NSM function is independent of the terminal device's SM function.

[0295] In some embodiments, the native service request message includes a first non-access stratum (NAS) message, and the native service response message includes a second NAS message.

[0296] In some embodiments, the first NAS message and the second NAS message include an "Extended Protocol Authentication" field, the value of which indicates that the first NAS message and the second NAS message are native service management messages.

[0297] In some embodiments, the native service request message includes at least one of the following: the identifier of the native service, or the parameters of the native service.

[0298] In some embodiments, the terminal device is further configured to: obtain address information of at least one service instance for the native service from the native service response message; and access at least one service instance for the native service based on the address information.

[0299] In some embodiments, native service request messages are used to create, update, or release native services.

[0300] In some embodiments, native services include at least one of the following: computing services; artificial intelligence (AI) services; data services; or perception services.

[0301] In some embodiments, at least one of the following is included: a first network device includes an integrated network and computing function (INCF) or a computing and network convergence (CNC) function; a second network device includes a session management function (SMF); or a third network device includes an access and mobility management function (AMF).

[0302] In some embodiments, the means capable of performing method 1600 (e.g., Figure 1A The first network device 110 shown may include components for performing the corresponding steps of method 1600. The components may be implemented in any suitable form. For example, the components may be implemented in a circuit or software module.

[0303] In some embodiments, the apparatus includes: components for receiving a request message associated with a native service, wherein the native service includes services other than connectivity services deployed by an operator of a communication network; components for determining decision information about the native service based on the request message; components for generating a response message associated with the native service; and components for sending the response message.

[0304] In some embodiments, the decision information instructs at least one of the following: selecting at least one deployed service instance to provide the native service; deploying at least one service instance for the native service; offloading at least one module of the terminal device for the native service to at least one compute service node; or rejecting the request message regarding the native service.

[0305] In some embodiments, the first network device determines decision information by: selecting at least one service instance from the deployed service instances for the native service based on the service requirements of the native service.

[0306] In some embodiments, the first network device determines decision information by: determining that at least one service instance is deployed for the native service based on the determination that the native service is not deployed or that the deployed service instance cannot meet the service requirements of the native service.

[0307] In some embodiments, the first network device determines decision information by: determining to reject the request message regarding the native service based on the determination that the radio access network (RAN) cannot guarantee the quality of service (QoS) of the native service.

[0308] In some embodiments, the apparatus further includes a component for storing or obtaining resource information associated with the native service, wherein decision information regarding the native service is also determined based on the resource information.

[0309] In some embodiments, the resource information includes at least one of the following: network topology information; available bandwidth information of the links; latency information of the links; computing information; distribution information of deployed service instances; or available capacity information of service instances.

[0310] In some embodiments, the apparatus further includes a component for sending deployment information of the service instance to the compute controller node based on the decision information, so as to deploy at least one service instance for the native service on at least one compute service node.

[0311] In some embodiments, the apparatus further includes a component for triggering the establishment of at least one of the following based on the decision information: an N6 path for native services, or a path between compute service nodes for native services.

[0312] In some embodiments, the request message associated with the native service is a decision request message about the native service received from the second network device, and the response message associated with the native service is a decision response message about the native service generated by the first network device and sent to the second network device, wherein the determined decision information is included in the decision response message.

[0313] In this embodiment, the second network device includes a second native service management (NSM) function module, and the terminal device includes a third NSM function module. The second NSM function module and the third NSM function module are configured to communicate with each other regarding native services, wherein the second NSM function module is located in the session management (SM) function module of the second network device, and the third NSM function module is located in the SM function module of the terminal device.

[0314] In some embodiments, the request message associated with the native service is a native service request message received from the terminal device via a third network device, and the response message associated with the native service is a native service response message generated by the first network device and sent to the terminal device via the third network device.

[0315] In this embodiment, the first network device includes a first NSM function module, and the terminal device includes a third NSM function module. The first NSM function module and the third NSM function module are configured to communicate with each other via the third network device regarding native services, and wherein the third NSM function is independent of the SM function of the terminal device.

[0316] In some embodiments, the native service request message includes at least one of the following: the identifier of the native service, or the parameters of the native service.

[0317] In some embodiments, native service request messages are used to create, update, or release native services.

[0318] In some embodiments, the native service response message includes address information for at least one service instance of the native service.

[0319] In some embodiments, the native service request message includes a first non-access stratum (NAS) message, and the native service response message includes a second NAS message.

[0320] In some embodiments, the first NAS message and the second NAS message include an "Extended Protocol Authentication" field, the value of which indicates that the first NAS message and the second NAS message are native service management messages.

[0321] In some embodiments, the apparatus further includes: components for triggering a second network device to establish a path for native services between the terminal device and the User Plane Function (UPF); components for sending a PDU session operation request message to the second network device to request the second network device to perform a PDU session operation associated with the native service; and components for receiving a PDU session operation response message from the second network device, the PDU session operation response message including the execution result of the PDU session operation, the native service response message being sent by the first network device to the terminal device based on receiving the PDU session operation response message.

[0322] In some embodiments, native services include at least one of the following: computing services; artificial intelligence (AI) services; data services; or perception services.

[0323] In some embodiments, at least one of the following is included: a first network device includes an integrated network and computing function (INCF) or a computing and network convergence (CNC) function; a second network device includes a session management function (SMF); or a third network device includes an access and mobility management function (AMF).

[0324] In some embodiments, the apparatus further includes components for performing additional steps of some embodiments of method 1600. In some embodiments, the components include at least one processor and at least one memory including computer program code, the at least one memory and the computer program code being configured, together with the at least one processor, to cause execution of the apparatus.

[0325] In some embodiments, the means capable of performing method 1700 (e.g., Figure 1A The second network device 120 shown may include components for performing the corresponding steps of method 1700. The components may be implemented in any suitable form. For example, the components may be implemented in a circuit or software module.

[0326] In some embodiments, the apparatus includes: components for sending a decision request message about a native service to a first network device based on a native service request message received from a terminal device, wherein the native service includes services other than connectivity services deployed by an operator of a communication network; components for receiving a decision response message about the native service from the first network device, the decision response message including decision information about the native service determined by the first network device; and components for sending the native service response message to the terminal device based on the decision response message.

[0327] In some embodiments, the decision information instructs at least one of the following: selecting at least one deployed service instance to provide the native service; deploying at least one service instance for the native service; offloading at least one module of the terminal device for the native service to at least one compute service node; or rejecting the request message regarding the native service.

[0328] In some embodiments, a native service request message is included in a Protocol Data Unit (PDU) session establishment request message; and a native service response message is included in a PDU session establishment accept message or a PDU session establishment reject message.

[0329] In some embodiments, a native service request message is included in a PDU session modification request message; and a native service response message is included in a PDU session modification command message or a PDU session modification rejection message.

[0330] In some embodiments, a PDU session establishment request message or a PDU session modification request message includes a first "Extended Protocol Configuration Options" information element (IE), which includes a first native service container for native services.

[0331] In some embodiments, the PDU session establishment accept message or PDU session modification command message includes a second "Extended Protocol Configuration Options" information element (IE), which includes a second native service container for native services.

[0332] In some embodiments, the first native service container or the second native service container includes at least one of the following: the identifier (ID) of the first native service container or the second native service container; the length of the first native service container or the second native service container; the length of the service parameter list associated with the native service; or the service parameter list associated with the native service.

[0333] In some embodiments, the apparatus further includes: components for suspending PDU session operations associated with a native service based on sending a decision request message to a first network device; and components for resuming execution of the suspended PDU session operations associated with the native service based on decision response information received from the first network device.

[0334] In some embodiments, the second network device includes a second native service management (NSM) functional module, and the terminal device includes a third NSM functional module. The second NSM functional module and the third NSM functional module are configured to communicate with each other regarding native services, wherein the second NSM functional module is located in the SM functional module of the second network device, and the third NSM functional module is located in the SM functional module of the terminal device.

[0335] In some embodiments, the native service request message includes at least one of the following: the identifier of the native service, or the parameters of the native service.

[0336] In some embodiments, the native service response message includes address information for at least one service instance of the native service.

[0337] In some embodiments, native service request messages are used to create, update, or release native services.

[0338] In some embodiments, native services include at least one of the following: computing services; artificial intelligence (AI) services; data services; or perception services.

[0339] In some embodiments, at least one of the following is included: a first network device includes an integrated network and computing function (INCF) or a computing and network convergence (CNC) function; a second network device includes a session management function (SMF); or a third network device includes an access and mobility management function (AMF).

[0340] In some embodiments, the apparatus further includes components for performing additional steps of some embodiments of method 1700. In some embodiments, the components include at least one processor and at least one memory including computer program code, the at least one memory and the computer program code being configured, together with the at least one processor, to cause execution of the apparatus.

[0341] In some embodiments, the means capable of performing method 1800 (e.g., Figure 1A The third network device 130 shown may include components for performing the corresponding steps of method 1800. The components may be implemented in any suitable form. For example, the components may be implemented in a circuit or software module.

[0342] In some embodiments, the apparatus includes: a component for forwarding a native service request message to a first network device based on receiving a native service request message from a terminal device, wherein the native service includes services other than connectivity services deployed by an operator of a communication network; and a component for sending a native service response message to a terminal device based on receiving a native service response message from the first network device.

[0343] In some embodiments, the apparatus further includes a component for performing a relay between a first native service management (NSM) function module of a first network device and a third NSM function module in a terminal device.

[0344] In some embodiments, the native service request message includes a first non-access stratum (NAS) message, and the native service response message includes a second NAS message.

[0345] In some embodiments, the first NAS message and the second NAS message include an "Extended Protocol Authentication" field, the value of which indicates that the first NAS message and the second NAS message are native service management messages.

[0346] In some embodiments, the native service request message includes at least one of the following: the identifier of the native service, or the parameters of the native service.

[0347] In some embodiments, the native service response message includes address information for at least one service instance of the native service.

[0348] In some embodiments, native service request messages are used to create, update, or release native services.

[0349] In some embodiments, native services include at least one of the following: computing services; artificial intelligence (AI) services; data services; or perception services.

[0350] In some embodiments, at least one of the following is true: a first network device includes an integrated network and computing function (INCF) or a computing and network convergence (CNC) function; or a third network device includes an access and mobility management function (AMF).

[0351] In some embodiments, the apparatus further includes components for performing additional steps of some embodiments of method 1800. In some embodiments, the components include at least one processor and at least one memory including computer program code, the at least one memory and the computer program code being configured, together with the at least one processor, to cause execution of the apparatus.

[0352] In some embodiments, the means capable of performing method 1900 (e.g., Figure 1AThe terminal device 140 shown may include components for performing the corresponding steps of method 1900. The components may be implemented in any suitable form. For example, the components may be implemented in a circuit or software module.

[0353] In some embodiments, the apparatus includes: a component for sending a native service request message, wherein the native service includes services other than connectivity services deployed by the operator of the communication network; and a component for receiving a native service response message.

[0354] In some embodiments, a native service request message is sent to a second network device, and a native service response message is received from the second network device.

[0355] In some embodiments, the terminal device includes a third native service management (NSM) function module, the third NSM function module and the second NSM function module included in the second network device are configured to communicate with each other about native services, and wherein the second NSM function module is located in the SM function module of the second network device and the third NSM function module is located in the SM function module of the terminal device.

[0356] In some embodiments, a native service request message is included in a Protocol Data Unit (PDU) session establishment request message; and a native service response message is included in a PDU session establishment accept message or a PDU session establishment reject message.

[0357] In some embodiments, a native service request message is included in a PDU session modification request message; and a native service response message is included in a PDU session modification command message or a PDU session modification rejection message.

[0358] In some embodiments, a PDU session establishment request message or a PDU session modification request message includes a first "Extended Protocol Configuration Options" information element (IE), which includes a first native service container for native services.

[0359] In some embodiments, the PDU session establishment accept message or PDU session modification command message includes a second "Extended Protocol Configuration Options" information element (IE), which includes a second native service container for native services.

[0360] In some embodiments, the first native service container or the second native service container includes at least one of the following: the identifier (ID) of the first native service container or the second native service container; the length of the first native service container or the second native service container; the length of the service parameter list associated with the native service; or the service parameter list associated with the native service.

[0361] In some embodiments, a native service request message is sent to a first network device via a third network device, and a native service response message is received from a first network device via a third network device.

[0362] In some embodiments, the terminal device includes a third native service management (NSM) function module, the third NSM function module and a first NSM function module included in the first network device are configured to communicate with each other via the third network device regarding native services, and wherein the third NSM function is independent of the terminal device's SM function.

[0363] In some embodiments, the native service request message includes a first non-access stratum (NAS) message, and the native service response message includes a second NAS message.

[0364] In some embodiments, the first NAS message and the second NAS message include an "Extended Protocol Authentication" field, the value of which indicates that the first NAS message and the second NAS message are native service management messages.

[0365] In some embodiments, the native service request message includes at least one of the following: the identifier of the native service, or the parameters of the native service.

[0366] In some embodiments, the apparatus further includes: a component for obtaining address information of at least one service instance for the native service from a native service response message; and a component for accessing at least one service instance for the native service based on the address information.

[0367] In some embodiments, native service request messages are used to create, update, or release native services.

[0368] In some embodiments, native services include at least one of the following: computing services; artificial intelligence (AI) services; data services; or perception services.

[0369] In some embodiments, at least one of the following is included: a first network device includes an integrated network and computing function (INCF) or a computing and network convergence (CNC) function; a second network device includes a session management function (SMF); or a third network device includes an access and mobility management function (AMF).

[0370] In some embodiments, the apparatus further includes components for performing additional steps of some embodiments of method 1900. In some embodiments, the components include at least one processor and at least one memory including computer program code, the at least one memory and the computer program code being configured, together with the at least one processor, to cause execution of the apparatus.

[0371] Figure 20 A simplified block diagram of a device 2000 suitable for implementing some example embodiments of the present disclosure is illustrated. The device 2000 can be provided to implement a communication device, such as... Figure 1A The first network device 110, the second network device 120, the third network device 130, or the terminal device 140 shown are illustrated. As shown, device 2000 includes one or more processors 2010, one or more memories 2020 coupled to processors 2010, and one or more communication modules 2040 coupled to processors 2010.

[0372] The communication module 2040 is used for bidirectional communication. The communication module 2040 has at least one antenna to facilitate communication. The communication interface can represent any interface required for communication with other network elements.

[0373] Processor 2010 can be any type suitable for a local technology network, and by way of non-limiting example, can include one or more of the following: general-purpose computer, special-purpose computer, microprocessor, digital signal processor, and processor based on a multi-core processor architecture. Device 2000 can have multiple processors, such as application-specific integrated circuit chips that are time-dependent on a clock of a synchronous main processor.

[0374] Memory 2020 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to, read-only memory (ROM) 2024, electrically programmable read-only memory, flash memory, hard disk, optical disk, digital video disk, and other magnetic and / or optical storage. Examples of volatile memories include, but are not limited to, random access memory (RAM) 2022, and other volatile memories that do not persist during the duration of a power outage.

[0375] Computer program 2030 includes computer-executable instructions that are executed by the associated processor 2010. Program 2030 may be stored in read-only memory 2024. Processor 2010 may perform any suitable actions and processes by loading program 2030 into RAM 2022.

[0376] The embodiments of this disclosure can be implemented by program 2030, enabling device 2000 to execute the reference. Figures 16 to 19 Any process discussed in this disclosure. Embodiments of this disclosure may also be implemented in hardware, or a combination of software and hardware.

[0377] In some example embodiments, program 2030 may be tangibly contained in a computer-readable medium, which may be contained in device 2000 (e.g., memory 2020) or other storage device accessible to device 2000. Device 2000 may load program 2030 from the computer-readable medium into RAM 2022 for execution. The computer-readable medium may include any type of tangible non-volatile storage, such as read-only memory, programmable read-only memory, flash memory, hard disk, optical disk, DVD, etc.

[0378] Figure 21 A block diagram illustrating an example of a computer-readable medium 2100 according to some exemplary embodiments of the present disclosure is shown. A program 2030 is stored on the computer-readable medium 2100. Note that although the computer-readable medium 2100... Figure 21 The program is shown in the form of a CD or DVD, but the computer-readable medium 2100 may be any other form suitable for carrying or storing the program 2030.

[0379] Generally, the various embodiments of this disclosure can be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. Some aspects can be implemented in hardware, while others can be implemented in firmware or software executable by a controller, microprocessor, or other computing device. Although various aspects of the embodiments of this disclosure are shown and described as block diagrams, flowcharts, or using some other graphical representation, it should be understood that, as non-limiting examples, the blocks, apparatuses, systems, techniques, or methods described herein can be implemented in hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or controllers, other computing devices, or some combination thereof.

[0380] This disclosure also provides at least one computer program product tangibly stored on a non-transient computer-readable storage medium. The computer program product includes computer-executable instructions (such as instructions contained in a program module) that execute on a device targeting a real or virtual processor to perform the functions described above. Figures 16 to 19 Methods 1600, 1700, 1800, and 1900 described herein. Typically, a program module includes routines, programs, libraries, objects, classes, components, data structures, etc., that perform specific tasks or implement specific abstract data types. In various embodiments, the functionality of a program module can be combined or divided among program modules as needed. The machine-executable instructions of a program module can be executed on a local or distributed device. In a distributed device, a program module can reside on both local and remote storage media.

[0381] Program code used to perform the methods of this disclosure may be written in any combination of one or more programming languages. This program code may be provided to a processor or controller of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus, such that, when executed by the processor or controller, the program code enables the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may be executed entirely on a machine, partially on a machine, partially on a machine as a standalone software package and partially on a remote machine, or entirely on a remote machine or server.

[0382] In the context of this disclosure, computer program code or related data may be carried by any suitable carrier to enable a device, apparatus, or processor to perform the various processes and operations described above. Examples of carriers include signals, computer-readable media, etc.

[0383] Computer-readable media can be computer-readable signal media or computer-readable storage media. Computer-readable media can include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or equipment, or any suitable combination of the foregoing. More specific examples of computer-readable storage media include electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable optical disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing. The term "non-transient" as used herein is a limitation on the medium itself (i.e., tangible, not signaling), and not a limitation on the persistence of data storage (e.g., random access memory versus read-only memory).

[0384] Furthermore, although operations are described in a specific order, this should not be construed as requiring that such operations be performed in the specific order or sequence shown, or requiring that all of the shown operations be performed to achieve the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, although several details of specific implementations are included in the foregoing discussion, these details should not be construed as limiting the scope of this disclosure, but rather as descriptions of features that may be characteristic of particular embodiments. Certain features described in the context of individual embodiments may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented individually in multiple embodiments, or in any suitable sub-combination.

[0385] Although this disclosure is described in language specific to structural features and / or methodological actions, it should be understood that the disclosure as defined in the appended claims is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are disclosed as exemplary forms of implementing the claims.

Claims

1. A first network device, comprising: At least one processor; as well as At least one memory storing instructions that, when executed by the at least one processor, cause the first network device to at least: Receive request messages associated with native services, wherein the native services include services other than connectivity services deployed by the operator of the communication network; Based on the request message, decision information regarding the native service is determined; Generate a response message associated with the native service; and Send the response message.

2. The first network device according to claim 1, wherein the decision information indicates at least one of the following: Select at least one deployed service instance to provide the native service; Deploy at least one service instance for the native service; Offload at least one module of the terminal device used for the native service to at least one computing service node; or The request message regarding the native service was rejected.

3. The first network device according to claim 1 or 2, wherein the first network device determines the decision information by: Based on the service requirements of the native service, select at least one service instance from the deployed service instances for the native service.

4. The first network device according to any one of claims 1 to 3, wherein the first network device determines the decision information by: Based on the determination that the native service has not been deployed, or that the deployed service instances cannot meet the service requirements of the native service, it is determined that at least one service instance will be deployed for the native service.

5. The first network device according to any one of claims 1 to 4, wherein the first network device determines the decision information by: Based on the determination that the Radio Access Network (RAN) cannot guarantee the Quality of Service (QoS) of the native service, the request message regarding the native service is rejected.

6. The first network device according to any one of claims 1 to 5, wherein the first network device is further configured to: Save or obtain resource information associated with the native service, wherein the decision information regarding the native service is further determined based on the resource information.

7. The first network device according to claim 6, wherein the resource information includes at least one of the following: Network topology information; Available bandwidth information for the link; Link delay information; Calculate information; Information on the distribution of deployed service instances; or Information on the available capabilities of the service instance.

8. The first network device according to any one of claims 1 to 7, wherein the first network device is further configured to: Based on the decision information, deployment information of service instances is sent to the compute controller node to deploy at least one service instance for the native service on at least one compute service node.

9. The first network device according to any one of claims 1 to 8, wherein the first network device is further configured to: Based on the decision information, trigger the establishment of at least one of the following: an N6 path for the native service or a path between computing service nodes for the native service.

10. The first network device according to any one of claims 1 to 9, wherein the request message associated with the native service is a decision request message about the native service received from the second network device, and the response message associated with the native service is a decision response message about the native service generated by the first network device and sent to the second network device, wherein the determined decision information is included in the decision response message.

11. The first network device of claim 10, wherein the second network device includes a second Native Service Management (NSM) functional module, the terminal device includes a third NSM functional module, the second NSM functional module and the third NSM functional module are configured to communicate with each other regarding the native service, and wherein, The second NSM function module is located in the session management (SM) function module of the second network device, and the third NSM function module is located in the SM function module of the terminal device.

12. The first network device according to any one of claims 1 to 9, wherein the request message associated with the native service is a native service request message received from the terminal device via a third network device, and the response message associated with the native service is a native service response message generated by the first network device and sent to the terminal device via the third network device.

13. The first network device of claim 12, wherein the first network device includes a first NSM functional module, the terminal device includes a third NSM functional module, the first NSM functional module and the third NSM functional module are configured to communicate with each other via the third network device regarding the native service, and wherein, The third NSM function is independent of the SM function of the terminal device.

14. The first network device according to claim 12 or 13, wherein the native service request message includes at least one of the following: an identifier of the native service, or parameters of the native service.

15. The first network device according to any one of claims 12 to 14, wherein the native service request message is used to establish, update, or release the native service.

16. The first network device according to any one of claims 12 to 15, wherein the native service response message includes address information for at least one service instance of the native service.

17. The first network device according to any one of claims 12 to 16, wherein the native service request message includes a first non-access stratum (NAS) message, and the native service response message includes a second NAS message.

18. The first network device of claim 17, wherein the first NAS message and the second NAS message include an "extended protocol identifier" field, the value of the "extended protocol identifier" field indicating that the first NAS message and the second NAS message are native service management messages.

19. The first network device according to any one of claims 12 to 18, wherein the first network device is further configured to: Trigger the second network device to establish a path between the terminal device and the User Plane Function (UPF) for the native service; Send a PDU session operation request message to the second network device to request the second network device to perform a PDU session operation associated with the native service; and The first network device receives a PDU session operation response message, which includes the execution result of the PDU session operation. The native service response message is sent by the first network device to the terminal device based on the receipt of the PDU session operation response message.

20. The first network device according to any one of claims 1 to 19, wherein the native service includes at least one of the following: Computing services; Artificial intelligence (AI) services; Data services; or Perception services.

21. The first network device according to any one of claims 12 to 20, wherein at least one of the following: The first network device includes integrated network and computing functions (INCF) or converged computing and networking (CNC) functions; The second network device includes a Session Management Function (SMF); or The third network device includes access and mobility management functions (AMF).

22. A second network device, comprising: At least one processor; as well as At least one memory storing instructions that, when executed by the at least one processor, cause the second network device to at least: Based on receiving a native service request message from a terminal device, a decision request message about the native service is sent to a first network device, wherein the native service includes services other than connectivity services deployed by the operator of the communication network. Receive a decision response message about the native service from the first network device, the decision response message including decision information about the native service determined by the first network device; as well as Based on the decision response message, a native service response message is sent to the terminal device.

23. The second network device of claim 22, wherein the decision information indicates at least one of the following: Select at least one deployed service instance to provide the native service; Deploy at least one service instance for the native service; Offload at least one module of the terminal device used for the native service to at least one computing service node; or The request message regarding the native service was rejected.

24. The second network device according to claim 22 or 23, wherein: The native service request message is included in the Protocol Data Unit (PDU) session establishment request message; and The native service response message is included in the PDU session establishment accept message or the PDU session establishment reject message.

25. The second network device according to claim 22 or 23, wherein: The native service request message is included in the PDU session modification request message; and The native service response message is included in the PDU session modification command message or the PDU session modification rejection message.

26. The second network device according to claim 24 or 25, wherein the PDU session establishment request message or the PDU session modification request message includes a first "Extended Protocol Configuration Options" information element (IE), the first "Extended Protocol Configuration Options" IE including a first native service container for the native service.

27. The second network device according to claim 24 or 25, wherein the PDU session establishment accept message or PDU session modification command message includes a second "Extended Protocol Configuration Options" information element (IE), the second "Extended Protocol Configuration Options" IE including a second native service container for the native service.

28. The second network device according to claim 26 or 27, wherein the first native service container or the second native service container includes at least one of the following: The identifier (ID) of the first native service container or the second native service container; The length of the first native service container or the second native service container; The length of the service parameter list associated with the native service; or The list of service parameters associated with the native service.

29. The second network device according to any one of claims 22 to 28, wherein the second network device is further configured to: Based on sending the decision request message to the first network device, the PDU session operation associated with the native service is suspended; and In response to receiving the decision response information from the first network device, the suspended PDU session operation associated with the native service is resumed based on the decision information.

30. The second network device according to any one of claims 22 to 29, wherein the second network device includes a second native service management (NSM) functional module, the terminal device includes a third NSM functional module, the second NSM functional module and the third NSM functional module are configured to communicate with each other regarding the native service, and wherein, The second NSM function module is located in the SM function module of the second network device, and the third NSM function module is located in the SM function module of the terminal device.

31. The second network device according to any one of claims 22 to 30, wherein the native service request message includes at least one of the following: an identifier of the native service or parameters of the native service.

32. The second network device according to any one of claims 22 to 31, wherein the native service response message includes address information for at least one service instance of the native service.

33. The second network device according to any one of claims 22 to 32, wherein the native service request message is used to establish, update or release the native service.

34. The second network device according to any one of claims 22 to 33, wherein the native service includes at least one of the following: Computing services; Artificial intelligence (AI) services; Data services; or Perception services.

35. The second network device according to any one of claims 22 to 34, wherein at least one of the following: The first network device includes integrated network and computing functions (INCF) or converged computing and networking (CNC) functions; or The second network device includes a Session Management Function (SMF).

36. A third network device, comprising: At least one processor; as well as At least one memory, the at least one memory storing instructions, the instructions, when executed by the at least one processor, cause the third network device to at least: Based on receiving a native service request message from a terminal device, the native service request message is forwarded to a first network device, wherein the native service includes services other than connectivity services deployed by the operator of the communication network. as well as Based on the native service response message received from the first network device, the native service response message is sent to the terminal device.

37. The third network device of claim 36, wherein the third network device is configured to perform relay between a first native service management (NSM) function module of the first network device and a third NSM function module in the terminal device.

38. The third network device according to claim 36 or 37, wherein the native service request message includes a first non-access stratum (NAS) message, and the native service response message includes a second NAS message.

39. The third network device of claim 38, wherein the first NAS message and the second NAS message include an "extended protocol identifier" field, the value of the "extended protocol identifier" field indicating that the first NAS message and the second NAS message are native service management messages.

40. The third network device according to any one of claims 36 to 39, wherein the native service request message includes at least one of the following: an identifier of the native service or parameters of the native service.

41. The third network device according to any one of claims 36 to 40, wherein the native service response message includes address information for at least one service instance of the native service.

42. The third network device according to any one of claims 36 to 41, wherein the native service request message is used to establish, update or release the native service.

43. The third network device according to any one of claims 36 to 42, wherein the native service includes at least one of the following: Computing services; Artificial intelligence (AI) services; Data services; or Perception services.

44. The third network device according to any one of claims 36 to 43, wherein at least one of the following: The first network device includes integrated network and computing functions (INCF) or converged computing and networking (CNC) functions; or The third network device includes access and mobility management functions (AMF).

45. A terminal device, comprising: At least one processor; as well as At least one memory, the at least one memory storing instructions, the instructions, when executed by the at least one processor, cause the terminal device to at least: Send a native service request message, wherein the native service includes services other than connectivity services deployed by the operator of the communication network; as well as Receive response messages from native services.

46. ​​The terminal device of claim 45, wherein the native service request message is sent to the second network device, and the native service response message is received from the second network device.

47. The terminal device according to claim 45 or 46, wherein the terminal device includes a third native service management (NSM) function module, the third NSM function module and a second NSM function module included in the second network device are configured to communicate with each other regarding the native service, and wherein, The second NSM function module is located in the SM function module of the second network device, and the third NSM function module is located in the SM function module of the terminal device.

48. The terminal device according to any one of claims 45 to 47, wherein: The native service request message is included in the Protocol Data Unit (PDU) session establishment request message; and The native service response message is included in the PDU session establishment accept message or the PDU session establishment reject message.

49. The terminal device according to any one of claims 45 to 47, wherein: The native service request message is included in the PDU session modification request message; and The native service response message is included in the PDU session modification command message or the PDU session modification rejection message.

50. The terminal device according to claim 48 or 49, wherein the PDU session establishment request message or the PDU session modification request message includes a first "Extended Protocol Configuration Options" information element (IE), the first "Extended Protocol Configuration Options" IE including a first native service container for the native service.

51. The terminal device according to claim 48 or 49, wherein the PDU session establishment accept message or PDU session modification command message includes a second "Extended Protocol Configuration Options" information element (IE), the second "Extended Protocol Configuration Options" IE including a second native service container for the native service.

52. The terminal device according to claim 50 or 51, wherein the first native service container or the second native service container includes at least one of the following: The identifier (ID) of the first native service container or the second native service container; The length of the first native service container or the second native service container; The length of the service parameter list associated with the native service; or The list of service parameters associated with the native service.

53. The terminal device of claim 45, wherein the native service request message is sent to the first network device via a third network device, and the native service response message is received from the first network device via the third network device.

54. The terminal device of claim 53, wherein the terminal device includes a third native service management (NSM) function module, the third NSM function module and a first NSM function module included in the first network device are configured to communicate with each other via the third network device regarding the native service, and wherein, The third NSM function is independent of the SM function of the terminal device.

55. The terminal device according to claim 53 or 54, wherein the native service request message includes a first non-access stratum (NAS) message, and the native service response message includes a second NAS message.

56. The terminal device of claim 55, wherein the first NAS message and the second NAS message include an "extended protocol identifier" field, the value of the "extended protocol identifier" field indicating that the first NAS message and the second NAS message are native service management messages.

57. The terminal device according to any one of claims 45 to 56, wherein the native service request message includes at least one of the following: an identifier of the native service or parameters of the native service.

58. The terminal device according to any one of claims 45 to 57, wherein the terminal device is further configured to: Obtain address information for at least one service instance for the native service from the native service response message; and Based on the address information, access the at least one service instance used for the native service.

59. The terminal device according to any one of claims 45 to 58, wherein the native service request message is used to establish, update, or release the native service.

60. The terminal device according to any one of claims 45 to 59, wherein the native service includes at least one of the following: Computing services; Artificial intelligence (AI) services; Data services; or Perception services.

61. The terminal device according to any one of claims 53 to 60, wherein at least one of the following: The first network device includes integrated network and computing functions (INCF) or converged computing and networking (CNC) functions; The second network device includes a Session Management Function (SMF); or The third network device includes access and mobility management functions (AMF).

62. A method comprising: At the first network device, a request message associated with a native service is received, wherein the native service includes services other than connectivity services deployed by the operator of the communication network. Based on the request message, decision information regarding the native service is determined; Generate a response message associated with the native service; and Send the response message.

63. A method comprising: At the second network device, based on the native service request message received from the terminal device, a decision request message about the native service is sent to the first network device, wherein the native service includes services other than connectivity services deployed by the operator of the communication network. Receive a decision response message about the native service from the first network device, the decision response message including decision information about the native service determined by the first network device; as well as Based on the decision response message, a native service response message is sent to the terminal device.

64. A method comprising: At the third network device, based on the native service request message received from the terminal device, the native service request message is forwarded to the first network device, wherein the native service includes services other than connectivity services deployed by the operator of the communication network. as well as Based on the native service response message received from the first network device, the native service response message is sent to the terminal device.

65. A method comprising: At the terminal device, a native service request message is sent, wherein the native service includes services other than connectivity services deployed by the operator of the communication network; as well as Receive response messages from native services.

66. An apparatus comprising: A component for receiving request messages associated with native services, wherein the native services include services other than connectivity services deployed by the operator of the communication network; A component used to determine decision information about the native service based on the request message; A component used to generate response messages associated with the native service; as well as The component used to send the response message.

67. An apparatus comprising: A component for sending a decision request message about the native service to a first network device based on a native service request message received from a terminal device, wherein the native service includes services other than connectivity services deployed by the operator of the communication network; A component for receiving a decision response message about the native service from the first network device, the decision response message including decision information about the native service determined by the first network device; as well as A component for sending the native service response message to the terminal device based on the decision response message.

68. An apparatus comprising: A component for forwarding a native service request message to a first network device based on a native service request message received from a terminal device, wherein the native service includes services other than connectivity services deployed by the operator of the communication network; as well as A component for sending the native service response message to the terminal device based on receiving the native service response message from the first network device.

69. An apparatus comprising: A component for sending native service request messages, wherein the native services include services other than connectivity services deployed by the operator of the communication network; as well as A component used to receive native service response messages.

70. A computer-readable medium comprising program instructions stored thereon, the program instructions being configured to perform at least the method according to claim 62, 63, 64 or 65.

Images