Techniques for quality of service management for delivery of service information

Abstract

The invention relates to a method, a device and a computer readable medium for managing service information delivery in a network. A method according to an embodiment includes receiving a request for delivery of service information related to an artificial intelligence or machine learning service of a network, a computing or storage service of the network, or a delivery or location service of the network; generating a configuration for indicating delivery of the service information; and sending the configuration information to the entity to which the service information is to be sent.

Description

Technical Field

[0001] This application relates to wireless networks, and more specifically, to techniques for managing the quality of service for delivering service information within said networks. Background Technology

[0002] In current wireless networks, Quality of Service (QoS) facilitates the transmission of user data from source applications to target applications via a two-phase mapping process. Multiple Internet Protocol (IP) flows of user data from the application layer are mapped to different QoS flows by the User Plane Function (UPF). These QoS flows are then further mapped by the Serving Data Application Protocol (SDAP) layer to Data Radio Bearers (DRBs) at the Radio Access Network (RAN). Each DRB can be configured using settings / parameters to provide different radio processing to meet the QoS requirements of the traffic flows without over-provisioning radio resources. Attached Figure Description

[0003] Figure 1 Examples of network environments based on some implementation schemes are provided.

[0004] Figure 2 Examples of service flows based on some implementation schemes are provided.

[0005] Figure 3 This illustrates deployment scenarios based on some implementation schemes.

[0006] Figure 4 Examples of components of a network environment based on some implementation schemes are shown.

[0007] Figure 5 The network architectures based on some implementation schemes are illustrated.

[0008] Figure 6 The signaling diagrams are illustrated according to some implementation schemes.

[0009] Figure 7 Another signaling diagram based on some implementation schemes is shown.

[0010] Figure 8 Another signaling diagram based on some implementation schemes is shown.

[0011] Figure 9 Examples of components of a network environment based on some implementation schemes are shown.

[0012] Figure 10 Another network architecture based on some implementation schemes is illustrated.

[0013] Figure 11 Another network architecture based on some implementation schemes is illustrated.

[0014] Figure 12 Another network architecture based on some implementation schemes is illustrated.

[0015] Figure 13 Examples of components of a network environment based on some implementation schemes are shown.

[0016] Figure 14 Another network architecture based on some implementation schemes is illustrated.

[0017] Figure 15 Another network architecture based on some implementation schemes is illustrated.

[0018] Figure 16 Another network architecture based on some implementation schemes is illustrated.

[0019] Figure 17 Examples of components of a network environment based on some implementation schemes are shown.

[0020] Figure 18 Examples of components of a network environment based on some implementation schemes are shown.

[0021] Figure 19 Examples of protocol stacks based on some implementation schemes are shown.

[0022] Figure 20 Examples of components of a network environment based on some implementation schemes are shown.

[0023] Figure 21 Another network architecture based on some implementation schemes is illustrated.

[0024] Figure 22 Examples of user plane and control plane according to some implementation schemes are shown.

[0025] Figure 23 Examples of mapping operations based on some implementation schemes are provided.

[0026] Figure 24 The operational flow / algorithm structure according to some implementation schemes is illustrated.

[0027] Figure 25 Another operational flow / algorithm structure based on some implementation schemes is illustrated.

[0028] Figure 26 Another operational flow / algorithm structure based on some implementation schemes is illustrated.

[0029] Figure 27 Another operational flow / algorithm structure based on some implementation schemes is illustrated.

[0030] Figure 28 Examples of devices based on some implementation schemes are shown. Detailed Implementation

[0031] The following detailed description refers to the accompanying drawings. The same reference numerals may be used to identify the same or similar elements in different drawings. In the following description, specific details, such as particular structures, architectures, interfaces, and techniques, are set forth for illustrative and non-limiting purposes to provide a thorough understanding of various aspects of the various embodiments. However, it will be apparent to those skilled in the art that various aspects of the various embodiments may be practiced in other examples departing from these specific details. In some cases, descriptions of well-known devices, circuits, and methods have been omitted so as not to obscure the description of the various embodiments with unnecessary detail. For the purposes of this document, the phrases “A / B” and “A or B” refer to (A), (B), or (A and B); and the phrase “based on A” means “at least partially based on A,” for example, it can be “based solely on A” or it can be “partially based on A.”

[0032] The following is a glossary of terms that may be used in this disclosure.

[0033] As used herein, the term "circuit" refers to, is part of, or includes a hardware component configured to provide the described functionality. Hardware components may include electronic circuitry, logic circuitry, processors (shared, dedicated, or grouped) or memories (shared, dedicated, or grouped), application-specific integrated circuits (ASICs), field-programmable devices (FPDs) (e.g., field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), complex PLDs (CPLDs), high-capacity PLDs (HCPLDs), structured ASICs, or programmable system-on-a-chip (SoCs)), or digital signal processors (DSPs). In some embodiments, the circuit may execute one or more software or firmware programs to provide at least some of the described functionality. The term "circuit" may also refer to a combination of one or more hardware elements (or combinations of circuits used in electrical or electronic systems) and program code for executing the functionality. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuit.

[0034] As used herein, the term "processor circuit" means a circuit capable of sequentially and automatically performing a series of arithmetic or logical operations or recording, storing, or transmitting digital data; a part of a circuit capable of sequentially and automatically performing a series of arithmetic or logical operations or recording, storing, or transmitting digital data; or includes circuit capable of sequentially and automatically performing a series of arithmetic or logical operations or recording, storing, or transmitting digital data. The term "processor circuit" may also refer to an application processor, baseband processor, central processing unit (CPU), graphics processing unit, single-core processor, dual-core processor, triple-core processor, quad-core processor, or any other device capable of executing or otherwise operating computer-executable instructions (such as program code, software modules, and / or functional procedures).

[0035] As used herein, the term "interface circuit" refers to circuitry that enables the exchange of information between two or more components or devices, a portion thereof, or includes circuitry that enables the exchange of information between two or more components or devices. The term "interface circuitry" may refer to one or more hardware interfaces, such as buses, I / O interfaces, peripheral component interfaces, and network interface cards.

[0036] As used herein, the term "user equipment" or "UE" refers to equipment having radio communication capabilities that allow a user to access network resources within a communication network. The term "user equipment" or "UE" may be considered synonymous with and may be referred to as a client, mobile phone, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, or reconfigurable mobile device. Furthermore, the term "user equipment" or "UE" can include any type of wireless / wired equipment or any computing device that includes a wireless communication interface.

[0037] As used herein, the term "computer system" means any type of interconnected electronic device, computer device, or component thereof. Additionally, the term "computer system" or "system" may refer to various components of a computer that are communicatively coupled to each other. Furthermore, the term "computer system" or "system" may refer to multiple computer devices or multiple computing systems that are communicatively coupled to each other and configured to share computing resources or network resources.

[0038] As used herein, the term "resource" refers to a physical or virtual device, a physical or virtual component within a computing environment, or a physical or virtual component within a specific device, such as computer equipment, mechanical equipment, memory space, processor / CPU time, processor / CPU utilization, processor and accelerator load, hardware time or utilization, power, input / output operations, port or network sockets, channel / link allocation, throughput, memory utilization, storage, network, database and application, or workload unit. "Hardware resource" can refer to computing, storage, or network resources provided by physical hardware components. "Virtualized resource" can refer to computing, storage, or network resources provided by virtualization infrastructure to an application, device, or system. The terms "network resource" or "communication resource" can refer to resources accessible by a computer device / system via a communication network. The term "system resource" can refer to any kind of shared entity providing a service and can include computing or network resources. System resources can be considered as a coherent set of functions, network data objects, or services accessible through a server, wherein such system resources reside on a single host or multiple hosts and are clearly identifiable.

[0039] As used herein, the term "channel" refers to any tangible or intangible transmission medium used to transmit data or data streams. The term "channel" may be synonymous or equivalent with "communication channel," "data communication channel," "transmission channel," "data transmission channel," "access channel," "data access channel," "link," "data link," "carrier," "radio frequency carrier," or any other similar term indicating a means or medium through which data is transmitted. Additionally, as used herein, the term "link" refers to a connection between two devices for the purpose of transmitting and receiving information.

[0040] As used in this article, the terms "instantiate" and "instantiate" refer to the creation of an instance. "Instance" also refers to the concrete occurrence of an object, which may occur, for example, during the execution of program code.

[0041] The term "connection" can refer to an established signaling relationship between two or more elements at a common communication protocol layer through a communication channel, link, interface, or reference point.

[0042] As used herein, the term "network element" refers to physical or virtualized equipment or infrastructure used to provide wired or wireless communication network services. The term "network element" may be considered synonymous with or referred to as a networked computer, network hardware, network equipment, network node, or virtualized network function.

[0043] The term "information element" refers to a structural element that contains one or more fields. The term "field" refers to the individual content of an information element, or the data element that contains that content. An information element may include one or more additional information elements.

