Systems, apparatus and methods that support data processing services within a network

By integrating session management functionality into the mobile network and configuring service function chains and tunnels, the problem of insufficient processing capability of 5G networks for perceived data is solved, and a communication link that efficiently supports applications in the digital world is realized.

CN123126016APending Publication Date: 2026-11-17HUAWEI TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202480085509.2
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-01-25
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

Current 5G mobile networks lack the capability and functionality to process sensor data, thus failing to effectively support digital world applications, such as metaverse services, and bandwidth limits the use of these applications.

Method used

Integrating Session Management Function (SMF) devices into mobile networks enables data processing between electronic devices and digital world application servers through a combination of functions in the core network and appropriate message handling. It also allows for the configuration of uplink and downlink service function chains and tunnels to achieve data processing within the network.

Benefits of technology

It enhances the mobile network's ability to support digital world applications, ensuring high bit rate and low latency communication links to meet the needs of digital world applications.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123126016A_ABST
    Figure CN123126016A_ABST
Patent Text Reader

Abstract

Systems and methods for enabling electronic devices to join digital world (DW) application sessions via network-based data processing services. Network functions on the data plane are used to process application session data and forward the processed data to a next destination. The electronic device can decide whether to invoke network-based data processing resources.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates generally to digital world application sessions, and more particularly to systems, apparatus, and methods for supporting digital world application sessions and digital world applications through in-network data processing. Background Technology

[0002] Future mobile networks can provide computing services to support applications, including digital world (DW) services such as metaverse services. Fifth-generation (5G) mobile systems are designed to support ultra-reliable low-latency communication (URLLC), massive device connectivity, and high data rates. However, 5G systems may lack the functionalities required to support digital world applications. For example, current 5G networks may lack the sensing capabilities and functions to process perceived data. Furthermore, mobile networks may lack specific features to support certain characteristics of some digital world applications. Electronic devices (EDs) such as smartphones, head-mounted displays, augmented reality (AR), or virtual reality (VR) glasses may have limited processing power. Additionally, the bandwidth requirements for transmitting large amounts of user and environmental data over 5G wireless links may limit the use of certain digital world applications in 5G mobile networks. Therefore, how mobile network operators (MNOs) can efficiently support digital world applications in current 5G and post-5G future mobile networks remains an open question.

[0003] Therefore, the system needs to be improved to support digital world application sessions and digital world applications.

[0004] This background information is provided to disclose information that the applicant believes may be relevant to the present invention. It is not intended to acknowledge, nor should it be construed as, prior art in relation to the present invention. Summary of the Invention

[0005] This invention relates to methods, apparatus, and systems for supporting digital world applications and digital world application sessions in a mobile network with in-network processing. To achieve this, various functions (such as network functions) are integrated into the mobile network and used to perform and support data processing to support digital world applications. Specifically, in-network processing can be performed through a combination of functions in the core network, for example, through service function chains. Other network functions in the core network and access network can facilitate this in-network processing through appropriate message handling and communication with electronic devices in the access network. Electronic devices, after being notified of the aforementioned capabilities, can adjust their operation accordingly.

[0006] According to embodiments of the present invention, a session management function (SMF) apparatus is provided for supporting DW application sessions between an electronic device (ED) and a digital world (DW) application server (DWAS). The SMF apparatus includes a processing electronic device and is integrated into the infrastructure of the core network (CN) portion of a mobile network (MN). The SMF apparatus can be used to receive DW application session establishment request information and, at least in part based on the DW application session establishment request information, select one or more NFs from a plurality of network functions (NFs) integrated into the CN infrastructure. The SMF apparatus can also be used to request and receive DW application session information; for example, the SMF apparatus can request and receive DW application session information from or from a DW support function (DWSF) or DWAS.

[0007] In some embodiments, DW application session information may include indications of at least one uplink (UL) service function chain (SFC), or at least one downlink (DL) SFC, or both. In some embodiments, DW application session information may also include one or more of the following: NF information indicating each NF in at least one UL SFC and NF information indicating each NF in at least one DL SFC. The DW application session can be processed using data packets in the CN. In other embodiments, one or more NFs selected by the SMF device may include each NF in at least one UL SFC, or each NF in at least one DL SFC, or a combination thereof. In the disclosed embodiments, the ED, DWAS, and MN may be communicatively connected, and the DWAS may be used to provide a DW application for performing a DW application session between the ED and the DWAS. According to some embodiments, the SMF device may configure or initiate the configuration of at least one UL SFC and at least one UL tunnel between the ED and the DWAS. Configuring or initiating the configuration of at least one UL SFC and at least one UL tunnel between the ED and the DWAS may be based at least in part on DW application session establishment request information and DW application session information. In some embodiments, at least one UL tunnel may be located at least partially in the CN, and one or more UL data packets of DW application session data may be sent through at least one UL tunnel and processed in the CN before being transmitted to DWAS.

[0008] According to some embodiments, the SMF device can configure or initiate the configuration of at least one DL SFC and at least one DL tunnel between DWAS and ED. Configuring or initiating the configuration of at least one DL SFC and at least one DL tunnel between DWAS and ED can be based at least in part on DW application session establishment request information and DW application session information. In some embodiments, at least one DL tunnel can be at least partially located in CN, and one or more DL data packets of DW application session data can be sent through at least one DL tunnel and processed in CN before being transmitted to ED.

[0009] In some embodiments, at least a portion of the DW application session establishment request information may be provided by DWAS or by the DW support function (DWSF) for supporting DW application sessions.

[0010] According to some embodiments, the DW application session establishment request information may include one or more of the following: DW application identifier (ID), DW application session ID, ED ID, ED location information, ID of at least one UL SFC, SFC header of at least one UL SFC, ID of at least one DL SFC, and SFC header of at least one DL SFC. In some embodiments, the SFC header of at least one UL SFC may include one or more of the following: ID of at least one UL SFC, ID of the source NF of at least one UL SFC, ID of the destination NF of at least one UL SFC, and UL message processing instructions. According to some embodiments, the SFC header of at least one DL SFC may include one or more of the following: ID of at least one DL SFC, ID of the source NF of at least one DL SFC, ID of the destination NF of at least one DL SFC, and DL message processing instructions.

[0011] In some embodiments, configuring or initiating the configuration of at least one UL SFC and at least one UL tunnel by an SMF device may include configuring the access network (AN) portion of the MN to add the SFC header of at least one UL SFC to one or more UL data packets and forward the one or more UL data packets to at least one NF in at least one UL SFC. Some embodiments disclosed herein may include configuring the SMF device to process one or more UL data packets based on the DW application ID and data processing ID of at least one NF in at least one UL SFC, and sending one or more processed UL data packets to the next NF in at least one UL SFC. Some embodiments may include configuring the SMF device to process the last NF in at least one UL SFC to send one or more processed UL data packets to the DWAS. According to some embodiments, configuring or initiating the configuration of at least one UL SFC and at least one UL tunnel by an SMF device may further include sending an indication to the ED that at least one NF in at least one UL SFC is used to process at least a portion of the DW application session data.

[0012] In some embodiments, configuring or initiating the configuration of at least one DL SFC and at least one DL tunnel by an SMF device may include configuring a DWAS or a data plane gateway (DPGW) to add an SFC header of at least one DL SFC to one or more DL data packets and forward the one or more DL data packets to at least one NF in the at least one DL SFC. The DPGW can provide a data transmission interface between the MN and the DWAS. In some embodiments, the SMF device may also configure at least one NF in the at least one DL SFC to process one or more DL data packets based on the DW application ID and data processing ID of the at least one NF in the at least one DL SFC, and send one or more processed DL data packets to the next NF in the at least one DL SFC. In some embodiments, configuring or initiating the configuration of at least one DL SFC and at least one DL tunnel by an SMF device may include configuring the last NF in the at least one DL SFC to send one or more processed DL data packets to the ED address. In some embodiments, configuring or initiating the configuration of at least one DL SFC and at least one DL tunnel by an SMF device may also include sending an indication to the ED that at least one NF in the at least one DL SFC is used to process at least a portion of the DW application session data.

[0013] Some other embodiments of the present invention relate to an electronic device (ED) for supporting a DW application session between the ED and a digital world (DW) application server (DWAS). The DW application session supported by the ED can use data packet processing in the core network (CN) portion of a mobile network (MN). In some embodiments, the ED may include processing electronics and may be configured to receive one or more of the following: an indication that a DW application is available for the DW application session and DW application session configuration information. The DW application session configuration information may be used by the ED when configuring the DW application session. The indication that a DW application is available for the DW application session, the DW application session configuration information, or a combination thereof may be provided to the ED by the DWAS or DWSF. In some embodiments, the ED may be configured to request at least one uplink (UL) tunnel between the ED and the DWAS, or at least one downlink (DL) tunnel between the DWAS and the ED, or both tunnels; at least one UL tunnel or at least one DL tunnel, or both tunnels may be at least partially located in the CN. According to some embodiments, the ED can also be used to receive an instruction from at least one network function (NF) of the CN for processing at least a portion of DW application session data. In some embodiments of the ED disclosed herein, the ED can communicatively connect to the DWAS and the MN, and the DWAS can be used to provide a DW application for performing a DW application session between the ED and the DWAS. In some embodiments, the ED can be used to send consent to process DW application session data in the CN or to refuse to process DW application session data in the CN.

[0014] In some embodiments, after sending consent to process DW application session data in the CN, the ED can be used to send one or more UL data packets of DW application session data through at least one UL tunnel, wherein the one or more UL data packets can be processed in the CN before being transmitted to the DWAS. In some embodiments, after sending consent to process DW application session data in the CN, the ED can be used to receive one or more DL data packets of DW application session data through at least one DL tunnel, wherein the one or more UL data packets can be processed in the CN before being transmitted to the ED. In some embodiments of the ED, DW application session configuration information and indications that a DW application can be used for the DW application session can be provided to the ED by the DWAS or by a DW support function (DWSF) for supporting the DW application session. In some embodiments of the ED, the DW application session configuration information may include one or more of the following: DW application identifier (ID), DW application session ID, ID of at least one UL service function chain (SFC), SFC header of at least one UL SFC, ID of at least one DL SFC, and SFC header of at least one DL SFC. According to some embodiments of the ED, the SFC header of at least one UL SFC may include one or more of the following: the ID of at least one UL SFC, the ID of the source NF of at least one UL SFC, the ID of the destination NF of at least one UL SFC, and UL message processing instructions. According to other embodiments of the ED, the SFC header of at least one DL SFC may include one or more of the following: the ID of at least one DL SFC, the ID of the source NF of at least one DL SFC, the ID of the destination NF of at least one DL SFC, and DL message processing instructions. According to some embodiments, the ED may also be used to receive an ED message container, wherein the ED message container may include one or more of the following: a message filter set, an indication that a DW application session establishment request is accepted, an indication that a DW application session establishment request is rejected, the ID of the endpoint of at least one UL tunnel, the ID of the endpoint of at least one DL tunnel, the address of at least one UL SFC, and the address of at least one DL SFC.

