Method and apparatus for digital user architecture

Abstract

An architecture of a digital subscriber is provided. Digital users reside in a network and perform functions on behalf of physical users such as wireless communication devices. The digital user comprises a plurality of functions which are required for supporting various user centers and management (UCM) services, and a plurality of functions which are required for supporting various user centers and management (UCM) services. The invention relates to a method and a system for managing the content of a user, and the method and the system comprise the following functions: a privacy protection portal (PPP), an authentication and authorization function (AAF), a policy function (PLF), an intelligent decision function (IDF), a network feature management function (NFMF), a traffic management function (TFMF), a content interest management function (CIMF), and a data management function (d).

Description

Cross-references to related applications

[0001] This application claims priority to U.S. Provisional Patent Application No. 63 / 591,281, filed October 18, 2023, the entire contents of which are incorporated herein by reference. Technical Field

[0002] This invention relates to wireless communication. Specifically, it relates to methods and apparatus for providing a functional architecture for digital users of wireless communication. Background Technology

[0003] The design of 6G or future wireless networks should seek to adapt to a variety of emerging technologies and trends, such as new network infrastructure (e.g., cloud-native infrastructure), technologies such as artificial intelligence (AI) and blockchain, new applications and services (e.g., AI services and data-aware services), and more open and collaborative operating models.

[0004] Other requirements for future networks include enhanced privacy and trustworthiness, simplified standardization, rapid deployment, and support for Anything as a Service (XaaS).

[0005] Furthermore, the 6G system network architecture should support third-party developed 6G services by providing an open ecosystem and enabling improvements in trusted management. Summary of the Invention

[0006] The purpose of this invention is to provide a digital user architecture for wireless communication.

[0007] In a first aspect, a method implemented at a network element is provided, the method comprising: receiving a request for a user controlled and managed (UCM) service from a physical user (P-User), the request including a UCM service identifier; in response to the request, creating a digital user (D-User) for the P-User, wherein the D-User includes a plurality of functions selected to support the UCM service; and configuring the D-User such that the P-User uses a control plane of the plurality of functions to control features of the UCM service.

[0008] According to one embodiment of the first aspect, the control plane functionality is provided as a service.

[0009] According to another embodiment of the first aspect, the plurality of functions includes at least one of the following: control and management gateway (C / M GW), privacy protection portal (PPP), authentication and authorization function (AAF), policy function (PLF), intelligent decision function (IDF), network feature management function (NFMF), traffic management function (TFMF), content interest management function (CIMF), data management function (DMF), data storage function (DSF), D-User management function (DUMF), data gateway (Data-GW), and data processing function (DPF).

[0010] According to yet another embodiment of the first aspect, the creation of the D-User is performed by the D-Usercreation function (DUCF).

[0011] According to yet another embodiment of the first aspect, the P-User can communicate with the D-User through a control and management (C / M) gateway.

[0012] According to yet another embodiment of the first aspect, each of the plurality of functions can access each of the other plurality of functions.

[0013] According to yet another embodiment of the first aspect, the plurality of functions include the CIMF and the DMF, wherein the CIMF is used to: select a network entity for monitoring; instruct the network entity to monitor the content consumption of the P-User; receive a content interest list from the DMF; and notify the P-User of the content interest list.

[0014] According to yet another embodiment of the first aspect, the CIMF is also used to provide the content interest list to a shared database.

[0015] According to yet another embodiment of the first aspect, the plurality of functions further include the PPP, which is used to change the P-User identifier associated with the content interest list.

[0016] According to yet another embodiment of the first aspect, the CIMF is further configured to receive content from the shared database and notify the P-User of the received content.

[0017] According to yet another embodiment of the first aspect, the selected network entity includes at least one of the following: the P-User, the DPF, and the network DPF.

[0018] According to yet another embodiment of the first aspect, the UCM service identifier includes a data processing type.

[0019] According to yet another embodiment of the first aspect, the request includes a data processing specification, a data identifier, a session identifier, a P-User identifier, a data processing function (DPF) identifier, and a reporting target.

[0020] According to yet another embodiment of the first aspect, the method further includes: responding to the P-User with a response message, the response message including at least one of the following: a success or failure indication, a data processing report.

[0021] According to yet another embodiment of the first aspect, the method further includes: receiving an authentication challenge from the P-User, providing the authentication challenge to the AAF, receiving a response from the AAF, and providing the response to the P-User.

[0022] According to yet another embodiment of the first aspect, the method further includes: receiving a request from the P-User to establish a synchronization channel, establishing the synchronization channel with the P-User, and using the synchronization channel to transmit context data with the P-User.

[0023] According to yet another embodiment of the first aspect, the method further includes: synchronizing data with the P-User's data processing function (DPF).

[0024] According to a second aspect, a network element is provided, the network element including one or more processors for implementing the method according to any embodiment of the first aspect. In one embodiment, the network element includes one or more processors and a memory storing instructions that, when executed by the one or more processors, cause the network element to implement the method according to any embodiment of the first aspect.

[0025] According to a third aspect, a computer-readable medium is provided storing computer-readable instructions that, when executed by one or more processors, cause a device to perform the method according to any embodiment of the first aspect. Attached Figure Description

[0026] The invention will be better understood with reference to the accompanying drawings, in which: Figure 1 This is a graphical representation of the NET4DW architecture provided in at least one embodiment of the present invention.

[0027] Figure 2 This is a graphical representation of a digital user (D-User) provided in at least one embodiment of the present invention.

[0028] Figure 3 This is a graphical representation of a network environment provided in at least one embodiment of the present invention.

[0029] Figure 4 This is a graphical representation of a communication system provided in at least one embodiment of the present invention.

[0030] Figure 5 This is a graphical representation of an electronic device communicating with a base station, provided in at least one embodiment of the present invention.

[0031] Figure 6 This is a block diagram of a device provided in at least one embodiment of the present invention.

[0032] Figure 7 This is a block diagram of the structure of a 6G system provided in at least one embodiment of the present invention.

[0033] Figure 8 This is a block diagram of the functional architecture of a digital user provided in at least one embodiment of the present invention.

[0034] Figure 9A This is a flowchart illustrating a method for preparing a list of content interests provided by at least one embodiment of the present invention.

[0035] Figure 9B yes Figure 9A The following image is a continuation of the previous one.

[0036] Figure 10This is a block diagram of an exemplary device for implementing embodiments of the present invention. Detailed Implementation

[0037] The present invention relates to methods and apparatus for providing digital user architecture for wireless communication.

[0038] A user-centric network (UCN) aims to improve the user experience by enabling the network to dynamically adapt to user context and needs. As a non-limiting example, a UCN can manage its resources, topology, and policies based on the user's location, mobility, and QoS requirements.

[0039] However, future UCN networks are expected to be designed to enable users to have greater control over the services provided by the network, and even control some network characteristics. Such services can be called user-controlled and managed (UCM) services. Through these services, users can control or manage the services provided by the network. As a non-limiting example, UCM services can provide users with the ability to make traffic-related decisions, such as appending processing, routing, packet inspection, packet dropping, packet buffering, QoS enforcement, etc. Therefore, UCM services in UCN networks can support exposing network-related capabilities and data to users, enabling them to make such decisions.

[0040] Some UCM services that may be offered include: Users can define service capabilities, meaning they can define the services they need, rather than simply selecting the services provided by the network. Users can manage and control the behavior and characteristics of the services provided by the network; Each user can be served by a specific part of the network (e.g., a dedicated logical slice) and have some control over that specific part of the network; User context can be used to provide customized services and dynamic network functionality; User equipment (including smartphones, drones, etc.) can become part of the network, acting as base stations, repeaters, application servers, etc.

[0041] To provide UCN-supported UCM services, a virtual representative of the physical user (P-User), i.e., user equipment, is provided. In this invention, the terms P-User and user equipment (UE) are used interchangeably. The virtual representative may be referred to as a virtual UE (V-UE) or a digital user (D-User). The D-User provides the functionality and resources to assist in providing UCM services, including the ability to interact closely with the UCN that provides services to the physical user.

[0042] Based on the X-centric 6G architecture, digital world (DW) services can be provided through the network for digital world (NET4DW). NET4DW can provide DW services such as D-User services, digital twin services, and extended reality (XR) services.

[0043] Now for reference Figure 1 The diagram illustrates the architecture of NET4DW provided by at least one embodiment of the present invention. Specifically, as shown... Figure 1 As shown, the network may include service module 100. Service module 100 includes D-User platform 130a, D-Inf platform 130b, and XR service platform 130c. More generally, service module 100 may include any number of service platforms, and platforms 130a, 130b, and 130c are provided for illustrative purposes only.

[0044] The D-User platform 130a can manage D-Users. For example, the D-User platform 130a can create, delete, and update D-Users. Similarly, the D-Inf platform 130b can manage digital twin services, and the XR platform 130c can manage XR services. Digital twin services provide digital representations of physical entities.

[0045] Each of platforms 130a, 130b, and 130c can communicate with C / M function 120 via the control and management (C / M) plane, or with data processing (DP) function 140 via the data plane. C / M function 120 manages and coordinates platform interactions, while DP function 140 performs specific processing and operations, such as routing.

[0046] NET4DW also includes a C / M function 120 and a DP function 140. The C / M function 120 can communicate with the network through a C / M gateway 110, and the DP function 140 can communicate with the network through a data gateway 150.

[0047] According to at least some embodiments of the present invention, the UCM service is provided based on functions deployed within a managed network (e.g., but not limited to a 3GPP network) and functions deployed within the D-User. Functions deployed within the managed network may include, but are not limited to: a privacy preserving portal (PPP) for managing privacy and access; authentication and authorization functions; a blueprint preparation function responsible for identifying the functions and interfaces required by the D-User; and a D-User creation function for managing D-User creation and UCM service initialization.

[0048] Figure 2 An example set of D-User features is shown. For example... Figure 2 As shown, UE 201 includes application 202, control plane function (CPF) 203, and user plane function (UPF) 204. CPF 203 may include existing control plane functions as well as new control plane functions that support the D-User architecture.