[0044] Figure 1 A network environment 100 according to some implementation schemes is illustrated. Network environment 100 may include user equipment (UE) 104 communicatively coupled to a base station 108 of a radio access network (RAN) 110. In some instances, base station 108 may be a next-generation (NG) RAN node, such as a gNB or ng-eNB. UE 104 and base station 108 may communicate via an air interface compatible with 3GPP TS, such as those defining sixth-generation (6G) or higher systems.

[0045] Network environment 100 may also include core network 112. For example, core network 112 may include a 6G or higher version core network (6GC). Core network 112 may be coupled to base station 108 via fiber optic or wireless backhaul. Core network 112 may provide functions to UE 104 via base station 108. These functions may include managing user profile information, user location, service authentication, switching functions for voice and data sessions, and routing and forwarding user plane packets between RAN 110 and external data network 120. RAN 110 and core network 112 may be collectively referred to as radio network 114.

[0046] In some implementations, the radio network 114 may provide services extended from existing fifth-generation (5G) services. For example, the radio network 114 may include immersive communications extended from enhanced mobile broadband (eMBB), ultra-reliable and low-latency communications (HRLLC) extended from ultra-reliable low-latency communications (URLCC), or massive communications extended from machine-type massive communications (mMTC). These services may be collectively referred to as communication services because they focus on transmitting user data from a source application to a target application via nodes of the radio network 114.

[0047] In some implementations, the radio network 114 may additionally / optionally support new services inherent to the nodes of the radio network 114. Services may include, for example, integrated artificial intelligence and communications, integrated sensing and communications, or ubiquitous connectivity. These services may be collectively referred to as network services as they may correspond to the overall characteristics of the radio network 114. The radio network 114 may provide local support for these network services by supporting information exchange between source and target nodes, wherein at least one of the source or target nodes resides in the radio network 114. Information exchange may include, for example, transmitting AI / machine learning (ML) models or datasets for training AI / ML models between the UE 104 and the nodes of the radio network 114; transmitting computational workloads or computation results between the UE 104 and the nodes of the radio network 114; or transmitting sensing results / measurements between the UE 104 and the nodes of the radio network 114.

[0048] Figure 2 This illustration depicts a service flow 200 between different source / destination nodes in a network environment 100 according to some implementation schemes. Service flow 200 represents some examples of transmitting service information in network environment 100. Other implementation schemes may include other examples.

