Control plane service selection

Abstract

Various aspects of the present disclosure generally relate to wireless communications. In some aspects, a user equipment (UE) may select services provided over a control plane. The UE may send a message including an indication of a service and a UE identifier of the UE. A UE may receive a configuration for a service. Numerous other aspects are described.

Description

[0001] Cross-reference to related applications

[0002] This patent application claims priority to U.S. Provisional Patent Application No. 63 / 584,841, filed September 22, 2023, entitled "CONTROL PLANE SERVICE SELECTION," and U.S. Non-Provisional Patent Application No. 18 / 600,580, filed March 8, 2024, entitled "CONTROL PLANE SERVICE SELECTION," which are assigned to the assignee of this application. The disclosure of the earlier applications is considered part of this patent application and is incorporated herein by reference. Technical Field

[0003] All aspects of this disclosure relate to wireless communication, and to technologies and apparatus for control plane services. Background Technology

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems employ multiple access technologies that enable communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems, and Long Term Evolution (LTE). LTE / LTE-Advanced is an enhancement set of the Universal Mobile Telecommunications System (UMTS) mobile standard issued by the 3rd Generation Partnership Project (3GPP).

[0005] A wireless network may include one or more network nodes that support communication for wireless communication devices, such as user equipment (UE) or multiple UEs. A UE may communicate with network nodes via downlink and uplink communication. A "downlink" (or "DL") refers to the communication link from the network node to the UE, and an "uplink" (or "UL") refers to the communication link from the UE to the network node. Some wireless networks may support device-to-device communication, such as via local links (e.g., sidelinks (SL), wireless local area network (WLAN) links, and / or wireless personal area network (WPAN) links, etc.).

[0006] The aforementioned multiple access technologies have been adopted in various telecommunications standards to provide a common protocol that enables different UEs to communicate at the city, country, region, and / or global levels. 5G (which may be referred to as New Radio (NR)) is an enhancement set of the LTE mobile standard issued by 3GPP. 5G is designed to better support mobile broadband internet access by using Orthogonal Frequency Division Multiplexing (OFDM) with a Cyclic Prefix (CP) (CP-OFDM) on the downlink, and CP-OFDM and / or Single Carrier Frequency Division Multiplexing (SC-FDM) (also known as Discrete Fourier Transform Extended OFDM (DFT-s-OFDM)) on the uplink, as well as supporting beamforming, multiple-input multiple-output (MIMO) antenna technologies and carrier aggregation to improve spectral efficiency, reduce costs, improve service, utilize new spectrum, and better integrate with other open standards. Further improvements to 4G, 5G, and other radio access technologies remain useful as the demand for mobile broadband access continues to increase. Summary of the Invention

[0007] In the early days of the internet, data networks were built to provide numerous services through heterogeneous devices. A design principle of the data network model was that it incorporated a layered system architecture with simple service interfaces spanning many applications and transports. The data network model resembled an hourglass with the Internet Protocol (IP) layer in the middle, allowing routing protocols to be placed on top of any type of interface. Different types of transmissions or services could run on this interface.

[0008] With the advent of cellular radio networks (such as 3G and 4G), the hourglass aspect of the data network model was adopted into the cellular network model. With the introduction of smartphones, 4G successfully provided many services. The 4G protocol stack was designed to support the same model as the internet but used for cellular radio networks. This involved a separate control plane to manage data transmission for cellular needs such as mobility. The separate control plane protocol stack and user plane protocol stack continued the architecture defined for 3G.

[0009] With the expansion of 4G, new features were introduced to extend system capabilities to new use cases and device types. However, deploying new services without upgrading the underlying protocols is not feasible. Adding services via the control plane is not as straightforward as enabling new services via IP. The challenge lies in enabling services to be deployed independently, while making the most of existing protocols and allowing UEs to address services directly without relying on intermediate network functions (e.g., Non-Access Layer (NAS) signaling, Radio Resource Control (RRC) signaling). Furthermore, with the move to 6G, defining new data collection, location, or other protocols in 6G and every subsequent generation (G) may not be optimal.

[0010] Based on the various aspects described herein, new network designs may involve a separate set of protocols (e.g., RRC, NAS) that are far removed from centralized control (e.g., Central Unit Control Plane (CU-CP), Access and Mobility Functions (AMF)). This separate set of protocols may make the control plane architecture very inflexible (and involve a large-scale control plane protocol). This could include providing separate control plane services that can be requested individually, such as authentication and security services, subscription services, and policy services. Any update to a separate service does not require an update to the entire control plane. For example, a User Equipment (UE) may send a message with an indication of a service (provided via the control plane) and a UE identifier (ID) to a Radio Access Network (RAN) entity. This message may include a control plane transport header on the control plane transport layer, which is used to forward the message to the address of the service. The RAN network entity may determine the address mapped to the service and forward the message to that address. The service entity at that address may send a configuration for the service, which is forwarded to the UE. The UE can then use the service via the control plane.

[0011] By using separate addressable services on the control plane, UEs and the network can deploy services more flexibly. Therefore, control plane updates can be faster and involve less service disruption. The core network can support more distributed functionalities, where the UE can communicate directly with each functionality (service). The UE can communicate with any service via the control plane, where control plane transports are shared with and independent of the control plane service. The UE can discover service addresses, while the network hides the network topology. New or enhanced services can be added later without affecting control plane transports at the UE, RAN, or intermediate nodes. Therefore, control plane updates can be faster and involve less service disruption. This also improves service adoption on the network and creates new revenue streams while limiting future generations of control plane redefinition.

[0012] Some aspects described herein relate to a method for wireless communication performed by a UE. This method may include selecting a service provided via the control plane. This method may include sending a message including an indication of the service and the UE's UEID. This method may include receiving configuration for the service.

[0013] Some aspects described herein relate to a method of wireless communication performed by a first network entity. The method may include receiving a message from a UE, the message including an indication of a service provided via a control plane and the UE's UE ID. The method may include forwarding the message to an address of the service based at least in part on the indication of the service.

[0014] Some aspects described herein relate to a method of wireless communication performed by a second network entity. The method may include receiving service selection information associated with a service from a first network entity. The method may also include sending a service ID associated with the service to the first network entity.

[0015] Some aspects described herein relate to a method for wireless communication performed by a network entity. This method may include receiving a message including an indication of a service provided via the control plane and the UE's UE ID. This method may also include sending configuration for that service.

[0016] Some aspects described herein relate to an apparatus for wireless communication at a UE. The apparatus may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured individually or collectively to select a service provided via a control plane. The one or more processors may be configured individually or collectively to transmit a message including an indication of the service and the UE ID of the UE. The one or more processors may be configured individually or collectively to receive configuration for the service.

[0017] Some aspects described herein relate to an apparatus for wireless communication at a first network entity. The apparatus may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured individually or collectively to receive a message from a UE, the message including an indication of a service provided via the control plane and the UE's UE ID. The one or more processors may be configured individually or collectively to forward the message to an address of the service, at least in part, based on the indication of the service.

[0018] Some aspects described herein relate to an apparatus for wireless communication at a second network entity. The apparatus may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured individually or collectively to receive service selection information associated with a service from a first network entity. The one or more processors may be configured individually or collectively to send a service ID associated with the service to the first network entity.

[0019] Some aspects described herein relate to an apparatus for wireless communication at a network entity. The apparatus may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured individually or collectively to receive messages including indications of services provided via the control plane and the UE ID of the UE. The one or more processors may be configured individually or collectively to transmit configuration for the service.

[0020] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a UE. When executed by one or more processors of the UE, the set of instructions enables the UE to select a service provided via a control plane. When executed by one or more processors of the UE, the set of instructions enables the UE to send a message including an indication of the service and the UE's UE identifier. When executed by one or more processors of the UE, the set of instructions enables the UE to receive configuration for the service.

[0021] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a first network entity. When executed by one or more processors of the first network entity, the set of instructions enables the first network entity to receive a message from a UE, the message including an indication of a service provided via a control plane and a UE identifier of the UE. When executed by one or more processors of the first network entity, the set of instructions enables the first network entity to forward the message to the address of the service, at least in part, based on the indication of the service.

[0022] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a second network entity. When executed by one or more processors of the second network entity, the set of instructions enables the second network entity to receive service selection information associated with a service from a first network entity. When executed by one or more processors of the second network entity, the set of instructions also enables the second network entity to send a service identifier associated with the service to the first network entity.

[0023] Some aspects described herein relate to a non-transitory computer-readable medium storing a set of instructions for wireless communication by a network entity. When executed by one or more processors of the network entity, the set of instructions enables the network entity to receive messages including indications of services provided via the control plane and a UE identifier of a UE. When executed by one or more processors of the network entity, the set of instructions enables the network entity to send configuration for the services.

[0024] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for selecting services provided via a control plane. The apparatus may include components for transmitting messages including an indication of the service and an identifier of the apparatus. The apparatus may include components for receiving configurations for the service.

[0025] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for receiving a message from another device, the message including an indication of a service provided via a control plane and an identifier of the other device. The apparatus may include components for forwarding the message to an address of the service, at least in part based on the indication of the service.

[0026] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for receiving service selection information associated with a service from a first network entity. The apparatus may also include components for transmitting a service identifier associated with the service to the first network entity.

[0027] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include components for receiving messages, including indications of services provided via a control plane and an identifier of another device. The apparatus may also include components for transmitting configurations for the services.

[0028] The general terms include, as fully described with reference to the accompanying drawings and description and illustrated by reference to the accompanying drawings and description, methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, wireless communication equipment, network entities, network nodes and / or processing systems.

[0029] The features and technical advantages of the examples according to this disclosure have been summarized rather extensively above in order to better understand the detailed description below. Additional features and advantages will be described below. The disclosed concepts and specific examples can be readily utilized as the basis for modifying or designing other structures for achieving the same purpose of this disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein (both their organization and manner of operation) and the associated advantages will be better understood from the following description when considered in conjunction with the accompanying drawings. Each figure in the drawings is provided for illustrative and descriptive purposes and not as a limitation of the definitions in the claims. Attached Figure Description

[0030] FIG. 1 This is a diagram illustrating an example of a wireless network.

[0031] FIG. 2 This is a diagram illustrating an example of communication between a network node and a user equipment (UE) in a wireless network.

[0032] FIG. 3 This is a diagram illustrating an example of a decomposed base station architecture.

[0033] FIG. 4 This is a diagram illustrating an example of a core network configured to provide network slicing.

[0034] FIG. 5 This is a diagram illustrating examples of the user plane protocol stack and control plane protocol stack of the network node and core network used for communication with the UE.

[0035] FIG. 6 This is an example diagram illustrating the design model.

[0036] FIG. 7 This is an example diagram illustrating a 5G design.

[0037] FIG. 8 This is a diagram illustrating an example of a new design for a network.

[0038] FIG. 9 This is a flowchart of an example method for wireless communication.

[0039] FIG. 10 This is a flowchart of an example method for wireless communication.

[0040] FIG. 11 This is a diagram of an example device used for wireless communication.

[0041] FIG. 12 This is a diagram illustrating an example of a hardware implementation of a device employing a processing system.

[0042] FIG. 13 This is a diagram of an example device used for wireless communication.

[0043] FIG. 14 This is a diagram illustrating an example of a hardware implementation of a device employing a processing system.

[0044] FIG. 15 This is a diagram illustrating an example of a new radio (NR) system architecture according to this disclosure.

[0045] FIG. 16 This is a diagram illustrating an example of a network design according to this disclosure.

[0046] FIG. 17 This is a diagram illustrating an example of a control plane service according to this disclosure.

[0047] FIG. 18 This is a diagram illustrating an example of a service-based architecture according to this disclosure.

[0048] FIG. 19 This is a diagram illustrating an example of a control plane protocol stack according to this disclosure.

[0049] FIG. 20 This is a diagram illustrating an example of a control plane protocol stack according to this disclosure.

[0050] FIG. 21 This is a diagram illustrating an example of a control plane transmission process according to this disclosure.

[0051] FIG. 22 This is a diagram illustrating an example of a security context flow according to this disclosure.

[0052] FIG. 23 This is a diagram illustrating an example of service selection according to this disclosure.

[0053] FIG. 24 This is a diagram illustrating an example of service selection according to this disclosure.

[0054] FIG. 25 This is a diagram illustrating an example of service selection according to this disclosure.

[0055] FIG. 26 This is a flowchart of an example method for wireless communication.

[0056] FIG. 27 This is a flowchart of an example method for wireless communication.

[0057] FIG. 28 This is a flowchart of an example method for wireless communication.

[0058] FIG. 29 This is a flowchart of an example method for wireless communication.

[0059] FIG. 30 This is a diagram of an example device for wireless communication according to the present disclosure.

[0060] FIG. 31 This is a diagram illustrating an example of a hardware implementation of a device employing a processing system according to the present disclosure.

[0061] FIG. 32 This is a diagram of an example device for wireless communication according to the present disclosure.

[0062] FIG. 33 This is a diagram illustrating an example of a hardware implementation of a device employing a processing system according to the present disclosure.

[0063] FIG. 34 This is a diagram of an example device for wireless communication according to the present disclosure.

[0064] FIG. 35 This is a diagram illustrating an example of a hardware implementation of a device employing a processing system according to the present disclosure.

[0065] FIG. 36 This is a diagram of an example device for wireless communication according to the present disclosure.

[0066] FIG. 37 This is a diagram illustrating an example of a hardware implementation of a device employing a processing system according to the present disclosure. Detailed Implementation

[0067] The detailed description that follows, taken in conjunction with the accompanying drawings, is intended as a description of various configurations and not as a representation of a configuration in which the concepts described herein can be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts can be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

[0068] Various apparatuses and methods will now be used to present several aspects of a telecommunications system. These apparatuses and methods will be described in detail below and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively, “elements”). These elements can be implemented using electronic hardware, computer software, or any combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the system as a whole.

[0069] By way of example, an element, or any part of an element, or any combination of elements, may be implemented using a "processing system" comprising one or more processors. Examples of processors include microprocessors, microcontrollers, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic units, discrete hardware circuits, and other suitable hardware configured to perform the various functionalities described throughout this disclosure. One or more processors in the processing system can execute software. Software should be interpreted broadly as instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description languages, or other names.

[0070] Therefore, in one or more example embodiments, the described functionality may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functionality may be stored or encoded as one or more instructions or code on a computer-readable medium. A computer-readable medium includes a computer storage medium. The storage medium may be any available medium accessible to a computer. By way of example, and not limitation, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), compact disc ROM (CD-ROM), or other optical disc storage devices, magnetic disk storage devices, or other magnetic storage devices, combinations of computer-readable media of the types described above, or any other medium that can be used to store computer-executable code in the form of computer-accessible instructions or data structures.

[0071] Although terms generally associated with 5G or New Radio (NR) Radio Access Technology (RAT) may be used herein to describe aspects, aspects of this disclosure may be applied to other RATs, such as 3G RAT, 4G RAT and / or 5G and later (e.g., 6G) RATs.

[0072] FIG. 1 This is an illustration of an example of a wireless network 100. Wireless network 100 can be a 5G (e.g., NR) network or a 4G (e.g., LTE) network, or may include elements of a 5G (e.g., NR) network or elements of a 4G (e.g., LTE) network, etc. Wireless network 100 may include one or more network nodes 110 (shown as network node 110a, network node 110b, network node 110c, and network node 110d), user equipment (UE) 120 or multiple UEs 120 (shown as UE 120a, UE 120b, UE 120c, UE 120d, and UE 120e), or other entities. Network node 110 is an example of a network node communicating with UE 120. As shown, network node 110 may include one or more network nodes. For example, network node 110 can be an aggregated network node, meaning that the aggregated network node is configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or unit). As another example, network node 110 can be a decomposed network node (sometimes referred to as a decomposed base station), meaning that network node 110 is configured to utilize a protocol stack that is physically or logically distributed among two or more nodes (such as one or more central units (CUs), one or more distributed units (DUs), or one or more radio units (RUs)).

[0073] In some examples, network node 110 is or includes network nodes such as RU that communicate with UE 120 via a radio access link. In some examples, network node 110 is or includes network nodes such as DU that communicate with other network nodes 110 via a fronthaul or midhaul link. In some examples, network node 110 is or includes network nodes such as CU that communicate with other network nodes 110 via a midhaul link or with the core network via a backhaul link. In some examples, network node 110 (such as aggregated network node 110 or decomposed network node 110) may include multiple network nodes, such as one or more RUs, one or more CUs, and / or one or more DUs. For example, network node 110 may include 5G base stations, LTE base stations, Node Bs, eNBs (e.g., in 4G), gNBs (e.g., in 5G), access points, Transmit / Receive Points (TRPs), DUs, RUs, CUs, network mobility elements, core network nodes, network elements, network equipment, RAN nodes, or combinations thereof. In some examples, network nodes 110 may interconnect with each other or with one or more other network nodes 110 in the wireless network 100 using any suitable transport network through various types of fronthaul, midhaul, and / or backhaul interfaces (such as direct physical connections, air interfaces, or virtual networks). In some examples, core network node 130 may be a network node that communicates with RAN nodes and / or other core network nodes.

[0074] In some examples, network node 110 may provide communication coverage for a specific geographic area. In the 3rd Generation Partnership Project (3GPP), depending on the context in which the term is used, the term "cell" may refer to the coverage area of ​​network node 110 or a network node subsystem serving that coverage area. Network node 110 may provide communication coverage for macrocells, picocells, femtocells, or another type of cell. A macrocell may cover a relatively large geographic area (e.g., with a radius of several kilometers) and may allow unrestricted access by UE 120 with a service subscription. A picocell may cover a relatively small geographic area and may allow unrestricted access by UE 120 with a service subscription. A femtocell may cover a relatively small geographic area (e.g., a residential area) and may allow restricted access by UE 120 associated with that femtocell (e.g., UE 120 in a Closed Subscriber Group (CSG)). Network node 110 used for macrocells may be referred to as a macro network node. Network node 110 used for picocells may be referred to as a pico network node. The network node 110 used for femtocells can be referred to as a femtocell network node or a home network node. FIG. 1In the example shown, network node 110a may be a macro network node for macro cell 102a, network node 110b may be a pico network node for pico cell 102b, and network node 110c may be a femto network node for femto cell 102c. Network nodes may support one or more (e.g., three) cells. In some examples, the cells may not necessarily be stationary, and the geographical area of ​​the cells may move depending on the location of the mobile network node 110 (e.g., a mobile network node).