[0049] D-User 255 includes CPF 211, UPF 212, memory 213, and management plane (MP) 214. D-User 255 is deployed by at least one network node. D-User 255 can be deployed in a hierarchical manner in different parts of the network (e.g., radio access network (RAN), core network (CN), and mobile edge computing (MEC) nodes) to support various UCM services of the UE. D-User 255 can represent UE 201 and perform certain actions on behalf of UE 201 to support applications and services participating throughout the network. Different types of D-Users can exist, providing different types of UCM services.

[0050] D-User 255 and UE 201 communicate with network 200 through various interfaces. The required interfaces may depend on the type of UCM services supported by D-User 255. A given interface may be used only by some UCM services. In addition to the interfaces defined in the 5G standard, D-User deployment and operation may require additional interfaces or additional messaging through existing interfaces.

[0051] Interface 240 can be used for control plane messaging between UE 201 and D-User 255, and the network may not be aware of these messages. Interface 240 can be used to synchronize UE data (e.g., UE context, location) between UE 201 and D-User 255 to provide authentication, authorization, and connection-related information between D-User 255 and UE 201, packet formats, and any new UCM protocol data unit (PDU) session initialization. A PDU data session can be defined as a communication session in which packets are exchanged between the UE and DN, the UE and D-User, the UE and the network, the D-User and DN, or the D-User and network entities. Depending on the UCM service, synchronization of large data streams may require a logical data plane connection between UE 201 and D-User 255.

[0052] Data plane connections can be established via interface 243 (which can be either the Uu interface or the B2 interface) in response to a request from D-User 255 or UE 201. For this purpose, UE 201 can send control plane messages to D-User 255 via interface 240. The network function (NF) of network 200 can be used to interact with UE 201 to obtain user context.

[0053] Interface 244 connects D-User 210 to RAN distributed unit / centralized unit 221. Interface 244 can be used for certain UCM services, for example, when D-User 255 requires specific radio access network (RAN) technologies or features. D-User 255 can use interface 244 to make such requests. Furthermore, interface 244 can be used for direct UE function authentication, similar to access and mobility-management function (AMF) functions. For some UCM applications, interface 244 can be used to direct UE traffic in and out of D-User 255, transparently to the managed network (core network or RAN). Interface 244 can be implemented as two interfaces, one for control plane traffic and one for user plane traffic.

[0054] Interface 249 connects D-User 255 to the core network control plane 222. Interface 249 can be used to establish connections, for authentication, authorization and accounting (AAA), for policy update processing, and for lifecycle management of network functions at D-User 255.

[0055] Interface 247a connects D-User 255 to the core network UPF 223 and can be used by certain types of UCM services to enable D-User CPF 211 to control CN UPF 223 for routing and data processing. Interface 247a can also be used to monitor information related to UE traffic (e.g., resource usage, quality of experience (QoE), different flows routed to different processing functions, UPF, or DN). NFs (or at least one NF in the network) can be used to acquire user traffic / data for internal processing. Interface 247b can be used at D-User 255 or when certain data must be terminated or started at D-User 255 for certain data processing. In this case, user traffic initiated by UE 201 or data network 230 is transferred to D-User 255 using interface 247b. NFs (or at least one NF in the network) can be used to acquire user traffic / data for internal processing.

[0056] Interface 248 connects D-User 255 to data network (DN) 230. Interface 248 can be used to send and receive data directly between D-User 255 and DN 230. Interface 248 is required only for certain UCM services.

[0057] Interface 241 connects the UE's CPF 203 to the access and mobility function (AMF) in the CN control plane 222. In addition to the functions defined in various 3GPP standards (e.g., 3GPP TS 23.501, V18.5.0, or other relevant standards), interface 241 can also be used to send D-User policies and parameters (including D-User service authorization) from the AMF to the UE 201, and to send D-User and UCM interaction capabilities to the AMF. Interface 241 can also be used to establish a synchronization channel and initial authentication process between D-User 255 and UE 201. Synchronization channel establishment and authentication can be performed by the AMF after a request from the session mobility function (SMF).

[0058] Interface 245 connects RAN 223 to CN control plane 222 (e.g., AMF). In addition to the relevant functions defined in various 3GPP standards (e.g., 3GPP TS 23.501, V18.5.0 or other relevant standards), interface 245 can also be used to support D-User and UCM services by sending D-User policies and parameters (including D-User service authorization) from AMF to RAN 223.

[0059] A further description of the set of UCM services and functions that can be used in conjunction with this application is further described in the commonly owned patent application PCT / CN2023 / 106032 entitled “Method, Apparatus and System for a User to Control Network Services by a Virtual User Equipment”, the entire contents of which are incorporated herein by reference.

[0060] The functionality within the managed network may be limited, and in some cases, may only accommodate basic D-User operations. Basic D-User operations can trigger or activate other UCM services as needed. However, other D-User functions can be used within the managed network to implement non-basic UCM services and ensure seamless operation of UCM services.

[0061] Therefore, as further described herein, embodiments of the present invention may include: The functionalities required for the proposed UCM service by the implementation within the Identifier Hosted Network and D-User; Provide details of the services provided by the identified functions, and identify service requirements, such as service inputs, service outputs, and service consumers; Provide an example message stream to illustrate the interaction of the identified functions in order to prepare a list of P-User content interests.

[0062] The embodiments described in this invention can be used in conjunction with or as part of an operating environment, which will now be described.

[0063] refer to Figure 3A simplified schematic diagram of a communication system is provided as an illustrative and non-limiting example. Communication system 100 includes a radio access network (RAN) 120. The RAN 120 can be a next-generation (e.g., 6th generation, 6G, or later) radio access network, or a traditional (e.g., 5th generation, 4th generation, 3rd generation, or 2nd generation, 2G) radio access network. In some implementations, 6G radio access refers to the next-generation standard air interface, which can include terrestrial networks (TN) and non-terrestrial networks (NTN). One or more electronic devices (EDs) 110a, 110b, 110c, 110d, 110e, 110f, 110g, 110h, 110i, 110j (generally referred to as 110) may interconnect with each other or be connected to one or more network nodes (170a, 170b, generally referred to as 170) in the wireless access network 120. The core network 130 may be part of the communication system and may depend on or be independent of the wireless access technology used in the communication system 100. Furthermore, the communication system 100 includes a public switched telephone network (PSTN) 140, the Internet 150, and other networks 160.

[0064] Typically, communication system 100 enables multiple wireless or wired components to transmit data and other content. Communication system 100 can provide voice, data, video, and / or text content through broadcasting, multicasting, unicasting, etc. Communication system 100 can provide a wide range of communication services and applications, including enhanced mobile broadband (eMBB) services, ultra-reliable low-latency communication (URLLC) services, massive machine-type communication (mMTC) services, integrated sensing and communication (ISAC), immersive communication, massive communication, high-reliability low-latency communication, ubiquitous connectivity, integrated AI and communication, and other services that future-generation communication systems can provide. Communication system 100 can provide other services and applications, such as earth monitoring, remote sensing, passive sensing and positioning, navigation and tracking, autonomous delivery and mobility, etc.

[0065] The communication system 100 can operate by sharing resources (such as carrier spectrum bandwidth) among its components.

[0066] Communication system 100 may include terrestrial communication systems and / or non-terrestrial communication systems. Communication system 100 can provide high availability and robustness through the joint operation of terrestrial and non-terrestrial communication systems. For example, integrating a non-terrestrial communication system (or components thereof) into a terrestrial communication system can enable a heterogeneous network comprising multiple layers. Heterogeneous networks can achieve better overall performance through efficient multi-link joint operation, more flexible function sharing, and faster physical layer link switching between terrestrial and non-terrestrial networks.

[0067] Terrestrial communication systems and non-terrestrial communication systems can be considered as subsystems of a communication system.

[0068] Electronic device 110 is used to connect people, objects, machines, etc. Electronic device 110 can be widely used in various scenarios, including cellular communication, device-to-device (D2D), vehicle-to-everything (V2X), peer-to-peer (P2P), machine-to-machine (M2M), MTC, Internet of Things (IoT), virtual reality (VR), augmented reality (AR), mixed reality (MR), metaverse, digital twins, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearable devices, intelligent transportation, smart cities, drones, robots, remote sensing, passive sensing, positioning, navigation and tracking, autonomous delivery and mobility, etc.

[0069] Each electronic device 110 represents any suitable end-user equipment for wireless operation and may include, for example (or may be referred to as, but is not limited to), user equipment (UE) or terminals, wireless transmit / receive units (WTRUs), mobile stations, fixed or mobile subscriber units, cellular phones, stations (STAs), MTC devices, personal digital assistants (PDAs), smartphones, laptops, computers, tablets, wireless sensors, consumer electronics, smart books, vehicles, automobiles, trucks, buses, trains, or IoT devices, wearable devices (e.g., watches, glasses, head-mounted devices, etc.), industrial equipment, or devices that include or incorporate the aforementioned equipment (e.g., communication modules, modems, or chips). Next-generation electronic devices 110 may be referred to using other terms.

[0070] Network node 170 can be a base station. A base station is a network element in a radio access network, responsible for wireless transmission and reception with user equipment in one or more cells. In some implementations, base stations 170a and 170b can use other names, such as base transceiver station (BTS), wireless base station, network node, network device, network-side device, transmit / receive node, Node B, evolved Node B (eNodeB or eNB), home eNodeB, next-generation Node B (gNB), transmission point (TP), site controller, access point (AP), wireless router, relay station, ground node, ground network device, ground base station, positioning node, etc. Base stations 170a and 170b can be macro base stations (BS), pico base stations, relay nodes, host nodes, etc., or combinations thereof.