[0015] Some embodiments of the present invention relate to an access network (AN) device for supporting DW application sessions between an electronic device (ED) and a digital world (DW) application server (DWAS), wherein the DW application session utilizes data packet processing in the core network (CN) portion of a mobile network (MN). In some embodiments, the AN device may include a processing electronic device and may be configured to receive an indication that a request to establish a DW application session has been accepted. In some embodiments, upon receiving the indication, the AN device may support one or more of the following: at least one downlink (DL) tunnel and at least one uplink (UL) tunnel. According to some embodiments of the AN device, supporting at least one UL tunnel may include adding a service function chain (SFC) header of at least one UL SFC to one or more UL data packets and forwarding one or more UL data packets to at least one network function (NF) of at least one UL SFC. According to some embodiments, the AN device may be part of the AN portion of the MN; and the ED, DWAS, CN, and AN device may be communicatively connected. DWAS can be used to provide a DW application for performing a DW application session between the ED and DWAS. In some embodiments, the AN device is also used to receive one or more of the following: DW application session establishment request information and an AN message container. In some embodiments, the DW application session establishment request information received by the AN device may include one or more of the following: DW application identifier (ID), DW application session ID, ED ID, ED location information, ID of at least one UL SFC, SFC header of at least one UL SFC, ID of at least one DL SFC, and SFC header of at least one DL SFC. According to some embodiments of the AN device, the SFC header of at least one UL SFC may include one or more of the following: ID of at least one UL SFC, ID of the source NF of at least one UL SFC, ID of the destination NF of at least one UL SFC, and UL message processing instructions. In some embodiments of the AN device, the SFC header of at least one DL SFC may include one or more of the following: ID of at least one DL SFC, ID of the source NF of at least one DL SFC, ID of the destination NF of at least one DL SFC, and DL message processing instructions.

[0016] Some embodiments of the present invention relate to a system for supporting DW application sessions between an electronic device (ED) and a digital world (DW) application server (DWAS), wherein the DW application sessions can use data packets processed in a mobile network (e.g., in a CN or an access network (AN), or both). In some embodiments, the system may include an ED, an access network (AN) device, a session management function (SMF) device, and a DWAS: according to some embodiments, the AN device may be integrated into the infrastructure of the AN portion of the mobile network (MN), and the SMF device may be integrated into the infrastructure of the core network (CN) portion of the MN. In some embodiments, the ED and DWAS may be communicatively connected to the MN, and thus communicatively connected to the AN device, the SMF device, and the ED and DWAS may be communicatively connected to each other.

[0017] In some embodiments of the system, the DWAS may include processing electronics and may be used to provide a DW application for performing a DW application session between the ED and the DWAS, and to send one or more of the following to the ED: an indication that the DW application can be used for the DW application session and DW application session configuration information. The DW application session configuration information can be used by the ED when configuring the DW application session.

[0018] In some embodiments of the system, the ED may include processing electronics and may be used to receive one or more of the following: an indication that the DW application is available for a DW application session and DW application session configuration information. In some embodiments of the system, the ED may be used to request at least one uplink (UL) tunnel between the ED and the DWAS, or at least one downlink (DL) tunnel between the DWAS and the ED, or both. In some embodiments of the system, the ED may be used to receive an indication from at least one network function (NF) of the CN for processing at least a portion of the DW application session data. In some embodiments of the system, at least one UL tunnel or at least one DL tunnel, or both tunnels, may be at least partially located within the CN.

[0019] In some embodiments of the system, the SMF device may include processing electronics and may be used to receive DW application session establishment request information. According to some embodiments of the system, the SMF device may select one or more NFs from a plurality of network functions (NFs) integrated into the CN infrastructure, at least in part, based on the DW application session establishment request information. According to some embodiments of the system, the SMF device may request and receive DW application session information. The DW application session information may include an indication of at least one UL service function chain (SFC), or an indication of at least one DL SFC, or both. The DW application session information may also include one or more of the following: NF information indicating each NF in at least one ULSFC and NF information indicating each NF in at least one DL SFC. According to some embodiments of the system, one or more NFs may include each NF in at least one UL SFC, or each NF in at least one DL SFC, or both.

[0020] In some embodiments of the system, the AN device may include processing electronics and may be used to receive an indication that a DW application session establishment request has been accepted. In some embodiments of the system, after receiving the indication, the AN device may support one or more of the following: at least one DL tunnel and at least one UL tunnel. In some embodiments of the system, the AN device supporting at least one UL tunnel may include: adding an SFC header of at least one UL SFC to one or more UL data packets, and forwarding one or more UL data packets to at least one NF of at least one UL SFC.

[0021] According to embodiments, methods corresponding to the embodiments of the above-described apparatus and systems are provided. A method may involve the above-described operations and be performed by a suitable computerized device or system (e.g., an SMF device, an AN device, or an ED device, or a combination thereof).

[0022] According to an embodiment, an electronic device in a mobile (communication) network is provided, the device including a processor, a network interface, and a memory, and for performing one or more of the methods described herein. According to an embodiment, a system of such electronic devices is provided, which are networked together and used to interact to perform one or more of the methods described herein. For example, the electronic device may be an SMF device, an AN device, or an ED device.

[0023] According to embodiments of the present invention, a computer program product is provided, comprising (e.g., a non-transitory) computer-readable medium storing statements and instructions that, when executed by one or more computer processors, cause the computer processors to perform the methods described above. The computer processor may be part of one or more electronic devices (e.g., network entities) as described herein.

[0024] Embodiments have been described above in conjunction with aspects of the present invention, and these embodiments can be implemented based on these aspects. Those skilled in the art will understand that embodiments can be implemented in conjunction with the aspects described therein, but may also be implemented together with other embodiments of that aspect. It will be apparent to those skilled in the art that embodiments are mutually exclusive or incompatible. Some embodiments may be described in conjunction with one aspect, but may also be applicable to other aspects, as will be apparent to those skilled in the art. Attached Figure Description

[0025] Further features and advantages of the invention will become apparent from the following detailed description, taken in conjunction with the accompanying drawings, in which: Figure 1 The system architecture supporting DW application sessions and DW applications with in-network processing is shown.

[0026] Figure 2 A block diagram of a system supporting DW application sessions is shown. A DW application session involves the collaboration between an electronic device (ED) 121, a digital world application server (DWAS) 123, and several network functions.

[0027] Figure 3A and Figure 3B The process of ED 121 joining a DW application session is shown. Figure 3A Actions 301 to 308 of the process are shown. Figure 3B The remaining actions 309 to 318 of the process are shown.

[0028] Figure 4A and Figure 4B The data transfer between ED 121 and DWAS 123 via in-network data processing is shown. Figure 4A The data transmission actions 401 to 408 are shown. Figure 4B The remaining actions 409 to 414 of the data transmission are shown.

[0029] Figure 5 An electronic device that can be used to perform operations, according to an embodiment of the present invention, is shown.

[0030] It should be noted that similar features are identified by similar reference numerals throughout the accompanying drawings. Detailed Implementation

[0031] Virtual reality (DW) applications (such as digital twins and metaverse applications) have been designed for a variety of business applications, including gaming, virtual meetings, virtual music performances, virtual art exhibitions, telemedicine, virtual classrooms, shopping, and industrial automation. DW applications can be virtual world applications, augmented reality applications, virtual reality applications, mixed reality applications, or combinations thereof. DW applications can support multiple users interacting in a computerized virtual reality or augmented reality environment through enhancements such as sensors detecting user input via natural movement, voice, or other actions, and actuators presenting outputs to the user, such as visual outputs (e.g., changes in light, video screen output, personal headphone output) or tactile or other sensory outputs (e.g., air movement, temperature changes, sound, vibration, mechanical motion, etc.). The DW environment can be a faithful representation of the real environment, an artificial environment, or a modified real environment. DW applications can simultaneously support a potentially large number of participants from different locations. Participants can interact in real time. The system may collect a large amount of information from the environment, backend, application servers, network, and users, such as sensory data, video, audio, text, images, and data. From the collected information, the DW application can create suitable content and send it, at least partially, to participants in the form of video, audio, voice, data, and text to create an immersive experience for DW participants. DW participants can have multiple sensors, such as cameras, LiDAR, radar, audio sensors, and environmental sensors (e.g., temperature, wind speed and direction, rainfall, lighting conditions, smoke levels, dust levels, pollution levels) to collect environmental information and participant information. The collected data can be shared with the DW application server and other users. To support the DW application, the mobile network may need to provide a high-bit-rate, low-latency, and highly reliable communication link between the DW application server (AS) and the DW terminal. Fifth-generation (5G) mobile networks can provide the communication link to meet data connectivity requirements. It should be noted that a significant amount of data processing may be required to support the DW application. To achieve this, embodiments of the present invention provide at least some data processing within the mobile network, such as a radio access network (RAN) or the core network of the mobile network, or a combination thereof, also referred to as a communication network, which connects the DW terminal device to the DW application server. In addition, data processing is provided in a specific manner as described in this article.

[0032] In this invention, the mobile network can have computing infrastructure (processing infrastructure) to provide application services to mobile network users. The mobile network function (NF) and the application server (DW) can be hosted in the same data center. Current mobile network technologies (such as 4G or 5G mobile networks) may not be able to take advantage of deploying in the same data center that simultaneously hosts the application server. Therefore, the mobile network and application server require multiple types of signaling messages to support data sessions. In practical applications, the mobile NF and application server can be deployed in the same data center to support mobile users within a region. This invention provides a scheme utilizing this deployment model.

[0033] For example, refer to Figure 1One aspect of the invention relates to an uplink (UL) connection between an electronic device (ED) 121 and a digital world application server (DWAS) 123. Establishing a UL connection may involve classifying and notifying ED 121 of UL data packets, performing intra-network data processing, and providing ED 121 with a set of packet filters and packet tags for UL data streams to be processed in CN 128. The destination address (e.g., IP header and port number) is a server in mobile network 131, such as a server in CN 128, or a server in data network (DN) 129. Establishing a UL connection may require establishing and configuring multiple tunnels from access network (AN) 127 to different NFs to support UL data streams from AN 127 to different destinations in CN 128 or DN 129. Therefore, after receiving a DW application session establishment request from ED 121, MN131 can be used to support at least one UL tunnel between ED 121 and DWAS 123, or at least one DL tunnel between DWAS 123 and ED 121, or both. AN 127 can be used to add a service function chain (SFC) header (e.g., including message processing instructions, message disposal instructions, and SFC ID) to a UL datagram and forward the UL datagram to at least one NF in the mobile network, which can be an NF in a UL SFC. Establishing a UL connection may also involve notifying the last network function in the SFC of the corresponding UL data stream of the destination address to which the processed UL datagram is sent. Data plane gateway (DPGW) 112 can be used to forward the processed UL datagram to DWAS 123. The last network function of the UL SFC can update the message header to include the DWAS 123 address. Establishing a UL connection may also involve configuring the DPGW 112 to perform network address translation (NAT) for the UL data stream after processing within the network.

[0034] Another aspect of the invention relates to a downlink (DL) connection between DWAS 123 and ED 121. Establishing a DL connection may require establishing and configuring multiple DL tunnels and DL SFCs from another server in DWAS 123 or CN 128 to different NFs to support DL data flows from DWAS 123 (the server in DN 129) to ED 121. Establishing a DL connection may involve providing a set of packet filters to DWAS 123 or DPGW 112 or both to classify DL data packets into multiple DL data flows. Establishing a DL connection may also involve providing SFC header information (e.g., SFC ID, source NF ID, destination NF ID, packet processing instructions, packet disposal instructions) to DPGW 112 to add to DL data packets of DL data flows that require in-network data processing. The last network function of the SFC for the corresponding DL data flow may be instructed to remove the SFC header information. Establishing a DL connection may also involve providing a destination address (e.g., ED 121 address) for the last network function of the SFC of the DL data stream, to which the processed DL datagram is sent.

[0035] In some embodiments of the present invention, reference is made again. Figure 1 MN 131 can provide sensing capabilities to perceive the environment, detect objects, and track the movement and actions of objects. MN 131 can provide functions to acquire sensed data, process sensed data, and convert real-world (RW) data into a digital-world (DW) data format to be used by DW applications. MN 131 can be (conceptually, practically, or both) classified as AN 127 and CN 128. Figure 1 The network system architecture with DW support capabilities of AN 127 and CN 128 is shown. The DW support capabilities of AN 127 and CN 128 are collectively referred to as network for digital world (NET4DW) 124.