[0049] Service flow 200 may include a first service flow (service flow #0) that includes sensed data as service information transmitted between application 204 on UE 104 and RAN 110. In some embodiments, application 204 may be the source of the sensed information, and RAN 110 may be the consumer. In these embodiments, the sensed data may enable RAN 110 to perform, for example, adjustments to improve the operation of the radio interface. In other embodiments, RAN 110 may be the source of the sensed data, and UE 104 may be the consumer.

[0050] Service flow 200 may additionally / optionally include a second service flow (service flow #1) that includes AI / ML data as service information transmitted between the access stratum (AS) and network function (NF#Y) 216 of UE 104. Service flow #1 may traverse other NFs of core network 112, such as NF #X 212. In some implementations, AS 208 may be the source of AI / ML data, and NF #Y 216 may be the consumer, or vice versa.

[0051] Service flow 200 may additionally / optionally include a third service flow (service flow #2), which includes computed data as service information transmitted between AS 208 of UE 104 and application 220 of another UE. In some embodiments, AS 208 may be the source of the computed data, and application 220 may be the consumer, or vice versa.

[0052] Therefore, each service flow in service flow 200 may include a source node or a destination node in radio network 114. Although not explicitly shown, some implementations may include service flows having both a source node and a destination node in radio network 114.

[0053] As described herein, providing service flow 200 to at least one of the source / target nodes in radio network 114 can be contrasted with user plane services in 5G networks, which are end-to-end (E2E) flows where information originates from one application and terminates in another.

[0054] QoS parameters for service information delivery (e.g., latency budget, target reliability, etc.) may vary significantly depending on the target consumer / task of the service. For example, the consumer of the service could be UE 104, a node of radio network 114, or an external application 220. For instance, the round-trip time (RTT) target for information delivery of AI or computing information for a first node could be within a first range (e.g., 1-50 milliseconds (ms)), while the information delivery for location services for a second node could be within a second range (e.g., 10-1000 ms).

[0055] Figure 3 Deployment scenario 300 of various parts of network environment 100 according to some implementation schemes is illustrated. In UE 104, multiple sensing sessions can be configured simultaneously to support different functions / consumers. Each sensing session can be associated with different RTT requirements. For example, a first session can be used for a first sensing service with a 50ms RTT, a second session can be used for a second sensing service with a 1000ms RTT, and a third session can be used for a third service with a 10ms RTT.

[0056] Core network 112 may include a Sensing Information Management Function (SensMF) 304 dedicated to managing sensing sessions. UE 104 can transmit all sensing results to SensMF 304. In a conventional network, all sensing data is transmitted as Non-Access Stratum (NAS) messages via dedicated signaling radio bearers (SRBs) (such as SRB2). This hinders the flexibility to adapt radio bearer settings to cope with services with different QoS requirements. To address this challenge, as well as other related challenges, the implementation provides techniques that enable flexible provisioning of differentiated QoS mapping and radio processing for the delivery of service information with different delivery targets.

[0057] The embodiments related to the first aspect of this disclosure describe QoS attributes and delivery methods for service information.

[0058] While existing QoS attributes are associated with the service data flow between external data network 120 and UE 104, some implementations provide QoS profiles specific to the delivery of service information. A QoS profile may include one or more of the following parameters.

[0059] The first parameter of the QoS profile can be the destination domain. The destination domain can indicate the domain where the target node (e.g., a consumer of service information) resides. For example, if the target node is in RAN 110, the destination domain can be set to RAN; if the target node is in core network 112, the destination domain can be set to core network; or if the target node is in external data network 120, the destination domain can be set to data network.

[0060] The second parameter of the QoS profile can be the preferred delivery plane. For example, various embodiments describe service information to be sent by the control plane, the user plane, or a service plane dedicated to the transmission of service information. The second parameter can indicate a preference for sending service information on one of these possible planes. In some embodiments, the selection of the preferred delivery plane can be based on the priority of the service information, the reliability of QoS attributes, the destination of the service information, etc.

[0061] The third parameter of the QoS profile can be a privacy attribute. For example, a privacy attribute could include an indication of whether anonymous delivery is supported. If anonymous delivery is supported, the routing network function can remove sender-specific information before delivering service information to the destination network function. In another example, a privacy attribute could include an indication of whether anonymous delivery is preferred. If anonymous delivery is preferred, the routing network function can be requested to remove sender-specific information before delivering service information to the destination network function. In yet another example, a privacy attribute could include an indication of preferred proxy delivery. If proxy delivery is preferred, the routing network function can be requested to replace the sender identifier with a self-assigned identifier. For example, the self-assigned identifier could be an identifier of the routing network function or another node on the path between the source and destination nodes. Traceability can be achieved through cooperation between the destination network function and the routing network function.

[0062] The fourth parameter of the QoS profile indicates whether delayed delivery is supported. If delayed delivery is supported, nodes forwarding service information can reduce the delivery priority of service information to support other data that may be more sensitive to latency.

[0063] Various delivery methods for service information can be defined to enable differentiated radio processing for different types of service information. Service information delivery methods can be categorized into one or more of the following classes.

[0064] In the first category (Category 1), service information may be delivered via the user plane. The delivery of service information via the user plane may be based on IP streams or non-IP streams, such as Ethernet or unstructured data.

[0065] In the second category (Category 2), service information can be delivered via a control plane that has control plane messages.

[0066] In the third category (Category 3), service information can be delivered via the control plane, where control plane messages offer the flexibility of QoS differentiation.

[0067] In the fourth category (Category 4), service information can be delivered via a user plane that has control plane messages.

[0068] In the fifth category (Category 5), service information can be delivered via a service plane dedicated to message exchange of service information.

[0069] The radio bearer mapping mechanisms used for each of these delivery method categories can be different, as described in further detail herein.

[0070] In some implementations, if radio network 114 supports two or more of the delivery method categories listed above, it may be necessary to select an appropriate delivery method. This selection can be performed by an entity involved in the transmission of service information. This entity can be UE 104, a node of radio network 114, or an external application / client. Specifically, the selection can be performed by an entity that requests such service information transmission, an entity that generates the service information to be transmitted, an entity that consumes the transmitted service information, or an entity that manages the transmission of service information.

[0071] In some embodiments, the selection of the delivery method may be based on or involve: which entity requests the delivery of service information, generates the information to be delivered, which entity consumes the delivered service information, which entity manages the delivery of service information, the QoS attributes of the service information (as described elsewhere herein), the need for QoS differentiation of such service information, or explicit indication / configuration.

[0072] The entity that performs the delivery method selection and related selection criteria described above can also apply to any other parameters of the QoS profile described elsewhere in this document.

[0073] The implementation scheme related to the second aspect of this disclosure describes the management of service information delivery using a direct interface.

[0074] Core network 112 may include one or more network functions dedicated to managing, for example, the delivery of service information between service information generators (also known as source nodes) and service information consumers (also known as target nodes). For example, in one embodiment, core network 112 may include: a Sensing Information Delivery Management Function (SIDMF) for managing the delivery of service information related to sensing services provided by radio network 114; an AI / ML Information Delivery Management Function (AMIDMF) for managing the delivery of service information related to AI / ML services provided by radio network 114; or a Computation / Storage Information Delivery Management Function (CSIDMF) for managing the delivery of service information related to computing / storage services provided by radio network 114.

[0075] Each of these Delivery Management Functions (DMFs) may need to manage the delivery of service information between RAN 110 and UE 104 (based on the delivery methods described elsewhere herein). The DMF may be able to perform one or more of the following operations: The DMF may receive requests for service information from consumers of service information (e.g., applications, nodes of wireless network 114, etc.). The DMF may respond to consumers of service information who have requested service information. The DMF may poll for the availability of service information at different entities. The DMF may configure entities to provide indications of available service information periodically or based on certain events. The DMF may determine the entities to generate service information flows. The DMF may determine the destination entity / node for each service information flow (e.g., UE 104, RAN 110, core network 112, or application 220). The DMF may determine / recommend QoS mappings for service information flows based on, for example, the QoS profiles of the service information. The DMF may determine / recommend radio bearer mappings for service information flows. The DMF may provide information to entities / nodes to assist in the configuration or radio resource allocation for service information delivery. This can include, for example, the periodicity of service information arrival, radio bearer mapping, or the (expected) size and jitter of the service information. The DMF can determine the method to be used for delivering the service information. This can be based on, for example, the desired destination. The DMF can provide service information to RAN 110 or UE 104 for transmission.

[0076] In some implementations, service information needs to be delivered only when a request exists. However, RAN 110 or UE 104 can always maintain appropriate DMF updates to determine whether such service information is available. This can be done by RAN 110 or UE 104 providing a service information availability indicator to the DMF. This can be done either initiated by RAN 110 or UE 104 or in response to a request from the DMF.

[0077] In some implementations, when service information is successfully delivered, RAN 110 or UE 104 may provide confirmation of successful delivery to the appropriate DMF.

[0078] Figure 4Component 400 of a network environment 100 according to some embodiments is illustrated. Component 400 may include a DMF 404, which is coupled to a service information generator 408 that provides service information and a service information consumer 412 that acts as a consumer of service information. The service information flow may traverse a first Uu node 416 and a second Uu node 420. The first Uu node may be coupled to the second Uu node 420 via an air interface, which may also be referred to as a Uu interface. In a downlink embodiment, the first Uu node 416 may correspond to a base station 108, and the second Uu node 420 may correspond to a UE 104. In an uplink embodiment, the first Uu node 416 may correspond to a UE 104, and the second Uu node 420 may correspond to a base station 108.

[0079] DMF 404 can receive requests for service information delivery. DMF 404 can then manage the delivery of service information from service information generator 408 to service information consumer 412 by providing information or instructions to one or more nodes to which the service information flow is to be traversed. In cases where the service information flow is to be traversed via an air interface, such as... Figure 4 As shown, DMF 404 can provide information / instructions to the first Uu node 416 or the second Uu node 420 to facilitate QoS implementation.

[0080] Although Figure 4 The service information generator 408 and the service information consumer 412 are shown as entities distinct from the first Uu node 416 and the second Uu node, but in other embodiments, the Uu node may generate or consume service information.

[0081] Figure 5 An example of a network architecture 500 including components of a network environment 100 according to some implementation schemes is shown.

[0082] The core network 112 may include an Access and Mobility Management Function (AMF) 504 coupled to the UE 104 and the base station 108. The AMF 504 may be a control plane function that provides registration management, connection management, reachability management, and mobility management services.

[0083] Core network 112 may also include a Session Management Function (SMF) 508 coupled to User Plane Function (UPF) 512. SMF 508 can be configured with service orientation, QoS control, and policy-related functions, performing Protocol Data Unit (PDU) session management, IP address allocation, General Packet Radio Service Tunneling Protocol-User Plane (GTP-U) tunnel management, user plane function selection and control, and downlink notification management. UPF 512 can provide routing and forwarding of user plane packets from (or to) data network 120. Core network 112 may include one or more additional Network Functions (NFs) 516.

[0084] Core network 112 may also include SIDMF 520 for managing the delivery of service information related to sensing services, AMIDMF 524 for managing the delivery of service information related to AI / ML services, or CSIDMF 528 for managing the delivery of service information related to computing / storage services provided by radio network 114. Each of SIDMF 520, AMIDMF 524, and CSIDMF 528 may have a direct logical interface to UE 104 and a direct logical interface to RAN 110 (e.g., BS 108). The direct logical interface may be enabled by the protocol layer of the DMF communicating with the corresponding protocol layer of UE 104 or RAN 110. Service information protocols may be used for communication between corresponding protocol layers.

[0085] Figure 6 This is an example of a signaling diagram 600 illustrating the delivery management of service information according to some implementation schemes. The signaling diagram 600 can occur between UE 104, BS 108, and DMF 604, where DMF can be SIDMF 520, AMIDMF 524, or CSIDMF 528.

[0086] exist Figure 6 In this configuration, UE 104 can operate as a service information generator, providing, for example, sensing results measured by the physical layer of UE 104. Service information consumers can reside in the network. For example, base station 108 can use the sensing results for resource allocation purposes. In this case, UE 104 can deliver service information to base station 108.

[0087] Signaling diagram 600 may include, at 608, UE 104 providing an indication to DMF 604 that service information is available. In some implementations, UE 104 may be configured to provide an indication of service information availability periodically or based on the detection of a triggering event (e.g., when UE 104 receives a request for information or when the information becomes available).

[0088] Signaling diagram 600 may further include, at 612, DMF 604 receiving a request for delivery of service information and determining delivery parameters associated with the delivery of the service information. Delivery parameters may include, for example, the QoS level of the service information and the delivery method.

[0089] In some implementations, the receipt of a request for delivery service information may be independent of the receipt of an SI availability indication, and may originate from different entities. Upon receiving a request for delivery service information, if the service information is not yet available, DMF 604 may transmit a request to UE 104 to generate the service information at 616.

[0090] Then, signaling diagram 600 may include: at 620, DMF 604 transmits air interface configuration to base station 108 to request or recommend that base station 108 allocate appropriate uplink resources to UE 104 to complete the delivery of service information over the air interface consistent with the delivery parameters determined at 612. For example, the air interface configuration may provide instructions / rules to meet QoS objectives associated with the service information. Then, at 624, base station 108 may provide uplink resource allocation to UE 104.

[0091] Signaling diagram 600 may further include, at 628, a request from DMF 604 to UE 104 for uplink transmission of service information. This request may include instructions on how UE 104 should deliver the service information, such as which radio bearer should be selected to transmit the service information or which transmission method category should be applied. In some implementations, the request at 628 may be transmitted along with the air interface configuration at 620 and the UL resource allocation at 624.

[0092] Signaling diagram 600 may further include: at 636, UE 104 prepares service information and selects uplink resources, as configured in the allocation sent at 624. At 640, UE 104 may send service information to base station 108. If necessary, base station 108 may forward the service information to another node in RAN 110 or core network 112.

[0093] Signaling diagram 600 may also include: at 640, base station 108 transmits an acknowledgment to DMF 604 to confirm that it has successfully received the service information. It can be noted that the service information itself may or may not reach DMF 604.

[0094] Figure 7 This is an example of a signaling diagram 700 illustrating the delivery management of service information according to some implementation schemes. Signaling diagram 600 may occur between UE 104, base station 108, and DMF 604.

[0095] exist Figure 7In this system, base station 108 can operate as a service information generator, and UE 104 can operate as a service information consumer.

[0096] Signaling diagram 700 may include: at 708, base station 108 provides DMF 604 with an indication that service information is available. In some embodiments, base station 108 may be configured to provide an indication of service information availability periodically or based on the detection of a triggering event (e.g., when base station 108 receives a request for information or when information becomes available).

[0097] Signaling diagram 700 may further include, at 712, DMF 604 receiving a request for delivery of service information and determining delivery parameters associated with the delivery of the service information. Delivery parameters may include, for example, the QoS level of the service information and the delivery method.

[0098] In some implementations, the receipt of a request for delivery service information may be independent of the receipt of an SI availability indication, and may originate from different entities. Upon receiving a request for delivery service information, if the service information is not yet available, DMF 604 may transmit a request to generate service information to base station 108 at 716.

[0099] Then, signaling diagram 700 may include: at 720, DMF 604 transmits air interface configuration to base station 108 to request or recommend that base station 108 allocate appropriate downlink resources to complete the delivery of service information over the air interface consistent with the delivery parameters determined at 712. For example, the air interface configuration may provide instructions / rules to meet QoS objectives associated with the service information. The message transmitted at 720 may also include a request for base station 108 to continue downlink transmission of the service information. This request may include instructions on how base station 108 should deliver the service information, such as which radio bearer should be selected to transmit the service information or which transmission method category should be applied.

[0100] Then, at 724, base station 108 can provide downlink resource allocation to UE 104. If downlink resources are already available, base station 108 can skip resource allocation.

[0101] At 728, signaling diagram 700 may also include base station 108 preparing service information and selecting downlink resources. At 732, base station 108 may send service information to UE 104. If necessary, UE 104 may forward the service information to another node at 734.

[0102] Signaling diagram 700 may also include: at 736, UE 104 sends an acknowledgment to DMF 604 to confirm that it has successfully received the service information. It can be noted that the service information itself may or may not reach DMF 604.

[0103] Figure 8 This is an example of a signaling diagram 800 illustrating the delivery management of service information according to some implementation schemes. The signaling diagram 800 may occur between UE 104, base station 108, DMF 604 and NF 804 of core network 112.

[0104] exist Figure 8 In this context, NF 804 can operate as a service information generator, and UE 104 can operate as a service information consumer.

[0105] Signaling diagram 800 may include, at 808, NF 804 providing DMF 604 with an indication that service information is available. In some implementations, NF 804 may be configured to provide an indication of service information availability periodically or based on the detection of a triggering event (e.g., when NF 804 receives a request for information or when the information becomes available).

[0106] Signaling diagram 800 may also include, at 812, DMF 604 receiving a request for delivery of service information and determining delivery parameters associated with the delivery of the service information. Delivery parameters may include, for example, the QoS level of the service information and the delivery method.

[0107] In some implementations, the receipt of a request for delivery service information may be independent of the receipt of an SI availability indication, and may originate from different entities. Upon receiving a request for delivery service information, if the service information is not yet available, DMF 604 may transmit a request to NF 804 at 816 to generate the service information.

[0108] Then, signaling diagram 800 may include: at 820, DMF 604 transmits air interface configuration to base station 108 to request or recommend that base station 108 allocate appropriate downlink resources to complete the delivery of service information over the air interface consistent with the delivery parameters determined at 812. For example, the air interface configuration may provide instructions / rules to meet QoS objectives associated with the service information.

[0109] Then, at 824, base station 108 can provide downlink resource allocation to UE 104. If downlink resources are already available, base station 108 can skip resource allocation.

[0110] At 828, signaling diagram 800 may also include NF 804 preparing service information. At 832, NF 804 may send service information to base station 108, which may then forward the service information to UE 104 at 836 using allocated downlink resources. If necessary, UE 104 may forward the service information to another node at 840.

[0111] Signaling diagram 800 may also include: at 844, UE 104 sends an acknowledgment to DMF 604 to confirm that it has successfully received the service information. It can be noted that the service information itself may or may not reach DMF 604.

[0112] The embodiments related to the third aspect of this disclosure describe QoS mapping for downlink service information in the absence of a direct interface. Similar to what was discussed above with respect to the second aspect, core network 112 may include one or more network functions dedicated to managing sensing services, AI / ML services, or compute / storage services. However, for the third aspect, these network functions may not have a direct logical connection to RAN 110 or UE 104. Furthermore, in some cases, service information may be generated outside of radio network 114 or UE 104 and delivered to nodes of radio network 114 or UE 104, as controlled by new service management functions in core network 112.

[0113] To facilitate this operation, the implementation describes the QoS mapping of service information before it arrives at RAN 110 for further transmission via the air interface. This can be accomplished by a UPF that obtains the QoS mapping policy associated with the service information from the management function. The management function can be dedicated to a specific service type, a general service information management function that oversees all service types, or an SMF.

[0114] UPF can perform service orientation to route service information to a target destination, and it can also be configured by one of the management functions listed above. Such configuration enables service information flows to reach target destinations, such as RAN 110, UE 104, or within the application.

[0115] As will be described in further detail herein, service information can be provided to the UPF via management functions for each new service type in the corresponding new service type or new service information processing functions that act as a processing center for service information.

[0116] Figure 9Component 900 of a network environment 100 according to some implementation schemes is illustrated. Component 900 may include a UPF 904 of the core network 112, a data network 120, and a Service Information Processing Function (SIPF) 908. Unless otherwise described, UPF 904 may be similar to that described above with respect to UPF 512.

[0117] The UPF 904 can receive IP streams from DN 120 via the N6 interface. The IP streams may include information generated from external applications. The UPF 904 can also receive service information streams from the SIPF 908 via an interface (e.g., a service-based interface).

[0118] The UPF 904 can perform QoS mapping to map received flows to multiple QoS flows, such as QoS flow #1, QoS flow #2, and QoS flow #3. QoS mapping can be based on an obtained QoS mapping policy. The QoS flows can be transmitted to RAN 110 for delivery.

[0119] Therefore, compared to existing UPFs that only perform QoS flow mapping on services from DNs, UPF 904 can also perform QoS flow mapping on service information from entities not in DN 120 (e.g., entities in core network 112).

[0120] Figure 10 A network architecture 1000 including components of a network environment 100 according to some implementation schemes is illustrated. Unless otherwise described herein, components may be similar to components with the same names described elsewhere herein.

[0121] In network architecture 1000, service-specific management functions (e.g., SIDMF 520, AMIDMF 524, and CSIDMF528) can provide QoS mapping policies and service orientation (QMP / TS) parameters for service information to the UPF 904. The SIPF 908 can receive service information generated from an internal NF via the SBI or a direct connection to the NF, and can provide this service information as one or more service information streams to the UPF 904. The UPF 904 can then perform QoS mapping to map the service information streams received from the SIPF 908 to QoS streams, as referenced above. Figure 9 As described.

[0122] Figure 11 A network architecture 1100 including components of a network environment 100 according to some implementation schemes is illustrated. Unless otherwise described herein, components may be similar to components with the same names described elsewhere herein.

[0123] In network architecture 1100, the Service Information Management Function (SIMF) 1104 can perform service information management functions for all service types (e.g., sensing, AI / ML, and compute / storage services). SIMF 1104 can provide UPF 904 with QoS mapping policies and service orientation (QMP / TS) parameters for service information. SIPF 908 can receive service information generated from an internal NF via SBI or a direct connection to the NF, and can provide the service information as one or more service information streams to UPF 904. UPF 904 can then perform QoS mapping to map the service information streams received from SIPF 908 to QoS streams, as referenced above. Figure 9 As described.

[0124] Figure 12 A network architecture 1200 including components of a network environment 100 according to some implementation schemes is illustrated. Unless otherwise described herein, components may be similar to components with the same names described elsewhere herein.

[0125] In Network Architecture 1200, DMF 404 performs service information management functions for service types (e.g., sensing, AI / ML, and compute / storage services). DMF 404 can represent individual management functions, such as SIDMF 520, AMIDMF524, or CSIDMF, or general management functions, such as SIMF 1104.

[0126] In this configuration, the SMF 508 can provide the UPF 904 with QoS mapping policies and service orientation (QMP / TS) parameters for service information. QMP / TS parameters can be provided via the N4 interface. The SIPF 908 can receive service information generated from an internal NF via the SBI or a direct connection to the NF, and can provide this service information as one or more service information streams to the UPF 904. The UPF 904 can then perform QoS mapping to map the service information streams received from the SIPF 908 to QoS streams, as referenced above. Figure 9 As described.

[0127] In some implementations, instead of using UPF, the Service Information Mapping Function (SIMPF) can be used to map service information flows to QoS flows.

[0128] SIMPF can obtain QoS mapping policies for service information from management functions. Management functions can be dedicated to specific service types, general service information management functions that oversee all service types, or SMF.

[0129] SIMPF can perform service orientation to route service information to a target destination, and it can also be configured by one of the management functions listed above. Such configuration enables service information flows to reach target destinations such as RAN 110, UE 104, or within the application.

[0130] As will be further described herein, service information can be provided to SIMPF via management functions for each of the corresponding new service types or by SIPF acting as a processing center for service information.

[0131] Figure 13 Component 1300 of a network environment 100 according to some implementation schemes is illustrated. Component 1300 may include UPF 512 of core network 112, data network 120 and SIMPF 1304.

[0132] The UPF 512 can receive IP flows from DN 120 via the N6 interface. The IP flows may include information generated from external applications. The UPF 512 can perform QoS mapping to map the received IP flows to multiple QoS levels, such as QoS flow #1 and QoS flow #2.

[0133] SIMPF 1304 can receive service information streams from SIPF 908 via an interface (e.g., a service-based interface). SIMPF 1304 can perform QoS mapping to map the received service information streams to multiple QoS streams, such as QoS stream #3 and QoS stream #4. QoS mapping can be based on an acquired QoS mapping policy.

[0134] QoS streams from UPF 512 and SIMPF 1304 can be transmitted to RAN 110 for transmission.

[0135] Figure 14 A network architecture 1400 including components of a network environment 100 according to some implementation schemes is illustrated. Unless otherwise described herein, components may be similar to components with the same names described elsewhere herein.

[0136] In network architecture 1400, service-specific management functions (e.g., SIDMF 520, AMIDMF 524, and CSIDMF528) can provide QoS mapping policies and service orientation (QMP / TS) parameters for service information to the SIMPF 1304. The SIMPF 1304 can receive service information streams from the SIPF 908, which receives service information generated from internal NFs via the SBI or a direct connection to the NF. The SIMPF 1304 can then perform QoS mapping to map the service information streams received from the SIPF 908 to QoS streams, as referenced above. Figure 9 As described.

[0137] UPF 512 can perform QoS mapping to map IP flows received from data network 120 to QoS flows, as described above. Figure 9 As described.

[0138] Figure 15 A network architecture 1500, including components of a network environment 100, is illustrated according to some implementation schemes. Unless otherwise described herein, components may be similar to components with the same names described elsewhere herein.

[0139] In network architecture 1500, SIPF 1204 can provide SIMPF 1304 with QoS mapping policies and service orientation (QMP / TS) parameters for service information. SIPF 908 can receive service information generated from an internal NF via SBI or a direct connection to the NF, and can provide the service information as one or more service information streams to SIMPF 1304. SIMPF 1304 can then perform QoS mapping to map the service information streams received from SIPF 908 to QoS streams, as referenced above. Figure 9 As described.

[0140] UPF 512 can perform QoS mapping to map IP flows received from data network 120 to QoS flows, as described above. Figure 9 As described.

[0141] Figure 16 A network architecture 1600, including components of a network environment 100, is illustrated according to some implementation schemes. Unless otherwise described herein, components may be similar to components with the same names described elsewhere herein.

[0142] In Network Architecture 1600, DMF 404 performs service information management functions for service types (e.g., sensing, AI / ML, and compute / storage services). DMF 404 can represent individual management functions, such as SIDMF 520, AMIDMF524, or CSIDMF 528, or general management functions, such as SIMF 1104.

[0143] In this configuration, the SMF 508 can provide the UPF 904 with QoS mapping policies and service orientation (QMP / TS) parameters for service information. QMP / TS parameters can be provided via the N4 interface. The SIMPF 1304 can receive service information generated from the internal NF as one or more service information streams via the DMF 404. The SIMPF 1304 can perform QoS mapping to map the service information streams received from the DMF 404 to QoS streams, as referenced above. Figure 9 As described.

[0144] UPF 512 can perform QoS mapping to map IP flows received from data network 120 to QoS flows, as described above. Figure 9 As described.

[0145] The implementation related to the fourth aspect of this disclosure describes uplink radio bearer mapping service information.

[0146] Figure 17 Component 1700 of a network environment 100 performing RRC bearer mapping is illustrated according to some implementation schemes. The RRC bearer mapping performed by component 1700 may correspond to a Category 3 delivery method, in which service information is delivered as a control plane message with QoS differentiation.

[0147] Component 1700 may include a protocol layer of UE 104, such as NAS layer 1704, for example, coupled to RRC layer 1708. NAS layer 1704 may be communicatively coupled to a corresponding NAS layer in any network function of core network 112. In some embodiments, NAS layer 1704 may represent multiple NAS layers. NAS layer 1704 may provide regular NAS messages to RRC layer 1708. RRC layer 1708 may map all regular NAS messages to SRB-2, consistent with normal operation.

[0148] The NAS layer 1704 can also provide service information flows to the RRC layer 1708. To provide QoS differentiation, the RRC layer 1708 can map service information flows to different SRBs, where different SRBs are configured to provide different radio processing. The RRC layer 1708 can map service information flows to SRBs based on pre-configured SIB mapping rules used for service information. The mapping can be static or configured by the network.

[0149] Figure 18 Component 1800 of a network environment 100 performing RRC bearer mapping is illustrated according to some implementation schemes. The RRC bearer mapping performed by component 1800 may correspond to a Category 3 delivery method, in which service information is delivered as a control plane message with QoS differentiation.

[0150] Component 1800 may include protocol layers of UE 104, such as distributed NAS (e.g., first NAS layer 1804 and second NAS layer 1808) and AS layer 1812 coupled to RRC layer 1816.

[0151] The first NAS layer 1804 can be communicatively coupled to the corresponding NAS layer in the AMF of the core network 112, and can provide regular NAS messages to the RRC layer 1816. The RRC layer 1708 can map all regular NAS messages to SRB-2, consistent with normal operation.

[0152] The second NAS layer 1808 can be coupled to the corresponding NAS layer in the core network 112 and can provide service information flow to the RRC layer 1816.

[0153] AS layer 1812 may be a layer or entity designated for processing service information (e.g., service information adaptation). AS layer 1812 may be communicatively coupled to a corresponding NAS layer in RAN 110. In various embodiments, AS layer 1812 may be a Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, Media Access Control (MAC) layer, and physical layer. AS layer 1812 may provide service information flows to RRC 1816.

[0154] To provide QoS differentiation, RRC layer 1816 can map service information flows from the second NAS layer 1808 and AS layer 1812 to different SRBs, where different SRBs are configured to provide different radio processing. RRC layer 1816 can map service information flows to SRBs based on pre-configured SIB mapping rules used for service information. The mapping can be static or can be configured by the network.

[0155] Figure 19 An example of a protocol layer stack 1900 for bearer mapping of control plane messages according to some implementation schemes is shown.

[0156] Protocol layer stack 1900 may include NAS 1904, Service Information Adaptation Layer (SIAL) 1908, RRC 1912, PDCP 1916, RLC 1920, MAC 1924, and PHY 1928.

[0157] In some implementations, SIAL 1908 may be positioned between NAS 1904 and RRC 1912. SIAL 1908 can process service information from NAS 1904 or a lower AS layer. For example, if the service information is generated based on radio measurements performed by PHY 1928, SIAL 1908 can receive the service information from PHY 1928.

[0158] In various implementations, SIAL 1908 can map service information flows from NAS 1904 to appropriate QoS flows, service information flows from AS to appropriate QoS flows, or service information flows from NAS / AS to appropriate radio bearers (in which case, PDUs from SIAL 1908 can bypass RRC 1912).

[0159] For regular NAS messages, SIAL 1908 can be bypassed, and NAS 1904 can pass them directly to RRC1912.

[0160] Figure 20 Component 2000 of a network environment 100 performing user plane bearer mapping for service information is illustrated according to some implementation schemes. The user plane bearer mapping performed by component 2000 may correspond to a Category 1 delivery method, wherein service information is delivered via the user plane.

[0161] Component 2000 may include Application 2004, Service Plane Function (SPF) 2008, and AS 2012 coupled to SDAP 2016. Application 2004 provides user data information QoS flows to SDAP 2016. SPF 2008 and the AS layer provide service information QoS flows to SDAP 2016. SDAP 2016 may be able to map both user data QoS flows and service information QoS flows to the DRB.

[0162] Figure 21 A network architecture 2100 including components of a network environment 100 according to some implementation schemes is illustrated. Unless otherwise described herein, components may be similar to components with the same names described elsewhere herein.

[0163] Network architecture 2100 may include control plane AS protocol 2104 to provide E2E connectivity between UE 104 and AMF 504.

[0164] Network architecture 2100 may also include a service plane AS protocol 2108, which defines a radio protocol for the delivery of service information. This can be used to provide E2E connectivity between UE 104 and management functions such as SIDMF 520, AMIDMF 524, and CSIDMF 528, or a generic SIMF, as shown in the figure.

[0165] Network architecture 2100 may also include user plane AS protocol 2112 to provide E2E connectivity between UE 104 and UPF 904.

[0166] Figure 22User plane 2200 and control plane 2204 are provided, according to some implementation schemes, to support bearer mapping for service information.

[0167] User plane 2200 may include UPF 512 to provide user data information QoS flows to SDAP 2208. SDAP 2208 can map QoS flows to various DRBs.

[0168] The control plane 2204 may include a service information function 2210 and an AS layer that provides service information QoS flows to the new SDAP 2216. The new SDAP 2216 can then map the service information QoS flows to radio bearers with appropriate radio processing.

[0169] Figure 23 An example of a mapping operation 2300 for segmented bearers that allows for QoS differentiation of service information according to some implementation schemes is illustrated.

[0170] Mapping operation 2300 may include mapping multiple service information QoS flows onto a single radio bearer. In some implementations, both user data flows and service information flows may be mapped onto a single radio bearer. PDCP 2308 may provide differentiated processing by providing different flows within the radio bearer to different RLCs. For example, PDCP 230 may provide a first flow to RLC1 2312 and a second flow to RLC2 2316.

[0171] Figure 24 An operational flow / algorithm structure 2400 is provided according to some implementation schemes. The operational flow / algorithm structure 2400 can be executed by a node or device 2800 of the network environment 100 or its components (e.g., processor 2804).

[0172] The operation process / algorithm structure 2400 may include, at 2404, generating a QoS profile associated with the delivery of service information. The QoS profile may indicate the destination domain of the service information, the preferred delivery plane of the service information, the preferred delivery method of the service information, or privacy attributes associated with the delivery of the service information.

[0173] The operation flow / algorithm structure 2400 may also include sending the QoS profile to the nodes of the cellular network at 2408. In some implementations, the entire QoS profile may be sent to a single node. In other implementations, the selected parameters of the QoS profile may be sent to the individual nodes.

[0174] Figure 25An operational flow / algorithm structure 2500 is provided according to some implementation schemes. The operational flow / algorithm structure 2500 can be executed by a node or device 2800 of the network environment 100 or its components (e.g., processor 2804).

[0175] The operation flow / algorithm structure 2500 may include receiving a request for the delivery of service information at 2504. The request can be received from the entity through a direct logical interface or an indirect logical interface. The service information may be related to the network's AI / ML services, the network's computing / storage services, or the network's sensing / location services.

[0176] The operation flow / algorithm structure 2500 may also include generating configuration information at 2508 to indicate the delivery of service information. In some implementations, the configuration information may indicate the periodicity of service information arrival, the radio bearer mapping for the service information, the expected size of the service information, or jitter information associated with the service information.

[0177] In some implementations, the configuration information can be configured to configure the air interface on which service information is to be sent.

[0178] The operation flow / algorithm structure 2500 may also include sending configuration information at 2512 to the entity that will send service information. The entity can be the source of the service information or a node that sends service information through it.

[0179] In some implementations, the operation process / algorithm structure 2500 may be executed by an entity that requests service information, an entity that generates service information, an entity that consumes service information, or an entity that manages the delivery of service information.

[0180] Figure 26 An operational flow / algorithm structure 2600 is provided according to some implementation schemes. The operational flow / algorithm structure 2600 can be executed by a node or device 2800 of the network environment 100 or its components (e.g., processor 2804).

[0181] The operation flow / algorithm structure 2600 may include receiving a QoS mapping policy for service information at 2604. In some implementations, the QoS mapping policy may be received from the SIPF of the core network, and the service information may originate from the core network.

[0182] The operation process / algorithm structure 2600 may also include receiving service information at 2608.

[0183] The operation process / algorithm structure 2600 may also include mapping service information to QoS flows based on the QoS mapping strategy at 2608.

[0184] Figure 27An operational flow / algorithm structure 2700 is provided according to some implementation schemes. The operational flow / algorithm structure 2700 can be executed by a node or device 2800 of the network environment 100 or its components (e.g., processor 2804).

[0185] The operation process / algorithm structure 2700 may include receiving service information at the first layer of the UE at 2704. The service information may be related to the network's AI / ML services, the network's computing / storage services, or the network's sensing / location services.

[0186] The operation flow / algorithm structure 2700 may also include mapping service information to QoS flows or radio bearers at 2708. The mapping may be based on the identified mapping rules.

[0187] In some implementations, the first layer may be the RRC layer, which maps service information to signaling radio bearers. The RRC layer may receive service information streams from the NAS or AS layer of the UE / device. In some implementations, the RRC layer may receive service information streams from the service information adaptation layer of the UE / device.

[0188] In some implementations, the first layer may be a service information adaptation layer that receives service information streams from the NAS layer or the AS layer.

[0189] In some implementations, the first layer may be an SDAP layer that receives service information streams as QoS streams and maps the QoS streams to DRBs.

[0190] The operation process / algorithm structure 2700 may also include using QoS streams or radio bearers at 2708 to send service information.

[0191] Figure 28 An example of device 2800 is shown according to some implementation schemes. Device 2800 may be UE 104, base station 108 or other nodes of RAN 110, or a node of core network 112.

[0192] Device 2800 may include a processor 2804, RF interface circuitry 2808, memory / storage device 2812, user or CN interface 2816, sensor 2820, drive circuitry 2822, power management integrated circuit (PMIC) 2824, antenna structure 2826, and battery 2828. Components of device 2800 may be implemented as integrated circuits (ICs), portions of integrated circuits, discrete electronic devices or other modules, logic components, hardware, software, firmware, or combinations thereof. Figure 28 The block diagram is intended to show a high-level view of some of the components of the device 2800. However, some of the components shown may be omitted, additional components may be present, and different arrangements of the components shown may occur in other specific implementations.

[0193] The components of device 2800 can be coupled to various other components via one or more interconnects 2832, which can represent any type of interface, input / output, bus (local, system, or extension), transmit line, trace, optical connection, etc., allowing various circuit components (on common or different chips or chipsets) to interact with each other.

[0194] Processor 2804 may include processor circuitry, such as, for example, baseband processor circuitry (BB) 2804A, central processing unit circuitry (CPU) 2804B, and graphics processing unit circuitry (GPU) 2804C. Processor 2804 may include any type of circuitry or processor circuitry that executes or otherwise operates computer-executable instructions (such as program code, software modules, or functional processes from memory / storage device 2812) to cause device 2800 to perform operations of the UE with respect to the AI ​​model as described herein.

[0195] In some implementations, the baseband processor circuit 2804A can access the communication protocol stack 2836 in the memory / storage device 2812 to communicate over a 3GPP-compliant network. Generally, the baseband processor circuit 2804A can access the communication protocol stack to perform user plane functions at the PHY, MAC, RLC, PDCP, SDAP, and PDU layers; and control plane functions at the PHY, MAC, RLC, PDCP, RRC, and non-access layer layers. In some implementations, PHY layer operation may additionally / optionally be performed by components of the RF interface circuit 2808.

[0196] The baseband processor circuit 2804A can generate or process baseband signals or waveforms carrying information in a 3GPP-compliant network. In some implementations, the waveforms used for NR can be based on cyclic prefix OFDM (CP-OFDM) in the uplink or downlink, and Discrete Fourier Transform Extended OFDM (DFT-S-OFDM) in the uplink.

[0197] Memory / storage device 2812 may include one or more non-transitory computer-readable media, including instructions (e.g., communication protocol stack 2836) that can be executed by one or more processors in processor 2804 to cause device 2800 to perform the various operations described herein. Memory / storage device 2812 includes any type of volatile or non-volatile memory that can be distributed throughout device 2800. In some embodiments, some memory / storage devices in memory / storage device 2812 may be located on processor 2804 itself (e.g., L1 cache and L2 cache), while other memory / storage devices 2812 are external to processor 2804 but accessible via a memory interface. Memory / storage device 2812 may include any suitable volatile or non-volatile memory, such as, but not limited to, dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state memory, or any other type of memory device technology.

[0198] RF interface circuitry 2808 may include transceiver circuitry and a radio frequency front-end module (RFEM) that allows device 2800 to communicate with other devices via a radio access network. RF interface circuitry 2808 may include various components arranged in the transmit or receive path. These components may include, for example, switches, mixers, amplifiers, filters, synthesizer circuitry, control circuitry, etc.

[0199] In the receiving path, the RFEM can receive the radiated signal from the air interface via antenna structure 2826, and continue to filter and amplify the signal (using a low-noise amplifier). The signal can be provided to the receiver of the transceiver, which down-converts the RF signal into a baseband signal that is provided to the baseband processor of processor 2804.

[0200] In the transmission path, the transceiver's transmitter up-converts the baseband signal received from the baseband processor and provides the RF signal to the RFEM. The RFEM can then amplify the RF signal using a power amplifier before it is radiated across the air interface via antenna structure 2826.

[0201] In various implementations, the RF interface circuit 2808 can be configured to transmit / receive signals in a manner compatible with NR access technologies.

[0202] Antenna structure 2826 may include antenna elements for converting electrical signals into radio waves to travel through the air and for converting received radio waves back into electrical signals. These antenna elements may be arranged in one or more antenna panels. Antenna structure 2826 may have omnidirectional, directional, or combinations thereof antenna panels to enable beamforming and multiple-input multiple-output communication. Antenna structure 2826 may include microstrip antennas, patch antennas, phased array antennas, printed antennas fabricated on the surface of one or more printed circuit boards, etc. Antenna structure 2826 may have one or more panels designed for a specific frequency band included in FR1 or FR2.

[0203] User or CN interface 2816 can be a user interface that includes various input / output (I / O) devices designed to enable a user to interact with device 2800. The user interface includes input device circuitry and output device circuitry. Input device circuitry includes any physical or virtual components for accepting input, particularly including one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, a keypad, a mouse, a touchpad, a touchscreen, a microphone, a scanner, or a head-mounted device. Output device circuitry includes any physical or virtual components for displaying information or otherwise conveying information, such as sensor readings, actuator positions, or other similar information. Output device circuitry can include any number or combination of audio or visual displays, particularly including one or more simple visual outputs / indicators (e.g., binary status indicators, such as light-emitting diodes "LEDs," and multi-character visual outputs), or more complex outputs such as display devices or touchscreens (e.g., liquid crystal displays (LCDs), LED displays, quantum dot displays, projectors, etc.), where the output of characters, graphics, multimedia objects, etc., is generated or produced by the operation of device 2800.

[0204] The user or CN interface 2816 may be a CN interface that provides connectivity to a core network (e.g., core network 112) using a network interface protocol such as Carrier Ethernet or some other suitable protocol. Network connectivity may be provided to / from device 2800 via fiber optic or wireless backhaul. The CN interface may include one or more dedicated processors or FPGAs for communicating using one or more of the aforementioned protocols. In some implementations, the CN interface may include multiple controllers for providing connectivity to other networks using the same or different protocols.

[0205] Sensor 2820 may include devices, modules, or subsystems designed to detect events or changes in their environment and transmit information about the detected events (sensor data) to other devices, modules, subsystems, etc. Examples of such sensors include, in particular: inertial measurement units including accelerometers, gyroscopes, or magnetometers; microelectromechanical systems (MEMS) or nanoelectromechanical systems (NEMS) including 3-axis accelerometers, 3-axis gyroscopes, or magnetometers; level sensors; flow sensors; temperature sensors (e.g., thermistors); pressure sensors; barometric pressure sensors; gravimeters; altimeters; image capture devices (e.g., cameras or lensless aperture sensors); light detection and ranging sensors; proximity sensors (e.g., infrared radiation detectors, etc.); depth sensors; ambient light sensors; ultrasonic transceivers; microphones or other similar audio capture devices; and so on.

[0206] The driving circuitry 2822 may include software and hardware elements that operate to control a specific device embedded in, attached to, or otherwise communicatively coupled to the device 2800. The driving circuitry 2822 may include various drivers that allow other components to interact with or control various input / output (I / O) devices that may be present in or connected to the device 2800. For example, the driving circuitry 2822 may include: a display driver for controlling and allowing access to a display device; a touchscreen driver for controlling and allowing access to a touchscreen interface; a sensor driver for acquiring sensor readings of a sensor 2820 and controlling and allowing access to the sensor 2820; a driver for acquiring actuator positions of electromechanical components or controlling and allowing access to electromechanical components; a camera driver for controlling and allowing access to an embedded image capture device; and an audio driver for controlling and allowing access to one or more audio devices.

[0207] The PMIC 2824 manages the power supplied to various components of the device 2800. Specifically, relative to the processor 2804, the PMIC 2824 controls power selection, voltage scaling, battery charging, or DC-DC conversion.

[0208] In some implementations, the PMIC 2824 can be controlled or otherwise integrated into various power-saving mechanisms of the device 2800. For example, if the platform UE is in the RRC_Connected state, where it remains connected to the RAN node as it anticipates receiving traffic soon, then after a period of inactivity, the platform UE can enter a state known as Discontinuous Receive Mode (DRX). During this state, the device 2800 can power down for short intervals to save power. If there is no data service activity during an extended period, the device 2800 can transition to the RRC_Idle state, where the device disconnects from the network and does not perform operations such as channel quality feedback, handover, etc. The device 2800 enters a very low-power state and performs paging, where the device periodically wakes up again to listen to the network and then power down again. The device 2800 can not receive data in this state; to receive data, the UE must transition back to the RRC_Connected state. Additional power-saving modes can render the device unusable from the network for periods exceeding the paging interval (from seconds to hours). During this period, the device is completely unable to connect to the network and can be completely powered off. Any data transmitted during this time will cause significant delays, which are assumed to be acceptable.

[0209] Battery 2828 can power device 2800, but in some examples, device 2800 may be installed or deployed in a fixed location and may have a power source coupled to the power grid. Battery 2828 may be a lithium-ion battery or a metal-air battery, such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, etc. In some specific implementations, such as in vehicle-based applications, battery 2828 may be a typical lead-acid automotive battery.

[0210] As is widely recognized, the use of personally identifiable information should comply with privacy policies and practices that are generally accepted to meet or exceed industry or governmental requirements for protecting user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly explained to users.

[0211] For one or more embodiments, at least one of the components illustrated in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, or methods described in the Embodiments section below. For example, the baseband circuitry described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more embodiments described below. Similarly, circuitry associated with a UE, base station, or network element as described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more embodiments described below in the Embodiments section.

[0212] Example Further exemplary implementations are provided in the following sections.

[0213] Example 1 includes a method comprising: generating a Quality of Service (QoS) profile associated with the delivery of service information, wherein the QoS profile indicates a destination domain of the service information, a preferred delivery plane of the service information, a preferred delivery method of the service information, or privacy attributes associated with the delivery of the service information; and sending the QoS profile to a node in a cellular network.

[0214] Example 2 includes the method according to Example 1 or some other embodiment herein, wherein the QoS profile is used to indicate a radio access network, core network, or data network as the destination domain for the service information.

[0215] Example 3 includes the method according to Example 1 or some other embodiment herein, wherein the QoS profile is used to indicate privacy attributes supporting anonymous delivery of the service information, wherein anonymous delivery of the service information is preferred, or proxy delivery of the service information is preferred.

[0216] Example 4 includes the method according to Example 1 or some other embodiment herein, wherein the QoS profile further indicates support for delayed delivery of the service information.

[0217] Example 5 includes the method according to Example 1 or some other embodiment herein, wherein the QoS profile is used to indicate a preferred delivery method, wherein the preferred delivery method is delivery via the user plane as a user plane message, via the control plane as a control plane message, via the user plane as a control plane message, or via the service plane.

[0218] Example 6 includes a method according to any one of Examples 1 to 5 or any other example herein, wherein the service information is information for supporting artificial intelligence or machine learning services of the network, computing or storage services of the network, or sensing or positioning services of the network.

[0219] Example 7 includes the method according to Example 1 or some other embodiment herein, wherein the method is implemented by an entity that requests the service information, an entity that generates the service information, an entity that consumes the service information, or an entity that manages the delivery of the service information.

[0220] Example 8 includes a method implemented by a Service Information Delivery Management Function (SIDMF), the method comprising: receiving a request for delivery of service information related to an artificial intelligence or machine learning service of the network, a computing or storage service of the network, or a sensing or location service of the network; generating configuration information for instructing the delivery of the service information; and sending the configuration information to an entity to which the service information is to be sent.

[0221] Example 9 includes the method according to Example 8 or some other embodiment of this document, further comprising: sending the configuration information via a direct logical interface between the entity and the SIDMF, wherein the entity is a user equipment or a base station.

[0222] Example 10 includes the method according to Example 9 or some other embodiment herein, wherein the configuration information is used to indicate the periodicity of service information arrival, radio bearer mapping for the service information, expected size of the service information, or jitter information associated with the service information.

[0223] Example 11 includes the method according to Example 8 or some other embodiment herein, further comprising: sending a report configuration to a source of the service information; and receiving an indication from the source of service information that can be delivered based on the report configuration.

[0224] Example 12 includes the method according to Example 8 or some other embodiment herein, wherein the entity is a base station, and the configuration information includes parameters for transmitting the service information via an air interface, and requests for downlink resource allocation for transmitting the service information to user equipment or for uplink resource allocation for receiving the service information from user equipment.

[0225] Example 13 includes the method according to Example 12 or some other embodiment herein, further comprising: sending a request to a network function or user equipment to generate the service information and deliver the service information to the base station.

[0226] Example 14 includes the method according to Example 8 or some other embodiment herein, further comprising: receiving from the entity an acknowledgment that the service information has been successfully delivered.

[0227] Example 15 includes a method for operating network functions of a core network, the method comprising: receiving a Quality of Service (QoS) mapping policy for service information related to artificial intelligence or machine learning services of the network, computing or storage services of the network, or sensing or location services of the network; receiving the service information; and mapping the service information to a QoS stream based on the QoS mapping policy.

[0228] Example 16 includes the method according to Example 15 or some other embodiment herein, wherein the network function is a user plane function (UPF), and receiving the QoS mapping policy includes: receiving the QoS mapping policy from a service information delivery management function or a session management function.

[0229] Example 17 includes the method according to Example 15 or some other embodiment herein, wherein receiving the service information includes: receiving the service information from the Service Information Processing Function (SIPF) of the core network, wherein the service information originates from the core network.

[0230] Example 18 includes the method described according to Example 17 or some other embodiment herein, wherein the network function is a user plane function (UPF) or a service function operating in parallel with a UPF.

[0231] Example 19 includes a method to be implemented in a user equipment (UE), the method comprising: receiving a service information stream at a first layer of the UE, the service information stream including service information related to artificial intelligence or machine learning services of the network, computing or storage services of the network, or sensing or location services of the network; mapping the service information stream to a quality of service (QoS) stream or radio bearer by the first layer; and transmitting the service information using the QoS stream or radio bearer.

[0232] Example 20 includes the method according to Example 19 or some other embodiment herein, wherein the first layer is a Radio Resource Control (RRC) layer, and the mapping includes mapping the service information flow to a radio bearer, wherein the radio bearer is a signaling radio bearer.

[0233] Example 21 includes the method according to Example 20 or some other embodiment herein, further comprising: providing the service information flow from the non-access stratum (NAS) layer or access stratum (AS) layer of the UE to the RRC layer.

[0234] Example 22 includes the method according to Example 20 or some other embodiment herein, further comprising: providing the service information flow from the UE's Service Information Adaptation (SIA) layer to the RRC layer.

[0235] Example 23 includes the method according to Example 19 or some other embodiment of this document, further comprising: identifying SRB mapping rules; and mapping the service information flow to the SRB based on the SRB mapping rules.

[0236] Example 24 includes the method according to Example 19 or some other embodiment herein, wherein the first layer is a Service Information Adaptation (SIA) layer, and the method further includes: receiving the service information stream from the non-access stratum (NAS) layer or access stratum (AS) layer of the UE at the SIA layer; and mapping the service information stream to a QoS stream.

[0237] Example 25 includes the method according to Example 19 or some other embodiment herein, wherein the first layer is a Service Data Adaptation (SDAP) layer, the service information flow is a Quality of Service (QoS) flow, and the mapping includes mapping the QoS flow to a radio bearer, wherein the radio bearer is a data radio bearer.

[0238] Another embodiment may include an apparatus comprising one or more elements for performing the method described or associated with any one of Embodiments 1 to 25 or any other method or process described herein.

[0239] Another embodiment may include one or more non-transitory computer-readable media, the one or more non-transitory computer-readable media including instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of the method described or associated with any of embodiments 1 to 25 or any other method or process described herein.

[0240] Another embodiment may include an apparatus comprising one or more elements for performing the methods described or associated with any one of Embodiments 1 to 25 or any other methods or processes described herein.

[0241] Another embodiment may include a method, technique or process described or associated with any one of embodiments 1 to 25 or any part or component thereof.

[0242] Another embodiment may include an apparatus comprising: one or more processors, and one or more computer-readable media including instructions that, when executed by the one or more processors, cause the one or more processors to perform the methods, techniques, or processes described or associated with any one or more of embodiments 1 to 25.

[0243] Another embodiment may include a signal described or associated with any one of embodiments 1 to 25 or a portion or component thereof.

[0244] Another embodiment may include a datagram, information element, packet, frame, segment, PDU, or message described or associated with any one of embodiments 1 to 25 or any part or component thereof, or otherwise described in this disclosure.

[0245] Another embodiment may include a signal encoded with data described or associated with any one of embodiments 1 to 25 or a portion or component thereof, or otherwise described in this disclosure.

[0246] Another embodiment may include a signal encoded as a datagram, IE, packet, frame, segment, PDU, or message, as described or associated with any one of embodiments 1 to 25 or any part or component thereof, or otherwise described in this disclosure.

[0247] Another embodiment may include an electromagnetic signal carrying computer-readable instructions, wherein the computer-readable instructions are executed by one or more processors to cause the one or more processors to perform a method, technique or process described or associated with any one or more of embodiments 1 to 25.

[0248] Another embodiment may include a computer program comprising instructions, wherein the program is executed by a processing element to cause the processing element to perform a method, technique, or process described or associated with any one or a portion thereof according to Embodiments 1 to 25.

[0249] Another embodiment may include signals in a wireless network as shown and described herein.

[0250] Another embodiment may include a method for communicating in a wireless network as shown and described herein.

[0251] Another embodiment may include a system for providing wireless communication as shown and described herein.

[0252] Another embodiment may include a device for providing wireless communication as shown and described herein.

[0253] Unless otherwise expressly stated, any embodiment described above may be combined with any other embodiment (or combination of embodiments). The foregoing description of one or more specific embodiments is illustrative and descriptive, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise forms disclosed. In view of the teachings above, modifications and variations are possible, or modifications and variations may be obtained from practice of various embodiments.

[0254] Although the above embodiments have been described in considerable detail, many variations and modifications will become apparent to those skilled in the art once the above disclosure is fully understood. It is intended that the following claims be construed as encompassing all such variations and modifications.

Claims

1. One or more computer-readable media having instructions that, when executed by one or more processors, cause a device to perform the following operations: Generate a Quality of Service (QoS) profile associated with the delivery of service information, wherein the QoS profile indicates the destination domain of the service information, the preferred delivery plane of the service information, the preferred delivery method of the service information, or privacy attributes associated with the delivery of the service information; and The QoS profile is sent to the nodes of the cellular network.

2. The one or more computer-readable media of claim 1, wherein the QoS profile is used to indicate a radio access network, a core network, or a data network as the destination domain for the service information.

3. One or more computer-readable media according to claim 1 or 2, wherein the QoS profile is used to indicate privacy attributes that support anonymous delivery of the service information, wherein anonymous delivery of the service information is preferred, or proxy delivery of the service information is preferred.

4. One or more computer-readable media according to claim 1 or 2, wherein the QoS profile further indicates support for delayed delivery of the service information.

5. One or more computer-readable media according to claim 1 or 2, wherein the QoS profile is used to indicate a preferred delivery method, wherein the preferred delivery method is delivery via user plane as user plane message, via control plane as control plane message, via control plane as control plane message, via user plane as control plane message, or via service plane delivery.

6. The one or more computer-readable media according to claim 1 or 2, wherein the service information is information for supporting artificial intelligence or machine learning services of the network, computing or storage services of the network, or sensing or positioning services of the network.

7. One or more computer-readable media according to claim 1 or 2, wherein the method is implemented by an entity that requests the service information, an entity that generates the service information, an entity that consumes the service information, or an entity that manages the delivery of the service information.

8. A method implemented by a Service Information Delivery Management Function (SIDMF), the method comprising: Receive requests for the delivery of service information related to artificial intelligence or machine learning services, computing or storage services, or sensing or location services of the network. Generate configuration information to indicate the delivery of the service information; as well as Send the configuration information to the entity to which the service information is to be sent.

9. The method according to claim 8, further comprising: The configuration information is sent through the direct logical interface between the entity and the SIDMF. The entity mentioned therein is user equipment or a base station.

10. The method of claim 9, wherein the configuration information is used to indicate the periodicity of service information arrival, radio bearer mapping for the service information, expected size of the service information, or jitter information associated with the service information.

11. The method according to claim 8 or 9, further comprising: Send report configuration to the source of the service information; as well as Based on the report configuration, receive instructions from the source regarding service information that can be used for delivery.

12. The method of claim 8 or 9, wherein the entity is a base station, and the configuration information includes parameters for transmitting the service information via an air interface, and a request for downlink resource allocation for transmitting the service information to user equipment or for uplink resource allocation for receiving the service information from user equipment.

13. The method according to claim 12, further comprising: Send a request to the network function or user equipment to generate the service information and deliver the service information to the base station.

14. The method according to claim 8 or 9, further comprising: Receive confirmation from the entity that the service information has been successfully delivered.

15. An apparatus for implementing network functions of a core network, the apparatus comprising: Interface circuit; as well as A processing circuit coupled to the interface circuit, the processing circuit being used for: The interface circuit receives a Quality of Service (QoS) mapping policy for service information related to artificial intelligence or machine learning services of the network, computing or storage services of the network, or sensing or location services of the network. The service information is received via the interface circuit. as well as Based on the QoS mapping strategy, the service information is mapped to the QoS stream.

16. The device of claim 15, wherein the network function is a user plane function (UPF), and the processing circuitry is configured to: The QoS mapping policy is received from the service information delivery management function or the session management function.

17. The device according to claim 15 or 16, wherein, in order to receive the service information, the processing circuitry is configured to: The service information is received from the Service Information Processing Function (SIPF) of the core network. The service information mentioned therein originates from the core network.

18. The device of claim 17, wherein the network function is a user plane function (UPF) or a service function operating in parallel with a UPF.

19. A method to be implemented in a user equipment (UE), the method comprising: The UE receives a service information stream at its first layer, the service information stream including service information related to the network's artificial intelligence or machine learning services, the network's computing or storage services, or the network's sensing or positioning services. The first layer maps the service information flow to a Quality of Service (QoS) flow or radio bearer; as well as The service information is transmitted using the QoS stream or radio bearer.

20. The method of claim 19, wherein the first layer is a Radio Resource Control (RRC) layer, and the mapping comprises: The service information flow is mapped to a radio bearer, wherein the radio bearer is a signaling radio bearer.

21. The method according to claim 20, further comprising: The service information flow is provided to the RRC layer by the UE’s non-access stratum (NAS) layer or access stratum (AS) layer.

22. The method of claim 20, further comprising: The service information flow is provided from the UE's Service Information Adaptation (SIA) layer to the RRC layer.

23. The method according to any one of claims 19 to 22, further comprising: Identify SRB mapping rules; as well as Based on the SRB mapping rules, the service information flow is mapped to the SRB.

24. The method according to any one of claims 19 to 22, wherein the first layer is a Service Information Adaptation (SIA) layer, and the method further comprises: The service information stream is received at the SIA layer from the UE's Non-Access Stratum (NAS) layer or Access Stratum (AS) layer; as well as Map the service information stream to a QoS stream.

25. The method according to any one of claims 19 to 22, wherein the first layer is a Service Data Adaptation (SDAP) layer, the service information flow is a Quality of Service (QoS) flow, and the mapping includes: The QoS flow is mapped to a radio bearer, wherein the radio bearer is a data radio bearer.

Images