[0071] Now for reference Figure 4 An exemplary communication system 100 is illustrated. Typically, the communication system 100 enables multiple wireless or wired components to transmit data and other content. The purpose of the communication system 100 may be to provide content, such as voice, data, video, and / or text, via broadcast, multicast, unicast, etc. The communication system 100 can operate by sharing resources (e.g., carrier spectrum bandwidth) among its constituent components. The communication system 100 may include terrestrial communication systems and / or non-terrestrial communication systems. The communication system 100 can provide a wide range of communication services and applications (e.g., earth monitoring, remote sensing, passive sensing and positioning, navigation and tracking, autonomous delivery and mobility, etc.). The communication system 100 can provide high availability and robustness through the joint operation of terrestrial and non-terrestrial communication systems. For example, integrating a non-terrestrial communication system (or components thereof) into a terrestrial communication system can enable a heterogeneous network comprising multiple layers. Compared to traditional communication networks, heterogeneous networks can achieve better overall performance through efficient multi-link joint operation, more flexible function sharing, and faster physical layer link switching between terrestrial and non-terrestrial networks.

[0072] Terrestrial communication systems and non-terrestrial communication systems can be considered subsystems of a communication system. Figure 4In the example shown, communication system 100 includes electronic devices (EDs) 110a, 110b, 110c, and 110d (generally referred to as ED 110), radio access networks (RANs) 120a and 120b, a non-terrestrial communication network 120c, a core network 130, a public switched telephone network (PSTN) 140, the Internet 150, and other networks 160. RANs 120a and 120b include corresponding base stations (BSs) 170a and 170b, which may generally be referred to as terrestrial transmit and receive points (T-TRPs) 170a and 170b. The non-terrestrial communication network 120c includes an access node 172, which may generally be referred to as a non-terrestrial transmit and receive point (NT-TRP) 172.

[0073] Any ED 110 can be used alternatively or additionally to connect, access, or communicate with any T-TRP 170a and 170b, NT-TRP 172, Internet 150, core network 130, PSTN 140, other network 160, or any combination thereof. In some examples, ED 110a can perform uplink and / or downlink transmission with T-TRP 170a via terrestrial air interface 190a. In some examples, ED 110a, 110b, 110c, and 110d can also communicate directly with each other via one or more sidelink air interfaces 190b. In some examples, ED 110d can perform uplink and / or downlink transmission with NT-TRP 172 via non-terrestrial air interface 190c.

[0074] Air interfaces 190a and 190b can use similar communication technologies, such as any suitable wireless access technology. For example, communication system 100 can implement one or more channel access methods in air interfaces 190a and 190b, such as code division multiple access (CDMA), space division multiple access (SDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), and single-carrier FDMA (SC-FDMA) (or discrete fourier transform spread OFDMA (DFT-s-OFDMA)). Air interfaces 190a and 190b can utilize other high-dimensional signal spaces, which may involve combinations of orthogonal and / or non-orthogonal dimensions.

[0075] The non-terrestrial air interface 190c enables communication between the ED 110d and one or more NT-TRP 172s via a wireless link or a simple link. For some examples, the link is a dedicated connection for unicast transmission, a connection for broadcast transmission, or a connection between a group of ED 110s and one or more NT-TRP 172s for multicast transmission.

[0076] RANs 120a and 120b communicate with core network 130 to provide various services, such as voice, data, and other services, to EDs 110a, 110b, and 110c. RANs 120a and 120b and / or core network 130 may communicate directly or indirectly with one or more other RANs (not shown), which may or may not be directly served by core network 130 and may or may not use the same radio access technology as RANs 120a, RAN 120b, or both. Core network 130 may also serve as a gateway access between (i) RANs 120a and 120b or EDs 110a, 110b, and 110c, or both, and (ii) other networks (e.g., PSTN 140, Internet 150, and other networks 160). Furthermore, some or all of EDs 110a, 110b, and 110c may include the ability to communicate with different wireless networks via different radio links using different radio technologies and / or protocols. Instead of wireless communication (or other than wireless communication), ED 110a, 110b, and 110c can also communicate with service providers or exchanges (not shown) via wired communication channels and with the Internet 150. PSTN 140 may include a circuit-switched telephone network for providing plain old telephone service (POTS). The Internet 150 may include a network of computers and / or subnets (internal networks) and incorporate protocols such as Internet Protocol (IP), Transmission Control Protocol (TCP), and User Datagram Protocol (UDP). ED 110a, 110b, and 110c may be multimode devices capable of operating under various wireless access technologies and include multiple transceivers required to support these wireless access technologies.

[0077] Figure 5Another example of the ED 110 and base stations 170a, 170b, and / or 170c is shown. The ED 110 is used to connect people, objects, and machines. The ED 110 can be widely used in various scenarios, including, for example, cellular communication, device-to-device (D2D), vehicle-to-everything (V2X), peer-to-peer (P2P), machine-to-machine (M2M), machine-type communication (MTC), Internet of Things (IoT), virtual reality (VR), augmented reality (AR), mixed reality (MR), metaverse, digital twins, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearable devices, smart transportation, smart cities, drones, robots, remote sensing, passive sensing, positioning, navigation and tracking, autonomous delivery and mobility, etc.

[0078] Each ED 110 represents any suitable end-user equipment used for wireless operation and may include, for example (or may be referred to as), user equipment (UE), wireless transmit / receive unit (WTRU), mobile station, fixed or mobile subscriber unit, cellular phone, station (STA), machine type communication (MTC) device, personal digital assistant (PDA), smartphone, laptop, computer, tablet, wireless sensor, consumer electronics device, smart book, vehicle, car, truck, bus, train, or IoT device, wearable device (e.g., watch, glasses, head-mounted device, etc.), industrial equipment, or devices in or including the above-mentioned equipment (e.g., communication module, modem, or chip). Next-generation ED 110 may be referred to using other terms. Base stations 170a and 170b are T-TRPs, hereinafter referred to as T-TRP 170. Also in Figure 5 As shown, NT-TRP is referred to below as NT-TRP 172. Each ED 110 connected to T-TRP 170 and / or NT-TRP 172 can be configured to be dynamically or semi-statically turned on (i.e., established, activated, or enabled), turned off (i.e., released, deactivated, or disabled), and / or in response to one or more of connection availability and connection necessity.

[0079] ED 110 includes a transmitter 201 and a receiver 203 coupled to one or more antennas 204. To avoid drawing clutter, only one antenna 204 is shown in the figure. One, some, or all of the antennas 204 may also be panels. The transmitter 201 and receiver 203 may be integrated as, for example, a transceiver. The transceiver is used to modulate data or other content for transmission through at least one antenna 204 or a network interface controller (NIC). The transceiver is also used to demodulate data or other content received by at least one antenna 204. Each transceiver includes any suitable structure for generating signals for wireless or wired transmission and / or for processing signals received wirelessly or wiredly. Each antenna 204 includes any suitable structure for transmitting and / or receiving wireless or wired signals.

[0080] ED 110 includes at least one memory 208. Memory 208 stores instructions and data used, generated, or collected by ED 110. For example, memory 208 may store software instructions or modules for implementing some or all of the functions and / or embodiments described herein, and executed by one or more processing units (e.g., processor 210). Each memory 208 includes any suitable one or more volatile and / or non-volatile storage and retrieval devices. Any suitable type of memory can be used, such as random access memory (RAM), read-only memory (ROM), hard disk, optical disk, subscriber identity module (SIM) card, memory stick, secure digital (SD) memory card, processor cache, etc.

[0081] ED 110 may also include one or more input / output devices (not shown) or interfaces (e.g., connected to...). Figure 4 (Wired interface of Internet 150 in the network). Input / output devices or interfaces can interact with users or other devices in the network. Each input / output device or interface includes any suitable structure for providing or receiving information from the user, and / or for network interface communication. Suitable structures include, for example, speakers, microphones, keypads, keyboards, displays, touchscreens, etc.

[0082] ED 110 includes a processor 210 for performing operations related to: preparing uplink transmissions to NT-TRP 172 and / or T-TRP 170, processing downlink transmissions received from NT-TRP 172 and / or T-TRP 170, and processing sidelink transmissions with another ED 110. Processing operations related to preparing uplink transmissions may include operations such as encoding, modulation, transmit beamforming, and generating symbols for transmission. Processing operations related to processing downlink transmissions may include operations such as receive beamforming, demodulation, and decoding of received symbols. According to an embodiment, the downlink transmissions may be received by receiver 203 possibly using receive beamforming, and processor 210 may extract signaling from the downlink transmissions (e.g., by detecting and / or decoding signaling). Examples of signaling may be reference signals transmitted by NT-TRP 172 and / or T-TRP 170. In some embodiments, processor 210 performs transmit beamforming and / or receive beamforming based on beam direction indications received from T-TRP 170, such as beam angle information (BAI). In some embodiments, processor 210 may perform network access-related operations (e.g., initial access) and / or downlink synchronization, such as operations related to detecting synchronization sequences, decoding, and acquiring system information. In some embodiments, processor 210 may perform channel estimation, for example, using reference signals received from NT-TRP 172 and / or from T-TRP 170.

[0083] Although not shown, processor 210 may form part of transmitter 201 and / or receiver 203. Although not shown, memory 208 may form part of processor 210.

[0084] The processor 210, the processing components of the transmitter 201, and the processing components of the receiver 203 may each be implemented by one or more processors, which are used to execute instructions stored in memory (e.g., in memory 208). Alternatively, some or all of the processor 210, the processing components of the transmitter 201, and the processing components of the receiver 203 may each be implemented using dedicated circuitry, such as a programmable field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), a graphics processing unit (GPU), or a hardware accelerator such as an artificial intelligence (AI) accelerator.

[0085] In some implementations, the T-TRP 170 can use other names, such as base station, basetransceiver station (BTS), wireless base station, network node, network device, network-side device, transmit / receive node, Node B, evolved Node B (eNodeB or eNB), home eNodeB, next-generation Node B (gNB), transmission point (TP), site controller, access point (AP), wireless router, relay station, ground node, ground network device, ground base station, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. The T-TRP 170 can be a macro base station, pico base station, relay node, host node, or a combination thereof. T-TRP 170 may refer to the aforementioned equipment or a device within the aforementioned equipment (e.g., a communication module, modem, or chip).