[0036] ED 121 may be equipped with or operatively coupled to sensors, such as cameras, lidar, radar, audio sensors, gyroscope sensors, position estimation sensors, and environmental sensors, to collect user information, user input and behavior, information about other users, information about other nearby objects, and environmental information of environment 119. ED 121 may also have or be operatively coupled to actuators to provide control functions, as well as control devices, such as video displays, lighting, speakers, mechanical devices, and robots. ED 121 may have computing resources, such as microprocessor chips, memory devices, storage devices, and input / output interfaces. ED 121 may also have wired interfaces for connecting to other devices and mobile networks, wireless interfaces for direct or indirect connection to MN 131, and wireless management. If ED 121 is connected to AN 127 via user equipment (UE), the UE may have applications supporting ED 121. For example, the UE can transparently forward data received from ED 121 via AN 127 and CN 128 to DWAS 123. In another example, ED 121 can send uncompressed video data captured by its camera to the UE for video compression. The UE can then send the compressed video to DWAS 123. The UE can convert RW sensor 117 data captured by ED 121 into the DW data format required by DWAS 123. The UE can also convert DW actuator commands into RW actuator commands usable by the actuators of ED 121. DWAS 123 can provide application services to ED 121, including computing resources (processing resources).

[0037] AN 127 may have one or more transmitter (Tx) and receiver (Rx) components (collectively shown as Tx / Rx) 114, sensors 117, and functions supporting data transmission, reception, and service. Tx component 114 may transmit radio signals to UEs and DW terminals. The radio signals may carry data packets from the UEs and DW terminals. The radio signals may also carry sensing signals to detect other UEs, objects, humans, movement, environmental changes, and other information. Rx component 114 may receive radio signals transmitted by UEs and DW terminals (e.g., ED 121 and UE). Rx component 114 may also receive radio signals, sensing signals, or combinations thereof transmitted by one or more other Tx components and subsequently reflected from ED 121, UE, other UEs, other DW terminals, and objects in the environment.

[0038] AN 127 may be equipped with sensors to perceive the environment and receive information from DW terminals and UEs operatively coupled to AN 127. Sensors may include radar, lidar, cameras, recorders, still cameras, thermal sensors, infrared sensors, wind sensors, gyroscopes, position estimation sensors (e.g., GPS devices), and other environmental sensors. AN 127 may also be equipped with RW actuators 118 to interact with the environment. RW actuators 118 may be machine controllers, such as light switches, room temperature controllers, robots, video displays (e.g., smartphone screens and head-mounted displays), augmented reality (AR) / virtual reality (VR) glasses, audio players, public address systems, and screens. In some embodiments, by integrating sensors and actuators into MN (e.g., AN 127 shown here), sensors and actuators can support multiple DW applications as needed (e.g., simultaneously). This enables more timely or efficient delivery of DW applications because each user does not need to provide their own sensors and actuators. Furthermore, sensors and actuators can be more tightly integrated into the MN to improve operation, compatibility, and management.

[0039] AN 127 may have a localization function (LF) 115 to coordinate the operation of Tx / Rx units (including Tx / Rx 114). LF 115 provides position estimates for ED 121, UE, humans, animals, birds, vehicles, flying objects, and any other objects.

[0040] In various embodiments, AN 127 may also have a sensing function (SF) 116 to coordinate the operation of sensors 117 of AN 127. SF 116 can acquire sensor data from sensors 117 and transmit the sensor data to other functions integrated in CN 128 for further processing. AN 127 may have additional functions to support other tasks such as wireless transmission scheduling. In some embodiments, SF also coordinates the operation of additional sensors that are not part of MN but are operatively coupled to MN.

[0041] The functions integrated in CN 128 can be arranged as CN control plane (CNCP) 125 functions and CN data plane (CNDP) 126 functions. CNCP 125 functions control the operation of MN 131 and user equipment (e.g., ED 121) connected to MN 131. CNDP 126 functions process and transmit data generated or collected by users, UEs, DWTs, application servers, and MN 131.

[0042] CNCP 125 functionality may include a connection management function (CMF) 101. CMF 101 can manage the access of ED 121 (or UE) to MN 131. CMF 101 can also manage the location data of ED 121. CNCP 125 may also include a session management function (SMF) 102 for managing DW application sessions between the ED and the application server; a control plane gateway function (CPGW) 108 for providing an interface between the network functions of CNCP 125 and functions other than MN 131; an authorization function (AuF) 105 for authorizing the ED and UE to access MN services; a policy function (PF) 104 for providing policies for managing MN 131 and ED 121; a location management function (LMF) 106 for managing location services of MN 131, such as tracking mobility, location of the ED and UE, and location of objects in the environment; and a digital world support function (DWSF) 107 for supporting DW applications hosted in DN 129. DW applications can be hosted in DWAS 123. DWAS 123, together with other DW application servers, defines DW nodes (DWNs) 130. DW applications hosted on DWAS 123 can have connections to other DW applications hosted on one or more other application servers in DN 129, another data network, or a combination thereof. DWSF 107 can select and configure additional functions in response to requests to support DW application sessions as directed by the digital world controller (DWC).

[0043] In various embodiments, the network entity repository (NER) 132 stores a database of all network entities in AN 127, CN 128, and DN 129. Each network entity (NE) may have a network entity profile stored in the NER 132, including network functions in the control plane (CP) and data plane (DP), as well as other network devices such as sensors, actuators, UEs, and routers. The network entities tracked by the NER 132 may include sensors 117 and actuators 118, ED 121, Tx / Rx 114, any NFs in AN 127 and CN 128, DWC 122, and DWAS 123. Each network entity in AN 127, CN 128, and DN 129 may send an NE profile request to the NER 132 to obtain NE profile information about other network entities. The NER 132 may send an NE profile response with such information to the requester. A network entity requester can select one or more NEs based on the information provided in its NE profile response using NER 132. In some implementations, the network entity requester can leverage NER 132 support to discover and select network entities in the mobile network domain or application servers in the data network domain.

[0044] The data storage function (DSF) 103 can manage the storage of data for MN 131, such as user (e.g., ED 121) subscription data, user and network policies, application data, analytics data related to ED 121 and NF, network operations, and network slice data.

[0045] The compute resource management function (CRMF) can belong to the compute management plane (CMP) or CNCP. CRMF manages compute resources (processing resources) in mobile networks. CRMF selection can be based on network slice information, such as data network name (DNN), single-network slice selection assistance information (S-NSSAI), and application identifier (ID).

[0046] The CNDP 126 may include: a location data processing function (LDPF) 109 for processing location and sense data transmitted from AN 127 or other sources; a real-world to digital-world adaptation function (R2DAF) 110 for performing real-to-digital data adaptation tasks (e.g., real-world (RW) sensor data received from AN 127 can be converted to digital-world (DW) format via R2DAF 110); and a digital-to-real-world adaptation function (D2RAF) 111 for performing digital-to-real-world data adaptation tasks. The CNDP 126 may also include a data plane gateway (DPGW) 112 to provide a data transmission interface between MN 131 and other data networks, including a DN hosting DW applications. DPGW 112 can serve as a network application gateway, acting as a gateway interface for both mobile networks (e.g., MN 131) and carrier application networks (e.g., DN 129). DPGW 112 can support DNS queries to the local DNS server, the firewall of DN 129, mobile anchors, and terminal tunnels to AN 127.

[0047] A network function (NF) can have multiple instances. Each NF instance can be selected to serve one or more DW applications. In this way, the same network infrastructure (which may have sensing devices, actuator devices, or both) can serve multiple DW applications. R2DAF 110 can receive RW sensor data, convert it into digital world information, and forward that information to DWAS 123. D2RAF 111 can be used to receive information from DWAS 123, convert it into actuator commands, and forward those commands to the appropriate actuators.

[0048] In some embodiments, the DW application can transmit DW configuration information to MN 131. For example, the DW application can transmit artificial intelligence (AI) (or machine learning (ML)) model information to MN 131 to detect RW objects. The AI ​​model can be represented by an AI model ID. The AI ​​model includes neural network parameters. The AI ​​model can be used to process different types of sensor data provided by wireless transceivers, cameras, sound sensors, LiDAR, radar, or other types of sensors, such as video data, audio data, sensor data, and text data. Each DW object can represent an RW object, identified by a DW object ID. A DW object can represent a person or object, such as a car, bus, table, traffic sign, etc. In the DW application, a person can be represented by an avatar. DW object characteristics can include a list of parameters. For example, a person DW object characteristic can include one or more of the following parameters: hair color, eye color, hairstyle, glassware, a list of 3D photos showing the face at different angles, etc. Each RW object can be converted into a DW object. RW objects can be detected by analyzing sensor data. Real-world to digital-world (R2D) data adaptation information provides a mapping between RW objects and their RW ​​characteristics and DW objects and their DW characteristics. DW applications can also transmit RW actuator information to the mobile network. RW actuator information may include one or more of the following: DW application ID, external actuator ID, actuator address (e.g., IP address and port number, Ethernet address), actuator type, and QoS parameters. The DWAS 123 entry point indicates the location where MN 131 can send ED and UE data to DWAS 123. For example, the DWAS 123 entry point can be an Internet exchange point (IXP), IP address, port number, Ethernet address, or a combination thereof.