[0075] In some aspects, the term "base station" or "network node" may refer to an aggregated base station, a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, or one or more components thereof. For example, in some aspects, "base station" or "network node" may refer to a CU, DU, RU, a near real-time (near RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC, or a combination thereof. In some aspects, the term "base station" or "network node" may refer to a device configured to perform one or more functions (such as those described herein in conjunction with network node 110). In some aspects, the term "base station" or "network node" may refer to multiple devices configured to perform one or more functions. For example, in some distributed systems, each of multiple different devices (which may be located in the same geographical location or different geographical locations) may be configured to perform at least a portion of a function, or to repeatedly perform at least a portion of that function, and the term "base station" or "network node" may refer to any one or more of these different devices. In some aspects, the term "base station" or "network node" may refer to one or more virtual base stations or one or more virtual base station functions. For example, in some aspects, two or more base station functions can be instantiated on a single device. In some aspects, the term "base station" or "network node" may refer to one base station function rather than another. In this way, a single device can include more than one base station.

[0076] Wireless network 100 may include one or more relay stations. A relay station is a network node that receives data transmissions from an upstream node (e.g., network node 110 or UE 120) and transmits data to a downstream node (e.g., UE 120 or network node 110). A relay station may be a UE 120 that can relay transmissions to other UE 120s. FIG. 1 In the example shown, network node 110d (e.g., a relay network node) can communicate with network node 110a (e.g., a macro network node) and UE 120d to facilitate communication between network node 110a and UE 120d. The network node 110 for relay communication may be referred to as a relay station, relay base station, relay network node, relay node, or relay, etc.

[0077] The wireless network 100 can be a heterogeneous network, comprising different types of network nodes 110, such as macro network nodes, pico network nodes, femto network nodes, or relay network nodes. These different types of network nodes 110 may have different transmit power levels, different coverage areas, or different effects on interference in the wireless network 100. For example, macro network nodes may have high transmit power levels (e.g., 5 watts to 40 watts), while pico network nodes, femto network nodes, and relay network nodes may have lower transmit power levels (e.g., 0.1 watts to 2 watts).

[0078] The network controller may be coupled to or communicate with a set of network nodes 110, and may provide coordination and control for these network nodes 110. The network controller may communicate with the network nodes 110 via a backhaul or midhaul link. The network nodes 110 may also communicate directly with each other, or indirectly via a wireless or wired backhaul link. In some aspects, the network controller may be a CU or a core network device, or may include a CU or a core network device.

[0079] UE 120 may be distributed throughout the wireless network 100, and each UE 120 may be stationary or mobile. UE 120 may include, for example, an access terminal, a terminal, a mobile station, or a subscriber unit. UE 120 may be a cellular phone (e.g., a smartphone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smartwatch, smart clothing, smart glasses, a smart wristband, smart jewelry (e.g., a smart ring or smart bracelet)), an entertainment device (e.g., a music device, a video device, or a satellite radio), an in-vehicle component or sensor, a smart meter / sensor, industrial manufacturing equipment, a GPS device, a UE function of a network node, or any other suitable device configured to communicate via wireless or wired media.

[0080] Some UEs 120 may be considered machine-type communication (MTC) or evolved or enhanced machine-type communication (eMTC) UEs. MTC UEs or eMTC UEs may include, for example, robots, unmanned aerial vehicles, remote devices, sensors, meters, monitors, or location markers that can communicate with network nodes, another device (e.g., a remote device), or some other entity. Some UEs 120 may be considered Internet of Things (IoT) devices or may be implemented as NB-IoT (Narrowband IoT) devices. Some UEs 120 may be considered customer premises equipment. UEs 120 may be included within a housing that houses the components of the UE 120, such as processor components or memory components. In some examples, the processor components and memory components may be coupled together. For example, the processor components (e.g., one or more processors) and memory components (e.g., memory) may be operatively coupled, communicatively coupled, electronically coupled, or electrically coupled.

[0081] Generally, any number of wireless networks 100 can be deployed in a given geographical area. Each wireless network 100 can support a specific RAT and can operate on one or more frequencies. A RAT can also be referred to as a radio technology or air interface. A frequency can also be referred to as a carrier or frequency channel. Each frequency in a given geographical area can support a single RAT to avoid interference between wireless networks using different RATs. In some cases, NR or 5G RAT networks can be deployed.

[0082] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly using one or more sidelink channels (e.g., without using network node 110 as an intermediary for communication with each other). For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocols (e.g., which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, or vehicle-to-pedestrian (V2P) protocols), or mesh networks. In such examples, UE 120 may perform scheduling operations, resource selection operations, or other operations described elsewhere herein as being performed by network node 110.

[0083] Devices in wireless communication network 100 can communicate using the electromagnetic spectrum, which can be subdivided into various categories, bands, or channels by frequency or wavelength. For example, devices in network 100 can communicate using one or more operating bands. In 5G, two initial operating bands have been identified as frequency ranges designated FR1 (410MHz-7.125GHz) and FR2 (24.25GHz-52.6GHz). Although a portion of FR1 is greater than 6GHz, in various documents and articles, FR1 is often (interchangeably) referred to as the “sub-6GHz” band. Similar naming issues sometimes occur with FR2, which is often (interchangeably) referred to in documents and articles as the “millimeter wave” band, although this is different from the extremely high frequency (EHF) band (30GHz to 300GHz) identified as a “millimeter wave” band by the International Telecommunication Union (ITU).

[0084] The frequencies between FR1 and FR2 are generally referred to as intermediate frequency (IF) bands. Recent 5G research has designated the operating bands for these IF bands as the frequency range designation FR3 (7.125 GHz – 24.25 GHz). Bands falling within FR3 can inherit FR1 or FR2 characteristics, thus effectively extending the features of FR1 or FR2 into the IF band. Furthermore, higher frequency bands are currently being explored to extend 5G operation beyond 52.6 GHz. For example, three higher operating bands have been designated as the frequency range designations FR4a or FR4-1 (52.6 GHz to 71 GHz), FR4 (52.6 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Each of these higher frequency bands falls within the EHF band.

[0085] In light of these examples, unless otherwise specifically stated, the term "below 6 GHz" as used herein can broadly refer to frequencies less than 6 GHz, frequencies within FR1, or frequencies that may include intermediate frequency bands. Furthermore, unless otherwise specifically stated, the term "millimeter wave" as used herein can broadly refer to frequencies that may include intermediate frequency bands, frequencies within FR2, FR4, FR4-a, FR4-1, or FR5, or frequencies within the EHF band. It is conceivable that the frequencies included in these operating frequency bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, or FR5) can be modified, and the techniques described herein are applicable to those modified frequency ranges.

[0086] In some aspects, the UE (e.g., UE 120) may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may select services provided via the control plane. The communication manager 140 may send a message including an indication of the service and the UE's UE identifier (ID). The communication manager 140 may receive configuration for the service. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0087] In some aspects, the first network entity (e.g., network node 110) may include a communication manager 150. As described elsewhere in this document in more detail, the communication manager 150 may receive a message from the UE that includes an indication of a service provided through the control plane and the UE's UE ID. The communication manager 150 may forward the message to the address of the service based at least in part on the indication of the service. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0088] In some aspects, the second network entity (e.g., core network node 130) may include a communication manager 160. As described elsewhere in this document in more detail, the communication manager 160 may receive service selection information associated with a service from the first network entity. The communication manager 160 may send the service ID associated with the service to the first network entity. Additionally or alternatively, the communication manager 160 may perform one or more other operations described herein.

[0089] In some respects, network entities (e.g., core network node 130) may include a communications manager 160. As described elsewhere in this document in more detail, the communications manager 160 may receive messages that include indications of services provided through the control plane and the UE's UE ID. The communications manager 160 may send configurations for those services. Additionally or alternatively, the communications manager 160 may perform one or more other operations described herein.

[0090] In some aspects, the UE (e.g., UE 120) may include a communication manager 140. As described elsewhere in this document in more detail, the communication manager 140 may select a user plane for service; send requests for service via the user plane. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0091] In some respects, a network entity (e.g., network node 110) may include a communication manager 150. As described elsewhere in this document in more detail, the communication manager 150 may receive requests for services through the user plane and send responses indicating that the service will be provided through the user plane. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0092] As indicated above, FIG. 1 This is provided as an example. Other examples are available with reference to [the relevant information]. FIG. 1 The examples described are different.

[0093] FIG. 2 This is a diagram illustrating an example 200 of a network node 110 communicating with a UE 120 in a wireless communication network 100. The network node 110 may be equipped with antenna sets 234a to 234t, such as T antennas (T≥1). The UE 120 may be equipped with antenna sets 252a to 252r, such as R antennas (R≥1). The network node 110 of example 200 includes one or more radio frequency components, such as antennas 234 and modems 232. In some examples, the network node 110 may include an interface, a communication component, or another component facilitating communication with the UE 120 or another network node. Some network nodes 110 may not include radio frequency components facilitating direct communication with the UE 120, such as one or more CUs or one or more DUs.