[0086] In some embodiments, the various parts of T-TRP 170 may be distributed. For example, some modules of T-TRP 170 may be located remotely from the device housing the antenna 256 of T-TRP 170 and may be coupled to the device housing the antenna 256 via a communication link (not shown) (sometimes referred to as a fronthaul, such as a Common Public Radio Interface (CPRI)). Therefore, in some embodiments, the term T-TRP 170 may also refer to modules on the network side that perform processing operations such as ED 110 location determination, resource allocation (scheduling), message generation, and encoding / decoding, which are not necessarily part of the device housing the antenna 256 of T-TRP 170. These modules may also be coupled to other T-TRPs. In some embodiments, T-TRP 170 may actually be multiple T-TRPs that operate together to serve ED 110, for example, by using cooperative multicast.

[0087] T-TRP 170 includes at least one transmitter 252 and at least one receiver 254 coupled to one or more antennas 256. To avoid drawing clutter, only one antenna 256 is shown in the figure. One, some, or all of the antennas 256 may also be panels. The transmitter 252 and receiver 254 may be integrated as a transceiver. T-TRP 170 also includes a processor 260 for performing operations including: preparing transmissions for downlink transmission to ED 110, processing uplink transmissions received from ED 110, preparing transmissions for backhaul transmission to NT-TRP 172, and processing transmissions received from NT-TRP 172 via backhaul. Processing operations related to preparing for downlink or backhaul transmissions may include operations such as encoding, modulation, precoding (e.g., multiple-input multiple-output (MIMO) precoding), transmit beamforming, and generating symbols for transmission. Processing operations related to uplink transmissions or transmissions received via backhaul transmissions may include operations such as receive beamforming, demodulation, and decoding of received symbols. Processor 260 may also perform network access-related operations (e.g., initial access and / or downlink synchronization), such as generating the contents of a synchronization signal block (SSB) and generating system information. In some embodiments, processor 260 also generates beam direction indications, such as a BAI, which can be scheduled for transmission by scheduler 253. Processor 260 performs other network-side processing operations described herein, such as determining the location of ED 110 and determining the deployment location of NT-TRP 172. In some embodiments, processor 260 may generate signaling, such as for configuring one or more parameters of ED 110 and / or one or more parameters of NT-TRP 172. Any signaling generated by processor 260 is transmitted by transmitter 252. It should be noted that the term "signaling" as used herein may also be referred to as control signaling. Signaling can be transmitted in physical layer control channels (e.g., physical downlink control channel (PDCCH)). In this case, the signaling can be called dynamic signaling. Signaling transmitted in the downlink physical layer control channel can be called downlink control information (DCI). Signaling transmitted in the uplink physical layer control channel can be called uplink control information (UCI). Signaling transmitted in the sidelink physical layer control channel can be called sidelink control information (SCI).Signaling can be included in higher-layer (e.g., above the physical layer) data packets transmitted in physical layer data channels (e.g., in the physical downlink shared channel, PDSCH). In this case, the signaling can be referred to as higher-layer signaling, static signaling, or semi-static signaling. Higher-layer signaling can also refer to radio resource control (RRC) protocol signaling or media access control-control element (MAC-CE) signaling.

[0088] Scheduler 253 may be coupled to processor 260. Scheduler 253 may be included within or operate separately from T-TRP 170. Scheduler 253 may schedule uplink, downlink, lateral link, and / or backhaul transmissions, including issuing scheduling authorizations and / or configuring scheduling-free (e.g., "configured authorization") resources. T-TRP 170 also includes memory 258 for storing information and data. Memory 258 stores instructions and data used, generated, or collected by T-TRP 170. For example, memory 258 may store software instructions or modules executed by one or more processors 260 for implementing some or all of the functions and / or embodiments described herein.

[0089] Although not shown, processor 260 may form part of transmitter 252 and / or receiver 254. Furthermore, although not shown, processor 260 may implement scheduler 253. Although not shown, memory 258 may form part of processor 260.

[0090] The processing components of processor 260, scheduler 253, transmitter 252, and receiver 254 may each be implemented by one or more processors, which may be the same or different, for executing instructions stored in memory (e.g., memory 258). Alternatively, some or all of the processing components of processor 260, scheduler 253, transmitter 252, and receiver 254 may be implemented using dedicated circuitry such as a programmable FPGA, hardware accelerator (e.g., GPU or AI accelerator), or ASIC.

[0091] Although the NT-TRP 172 is shown as an example of a drone only, it can be implemented in any suitable non-terrestrial form, such as satellites and high-altitude platforms, including international mobile communication base stations and unmanned aerial vehicles. Furthermore, in some implementations, the NT-TRP 172 may use other names, such as a non-terrestrial node, a non-terrestrial network device, or a non-terrestrial base station. The NT-TRP 172 includes a transmitter 272 and a receiver 274 coupled to one or more antennas 280. To avoid cluttering the drawing, only one antenna 280 is shown. One, some, or all of the antennas may also be panels. The transmitter 272 and receiver 274 may be integrated as a transceiver. The NT-TRP 172 also includes a processor 276 for performing operations including: preparing transmissions for downlink transmission to ED 110, processing uplink transmissions received from ED 110, preparing transmissions for backhaul transmission to T-TRP 170, and processing transmissions received from T-TRP 170 via backhaul. Processing operations related to preparing for downlink or backhaul transmission may include operations such as encoding, modulation, precoding (e.g., MIMO precoding), transmit beamforming, and generating symbols for transmission. Processing operations related to processing transmissions received during uplink transmission or via backhaul transmission may include operations such as receive beamforming, demodulation, and decoding of received symbols. In some embodiments, processor 276 performs transmit beamforming and / or receive beamforming based on beam direction information (e.g., BAI) received from T-TRP 170. In some embodiments, processor 276 may generate signaling, such as configuring one or more parameters of ED 110. In some embodiments, NT-TRP 172 implements physical layer processing but does not implement higher-layer functions, such as medium access control (MAC) or radio link control (RLC) layer functions. Since this is only an example, more generally, NT-TRP 172 may implement higher-layer functions in addition to physical layer processing.

[0092] The NT-TRP 172 also includes a memory 278 for storing information and data. Although not shown, a processor 276 may form part of the transmitter 272 and / or receiver 274. Although not shown, the memory 278 may form part of the processor 276.

[0093] The processor 276, the processing components of the transmitter 272, and the processing components of the receiver 274 can each be implemented using one or more processors, which are the same or different, to execute instructions stored in memory (e.g., in memory 278). Alternatively, some or all of the processor 276, the processing components of the transmitter 272, and the processing components of the receiver 274 can be implemented using dedicated circuitry such as a programmable FPGA, hardware accelerator (e.g., a GPU or AI accelerator), or ASIC. In some embodiments, the NT-TRP 172 can actually be multiple NT-TRPs operating together to serve ED 110, for example, through cooperative multicast.

[0094] T-TRP 170, NT-TRP 172 and / or ED 110 may include other components, but for clarity these components are omitted.

[0095] according to Figure 6 One or more steps of the methods in the various embodiments provided herein can be performed by the corresponding units or modules. Figure 6 Units or modules in device 600 are shown, such as in ED 110, T-TRP 170, or NT-TRP 172. For example, the device may include an operating system module 610. Signals may be transmitted by a transmitting unit or transmitting module 620. Signals may be received by a receiving unit or receiving module 630. Signals may be processed by a processing unit or processing module 640. Other steps may be performed by an artificial intelligence (AI) or machine learning (ML) module 650. The corresponding units or modules may be implemented using hardware, one or more components or devices executing software, or a combination thereof. For example, one or more units or modules may be circuits such as integrated circuits. Examples of integrated circuits include programmable FPGAs, GPUs, or ASICs. For example, one or more units or modules may be logic, such as logical functions performed by circuits, a portion of an integrated circuit, or software instructions executed by a processor. It should be understood that if the above modules are implemented using software for execution by a processor, etc., these modules can be retrieved by the processor in whole or in part as needed, retrieved individually or collectively for processing, retrieved in one or more instances as needed, and these modules themselves may include instructions for further deployment and instantiation.

[0096] Further details regarding ED 110, T-TRP 170, and NT-TRP 172 are known to those skilled in the art. Therefore, these details are omitted herein.

[0097] The solutions described in this application are applicable to next-generation (e.g., sixth generation, 6G or higher) networks or traditional (e.g., 5G, 4G, 3G or 2G) networks.

[0098] The proposed 6G system architecture is defined as supporting 6G XaaS services through the use of technologies such as network function virtualization and network slicing. The 6G system architecture utilizes service-based interactions between 6G services.

[0099] 6G systems utilize a service-based architecture and the XaaS concept. XaaS services in 6G systems are categorized into three layers. Figure 7 The conceptual architecture of a 6G system 700 is shown.

[0100] Infrastructure layer 730 includes the infrastructure supporting 6G services. This includes wireless network (RAN, CN) infrastructure 731 and 732, cloud / data center infrastructure 734, satellite infrastructure 733, and storage / database infrastructure 735. Infrastructure layer 730 may also include other infrastructure 736, such as sensing networks. This infrastructure can be provided by a single provider or multiple providers.

[0101] Each of these infrastructures can have its own control and management functions, known as C / M functions, for infrastructure management. Each of these infrastructures is an Infrastructure as a Service.

[0102] The control and management (C / M) layer 720 includes control and management services for the 6G system. These are developed and deployed using slicing technology and leveraging resources provided by the infrastructure layer. The 6G services in the control and management (C / M) layer are as follows: Resource management (RM) as a service 721 enables lifecycle management of various slices and over-the-air resource allocation for wireless devices.

[0103] Mission management (MM), or Service 722, enables the arrangement of XaaS service provision at the service layer, thereby providing mission services. A 6G mission is defined as a service provided by the 6G system to its customers. A mission can be a type of service provided by a single 6G XaaS service, or it can be a type of service that requires contributions from multiple XaaS services.

[0104] The Confederation Network (CONET) as a Service 725 enables multiple partners to jointly provide 6G services. This capability is achieved through consortium formation, mutual authentication and authorization among partners, and agreement on the recording and traceability of partner-specific operations, ensuring a trusted environment for the operation of 6G systems.

[0105] Service provisioning management (SPM), or Service 723, provides the ability to control and manage customer access to 6G services and the provision of requested services. This capability can be provided through unified mutual authentication, authorization and policies, key management, QoS guarantees, and billing between any pair of XaaS service providers and customers. Customers include not only end customers in the physical world but also digital representatives in the digital world.