[0049] In some embodiments of the present invention, DWSF 107 or DWAS 123 can notify ED 121 of a DW application session by sending a DW application session ID to ED 121. For example, DWSF 107 can send a control plane message with a DW application session ID via CMF 101. After receiving the control plane message with the DW application session ID, ED 121 can request to establish a DW application session by sending a DW application session establishment request (with the DW application session ID) to the NF of MN 131. The NF (e.g., SMF 102) can optionally receive the DW application session establishment request. In response to receiving a DW application session establishment request, SMF 102 can configure the network function (NF) of CNDP 126 (or, for example, the user plane in a 5G network) and other network entities communicatively coupled to CNDP 126 to connect AN 127 with DPGW 112 and in-network data processing functions (e.g., LDPF 109, R2DAF 110, and D2RAF 111). Therefore, SMF 102 can configure at least one NF in at least one UL SFC to process one or more UL datagrams based on the DW application ID and the data processing ID of at least one NF in at least one UL SFC. At least one NF in at least one UL SFC can also be used to send one or more processed UL datagrams to the next NF in at least one UL SFC. The last NF in at least one UL SFC can also be used to send one or more processed UL datagrams to DWAS 123. SMF 102 can configure at least one NF in at least one DL SFC to process one or more DL datagrams based on the DW application ID and the data processing ID of at least one NF in at least one DL SFC. At least one NF in at least one DL SFC can also be used to send one or more processed DL datagrams to the next NF in at least one DL SFC. The last NF in at least one DL SFC can also be used to send one or more processed DL datagrams to ED 121. Before configuring the NFs and network entities of CNDP 126, SMF 102 can request and receive DW application session information from DSF 103 or DWSF 107. A DW application session information request from SMF 102 may include the DW application session ID, information from DWC 122, and information from DWAS 123. The information from DWC 122 may include one or more IDs from the DWC 122 ID.The information for DWAS 123 may include one or more of the following: DWAS 123's ID, DWAS 123's address information (such as fully qualified domain name (FQDN), DWAS 123's IP address and port number), and DWAS 123's entry point information.

[0050] In some embodiments, SMF 102 can discover DWSF 107 by requesting and receiving DWSF profile information from NER 132. The request for DWSF profile information by SMF 102 may include the DW application session ID, the ID of DWC 122, and the entry point of DWAS 123.

[0051] To support DW application sessions, SMF 102 can configure ED 121 and provide it with at least one data flow ID and at least one uplink (UL) message filter. The UL message filter is used to map UL data packets to data flows. UL data packets can be processed in MN 131, for example, in CN 128, or outside of MN 131. SMF 102 can also provide ED 121 with an in-network data processing (INDP) indication, which indicates that the data flow carries UL packets to be processed at the local data processing function. The INDP indication can be an ID of a service function chain (SFC). ED 121 can also map UL data packets to UL data flows. For UL data packets to be processed in the network, ED 121 can add an INDP indication to the UL data packets within the UL data flow.

[0052] Figure 2 A block diagram of a system that supports DW application sessions is shown. Figure 2 The schematic diagram can be regarded as Figure 1A simplified version is shown, with arrows illustrating the information flow relevant to embodiments of the invention. UL data streams from ED 121 are sent directly (when in-network processing is not required) or via NET4DW 124 to DWAS 123 to maintain in-network processing of these UL data streams. For example, UL data stream 203 from ED 121 is sent directly to DWAS 123. UL data stream 204 is sent to DWAS 123 via NET4DW 124 of MN 131. DL data streams from DWAS 123 are sent directly (when in-network processing of DL data is not required) or via NET4DW 124 to ED 121 to provide in-network processing for these DL data streams. For example, DL data stream 205 is sent from DWAS 123 to ED 121 via NET4DW 124 because this DL data stream requires in-network processing. DL data stream 206 bypasses NET4DW 124 in MN 131 and is sent directly from DWAS 123 to ED 121. SMF 102 can provide ED 121 with the address of the first NF in the UL SFC. ED 121 can send UL datagrams to be processed in CN128 to the provided address of the first NF in the UL SFC. For example, ED 121 can send UL datagrams to UL SFC 201, such as... Figure 2 As shown.

[0053] SMF 102 can provide UL tunnel information to AN 127. In the UL tunnel information, UL data streams are mapped to UL tunnels; each UL tunnel can transmit UL data packets to DPGW 112 or NET4DW 124 (internal SFC). AN 127 can forward UL data packets directly to DPGW 112 or to the local data processing NF of the SFC in CN 128. For some UL data streams, SMF 102 can provide an SFC header to AN 127 so that AN 127 can add the appropriate SFC header to the UL data packet (the SFC header may include the SFC ID, the ID of the source NF, the ID of the destination NF, and message processing instructions). Therefore, AN can be used to add SFC headers to UL data packets and subsequently forward the UL data packets to NFs in the SFC. According to some embodiments, SMF 102 can provide the SFC header to any NF or entity in MN 131 or DN 129. For example, SMF 102 can provide SFC headers to AN 127, LDPF 109, R2DAF 110, D2RAF 111, DPGW 112, and DWAS 123.

[0054] SMF 102 can provide external INDP instructions and DL INDP packet filters to DWAS 123 to facilitate the mapping of DL data packets to appropriate data flows and their processing within the network before forwarding them to ED 121. Each DL INDP packet filter and each DL packet filter may include one or more DL headers with the IP address and port number of the corresponding DL tunnel or corresponding DL SFC. (Therefore, each UL INDP packet filter and each UL packet filter may include one or more UL headers with the IP address and port number of the corresponding UL tunnel or corresponding UL SFC). INDP packet filters may be separate from or integrated with more general packet filters (if present). DPGW 112 can forward DL data packets to the appropriate DL data flows. DL data packets awaiting processing in CN 128 can be directed by DPGW 112 to the appropriate DL tunnel that processes the DL data packets. For example, DL data packets can be directed to DL SFC 202, such as... Figure 2 As shown. SMF 102 can provide the DL SFC address (e.g., the IP address and port number of the first NF in the DL SFC) to DWAS 123 or DWC 122. DWAS 123 can use the DL SFC address as the destination to send DL datagrams to the selected SFC of CN 128. The last NF of the DL SFC can add the ED 121 address (e.g., the IP address and port number of ED 121) to the processed data and can send the processed DL datagram to ED 121.

[0055] SMF 102 can configure DPGW 112 or DWAS 123 to map DL data stream IDs to DL tunnels. In the downlink, DPGW 112 or DWAS 123 can classify DL data packets to DL tunnels based on DL packet filters. Therefore, SMF 102 can configure DWAS 123 or DPGW 112 to add an SFC header of at least one DL SFC to one or more DL data packets and forward one or more DL data packets to at least one NF in at least one DL SFC. DPGW 112 or DWAS 123 can forward DL data packets directly to AN 127 or to the local data processing NF of the DLSFC in CN 128. For INDP DL data packets, DPGW 112 or DWAS 123 can add an SFC header field to the DL data packet. The SFC header field of a UL or DL ​​SFC may include one or more of the following: SFC ID, the ID of the source NF sending the data packet (e.g., the ID of DPGW 112), the ID of the destination NF receiving the data packet (e.g., the ID of D2RAF 111), and message processing instructions. For example, message processing instructions may include instructions for performing real-world to digital-world data conversion or digital-world to real-world data conversion.

[0056] Some UL messages can be processed in CN 128. After processing, the UL data packets can be sent to DPGW 112. DPGW 112 can replace some header fields and then forward the UL data packets to DWAS 123. DPGW 112 can use some UL network address translation (NAT) tables of UL data streams to replace some header fields.

[0057] DWC 122 of DWAS 123 can send a DW application configuration request to CN 128. In response to the DW application configuration request, CN 128 can select one or more NFs and create a service function chain (SFC) to process UL datagrams, DL datagrams, or both from ED 121. CN 128 can provide DWC 122 with one or more SFC IDs for each required DW service. For example, UL SFC 201 processes UL datagrams for the digital representation of an object and may include LDPF 109 and R2DAF 110, such as... Figure 2 As shown. In another example, the SFC, represented as DL SFC 202, processes downlink messages controlling the actuator. DL SFC 202 may include D2RAF 111.

[0058] Figure 3A and Figure 3B The process of ED 121 joining a DW application session is illustrated. In action 300, ED 121 may receive a DW application session configuration message, thereby notifying ED of the DW application session. The DW application session configuration message may be sent by DWAS 123 or DWSF 107. The DW application session configuration information in the DW application session configuration message may include one or more of the following: DW application session identifier (ID), DW application ID, and data flow information. Therefore, ED 121 may be used to receive an indication of the availability of the DW application in the DW application session, or DW application session configuration information, or both. The data flow information may include parameters of more than one data flow. Each UL data flow may be represented by one or more of the following: UL data flow ID, UL SFC ID, UL SFC header, and corresponding QoS requirements. Each DL data flow information may include one or more of the following: DL data flow ID, DL SFC ID, DL SFC header, and corresponding QoS requirements. The header of a UL SFC may include one or more of the following: UL SFCID, the address of the UL SFC, the DW application ID, and the corresponding message processing instructions. The header of a DL SFC may include one or more of the following: DL SFC ID, the address of the DL SFC, the DW application ID, and the corresponding message processing instructions. The SFC ID can be an external SFC ID or an internal SFC ID. DWSF 107 may store a mapping between external and internal SFC IDs. After receiving a DW application session configuration message, ED 121 may send one or more of the following to DWAS 123 or DWSF 107: a response to DW application session information, consent to process DW application session data in CN 128 (or refusal to process DW application session data in CN 128). In various embodiments, the term "consent" may be replaced by the term "permission".

[0059] In Action 301, ED 121 may send a DW application session establishment request message to CN 128 via AN 127. The DW application session establishment request message may include at least a portion of a DW application session configuration message (provided by DWAS 123 or DWSF 107). This message may include one or more of the following: data network information identifying the data network, such as a data network name (DNN); network slice information identifying the network slice; an indication to consent to in-network data processing of DL datagrams or UL datagrams or both; and an indication to refuse in-network data processing of DL datagrams or UL datagrams or both. The network slice information may include a network slice ID (NSI) and single-network slice selection assistance information (S-NSSAI). The DW application session establishment request message may also include service information provided by DN 129 to identify the service. For example, the service information may include a service ID. The service may be an AI service. The DW application session establishment request message may also include DW application information to identify the application provided in DN 129. The DW application session establishment request information may include a DW application ID, an application profile ID, and a DW application session ID. The application may support object detection based on sensor data, such as object detection from images, video signals, wireless signals, LiDAR signals, and radar signals; and object detection via video and / or audio split rendering for augmented reality (AR), virtual reality (VR), mixed reality (MR), digital twins, digital worlds, and metaverse applications. The DW application ID identifies the DW application. The application profile ID identifies the application profile stored in CN 128 (e.g., in DSF 103). The application profile may also include a list of parameters for each application. For example, a metaverse application profile may include information indicating a digital object (e.g., a virtual avatar) representing the user requesting the establishment of a DW application session. The DW application session establishment request may also include application requirements such as video descriptions, image resolution, bitrate, and image size. The DW application session establishment request information may also include one or more of the following: ED identifier (ID), ED location information, and data stream information. The data stream information in the DW application session establishment request information may include one or more data stream IDs, as well as the QoS requirements for each data stream.The data flow information may also include the ID of at least one UL SFC, or the ID of at least one DL SFC, or both.

[0060] In Action 302, AN 127 may forward the DW Application Session Establishment Request message to CMF 101. This message may also include the ED location. The ED location may include one or more of the following: cell ID, AN 127 address (e.g., the IP address of AN 127's port number), geographic location (e.g., two-dimensional (2D) location, three-dimensional (3D) location), and tracking area (TA) ID.

[0061] In action 303a, CMF 101 may send an ED subscription data request to DSF 103. After receiving the ED subscription data request, DSF 103 may send an ED subscription response to CMF 101. This response may include ED subscription data.

[0062] In action 303b, CMF 101 may send an ED connection policy request message to PF 104 to request a connection policy from ED 121. PF 104 may send an ED connection policy response message back to CMF 101. The ED connection policy response message may include one or more of the following: an indication that the ED connection policy request is accepted, an indication that the ED connection policy request is rejected (providing a reason or error code or both), and connection policy information. The connection policy information may specify whether ED 121 is allowed to establish a data connection to the computing services (processing services) of CN128 (e.g., LDPF 109 and R2DAF 110). The connection policy may include descriptions of SFCs in UL tunnels and DL tunnels to handle UL data packets and DL data packets respectively.

[0063] In action 303c, if ED 121 is allowed to establish a data connection, CMF 101 can select SMF 102 to provide the data connection for ED 121. CMF 101 can use information provided by ED 121, ED location, and ED subscription data to select SMF 102. CMF 101 can send an NE profile request message to NER 132 to discover the SMF instance. This message can include EDID, ED location, DW application ID, DW application session ID, and application profile ID. NER 132 can send an NE profile response message back to CMF 101. This message can include a list of SMF profiles. CMF 101 can select SMF 102 from the provided SMF profiles. CMF 101 can also select SMF 102 from pre-configured information stored in or accessible by CMF 101.

[0064] In action 304, CMF 101 may send a DW application session establishment request message to SMF 102. This may be a forwarded version of the message received in action 302, possibly modified. For example, CMF 101 may include additional ED information received in action 302, such as ED location information and ED ID, in the request. ED location information may be represented by one or more of AN 127 node ID, AN address, cell ID, citizen address, 2D location, 3D location, or any identifier that can be used to identify the location of a wireless node providing wireless or wired connectivity to ED 121. In some embodiments, CMF may include information received in actions 303a, 303b, or 303c in the request.

[0065] In action 305a, after receiving a DW application session establishment request message from CMF 101, SMF 102 can request and receive ED subscription data from DSF 103. SMF can send an ED subscription data request message to DSF 103. This message may include one or more of the following: ED ID, ED location information, DW application session ID, and the DW application ID requested by ED 121. DSF 103 can send an ED subscription data response to SMF 102. The ED subscription data response may include ED subscription data. SMF 102 can use the ED subscription data to determine whether to allow ED 121 to access the requested DW service.

[0066] In action 305b, SMF 102 may send an ED session policy request message to PF 104 to request ED session policy information. This message may include one of the multiple ED information elements received in actions 304 and 305a. PF 104 may send an ED session policy response message to SMF 102. This message may include ED session policy information and an indication of whether ED 121 is permitted to use the requested DW application. This message may also include SFC information with one or more of the following: SFC ID, a list of network functions (NFs) in the SFC. The list of NFs in the SFC may specify the order in which the NFs will process the datagrams. The list of NFs may include the address (e.g., IP address and port number) of each NF in the SFC.

[0067] In Action 305c, SMF 102 can discover DWSF 107 that can serve a DW application session. SMF 102 can send an NE profile request message to NER 132. This message may include the ED ID, ED location, DW application session ID, and DW application ID. NER 132 can use the provided information to obtain the DWSF profile. NER 132 can send an NE profile response message back to SMF 102. This message may include one or more DWSF profiles. The DWSF profiles can identify all DWSFs and their instances that can be used to support a DW application session, as specified in CN 128. The DWSF profiles can also provide parameters for the DWSF (and its instances).

[0068] In action 306a, based at least in part on the DWSF profile, SMF 102 can select DWSF 107. SMF 102 can send a DW application session information request message to the selected DWSF 107. This message may include one or more of the following: ED ID, ED location, DW application ID, DW application session ID, and one or more SFC IDs.

[0069] In Action 306b, DWSF 107 can use the information received in Action 306a to collect information related to the DW application session. DWSF 107 can send a DW application session information response message to SMF 102. This message may include one or more of the following: an indication of the UL SFC; an indication of the DL SFC; one or more SFC IDs; a DW application ID; and NF information indicating the NF (e.g., UL SFC, DL SFC, or both) in the corresponding SFC, such as LDPF information, R2DAF information, D2RAF information, DPGW information, and DWAS information. For each NF, the NF information may include one or more of the following: NF type (e.g., LDPF, R2DAF, D2RAF, DPGW), NF ID, SFC ID, SFC location number, NF address information (e.g., IP address and port number, FQDN, URL), NF profile, NF payload, and data processing ID. The SFC ID indicates the ID of the SFC to which the NF belongs. The SFC location number indicates the location of the NF in the SFC (e.g., location number 1, 2, 3, etc.). A data processing ID can indicate the processing task that an NF (Network Function) is to perform. For example, a data processing ID can indicate a data privacy protection task, in which privacy data is removed or encrypted by the NF. In another example, a data processing ID can indicate a task used to estimate the location of an object from wireless signals, radar signals, video signals, images, or thermal signals.

[0070] In some implementations, SMF 102 may receive an instruction from ED 121 in action 304 to consent to in-network data processing (INDP) of DL data packets, UL data packets, or both. Upon receiving the instruction to consent to INDP, SMF 102 may select one or more NFs. For example, SMF 102 may select LDPF 109 and R2DAF 110 to process UL data packets, or select D2RAF 111 to process DL data packets.

[0071] In some implementations, SMF 102 may receive an instruction from ED 121 in action 304 to refuse intra-network data processing of DL data packets or UL data packets, or both. Upon receiving the instruction to refuse INDP processing of DL data packets or UL data packets, or both, SMF 102 may therefore not select an NF to process the DL data packet, or not select an NF to process the UL data packet, or both.

[0072] In some implementations, DWSF 107 may not need to provide the NF ID of the NF in the SFC. In this case, SMF 102 can send one or more NF profile requests to NER 132 based on the NF type described in the SFC information received from DWSF 107 to discover NF instances in the UL SFC and DL SFC. NER 132 can send one or more NF profile responses to SMF 102, each NF profile response may include one or more NF profiles of the NF instance, such as NF profiles for LDPF, R2DAF, D2RAF, and DPGW. SMF 102 can select one or more NF instances from the provided NF profiles to support the UL SFC and DL SFC specified by DWSF 107.

[0073] In Action 307a, SMF 102 may select DPGW 112 using DPGW information provided by DWSF 107 in Action 306b or DPGW information provided by NER 132, or a combination thereof. SMF 102 may send a DPGW data plane establishment request message to DPGW 112. This message may include one or more of the following: the NF ID (or ID of SMF 102), the NF ID (or ID of DPGW 112), the DP session ID between SMF 102 and DPGW 112, the DW application session ID requested by ED 121 to indicate the DW application session, and data flow information. Data flow information may include one or more of the following: data flow ID, DL or UL indication, SFC ID, SFC information, SFC header information, QoS parameters, UL and DL packet filters, and UL and DL network address translation (NAT) tables. QoS parameters may include any combination of QoS group indexes and values. QoS parameters can be one or more of the following: average data stream bit rate, maximum data stream bit rate, packet delay budget, and packet loss rate. As an illustrative example, QoS parameters could include the following values: average data stream bit rate of 10 Mbit / s, maximum data stream bit rate of 15 Mbit / s, packet delay budget of 50 ms, and packet loss rate of 0.1%. A QoS group index can be a normalized index representing combinations of QoS parameter values.

[0074] In the UL NAT table, one or more of the UL SFC flow source address and UL SFC flow destination address (e.g., IP address and port number) can be assigned to each UL flow ID or each corresponding UL message filter or a combination thereof. UL message filters can include one or more source addresses and one or more destination addresses in the message header. The DPGW 112 can examine the UL message header to identify whether the UL message header fields match entries in the UL NAT table. If an entry in the UL NAT table matches, the DPGW 112 can replace one or more of the source address and destination address in the UL message header with the corresponding one or more of the UL SFC flow source address and UL SFC flow destination address specified in the matching UL NAT table entry.

[0075] In the DL NAT table, one or more of the DL SFC flow source address and DL SFC flow destination address (e.g., IP address and port number) can be assigned to each DL flow ID or each corresponding DL packet filter or a combination thereof. DL packet filters can include one or more source addresses and one or more destination addresses in the packet header. The DPGW 112 can examine the DL packet header to identify whether the DL packet header fields match entries in the DL NAT table. If an entry in the DL NAT table matches, the DPGW 112 can replace one or more of the source address and destination address in the DL packet header with the corresponding one or more of the DL SFC flow source address and DL SFC flow destination address specified in the matching DL NAT table entry.

[0076] Message filters may include indications from the DPGW 112 header fields used to classify DL data packets (matching DL data packets) into DL data streams. SFC information may include information from one or more NFs. For example, such as... Figure 2 As shown, LDPF109 is the upstream NF that sends datagrams to the current NF (e.g., R2DAF 110). Upstream NF information may include NF ID and NF address (e.g., IP address and port number). The downstream NF (e.g., R2DAF 110) is the NF to which the current NF (e.g., LDPF 109) will send datagrams. Downstream NF information may include NF ID, NF address information, and tunnel endpoint ID. Therefore, the terms upstream and downstream are used to indicate the order of NFs relative to the data flow. Conversely, the terms uplink and downlink are used to indicate the direction of data transmission toward DWAS (uplink) or ED (downlink).

[0077] The DPGW 112 can be connected to more than one SFC. Figure 2The diagram shows DPGW 112 connected to UL SFC 201 and DLSFC 202. UL SFC 201 processes UL data messages for digital representation of objects. This SFC includes two network functions: LDPF 109 and R2DAF 110. DL SFC 202 processes DL data messages controlling actuators and includes one network function: D2RAF 111.

[0078] Upstream and downstream NFs do not necessarily belong to SFC. For example, AN 127 is the upstream NF of the first NF (LDPF109) in UL SFC 201. DPGW 112 is the downstream NF of the last NF (R2DAF 110) in UL SFC 201.

[0079] In Action 307b, DPGW 112 can allocate its resources to support DW application sessions. DPGW 112 can send a DPGW data plane establishment response message to SMF 102. This message may include one or more of the following: the NF ID of DPGW 112, the NF ID of SMF 102, the DP session ID, the DW application session ID, and upstream tunnel information (e.g., the IP address, port number, and tunnel endpoint ID (TEID) of DPGW 112) for use by the upstream NFs (AN 127 and R2DAF 110) to send datagrams to the current NF (DPGW 112).

[0080] In action 308a, SMF 102 may select an NF in the UL SFC, such as R2DAF 110, based on R2DAF information provided by DWSF 107 in action 306b or R2DAF information provided by NER 132, or a combination thereof. SMF 102 may send an R2DAF data plane establishment request message to R2DAF 110 to establish a data connection between R2DAF 110 and other NFs (such as LDPF 109 and DPGW 112). This message may include one or more of the following: the NF ID of SMF 102, the NF ID of R2DAF 110, the DP session ID, the DW application ID, the DW application session ID, the SFC ID, the data processing ID, and data flow information.

[0081] The DW application ID can indicate the requested DW application, such as a smart city infrastructure management application, an autonomous driving application, or a healthcare application. The data processing ID can indicate a specific task of the DW application, such as a real-world to digital-world data conversion task. Data flow information can include parameters as described in Action 307a. For R2DAF 110, the upstream NF is LDPF 109, and the downstream NF is DPGW 112. Downstream NF information can include the IP address, port number, and tunnel endpoint ID (TEID) received by SMF 102 in Action 307b. Data flow information can include the destination address to which R2DAF 110 can send the UL datagram after processing. The destination address can be the address of DWAS 123 (e.g., IP address and port number). R2DAF 110 can add the destination address to the UL datagram.

[0082] In Action 308b, R2DAF 110 can allocate or commit some or all of its resources to support DW application sessions. R2DAF 110 can send an R2DAF data plane establishment response message to SMF 102. This message may include one or more of the following: R2DAF 110's NF ID, SMF 102's NF ID, DP session ID, DW application session ID, and upstream tunnel information (e.g., R2DAF 110's IP address, port number, and tunnel endpoint ID (TEID)), for the upstream NF (LDPF109) to use to send datagrams to the current NF (R2DAF 110).

[0083] In action 309a, based on LDPF information (received in action 306b, received by NER 132, or a combination thereof), SMF 102 can select LDPF 109. SMF 102 can send an LDPF data plane establishment request message to LDPF 109 to establish a data connection between AN 127 and LDPF 109. This message may include one or more of the following: DP session identifier, DW application session identifier, SFC ID, DW application ID, data processing ID, and data flow information. The DW application ID may indicate the requested DW application, such as a smart city infrastructure management application, an autonomous driving application, or a healthcare application. The data processing ID may indicate a specific task of the application. For example, it may be a task for estimating the location of ED 121. The data flow information may include parameters as described in action 307a. For LDPF 109, the upstream NF is AN 127, and the downstream NF is R2DAF 110. Downstream NF information may include the IP address, port number, and TEID of R2DAF 110 received by SMF 102 in Action 308b. Upstream NF information, i.e., information about AN 127, may include the address of AN 127, such as IP address and port number.

[0084] In Action 309b, LDPF 109 may allocate or commit some or all of its resources to process datagrams sent from other NFs. LDPF 109 may use the DW application session ID to identify the resources required to support the DW application session. LDPF 109 may send an LDPF data plane establishment response message to SMF 102. This message may include one or more of the following: the NF ID of LDPF 109, the NF ID of SMF 102, the DP session ID, the DW application session ID, and upstream tunnel information. The upstream tunnel information may include information about LDPF 109 (e.g., IP address, port number, TEID) for AN 127 to use when sending datagrams to LDPF 109.

[0085] In action 310a, SMF 102 may select D2RAF 111 from, for example, a plurality of potential D2RAFs, based on D2RAF information provided by DWSF 107 in action 306b or D2RAF information provided by NER 132, or a combination thereof. After selection, SMF 102 may send a D2RAF data plane establishment request message to D2RAF 111. The data plane connects D2RAF 111 to AN 127 and DPGW 112. This message may include one or more of the following: the NF ID of SMF 102, the NF ID of D2RAF 111, the DP session ID, the DW application session ID, the SFC ID, the DW application ID, the data processing ID, and data flow information.

[0086] The DW application ID can indicate the requested DW application, such as a smart city infrastructure management application, an autonomous driving application, or a healthcare application. The data processing ID can indicate the specific task the DW application is to perform. For example, it might be a digital-to-real-world data transformation task. Data flow information can include parameters similar to those described in Action 307a. For D2RAF 111, the upstream NF is DPGW 112, and the downstream NF is AN 127. The upstream NF information can include DPGW 112 information, such as the address of DPGW 112 (IP address and port number). The downstream NF information can include the address information of AN 127 (e.g., IP address and port number). Data flow information can include the destination address to which the DL datagram is sent after processing. The destination address can be the address of ED 121 (e.g., IP address and port number). After processing the received DL datagram, D2RAF 111 can forward the processed DL datagram to the destination address via AN 127.

[0087] In action 310b, D2RAF 111 can allocate its resources to process data packets sent from the upstream NF. D2RAF 111 can send a D2RAF data plane establishment response message to SMF 102. This message may include one or more of the following: the NF ID of D2RAF 111, the NF ID of SMF 102, the DP session ID, the DW application session ID, and upstream tunnel information. The upstream tunnel information may include the address of D2RAF 111 (e.g., IP address, port number, and TEID) for DPGW 112 to use in sending data packets to D2RAF 111.

[0088] In action 311a, SMF 102 may send a DWAS data plane establishment request message to DWAS 123 to establish a data plan between DPGW 112 and DWAS 123. This message may include one or more of the following: the NF ID of SMF 102, the ID of DWAS 123, the DP session ID, the address of DPGW 112 (e.g., IP address and port number), a packet filter for INDP of the data stream, and a packet filter for other data streams. SMF 102 may send the DWAS data plane establishment request message via the control plane (e.g., via CPGW 108) or via the data plane (e.g., via DPGW 112).

[0089] In action 311b, DWAS 123 may send a DWAS data plane establishment response message to SMF 102 to acknowledge receipt of the DWAS data plane establishment request message sent in action 311a. This message may include one or more of the following: the NF ID of DWAS 123, the NF ID of SMF 102, and the DP session ID received in action 311a.

[0090] In action 312, SMF 102 may send a DW application session establishment response message to CMF 101. This message may include one or more of the following: the NF ID of SMF 102, the NF ID of CMF 101, the ID of AN 127, the ID of ED 101, the ED message container to be transmitted to ED 121, the AN message container to be transmitted to AN 127, and the CMF message container to be transmitted to CMF 101.

[0091] The CMF message container may include one or more of the following: an indication to accept a DW application session establishment request, an indication to reject a DW application session establishment request, a DW session ID, a DW application ID, and a DW application session ID. The DW session ID is created by SMF 102 and is used to identify the DW application session requested by ED 121.

[0092] The AN message container may include one or more of the following: DW application session ID, DW session ID, SMF NF ID (SMFID), DW application ID, and data flow information. The data flow information may include one or more of the following: data flow ID, UL direction indication (where, for example, ED 121 sends a data packet to AN 127), DL direction indication (where, for example, AN 127 sends a data packet to ED 121), upstream NF information, downstream NF information, QoS parameters, UL SFC information (for example, UL SFC ID, ID of the first NF in the ULSFC, IP address and port number of the first NF in the UL SFC), DL SFC information (for example, DL SFC ID, ID of the last NF in the DLSFC, IP address and port number of the last NF in the DL SFC), and UL SFC header. The upstream NF information may be the NF and tunnel information already received by SMF 102 in actions 307b and 309b, for AN 127 to use in sending data packets to DPGW112 and LDPF 109, respectively. Downstream NF information can be one or more of NF ID and tunnel information (e.g., the IP address, port number, and TEID of DPGW 112 and D2RAF 111 that SMF 102 has received in Actions 307b and 310b, respectively).

[0093] The ED message container may include one or more of the following: an indication of accepting a DW application session establishment request, an indication of rejecting a DW application session establishment request, a reason for rejecting a DW application session establishment request, a DW application session ID, a DW session ID, a DW application ID, and data flow information. The data flow information may include one or more of the following: a data flow ID, an indication of a UL data flow, an indication of a DL data flow, an INDP indication of a UL data flow, an INDP indication of a DL data flow, a message filter set, the UL SFC ID and address of the UL data flow, and the DL SFC ID and address of the DL data flow.

[0094] In action 313, after receiving the DW application session establishment response message from SMF 102, CMF 101 may store the information in the CMF message container and forward the DW application session establishment response message having one or more of the following to AN 127: the NF ID of CMF 101, the NF ID of SMF 102, the ID of ED 121, the ID of AN 127, the AN message container, and the ED message container.

[0095] In action 314, AN 127 may receive a DW application session establishment response message with an AN message container and an ED message container sent by CMF 101. AN 127 may store information in the AN message container. If the ED application session establishment request is accepted, AN 127 may allocate or commit some or all of its resources to support the DW application session requested by ED 121. Therefore, upon receiving an indication that the request to establish a DW application session has been accepted, AN 127 may support at least one DL tunnel, or at least one UL tunnel, or both. For example, in some embodiments, AN 127 may support one or more DL tunnels upon receiving an indication that the request to establish a DW application session has been accepted. In other embodiments, AN 127 may support one or more UL tunnels upon receiving the indication. In some other embodiments, AN 127 may support one or more DL tunnels and one or more UL tunnels upon receiving an indication that the request to establish a DW application session has been accepted. AN 127 may forward the DW application session establishment response message with the ED message container to ED 121. After receiving the DW application session establishment response message, ED 121 can send an agreement to process the DW application session data in CN 128 (or refuse to process the DW application session data in CN 128) to DWAS 123 or DWSF 107.

[0096] In Action 315, AN 127 may send AN data plane information messages directly or via CMF 101 to SMF 102. For each data flow, the message may include one or more of the following: data flow ID, UL tunnel information, and (for DL ​​data flows) DL tunnel information (e.g., IP address, port number, TEID, source NF information of the NF that sent the DL datagram to AN 127). The source NF information may include the network function ID of CN 128 (e.g., DPGW 112 and D2RAF 111 sending datagrams to AN 127) and the DL SFC ID. SMF 102 may use the SFC NF information to identify any combination of the corresponding NF, DL SFC, data flow, or entities communicating with AN 127 in the DL.

[0097] In action 316, after receiving the AN data plane information, CMF 101 can forward the AN data plane information message to SMF 102.

[0098] In action 317a, SMF 102 can receive AN data plane information messages from AN 127. SMF 102 can send a D2RAF data plane modification request message to D2RAF 111. This message may include one or more of the following: DP session ID, DW application session ID, data stream ID, and AN DL tunnel information. D2RAF 111 can use the AN DL tunnel information to direct data packets of the data stream to AN 127.

[0099] In action 317b, D2RAF 111 can send a D2RAF data plane modification response message to SMF 102 to acknowledge receipt of the D2RAF data plane modification request.

[0100] In action 318a, SMF 102 can receive AN data plane information messages from AN 127. SMF 102 can send DPGW data plane modification request messages to DPGW 112. This message may include one or more of the following: DP session ID, DW application session ID, data stream ID, and AN DL tunnel information. DPGW 112 can use the AN DL tunnel information to direct data packets of the data stream to AN 127.

[0101] In action 318b, DPGW 112 can send a DPGW data plane modification response message to SMF 102 to acknowledge receipt of the DPGW data plane modification request.

[0102] In some implementations, SMF 102 can generate a unique DP session ID to identify communication with DPGW 112 (in action 307a), R2DAF 110 (in action 308a), LDPF 109 (in action 309a), D2RAF 111 (in action 310a), and DWAS 123 (in action 311a). In some other embodiments, SMF 102 can generate the same DP session ID for all communication with NF and DWAS 123 in actions 307a, 308a, 309a, 310a, and 311a. In this implementation, SMF 102 can use the DP session ID and the NF ID of the NF that sent the data plane establishment response message (in actions 307b, 308b, 309b, 310b, and 311b) to identify communication with other NFs.

[0103] In some implementations, SMF 102 may not generate a DP session ID; therefore, the DP session ID can be omitted from the data plane establishment request messages sent by SMF 102 in actions 307a, 308a, 309a, 310a, and 311a. Each NF (DPGW 112, R2DAF 110, LDPF 109, D2RAF 111) or DWAS 123 may generate a DP session ID in actions 307b, 308b, 309b, 310b, and 311b and send it to SMF 102 in the data plane establishment response message.

[0104] In some implementations, SMF 102 can generate a DW session ID. The DW session ID can be used to identify the data session requested by ED 121 in action 304. The DW session ID can be based at least in part on the DW application session ID and the current state of MN 131 (processing resource availability). SMF 102 can send the DW session ID to other NFs (to DPGW 112 in action 307a, to R2DAF 110 in action 308a, to LDPF 109 in action 309a, to D2RAF 111 in action 310a, to DWAS 123 in action 311a, and to ED 121 and AN 127 in action 312). Other network entities can send the DW session ID to SMF 102 in actions 307b, 308b, 309b, 310b, 311b, and 315.

[0105] Figure 4A and Figure 4B This illustrates how, after establishing a DW application session between ED 121 and DWAS 123, for example via... Figure 3A and Figure 3BThe process involves data transmission between these devices.

[0106] In action 401, after receiving an indication to accept the DW application session establishment request (e.g., in the DW application session establishment response message of action 314), ED 121 may begin sending UL data packets. UL data can be of two types: (1) UL data that is not (or will not) be processed in the mobile network, and (2) UL data that is (or will) be processed in the mobile network. Each type of UL data can be assigned to one or more data streams based on QoS requirements. ED 121 can use data stream information provided by SMF 102, such as UL packet filters, UL destination addresses (e.g., the address of the first NF in the UL SFC), QoS parameters, and INDP indications, to assign UL data packets to the appropriate UL data stream, marked by the data stream ID in the packet header. To send a data packet to DWAS 123, ED 121 may add the DWAS 123 address as the destination address of the UL data packet in the packet header. For UL data packets to be processed in a mobile network, ED 121 can add the SFC address (e.g., the address of LDPF 109) as the destination address to the packet header.

[0107] In action 402, AN 127 can receive UL data messages from a data stream. AN 127 can classify UL data messages based on header information such as data stream ID, destination address, or any combination thereof.

[0108] In Action 403a, for UL data flows that are to be forwarded to DPGW 112 but not processed in the mobile network, AN127 can send the data packet to DPGW 112 through the allocated UL tunnel. The header of these data packets may include the data flow ID and tunnel information (e.g., the IP address, port number, and UL TEID of DPGW 112).

[0109] In action 403b, DPGW 112 can receive UL data packets. DPGW 112 can remove some header information added by AN 127 in action 403a. For example, DPGW 112 can remove the UL data stream ID and UL tunnel information and forward the UL data packets to DWAS 123.

[0110] In Action 404, for data flows to be processed in the mobile network, AN 127 can update the header information of the corresponding UL data packets. For example, before sending a UL data packet to LDPF 109, AN 127 can update the UL data flow ID and tunnel information (e.g., the address, port number, and TEID of LDPF 109). AN 127 can also update the SFC header information (e.g., SFCID, source NF ID, destination NF ID, and message processing instructions).

[0111] In action 405, LDPF 109 can acquire one or more UL data packets from one or more data streams and process the information in these UL data packets. For example, LDPF 109 can estimate the position of an object based on the sensing data provided by ED 121 and detect the movement of the object, such as the movement of a person.

[0112] In action 406, after UL data processing, LDPF 109 can repackage the processed information into one or more UL data packets, adding header information such as the data stream ID, the address of the next NF in the SFC as the destination address, and the tunnel information of the next data processing function in the associated SFC (e.g., R2DAF 110). LDPF 109 can then send the processed UL data packets to R2DAF 110.

[0113] In action 407, R2DAF 110 can receive one or more UL data packets from LDPF 109. R2DAF 110 can further process the data, for example, by converting real-world data acquired by the sensors of ED 121 into a digital data format that can be used by DWAS 123. R2DAF 110 can also perform 3D scene rendering.

[0114] In action 408a, after processing the data, R2DAF 110 can repackage the processed data, add a UL header, and send the processed UL data packet directly or via DPGW 112 to DWAS 123. The UL header may include the source address (the address of the last NF in the SFC (R2DAF 110 in this embodiment), the destination address (e.g., the address of DWAS 123 or DPGW 112), and a tunnel header. The tunnel header may include the DPGW 112 address and TEID.

[0115] In action 408b, DPGW 112 can receive UL data packets from R2DAF 110. DPGW 112 can remove some header fields, such as tunnel header information and SFC header, and forward the data packets to DWAS 123. If the UL packet header fields match entries in the UL NAT table, DPGW 112 can perform network address translation (NAT) on the corresponding UL data packet. For example, DPGW 112 can replace the destination address of the UL data packet (which could be the address of DPGW 112 in this embodiment) with the address of DWAS 123. In another example, DPGW 112 can replace the source address of the UL data packet (which could be the address of R2DAF 110 in this embodiment) with the UL SFC flow source address.

[0116] In action 409, DWAS 123 can send DL data packets to ED 121 via DPGW 112.

[0117] In action 410, DPGW 112 can classify received DL data packets into DL data streams using the header information of the received packets. DL data packets are assigned to one or more DL data streams. DPGW 112 can add header fields such as a data stream ID, a tunnel header field, and an SFC header (e.g., SFC ID, source NF ID, destination NF ID, and packet processing instructions). If the DL packet header fields match entries in the DL NAT table, DPGW 112 can perform network address translation (NAT) on the corresponding DL data packet. For example, DPGW 112 can replace the destination address of the DL data packet with the address of D2RAF 111, which could be the address of DPGW 112 or ED 121 as in this embodiment. In another example, DPGW 112 can replace the source address of the DL data packet (which could be the address of DWAS123 in this embodiment) with the DL SFC stream source address. Similar to Action 402, this classification can categorize messages into those that will undergo in-network data processing and those that will not.

[0118] In action 411a, some data streams that may not require data processing within the network can be sent directly to AN 127.

[0119] In action 411b, AN 127 can receive DL data packets and can remove some header fields of the received DL data packets, such as the tunnel header field. AN 127 can send DL data packets to ED 121.

[0120] As described above, some data streams can be designated for data processing within the network. In action 412, DPGW 112 can send DL data packets of these data streams to D2RAF 111.

[0121] In action 413, D2RAF 111 can process DL data packets. For example, D2RAF 111 can convert the format of data sent from DWAS 123 into another format that can be read by the actuator in ED 121. In another example, D2RAF 111 can render a 3D scene or audio that will be consumed by ED 121. Although not shown, other NFs in the DL SFC can be used for further processing of DL data packets.

[0122] In action 414a, D2RAF 111 can package the processed DL data, adding a message header and a tunnel header. D2RAF 111 can then send the DL data message to AN 127.

[0123] The message header may include a source address and a destination address. The source address may be the address of the last NF in the DL SFC (e.g., the address of D2RAF 111) or the address of DWAS 123 (e.g., the separate IP address of the port number of DWAS 123). The destination address may be the address of AN 127 or the address of ED 121.

[0124] In action 414b, AN 127 can receive DL data packets from D2RAF 111. After receiving the DL data packets, AN 127 can remove some header fields of the received DL data packets, such as the tunnel header field. AN 127 can replace the destination address in the packet header (which in this embodiment could be the address of AN 127) with the address of ED 121. AN 127 can then forward the DL data packets to ED 121.

[0125] Figure 5This is a schematic diagram of an electronic device 500 provided in different embodiments of the present invention, which can perform any or all of the operations of the methods and features described herein, explicitly or implicitly. For example, a computer equipped with network capabilities can be configured as electronic device 500. Such electronic device can be used as part of one or more of the following: controller, edge server, processing device, boundary area module, AV, roadside unit (RSU), etc. Multiple such devices, when networked, can be used to perform the operations described herein. Networked computing devices can host various functions as described herein, and network function virtualization or similar technologies can be used to facilitate such hosting. Other network infrastructure devices, such as base stations, eNBs, gNBs, distributed base stations, eNBs or gNBs, access point components, etc., can also be used. More generally, devices employing networking and computing capabilities can be used to run one or more of the functions described herein (e.g., DWSF, D2RAF, R2DAF, etc.). Sensors and actuators can be operated by such devices.

[0126] As shown in the figure, the device includes a processor 501 (e.g., a dedicated processor such as a central processing unit (CPU), graphics processing unit (GPU), or other such processing units), a memory 504, a non-transient mass storage 502, an I / O interface 505, a network interface 503, and a transceiver 506, all of which are communicatively coupled via a bidirectional bus 507. According to some embodiments, any or all of the elements shown may be used, or only a subset of these elements. Furthermore, the electronic device 500 may include multiple instances of some elements, such as multiple processors, multiple memories, or multiple transceivers. Additionally, elements of the hardware device may be directly coupled to other elements without requiring a bidirectional bus. Alternatively or additionally, in addition to processors and memory, other processing electronics (e.g., application-specific integrated circuits, field-programmable gate arrays, digital circuits, analog circuits, etc., or combinations thereof) may be used to perform the required logic operations. Each integrated circuit may include one or more semiconductor chips and semiconductor chipsets.

[0127] Memory 504 may include any type of non-transitory memory, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous DRAM (SDRAM), read-only memory (ROM), or combinations thereof. Mass storage element 502 may include any type of non-transitory storage device, such as a solid-state drive, hard disk drive, disk drive, optical disk drive, USB drive, or any computer program product configured to store data and machine-executable program code. According to some embodiments, memory 504 or mass storage 502 may record statements and instructions executable by processor 501 thereon for performing any of the above-described method operations.

[0128] It should be understood that although specific embodiments of the technology have been described herein for illustrative purposes, various modifications may be made without departing from the scope of the technology. Therefore, the specification and drawings are to be considered merely as an illustration of the invention as defined by the appended claims, and are intended to cover any and all modifications, variations, combinations, or equivalents falling within the scope of the invention. Specifically, within the scope of this technology, a computer program product or program element, or a program memory or memory device (e.g., magnetic or optical wires, magnetic tape, or disk, etc.) is provided for storing machine-readable signals, controlling the operation of a computer according to the method of this technology, or constructing some or all of its components according to the system of this technology.

[0129] The actions associated with the method described herein can be implemented as coded instructions in a computer program product. In other words, a computer program product is a computer-readable medium on which software code is recorded, which executes the method when the computer program product is loaded into memory and executed on the microprocessor of a wireless communication device.

[0130] Furthermore, each operation of this method can be performed on any computing device such as a personal computer, server, or PDA, based on one or more program units, modules, or objects, or a portion thereof, generated from any programming language such as C++ or Java. Additionally, each operation, or the file or object implementing each operation, can be performed by dedicated hardware or a circuit module designed for this purpose.

[0131] Based on the description of the above embodiments, the present invention can be implemented using only hardware, or using software and necessary general-purpose hardware platforms. Based on this understanding, the technical solution of the present invention can be embodied in the form of a software product. The software product can be stored in a non-volatile or non-transitory storage medium, such as a compact disk read-only memory (CD-ROM), a USB flash drive, or a removable hard drive. The software product includes a number of instructions that enable a computer device (personal computer, server, or network device) to perform the methods provided in the embodiments of the present invention. For example, such performance may correspond to the simulation of the logical operations described herein. The software product may additionally or alternatively include multiple instructions that enable a computer device to perform operations for configuring or programming a digital logic device according to embodiments of the present invention.

[0132] Although the invention has been described with reference to specific features and embodiments thereof, it will be apparent that various modifications and combinations thereof can be made without departing from the invention. Therefore, the specification and drawings are to be regarded merely as illustrative of the invention as defined by the appended claims and are intended to cover any and all modifications, variations, combinations, or equivalents falling within the scope of the invention.

Claims

1. A Session Management Function (SMF) device, characterized in that, The SMF device, used to support DW application sessions between electronic devices (ED) and the Digital World Application Server (DWAS), includes processing electronics integrated into the infrastructure of the core network (CN) portion of the mobile network (MN), and is used for: Receive DW application session establishment request information; The request information is established at least in part based on the DW application session, and one or more NFs are selected from multiple network function NFs integrated into the CN infrastructure; Request and receive DW application session information. The DW application session information includes indications of one or more uplink UL service function chain (SFC) indicators, or indications of one or more downlink DL SFC indicators, or both. The DW application session information includes one or more of the following: NF information indicating each NF in the one or more UL SFCs; NF information indicating each NF in the one or more downlink DL SFCs; Wherein, the one or more NFs include each NF in the one or more UL SFCs, or each NF in the one or more DL SFCs, or both. The ED, DWAS, and MN are connected in communication, and the DWAS is used to provide a DW application for executing the DW application session between the ED and the DWAS. The DW application session uses data packets from the CN for processing.

2. The SMF device according to claim 1, characterized in that, Also used for: Based at least in part on the DW application session establishment request information and the DW application session information, configure or initiate the configuration of at least one UL tunnel between the one or more UL SFCs and the ED and DWAS; The at least one UL tunnel is located at least partially within the CN.

3. The SMF device according to claim 1 or 2, characterized in that, Also used for: Based at least in part on the DW application session establishment request information and the DW application session information, configure or initiate the configuration of one or more DL SFCs and at least one DL tunnel between the DWAS and the ED; The at least one DL tunnel is located at least partially within the CN.

4. The SMF device according to claim 1, characterized in that, At least a portion of the DW application session establishment request information is provided by the DWAS or by the DW support function DWSF used to support the DW application session; One or more UL data packets of DW application session data are sent through the at least one UL tunnel and processed in the CN before being transmitted to the DWAS. The one or more DL data packets of the DW application session data are sent through the at least one DL tunnel and processed in the CN before being transmitted to the ED.

5. The SMF device according to claim 1 or 4, characterized in that, The DW application session establishment request information includes one or more of the following: DW Application Identifier (ID) DW application session ID, ED ID, ED location information The ID of one or more UL SFCs, The SFC header of one or more UL SFCs The ID of the one or more DL SFCs The SFC header of the one or more DL SFCs.

6. The SMF device according to claim 5, characterized in that, The SFC header of the one or more UL SFCs includes one or more of the following: the address of the one or more UL SFCs and UL message processing instructions. The SFC header of the one or more DL SFCs includes one or more of the following: the address of the one or more DL SFCs and DL message processing instructions.

7. The SMF device according to claim 2, characterized in that, The configuration or initiation of configuration of the one or more UL SFCs and the at least one UL tunnel includes: Configure the access network AN portion of the MN such that the AN adds the SFC header of the one or more UL SFCs to one or more UL data packets and forwards the one or more UL data packets to at least one NF in the one or more UL SFCs; Configure at least one NF in the one or more UL SFCs to process the one or more UL data packets according to the DW application ID and data processing ID of the at least one NF in the one or more UL SFCs, and send one or more processed UL data packets to the next NF in the one or more UL SFCs; Configure the last NF in the one or more UL SFCs to send the one or more processed UL data packets to the DWAS; Send to the ED an indication that at least one NF in one or more UL SFCs is used to process at least a portion of the DW application session data.

8. The SMF device according to claim 3, characterized in that, The configuration or initiation of configuration of the one or more DL SFCs and the at least one DL tunnel includes: Configure the DWAS or Data Plane Gateway (DPGW) to add the SFC header of the one or more DL SFCs to one or more DL data packets and forward the one or more DL data packets to at least one NF in the one or more DL SFCs. Configure at least one NF in the one or more DL SFCs to process the one or more DL data packets according to the DW application ID and data processing ID of the at least one NF in the one or more DL SFCs, and send one or more processed DL data packets to the next NF in the one or more DL SFCs; Configure the last NF in the one or more DL SFCs to send the one or more processed DL data packets to the ED address; Send to the ED an indication that at least one NF in one or more DL SFCs is used to process at least a portion of the DW application session data.

9. The SMF device according to claim 8, characterized in that, The DPGW provides a data transmission interface between the MN and the DWAS.

10. An electronic device ED, characterized in that, The ED is used to support DW application sessions between the ED and the Digital World Application Server (DWAS), and the ED includes processing electronics for: Receive one or more of the following: an indication that the DW application can be used in the DW application session and DW application session configuration information, wherein the DW application session uses data packet processing in the core network CN part of the mobile network MN; Request one or more uplink UL tunnels between the ED and the DWAS, or one or more downlink DL tunnels between the DWAS and the ED, or both; Receive an indication from at least one network function (NF) of the CN for processing at least a portion of the DW application session data; The ED, DWAS, and MN are connected in a communication manner. The DWAS is used to provide the DW application for executing the DW application session between the ED and the DWAS. The DW application session configuration information is used by the ED when configuring the DW application session. The one or more UL tunnels and the one or more DL tunnels are at least partially located in the CN.

11. The ED according to claim 10, characterized in that, It is also used to send consent to or refusal to process the DW application session data in the CN.

12. The ED according to claim 11, characterized in that, Also used for: After the consent is sent to process the DW application session data in the CN, One or more UL data packets of the DW application session data are sent through the one or more UL tunnels, and the one or more UL data packets are processed in the CN before being transmitted to the DWAS. One or more DL data packets of the DW application session data are received through the one or more DL tunnels, and the one or more UL data packets are processed in the CN before being transmitted to the ED, or both of the above steps are performed.

13. The ED according to claim 10, characterized in that, The DW application session configuration information and the indication that the DW application can be used in the DW application session are provided by the DWAS or by the DW support function DWSF for supporting the DW application session.

14. The ED according to claim 10 or 13, characterized in that, The DW application session configuration information includes one or more of the following: DW Application Identifier (ID) DW application session ID, At least one UL service function chain (SFC) ID, The SFC head of at least one UL SFC At least one DL SFC ID, The SFC header of at least one DL SFC.

15. The ED according to claim 14, characterized in that, The SFC header of the at least one UL SFC includes one or more of the following: the address of the at least one UL SFC and UL message processing instructions; The SFC header of the at least one DL SFC includes one or more of the following: the address of the at least one DL SFC and DL message processing instructions.

16. The ED according to claim 14, characterized in that, Also used for: Receive an ED message container, wherein the ED message container includes one or more of the following: Message filter set, Indication that the DW application session establishment request has been accepted. The indication that the DW application session establishment request was rejected. IDs of the endpoints of the one or more UL tunnels, The IDs of the endpoints of the one or more DL tunnels, The address of at least one UL SFC The address of at least one DL SFC.

17. An access network (AN) device, characterized in that, The AN device, used to support DW application sessions between electronic devices (ED) and the Digital World Application Server (DWAS), includes processing electronics and is used for: An indication is received that a request to establish a DW application session has been accepted, the DW application session utilizing data packet processing in the core network CN portion of the mobile network MN; Upon receiving the instruction, support one or more of the following: at least one downlink DL tunnel and at least one uplink UL tunnel; Specifically, supporting the at least one UL tunnel includes adding a Service Function Chain (SFC) header of at least one UL SFC to one or more UL data packets and forwarding the one or more UL data packets to at least one Network Function (NF) of the at least one UL SFC. The ED, DWAS, CN, and AN device are communicatively connected. The AN device is part of the AN portion of the MN. The DWAS is used to provide a DW application for executing the DW application session between the ED and the DWAS.

18. The AN device according to claim 17, characterized in that, It is also used to receive one or more of the following: DW application session establishment request information and AN message container. The DW application session establishment request information includes one or more of the following: DW Application Identifier (ID) DW application session ID, ED ID, ED location information The ID of at least one UL SFC The SFC head of the at least one UL SFC; At least one DL SFC ID, The SFC header of at least one DL SFC.

19. The AN device according to claim 18, characterized in that, The SFC header of the at least one UL SFC includes one or more of the following: the ID of the at least one UL SFC, the ID of the source NF of the at least one UL SFC, the ID of the destination NF of the at least one UL SFC, and UL message processing instructions; The SFC header of the at least one DL SFC includes one or more of the following: the ID of the at least one DL SFC, the ID of the source NF of the at least one DL SFC, the ID of the destination NF of the at least one DL SFC, and DL message processing instructions.

20. A system, characterized in that, The system is used to support DW application sessions between electronic devices (ED) and digital world application servers (DWAS). The system includes the ED, an access network (AN) device, a session management function (SMF) device, and the DWAS. The AN device is integrated into the infrastructure of the AN portion of the mobile network MN, and the SMF device is integrated into the infrastructure of the core network CN portion of the MN; the ED and the DWAS are communicatively connected to the MN, and therefore communicatively connected to the AN device, the SMF device, and the ED and DWAS, wherein: The DWAS includes processing electronics and is used for: Provides a DW application for performing the DW application session between the ED and the DWAS. Send one or more of the following to the ED: an indication that the DW application can be used in the DW application session and DW application session configuration information. The DW application session configuration information is used by the ED when configuring the DW application session, and the DW application session uses data packets from the CN for processing. The ED includes processing electronics and is used for: Receive one or more of the following: the indication that the DW application can be used in the DW application session and the DW application session configuration information; Request one or more uplink UL tunnels between the ED and the DWAS, or one or more downlink DL tunnels between the DWAS and the ED, or both; Receive an indication from at least one network function (NF) of the CN for processing at least a portion of the DW application session data; Wherein, the one or more UL tunnels and the one or more DL tunnels are at least partially located in the CN. The SMF device includes processing electronics and is used for: Receive DW application session establishment request information; The request information is established at least in part based on the DW application session, and one or more NFs are selected from multiple network function NFs integrated into the CN infrastructure; Request and receive DW application session information. The DW application session information includes indications of one or more UL Service Function Chain (SFC) indicators, or indications of one or more DLSFC indicators, or both. The DW application session information includes one or more of the following: NF information indicating each NF in the one or more UL SFCs and NF information indicating each NF in the one or more DL SFCs. Wherein, the one or more NFs include each NF in the one or more UL SFCs, or each NF in the one or more DL SFCs, or both. The AN device includes processing electronics and is used for: Receive an indication that the DW application session establishment request has been accepted; Upon receiving the instruction, one or more of the following are supported: the one or more DL tunnels and the one or more UL tunnels; The support for the one or more UL tunnels includes adding the SFC header of the one or more UL SFCs to one or more UL data packets and forwarding the one or more UL data packets to at least one NF in the one or more UL SFCs.

21. A method, characterized in that, The method for supporting DW application sessions between electronic devices (ED) and the Digital World Application Server (DWAS) includes: Session Management Function (SMF) is integrated into the infrastructure of the core network (CN) portion of the mobile network (MN): Receive DW application session establishment request information; The request information is established at least in part based on the DW application session, and one or more NFs are selected from a plurality of network function NFs integrated into the infrastructure of the CN; Requesting and receiving DW application session information, The DW application session information includes indications of one or more uplink UL service function chain (SFC) indicators, or indications of one or more downlink DL SFC indicators, or both. The DW application session information includes one or more of the following: NF information indicating each NF in the one or more UL SFCs; or NF information indicating each NF in the one or more DL SFCs. Wherein, the one or more NFs include each NF in the one or more UL SFCs, or each NF in the one or more DL SFCs, or both. The ED, DWAS, and MN are connected in communication. The DW application session uses data packets from the CN for processing. The DWAS is used to provide a DW application for executing the DW application session between the ED and the DW DWAS.

22. The method according to claim 21, characterized in that, Also includes: Based at least in part on the DW application session establishment request information and the DW application session information, configure or initiate the configuration of at least one UL tunnel between the one or more UL SFCs and the ED and DWAS; The at least one UL tunnel is located at least partially within the CN.

23. The method according to claim 21 or 22, characterized in that, Also includes: Based at least in part on the DW application session establishment request information and the DW application session information, configure or initiate the configuration of one or more DL SFCs and at least one DL tunnel between the DWAS and the ED; The at least one DL tunnel is located at least partially within the CN.

24. The method according to claim 21, characterized in that, At least a portion of the DW application session establishment request information is provided by the DWAS or by the DW support function DWSF used to support the DW application session.

25. The method according to claim 21, characterized in that, One or more UL data packets of DW application session data are sent through at least one UL tunnel and processed in the CN before being transmitted to the DWAS. The one or more DL data packets of the DW application session data are sent through at least one DL tunnel and processed in the CN before being transmitted to the ED.

26. A method, characterized in that, The method for supporting DW application sessions between electronic devices (ED) and the Digital World Application Server (DWAS) includes: The ED: Receive one or more of the following: an indication that the DW application can be used in the DW application session, or DW application session configuration information for the ED to configure the DW application session, wherein the DW application session uses data packet processing in the core network CN part of the mobile network MN; Request one or more uplink UL tunnels between the ED and the DWAS, or one or more downlink DL tunnels between the DWAS and the ED, or both; Receive an indication from at least one network function (NF) of the CN for processing at least a portion of the DW application session data; The ED, DWAS, and MN are connected in a communication manner. The DWAS is used to provide the DW application for executing the DW application session between the ED and the DWAS. The one or more UL tunnels and the one or more DL tunnels are at least partially located in the CN.

27. The method according to claim 26, characterized in that, Also includes: Send a message indicating agreement to process the DW application session data in the CN or refusal to process the DW application session data in the CN.

28. The method according to claim 27, characterized in that, Also includes: After the consent is sent to process the DW application session data in the CN, One or more UL data packets of the DW application session data are sent through the one or more UL tunnels, and the one or more UL data packets are processed in the CN before being transmitted to the DWAS. One or more DL data packets of the DW application session data are received through the one or more DL tunnels, and the one or more UL data packets are processed in the CN before being transmitted to the ED, or both of the above steps are performed.

29. A method, characterized in that, The method for supporting DW application sessions between electronic devices (ED) and the Digital World Application Server (DWAS) includes: Access Network (AN): An indication is received that a request to establish a DW application session has been accepted, the DW application session utilizing data packet processing in the core network CN portion of the mobile network MN; Upon receiving the instruction, support one or more of the following: at least one downlink DL tunnel and at least one uplink UL tunnel; Specifically, supporting the at least one UL tunnel includes adding a Service Function Chain (SFC) header of at least one UL SFC to one or more UL data packets and forwarding the one or more UL data packets to at least one Network Function (NF) of the at least one UL SFC. The ED, DWAS, CN, and AN are communicatively connected, the AN being a part of the AN portion of the MN, and the DWAS providing a DW application for executing the DW application session between the ED and the DWAS.