[0094] At network node 110, transmitting processor 220 can receive data from data source 212 intended for use by UE 120 (or UE set 120). Transmitting processor 220 can use one or more Channel Quality Indicators (CQIs) received from UE 120 to select one or more modulation and decoding schemes (MCSs) for that UE 120. Network node 110 can use the MCS selected for UE 120 to process (e.g., encode and modulate) the data for UE 120 and can provide data symbols to UE 120. Transmitting processor 220 can process system information (e.g., semi-static resource partitioning information (SRPI)) and control information (e.g., CQI requests, grants, or upper-layer signaling) and provide overhead symbols and control symbols. Transmitting processor 220 can generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS) or demodulation reference signals (DMRS)) and synchronization signals (e.g., primary synchronization signal (PSS) or secondary synchronization signal (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 can perform spatial processing (e.g., pre-decoding, if applicable) on data symbols, control symbols, overhead symbols, or reference symbols, and can provide a set of output symbol streams (e.g., T modems) to a corresponding set of modems 232, shown as modems 232a to 232t. For example, each output symbol stream can be provided to a modulator component (shown as MOD) of modem 232. Each modem 232 can use a corresponding modulator component to process the corresponding output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modem 232 can also use a corresponding modulator component to process (e.g., convert to analog, amplify, filter, or up-convert) the output sample stream to obtain a downlink signal. Modems 232a to 232t can transmit a set of downlink signals (e.g., T downlink signals) via a corresponding set of antennas 234 (e.g., T antennas) (shown as antennas 234a to 234t).

[0095] At UE 120, an array of antennas 252 (shown as antennas 252a to 252r) can receive downlink signals from network node 110 or other network nodes 110, and can provide an array of received signals (e.g., R received signals) to an array of modems 254 (e.g., R modems) (shown as modems 254a to 254r). For example, each received signal can be provided to a demodulator component (shown as DEMOD) of modem 254. Each modem 254 can use a corresponding demodulator component to condition (e.g., filter, amplify, downconvert, or digitize) the received signal to obtain an input sample. Each modem 254 can use the demodulator component to further process the input sample (e.g., for OFDM) to obtain a received symbol. MIMO detector 256 can obtain the received symbols from modem 254, perform MIMO detection on the received symbols where applicable, and provide the detected symbols. The receiver processor 258 can process (e.g., demodulate and decode) the detected symbols, provide the decoded data for UE 120 to data sink 260, and provide the decoded control and system information to controller / processor 280. The term "controller / processor" can refer to one or more controllers, one or more processors, or a combination thereof. The channel processor can determine Reference Signal Received Power (RSRP) parameters, Received Signal Strength Indicator (RSSI) parameters, Reference Signal Received Quality (RSRQ) parameters, or CQI parameters, etc. In some examples, one or more components of UE 120 may be included in housing 284.

[0096] The network controller may include a communication unit 294, a controller / processor 290, and a memory 292. The network controller may include, for example, one or more devices in the core network. The network controller may communicate with network node 110 via the communication unit 294.

[0097] One or more antennas (e.g., antennas 234a to 234t or antennas 252a to 252r) may include or be included in the following: one or more antenna panels, one or more antenna groups, one or more collections of antenna elements, or one or more antenna arrays, etc. Antenna panels, antenna groups, collections of antenna elements, or antenna arrays may include one or more antenna elements (within a single housing or multiple housings), coplanar antenna element collections, non-coplanar antenna element collections, or coupled to one or more transmitting or receiving components (such as...). FIG. 2 One or more antenna elements (one or more components).

[0098] On the uplink, at UE 120, transmit processor 264 can receive and process data from data source 262 and control information (e.g., for reports including RSRP, RSSI, RSRQ, or CQI) from controller / processor 280. Transmit processor 264 can generate reference symbols for one or more reference signals. Symbols from transmit processor 264 may be pre-decoded by TX MIMO processor 266 where applicable, further processed by modem 254 (e.g., for DFT-s-OFDM or CP-OFDM), and transmitted to network node 110. In some examples, modem 254 of UE 120 may include a modulator and demodulator. In some examples, UE 120 includes a transceiver. This transceiver may include any combination of antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, or TX MIMO processor 266. The transceiver may be used by a processor (e.g., controller / processor 280) and memory 282 to perform any aspect of the process described herein.

[0099] At network node 110, uplink signals from UE 120 or other UEs may be received by antenna 234, processed by modem 232 (e.g., demodulator component of modem 232, shown as DEMOD), detected by MIMO detector 236 where applicable, and further processed by receiver processor 238 to obtain decoded data and control information transmitted via UE 120. Receiver processor 238 may provide the decoded data to data sink 239 and the decoded control information to controller / processor 240. Network node 110 may include communication unit 244 and may communicate with network controller via communication unit 244. Network node 110 may include scheduler 246 to schedule one or more UEs 120 for downlink or uplink communication. In some examples, modem 232 of network node 110 may include modulator and demodulator. In some examples, network node 110 includes transceiver. The transceiver may include any combination of antenna 234, modem 232, MIMO detector 236, receive processor 238, transmit processor 220, or TX MIMO processor 230. The transceiver may be used by a processor (e.g., controller / processor 240) and memory 242 to perform aspects of any of the processes described herein.

[0100] The controller / processor of the network entity (e.g., controller / processor 240 of network node 110, controller / processor 290 of network node 130), controller / processor 280 of UE 120, and / or FIG. 2Any other component may perform one or more technologies associated with the use of services via the user plane, as described in more detail elsewhere herein. For example, the controller / processor 240 of network node 110, the controller / processor 290 of network node 130, the controller / processor 280 of UE 120, and / or FIG. 2 Any other component that can be executed or bootstrap, for example FIG. 26 Method 2600 FIG. 27 Method 2700 FIG. 28 Method 2800 FIG. 29 The operation of method 2900 and / or other processes as described herein. Memory 242, memory 292, and memory 282 may store data and program code for network node 110, core network node 130, and UE 120, respectively. In some examples, memory 242, memory 292, and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions (e.g., code and / or program code) for wireless communication. For example, these one or more instructions may cause the one or more processors, UE 120, core network node 130, and / or network node 110 to execute or bootstrap, for example, when executed by one or more processors of network node 110, core network node 130, and / or UE 120 (e.g., directly executed, or executed after compilation, transformation, and / or interpretation). FIG. 26 Method 2600 FIG. 27 Method 2700 FIG. 28 Method 2800 FIG. 29 Method 2900 and / or other procedures as described herein. In some examples, execution instructions may include run instructions, transformation instructions, compilation instructions, and / or interpretation instructions, etc.

[0101] In some aspects, the UE (e.g., UE 120) includes: components for selecting services provided via the control plane; components for transmitting a message including an indication of the service and the UE ID of the UE; and / or components for receiving configurations for the service. Components for enabling the UE to perform the operations described herein may include, for example, one or more of the following: a communication manager 140, an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, a TX MIMO processor 266, a controller / processor 280, or a memory 282.

[0102] In some aspects, the first network entity (e.g., network node 110) includes: components for receiving a message from a UE, the message including an indication of a service provided through the control plane and the UE's UE ID; and / or components for forwarding the message to an address of the service, at least in part based on the indication of the service. In some aspects, components for the first network entity to perform the operations described herein may include, for example, one or more of a communication manager 150, a transmit processor 220, a TX MIMO processor 230, a modem 232, an antenna 234, a MIMO detector 236, a receive processor 238, a controller / processor 240, a memory 242, or a scheduler 246.

[0103] In some aspects, the second network entity (e.g., core network node 130) includes: components for receiving service selection information associated with a service from the first network entity; and / or components for sending a service ID associated with the service to the first network entity. In some aspects, the components for enabling the second network entity to perform the operations described herein may include one or more of, for example, a communication manager 160, a controller / processor 290, a memory 292, or a communication unit 294.

[0104] In some aspects, the network entity (e.g., core network node 130) includes: components for receiving messages including indications of services provided through the control plane and the UE's UE ID; and / or components for transmitting configurations for those services. In some aspects, the components for enabling the second network entity to perform the operations described herein may include, for example, one or more of a communication manager 160, a controller / processor 290, a memory 292, or a communication unit 294.

[0105] In some aspects, the UE (e.g., UE 120) includes: components for selecting a user plane for service; and components for sending a request for service via the user plane. Components for enabling the UE to perform the operations described herein may include one or more of the following: a communication manager 140, an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, a TX MIMO processor 266, a controller / processor 280, or a memory 282.

[0106] In some aspects, a network entity (e.g., core network node 130) includes: components for receiving requests for services via the user plane; and / or components for sending a response indicating that the service will be transmitted via the user plane. In some aspects, components for enabling the network entity to perform the operations described herein may include, for example, one or more of a communication manager 150, a transmit processor 220, a TX MIMO processor 230, a modem 232, an antenna 234, a MIMO detector 236, a receive processor 238, a controller / processor 240, a memory 242, or a scheduler 246.

[0107] In some respects, a single processor can perform all the functions described as being performed by that one or more processors. In other respects, the one or more processors can jointly perform a set of functions. For example, a first group(s) of the one or more processors can perform a first function described as being performed by that one or more processors, and a second group(s) of the one or more processors can perform a second function described as being performed by that one or more processors. The first group and the second group of processors can be the same group of processors or can be different groups of processors. The reference to "one or more processors" should be understood as referring to a combination of functions. FIG. 2 Any one or more processors described. The reference to "one or more memories" should be understood to refer to any one or more memories of the corresponding device, such as those in conjunction with... FIG. 2 The memory described. For example, a function described as being performed by one or more memories can be performed by the same subset of the one or more memories or by different subsets of the one or more memories.

[0108] Although FIG. 2 The boxes in the diagram are illustrated as different components, but the functions described above with respect to these boxes may be implemented in a single hardware, software, or combined component, or in various combinations of components. For example, the functions described with respect to transmit processor 264, receive processor 258, and / or TX MIMO processor 266 may be performed by or under the control of controller / processor 280.

[0109] As indicated above, FIG. 2 This is provided as an example. Other examples are available with reference to [the relevant information]. FIG. 2 The examples described are different.

[0110] Communication systems (such as 5G NR systems) can be deployed in various ways using a variety of components or parts. In a 5G system or network, network nodes, network entities, network mobility elements, RAN nodes, core network nodes, network elements, base stations, or network equipment can be implemented in aggregated or decomposed architectures. For example, a base station (such as a Node B (NB), evolved NB (eNB), NR base station, 5G NB, access point (AP), TRP, or cell, etc.) or one or more units (or components) performing base station functionality can be implemented as an aggregated base station (also known as a standalone base station or monolithic base station) or a decomposed base station. A “network entity” or “network node” can refer to a decomposed base station or one or more units of a decomposed base station (such as one or more CUs, one or more DUs, one or more RUs, or combinations thereof).

[0111] Aggregated base stations (e.g., aggregated network nodes) can be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node (e.g., within a single device or cell). Decomposed base stations (e.g., decomposed network nodes) can be configured to utilize a protocol stack that is physically or logically distributed across two or more cells (such as one or more CUs, one or more DUs, or one or more RUs). In some examples, the CU may be implemented within a network node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed across one or more other network nodes. DUs may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU can also be implemented as a virtual cell, such as a Virtual Central Unit (VCU), a Virtual Distributed Unit (VDU), or a Virtual Radio Unit (VRU), etc.

[0112] Base station type operation or network design can take into account the aggregation characteristics of base station functionality. For example, decomposed base stations can be utilized in IAB networks, Open Radio Access Networks (O-RAN (such as network configurations initiated by the O-RAN Alliance)), or Virtualized Radio Access Networks (vRAN, also known as Cloud Radio Access Networks (C-RAN)) to facilitate the scaling of communication systems by separating base station functionality into one or more units that can be deployed independently. Decomposed base stations can include functionality implemented across two or more units at various physical locations, as well as functionality virtually implemented for at least one unit, which enables flexibility in network design. Each unit of a decomposed base station can be configured for wired or wireless communication with at least one other unit of the decomposed base station.

[0113] FIG. 3This is an illustration of an example decomposed base station architecture 300. The decomposed base station architecture 300 may include a CU 310, which may communicate directly with the core network 320 via a backhaul link, or indirectly with the core network 320 via one or more decomposed control units (such as near-RT RIC 325 via an E2 link, or a non-RT RIC 315 associated with a Service Management and Orchestration (SMO) framework 305, or both). The CU 310 may communicate with one or more DUs 330 via a corresponding midhaul link (such as via an F1 interface). Each DU 330 may communicate with one or more RUs 340 via a corresponding fronthaul link. Each RU 340 may communicate with one or more UEs 120 via a corresponding radio frequency (RF) access link. In some implementations, a UE 120 may be served simultaneously by multiple RUs 340.

[0114] Each unit in the clusters (including CU 310, DU 330, RU 340), as well as the near-RT RIC 325, non-RT RIC 315, and SMO frame 305, may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via wired or wireless transmission media. Each unit in the cluster, or an associated processor or controller providing instructions to one or more communication interfaces of the corresponding unit, may be configured to communicate with one or more units in other clusters via transmission media. In some examples, each unit in the cluster may include a wired interface and a wireless interface configured to receive signals or transmit signals to one or more units in other clusters via a wired transmission media, and the wireless interface may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive signals or transmit signals to one or more units in other clusters via a wireless transmission media, or both.

[0115] In some aspects, the CU 310 can host one or more higher-level control functions. Such control functions may include RRC functions, Packet Data Convergence Protocol (PDCP) functions, or Service Data Adaptation Protocol (SDAP) functions, etc. Each control function can be implemented using an interface configured to signal to other control functions hosted by the CU 310. The CU 310 can be configured to handle user plane functions (e.g., Central Unit-User Plane (CU-UP) functions), control plane functions (e.g., Central Unit-Control Plane (CU-CP) functions), or combinations thereof. In some implementations, the CU 310 can be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units can communicate bidirectionally with the CU-CP units via an interface such as an E1 interface. The CU 310 can be implemented to communicate with the DU330 for network control and signaling purposes, as needed.

[0116] Each DU 330 may correspond to a logical unit comprising one or more base station functions for controlling the operation of one or more RU 340s. In some aspects, the DU 330 may host one or more of the Radio Link Control (RLC) layer, Medium Access Control (MAC) layer, and one or more high physical (PHY) layers, at least in part, according to functional splits (such as those defined by 3GPP). In some aspects, the one or more high PHY layers may be implemented by one or more modules for forward error correction (FEC) encoding and decoding, scrambling, and modulation and demodulation, etc. In some aspects, the DU 330 may also host one or more low PHY layers, such as those implemented by one or more modules for Fast Fourier Transform (FFT), Inverse FFT (iFFT), Digital Beamforming, or Physical Random Access Channel (PRACH) extraction and filtering, etc. Each layer (which may also be referred to as a module) may be implemented using an interface configured to communicate signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.

[0117] Each RU 340 can implement low-level functionality. In some deployments, an RU 340 controlled by a DU 330 can correspond to a logical node that hosts RF processing functions or low-PHY layer functions, such as performing FFT, performing iFFT, digital beamforming, or PRACH extraction and filtering, based on function splitting (e.g., function splitting defined by 3GPP) (such as low-level function splitting). In such architectures, each RU 340 can be operated to handle over-the-air (OTA) communications with one or more UEs 120. In some specific implementations, the real-time and non-real-time aspects of control plane and user plane communications with the RU 340 can be controlled by the corresponding DU 330. In some scenarios, this configuration allows each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0118] The SMO framework 305 can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 305 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via operation and maintenance interfaces such as the O1 interface. For virtualized network elements, the SMO framework 305 can be configured to interact with cloud computing platforms such as the Open Cloud (O-Cloud) platform 390 to perform network element lifecycle management (such as instantiating virtualized network elements) via cloud computing platform interfaces such as the O2 interface. Such virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, non-RT RIC 315, and near-RTTRIC 325. In some specific implementations, the SMO framework 305 may communicate with 4G RAN hardware aspects such as the Open eNB (O-eNB) 311 via the O1 interface. Additionally, in some implementations, the SMO framework 305 can communicate directly with each of one or more RUs 340 via a corresponding O1 interface. The SMO framework 305 may also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305.

[0119] The non-RT RIC 315 can be configured to include logical functions that enable non-real-time control and optimization of RAN elements and resources, including AI / ML workflows for model training and updates, or policy-based guidance for applications / features in the near-RT RIC 325. The non-RT RIC 315 can be coupled to or communicate with the near-RT RIC 325, such as via an A1 interface. The near-RT RIC 325 can be configured to include logical functions that enable near real-time control and optimization of RAN elements and resources via an interface, such as an E2 interface, through data collection and action, connecting one or more CU 310s, one or more DU 330s, or both, and O-eNBs to the near-RT RIC 325.

[0120] In some implementations, to generate AI / ML models to be deployed in the near-RT RIC 325, the non-RT RIC 315 may receive parameters or external enrichment information from an external server. This information can be utilized by the near-RT RIC 325 and can be received from non-network data sources or network functions at the SMO framework 305 or the non-RT RIC 315. In some examples, the non-RT RIC 315 or the near-RT RIC 325 may be configured to regulate RAN behavior or performance. For example, the non-RT RIC 315 may monitor long-term trends and patterns in performance and employ AI / ML models to perform corrective actions via the SMO framework 305 (such as reconfiguration via the O1 interface) or via the creation of RAN management policies (such as A1 interface policies).

[0121] As indicated above, FIG. 3 This is provided as an example. Other examples are available with reference to [the relevant information]. FIG. 3 The examples described are different.

[0122] FIG. 4 This is a diagram of an example 400 of a core network 405 configured to provide network slicing. (See diagram for example.) FIG. 4 As shown, Example 400 may include UE 120, wireless communication network 100, and core network 405. The devices and / or networks of Example 400 may be interconnected via wired connections, wireless connections, or a combination thereof.

[0123] For example, wireless communication network 100 may support cellular RAT. Network 100 may include one or more network nodes, such as base stations (e.g., base transceivers, radio base stations, Node Bs, eNodeBs (eNBs), gNodeBs (gNBs), base station subsystems, cellular sites, cellular towers, access points, TRPs, radio access nodes, macrocell base stations, microcell base stations, picocell base stations, femtocell base stations, or similar devices) and other network nodes that can support wireless communication for UE 120. Network 100 may deliver services between UE 120 (e.g., using a cellular RAT), one or more network nodes (e.g., using a radio interface or backhaul interface, such as a wired backhaul interface) and / or core network 405. Network 100 may provide one or more cells covering a geographic area.

[0124] In some aspects, the wireless communication network 100 may perform scheduling and / or resource management for UE 120 covered by the network 100 (e.g., UE 120 with cell coverage provided by the network 100). In some aspects, the network 100 may be controlled or coordinated by a network controller, which may perform load balancing and / or network-level configuration, etc., as described above. FIG. 1 As described, the network controller can communicate with network 100 via wireless or wired backhaul. In some aspects, network 100 may include a network controller, an ad hoc network (SON) module or component, or a similar module or component. Therefore, network 100 can perform network control, scheduling, and / or network management functions (e.g., for uplink, downlink, and / or sidelink communication of UE 120 covered by network 100).

[0125] In some aspects, core network 405 may include example functional architectures in which the systems and / or methods described herein can be implemented. For example, core network 405 may include example architectures of 5G next-generation (NG) core networks included in fifth-generation (5G) wireless telecommunications systems. Although FIG. 4 The example architecture of the core network 405 shown can be an example of a service-based architecture, but in some respects, the core network 405 can be implemented as a reference point architecture and / or a 4G core network, etc.

[0126] like FIG. 4As shown, the core network 405 may include multiple functional elements. These functional elements may include, for example, a network slice selection function (NSSF) 410, a network open function (NEF) 415, an authentication server function (AUSF) 420, a unified data management (UDM) component 425, a policy control function (PCF) 430, an application function (AF) 435, an access and mobility management function (AMF) 440, a session management function (SMF) 445, and / or a user plane function (UPF) 450, etc. These functional elements may be communicatively connected via a message bus 455. FIG. 4 Each of the functional elements shown can be implemented on one or more devices associated with a wireless telecommunications system. In some implementations, one or more of these functional elements can be implemented on physical devices such as access points, base stations, and / or gateways. In some implementations, one or more of these functional elements can be implemented on computing devices in a cloud computing environment.

[0127] NSSF 410 may include one or more devices for selecting network slice instances for UE 120. A network slice is a network architecture model in which logically distinct network slices operate using a common network infrastructure. For example, several network slices may operate as isolated end-to-end networks customized to meet different target service standards for different types of applications and / or communications to and from UE 120, which are at least partially performed by UE 120. Network slicing efficiently provides communication for different types of services with different service standards.

[0128] The NSSF 410 determines a set of network slicing policies to be applied at the wireless communication network 100. For example, the NSSF 410 can apply one or more UE routing policy (URSP) rules. In some aspects, the NSSF 410 can select network slices based on a mapping from the Data Network Name (DNN) field included in the Routing Description (RSD) to the DNN field included in the Service Descriptor selected by the UE 120. By providing network slices, the NSSF 410 allows operators to potentially deploy multiple substantially independent end-to-end networks over the same infrastructure. In some implementations, each slice can be customized for a different service.

[0129] NEF 415 may include one or more devices that support the opening of capabilities and / or events in a wireless telecommunications system to help other entities in the wireless telecommunications system discover network services. AUSF 420 may include one or more devices that act as an authentication server and support the process of authenticating UE 120 in a wireless telecommunications system.

[0130] The UDM 425 may include one or more devices for storing user data and profiles in a wireless telecommunications system. In some respects, the UDM 425 may be used for fixed access and / or mobile access, etc., in the core network 405.

[0131] PCF 430 may include one or more devices that provide a policy framework that incorporates network slicing, roaming, packet processing, and / or mobility management, among other things. In some aspects, PCF 430 may include one or more URSP rules used by NSSF 410 to select network slice instances for UE 120.

[0132] AF 435 may include one or more devices that support the impact of applications on service routing, access to NEF 415, and / or policy control, etc. AMF 440 may include one or more devices that act as an endpoint for NAS signaling and / or mobility management, etc. In some aspects, AMF may request NSSF 410 to select a network slice instance for UE 120, for example, at least in part in response to a request for data services from UE 120.

[0133] The SMF 445 may include one or more devices that support the establishment, modification, and release of communication sessions in a wireless telecommunications system. For example, the SMF 445 may configure service bootstrapping policies at the UPF 450 and / or enforce UE Internet Protocol (IP) address allocation and policies, etc. In some respects, the SMF 445 may supply the UE 120 with network slice instances selected by the NSSF 410.

[0134] UPF 450 may include one or more devices that act as anchors for mobility within and / or between RATs. In some respects, UPF 450 may apply rules to packets, such as rules relating to packet routing, traffic reporting, and / or handling of user plane quality of service (QoS).

[0135] The message bus 455 can be a logical communication structure and / or a physical communication structure for communication between functional elements. Therefore, the message bus 455 can allow communication between two or more functional elements, whether logically (e.g., using one or more application programming interfaces (APIs) and / or physically (e.g., using one or more wired and / or wireless connections).

[0136] FIG. 4 The number and arrangement of devices and networks shown are provided as an example. In practice, there may be different arrangements. FIG. 4 The devices and / or networks shown are compared to additional devices and / or networks, fewer devices and / or networks, different devices and / or networks, or devices and / or networks arranged in a different manner. Furthermore,FIG. 4 The two or more devices shown can be implemented within a single device, or FIG. 4 The single device shown can be implemented as multiple distributed devices. Additionally or alternatively, the set of devices in Example 400 (e.g., one or more devices) can perform one or more functions described as being performed by another set of devices in Example Environment 400.

[0137] Although FIG. 4 The components of a 5G network are described, but such components may be included in 6G networks and even more advanced networks.

[0138] As indicated above, FIG. 4 This is provided as an example. Other examples are available with reference to [the relevant information]. FIG. 4 The examples described are different.

[0139] FIG. 5 This is a diagram illustrating example 500 of network node 110 and the user plane protocol stack and control plane protocol stack of the core network used for communication with UE 120.

[0140] In some aspects, network node 110 may include multiple network nodes 110. In some aspects, the protocol stack functionality of network node 110 may be distributed across multiple network nodes 110. For example, a first network node 110 may implement a first layer of the protocol stack, and a second network node 110 may implement a second layer of the protocol stack. The distribution of the protocol stack across network nodes (in this example of the distribution of the protocol stack across network nodes) may be based at least in part on functional partitioning, as described elsewhere herein. It should be understood that, in some aspects, the reference to “network node 110” may refer to multiple network nodes.

[0141] On the user plane, UE 120 and network node 110 may include corresponding PHY, MAC, RLC, PDCP, and SDAP layers. User plane functions handle the transmission of user data between UE 120 and network node 110. On the control plane, UE 120 and network node 110 may include corresponding RRC layers. Additionally, UE 120 may include a NAS layer that communicates with the AMF's NAS layer. The AMF may be associated with a core network (such as a 5G core network (5GC), 6G core network, or NG-RAN) associated with network node 110. Control plane functions handle the transmission of control information between the UE and the core network. Generally, if a first layer is further from the PHY layer than a second layer, the first layer is referred to as being higher than the second layer. For example, the PHY layer may be referred to as the lowest layer, and the SDAP / PDCP / RLC / MAC layers may be referred to as being higher than the PHY layer and lower than the RRC layer. FIG. 5The Application (APP) layer, not shown, may be higher than the SDAP / PDCP / RLC / MAC layers. In some cases, an entity may handle the services and functions of a given layer (e.g., a PDCP entity may handle the services and functions of the PDCP layer), although the description herein mentions that the layer itself handles these services and functions.

[0142] The RRC layer handles communications related to the configuration and operation of UE 120, such as: broadcasting system information related to the Access Layer (AS) and NAS; paging initiated by 5GC or NG-RAN; establishment, maintenance, and release of RRC connections between the UE and NG-RAN, including the addition, modification, and release of carrier aggregation, as well as the addition, modification, and release of dual connections; security functions, including key management; establishment, configuration, maintenance, and release of Signaling Radio Bearers (SRBs) and Data Radio Bearers (DRBs); mobility functions (e.g., handover and context passing, UE cell selection and reselection and control of cell selection and reselection, inter-RAT mobility); QoS management functions; UE measurement reporting and control of reports; detection and recovery from radio link failures; and NAS messaging between the NAS layer and the lower layers of UE 120. The RRC layer is often referred to as Layer 3 (L3).

[0143] The SDAP, PDCP, RLC, and MAC layers can be collectively referred to as Layer 2 (L2). Therefore, in some cases, the SDAP, PDCP, RLC, and MAC layers are referred to as sublayers of Layer 2. On the transmitting side (e.g., if UE 120 is transmitting uplink communication or network node 110 is transmitting downlink communication), the SDAP layer can receive data streams in the form of QoS streams. A QoS stream is associated with a QoS identifier and a QoS stream identifier (QFI), the QoS identifier identifying the QoS parameters associated with the QoS stream and the QoS stream identifier (QFI) identifying the QoS stream. Policies and charging parameters are implemented according to the QoS stream granularity. A QoS stream may include one or more Service Data Streams (SDFs), provided that each SDF of the QoS stream is associated with the same policies and charging parameters. In some aspects, the RRC / NAS layer can generate control information to be transmitted and can map this control information to one or more radio bearers for provision to the PDCP layer.

[0144] The SDAP or RRC / NAS layer can map QoS flows or control information to radio bearers. Therefore, it can be said that the SDAP layer handles QoS flows on the transmitting side. The SDAP layer can provide QoS flows to the PDCP layer via the corresponding radio bearer. The PDCP layer can map radio bearers to RLC channels. The PDCP layer handles various services and functions on the user plane, including sequence numbering, header compression and decompression (if robust header compression is enabled), delivery of user data, reordering and replication detection (if required for in-order delivery to layers above the PDCP layer), PDCP Protocol Data Unit (PDU) routing (in the case of split bearers), retransmission, encryption and decryption of PDCP Service Data Units (SDUs), PDCP SDU discarding (e.g., according to timers, as described elsewhere in this document), PDCP reconstruction and data recovery for RLC Acknowledgment Mode (AM), and replication of PDCP PDUs. The PDCP layer handles similar services and functions on the control plane, including sequence numbering, encryption, decryption, integrity protection, delivery of control plane data, replication detection, and replication of PDCP PDUs.

[0145] The PDCP layer can provide data in the form of PDCP PDUs to the RLC layer via the RLC channel. The RLC layer can handle the transmission of upper-layer PDUs to the MAC and / or PHY layers, sequence numbering independent of PDCP sequence numbering, error correction via Automatic Repeat Request (ARQ), segmentation and resegmentation, SDU reassembly, RLC SDU discarding, and RLC reconstruction.

[0146] The RLC layer can provide the MAC layer with data mapped to logical channels. The services and functions of the MAC layer include mapping between logical channels and transport channels (used by the PHY layer as described below), multiplexing MACSDUs belonging to one or different logical channels into / from a transport block (TB) delivered to / from the physical layer on the transport channel, scheduling information reporting, error correction via Hybrid ARQ (HARQ), priority handling between UEs via dynamic scheduling, priority handling between logical channels of a UE via logical channel prioritization, and padding.

[0147] The MAC layer can encapsulate data from logical channels into data blocks (TBs) and can provide TBs to the PHY layer on one or more transport channels. The PHY layer can handle various operations related to the transmission of data signals, such as combining... FIG. 2 In more detail, the PHY layer is often referred to as layer 1 (L1).

[0148] On the receiving side (e.g., if UE 120 is receiving downlink communication or network node 110 is receiving uplink communication), the operation can be similar to that described for the transmitting side, but in the reverse direction. For example, the PHY layer can receive the transport layer (TB) and provide the TB to the MAC layer on one or more transport channels. The MAC layer can map the transport channels to logical channels and provide data to the RLC layer via the logical channels. The RLC layer can map the logical channels to RLC channels and provide data to the PDCP layer via the RLC channels. The PDCP layer can map the RLC channels to radio bearers and provide data to the SDAP layer or RRC / NAS layer via the radio bearers.

[0149] Data can be transferred between layers in the form of PDUs and SDUs. An SDU is a data unit that has been passed from a layer or sublayer to the next layer. For example, the PDCP layer can receive PDCP SDUs. A given layer can then encapsulate the data unit into a PDU and pass the PDU to the next layer. For example, the PDCP layer can encapsulate a PDCP SDU into a PDCP PDU and pass the PDCP PDU to the RLC layer. The RLC layer can receive the PDCP PDU as an RLC SDU, encapsulate the RLC SDU into an RLC PDU, and so on. In effect, the PDU carries the SDU as a payload.

[0150] As indicated above, FIG. 5 This is provided as an example. Other examples are available with reference to [the relevant information]. FIG. 5 The examples described are different.

[0151] FIG. 6 This is a diagram illustrating example 600 of the design model.

[0152] In the early days of the Internet, data networks were established to provide numerous services through heterogeneous devices. One design principle illustrated by data network model 602 includes a layered system architecture with simple service interfaces spanning many applications and transports. Data network model 602 resembles an hourglass, with an IP layer in the middle that allows routing protocols to be placed on top of any type of interface. Different transmission or service types can run on this interface.

[0153] With the advent of cellular radio networks (such as 3G and 4G), the hourglass aspect of data network model 602, as shown in cellular network model 604, was adopted. With the introduction of smartphones, 4G successfully provided many services. The 4G protocol stack was designed to support the same model as the Internet but used for cellular radio networks. This involves a separate control plane to manage data transmission for cellular needs such as mobility. The separate control plane protocol stack and user plane protocol stack continue the architecture defined for 3G.

[0154] With the expansion of 4G, new features were introduced to extend the system's capabilities to new use cases and device types. This includes horizontal expansion (carrier aggregation (CA), dual connectivity (DC), etc.) and vertical expansion (IoT, V2X, etc.). The success of 4G helped activate expectations for 5G vertical industries. Additionally, services were introduced into the protocol stack as part of NAS / RRC protocols. NAS protocol services include location. RRC protocol services include data collection, such as Minimum Drive Test (MDT). In addition to data transmission and connectivity, additional services provided by NAS and / or RRC include positioning, sensing, timing, AI / ML, etc. The adoption of such NAS / RRC services is limited. Deploying new services without upgrading the underlying protocols is not feasible. Adding services via the control plane is not as straightforward as enabling new services via IP.

[0155] As indicated above, FIG. 6 This is provided as an example. Other examples are available with reference to [the relevant information]. FIG. 6 The examples described are different.

[0156] FIG. 7 This is a diagram illustrating Example 700, a 5G design.

[0157] Example 700 illustrates a 5G network model 702 that can be deployed standalone or non-standalone, involving 4G. However, the 5G NAS / RRC protocol stack may be even more monolithic than in 4G. NAS / RRC continues to evolve to support even more features, such as industrial IoT, satellite, etc. Service revenue has been concentrated on the user plane due to continued support for legacy services from the 4G era. Historical data further indicates that the adoption of control plane services is limited. Differentiated services built on network slices already exist as potential features driving 5G standalone deployments. Policy and billing functions allow new revenue streams beyond data consumption.

[0158] The challenge lies in enabling services to be deployed independently, while making the most of existing protocols and allowing UEs to address services directly without relying on intermediate network functions (e.g., NAS signaling, RRC signaling). Furthermore, defining new data collection, location, or other protocols in 6G and each subsequent generation may not be optimal as we move to 6G.

[0159] As indicated above, FIG. 7 This is provided as an example. Other examples are available with reference to [the relevant information]. FIG. 7 The examples described are different.

[0160] FIG. 8 This is a diagram illustrating the new design of the network, example 800. (See diagram for example.) FIG. 8As shown, network entity 810 (e.g., network node 110) and UE 820 (e.g., UE 120) can communicate with each other via a wireless network (e.g., including elements of wireless communication network 100). This network can be a 5G network, a 6G network, a next-generation network, or a combination of such networks.

[0161] In some aspects, the new network design may involve no longer defining a G-specific control plane for each G, and no longer enabling the hourglass model on that control plane. This may include defining what is hosted in the control plane using a user plane-first approach. A thinner control plane for 6G allows control plane services to be available in 5G and other RATs. Control plane services, including location and data collection, can be made available via the user plane (e.g., based on address requests) and can become G-independent using standardized APIs. Services addressed and executed via the user plane may include data sessions, PDU sessions, sensing services, location services, policy services, UE device management, and / or policy downloads on the UE.

[0162] The new design leverages the scale of internet services and protocols to enable many potential vendors, rather than the limited number of infrastructure providers available today, to offer such services. The new design may include simplified ways to enable remaining services via NAS and RRC. The control plane does not need to be generation-specific, and NAS and RRC can be defined solely as the transport layer for services. Services can be decoupled from transport. For example, service interfaces can be enabled so that connectivity, session management, and other services are built on top of NAS and RRC rather than incorporated into the NAS protocol.

[0163] In some respects, the NAS layer can commonly span services. The NAS layer can provide service discovery, routing, and late binding. The transport layer can reside at the service entry point. The same transport layer can be used for both the user plane and control plane; from a protocol perspective, there is no difference. Services can be distinguished by service IDs. Reliability and security can be implemented at the transport / service layer or relocated according to service requirements. The microservices behind the service entry point can be transparent to other parts of the system, such as the UE. In some respects, the UE can use the service ID, NAS ID, paging ID, and / or RAN ID. The UE can use such IDs to directly address services via the user plane. The NAS / RRC layer can be used for authentication, some mobility services, and for setting up the user plane.

[0164] By using NAS protocols and RRC signaling as the transport / service layer operating on the user plane for setting up services, the adoption of services on the network can be scaled and new revenue streams can be created, while limiting the redefinition of the control plane with future generations.

[0165] Example 800 illustrates an example of a UE 820 requesting a service via the user plane. At 825, network entity 810 and UE 820 may configure the control plane (e.g., NAS protocol, RRC signaling) for services via the user plane. This may include configuring the NAS / RRC layer to operate as a transport for a service that may have been handled by the control plane in earlier network scenarios. The control plane configuration may involve authenticating the UE 820 requesting the service.

[0166] In some respects, at 830, UE 820 may select to request services using either the user plane or the control plane, at least in part, based on the network type. For example, if the network is 6G, UE 820 may select the user plane, or if the network is 5G, the UE may select the control plane. The selection between the user plane and the control plane may be based on the network connectivity (6G+ vs. 3G / 4G / 5G). The selection between the user plane and the control plane may be based at least in part on the service or service type. The selection between the user plane and the control plane may be based at least in part on UE configuration, user preferences, or service availability. The service may be a service type that is typically handled by the control plane, such as MDT or managed QoS. The service may be a service type carried by signaling radio in 5G. The service protocol may be unaffected by whether the transport is performed via the control plane or the user plane.

[0167] In some respects, the control plane can be a thinner control plane that provides fewer services, and those services are provided on the user plane. That is, some services on the control plane can be replaced by services on the user plane. Compared to the control plane used for 5G, the thinner control plane used for 6G can have fewer protocols or signaling.

[0168] At 835, if UE 820 selects the user plane, UE 820 may send a request for services via the user plane. This may include addressing the service using a user plane address. This may include using a service ID, RAN ID, and / or NAS ID. At 840, UE 820 may execute services via the user plane.

[0169] In some respects, UE 820 can use specific PDU sessions and / or dedicated physical resource blocks (PRBs) that provide higher priority on the user plane to prevent the increase in latency from exceeding the latency expected on the control plane.

[0170] As indicated above, FIG. 8 This is provided as an example. Other examples are available with reference to [the relevant information]. FIG. 8 The descriptions are different.

[0171] FIG. 9 This is a flowchart of an example method 900 for wireless communication. Method 900 may be performed at, for example, a UE (e.g., UE 120, UE 820) or a device of the UE.

[0172] At 910, the UE can select the user plane for service. For example, the UE (e.g., using communication manager 140 and / or FIG. 11 The selection component 1108 described above can be used to select the user face for the service, as in conjunction with, for example, the user face for the service. FIG. 5 and FIG. 8 As described.

[0173] At 920, the UE can send a request for services via the user plane. For example, the UE (e.g., using communication manager 140 and / or FIG. 11 The described sending component 1104 can send requests for services via the user plane, as described above in conjunction with, for example... FIG. 5 and FIG. 8 As described.

[0174] In some aspects, selecting the user plane involves choosing between the user plane and the control plane. In some aspects, selecting the user plane involves choosing between the user plane and the control plane based at least in part on the generation of network connectivity. In some aspects,

[0175] In some respects, method 900 includes using services via the user plane. The service protocol may be unaffected by whether the transport is conducted via the control plane or the user plane.

[0176] In some aspects, services via the user plane use protocol data unit sessions specific to that service via the user plane. In some aspects, services via the user plane use frequency resources specific to that service via the user plane and having a priority associated with that service via the user plane. In some aspects, services via the user plane include quality of service management services. In some aspects, services via the user plane include mobility services. In some aspects, services via the user plane include minimized drive test services. In some aspects, services via the user plane include routing services. In some aspects, services via the user plane include services associated with the connection between the UE and access and mobility functions in the core network.

[0177] although FIG. 9 An example box of method 900 is shown, but in some respects, method 900 may include... FIG. 9 The boxes depicted may be fewer, different, or arranged differently compared to additional boxes. Alternatively, two or more boxes in the box of method 900 may be executed in parallel.

[0178] FIG. 10 This is a flowchart of an example method 1000 for wireless communication. Method 1000 may be performed at, for example, a network entity (e.g., network node 110, network entity 810) or a device of a network entity.

[0179] At point 1010, the network entity can receive requests for services via the user plane. For example, the network entity (e.g., using communication manager 150 and / or...) FIG. 13 The described receiving component 1302 can receive requests for services via the user plane, as described above in conjunction with, for example... FIG. 5 and FIG. 8 As described.

[0180] At point 1020, the network entity can send an indication that the service will be delivered via the user plane. For example, the network entity (e.g., using communication manager 150 and / or...) FIG. 13 The described sending component 1304 can send a response indicating that the service will be transmitted through the user plane, as described above in conjunction with, for example... FIG. 5 and FIG. 8 As described.

[0181] In some respects, the service is decoupled from the transport layer. In some respects, method 1000 includes using a control plane to authenticate the service and facilitate the operation of the service through the user plane.

[0182] although FIG. 10 An example box of method 1000 is shown, but in some aspects, method 1000 may include... FIG. 10 The boxes depicted may be fewer, different, or arranged differently compared to additional boxes. Alternatively, two or more boxes in the boxes of method 1000 may be executed in parallel.

[0183] FIG. 11 This is a diagram of an example device 1100 for wireless communication. Device 1100 may be a UE, or a UE may include device 1100. In some aspects, device 1100 includes a receiving component 1102 and a transmitting component 1104, which can communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, device 1100 can use the receiving component 1102 and the transmitting component 1104 to communicate with another device 1106 (such as a UE, a base station, or another wireless communication device). As further shown, device 1100 may include a communication manager 140. Communication manager 140 may select component 1108 and / or service component 1110, etc.

[0184] In some respects, device 1100 can be configured to perform the functions described herein. FIG. 1 to FIG. 8 The described one or more operations. Additionally or alternatively, the apparatus 1100 may be configured to perform one or more processes described herein, such as FIG. 9 Method 900. In some respects, FIG. 11 The illustrated device 1100 and / or one or more components may include a combination FIG. 2One or more components of the described UE. Additionally or alternatively, FIG. 11 One or more components shown can be combined FIG. 2 Implementation within one or more of the described components. Additionally or alternatively, one or more components in the set of components may be implemented at least partially as software stored in one or more memories. For example, a component (or a portion thereof) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by one or more controllers or one or more processors to perform the function or operation of the component.

[0185] Receiver 1102 may receive communications from device 1106, such as reference signals, control information, data communications, or combinations thereof. Receiver 1102 may provide the received communications to one or more other components of device 1100. In some aspects, receiver 1102 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) and may provide the processed signals to one or more other components of device 1100. In some aspects, receiver 1102 may include combinations of... FIG. 2 The described UE includes one or more antennas, one or more modems, one or more demodulators, one or more MIMO detectors, one or more receiver processors, one or more controllers / processors, one or more memories, or combinations thereof.

[0186] Transmitting component 1104 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1106. In some aspects, one or more other components of device 1100 may generate communications and provide the generated communications to transmitting component 1104 for transmission to device 1106. In some aspects, transmitting component 1104 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to device 1106. In some aspects, transmitting component 1104 may include combinations of... FIG. 2 The described UE may include one or more antennas, one or more modems, one or more modulators, one or more transmit MIMO processors, one or more transmit processors, one or more controllers / processors, one or more memories, or combinations thereof. In some aspects, the transmit component 1104 may co-located with the receive component 1102 in one or more transceivers.

[0187] Select component 1108 allows you to select the user plane for the service. Send component 1104 allows you to send a request for the service via the user plane. Service component 1110 can use the service via the user plane.

[0188] FIG. 11 The number and arrangement of components shown are provided as an example. In practice, different arrangements may exist. FIG. 11 The components shown are compared to additional components, fewer components, different components, or components arranged in a different manner. Furthermore, FIG. 11 The two or more components shown can be implemented within a single component, or FIG. 11 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, FIG. 11 The set (one or more) components shown are executable descriptions by FIG. 11 The other set of components shown performs one or more functions.

[0189] FIG. 12 This is an illustration of an example 1200 of a hardware implementation of a device 1205 employing a processing system 1210. The device 1205 may be a UE or may be located at a UE (e.g., included in a UE).

[0190] Processing system 1210 may be implemented using a bus architecture generally represented by bus 1215. Bus 1215 may include any number of interconnect buses and bridges, depending on the specific application of processing system 1210 and overall design constraints. Bus 1215 links together various circuits including one or more processors and / or hardware components represented by processor 1220, illustrated components, and computer-readable medium / memory 1225. Bus 1215 may also link various other circuits, such as timing sources, peripheral devices, voltage regulators, and / or power management circuits.

[0191] Processing system 1210 may be coupled to one or more transceivers 1230. Transceiver 1230 is coupled to one or more antennas 1235. Transceiver 1230 provides components for communicating with various other devices via a transmission medium. Transceiver 1230 receives signals from one or more antennas 1235, extracts information from the received signals, and provides the extracted information to processing system 1210 (specifically, receiving component 1102). Furthermore, transceiver 1230 receives information from processing system 1210 (specifically, transmitting component 1104) and generates signals to be applied to one or more antennas 1235 based at least in part on the received information.

[0192] Processing system 1210 includes one or more processors 1220 coupled to computer-readable medium / memory 1225. Processor 1220 is responsible for general processing, including executing software stored on computer-readable medium / memory 1225. When executed by processor 1220, the software causes processing system 1210 to perform the various functions described herein with respect to any particular device. Computer-readable medium / memory 1225 can also be used to store data manipulated by processor 1220 during software execution. The processing system also includes at least one of the illustrated components. These components may be software modules running in processor 1220, residing in / stored on computer-readable medium / memory 1225, one or more hardware modules coupled to processor 1220, or some combination thereof.

[0193] In some aspects, processing system 1210 may be a component of UE 120 and may include one or more memories (such as memory 282) and / or may include one or more processors (such as at least one of TX MIMO processor 266, RX processor 258, and / or controller / processor 280). In some aspects, apparatus 1205 for wireless communication includes components for selecting a user plane for service and components for sending a request for service via the user plane. The aforementioned components may be one or more of the aforementioned components of apparatus 1100 and / or processing system 1210 of apparatus 1205 configured to perform the functions stated by the aforementioned components. As described elsewhere herein, processing system 1210 may include TX MIMO processor 266, RX processor 258, and / or controller / processor 280. In one configuration, the aforementioned components may be TX MIMO processor 266, RX processor 258, and / or controller / processor 280 configured to perform the functions and / or operations stated herein.

[0194] FIG. 12 This is provided as an example. Other examples can be combined with it. FIG. 12 The examples described are different.

[0195] FIG. 13This is a diagram of an example device 1300 for wireless communication. Device 1300 may be a network entity, or a network entity may include device 1300. In some aspects, device 1300 includes a receiving component 1302 and a transmitting component 1304, which can communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, device 1300 can use the receiving component 1302 and the transmitting component 1304 to communicate with another device 1306 (such as a UE, a base station, or another wireless communication device). As further shown, device 1300 may include a communication manager 150. Communication manager 150 may include a service component 1308 and / or an authentication component 1310, etc.

[0196] In some respects, device 1300 can be configured to perform the functions described herein. FIG. 1 to FIG. 8 One or more operations described herein. Additionally or alternatively, the apparatus 1300 may be configured to perform one or more processes described herein, such as FIG. 10 Method 1000. In some respects, FIG. 13 The illustrated device 1300 and / or one or more components may include a combination FIG. 2 One or more components of the described network entity. Additionally or alternatively, FIG. 13 One or more components shown can be combined FIG. 2 Implementation within one or more of the described components. Additionally or alternatively, one or more components in the set of components may be implemented at least partially as software stored in one or more memories. For example, a component (or a portion thereof) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by one or more controllers or one or more processors to perform the function or operation of the component.

[0197] Receiver 1302 may receive communications from device 1306, such as reference signals, control information, data communications, or combinations thereof. Receiver 1302 may provide the received communications to one or more other components of device 1300. In some aspects, receiver 1302 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) and may provide the processed signals to one or more other components of device 1300. In some aspects, receiver 1302 may include combinations of... FIG. 2 The described network entity includes one or more antennas, one or more modems, one or more demodulators, one or more MIMO detectors, one or more receiver processors, one or more controllers / processors, one or more memories, or combinations thereof.

[0198] Transmitting component 1304 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1306. In some aspects, one or more other components of device 1300 may generate communications and provide the generated communications to transmitting component 1304 for transmission to device 1306. In some aspects, transmitting component 1304 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to device 1306. In some aspects, transmitting component 1304 may include combinations of... FIG. 2 The described network entity includes one or more antennas, one or more modems, one or more modulators, one or more transmit MIMO processors, one or more transmit processors, one or more controllers / processors, one or more memories, or combinations thereof. In some aspects, the transmit component 1304 may co-located with the receive component 1302 in one or more transceivers.

[0199] The receiving component 1302 can receive requests for services through the user plane. The sending component 1304 can send a response indicating that the service will be provided through the user plane.

[0200] Service component 1308 supports services via the user plane, where the service is decoupled from the transport layer. Authentication component 1310 can authenticate services using the control plane. Service component 1308 assists in the operation of services via the user plane.

[0201] FIG. 13 The number and arrangement of components shown are provided as an example. In practice, different arrangements may exist. FIG. 13 The components shown are compared to additional components, fewer components, different components, or components arranged in a different manner. Furthermore, FIG. 13 The two or more components shown can be implemented within a single component, or FIG. 13 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, FIG. 13 The set (one or more) components shown are executable descriptions by FIG. 13 The other set of components shown performs one or more functions.

[0202] FIG. 14 This is an illustration of an example 1400 of a hardware implementation of a device 1405 employing a processing system 1410. The device 1405 may be a network entity or may be located at a network entity (e.g., included in a network entity).

[0203] Processing system 1410 may be implemented using a bus architecture generally represented by bus 1415. Bus 1415 may include any number of interconnect buses and bridges, depending on the specific application of processing system 1410 and overall design constraints. Bus 1415 links together various circuits including one or more processors and / or hardware components represented by processor 1420, illustrated components, and computer-readable medium / memory 1425. Bus 1415 may also link various other circuits, such as timing sources, peripheral devices, voltage regulators, and / or power management circuits.

[0204] Processing system 1410 may be coupled to one or more transceivers 1430. Transceiver 1430 is coupled to one or more antennas 1435. Transceiver 1430 provides components for communicating with various other devices via a transmission medium. Transceiver 1430 receives signals from one or more antennas 1435, extracts information from the received signals, and provides the extracted information to processing system 1410 (specifically, receiving component 1302). Furthermore, transceiver 1430 receives information from processing system 1410 (specifically, transmitting component 1304) and generates signals to be applied to one or more antennas 1435 based at least in part on the received information.

[0205] Processing system 1410 includes one or more processors 1420 coupled to computer-readable medium / memory 1425. Processor 1420 is responsible for general processing, including executing software stored on computer-readable medium / memory 1425. When executed by processor 1420, the software causes processing system 1410 to perform the various functions described herein with respect to any particular device. Computer-readable medium / memory 1425 can also be used to store data manipulated by processor 1420 during software execution. The processing system also includes at least one of the illustrated components. These components may be software modules running in processor 1420, residing in / stored on computer-readable medium / memory 1425, one or more hardware modules coupled to processor 1420, or some combination thereof.

[0206] In some aspects, processing system 1410 may be a component of network node 110 and may include one or more memories (such as memory 242) and / or may include one or more processors (such as at least one of TX MIMO processor 230, RX processor 238, and / or controller / processor 240). In some aspects, apparatus 1405 for wireless communication includes components for receiving a request for a service via a user plane and components for sending a response indicating that the service will pass through the user plane. The aforementioned components may be one or more of the aforementioned components of processing system 1410 of apparatus 1300 and / or apparatus 1405 configured to perform the functions stated by the aforementioned components. As described elsewhere herein, processing system 1410 may include TX MIMO processor 230, receiver processor 238, and / or controller / processor 240. In one configuration, the aforementioned components may be TX MIMO processor 230, receiver processor 238, and / or controller / processor 240 configured to perform the functions and / or operations stated herein.

[0207] FIG. 14 This is provided as an example. Other examples can be combined with it. FIG. 14 The examples described are different.

[0208] FIG. 15 This is a diagram illustrating an example 1500 of the NR system architecture according to this disclosure.

[0209] Example 1500 illustrates an NR architecture for 5G. The NR architecture may include network functions in RAN 1502 and core network 1504. RAN 1502 may perform RAN paging or mobility functions. Core network 1504 may include an AMF that provides functionality to UEs using NAS protocols. These functions may include: mobility; paging; identity; access, authorization, and registration; connectivity management; selection and transport; slicing; and security termination. Application services via the control plane may include SMF services (e.g., QoS, slicing), PCF services, AUSF services, location services, and sensing services. Each of these services has arbitrary interdependencies with the AMF. That is, all core network functions depend on the AMF. Furthermore, the mobility management layer is involved in slice management, which is a service concept and therefore an inefficient division of network functionality. There is also duplicate functionality in the RAN and core network. All these services in the control plane involve single-vendor deployments, which are difficult to extend beyond the first version.

[0210] Additionally, there is only one control plane path between RAN 1502 and core network 1504. This forces the architecture to add functionality that is essentially unrelated to access and mobility management to the AMF. This single control plane path also creates an interdependence between the AMF and RAN 1502. The single set of protocols (e.g., NAS protocol, RRC protocol) at the centralized control plane (e.g., CU-CP, AMF) makes the network design less flexible in adding new features.

[0211] As indicated above, FIG. 15 This is provided as an example. Other examples are available with reference to [the relevant information]. FIG. 15 The examples described are different.

[0212] FIG. 16 This is a diagram illustrating Example 1600 of a network design according to this disclosure.

[0213] Based on the various aspects described herein, new network designs may involve moving away from separate sets of protocols with centralized control. This could include providing separate, modular control plane services (functionalities) that can be requested individually, such as authentication and security services, subscription services, and policy services. Any update to a separate service does not require an update to the entire control plane. For example, a UE may send a message containing an indication of a service (provided via the control plane) and its UE ID to a radio access network (RAN) entity. This message may include a control plane transport header on the control plane transport layer, which is used to forward the message to the address of the service. The RAN entity can determine the address mapped to the service and forward the message to that address. The service entity at that address can send a configuration for the service, which is forwarded to the UE. The UE can then use the service via the control plane. In some aspects, the core network may provide a discovery and selection service for locating addresses for services.

[0214] By using separate addressable services on the control plane, the UE and core network can deploy services and features with greater flexibility. The core network can support more distributed functionalities, where the UE can communicate directly with each functionality (service). The UE can communicate with any service via the control plane, where control plane transports are shared with and independent of the control plane service. The UE can discover service addresses, while the network hides the network topology. New services or service enhancements can be added later without affecting control plane transports at the RAN or intermediate nodes. Therefore, updates to the control plane can be faster and involve less service disruption. This also improves the adoption of services on the network and creates new revenue streams while limiting future generations of redefinition of the control plane.

[0215] Example 1600 illustrates an example network design with an end-to-end system architecture for future generations, such as 6G. The network design demonstrates a modular control plane protocol with a cloud-native services-based architecture. A streamlined service-based control plane 1602 provides separate access services 1606, 1608, and 1610, typically provided by the AMF. Some services, such as device management, location, sensing, and data services, can be provided via either the control plane 1602 or the user plane 1604.

[0216] The new design can involve modularity and RAN / core network convergence. Network functionality can be modularized into independent service modules. RAN and core network functionality can be converged. NAS protocols and UE contexts can be modularized. A more streamlined control plane can focus on access, connectivity, mobility, and data services. Connectivity-insensitive services can be moved to the user plane.

[0217] This new design allows for functional partitioning of networks both between and within vendors. It enables faster and easier adoption of new vertical industries. Furthermore, it achieves forward compatibility with evolving and new features with minimal network impact.

[0218] As indicated above, FIG. 16 This is provided as an example. Other examples are available with reference to [the relevant information]. FIG. 16 The examples described are different.

[0219] FIG. 17 This is a diagram illustrating example 1700 of a control plane service according to this disclosure.

[0220] Example 1700 illustrates that dedicated services can be addressed via service IDs. Control plane services may include, for example, subscriptions, policies, authentication and security, discovery and selection, and NEF. Control plane services may also include different Access and Mobility Services (AMS) for specific types of devices (e.g., RedCap.IoT, smartphones). Different vendors may offer dedicated solutions. In some respects, these dedicated AMS services may be identified by their respective service IDs. For example, AMS service 1702 may be identified by service ID 1, and AMS service 1704 may be identified by service ID 2.

[0221] User plane services may include dedicated data services, each identified by a service ID. Each UE may have multiple data service slices (DSS). DSSs can interact directly with the UE and DU (e.g., eDU). DSSs can interact with AMS (e.g., for mobility areas, paging). DSSs can interact with authentication and security services to derive their own security context. DSS 1706 can be identified by service ID 3, and DSS 1708 can be identified by service ID 4.

[0222] As indicated above, FIG. 17 This is provided as an example. Other examples are available with reference to [the relevant information]. FIG. 17 The examples described are different.

[0223] FIG. 18 This is a diagram illustrating example 1800 of a service-based architecture according to this disclosure.

[0224] In some respects, UE 1802 can use Control Plane Transport 1808 to signal Control Plane Services 1806 within an end-to-end control plane signaling solution. Control Plane Transport 1808 can be a shared transport used for all services. RAN 1804 can participate in routing without knowing which service UE 1802 is communicating with. End-to-end security can be service-independent (support for the zero-trust paradigm).

[0225] In some respects, one or more control plane transport APIs may exist between RAN 1804 and control plane service 1806. The APIs may utilize service-based interfaces (SBIs). Control plane service 1806 can use the configuration API to request specific RAN configurations. The RAN can aggregate requests for different services and can accept, modify, or reject requests.

[0226] UE 1802 can use control plane transport 1808 to request services and receive service-specific configuration. This configuration can be local. It can be service-specific (e.g., a logical channel corresponding to a QoS flow) or service-agnostic (SAA) configuration inherent to eDU-UE connection operation and shared by all services.

[0227] As indicated above, FIG. 18 This is provided as an example. Other examples are available with reference to [the relevant information]. FIG. 18 The examples described are different.

[0228] FIG. 19 This is a diagram illustrating example 1900 of the control plane protocol stack according to this disclosure. Control plane transport can use the network service layer 1902 for signaling transmission between core network entities or between RAN (e.g., eDU) network entities and core network entities. Control plane transport can reuse the SBI. When using local configuration, the UE can use the 6G RRC layer for AS signaling transmission between the UE and the RAN.

[0229] As indicated above, FIG. 19 This is provided as an example. Other examples are available with reference to [the relevant information]. FIG. 19 The examples described are different.

[0230] FIG. 20This is a diagram illustrating Example 2000 of the control plane protocol stack according to this disclosure. In some aspects, as shown in the control plane protocol stack of Example 2000, the UE may use the control plane transport layer 2002 located on the 6G layer 2004 for signaling between the UE and the RAN (e.g., eDU), which provides L1 or L2 functionality (e.g., PHY, MAC, RLC, PDCP). The RAN (e.g., eDU) may use the control plane transport layer 2002 (such as the Hypertext Transfer (HTTP) layer, Transmission Control Protocol (TCP) layer, IP layer, and L1 / L2 layer) above the Internet-based layer 2006 for signaling between the RAN and control plane services. The UE may use the control plane transport layer 2002, the security layer 2008, and the service PDU layer 2010 for signaling between the UE and the control plane services. The security layer 2008 provides end-to-end security conforming to the zero-trust paradigm. The same security layer protocol may be used for different service PDUs. In some aspects, the service may be interpreted as being in the application layer. A service PDU can be viewed as an "application PDU" at the application layer.

[0231] In some respects, the control plane transport layer 2002 can provide addressing solutions through the control plane. The control plane transport layer 2002 can operate independently of the service with which the UE is communicating. The service can be identified by a service ID. The UE can be identified by a temporary UE ID.

[0232] The control plane protocol stack provides complete independence between control plane transports and control plane services. New control plane services can be added without affecting other existing network services. Control plane transports can be used at the RAN independently of any selected control plane service. Control plane transports minimize the interdependence between the RAN and the core network. Control plane transports provide end-to-end security solutions (e.g., implementing zero-trust end-to-end security solutions in 6G). A single security layer solution can be defined for all services.

[0233] As indicated above, FIG. 20 This is provided as an example. Other examples are available with reference to [the relevant information]. FIG. 20 The examples described are different.

[0234] FIG. 21 This is a diagram illustrating example 2100 of the control plane transport flow according to this disclosure. Example 2100 shows a UE 2105 (e.g., UE 120) and a RAN eDU 2110 (e.g., network node 110) that can communicate with each other via a wireless network (e.g., wireless network 100). eDU 2110 can communicate with core network entities such as discovery and selection service 2115 (e.g., core network node 130) and CP service 2120 (e.g., core network node 130) .

[0235] At 2125, UE 2105 can select the services provided via the control plane. At 2130, UE 2105 can send a message to the CP transport layer. This message can be a service PDU with a control plane transport header, which includes an indication of the service (e.g., a service ID) and the UE ID of UE 2105. This message can be encrypted.

[0236] eDU 2110 can request the discovery and selection service 2115 to resolve the service ID. At 2135, eDU 2110 can obtain the address of the service. In some respects, the service ID can be mapped to this address at eDU 2110 or at the discovery and selection service 2115. eDU 2110 can send a service discovery message with the service ID to the discovery and selection service 2115. The discovery and selection service 2115 can select a specific service instance for the service ID. The discovery and selection service 2115 can send all necessary information to eDU 2110. This information may include the service profile and service address (e.g., IP address). eDU 2110 can store the service IP address for future forwarding. At 2140, eDU 2110 can forward the message to the service IP address. eDU 2110 can use the transport API for uplink service PDUs. In some respects, the eDU 2110 can use tunneling, such as via HTTP2 / TCP / IP or HTTP3 / Fast User Datagram Protocol (UDP) Internet Connection (QUIC) / UDP / IP.

[0237] At 2145, CP service 2120 can send service-specific configuration. CP service 2120 can use the configuration API for RAN configuration requests and receive RAN configuration responses. eDU 2110 can use RRC simplified reconfiguration involving less information and signaling to communicate service-specific configuration to UE 2105.

[0238] At 2145, CP service 2120 can send a service PDU for CP service 2120. At 2150, CP service 2120 can use the transport API to send a downlink service PDU. At 2155, eDU 2110 can forward the service PDU. Each service PDU may have a CP transport header, which includes the service ID of the service and the UE's UE ID.

[0239] As indicated above, FIG. 21 This is provided as an example. Other examples are available with reference to [the relevant information]. FIG. 21 The examples described are different.

[0240] FIG. 22This is a diagram illustrating example 2200 of the security context flow according to this disclosure. eDU 2110 may communicate with authentication and security services 2205 (e.g., core network node 130).

[0241] In some respects, the authentication and security service 2205 and the discovery and selection service are special. These services are configured at UE 2105 and eDU 2110 and can be used prior to any service selected by UE 2105. The authentication and security service ID can be discovered by UE 2105 before any authentication and authorization is performed. At 2210, UE 2105 can determine the authentication and security service ID. The authentication and security service ID can be provided via insecure system information as part of the establishment of an insecure connection, such as at 2215. The discovery and selection service 2115 can be an entry point for UE 2105 to discover services, and therefore its own service ID can be discovered by all UEs. The authentication and security service ID and / or the discovery and selection service ID can be received by UE 2105 in system information and / or pre-configured (e.g., each Public Land Mobile Network (PLMN)). In some respects, these service IDs can be established as standard service IDs.

[0242] At 2220, UE 2105 may send a request to establish a security context. UE 2105 may select authentication and security service 2205 and send a request with the service ID of authentication and security service 2205. At 2225, eDU 2110 may obtain the service address of the authentication and security service. For example, eDU 2110 may send the service ID and receive an authentication and security service profile. This profile may include or be accompanied by the address of authentication and security service 2205.

[0243] At 2230, UE 2105 can establish security with Authentication and Security Service 2205. eDU 2110 can forward security requests to Authentication and Security Service 2205. Authentication and Security Service 2205 can establish security with UE 2105. This may include authenticating UE 2105, sending encryption keys, and / or setting privileges for UE 2105. With a secure connection established, UE 2105 can register with AMS or another service on the control plane.

[0244] As indicated above, FIG. 22 This is provided as an example. Other examples are available with reference to [the relevant information]. FIG. 22 The examples described are different.

[0245] FIG. 23 This is a diagram illustrating example 2300 of service selection according to this disclosure.

[0246] In some respects, service selection information can be used to configure the UE. Service selection information can identify the type of service (e.g., AMS, DSS). Service selection information may also include other information, such as preferred vendors. The actual service ID is derived from the service selection information. New designs can be service-independent, and the same selection framework can be used for AMS, DSS, or any other service via the control plane, including for future services (e.g., 7G).

[0247] Example 2300 illustrates that UE 2105 can directly receive a service ID from UE Discovery and Selection Service 2305. At 2310, UE 2105 can discover the service ID of the UE Discovery and Selection Service. UE 2105 can establish a context with UE Discovery and Selection Service 2305, which provides a list of services with service selection information. Each of these services may have a service ID mapped to a selection ID.

[0248] At 2315, UE 2105 may send a message to eDU 2110. This message may include a control plane transport header containing the UE ID, UE service and discovery service ID, and one or more selection IDs. At 2320, eDU 2110 may use the service ID of network discovery and selection service 2115 to obtain a service profile. At 2325, eDU 2110 may send a service PDU to UE discovery and selection service 2305, which has one or more selection IDs received from UE 2105. At 2330, eDU 2110 may send a selection ID to service ID mapping (or service ID only) to UE 2105.

[0249] At 2335, UE 2105 can send a message with a control plane transport header to eDU 2110, which includes the UE ID and the service ID of the selected service. At 2340, eDU 2110 can obtain a service profile from UE Discovery and Selection Service 2305. This service profile may include the address of the service. At 2345, UE 2105 can send a service PDU to the address of the selected service (CP service 2120). For UE 2105, the process for control plane services can continue.

[0250] In some respects, a service may include multiple service modules. A service module may provide a specific subset of the services offered. A service module may be associated with a service module ID. UE 2105, eDU 2110, discovery and selection service 2115, and CP service 2120 can be configured to use different combinations of service modules. This modularity of services allows the core network to add core network services without altering the selection and addressing of control plane services.

[0251] In some respects, UE 2105 can use a service selection ID to make an initial selection of control plane services (e.g., AMS, DSS). UE 2105 can send a service-specific message, which includes a field for the service type and a field for the dedicated service selection ID. The service type can indicate the type of service (e.g., AMS for enhanced mobile broadband (eMBB) devices, AMS for IoT devices, DSS). The service type can correspond to the minimum required functionality of the UE and / or the service. A default set of service module types may exist. The dedicated service selection ID can identify a specific service selection for the service type (e.g., vendor-specific, operator-controlled). UE 2105 can assign a temporary service ID to the service after the initial selection. UE 2105 can use the temporary service ID to address the service.

[0252] In some respects, each service ID may have multiple service module IDs. Messages for a service may include a service module type field and a service module selection ID field. The service module type may be service-type specific. For the AMS type, security, mobility, and transport services may exist. For the DSS type, SMF and SM-PCF services may exist. A dedicated service module ID can identify a specific service module of a service module type. In some respects, UE 2105 may use temporary service module IDs for module instantiation.

[0253] As indicated above, FIG. 23 This is provided as an example. Other examples are available with reference to [the relevant information]. FIG. 23 The examples described are different.

[0254] FIG. 24 This is a diagram illustrating example 2400 of service selection according to this disclosure.

[0255] In some respects, the control plane transport header can be used to send NAS PDUs or service PDUs. The control plane transport header can remain unchanged end-to-end or between UE 2105 and CP service 2120. In some respects, an AS transport header can be added to the NAS PDU. The AS header can be used for communication between UE 2105 and eDU 2110, and the AS header can be modified when the NAS PDU is forwarded from eDU 2110 to CP service 2120.

[0256] At 2405, UE 2105 can send a message, which can be a NAS PDU. The NAS PDU can include a service ID or a selection ID in the AS transport header. If a context has been created for a service, the AS transport header can include a temporary service ID (e.g., an AMS service ID) generated during registration with the 6G network. UE 2105 can use the service selection ID for initial context establishment. The temporary service ID may be unknown to UE 2105. The temporary service ID can be used at eDU 2110 to select a service or network function (e.g., Service Open and Orchestration Function (SEOF)) and forward the NAS PDU to the selected service or function.

[0257] In some respects, AS transports can be included in a simplified or separate RRC protocol that uses less signaling or information than an RRC reconfiguration. UE 2105 can establish an AS security context.

[0258] At 2410, eDU 2110 obtains a service profile with a service ID or a selection ID. At 2415, if eDU 2110 has a selection ID, it can select a service. At 2420, eDU 2110 can forward messages (NAS PDUs) to CP service 2120. Similar to... FIG. 21 As shown in Example 2100, UE 2105 can then receive configuration and use services on the control plane.

[0259] As indicated above, FIG. 24 This is provided as an example. Other examples are available with reference to [the relevant information]. FIG. 24 The examples described are different.

[0260] FIG. 25 This is a diagram illustrating example 2500 of the service selection according to this disclosure.

[0261] UE 2105 can provide a message with a service selection ID to eDU 2110. This message can be a service PDU. However, in some aspects, eDU 2110 can forward the service selection ID to discovery and selection service 2115 (without performing a check). At 2410, discovery and selection service 2115 can check security and subscription (e.g., check if UE 2105 is authorized to reach the service). Discovery and selection service 2115 can select the service and provide the service profile (e.g., service address) to eDU 2110. Similar to... FIG. 21 As described in Example 2100, eDU 2110 can then forward the message to CP service 2120.

[0262] As indicated above, FIG. 25This is provided as an example. Other examples are available with reference to [the relevant information]. FIG. 25 The examples described are different.

[0263] FIG. 26 This is a flowchart of an example method 2600 for wireless communication. Method 2600 may be performed at, for example, a UE (e.g., UE 120, UE 2105) or a device of the UE.

[0264] At 2610, the UE can select the services provided via the control plane. For example, the UE (e.g., using communication manager 140 and / or FIG. 30 The described service component 3008) can optionally provide services through the control plane, as described above in conjunction with, for example... FIG. 16 to FIG. 25 As described. In some respects, the service may be via AMS on the control plane, DSS on the control plane, subscription service on the control plane, policy service on the control plane, or NEF on the control plane.

[0265] At 2620, the UE can send a message including an instruction for the service and the UE's UE ID. For example, the UE (e.g., using Communication Manager 140 and / or FIG. 30 The described transmitting component 3004 can transmit messages including an indication of the service and the UE ID of the UE, as described above in conjunction with, for example... FIG. 16 to FIG. 25 As described. In some aspects, the message includes a first PDU having a control plane transport header that includes an indication of a service and a UE ID. In some aspects, the control plane transport header is associated with a control plane transport protocol layer, and the first PDU is a service PDU associated with a service PDU protocol layer. In some aspects, the PDU includes a NAS PDU. In some aspects, the indication of a service includes a service ID or service selection information associated with the service ID. The service selection information may include a service selection ID.

[0266] In some aspects, method 2600 includes establishing the security of the UE using security services and message reception at a security protocol layer between the control plane transport protocol layer and the serving PDU protocol layer. In some aspects, establishing the security of the UE includes selecting authentication and security services, and indicating the authentication and security services to the service.

[0267] At 2630, the UE can receive configuration for this service. For example, the UE (e.g., using communication manager 140 and / or FIG. 30 The described receiving component 3002 can receive configuration for the service, as described above in conjunction with, for example... FIG. 16 to FIG. 25As described. In some aspects, method 2600 includes sending one or more PDUs associated with the use of services via the control plane. This configuration can be used to send the PDUs.

[0268] In some aspects, method 2600 includes obtaining a service ID for discovering and selecting a service, the discovery and selection of which indicates an available service on the control plane. Obtaining the service ID for discovering and selecting a service may include receiving the service ID in system information or via configuration. Method 2600 may include obtaining the service ID for discovering and selecting a service, including obtaining a pre-configured service ID (e.g., according to a wireless communication standard). In some aspects, alone or in combination with one or more of the first to twelfth aspects, method 2600 includes receiving a service module ID of a service module associated with a service.

[0269] although FIG. 26 An example box of method 2600 is shown, but in some aspects, method 2600 may include... FIG. 26 The boxes depicted may be fewer, different, or arranged differently compared to additional boxes. Alternatively, two or more boxes in the box of method 2600 may be executed in parallel.

[0270] FIG. 27 This is a flowchart of an example method 2700 for wireless communication. Method 2700 may be performed at, for example, a first network entity (e.g., network node 110, eDU 2110) or a device of the first network entity.

[0271] At 2710, the first network entity can receive messages from the UE, including indications of services provided via the control plane and the UE's UE ID. For example, the first network entity (e.g., using communication manager 150 and / or FIG. 32 The described receiving component 3202 can receive messages from the UE, including indications of services provided through the control plane and the UE's UE ID, as described above in conjunction with, for example... FIG. 16 to FIG. 25 As described. The message may include a first PDU with a control plane transport header that includes an indication of a service and a UE ID. An address may be associated with a service ID. In some respects, the address is an IP address. In some respects, the first network entity may map the address to the service. The message may include a first PDU with a control plane transport header that includes an indication of a service and a UE ID.

[0272] In some aspects, the instruction for the service includes service selection information associated with a service ID, and method 2700 includes sending the service selection information, along with a request for the service ID, to a second network entity that discovers and selects the service, and one or more of the address or service ID for receiving the service. In some aspects, method 2700 includes sending the service ID to the UE.

[0273] In some aspects, the instruction for the service includes a service selection ID, the message includes a NAS PDU, and method 2700 includes using the service selection ID to select an SEOF, and forwarding the NAS PDU to the SEOF.

[0274] At 2720, the first network entity may forward the message to the address of the service, at least in part, based on this instruction to the service. For example, the first network entity (e.g., using communication manager 150 and / or FIG. 32 The described sending component 3204 may forward the message to the address of the service, at least in part, based on the instruction to the service, as described above in conjunction with, for example... FIG. 16 to FIG. 25 As described. In some respects, the address is an IP address. In some respects, the first network entity may use tunneling, such as HTTP / 2 or HTTP / 3 via QUIC / UDP / IP or TCP / IP. In some respects, the first network entity may map the address to the service.

[0275] At 2730, the first network entity can send the configuration for the service to the UE. For example, the first network entity (e.g., using communication manager 150 and / or FIG. 32 The described transmitting component 3204 can transmit the configuration for the service to the UE, as described above in conjunction with, for example... FIG. 16 to FIG. 25 As described.

[0276] although FIG. 27 An example box of method 2700 is shown, but in some aspects, method 2700 may include... FIG. 27 The boxes depicted may be fewer, different, or arranged differently compared to additional boxes. Alternatively, two or more boxes in the box of method 2700 may be executed in parallel.

[0277] FIG. 28 This is a flowchart of an example method 2800 for wireless communication. Method 2800 may be performed at, for example, a second network entity (e.g., core network node 130, service discovery and selection 2115) or a device of the second network entity.

[0278] At 2810, the second network entity can receive service selection information associated with the service from the first network entity. For example, the second network entity (e.g., using communication manager 160 and / or...) FIG. 34 The described receiving component 3402 can receive service selection information associated with a service from a first network entity, as described above in conjunction with, for example... FIG. 16 to FIG. 25 As described. In some aspects, method 2800 includes performing a security check on the UE and receiving subscription information for the service.

[0279] At point 2820, the second network entity can send the service ID associated with the service to the first network entity. For example, the second network entity (e.g., using communication manager 160 and / or...) FIG. 34 The described sending component 3404 can send the service ID associated with the service to the first network entity, as described above in conjunction with, for example... FIG. 16 to FIG. 25 As described.

[0280] At 2830, the second network entity may send the address of the service or the service configuration file of the service to the first network entity. For example, the second network entity (e.g., using communication manager 160 and / or FIG. 34 The described sending component 3404 can send the address of the service or the service configuration file of the service to the first network entity, as described above in conjunction with, for example... FIG. 16 to FIG. 25 As described. In some respects, this service profile is used to discover and select services or authentication and security services.

[0281] although FIG. 28 An example box of method 2800 is shown, but in some respects, method 2800 may include... FIG. 28 The boxes depicted may be fewer, different, or arranged differently compared to additional boxes. Alternatively, two or more boxes in the box of method 2800 may be executed in parallel.

[0282] FIG. 29 This is a flowchart of an example method 2900 for wireless communication. Method 2900 may be performed at, for example, a network entity (e.g., core network node 130, CP service 2120) or a device of the network entity.

[0283] At 2910, the network entity can receive messages that include instructions for services provided via the control plane and the UE's UE ID. For example, the network entity (e.g., using Communication Manager 160 and / or FIG. 36 The described receiving component 3602 can receive messages including indications of services provided through the control plane and the UE's UE ID, as described above in conjunction with, for example... FIG. 16 to FIG. 25 As described.

[0284] At point 2920, the network entity can send configuration for the service. For example, the network entity (e.g., using Communication Manager 160 and / or FIG. 36 The described sending component 3604 can send configurations for the service, as described above in conjunction with, for example... FIG. 16 to FIG. 25 As described.

[0285] At 2930, the network entity may send one or more PDUs associated with the use of the service via the control plane. For example, the network entity (e.g., using Communication Manager 160 and / or FIG. 36 The described sending component 3604 can send one or more PDUs associated with the service used through the control plane, as described above in conjunction with, for example... FIG. 16 to FIG. 25 As described.

[0286] although FIG. 29 An example box of method 2900 is shown, but in some aspects, method 2900 may include... FIG. 29 The boxes depicted may be fewer, different, or arranged differently compared to additional boxes. Alternatively, two or more boxes in the box of method 2900 may be executed in parallel.

[0287] FIG. 30 This is a diagram illustrating an example device 3000 for wireless communication according to the present disclosure. Device 3000 may be a UE (e.g., UE 120, UE 2105), or a UE may include device 3000. In some aspects, device 3000 includes a receiving component 3002 and a transmitting component 3004, which can communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, device 3000 can use the receiving component 3002 and the transmitting component 3004 to communicate with another device 3006 (such as a UE, a base station, or another wireless communication device). As further shown, device 3000 may include a communication manager 140. Communication manager 140 may include a service component 3008 and / or a security component 3010, etc.

[0288] In some respects, device 3000 can be configured to perform the functions described herein. FIG. 1 to FIG. 25 One or more operations described herein. Additionally or alternatively, the apparatus 3000 may be configured to perform one or more processes described herein, such as FIG. 26 Method 2600. In some respects, FIG. 30 The illustrated device 3000 and / or one or more components may include a combination FIG. 2 One or more components of the described UE. Additionally or alternatively, FIG. 30One or more components shown can be combined FIG. 2 Implementation within one or more of the described components. Additionally or alternatively, one or more components in the set of components may be implemented at least partially as software stored in one or more memories. For example, a component (or a portion thereof) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by one or more controllers or one or more processors to perform the function or operation of the component.

[0289] Receiver 3002 may receive communications from device 3006, such as reference signals, control information, data communications, or combinations thereof. Receiver 3002 may provide the received communications to one or more other components of device 3000. In some aspects, receiver 3002 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) and may provide the processed signals to one or more other components of device 3000. In some aspects, receiver 3002 may include combinations of... FIG. 2 The described UE includes one or more antennas, one or more modems, one or more demodulators, one or more MIMO detectors, one or more receiver processors, one or more controllers / processors, one or more memories, or combinations thereof.

[0290] Transmitting component 3004 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 3006. In some aspects, one or more other components of device 3000 may generate communications and provide the generated communications to transmitting component 3004 for transmission to device 3006. In some aspects, transmitting component 3004 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to device 3006. In some aspects, transmitting component 3004 may include combinations of... FIG. 2 The described UE may include one or more antennas, one or more modems, one or more modulators, one or more transmit MIMO processors, one or more transmit processors, one or more controllers / processors, one or more memories, or combinations thereof. In some aspects, the transmit component 3004 may co-located with the receive component 3002 in one or more transceivers.

[0291] Service component 3008 can select services provided via the control plane. Transmitting component 3004 can send a message including an indication of the service and the UE ID of the UE. Service component 3008 can obtain the service ID of the discovered and selected service, which indicates the available services on the control plane. Receiving component 3002 can receive the service module ID of the service module associated with the service.

[0292] The receiving component 3002 can receive configuration for the service. The transmitting component 3004 can transmit one or more PDUs associated with using the service through the control plane. The security component 3010 can establish the security of the UE using security services and message reception at a security protocol layer between the control plane transport protocol layer and the service PDU protocol layer.

[0293] FIG. 30 The number and arrangement of components shown are provided as an example. In practice, different arrangements may exist. FIG. 30 The components shown are compared to additional components, fewer components, different components, or components arranged in a different manner. Furthermore, FIG. 30 The two or more components shown can be implemented within a single component, or FIG. 30 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, FIG. 30 The set (one or more) components shown are executable descriptions by FIG. 30 The other set of components shown performs one or more functions.

[0294] FIG. 31 This is an illustration of an example 3100 of a hardware implementation of a device 3105 employing a processing system 3110 according to the present disclosure. The device 3105 may be a UE or may be located at a UE (e.g., included in a UE).

[0295] Processing system 3110 may be implemented using a bus architecture generally represented by bus 3115. Bus 3115 may include any number of interconnect buses and bridges, depending on the specific application of processing system 3110 and overall design constraints. Bus 3115 links together various circuits including one or more processors and / or hardware components represented by processor 3120, illustrated components, and computer-readable medium / memory 3125. Bus 3115 may also link various other circuits, such as timing sources, peripheral devices, voltage regulators, and / or power management circuits.

[0296] The processing system 3110 may be coupled to one or more transceivers 3130. The transceiver 3130 is coupled to one or more antennas 3135. The transceiver 3130 provides components for communicating with various other devices via a transmission medium. The transceiver 3130 receives signals from the one or more antennas 3135, extracts information from the received signals, and provides the extracted information to the processing system 3110 (specifically, the receiving component 3002). Furthermore, the transceiver 3130 receives information from the processing system 3110 (specifically, the transmitting component 3004) and generates signals to be applied to the one or more antennas 3135, at least in part, based on the received information.

[0297] Processing system 3110 includes one or more processors 3120 coupled to computer-readable medium / memory 3125. Processor 3120 is responsible for general processing, including executing software stored on computer-readable medium / memory 3125. When executed by processor 3120, the software causes processing system 3110 to perform the various functions described herein with respect to any particular device. Computer-readable medium / memory 3125 can also be used to store data manipulated by processor 3120 during software execution. The processing system also includes at least one of the illustrated components. These components may be software modules running in processor 3120, residing in / stored on computer-readable medium / memory 3125, one or more hardware modules coupled to processor 3120, or some combination thereof.

[0298] In some aspects, processing system 3110 may be a component of UE 120 and may include one or more memories (such as memory 282) and / or may include one or more processors (such as at least one of TX MIMO processor 266, RX processor 258, and / or controller / processor 280). In some aspects, apparatus 3105 for wireless communication includes: components for selecting a service provided via a control plane; components for transmitting a message including an indication of the service and an identifier of the apparatus; and components for receiving configuration for the service. The aforementioned components may be one or more of the aforementioned components of apparatus 3000 and / or processing system 3110 of apparatus 3105 configured to perform the functions stated by the aforementioned components. As described elsewhere herein, processing system 3110 may include TX MIMO processor 266, RX processor 258, and / or controller / processor 280. In one configuration, the aforementioned components may be TX MIMO processor 266, RX processor 258, and / or controller / processor 280 configured to perform the functions and / or operations stated herein.

[0299] FIG. 31 This is provided as an example. Other examples can be combined with it.FIG. 31 The examples described are different.

[0300] FIG. 32 This is a diagram of an example device 3200 for wireless communication according to the present disclosure. Device 3200 may be a first network entity (e.g., network node 110, eDU 2110), or the first network entity may include device 3200. In some aspects, device 3200 includes a receiving component 3202 and a transmitting component 3204, which can communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, device 3200 can use the receiving component 3202 and the transmitting component 3204 to communicate with another device 3206 (such as a UE, base station, or another wireless communication device). As further shown, device 3200 may include a communication manager 150. Communication manager 150 may include a service component 3208, etc.

[0301] In some respects, device 3200 can be configured to perform the functions described herein. FIG. 1 to FIG. 25 One or more operations described herein. Additionally or alternatively, the apparatus 3200 may be configured to perform one or more processes described herein, such as FIG. 27 Method 2700. In some respects, FIG. 32 The illustrated device 3200 and / or one or more components may include a combination FIG. 2 One or more components of the first network entity described. Additionally or alternatively, FIG. 32 One or more components shown can be combined FIG. 2 Implementation within one or more of the described components. Additionally or alternatively, one or more components in the set of components may be implemented at least partially as software stored in one or more memories. For example, a component (or a portion thereof) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by one or more controllers or one or more processors to perform the function or operation of the component.

[0302] Receiver 3202 may receive communications from device 3206, such as reference signals, control information, data communications, or combinations thereof. Receiver 3202 may provide the received communications to one or more other components of device 3200. In some aspects, receiver 3202 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) and may provide the processed signals to one or more other components of device 3200. In some aspects, receiver 3202 may include combinations of... FIG. 2The first network entity described includes one or more antennas, one or more modems, one or more demodulators, one or more MIMO detectors, one or more receiver processors, one or more controllers / processors, one or more memories, or combinations thereof.

[0303] Transmitting component 3204 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 3206. In some aspects, one or more other components of device 3200 may generate communications and provide the generated communications to transmitting component 3204 for transmission to device 3206. In some aspects, transmitting component 3204 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to device 3206. In some aspects, transmitting component 3204 may include combinations of... FIG. 2 The described first network entity includes one or more antennas, one or more modems, one or more modulators, one or more transmit MIMO processors, one or more transmit processors, one or more controllers / processors, one or more memories, or combinations thereof. In some aspects, the transmit component 3204 may co-located with the receive component 3202 in one or more transceivers.

[0304] Receiving component 3202 can receive a message from the UE, the message including an indication of a service provided through the control plane and the UE's UE ID. Transmitting component 3204 can forward the message to the address of the service, at least in part, based on the indication of the service. Service component 3208 can map the address to the service. Transmitting component 3204 can send configuration for the service to the UE. Transmitting component 3204 can send the service ID to the UE.

[0305] FIG. 32 The number and arrangement of components shown are provided as an example. In practice, different arrangements may exist. FIG. 32 The components shown are compared to additional components, fewer components, different components, or components arranged in a different manner. Furthermore, FIG. 32 The two or more components shown can be implemented within a single component, or FIG. 32 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, FIG. 32 The set (one or more) components shown are executable descriptions by FIG. 32 The other set of components shown performs one or more functions.

[0306] FIG. 33This is an illustration of an example 3300 of a hardware implementation of a device 3305 employing a processing system 3310 according to the present disclosure. The device 3305 may be a first network entity or may be located at a first network entity (e.g., included in a first network entity).

[0307] Processing system 3310 may be implemented using a bus architecture generally represented by bus 3315. Bus 3315 may include any number of interconnect buses and bridges, depending on the specific application of processing system 3310 and overall design constraints. Bus 3315 links together various circuits including one or more processors and / or hardware components represented by processor 3320, illustrated components, and computer-readable medium / memory 3325. Bus 3315 may also link various other circuits, such as timing sources, peripheral devices, voltage regulators, and / or power management circuits.

[0308] The processing system 3310 may be coupled to one or more transceivers 3330. The transceivers 3330 are coupled to one or more antennas 3335. The transceivers 3330 provide components for communicating with various other devices via a transmission medium. The transceivers 3330 receive signals from the one or more antennas 3335, extract information from the received signals, and provide the extracted information to the processing system 3310 (specifically, the receiving component 3202). Furthermore, the transceivers 3330 receive information from the processing system 3310 (specifically, the transmitting component 3204) and generate signals to be applied to the one or more antennas 3335, at least in part, based on the received information.

[0309] Processing system 3310 includes one or more processors 3320 coupled to computer-readable medium / memory 3325. Processor 3320 is responsible for general processing, including executing software stored on computer-readable medium / memory 3325. When executed by processor 3320, the software causes processing system 3310 to perform the various functions described herein with respect to any particular device. Computer-readable medium / memory 3325 can also be used to store data manipulated by processor 3320 during software execution. The processing system also includes at least one of the illustrated components. These components may be software modules running in processor 3320, residing in / stored on computer-readable medium / memory 3325, one or more hardware modules coupled to processor 3320, or some combination thereof.

[0310] In some aspects, processing system 3310 may be a component of network node 110 and may include one or more memories (such as memory 242) and / or may include one or more processors (such as at least one of TX MIMO processor 230, RX processor 238, and / or controller / processor 240). In some aspects, apparatus 3305 for wireless communication includes: components for receiving a message from another device, the message including an indication of a service provided via a control plane and an identifier of the other device; and components for forwarding the message to an address of the service, at least in part based on the indication of the service. The aforementioned components may be one or more of the aforementioned components of processing system 3310 of apparatus 3200 and / or apparatus 3305 configured to perform the functions stated by the aforementioned components. As described elsewhere herein, processing system 3310 may include TX MIMO processor 230, receiver processor 238, and / or controller / processor 240. In one configuration, the aforementioned components may be a TX MIMO processor 230, a receiver processor 238, and / or a controller / processor 240 configured to perform the functions and / or operations set forth herein.

[0311] FIG. 33 This is provided as an example. Other examples can be combined with it. FIG. 33 The examples described are different.

[0312] FIG. 34 This is a diagram of an example device 3400 for wireless communication according to the present disclosure. Device 3400 may be a second network entity (e.g., core network node 130, discovery and selection service 2115), or the second network entity may include device 3400. In some aspects, device 3400 includes a receiving component 3402 and a transmitting component 3404, which can communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, device 3400 can use the receiving component 3402 and the transmitting component 3404 to communicate with another device 3406 (such as a UE, base station, or another wireless communication device). As further shown, device 3400 may include a communication manager 160. Communication manager 160 may include a security component 3408, etc.

[0313] In some respects, device 3400 can be configured to perform the functions described herein. FIG. 1 to FIG. 25 One or more operations described herein. Additionally or alternatively, the apparatus 3400 may be configured to perform one or more processes described herein, such as FIG. 28 Method 2800. In some respects, FIG. 34 The illustrated device 3400 and / or one or more components may include a combination FIG. 2One or more components of the described second network entity. Additionally or alternatively, FIG. 34 One or more components shown can be combined FIG. 2 Implementation within one or more of the described components. Additionally or alternatively, one or more components in the set of components may be implemented at least partially as software stored in one or more memories. For example, a component (or a portion thereof) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by one or more controllers or one or more processors to perform the function or operation of the component.

[0314] Receiver 3402 may receive communications from device 3406, such as reference signals, control information, data communications, or combinations thereof. Receiver 3402 may provide the received communications to one or more other components of device 3400. In some aspects, receiver 3402 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications, and may provide the processed signals to one or more other components of device 3400. In some aspects, receiver 3402 may include combinations of... FIG. 2 The second network entity described includes one or more antennas, one or more modems, one or more demodulators, one or more MIMO detectors, one or more receiver processors, one or more controllers / processors, one or more memories, or combinations thereof.

[0315] Transmitting component 3404 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 3406. In some aspects, one or more other components of device 3400 may generate communications and provide the generated communications to transmitting component 3404 for transmission to device 3406. In some aspects, transmitting component 3404 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to device 3406. In some aspects, transmitting component 3404 may include combinations of... FIG. 2 The described second network entity includes one or more antennas, one or more modems, one or more modulators, one or more transmit MIMO processors, one or more transmit processors, one or more controllers / processors, one or more memories, or combinations thereof. In some aspects, the transmit component 3404 may co-located with the receive component 3402 in one or more transceivers.

[0316] The receiving component 3402 can receive service selection information associated with the service from the first network entity. The sending component 3404 can send the service ID associated with the service to the first network entity.

[0317] The transmitting component 3404 can send the address of the service or the service configuration file of the service to the first network entity. The security component 3408 can perform a security check on the UE. The receiving component 3402 can receive the subscription information of the service.

[0318] FIG. 34 The number and arrangement of components shown are provided as an example. In practice, different arrangements may exist. FIG. 34 The components shown are compared to additional components, fewer components, different components, or components arranged in a different manner. Furthermore, FIG. 34 The two or more components shown can be implemented within a single component, or FIG. 34 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, FIG. 34 The set (one or more) components shown are executable descriptions by FIG. 34 The other set of components shown performs one or more functions.

[0319] FIG. 35 This is an illustration of an example 3500 of a hardware implementation of a device 3505 employing a processing system 3510 according to the present disclosure. The device 3505 may be a second network entity or may be located at a second network entity (e.g., included in a second network entity).

[0320] Processing system 3510 can be implemented using a bus architecture generally represented by bus 3515. Bus 3515 may include any number of interconnect buses and bridges, depending on the specific application of processing system 3510 and overall design constraints. Bus 3515 links together various circuits including one or more processors and / or hardware components represented by processor 3520, illustrated components, and computer-readable medium / memory 3525. Bus 3515 may also link various other circuits, such as timing sources, peripheral devices, voltage regulators, and / or power management circuits.

[0321] The processing system 3510 may be coupled to one or more transceivers 3530. The transceiver 3530 is coupled to one or more antennas 3535. The transceiver 3530 provides components for communicating with various other devices via a transmission medium. The transceiver 3530 receives signals from the one or more antennas 3535, extracts information from the received signals, and provides the extracted information to the processing system 3510 (specifically, the receiving component 3402). Furthermore, the transceiver 3530 receives information from the processing system 3510 (specifically, the transmitting component 3404) and generates signals to be applied to the one or more antennas 3535, at least in part, based on the received information.

[0322] Processing system 3510 includes one or more processors 3520 coupled to computer-readable medium / memory 3525. Processor 3520 is responsible for general processing, including executing software stored on computer-readable medium / memory 3525. When executed by processor 3520, the software causes processing system 3510 to perform the various functions described herein with respect to any particular device. Computer-readable medium / memory 3525 can also be used to store data manipulated by processor 3520 during software execution. The processing system also includes at least one of the illustrated components. These components may be software modules running in processor 3520, residing in / stored in computer-readable medium / memory 3525, one or more hardware modules coupled to processor 3520, or some combination thereof.

[0323] In some aspects, processing system 3510 may be a component of core network node 130 and may include one or more memories, such as memory 292, and / or may include one or more processors, such as controller / processor 290. In some aspects, apparatus 3505 for wireless communication includes: components for receiving service selection information associated with a service from a first network entity; and components for sending a service identifier associated with the service to the first network entity. The aforementioned components may be one or more of the aforementioned components of apparatus 3400 and / or processing system 3510 of apparatus 3505 configured to perform the functions stated by the aforementioned components. As described elsewhere herein, processing system 3510 may include controller / processor 290. In one configuration, the aforementioned components may be controller / processor 290 configured to perform the functions and / or operations stated herein.

[0324] FIG. 35 This is provided as an example. Other examples can be combined with it. FIG. 35 The examples described are different.

[0325] FIG. 36 This is a diagram illustrating an example device 3600 for wireless communication according to the present disclosure. Device 3600 may be a network entity (e.g., core network node 130, CP service 2120), or a network entity may include device 3600. In some aspects, device 3600 includes a receiving component 3602 and a transmitting component 3604, which can communicate with each other (e.g., via one or more buses and / or one or more other components). As shown, device 3600 can use the receiving component 3602 and the transmitting component 3604 to communicate with another device 3606 (such as a UE, base station, or another wireless communication device). As further shown, device 3600 may include a communication manager 160. Communication manager 160 may include a service component 3608, etc.

[0326] In some respects, device 3600 can be configured to perform the functions described herein. FIG. 1 to FIG. 25 One or more operations described herein. Additionally or alternatively, the device 3600 may be configured to perform one or more processes described herein, such as FIG. 29 Method 2900. In some respects, FIG. 36 The illustrated device 3600 and / or one or more components may include a combination FIG. 2 One or more components of the described network entity. Additionally or alternatively, FIG. 36 One or more components shown can be combined FIG. 2 Implementation within one or more of the described components. Additionally or alternatively, one or more components in the set of components may be implemented at least partially as software stored in one or more memories. For example, a component (or a portion thereof) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by one or more controllers or one or more processors to perform the function or operation of the component.

[0327] Receiver 3602 may receive communications from device 3606, such as reference signals, control information, data communications, or combinations thereof. Receiver 3602 may provide the received communications to one or more other components of device 3600. In some aspects, receiver 3602 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) and may provide the processed signals to one or more other components of device 3600. In some aspects, receiver 3602 may include combinations of... FIG. 2 The described network entity includes one or more antennas, one or more modems, one or more demodulators, one or more MIMO detectors, one or more receiver processors, one or more controllers / processors, one or more memories, or combinations thereof.

[0328] Transmitting component 3604 can transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 3606. In some aspects, one or more other components of device 3600 can generate communications and provide the generated communications to transmitting component 3604 for transmission to device 3606. In some aspects, transmitting component 3604 can perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and can transmit the processed signals to device 3606. In some aspects, transmitting component 3604 may include combinations of... FIG. 2The described network entity includes one or more antennas, one or more modems, one or more modulators, one or more transmit MIMO processors, one or more transmit processors, one or more controllers / processors, one or more memories, or combinations thereof. In some aspects, the transmit component 3604 may co-located with the receive component 3602 in one or more transceivers.

[0329] Receiving component 3602 can receive messages including indications of services provided via the control plane and the UE's UEID. Transmitting component 3604 can transmit configurations for the service. Transmitting component 3604 and service component 3608 can transmit one or more PDUs associated with using the service via the control plane.

[0330] FIG. 36 The number and arrangement of components shown are provided as an example. In practice, different arrangements may exist. FIG. 36 The components shown are compared to additional components, fewer components, different components, or components arranged in a different manner. Furthermore, FIG. 36 The two or more components shown can be implemented within a single component, or FIG. 36 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, FIG. 36 The set (one or more) components shown are executable descriptions by FIG. 36 The other set of components shown performs one or more functions.

[0331] FIG. 37 This is an illustration of an example 3700 of a hardware implementation of a device 3705 employing a processing system 3710 according to the present disclosure. The device 3705 may be a network entity or may be located at a network entity (e.g., included in a network entity).

[0332] Processing system 3710 can be implemented using a bus architecture generally represented by bus 3715. Bus 3715 may include any number of interconnect buses and bridges, depending on the specific application of processing system 3710 and overall design constraints. Bus 3715 links together various circuits including one or more processors and / or hardware components represented by processor 3720, illustrated components, and computer-readable medium / memory 3725. Bus 3715 may also link various other circuits, such as timing sources, peripheral devices, voltage regulators, and / or power management circuits.

[0333] The processing system 3710 may be coupled to one or more transceivers 3730. The transceiver 3730 is coupled to one or more antennas 3735. The transceiver 3730 provides components for communicating with various other devices via a transmission medium. The transceiver 3730 receives signals from the one or more antennas 3735, extracts information from the received signals, and provides the extracted information to the processing system 3710 (specifically, the receiving component 3602). Furthermore, the transceiver 3730 receives information from the processing system 3710 (specifically, the transmitting component 3604) and generates signals to be applied to the one or more antennas 3735, at least in part, based on the received information.

[0334] Processing system 3710 includes one or more processors 3720 coupled to computer-readable medium / memory 3725. Processor 3720 is responsible for general processing, including executing software stored on computer-readable medium / memory 3725. When executed by processor 3720, the software causes processing system 3710 to perform the various functions described herein with respect to any particular device. Computer-readable medium / memory 3725 can also be used to store data manipulated by processor 3720 during software execution. The processing system also includes at least one of the illustrated components. These components may be software modules running in processor 3720, residing in / stored on computer-readable medium / memory 3725, one or more hardware modules coupled to processor 3720, or some combination thereof.

[0335] In some aspects, processing system 3710 may be a component of core network node 130 and may include one or more memories, such as memory 292, and / or may include one or more processors, such as controller / processor 290. In some aspects, apparatus 3705 for wireless communication includes: components for receiving a message including an indication of a service provided via a control plane and an identifier of another device; and components for transmitting configuration for the service. The aforementioned components may be one or more of the aforementioned components of processing system 3710 of apparatus 3600 and / or apparatus 3705 configured to perform the functions stated by the aforementioned components. As described elsewhere herein, processing system 3710 may include controller / processor 290. In one configuration, the aforementioned components may be controller / processor 290 configured to perform the functions and / or operations stated herein.

[0336] FIG. 37 This is provided as an example. Other examples can be combined with it. FIG. 37 The examples described are different.

[0337] The following provides an overview of some aspects of this disclosure:

[0338] Aspect 1: A method for wireless communication performed by a user equipment (UE), the method comprising: selecting a service provided via a control plane; sending a message including an indication of the service and a UE identifier (ID) of the UE; and receiving configuration for the service.

[0339] Aspect 2: According to the method of aspect 1, the message includes a first protocol data unit (PDU) having a control plane transmission header, the control plane transmission header including the indication of the service and the UE ID.

[0340] Aspect 3: According to the method of aspect 2, wherein the control plane transmission header is associated with the control plane transmission protocol layer, and wherein the first PDU is a service PDU associated with the service PDU protocol layer.

[0341] Aspect 4: According to the method of aspect 3, the method further includes: establishing the security of the UE by using security services and message reception on a security protocol layer between the control plane transport protocol layer and the service PDU protocol layer.

[0342] Aspect 5: According to the method of aspect 4, establishing the security of the UE includes: selecting authentication and security services, and wherein the indication of the services indicates the authentication and security services.

[0343] Aspect 6: According to the method of aspect 2, the first protocol data unit (PDU) includes a non-access stratum (NAS) PDU.

[0344] Aspect 7: The method according to any one of Aspects 1 to 6, wherein the indication for the service includes a service ID.

[0345] Aspect 8: The method according to any one of Aspects 1 to 7, wherein the indication for the service includes service selection information associated with the service ID.

[0346] Aspect 9: According to the method described in aspect 8, the service selection information includes a service selection ID.

[0347] Aspect 10: The method according to any one of Aspects 1 to 9, the method further comprising: sending one or more Protocol Data Units (PDUs) associated with the use of the service through the control plane.

[0348] Aspect 11: The method according to any one of Aspects 1 to 10, the method further comprising: obtaining a service ID for a discovery and selection service, the discovery and selection service indicating available services on the control plane.

[0349] Aspect 12: According to the method of aspect 11, obtaining the service ID of the discovery and selection service includes receiving the service ID in system information or via configuration.

[0350] Aspect 13: According to the method of aspect 11, obtaining the service ID of the discovery and selection service includes: obtaining a pre-configured service ID.

[0351] Aspect 14: The method according to any one of Aspects 1 to 13, the method further comprising: receiving a service module ID of a service module associated with the service.

[0352] Aspect 15: The method according to any one of Aspects 1 to 14, wherein the service is access and mobility service through the control plane.

[0353] Aspect 16: The method according to any one of Aspects 1 to 14, wherein the service is a data service through the control plane.

[0354] Aspect 17: The method according to any one of Aspects 1 to 14, wherein the service is a subscription service or a policy service through the control plane.

[0355] Aspect 18: The method according to any one of Aspects 1 to 14, wherein the service is provided through the network opening function of the control plane.

[0356] Aspect 19: A method of wireless communication performed by a first network entity, the method comprising: receiving a message from a user equipment (UE), the message including an indication of a service provided through a control plane and a UE identifier (ID) of the UE; and forwarding the message to an address of the service based at least in part on the indication of the service.

[0357] Aspect 20: The method according to aspect 19, wherein the address is an Internet Protocol address.

[0358] Aspect 21: The method according to any one of Aspects 19 to 20, wherein forwarding the message comprises: using tunneling to forward the message via one or more of Hypertext Transfer Protocol, Transmission Control Protocol, Internet Protocol, User Datagram Protocol or Fast User Datagram Protocol Internet connection.

[0359] Aspect 22: The method according to any one of aspects 19 to 21, the method further comprising: mapping the address to the service.

[0360] Aspect 23: The method according to any one of aspects 19 to 22, the method further comprising: sending a configuration for the service to the UE.

[0361] Aspect 24: The method according to any one of Aspects 19 to 23, wherein the message includes a first Protocol Data Unit (PDU) having a control plane transmission header, the control plane transmission header including the indication to the service and the UE ID.

[0362] Aspect 25: The method according to any one of Aspects 19 to 24, wherein the indication for the service includes service selection information associated with a service ID, and wherein the method includes: sending the service selection information together with a request for the service ID to a second network entity for discovering and selecting services; and receiving one or more of the address of the service or the service ID.

[0363] Aspect 26: According to the method of aspect 25, wherein the address is associated with the service ID.

[0364] Aspect 27: The method according to aspect 25 further includes: sending the service ID to the UE.

[0365] Aspect 28: The method according to any one of Aspects 19 to 27, wherein the indication for the service includes a service selection ID, wherein the message includes a Non-Access Layer (NAS) Protocol Data Unit (PDU), and wherein the method includes: using the service selection ID to select a Service Opening and Orchestration Function (SEOF); ​​and forwarding the NAS PDU to the SEOF.

[0366] Aspect 29: A method for wireless communication performed by a second network entity, the method comprising: receiving service selection information associated with a service from a first network entity; and sending a service identifier (ID) associated with the service to the first network entity.

[0367] Aspect 30: According to the method of aspect 29, the method further includes: sending the address of the service or the service configuration file of the service to the first network entity.

[0368] Aspect 31: According to the method of aspect 30, the service profile is used to discover and select services or authentication and security services.

[0369] Aspect 32: The method according to any one of Aspects 29 to 31, the method further comprising: performing a security check on the user equipment (UE); and receiving subscription information for the service.

[0370] Aspect 33: A method for wireless communication performed by a network entity, the method comprising: receiving a message including an indication of a service provided through a control plane and a UE identifier (ID) of a user equipment (UE); and sending a configuration for the service.

[0371] Aspect 34: The method according to aspect 33 further includes: sending one or more protocol data units (PDUs) associated with using the service through the control plane.

[0372] Aspect 35: An apparatus for wireless communication at a device, the apparatus comprising: one or more processors; one or more memories coupled to the one or more processors; and instructions stored in the one or more memories and executable by the one or more processors to cause the apparatus to perform the method according to one or more of aspects 1 to 34.

[0373] Aspect 36: An apparatus for wireless communication at a device, the apparatus comprising one or more memories and one or more processors coupled to the one or more memories, the one or more processors being configured to cause the device to perform the method according to one or more of aspects 1 to 34.

[0374] Aspect 37: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 1 to 34.

[0375] Aspect 38: A non-transitory computer-readable medium storing code for wireless communication, the code including instructions executable by one or more processors to perform the method according to one or more of aspects 1 to 34.

[0376] Aspect 39: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions which, when executed by one or more processors of a device, cause the device to perform the method according to one or more of aspects 1 to 34.

[0377] Aspect 40: A device for wireless communication, the device including a processing system comprising one or more processors and one or more memories coupled to the one or more processors, the processing system being configured to cause the device to perform the method according to one or more of aspects 1 to 34.

[0378] Aspect 41: An apparatus for wireless communication at a device, the apparatus comprising one or more memories and one or more processors coupled to the one or more memories, the one or more processors being individually or collectively configured to cause the device to perform one or more of the methods according to aspects 1 to 34.

[0379] While the foregoing disclosure provides examples and descriptions, it is not intended to be exhaustive or to limit aspects to the precise forms disclosed. Modifications and variations can be made based on the foregoing disclosure, or from various aspects of practice.

[0380] As used herein, the term "component" is intended to be interpreted broadly as hardware and / or a combination of hardware and software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other names, "software" should be interpreted broadly as meaning instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, and / or functions, etc. As used herein, a "processor" is implemented in hardware and / or a combination of hardware and software. It will be apparent that the systems and / or methods described herein can be implemented through various forms of hardware and / or combinations of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods is not limiting in any way. Therefore, no specific software code is referred to in this document to describe the operation and behavior of the systems and / or methods, as those skilled in the art will understand that the software and hardware can be designed, at least in part, based on the descriptions herein, to implement the systems and / or methods.

[0381] As used in this article, depending on the context, "meeting the threshold" can mean a value greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, etc.

[0382] Although specific combinations of features are set forth in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features may be combined in ways not specifically set forth in the claims and / or not disclosed in the specification. The disclosure of various aspects includes each dependent claim in combination with each other claim in the set of claims. As used herein, the phrase “at least one of” in the list of items refers to any combination of these entries, including a single member. As an example, “at least one of a, b, or c” is intended to cover a, b, c, a+b, a+c, b+c, and a+b+c, as well as any combination having multiple identical elements (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c, and c+c+c, or any other ordering of a, b, and c).

[0383] No element, action, or instruction used herein should be construed as essential or necessary unless explicitly stated otherwise. Furthermore, as used herein, the articles “a” and “an” are intended to include one or more items and are interchangeable with “one or more.” Similarly, as used herein, the article “the” is intended to include one or more items mentioned in connection with the article “the” and is interchangeable with “one or more.” Furthermore, as used herein, the terms “group” and “cluster” are intended to include one or more entries and are interchangeable with “one or more.” If only one item is desired, the phrase “only one” or similar terminology will be used. Additionally, as used herein, the terms “having” and the like are intended to be open-ended terms that do not limit the elements they modify (e.g., an element “having” A may also have B). Furthermore, the phrase “based on” is intended to mean “at least partially based on” unless otherwise explicitly stated. Additionally, as used herein, the term “or” is intended to be open-ended when used in a series and is interchangeable with “and / or” unless otherwise explicitly stated (e.g., if used in conjunction with “any” or “only one”).

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: One or more memory units; and One or more processors, said one or more processors coupled to said one or more memories, said one or more processors individually or collectively configured to cause the UE to: Select the services provided through the control plane; Send a message, the message including an indication of the service and the UE identifier (ID) of the UE; and Receive the configuration for the service.

2. The apparatus of claim 1, wherein the message includes a first protocol data unit (PDU) having a control plane transmission header, the control plane transmission header including the indication of the service and the UE ID.

3. The apparatus of claim 2, wherein the control plane transmission header is associated with a control plane transmission protocol layer, and wherein the first PDU is a service PDU associated with a service PDU protocol layer.

4. The apparatus of claim 3, wherein the one or more processors are individually or collectively configured to enable the UE to establish security for the UE by using security services and message reception at a security protocol layer between the control plane transport protocol layer and the service PDU protocol layer.

5. The apparatus of claim 4, wherein, in order to establish the security of the UE, the one or more processors are individually or jointly configured to cause the UE to select an authentication and security service, and wherein the indication of the service indicates the authentication and security service.

6. The apparatus of claim 5, wherein the first protocol data unit (PDU) comprises a non-access stratum (NAS) PDU.

7. The apparatus of claim 1, wherein the indication for the service includes a service ID.

8. The apparatus of claim 1, wherein the one or more processors are individually or jointly configured to associate the UE with service selection information of a service ID.

9. The apparatus of claim 8, wherein the service selection information includes a service selection ID.

10. The apparatus of claim 1, wherein the one or more processors are individually or collectively configured to cause the UE to transmit one or more Protocol Data Units (PDUs) associated with the use of the service via the control plane.

11. The apparatus of claim 1, wherein the one or more processors are individually or collectively configured to enable the UE to obtain a service ID for discovery and selection services, the discovery and selection services indicating available services on the control plane.

12. The apparatus of claim 11, wherein, in order to obtain the service ID of the discovery and selection service, the one or more processors are individually or jointly configured to cause the UE to receive the service ID in system information or via configuration.

13. The apparatus of claim 11, wherein, in order to obtain the service ID of the discovery and selection service, the one or more processors are individually or jointly configured to enable the UE to obtain a pre-configured service ID.

14. The apparatus of claim 1, wherein the one or more processors are individually or collectively configured to cause the UE to receive a service module ID associated with the service module.

15. The apparatus of claim 1, wherein the service is access and mobility service via the control plane.

16. The apparatus of claim 1, wherein the service is a data service provided through the control plane.

17. The apparatus of claim 1, wherein the service is a subscription service, a policy service via the control plane, or a network openness function via the control plane.

18. An apparatus for wireless communication at a first network entity, the apparatus comprising: One or more memory units; and One or more processors, coupled to one or more memories, wherein the one or more processors are individually or collectively configured to cause the first network entity to: Receive a message from the user equipment (UE), the message including an indication of services provided via the control plane and the UE's UE identifier (ID); and The message is forwarded to the address of the service, at least in part, based on the instruction given to the service.

19. The apparatus of claim 18, wherein the one or more processors are individually or collectively configured to cause the first network entity to map the address to the service.

20. The apparatus of claim 18, wherein the one or more processors are individually or collectively configured to cause the first network entity to send a configuration for the service to the UE.

21. The apparatus of claim 18, wherein the message includes a first protocol data unit (PDU) having a control plane transmission header, the control plane transmission header including the indication of the service and the UE ID.

22. The apparatus of claim 18, wherein the indication of the service includes service selection information associated with a service ID, and wherein the one or more processors are individually or jointly configured to cause the first network entity to: The service selection information, along with the request for the service ID, is sent to the second network entity that discovers and selects services; and The address or service ID of the service is received.

23. The apparatus of claim 22, wherein the one or more processors are individually or collectively configured to cause the first network entity to send the service ID to the UE.

24. The apparatus of claim 18, wherein the indication of the service includes a service selection ID, wherein the message includes a Non-Access Stratum (NAS) Protocol Data Unit (PDU), and wherein the one or more processors are individually or jointly configured to cause the first network entity to: Use the Service Selection ID to select Service Opening and Orchestration Function (SEOF); ​​and Forward the NAS PDU to the SEOF.

25. An apparatus for wireless communication at a second network entity, the apparatus comprising: One or more memory units; and One or more processors, said one or more processors coupled to said one or more memories, said one or more processors individually or collectively configured to cause the second network entity to: Receive service selection information associated with the service from the first network entity; and Send the service identifier (ID) associated with the service to the first network entity.

26. The apparatus of claim 25, wherein the one or more processors are individually or collectively configured to cause the first network entity to send the address of the service or the service profile of the service to the first network entity.

27. The apparatus of claim 26, wherein the service profile is used for discovering and selecting services or authentication and security services.

28. The apparatus of claim 25, wherein the one or more processors are individually or jointly configured to cause the first network entity to: Perform security checks on user equipment (UE); and Receive subscription information for the service.

29. An apparatus for wireless communication at a network entity, the apparatus comprising: One or more memory units; and One or more processors, coupled to one or more memories, wherein the one or more processors are individually or collectively configured to enable the network entity to: Receive a message, the message including an indication of services provided through the control plane and the UE identifier (ID) of the user equipment (UE); and Send the configuration for the service.

30. The apparatus of claim 29, wherein the one or more processors are individually or collectively configured to cause the network entity to send one or more Protocol Data Units (PDUs) associated with the use of the service via the control plane.

Images