[0106] Connectivity Management (CM) as a Service 724 leverages 5G connectivity management capabilities but extends to include the digital world.

[0107] Protocol as a Service (PCS) 726 enables the design of customized protocol stacks for identified interfaces. Protocol stacks can be predefined for on-demand selection or designed as needed.

[0108] Cybersecurity as a Service (CSIS) 727 enables infrastructure owners to detect potential security risks to their infrastructure.

[0109] The XaaS service 720 in the C / M layer supports the control and management of the 6G system itself and can also provide support for vertical services when needed. For example, the RM service 721 can provide air resource management for the Radio Access Network (RAN) and can also provide services to vertical services to enable the allocation of air resources to their end customers. The XaaS service in the C / M layer can be deployed using slicing technology.

[0110] Service layer 710 includes 6G services provided to customers. Service layer 710 may include: Artificial Intelligence (AI) Service 711, referred to as NET4AI as a Service, provides AI capabilities to support a variety of AI applications.

[0111] The service of data collection, data cleansing, data analysis, and data delivery is referred to as DAM as a Service 713. This service provides lifecycle management of statistical data, including the acquisition, de-anonymization, analysis, and delivery of data from any type of sensor, device, network function, etc.

[0112] The data storage and sharing service is designated NET4Data as a Service 712. This service provides data owners with trusted data storage and sharing while complying with regulatory requirements regarding the control of identifiable data.

[0113] Digital World Services, referred to as NET4DW as a Service 715, provides the ability to build, control, and manage digital implementations of the physical world.

[0114] The blockchain service is designated NET4BC as Service 714. NET4Con as Service 716 provides support for 6G blockchain services.

[0115] Enhanced connectivity services, such as Network for Connectivity (NET4CON) as a Service 716, support message and data exchange between new 6G services.

[0116] The XaaS services of the service layer 710 are developed and deployed by leveraging the resources provided by the infrastructure layer 730 and employing network function virtualization and slicing technologies. The capabilities of each 6G service are provided by its control and management functions as well as service-specific data processing functions.

[0117] In addition to supporting 6G XaaS services at Service Layer 710, the 6G system also utilizes the 5G system to provide vertical services. The difference between 6G XaaS services and other vertical services is that vertical services are purely customer-facing and require other XaaS services to operate, while each XaaS service provides its own capabilities to 6G customers.

[0118] In a 6G system, any pair of XaaS services can also act as both customer and provider to each other. For example, an infrastructure owner can provide its resources to XaaS services in Service Layer 710 and C / M Layer 720, while RM service 721 may require capabilities provided by NET4AI 711, DAM 713, and NET4DW 715 to leverage vertical slicing when providing resource management services. Similarly, CONET service 725 and NET4Data service 712 may require capabilities provided by NET4BC to function.

[0119] Key concepts of 6G systems may include: Basic XaaS services are defined by decoupling comprehensive service types into basic XaaS services. Basic XaaS services provide unique capabilities to enable specific types of services, such as NET4AI, NET4DW, DAM, NET4Data, blockchain services, task management services, etc.

[0120] Supports joint operation of 6G systems by multiple partners. Define the data plane of the 6G system, including the data plane processing capabilities of XaaS services. By programming the interconnection of these capabilities through task management services, various customized customer services can be implemented.

[0121] The 6G system architecture is simplified by categorizing basic control and management services and combining them into basic XaaS services in the control and management (C / M) layer.

[0122] Define the C / M layer of the 6G system, including C / M functions as XaaS services, and optionally include the 5G control plane (CP), such as access and mobility functions (AMF).

[0123] Define the basic architecture structure (BAS), which is a unified basic structure with a minimal number of interfaces and is independent of the infrastructure type.

[0124] The BAS concept simplifies the standardization, development, and deployment of 6G systems, while supporting a variety of infrastructure deployment scenarios.

[0125] By applying BAS or subsets of it to the infrastructure based on the capabilities, capacity, and needs of the infrastructure network, it can be adapted to a variety of deployment scenarios.

[0126] The concept of service-based interface (SBI) is utilized, and SBI interaction is applied in the 6G C / M plane and 6G data plane.

[0127] The SBI interface is simplified by introducing trusted gateways in the C / M plane and the data plane.

[0128] Trustworthiness is enhanced from the perspective of 6G system operators by introducing CONET capabilities, NET4BC capabilities, and anonymity services provided by trusted gateways in the C / M plane and data plane of 6G systems.

[0129] By providing unified mutual authentication, identity management (IDM), and data cleansing through SPM, DAM, and 6G blockchain services, the reliability of end-customer privacy protection is improved.

[0130] Simplify roaming management of wireless devices in the physical and digital worlds through unified authentication (across all participating partners and customers).

[0131] By defining multiple architectural options, it supports various development paths from 5G to 6G systems. Due to the introduction of the BAS concept, not much work needs to be done.

[0132] By leveraging the benefits of service-based architecture (SBA) and its additional features, backward compatibility is supported, allowing 5G users to access 5G services using 6G systems.

[0133] By adding new XaaS services to support future expansion, the impact on standardization and deployment is minimized, thanks to the concept of anonymous service provision implemented by trusted gateways in the 6G C / M plane and 6G data plane.

[0134] Digital user support features D-User operations may require several functions initiated by the UE, D-User, and network to support a specific D-User service. The functions that can be hosted on the UE, D-User, and network are described below.

[0135] refer to Figure 8 According to some embodiments of the present invention, UE 803 includes a control plane (CP) that may include authentication and authorization functions. The authentication and authorization functions of UE 803 can be used in conjunction with the authentication and authorization functions of the network and the authentication and authorization function (AAF) 810 of D-User 804. As a non-limiting example, D-User 804 may request data collection directly from UE 803 without the network needing to know the content. Before collecting and sending data, UE 803 may need to authenticate D-User 804. In this case, the authentication and authorization function of UE 803 can challenge D-User 804, which can complete the authentication process through its AAF 810 response.

[0136] The CP of UE 803 may also include functions related to establishing a synchronization channel. A synchronization channel is a secure channel or logical link that enables communication between UE 803 and D-User 804 without notifying the network. For example, using the synchronization channel between UE 803 and D-User 804, context data transmission and updates between UE 803 and D-User 804 can be achieved. UE 803 can install applications to interact with and control some services. For example, UE 803 can utilize applications to subscribe to and request services.

[0137] UE 803 can also host data processing functions (DPFs), such as synchronizing UE data and content with D-User 804, pre-filtering UE application data, and updating the user content interest database.

[0138] According to some embodiments of the present invention, control functions that can be hosted on the network include a D-User creation function (DUCF) 824. DUCF 824 can prepare and save the configurations, policies, and task blueprints required for different UCM services, and store them in a database. DUCF 824 can also establish a synchronization channel between D-User 804 and UE 803, use UCMS to subscribe to and update UE profiles, assess UE capabilities (e.g., software availability, computing power, etc.), and process UE requests for new UCM services. Figure 8 As shown, DUCF 824 is within the hosting platform 823, but in other embodiments, DUCF 824 may be within the C / M plane of the hosting network function 802.

[0139] DUCF 824 can also be responsible for establishing the requested UCM service after correctly authenticating and authorizing a request received from UE 803 or the CPF of a specific network. After authenticating the sender, DUCF 824 can check the user's subscription details and establish the requested UCM service. However, in some cases, UE 803 can directly request the D-User Management Function (DUMF) 818 to dynamically establish the UCM service; DUMF 818 will create the necessary functions and interfaces.

[0140] Digital User Function Architecture D-User can support a wide range of UCM services. Each UCM service may have requirements regarding the support of the network or the functions and services provided by D-User. Figure 8 As shown, D-User functions can be broadly divided into control and management (C / M) plane functions and data plane functions. C / M plane functions provide signaling to control the operation of the D-User, while data plane functions are used to process data. C / M plane functions can also connect to external entities or functions (such as the network's C / M plane functions and / or the network's data plane functions).

[0141] Some D-User and network functions and interfaces may be common across all UCM services, while others may be UCM service-specific. Typically, depending on the UCM service supported by a particular D-User type, a D-User may require one or more C / M functions, and possibly one or more DP functions, to provide the UCM service. Therefore, a D-User may not include all the functions provided in this invention. Each D-User may only include the functions required to provide the requested UCM service. This can reduce costs and save resources.

[0142] Figure 8 This paper illustrates a service-based architecture (SBA) for D-Users provided by at least one embodiment of the present invention. D-User functions are interconnected internally via a common logical bus. In other words, any D-User C / M or DP function can request or use any service of any other function by invoking a service request, as further described herein.

[0143] like Figure 8 As shown, the SBA architecture 800 includes D-User 804. D-User 804 includes a C / M plane (or control and management plane) 805 and a data plane 806. Each of the C / M plane 805 and the data plane 806 includes various functions, as described below.

[0144] The C / M function can provide services to or request services from other intranet functions or external entities through the C / M gateway 807. For example, D-User 804 can be deployed on a managed platform that includes a managed platform C / M face 823 (including DUCF 824) and a managed platform DP 825. The C / M face 823 may also include... Figure 8 Other functions not shown. For example, in some embodiments, the hosting platform may include the NET4DW network or the D-User platform, etc.

[0145] Communication with other entities (internal functions, XaaS services, or third-party networks) can be layered. For example, a D-User C / M function can communicate externally by sending messages to a D-User C / M gateway 807, which then forwards the messages to the gateway of the managed platform C / M plane 823. The gateway of the managed platform C / M plane 823 can then forward the messages to C / M gateways serving the intended function, XaaS service, or third party, such as network managed function 802 or UE 803.

[0146] D-User 804 may require several functionalities to support specific UCM services. While some of these functionalities can be provided by the network or third-party entities, it is preferable that D-User 804 provide them. For example, the privacy preserving portal (PPP) functionality used to protect the D-User's identity could be hosted outside of D-User, such as on NET4DW. However, by hosting the PPP functionality on D-User, additional privacy protection can be achieved because D-User can hide its identity from the hosting platform.

[0147] The following describes some functions that can be hosted on D-User according to some embodiments of the present invention.

[0148] According to some embodiments, D-User 804 includes a C / M gateway 807 in C / M plane 805. C / M gateway 807 is responsible for the interaction between D-User and the network, UE, external entities, etc. For this purpose, C / M gateway 807 may need to identify requests sent to D-User and direct them to the appropriate C / M plane function within D-User.

[0149] According to some embodiments, D-User 804 includes a D-User Management Function (DUMF) 818 in the C / M plane 805. DUMF 818 can receive service establishment requests from UE 803, such as UCM services or XR services, but is not limited to these. DUMF 818 can establish the requested service by creating a new NF and associated interface, as indicated in the blueprint of the corresponding UCM service. DUMF 818 manages the orchestration and lifecycle management (LCM) of other D-User functions, such as D-User control and data plane functions. However, in some embodiments (e.g., when the managed network uses its infrastructure to provide a platform), orchestration can be performed by a network functions virtualization orchestrator (NFVO) using the virtualized infrastructure upon request from DUMF 818. DUMF 818 can also perform LCM on local NFs and radio resource management (RRM) on allocated local resources, including requesting new resources.

[0150] According to some embodiments, D-User 804 includes a policy function (PLF) 812 in the C / M plane 805. The PLF 812 can be used in conjunction with network policy functions to set policies controlling the operation of UCM services. Specifically, the PLF 812 can be responsible for setting policies controlling the operation of internal functions of D-User 804, as well as policies controlling the interaction between D-User functions and external entities. These policies may include, but are not limited to, traffic routing policies, billing policies, reporting policies, payment policies, and data caching policies.

[0151] In at least some embodiments, the operation of PLF 812 may include the following: Session Policy Request: A session policy request can be used to authorize session requests and prepare session-related policies. A session can be defined as an association between a UE and a data network providing data connectivity services. A consumer can be a TFMF, D-User C / M (including C / M gateways), NET4CON C / M gateway, or NET4DW C / M. Inputs may include the UE ID, D-User ID, session ID, data network ID, network feature exposure function (NFEF) ID, one or more NET4CON data gateway IDs, requested QoS parameters, and traffic routing information, such as, but not limited to, packet forwarding or buffering parameters. Outputs may include the policy ID, success or failure indicator, failure reason, and policy details (including the involved NET4CON data gateway ID, involved DPF ID, QoS parameters, and traffic routing information).

[0152] Session Policy Update: The session policy update operation can be used by authorized consumers to update session management policies. Consumers can be TFMF, D-User C / M (including C / M gateways), NET4CON C / M gateways, or NET4DW C / M. Inputs may include policy ID, D-User ID, session ID, data network ID, NFEF ID, one or more NET4CON data gateway IDs, requested QoS parameters, and traffic routing information, such as, but not limited to, packet forwarding or buffering parameters.

[0153] Session Policy Deletion: The session policy deletion operation enables authorized consumers to delete session management policies. Consumers can be XaaS, TFMF, D-User C / M (including C / M gateways), NET4CON C / M gateways, or NET4DW C / M. Inputs may include the policy ID and deletion time. Outputs may include success or failure indicators.

[0154] According to some embodiments, D-User 804 includes an intelligent decision function (IDF) 814 in the C / M plane 805. For some UCM use cases, D-User 804 can act as an intelligent entity that can make decisions on behalf of P-User. The decisions that IDF 814 can make can include decisions related to expected or unexpected situations. For example, D-User 804 can monitor a patient's health status based on various sensor readings and send alerts to the patient when appropriate. D-User 804 can also make doctor-like suggestions to the patient based on the monitored data. IDF 814 can also support UE 803 in smart home control by coordinating events with an appropriate smart home application server.

[0155] As another non-limiting example, D-User 804 can make payments on behalf of P-User via IDF 814. In this example, IDF 814 receives the payment request and can authorize the payment based on P-User's needs and the permissions granted by P-User.

[0156] IDF 814 operates based on payments authorized by P-User through D-User. IDF 814 can create, update, and delete payments authorized by P-User. In at least some embodiments, the operation of IDF 814 may include the following: Authorized Payment Request: The authorized payment request creates a payment profile, which includes payment data identifying the payment authorized by the UE. Inputs may include a payee identifier, the maximum or exact allowed payment amount, the payee's full name, the payment method, the payment frequency, and payment reporting details (e.g., notifying the UE if the payment is successful or rejected). Outputs may include the result of payment profile creation, such as a success or failure indication, the reason for failure, and the payment profile ID.

[0157] Payment Authorization Cancellation: The Payment Authorization Cancellation operation is used to cancel payment authorization and delete the payment profile. Inputs may include the payment profile ID and the recipient ID. Output may include a success or failure indicator.

[0158] According to some embodiments, D-User 804 includes a network feature management function (NFMF) 811 in the C / M plane 805. For some UCM use cases, the network allows D-User 804 to manage one or more network features directly or indirectly. Therefore, D-User 804 can directly control network features by configuring the network entity responsible for managing network features.

[0159] For example, D-User 804 can be granted the ability to manage its service routing within the network and can directly configure the NET4CON data gateway according to its own policy set by PLF 812. Direct NET4CON data gateway configuration is suitable for situations where the NET4CON data gateway is dedicated to D-User 804 and is not shared with other users.

[0160] D-User 804 can also indirectly control network characteristics through the network entity responsible for managing network characteristics. For example, D-User 804 can prepare policies based on pre-defined policy rules of the network, and then D-User 804 can configure the NET4CON data gateway through the network entity that controls the characteristics; in this case, the network entity will be the NET4CON C / M plane. Indirect network characteristic management allows D-User 804 to control its traffic when sharing the NET4CON data gateway with other users.

[0161] According to some embodiments, D-User 804 includes a traffic management function (TFMF) 813 in the C / M plane 805. TFMF 813 can be used when the network allows D-User 804 to manage traffic within D-User and within the network. TFMF 813 can determine the applicable traffic policy based on policies retrieved from PLF 812, and then configure the D-User data plane function (DPF) 817 and the network data plane function accordingly. The traffic-related decisions made by TFMF 813 may involve, but are not limited to, (1) routing (e.g., packet forwarding, buffering, dropping, etc.), (2) packet content inspection, (3) changing source address rules for privacy purposes, and (4) billing (e.g., traffic reporting windows, reporting traffic usage to the network, etc.).

[0162] TFMF 813 can operate on the UE's data sessions. Operations performed by TFMF 813 may include creating, updating, and deleting D-User controlled data sessions. Specifically, in at least some embodiments, the operations of TFMF 813 may include the following: Traffic management request: A traffic management request enables consumers to request traffic management capabilities. Traffic management can include the following: Route assistance and network feature selection: This feature prioritizes certain traffic and provides instructions for forwarding data to a specific destination, taking into account network load on different paths. Service capabilities can be provided to customers. With the help of D-User AI, TFMF 813 can optimize resource utilization by selecting efficient paths and opportunistically proposing and transmitting certain traffic based on network load, user needs, and user interests. To this end, certain network details (e.g., slice abstraction and slice features) are provided to D-User 804 or UE 803, allowing UE 803 to select special features such as special quality-enhanced network configurations, power-saving channels, low-cost routes, and available service locations.

[0163] Network Link Assessment: TFMF 813 can assess the quality of network links along the predicted path of UE 803. For example, TFMF 813 can use the mobility prediction capabilities provided by DMF 809 to predict the future location of UE 803. Users can also obtain coverage information for certain time periods, such as current signal strength and associated costs. Furthermore, users may be able to suggest optimal times and locations for certain applications.

[0164] Consumers can be P-User, NET4DW C / M, D-User platform C / M, NET4CON C / M, or mission manager (MM) C / M. Inputs may include UE ID, D-User ID, ID of the NET4CON data gateway or DPF (if known, controlled), data network ID, session ID, and QoS parameters or reference QoS indicators. Outputs may include success or failure indicators, QoS setup parameters of the NET4CON data gateway, network DPF and D-User internal DPF (e.g., packet latency, bit rate, etc. for each session), packet processing parameters (e.g., rules for buffering, forwarding, filtering, etc.), and traffic management profile ID.

[0165] Traffic Management Cancellation: The Traffic Management Cancellation operation cancels a previously requested traffic management capability. The consumer can be an entity that previously requested the traffic management capability, such as a UE, NET4DW C / M, D-User Platform C / M, NET4CON C / M, or Mission Manager (MM) C / M. Inputs may include the Traffic Management Profile ID, UE ID, D-User ID, Data Network ID, and Session ID. Output may include a success or failure indicator.

[0166] According to some embodiments, D-User 804 includes a content interest management function (CIMF) 815 in the C / M plane 805. For some use cases, the UE 803's interests in different types of content may be available. As a non-limiting example, interest data from UE 803 can be used to prefetch user content and cached at the network and / or D-User 804. CIMF 815 can monitor the behavior and interests of UE 803, prepare a list of content interests, and interact with content providers to retrieve appropriate content. Content data can be stored in a data storage function (DSF) within D-User 804 for later access, such as sending it to UE 803. Implementing CIMF 815 within D-User 804 offers several advantages, such as the ability to select content even when UE 803 is idle or off. With CIMF and DPF within D-User and controlled by D-User, a list of content interests can be prepared while protecting the privacy of UE 803.

[0167] According to some embodiments, D-User 804 includes a privacy protection portal (PPP) 808 in the C / M plane 805. PPP 808 can protect the privacy of UE 803 by preventing the data of UE 803 from being disclosed to untrusted hosts. PPP 808 can also protect user privacy by hiding the user's identity, for example, by changing the user ID when communicating on behalf of D-User 804 with external entities.

[0168] According to some embodiments, D-User 804 includes an authentication and authorization function (AAF) 810 in the C / M plane 805. AAF 810 can be responsible for authenticating UE 803 to D-User 804 and / or authenticating D-User 804 to UE 803.

[0169] In at least some embodiments, the operation of AAF 810 may include the following: User authentication request: The user authentication request is used to authenticate the P-User to other functions, XaaS, etc. The consumer can be a UE or an XaaS. Input can include the UE ID and authentication method. Output can include a success or failure indicator.

[0170] UCMS Authorization Request: A UCMS authorization request can be used to authenticate UCM services. The consumer can be a UE, D-User, or XaaS. Inputs may include the UCM ID, UE ID, and D-User ID. Output may include a success or failure indication.

[0171] According to some embodiments, D-User 804 includes a data management function (DMF) 809 in the C / M plane 805. DMF 809 can support UCM services by providing data-related services to other D-User C / M functions (such as data collection and data analysis). For example, for privacy reasons, D-User 804 may decide to use its own DMF instead of the DAM services provided by the network to collect its data. DMF 809 can also analyze user data and provide the analysis to other D-User C / M functions, or even to the network.

[0172] DMF 809 can also collect network information and provide it to various other functions. For example, according to previous protocols, the network can provide network topology and coverage information. The network can also provide dynamic information, such as network load and billing information. This information can be provided for each slice, as D-User 804 can have functions common to multiple slices or slice-specific functions.

[0173] DMF 809 can also provide mobility management services to the UE. When a UE (e.g., UE 803) moves from one BS area to another, a handover is performed. DMF 809 can anticipate the handover, thus supporting the transfer of UE context and other information to the new BS. DMF 809 can also provide dynamic access to various databases (DBs) installed inside or outside the D-User 804. D-User functions can retrieve, store, and / or update data in the DBs through DMF 809.

[0174] DMF 809 can also provide user context tracking services based on data obtained from UE 803, the predicted location of UE 803, and historical data of UE 803. User context may include information such as attending a football match, watching a sporting event, or traveling by car. User context can be used to predict a user's communication activities.

[0175] DMF 809 can also provide performance monitoring, such as collecting quality metrics and data volume of uplink and downlink data transmissions monitored at the network UPF. The collected performance data can then be used for analysis by the D-User function.

[0176] According to some embodiments, D-User 804 includes a data storage function (DSF) 819 in the data plane 806. DSF 819 may include several data stores for different purposes. For example, one data store may be used for data downloaded from a server based on the user's content interests. Such data may be stored in DSF 819 until it is sent to UE 803. Similarly, UE 803 may send some data to be uploaded to a server. This data may be stored by DSF 819 for uploading to the server based on priority and urgency. DSF 819 may also store a list of content interests for periodic updates by CIMF 815. DSF 819 may also store the user's predicted future location and association probability for access by other algorithms. DSF 819 may also store the user's prediction context.

[0177] According to some embodiments, D-User 804 includes a data processing function (DPF) 817 in the data plane 806. D-User 804 may need to perform data processing for UE 803, the network, or third parties. For example, D-User 804 may perform source address changes for privacy reasons. D-User 804 may also use DPF 817 to manage UE traffic, for example, by making routing decisions, performing packet inspection, classifying data, reporting traffic, and assisting with billing and quality of service (QoS) enforcement.

[0178] DPF 817 can perform specific data processing for P-User, XaaS, D-User functions, or other network entities. In at least some embodiments, the operation of DPF 817 may include the following: Data Processing Request: A data processing request enables a consumer to request specific data processing for a UE, XaaS, or D-User function. Inputs may include one or more processing type IDs, data processing specifications, data identifiers, session IDs, UEIDs, and the target for processing the reported data. Outputs may include a success or failure indicator, a processing report (if available and requested), and a processing profile ID.

[0179] Data Processing Cancellation: The data processing cancellation operation allows consumers to cancel a previously requested data processing request from the DPF. Inputs may include the processing profile ID, and outputs may include a success or failure indication.

[0180] Traffic Parameter Configuration Request: A traffic parameter configuration request allows consumers to manage traffic by setting traffic-related parameters, such as, but not limited to, QoS, packet processing, routing parameters, changing data fields and source addresses to modify user information. The consumer can be a TFMF, such as TFMF 813. Inputs may include information used to identify the traffic (e.g., UE ID, session ID, data network ID), QoS parameters, and packet processing parameters (e.g., buffering, dropping, destination). Outputs may include success or failure indications and the traffic management profile ID.

[0181] Traffic Parameter Setting Cancel: The Traffic Parameter Setting Cancel operation causes the consumer to cancel a previously requested traffic parameter setting request. The consumer can be a TFMF, such as TFMF 813. Inputs may include UE ID, Session ID, Data Network ID, and Traffic Management Profile ID. Output may include a success or failure indication.

[0182] Event Reporting Subscription: The event reporting subscription operation can be used to report specific event data to D-User functions, XaaS, UEs, or third parties, such as, but not limited to, QoS data and data usage. Consumers can be UEs, IDFs, TFMFs, or CIMFs. Inputs may include the event ID, event-specific parameters, UE ID, session ID, reporting method and frequency, timestamp, and the target used for reporting. Outputs may include a success or failure indication, and the reported data (if available).

[0183] Event Reporting Unsubscribe: The event reporting subscription operation can be used to unsubscribe from previously subscribed event reporting. The consumer can be a UE, IDF, TFMF, or CIMF. Inputs can include the event ID, and outputs can include a success or failure indication.

[0184] Now for reference Figure 9A and Figure 9B , Figure 9A and Figure 9B Together, they illustrate a method for providing UCM services based on requests from the UE. Specifically, Figure 9A and Figure 9B The present invention illustrates a method provided by at least some embodiments, wherein the UCM service includes preparing a content interest list for the UE and prefetching relevant content using D-User. In another example, the UCM service includes UE-based request processing data.

[0185] exist Figure 9A and Figure 9B In the scenario shown, P-User 901 and D-User 910 have established 6G C / M connections with their service C / M gateway. The UCM service has been authorized, and support for the D-User functionality of the UCM service has been created.

[0186] like Figure 9A and Figure 9B As shown, the network may include a NET4CON C / M gateway 902, a service provisioning management (SPM) C / M gateway 903, a data analytics and management (DAM) system 904, and a shared database 905. The network may also include a D-User 910, comprising a C / M gateway 911, a CIMF 912, a PLF 913, a DMF 914, a DPF 915, and a PPP 916.

[0187] like Figure 9A As shown, P-User 901 sends message 920 to request the UCM service. The UCM service may include content interest preparation or data processing. Request 920 may be provided to the NET4CON C / M gateway 902. Message 920 may include one or more of the following: UCM service ID, D-User ID, processing type ID, processing specification, data identifier, session ID, P-User ID, time period for content monitoring, geographical area for content monitoring, content ID or a list of content topics to be monitored (e.g., news, sports, social topics, etc.), content provider ID, and an indication of whether the content list or content should be sent to P-User 901.

[0188] After receiving message 920, the NET4CON C / M gateway 902 for service P-User 901 interacts with the SMP C / M gateway 903 to authorize content interest preparation or data processing type, as shown in box 921.

[0189] After authorizing the requested UCM service for P-User 901, NET4CON C / M gateway 902 sends message 922 to D-User C / M gateway 911, which then forwards the message to CIMF 912 as message 923. Messages 922 and 923 may include one or more of the following: P-User ID, UCM service ID, processing type ID, data processing specification, data identifier, session ID, and content-specific information, such as time period, geographic region, content ID, or a list of content topics to be monitored.

[0190] Then, CIMF 912 can send message 924 to PLF 913 to authorize the UCM service request. As a non-limiting example, PLF 913 can determine whether the list of requested content is permitted. Upon receiving message 924, PLF 913 can create a content interest-related policy. As another non-limiting example, PLF 913 can determine whether the data processing type of the identified data is authorized.

[0191] Then, PLF 913 can send a message 925 to CIMF 912, which includes the corresponding policy. Message 925 may also include, but is not limited to, the D-User DPF ID to be monitored, the monitoring time and monitoring area, the target of content interest reporting, and an indication of whether the P-User ID or D-User ID should be protected by privacy.

[0192] Upon receiving message 925, CIMF 912 determines a content preparation strategy or data processing strategy based on the type of the requested UCM service. As a non-limiting example, CIMF 912's content preparation strategy may include selecting the content type based on user input (such as topic selection) and selecting the content type based on user behavior (e.g., frequently consuming a certain type of content, consuming a certain type of content over a longer period). CIMF 912 may also determine which entities (e.g., DAM 904, NET4CON C / M gateway 902) will participate in data monitoring, and options such as update frequency. As another non-limiting example, the data processing strategy may include selecting data monitoring, update frequency, and processing algorithms based on the requested data processing specifications.

[0193] Then, CIMF 912 can send Request 927 to DMF 914. Request 927 may include a request to monitor user behavior and may include a request to retrieve previously collected user data from the network. Request 927 may also include information for identifying the data to be monitored, including but not limited to P-User ID, D-User ID, data network ID, content ID, and time and region parameters. Request 927 may also include information for identifying the data to be retrieved from the network, including but not limited to data location, data ID, description, indication of collection time, user location-specific data, etc.

[0194] Upon receiving request 927, DMF 914 can send message 928 to DPF 915 and message 929 to D-User C / M gateway 911. Message 928 may include a request for monitoring and processing data, and message 929 may include the result of data processing or processed data. D-User C / M gateway 911 can then forward message 929 as messages 930 and 931 to DAM 904 and NET4CON C / M gateway 902, respectively. NET4CON C / M gateway 902 can then forward message 931 as message 932 to P-User 901. Message 928 may request data monitoring and reporting based on one or more specific data processing types and policies determined by PLF 913, while messages 929, 930, 931, and 932 may request data monitoring and reporting based on content interest lists or data identifiers. Data can be reported based on a subscription-notification model (i.e., data is reported whenever it is available) or a request-response model (i.e., data is sent in response to a request from DMF 914). Messages 928, 929, 930, 931, and 932 may also include time and region parameters, content ID or description, data identifier, processed data, accessed data network ID, P-User ID, D-User ID, and the reporting frequency for the subscription-notification model.

[0195] Then, as shown in box 933, the entity responsible for monitoring users monitors users, while the entity responsible for processing user data processes the data and reports the monitoring data to DMF 914. Figure 9A and Figure 9B In the example, these entities include P-User901, NET4CON C / M Gateway902, DAM 904, and DPF 915, but this is not intended to be restrictive.

[0196] like Figure 9B As shown, Figure 9B yes Figure 9A The following diagram illustrates the provision of the UCM service. DMF 914 can then analyze the received user behavior data in box 934 according to the policy or analysis type determined in box 926 by CIMF 912. The analysis results can be stored in the D-User database and updated periodically as new data becomes available. For example, new data may become available as more reports are received from P-User 901, NET4CON C / M gateway 902, DAM 904, and DPF 915, or due to the sending of more data requests (such as messages 928, 929, 930, 931, and 932).

[0197] Then, DMF 914 can send a message 935 to CIMF 912 that includes the results of the content interest analysis. The analysis results may include, but are not limited to, a list of content interests, indications of interest time (e.g., daytime, nighttime, morning, afternoon, time, etc.), and indications of interest location (e.g., office, school, area identifier, etc.).

[0198] Then, CIMF 912 can send message 936 to notify P-User 901 that the content interest list has been updated. Specifically, message 936 can be received by D-User C / M gateway 911, which then forwards message 936 as message 937 to NET4CON C / M gateway 902, which can then notify P-User 901. Message 936 may also include (if requested by P-User) content interest analysis results, which may include, but are not limited to, the content interest list, indications of interest time (e.g., daytime, nighttime, morning, afternoon, time, etc.), and indications of interest location (e.g., office, school, area identifier, etc.).

[0199] CIMF 912 can then send request 938, which instructs PPP 916 to change the P-User ID to protect the privacy of P-User 901 and send the list of content interests to the shared database 905. PPP 916 then changes the P-User ID at box 939.

[0200] PPP 916 can then send message 940 to shared database 905. Message 940 may include a list of content interests and a modified P-User ID. According to at least some embodiments, shared database 905 includes a list of content interests for all D-Users.

[0201] As shown in box 941, the shared database 905 can then extract specific content from various content providers based on specific criteria associated with the content interest list of D-User 910. For example, criteria could include the most popular content or predicted content for the next time window.

[0202] Shared database 905 can then send the extracted content to CIMF 912 via PPP 916 using messages 942 and 943. CIMF 912 can then send the content to P-User 901 for download or browsing, as shown in messages 944, 945, and 946.

[0203] The above functions can be implemented on any one or a combination of computing devices. Figure 10This is a block diagram of a computing device 1000 that can be used to implement the devices and methods disclosed herein. A particular device may use all the components shown or only a subset of those components, and the degree of integration between devices may vary. Furthermore, a device may include multiple instances of components, such as multiple processing units, processors, memory, transmitters, receivers, etc. The computing device 1000 may include a processor 1010, memory 1020, mass storage device 1040, and peripheral devices 1030. Peripheral devices 1030 may include one or more input / output devices, such as speakers, microphones, mice, touchscreens, keyboards, keypads, printers, displays, network interfaces, etc. Communication between the processor 1010, memory 1020, mass storage device 1040, and peripheral devices 1030 may be performed via one or more buses 1050.

[0204] Bus 1050 can be one or more of several bus architectures of any type, including memory bus or memory controller, peripheral device bus, video bus, etc. Processor 1010 can include any type of electronic data processor. Memory 1020 can include any type of system memory, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous DRAM (SDRAM), read-only memory (ROM), or combinations thereof. In one embodiment, memory 1020 can include ROM used at power-on and DRAM used to store programs and data during program execution.

[0205] Mass storage device 1040 may include any type of storage device for storing data, programs (e.g., instructions or code), and other information, and for making this data, programs, and other information accessible via a bus. Mass storage device 1040 may include one or more of solid-state drives, hard disk drives, disk drives, optical disk drives, etc. Memory 1020 or mass storage device 1040 may store instructions that, when executed by a processor or processing unit, cause computing device 1000 to perform any of the methods described herein.

[0206] The computing device 1000 may further include a communication subsystem 1060 for communicating with other computing devices or for connecting the computing device 1000 to a computer network. The communication subsystem 1060 may include one or more network interfaces (not shown), which may include wired links such as Ethernet cables and / or wireless links for accessing nodes or different networks. The network interface enables the processing unit to communicate with remote units over a network. For example, the network interface may provide wireless communication via one or more transmitter / transmit antennas 1070 and one or more receiver / receive antennas 1070. In one embodiment, the processing unit is coupled to a local area network (LAN) or wide area network (WAN) for data processing and communication with remote devices, such as other processing units, the Internet, remote storage facilities, etc.

[0207] The computing device may also include a power supply 1080.

[0208] This invention can be implemented on a computing device (e.g., exemplary computing device 1000). The computing device 1000 can be a network element of a telecommunications network, enabling it to connect to other network elements within the telecommunications network, where all network elements form the telecommunications network. The network element can also receive communications from client devices connected to the telecommunications network and provide services to these client devices.

[0209] Based on the description of the above embodiments, the teachings of this invention can be implemented solely by hardware, or by a combination of software and hardware. Software or other computer-executable instructions for implementing one or more embodiments or parts thereof can be stored on any suitable computer-readable storage medium. The computer-readable storage medium can be a tangible or non-transitory medium, such as optical (e.g., CD, DVD, Blu-ray, etc.), magnetic, hard disk, volatile or non-volatile, solid-state, or any other type of storage medium known in the art.

[0210] Other features and advantages of the present invention will be understood by those skilled in the art.

[0211] The structures, features, accessories, and alternatives of the specific embodiments described herein and illustrated in the accompanying drawings are intended to be generally applicable to all teachings of the invention, including all embodiments described and illustrated herein, provided that compatibility is maintained. In other words, unless so indicated, the structures, features, accessories, and alternatives of a particular embodiment are not intended to be limited to that particular embodiment.

[0212] Furthermore, the detailed description provided above is intended to enable any person skilled in the art to implement or use one or more embodiments of the invention. Various modifications to these embodiments will readily be apparent to those skilled in the art, and the general principles defined herein may be applied to other embodiments without departing from the spirit or scope of the teachings provided herein. Therefore, the methods, systems, and / or apparatuses of the invention are not intended to be limited to the embodiments disclosed herein. The scope of the claims should not be limited by these embodiments but should be given the broadest interpretation consistent with the entire description. Reference to an element in the singular, such as “a” or “an,” unless specifically stated otherwise, does not mean “one and only one,” but rather “one or more.” All structural and functional equivalents of the various embodiment elements described throughout the invention, known to or to be known hindsight by a person of ordinary skill in the art, are intended to be covered by the elements of the claims.

[0213] Furthermore, nothing herein is intended to acknowledge prior art or common general knowledge. Moreover, the citation or identification of any document in this application does not imply an acknowledgment that such document can be used as prior art, nor does it imply that any reference constitutes part of common general knowledge in the art. Furthermore, nothing disclosed herein is intended to be offered to the public, whether or not such disclosure is expressly stated in the claims.

[0214] In the foregoing description, numerous details have been set forth to provide an understanding of the subject matter disclosed herein. However, implementations may be carried out without these details. Other implementations may include modifications and variations to the foregoing details. The appended claims cover such modifications and variations.

Claims

1. A method implemented at a network element, characterized in that, include: Receive a request for user controlled and managed (UCM) services from a physical user (P-User), the request including a UCM service identifier; In response to the request, a digital user (D-User) is created for the P-User, wherein the D-User includes multiple functions that are selected to support the UCM service; Configure the D-User so that the P-User can use the control plane of the multiple functions to control the features of the UCM service.

2. The method according to claim 1, characterized in that, The control plane functionality is provided as a service.

3. The method according to claim 1, characterized in that, The multiple functions include at least one of the following: control and management gateway (C / M GW), privacy protection portal (PPP), authentication and authorization function (AAF), policy function (PLF), intelligent decision function (IDF), network feature management function (NFMF), traffic management function (TFMF), content interest management function (CIMF), data management function (DMF), data storage function (DSF), D-User management function (DUMF), data gateway (Data-GW), and data processing function (DPF).

4. The method according to claim 1, characterized in that, The creation of the D-User is performed by the D-User creation function (DUCF).

5. The method according to claim 1, characterized in that, The P-User communicates with the D-User through a control and management (C / M) gateway.

6. The method according to claim 1, characterized in that, Each of the multiple functions accesses each of the other multiple functions.

7. The method according to claim 3, characterized in that, The plurality of functions include the CIMF and the DMF, wherein the CIMF is used for: Select the network entity to be monitored; The network entity is instructed to monitor the content consumption of the P-User; Receive a list of content interests from the DMF; The content interest list is notified to the P-User.

8. The method according to claim 7, characterized in that, The CIMF is also used to provide the content interest list to a shared database.

9. The method according to claim 8, characterized in that, The multiple functions also include the PPP, which is used to change the P-User identifier associated with the content interest list.

10. The method according to claim 9, characterized in that, The CIMF is also used for: Receive content from the shared database; The received content is notified to the P-User.

11. The method according to claim 7, characterized in that, The selected network entity includes at least one of the following: the P-User, the DPF, and the network DPF.

12. The method according to claim 1, characterized in that, The UCM service identifier includes the data processing type.

13. The method according to claim 12, characterized in that, The request includes a data processing specification, a data identifier, a session identifier, a P-User identifier, a data processing function (DPF) identifier, and a reporting target.

14. The method according to claim 13, characterized in that, Also includes: The response message is sent to the P-User, and the response message includes at least one of the following: a success or failure indication, a data processing report.

15. The method according to claim 3, characterized in that, Also includes: Receive authentication challenge from the P-User; Provide the authentication challenge to the AAF; Receive a response from the AAF; The response is provided to the P-User.

16. The method according to claim 1, characterized in that, Also includes: Receive a request to establish a synchronization channel from the P-User; Establish the synchronization channel with the P-User; Use the synchronization channel to transmit context data with the P-User.

17. The method according to claim 1, characterized in that, Also includes: Synchronize data with the P-User's data processing function (DPF).

18. A network element, characterized in that, include: One or more processors for performing the method according to any one of claims 1 to 17.

19. A computer-readable medium, characterized in that, The system stores executable code for execution by a processor of a network element, the executable code including instructions for performing the method according to any one of claims 1 to 17.

Images