An analytics-assisted satellite access optimization (SAO) function is described herein. In an example, an application/service enabler layer server supporting the SAO function may receive, from a requestor, a request to provide analytics information for satellite access. The server may send, to a satellite service provider, a request, for satellite information. The server may receive, from the satellite service provider, satellite information. The server may send, to a core network and/or one or more UEs, a request for UE information. The server may receive, from the core network and/or the one or more UEs, the UE information. The server may generate, based on the satellite information and the UE information, analytics information for satellite access. The server may send a notification indicating the generated analytics information. The server may receive updated satellite information and/or UE information, based on a generation of updated analytics information.
Methods, apparatuses, and systems for AIML enabled digital avatars are described herein. In one aspect, a method performed by an extended reality (XR) application server can include: receiving a first request to provision an authorization and usage policy for an AIML enabled digital avatar; determining whether the requestor of the first request is authorized to provision the authorization and usage policy; assigning an identifier for the authorization and usage policy based on determining the requestor of the first request is authorized; and sending a response to the first request with a status and the assigned policy identifier.
IoT service layer capabilities may be employed to automate and simplify the service enrollment process for IOT service subscribers/enrollees. These capabilities enable virtualization of a service subscriber and the physical IoT devices, applications, data and authorized users of the subscriber into a software profile that is representative of the subscriber. Once virtualized, a service subscriber may then delegate the complexities and burden of service enrollment to an automated IoT service enrollment software function.
Methods for managing personal IoT networks (PINs) are described herein. In one aspect, a method may include determining, by a personal IoT network (PIN) Element Management Capability (PEMC) of a PIN, a PIN Element Gateway Capability (PEGC) of the PIN is not within a coverage area of the PIN: sending, by the PEMC and to a PIN server, a request for the PIN server to perform a PEGC role change; and receiving, by the PEMC and from the PIN server, a notification that a PIN element (PINE) of the PIN is selected to perform PEGC functions for the PIN.
H04L 41/0895 - Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
H04L 41/5054 - Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components
6.
INTERWORKING BETWEEN IOT SERVICE LAYER SYSTEMS AND DISTRIBUTED LEDGER SYSTEMS
A distributed ledger interworking architecture is described wherein a distributed ledger proxy interfaces with IT service layer systems and distributed ledger systems. Service layer nodes may interact with the distributed ledger proxy to leverage functions provided by distributed ledger systems, such as to request that the distributed ledger proxy insert some service layer information into the distributed ledgers. A distributed ledger proxy can support multiple service layer nodes and may interface to multiple different distributed ledger systems.
H04L 9/00 - Arrangements for secret or secure communicationsNetwork security protocols
H04L 9/32 - Arrangements for secret or secure communicationsNetwork security protocols including means for verifying the identity or authority of a user of the system
H04L 67/12 - Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
H04L 67/566 - Grouping or aggregating service requests, e.g. for unified processing
H04L 67/567 - Integrating service provisioning from a plurality of service providers
7.
Interworking Service For The Restful Internet Of Things
An interworking service entity receives server registration requests including indications of service layer protocols used by each server, maintains a repository of server information, and uses the repository for interworking requests of devices to servers of different protocols based on a server type provided in discovery requests. Other matching information may include, for example, server security protocol, supported services, service territory, availability, capacity, or loading, as device information or preferences, such a supported service, supported interface type, or a supported device type.
H04L 41/22 - Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks comprising specially adapted graphical user interfaces [GUI]
H04L 67/12 - Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
H04L 67/51 - Discovery or management thereof, e.g. service location protocol [SLP] or web services
H04L 69/08 - Protocols for interworkingProtocol conversion
8.
METHODS TO ENABLE 3GPP CAPIF CONTEXT AWARE SERVICE API AUTHORIZATION
Methods are described herein for defining context aware service API authorization functionality. Based on the awareness of the state of the API invoker, resource owner, service being invoked and the underlying 3GPP network, differentiated discovery and access to these service APIs can be realized. This provides the ability to control access for specific API invokers or categories of API invokers to certain services or types of services based on the current state of key resources within the system.
Methods, devices, and systems for data collection enablement services are described herein. In one aspect, a method may include receiving, by a data collection enablement service (DCES), a data collection request; determining, by the DCES, one or more data sources based at least on discovered data source profiles; receiving, from the one or more data sources and by the DCES, data according to the received request; generating, by the DCES, a dataset from the received data; storing the generated dataset in a repository in communication with the DCES; and transmitting, by the DCES, a response to the data collection request indicative of a storage location of the generated dataset.
Systems and methods are presented herein for determining and providing enhanced location information in a communication network. The method may comprise receiving, at a location management server (LMS) and from another server, a request for enhanced location information associated with a user equipment (UE). The method may comprise sending, to the another server and based on authorizing the subscription request, an indication that the LMS will send enhanced location information associated with the UE to the another server. The method may comprise determining, at one or more time intervals, basic location information associated with the UE. The method may comprise determining, based at least in part on the basic location information associated with the UE, enhanced location information associated with the UE. The method may comprise sending, to the another server, the enhanced location information associated with the UE.
Disclosed herein are methods and systems for the support of redundant transport in a cellular system at an application layer. A user equipment may establish a first connection and a second connection to a wireless network. The user equipment may transmit data to a receiver device via both the first and second connection. The first and the second connections may be redundant connections. The methods and systems are applied in the context of 3GPP SA6 Service Enabler Architecture Layer for Verticals (SEAL) and Key Issue #1 of 3GPP TR 23.700-34.
H04W 40/22 - Communication route or path selection, e.g. power-based or shortest path routing using selective relaying for reaching a BTS [Base Transceiver Station] or an access point
H04W 76/15 - Setup of multiple wireless link connections
12.
DIGITAL REPRESENTATION BASED METHODS FOR ENABLING METAVERSE APPLICATION SESSION MANAGEMENT
Digital representation based methods, and associated apparatuses and systems, for enabling metaverse application session management are described herein. In one aspect, a method can include receiving, from a Metaverse application client or server, a request to create or update a MAS policy comprising multi-modal digital representation information of the MAS; determining one or more network communication flow requirements of the MAS based on MAS digital representations policy information of the request; creating or updating one or more network communication flows for the MAS based on the determined network communication flow requirements of the digital representations; and detecting a MAS synchronization or measurement threshold condition has been met and performing one or more MAS synchronization or measurement actions.
Systems and methods are presented herein for application enabler layer (AEL) support for management of artificial intelligence / machine learning (AIML) operations. The method may comprise generating, based on receiving an AIML job request, an AIML job, wherein the AIML job is assigned an identifier. The method may comprise sending a response associated with the AIML job. The method may comprise sending, to one or more AIML enabler clients, at least one AIML task request. The method may comprise updating, based on receiving one or more notifications associated with a disturbance to an AIML task, an operational task associated with the AIML job. The method may comprise receiving at least one AIML task notification from one or more AIML enabler clients. The method may further comprise sending, to a VAL server, a job notification.
Methods for enabling sensing enablement services in 3GPP systems are described herein. In one aspect, a method may include receiving, from a sensing enablement client and via a sensing enablement client registration procedure, sensing capability information of a hosting user equipment (UE); receiving, from the sensing enablement client and via the sensing enablement client registration procedure, characteristics information and consent policy of the hosting UE; receiving, from a consumer, a request for a sensing enablement service; sending, to a sensing data source, a request for configuring the sensing service; receiving sensing data/results and assistance information in response to the request for configuring the sensing service; generating sensing outputs comprising processed sensing results; and sending, to a notification target specified by the consumer, a message including the generated sensing outputs.
H04W 4/38 - Services specially adapted for particular environments, situations or purposes for collecting sensor information
H04L 67/12 - Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
Systems and methods are presented herein for providing spatial mapping services. A spatial mapping server may create, based on a first request from one or more of a first VAL server or a first VAL client, a spatial map of an area of interest and comprising one or more requested layers of spatial map information. The spatial mapping server may receive, from one or more of a second VAL server or a second VAL client, a second request for a spatial map matching spatial map discovery criteria. The spatial mapping server may send, to the one or more second VAL server or second VAL client and in response to a permission to discover the spatial map, a response to the one or more second VAL server or second VAL client comprising an indication of the spatial map.
Systems and methods for enabling federated learning deployment services are disclosed, comprising receiving a message comprising deployment configuration information for a trained ML model, wherein the deployment configuration information comprises policies for re-training the trained ML model. A request may be sent, to a first group of client devices, to deploy the trained ML model at the first group of client devices and a request may be sent to receive responses of deployment information associated with deploying the trained ML model. A response comprising the deployment information may be received from at least one of the first group of client devices. A determination to trigger re-training of the ML model may be made based on the one or more policies for re-training the ML model and the received deployment information. The method may comprise sending, to a second group of client devices, a request to re-train the ML model.
Service layer support of traffic steering over multiple accesses are described herein. In one aspect, a method performed by an application enabler layer (AEL) server, can include: receiving a request from a vertical application layer (VAL) server for configuring a traffic steering policy for one or more UEs; sending a response to the VAL server; receiving an application layer traffic flow request for one or more access network connections, where the request includes information corresponding to traffic steering policy and an access network identifier; mapping an AEL client and one or more traffic flow identifiers with the access network identifier and a VAL server identifier to enable traffic steering of application traffic; receiving traffic steering adaptation reports for one or more flows, and applying traffic adaptation processes to the one or more flows to an AEL client based on the traffic steering adaptation reports.
A method may include receiving by a Rule Engine (RE) service one or more requests to define an RE definition for a Digital Twin (DT) system; communicating with a DT service, a storage service, a Machine Learning (ML) service, or a combination thereof, according to rules specified in the DT system, for processing the one or more requests; and sending, by the RE service, one or more responses with a status to the one or more requests, wherein the one or more response comprise one or more of an overall status of processing the RE definition, an individual status for each event condition, action, state, and/or state transition that was specified in the RE definition, and the status for an interconnection of services between the RE and ML services.
Methods, apparatus, and systems are described for managing artificial intelligence (AI) / machine learning (ML) resources and capabilities available to the application and service enablement layer and coordinating AI/ML-enabled analytics services. According to some aspects, an application data analytics enablement (ADAE) service may be enhanced to support AI/ML-enabled analytics services.
H04L 41/16 - Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using machine learning or artificial intelligence
20.
SERVICE LAYER MECHANISMS TO SUPPORT MULTI-MODAL FLOW MANAGEMENT
Methods and systems for service layer mechanisms to support multi-modal flow management are disclosed. Individual service enabler flows may be synchronized to support applications that use multiple communication flows in tandem. A multi-modal flow management service may provide monitoring and synchronization capabilities for the individual service enabler flows. The multi-modal flow management service may measure the synchronized individual service enabler flows to determine if deviations from a synchronization threshold occur. The multi-modal flow management service may buffer or delay one or more of the individual service enabler flows to maintain the synchronization of the individual service enabler flows within the synchronization threshold.
Methods and systems for service layer support of federated learning groups are described herein. In one aspect, a method performed by an application enabler server, may include: receiving a first request for forming a federated learning (FL) group; sending one or more requests, to a core network, corresponding to assistance for FL operations; receiving a response to the one or more requests from the core network; and sending a response to the first request comprising one of a FL group identifier, a list of FL clients associated with the FL group, a validity time or schedule for the FL group, or a combination thereof.
Described herein are methods for advanced federated learning hyperparameter optimization. Federated learning hyperparameter optimization presents challenges to machine-learning training that do not exist in centralize hyperparameter optimization. Issues such as lack of data visibility, model parameter aggregation strategies, communications overhead between federated learning servers and federated learning clients, federated learning training round schedules, and availability of federated learning clients need to be addressed. Certain enhancements may be made to federated learning training to improve the federated learning hyperparameter optimization process. This disclosure proposes the following enhancements: a method for configuring hyperparameters for federated learning training; a method for requesting federated learning hyperparameter optimization search space reduction; and a method for configuring federated learning hyperparameter optimization training rounds.
Methods, apparatuses, and systems for inferencing model selection and management are described herein. In one aspect, a method can include sending, by a model selection and management client (MSMC) and to a model selection and management service (MSMS), a management service request; receiving, by the MSMC and from the MSMS, a notification indicating a request for a model selection by the MSMC; and sending, by the MSMC and to the MSMS, a model selection message indicative of a machine learning model selected by the MSMC.
Federated learning (FL) may be deployed as a service via the definition of FL job management functionality. An FL service may have the capability to receive FL job specifications from FL users, process and manage these FL jobs on behalf of FL users via interaction with FL clients, and update FL users with the status of FL jobs as they are being processed.
An application coordination service (ACS) enables awareness among applications and perform coordination actions regarding these applications. For example, application client may request application coordination service from an ACS client. The ACS client may identify the influencer applications that are of interest, monitor the activities and status of the influencer applications, generate notifications, or determine and perform actions regarding the service request.
Methods, apparatus, and systems are described for management of information associated with digital avatars, including user eXtended Reality (XR) digital avatar creation and management, user XR digital avatar certification, and/or user XR digital avatar access and storage by third parties.
A63F 13/60 - Generating or modifying game content before or while executing the game program, e.g. authoring tools specially adapted for game development or game-integrated level editor
A63F 13/71 - Game security or game management aspects using secure communication between game devices and game servers, e.g. by encrypting game data or authenticating players
A63F 13/79 - Game security or game management aspects involving player-related data, e.g. identities, accounts, preferences or play histories
G06F 3/01 - Input arrangements or combined input and output arrangements for interaction between user and computer
27.
METHODS AND APPARATUS FOR FEDERATED LEARNING CLIENT REGISTRATION, DISCOVERY AND SELECTION SERVICES
Methods, apparatus, and systems are described for improved federated learning (FL) service used for training of machine learning models. In some examples, an improved FL service may allow FL clients to register to the FL service. The FL service may provide methods for discovery and selection of FL clients by FL users.
Described herein are methods, apparatuses, and systems that enable the management and communication of machine learning data preparation requirements, client data availability, client data information, and client data processing capabilities in a FL system. An interface is defined between a FL user application and a FL service to enable the management and communication of the ML application and data preparation requirements for the FL process. Another interface is defined for the FL service to query FL clients for data availability and characteristics as well as data processing capabilities. The FL service may utilize the second interface to communicate data processing functions to the FL clients. These solutions ensure that the data used for training a machine learning model in a federated manner is standardized, meets the requirements of the ML model, processes efficiently and accurately, and utilizes the client's processing capabilities while preserving the privacy of the local client data.
An interworking service entity receives server registration requests including indications of service layer protocols used by each server, maintains a repository of server information, and uses the repository for interworking requests of devices to servers of different protocols based on a server type provided in discovery requests. Other matching information may include, for example, server security protocol, supported services, service territory, availability, capacity, or loading, as device information or preferences, such a supported service, supported interface type, or a supported device type.
H04L 41/22 - Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks comprising specially adapted graphical user interfaces [GUI]
H04L 67/12 - Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
H04L 67/51 - Discovery or management thereof, e.g. service location protocol [SLP] or web services
H04L 69/08 - Protocols for interworkingProtocol conversion
30.
NETWORK CENTRIC METHODS FOR MANAGING SPATIAL ANCHORS IN 3GPP SYSTEMS
Described herein are methods and procedures to enhance the 3GPP system with XRM Server functionality to assist VAL servers with the creation and management of spatial anchors. For example, an XRM server may send a spatial anchor ranging request to one or more other services. The one or more other services may determine ranging distances and orientations between a spatial anchor and a user device and send the ranging distances and orientations to the XRM server. The XRM server may receive the ranging distances and orientations, compare the received ranging distances and orientations with predetermined ranging distance and orientation limits for the spatial anchor, and based on the ranging distances and orientations limits being greater than the received ranging distances and orientations, perform one or more spatial anchor operations.
Disclosed herein are methods and systems for the determination or generation of datasets for data-centric services, for example ML services. An apparatus may receive a data source management service request associated with a data source. The apparatus may determine, for each data source of one or more data sources, a data source profile. The apparatus may send, to the data source, a configuration indication. The apparatus may determine, for the data source, at least one of data usage associated with the data source or an indication of data analysis associated with the data source, wherein the indication of the data analysis is received from a computing device. The apparatus may send, to at least one of the data source or the computing device, an updated configuration indication.
XR digital vaults may contain not only contents from digital wallets but also offer enhancements for user privacy and protection in a virtualized environment. These enhancements may comprise enhanced identification mechanisms to authenticate and verify user information and provide the ability to save artifacts from XR services such as XR experiences and virtual items in the XR digital vault.
G06F 21/33 - User authentication using certificates
G06Q 20/40 - Authorisation, e.g. identification of payer or payee, verification of customer or shop credentialsReview and approval of payers, e.g. check of credit lines or negative lists
Device centric methods for managing spatial anchors in 3GPP systems are described herein. In one aspect, a method can include receiving, by an eXtended Reality and Media services (XRM) client of a UE, a spatial anchor request, wherein the spatial anchor request comprises a request to register a VAL client to the XRM client; and sending, by the XRM and in response to the spatial anchor request, a response comprising an identifier of a spatial anchor the VAL client is registered to, a representation of the spatial anchor the VAL is registered to, or both.
A lightweight and extensible information model for machine-to-machine systems is disclosed. A service layer information management architecture uses three categories of atomic objects, subjects, actions, and descriptions. Information for use within the model is built using the atomic information objects. Application programming interfaces are used to perform operations and information processing by different nodes. Common service functions are used in the model as instances of a generic common service information model.
System and methods that improve the use of network functions on edge data networks are disclosed. A mechanism that supports edge-assisted UE context and trigger collection is described herein, where a UE can actively send its context information and/or any trigger (e.g. a request for a network function/service to be deployed in edge data networks, etc.) to an edge enabler server, which processes the received context and triggers from its UEs. The edge enabler server may also forward UE context and triggers to 5G core network (5GC) upon receiving a solicitation request from the 5GC, or if the 5GC has already made a subscription for getting notification on UE context and triggers. A network repository function is provided as a new network function collect, store, and manage edge data network information.
H04L 67/60 - Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
H04W 84/04 - Large scale networksDeep hierarchical networks
36.
MECHANISMS FOR INTELLIGENT MACHINE LEARNING DATA PREPARATION SERVICE
Mechanisms for intelligent machine learning data preparation services are described herein. In one aspect, a method by an intelligent data preparation service can include: receiving configuration information from a service provider to configure the data preparation service; receiving, from a user, configuration information comprising output requirements for data processed by the data preparation service and for the user; combining data inputs into a dataset; generating metadata for a set of features of the dataset; analyzing the data inputs, the set of features, and the metadata to derive recommended data preparation operations; selecting another set of features that satisfy the output requirements of the user, based on the user configuration information, the service provider configuration, the feature metadata, dataset context information, and the recommended data preparation operations; and configuring the intelligent data preparation service to manipulate the dataset for machine learning (ML) applications.
Methods and apparatuses are described herein for Multi cast/Broadcast Services (MBS). The embodiments described herein are directed to procedures for managing multiplexed MBS traffic, for prioritization between MBS related UL traffic, unicast UL traffic, and SL traffic, for handling HARQ retransmissions over C-RNTI, to support PDCP Status Reporting for MBS services, and for a wireless transmit/receive unit (WTRU) joining already started/activated Multicast Sessions. In one example, a WTRU may receive multiplexed MBS services via one or more MBS radio bearers (MRB) and/or one or more unicast data radio bearers (DRBs). The WTRU may be configured with a single Service Data Adaptation Protocol (SDAP) entity for the MBS services, and demultiplexing of traffic may be performed at the SDAP layer. The WTRU may be configured to demultiplex multiple logical channels across different MBS services, where the logical channels are received over the same transport block.
H04L 1/1822 - Automatic repetition systems, e.g. Van Duuren systems involving configuration of automatic repeat request [ARQ] with parallel processes
H04W 4/06 - Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]Services to user groupsOne-way selective calling services
38.
Cross-domain discovery between service layer systems and web of things systems
Systems and methods are introduced to enable cross-domain discovery. Systems and methods are also introduced to create representations of resources and information discovered from cross-domain discovery.
H04L 67/51 - Discovery or management thereof, e.g. service location protocol [SLP] or web services
H04L 67/125 - Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks involving control of end-device applications over a network
H04W 4/70 - Services for machine-to-machine communication [M2M] or machine type communication [MTC]
39.
ENHANCEMENTS FOR TCI ACTIVATION AND APPLICATION IN COMMON TCI OPERATION
Methods, apparatus, and systems are described for addressing common beam operation, in which a Transmission Configuration Indicator (TCI) state (e.g., beam) may be indicated by a Downlink Control Information (DCI) and subsequently be applied to both control and data channels and, in some aspects, to both downlink and uplink.
H04W 72/231 - Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal the control data signalling from the layers above the physical layer, e.g. RRC or MAC-CE signalling
H04W 72/1268 - Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows of uplink data flows
H04W 72/21 - Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network
H04W 76/20 - Manipulation of established connections
40.
METHODS, DEVICES, AND SYSTEMS FOR ANALYTICS-ENHANCED EDGE ENABLING LAYER SERVICE CONTINUITY
Methods, devices, and systems for analytics-enhanced edge enabling layer service continuity are described herein. In one aspect, a method can include receiving, by an analytics service, an analytics request from an Edge Enabling Layer (EEL) entity to perform Application Context Relocation (ACR) detection; collecting, by the analytics service, analytics information related to the detection of ACR; generating, by the analytics service, an ACR detection notification according to the collected analytics information; and sending, by the analytics service, the ACR detection notification to one or more reporting targets.
Methods and procedures are described herein to support the management of multiple simultaneously active gateways within a PIN. A method may comprise receiving, by a PEMC, two PIN join requests from two PIN elements, comprising PIN client profile information indicating that the respective PIN element can serve as a gateway, determining, based on each PIN client profile information, to configure the PIN elements as gateways, receiving, from a third PIN element, a PIN join request comprising PIN client profile information, determining, based on PIN client profile information of each PIN element, to assign the first PIN element as a default gateway and the second PIN element as a backup gateway for the third PIN element, and sending, to the PIN elements, a notification indicating the first PIN element is serving as the default gateway and the second PIN element is serving as the backup gateway for the third PIN element.
Methods, devices, and systems for migration or sharing of existing M2M service layer sessions are disclosed. In one embodiment, a Session Migration and Sharing Function (SMSF) performs the migration or sharing of a M2M service layer session. Various forms of service layer session context may be used to enable the migration and sharing of M2M service layer sessions.
G06F 15/16 - Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs
H04L 67/00 - Network arrangements or protocols for supporting network services or applications
Systems and methods are introduced to enable cross-domain discovery. Systems and methods are also introduced to create representations of resources and information discovered from cross-domain discovery.
H04L 67/51 - Discovery or management thereof, e.g. service location protocol [SLP] or web services
H04L 67/125 - Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks involving control of end-device applications over a network
H04W 4/70 - Services for machine-to-machine communication [M2M] or machine type communication [MTC]
44.
SERVICE LAYER-BASED METHODS TO ENABLE EFFICIENT ANALYTICS OF IOT DATA
Methods, systems, and apparatuses that enable a Service Layer (SL) to support analysis of internet of things (IoT) data and enable shared access to information generated by the analysis. An analytics management service may allow SL entities to configure analytics functions for many different IoT sources of data and organize the results in a customizable manner. The SL may support coordinating the analysis of IoT data from multiple independent sources and organizing the results of the analysis.
H04L 67/60 - Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
H04L 67/12 - Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
45.
Security lifecycle management of devices in a communications network
Described herein are complete lifecycle management processes for IoT/M2M devices. In an example, devices are commissioned and de-commissioned in a given system without requiring a user/human administrator. A delegated life-cycle management process is described, wherein devices rely upon a delegatee, which may have more computing and battery resources than the devices, to perform complete or partial lifecycle management operations on behalf of the devices. The delegatee may be a trusted entity that may belong to the same domain as the devices. Further, a Trust Enabling Infrastructure (TEI) is described herein, which may belong to a different trusted domain than the given device and its delegatee.
Methods are described herein for SEALDD data transmission measurement and data delivery services. A SEALDD client may receive a first request for data delivery service from an application comprising information for configuring data transmission measurements (DTM) or an action guarantee for the data delivery service. The SEALDD client may send a second request to a SEALDD server comprising a configuration for enabling at least one of data transmission measurements or an action guarantee. The SEALDD client may receive a first response to the second request that comprises a DTM configuration to configure the SEALDD client to collect data transmission information and may send a second response to the application that comprises information received in the first response. The SEALDD client may collect data transmission measurements during application data traffic, may receive a DTM report for the configured measurements, and may send a DTM report for the configured measurements.
A SEALDD server may receive a request to establish a SEALDD flow, wherein the SEALDD flow facilitates a transfer of VAL data between a VAL client endpoint and a first VAL server endpoint, and wherein the request comprises at least one of VAL client endpoint information and first VAL server endpoint information. The SEALDD server may establish a SEALDD flow associated with the first VAL server and associated with at least one VAL client endpoint. The SEALDD server may subscribe to a core network and receive a notification from the core network indicating a UE mobility event associated with a UE upon which the VAL client is hosted. The SEALDD server may determine to transfer the VAL client to a second VAL server. The SEALDD server may transfer the SEALDD flow to a different SEALDD server associated with the second VAL server.
Provided herein are methods for enhancing the existing discovery procedure by leveraging data analytics in the application and service enablement layer. For example, a method may comprise receiving, by an edge enabler server and from a user device, a first message indicating a discovery request for one or more discovery targets, sending, to an analytics service, a second message indicating a request for analytics information associated with the one or more discovery targets, wherein the analytics information comprises prediction information associated with a future status of the one or more discovery targets, receiving, from the analytics service, a third message comprising the analytics information associated with the one or more discovery targets, sending, to the user device and in response to the first message, a fourth message comprising a filtered list of discovery targets based on the analytics information associated with the one or more discovery targets.
H04L 67/289 - Intermediate processing functionally located close to the data consumer application, e.g. in same machine, in same home or in same sub-network
49.
Efficient resource representation exchange between service layers
Some underlying networks such as Low-Power Wide-Area Networks (LPWAN) have limited communication bandwidth and strict requirements on maximum message size. These requirements may pose a challenge for data or resource exchange between two service layer (SL) entities, for example, because resource representations to be exchanged may have too large a size to be supported by the underlying networks. In some cases, traditional data compression algorithms can be used to alleviate this problem to some degree, but it is recognized herein that there are associated computation costs due to compression and decompression that may not be affordable for constrained IoT devices. Various embodiments described herein address this problem, among others by defining a Resource Representation Common Part (RRCP) and storing it at the service layer. In some cases, the RRCP is not transmitted between SL entities, thereby reducing SL message sizes to cater to the constraints of underlying networks.
H04L 47/76 - Admission controlResource allocation using dynamic resource allocation, e.g. in-call renegotiation requested by the user or requested by the network in response to changing network conditions
H04L 67/60 - Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
Methods for managing personal IoT networks (PINs) are described herein. In one aspect, a method may include determining, by a personal IoT network (PIN) Element Management Capability (PEMC) of a PIN, a PIN Element Gateway Capability (PEGC) of the PIN is not within a coverage area of the PIN; sending, by the PEMC and to a PIN server, a request for the PIN server to perform a PEGC role change; and receiving, by the PEMC and from the PIN server, a notification that a PIN element (PINE) of the PIN is selected to perform PEGC functions for the PIN.
H04L 67/51 - Discovery or management thereof, e.g. service location protocol [SLP] or web services
H04L 67/12 - Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
H04L 41/0895 - Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
H04L 41/5054 - Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components
Methods, devices, and systems for data collection enablement services are described herein. In one aspect, a method may include receiving, by a data collection enablement service (DCES), a data collection request; determining, by the DCES, one or more data sources based at least on discovered data source profiles; receiving, from the one or more data sources and by the DCES, data according to the received request; generating, by the DCES, a dataset from the received data; storing the generated dataset in a repository in communication with the DCES; and transmitting, by the DCES, a response to the data collection request indicative of a storage location of the generated dataset.
Methods, systems, and devices may manage multi-user sessions in edge data networks. Edge devices may be configured to enable and operate different types of multi-user sessions.
Disclosed herein are methods and systems for pre-emptive vehicular to pedestrian detection. A VAE client may receive a first request from an application client on a UE to enable VRUP services associated with the UE. The VAE client may send a second request to a VAE server to create a V2P policy. The VAE client may receive a first response to the second request indicating the status of the second request, the first response comprising information of the V2P policy that applies to the UE. The VAE client may send a second response to the first request indicating the status of the first request.
Mechanisms for subscription and notification may include dynamically changing notification behavior based on notification target status or support access to notification history information.
H04L 67/12 - Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
G06Q 10/06 - Resources, workflows, human or project managementEnterprise or organisation planningEnterprise or organisation modelling
H04L 43/00 - Arrangements for monitoring or testing data switching networks
H04L 67/125 - Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks involving control of end-device applications over a network
H04L 67/288 - Distributed intermediate devices, i.e. intermediate devices for interaction with other intermediate devices on the same level
56.
Automated service enrollment in a machine-to-machine communications network
IoT service layer capabilities may be employed to automate and simplify the service enrollment process for IoT service subscribers/enrollees. These capabilities enable virtualization of a service subscriber and the physical IoT devices, applications, data and authorized users of the subscriber into a software profile that is representative of the subscriber. Once virtualized, a service subscriber may then delegate the complexities and burden of service enrollment to an automated IoT service enrollment software function.
Mechanisms for multidimensional data modeling and operations and related procedures are described. Resource structures for multidimensional data can be used. This can allow lumped operations such as RESTful operations and procedures on the multidimensional data. A new attribute “SamplingPeriodCovered” can be used to indicate the time interval when the related time series data (or any multi-dimension data streams) are stored. This can reduce the total size of the data stored.
Methods, devices, and systems for UE-initiated network slice management at a service enablement layer are described herein. In one aspect, a method can include receiving, by a NSCE client of a user equipment (UE) and from a VAL client of the UE, context information corresponding to application or user information of the UE; determining, by the NSCE client and based on the received context information, one or more network slices required by the VAL client; generating, by the NSCE client, one or more network slice management requests corresponding to the determined one or more network slices; and transmitting, by the NSCE client and to one or more NSCE servers, the generated one or more network slice management requests.
Provided herein are various methods, apparatus, and systems for providing a service enablement layer analytics service in a cellular network, such as at the 3GPP service enabler layer. For example, an apparatus may receive, from an analytics service consumer, a service enablement layer data analytics request, wherein the request includes requirements of the analytics service, determine based on the service enablement layer analytics request, to collect data from a service layer server and/or a service layer client, generate analytics result based on the received server-side data, the received client-side data and the requirements of the analytics service, send, to the analytics service consumer, and perform actions or trigger actions to be performed based on the analytics results.
Disclosed herein are methods and systems for the support of redundant transport in a cellular system at an application layer. A user equipment may establish a first connection and a second connection to a wireless network. The user equipment may transmit data to a receiver device via both the first and second connection. The first and the second connections may be redundant connections. The methods and systems are applied in the context of 3GPP SA6 Service Enabler Architecture Layer for Verticals (SEAL) and Key Issue #1 of 3GPP TR 23.700-34.
Internet of Things (IoT) configurable event and action sequencing mechanisms for interconnecting various IoT events together to achieve an event and action sequencing process that may efficiently enable complex uses of the data available in IoT systems.
H04L 67/125 - Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks involving control of end-device applications over a network
G16Y 40/35 - Management of things, i.e. controlling in accordance with a policy or in order to achieve specified objectives
H04W 4/70 - Services for machine-to-machine communication [M2M] or machine type communication [MTC]
A lightweight and extensible information model for machine-to-machine systems is disclosed. A service layer information management architecture uses three categories of atomic objects, subjects, actions, and descriptions. Information for use within the model is built using the atomic information objects. Application programming interfaces are used to perform operations and information processing by different nodes. Common service functions are used in the model as instances of a generic common service information model.
Methods, systems, and devices may support capabilities of user equipment which may be part of an application programming interface (API) exposure system or deployment, such as common API framework (CAPIF).
42 - Scientific, technological and industrial services, research and design
Goods & Services
Engineering consulting, development, and research services in the field of wireless connectivity, internet of things (IoT) communications, and computer network connectivity; Designing and testing of new products for others, namely, wireless internet of things (IoT) systems, platforms, equipment, devices and software and components thereof; Computer software design and custom computer software design; Computer software design and custom computer software design in the field of computer network connectivity and wireless internet of things (IoT) systems and platforms; Technological services, namely, technological consultation in the technology field of computer software, firmware, and hardware systems for use in internet of things (IoT) enabled devices
Mechanisms for subscription and notification may include dynamically changing notification behavior based on notification target status or support access to notification history information.
H04L 67/12 - Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
H04W 4/70 - Services for machine-to-machine communication [M2M] or machine type communication [MTC]
G06Q 10/06 - Resources, workflows, human or project managementEnterprise or organisation planningEnterprise or organisation modelling
H04L 67/63 - Routing a service request depending on the request content or context
H04L 67/125 - Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks involving control of end-device applications over a network
H04L 43/00 - Arrangements for monitoring or testing data switching networks
H04L 67/288 - Distributed intermediate devices, i.e. intermediate devices for interaction with other intermediate devices on the same level
66.
ASSISTING LOCAL SERVICE MANAGEMENT ON EDGE TERMINAL DEVICES
Edge terminal service host that hosts a local service and initiates relocating this local service to another service host in the system. Relocation may occur when there is a determination that the local service has become overloaded.
An application coordination service (ACS) enables awareness among applications and perform coordination actions regarding these applications. For example, application client may request application coordination service from an ACS client. The ACS client may identify the influencer applications that are of interest, monitor the activities and status of the influencer applications, generate notifications, or determine and perform actions regarding the service request.
The present application describes a method and apparatus for managing a service in a service layer. In particular, a method describes a computer readable storage medium including instructions for managing a service in a service layer where the instructions are executed by a processor. The executed instructions cause the processor to receive a request to manage, via a service enabler function of the service layer, a change of state of the service including adding, removing, activating, or deactivating the service. The request may include a service description. The executed instructions also cause the processor to evaluate, via the service enabler function, the service description comprising identifiers of one or more services to manage. The executed instructions further cause the processor to identify one or more service capabilities in the service layer to assist in managing the one or more services identified in the service description. A request may be sent and/or may instruct the one or more service capabilities to perform the change of state of the one or more services identified in the service description.
H04L 41/5041 - Network service management, e.g. ensuring proper service fulfilment according to agreements characterised by the time relationship between creation and deployment of a service
Support of end-to-end edge application service continuity is described herein. In one aspect, a service resident on a first wireless transmit/receive unit (WTRU) can receive, from a first application resident on the first WTRU, information for an association between the first application and a second application resident on a second WTRU. The service can send the association information to a service in the network such that the first and second applications are assigned to a first application server providing the type of service required for first and second application interactions. The service can detect the first WTRU's location is no longer in the service area of the first application server, and can send a request to the service in the network such that the first application and second applications are assigned to a second application server providing the type of service required for interactions between the first and second applications.
H04L 65/401 - Support for services or applications wherein the services involve a main real-time session and one or more additional parallel real-time or time sensitive sessions, e.g. white board sharing or spawning of a subconference
Methods, systems, and devices may assist in enhancements to PMF protocol and new ATSSS steering modes to enable support for analytics driven or multi-USIM steering. The following functionalities are disclosed: 1) Enable UEs to use the PMF protocol to provide UE specific data to the NWDAF for analytics purposes; 2) Enable multi-USIM UEs to notify the core network over the user plane of the UE's desire to pause communications with the CN associated with one USIM so the UE can communicate with the CN associated with another USIM; 3) Define new ATSSS steering modes to support data analytics driven steering; and 4) Define new ATSSS steering modes to support Multi-USIM steering, among other things.
System and methods that improve the use of network functions on edge data networks are disclosed. A mechanism that supports edge-assisted UE context and trigger collection is described herein, where a UE can actively send its context information and/or any trigger (e.g. a request for a network function/service to be deployed in edge data networks, etc.) to an edge enabler server, which processes the received context and triggers from its UEs. The edge enabler server may also forward UE context and triggers to 5G core network (5GC) upon receiving a solicitation request from the 5GC, or if the 5GC has already made a subscription for getting notification on UE context and triggers. A network repository function is provided as a new network function collect, store, and manage edge data network information.
H04L 67/60 - Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
H04W 84/04 - Large scale networksDeep hierarchical networks
72.
Interworking service for the restful internet of things
An interworking service entity receives server registration requests including indications of service layer protocols used by each server, maintains a repository of server information, and uses the repository for interworking requests of devices to servers of different protocols based on a server type provided in discovery requests. Other matching information may include, for example, server security protocol, supported services, service territory, availability, capacity, or loading, as device information or preferences, such a supported service, supported interface type, or a supported device type.
H04L 67/51 - Discovery or management thereof, e.g. service location protocol [SLP] or web services
H04L 41/22 - Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks comprising specially adapted graphical user interfaces [GUI]
H04L 67/12 - Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
H04L 69/08 - Protocols for interworkingProtocol conversion
H04L 69/321 - Interlayer communication protocols or service data unit [SDU] definitionsInterfaces between layers
Mechanisms for multidimensional data modeling and operations and related procedures are described. Resource structures for multidimensional data can be used. This can allow lumped operations such as RESTful operations and procedures on the multidimensional data. A new attribute “SamplingPeriodCovered” can be used to indicate the time interval when the related time series data (or any multi-dimension data streams) are stored. This can reduce the total size of the data stored.
Methods, devices, and systems for migration or sharing of existing M2M service layer sessions are disclosed. In one embodiment, a Session Migration and Sharing Function (SMSF) performs the migration or sharing of a M2M service layer session. Various forms of service layer session context may be used to enable the migration and sharing of M2M service layer sessions.
G06F 15/16 - Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs
The performance of user equipment (UE) using sidelink radio communications may be improved by providing the UE with sidelink configuration information pertaining to modes, functions, channels, signals, and/or resources for use in sidelink communications. For example, a UE may receive information indicating a sidelink mode, e.g., a transmit-only, receive-only, or a transmit and receive mode. Sidelink configuration may include indications of signals and/or channels for use in sidelink transmit and/or receive communications, etc.
Methods, apparatus, and systems are described for addressing common beam operation, in which a Transmission Configuration Indicator (TCI) state (e.g., beam) may be indicated by a Downlink Control Information (DCI) and subsequently be applied to both control and data channels and, in some aspects, to both downlink and uplink.
H04B 7/06 - Diversity systemsMulti-antenna systems, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station
H04B 7/08 - Diversity systemsMulti-antenna systems, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the receiving station
H04L 5/00 - Arrangements affording multiple use of the transmission path
Methods, apparatus, and systems for beam management and BWP operations for NR NTN. Beam management methods for both one beam per cell and for multiple beams per cell may be implemented. A transmission configuration indication (TCI) state sequence also may be implemented, in which a network node may broadcast the transmission of TCI states.
H04B 7/06 - Diversity systemsMulti-antenna systems, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station
A first apparatus receives, from a second apparatus via a sidelink (SL) transmission, first configuration parameters for a first SL DRX group and second configuration parameters for a second SL DRX group. The first configuration parameters for the first SL DRX group comprise: a common SL DRX parameter set that is shared with the second configuration parameters for the second SL DRX group, and a first dedicated SL DRX configuration parameter set. The first dedicated DRX parameter set comprises: a first on duration at the beginning of a SL DRX cycle of the first apparatus, and a first duration: after an occasion of a PSCCH carrying a first-stage SL control information (SCI) indicates a new SL transmission for a MAC entity of the first apparatus, or after an occasion of a PSSCH carrying a second-stage SCI indicates a new SL transmission for the MAC entity of the first apparatus. The first apparatus determines that the first apparatus is in a first SL active time for receiving information on the SL based on the first configuration parameters for the first SL DRX group, and in a second SL active time for receiving information on the SL based on the configuration parameter for the second SL DRX group.
Methods and apparatuses are described herein for Multi cast/B roadcast Services (MBS). The embodiments described herein are directed to procedures for managing multiplexed MBS traffic, for prioritization between MBS related UL traffic, unicast UL traffic, and SL traffic, for handling HARQ retransmissions over C-RNTI, to support PDCP Status Reporting for MBS services, and for a wireless transmit/receive unit (WTRU) joining already started/ activated Multicast Sessions. In one example, a WTRU may receive multiplexed MBS services via one or more MBS radio bearers (MRB) and/or one or more unicast data radio bearers (DRBs). The WTRU may be configured with a single Service Data Adaptation Protocol (SDAP) entity for the MBS services, and demultiplexing of traffic may be performed at the SDAP layer. The WTRU may be configured to demultiplex multiple logical channels across different MBS services, where the logical channels are received over the same transport block.
A caching entity may store a cached copy of a service layer resource. An original hosting entity may maintain a registry of the corresponding cached resources. Optionally, the original hosting entity may set cache parameters to govern the lifetime of the cache on a caching entity. The caching entity may keep storing the cached copy of the resource and the original hosting entity may obtain statistics about the cached resource. By knowing the statistics, e.g. how many times a resource is retrieved on each caching entity, the original hosting entity may better manage the resource.
Radio network Positioning Reference Signals (PRSs) may be managed dynamically via user equipment (UE) requests triggered by measurements in accordance with initial PRS configurations, whereby a UE contacts an Access and Mobility Management Function (AMF) and/or a Location Management Function (LMF). Similarly, an LMF may initiate adjustments in PRS configurations and transmission via communications with base stations, UEs, and/or AMFs. Dynamic signaling of PRS configurations may be achieved via legacy protocols and/or New Radio Positioning Protocol A (NRPPa), for example. A requests from a UE for PRS configuration adjustment may include an indication of a required level of service or of a class of service, for example, and/or an indication of signal measurements, a position estimate, an indication of a capability of the UE.
H04W 64/00 - Locating users or terminals for network management purposes, e.g. mobility management
G01S 5/02 - Position-fixing by co-ordinating two or more direction or position-line determinationsPosition-fixing by co-ordinating two or more distance determinations using radio waves
Methods for dynamic user plane management may include new Layer 2 architectures for supporting simultaneous User Plane direct and indirect connections between a remote UE and gNB. Methods are described for dynamically managing UP Plane connections based on the QoS requirement of the traffic flow and the power consumption requirement of the remote UE. A method is described for dynamically managing CP connections between a remote UE and remote UE via a direct CP connection. A method is described for dynamically managing CP connections between a remote UE and remote UE via an indirect CP connection.
H04W 40/22 - Communication route or path selection, e.g. power-based or shortest path routing using selective relaying for reaching a BTS [Base Transceiver Station] or an access point
H04W 40/24 - Connectivity information management, e.g. connectivity discovery or connectivity update
83.
METHOD OF CONFIGURING PC5 DRX OPERATION IN 5G NETWORK
Methods, apparatus, and systems are described for improved discontinuous reception (DRX) for PCS communication (e.g., including unicast, groupcast and broadcast) for a User Equipment (UE) and particularly for reducing the power consumption.
The concept of a service layer message template is introduced, which may be a request template or a response template. Message templates may be created and stored at the service layer. Each message template may contain a set of request or response parameters and their values. Once in place, an application can send a request to the service layer that does not include the request parameters contained in the message template (i.e. request template); instead, a message template identifier may be sent. Since request parameters are included in the message template and stored at the service layer, communication overhead between the service layer and the application (or another service layer) may be reduced.
A lightweight and extensible information model for machine-to-machine systems is disclosed. A service layer information management architecture uses three categories of atomic objects, subjects, actions, and descriptions. Information for use within the model is built using the atomic information objects. Application programming interfaces are used to perform operations and information processing by different nodes. Common service functions are used in the model as instances of a generic common service information model.
Internet of Things (IoT) configurable event and action sequencing mechanisms for interconnecting various IoT events together to achieve an event and action sequencing process that may efficiently enable complex uses of the data available in IoT systems.
H04L 67/125 - Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks involving control of end-device applications over a network
H04W 4/70 - Services for machine-to-machine communication [M2M] or machine type communication [MTC]
G16Y 40/35 - Management of things, i.e. controlling in accordance with a policy or in order to achieve specified objectives
Methods, apparatus, and systems are described for improved edge network access for a UE. According to some aspects, a UE may receive a first Data Network Name (DNN) from an application and determine, based on a Data Network Name (DNN) Replacement Rule, the first DNN is associated with a second Data Network Name (DNN), where the first DNN and the second DNN are different. The UE may determine, based on the DNN Replacement Rule, to associate traffic from the application with a Protocol Data Unit (PDU) Session, where the PDU Session may be used to send data from the application to a network and the PDU Session is associated with the second DNN.
Methods are described for dynamically managing device locationing groups. According to some aspects, mobile devices may be tracked on a group basis, e.g., as opposed to being tracking on an individual basis. For example, location information for each of a plurality of mobile devices may be received at a location group server (LGS) and the LGS may determine (e.g., based on the location information) that each of the plurality of devices are in a physical location. One or more location group operations may be triggered by the location group server (e.g., based on determining that each of the plurality of devices are in the physical location) and the LGS may receive a location update from a device of the plurality of mobile devices (e.g., wherein the location update is not received from a remainder of the plurality of mobile devices).
Methods are described for improved application-layer Subscriber Identification Module (SIM) management on Multi-SIM user equipment (UEs). For example, application- layer SIM management solutions are defined for Multi-SIM UEs for supporting different applications. In one aspect, Dynamic SIM Switching based on Application Priority is provided.
Disclosed herein is service continuity assistance (SCA) functionality that may assist in the relocation of edge application server instance between different edge nodes in the system. The procedures may include: 1) edge application relocation target prediction and selection; 2) defining and generating relocation trigger; 3) proactive relocation; or 4) multi-application and multi-UE joint relocation.
A labeled data generation service provides an Internet-of-Things (IoT) system with a capability whereby users may configure how the system gathers, processes, and generates labeled data instances by: collecting and processing the data into a format required by supervised learning algorithms; generating expected outputs from data available in the IoT system; supporting the linking of collected inputs with generated expected outputs; forming labeled data instances; cleaning the labeled data set appropriately; sending the labeled data set to target nodes; and/or communicating with target nodes regarding improving the data processing and labeling processes, as required.
A user equipment. (UE) and a network may communicate to dynamically adapt the steering of traffic over both 3 GPP and non-3GPP accesses for uplink, downlink, or both. For example, a UE may request from the network the ability to dynamically adapt uplink traffic and the network may also apply the same traffic adaptation on downlink traffic. The UE and network may communicate dynamic traffic adaptation using traffic steering rules, e.g., via control plane NAS protocol, and with user plane signalling, e.g., via user plane PMF protocol.
Some underlying networks such as Low-Power Wide-Area Networks (LPWAN) have limited communication bandwidth and strict requirements on maximum message size. It is recognized herein that these requirements may pose a challenge for data or resource exchange between two service layer (SL) entities, for example, because resource representations to be exchanged may have too large a size to be supported by the underlying networks. In some cases, traditional data compression algorithms can be used to alleviate this problem to some degree, but it is recognized herein that there are associated computation costs due to compression and decompression that may not be affordable for constrained IoT devices. Various embodiments described herein address this problem, among others, by defining a Resource Representation Common Part (RRCP) and storing it at the service layer. In some cases, the RRCP is not transmitted between SL entities, thereby reducing SL message sizes to cater to the constraints of underlying networks.
H04L 67/60 - Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
H04L 47/76 - Admission controlResource allocation using dynamic resource allocation, e.g. in-call renegotiation requested by the user or requested by the network in response to changing network conditions
95.
Automated service enrollment in a machine-to-machine communications network
IoT service layer capabilities may be employed to automate and simplify the service enrollment process for IoT service subscribers/enrollees. These capabilities enable virtualization of a service subscriber and the physical IoT devices, applications, data and authorized users of the subscriber into a software profile that is representative of the subscriber. Once virtualized, a service subscriber may then delegate the complexities and burden of service enrollment to an automated IoT service enrollment software function.
Beam management for the downlink can be based on user equipment (UE) measurement of downlink (DL) reference signal (RS) and UE reporting. An alternative approach that may reduce overall RS overhead and latency is BM for the downlink based on uplink (UL) RS. With this approach, the network measures UL RS transmissions on multiple beams and uses these measurements for managing beams for the DL. Disclosed herein are various problems and enhancements related to UL RS based DL BM, in particular beam failure detection and recovery.
H04L 5/00 - Arrangements affording multiple use of the transmission path
H04B 7/06 - Diversity systemsMulti-antenna systems, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station
H04B 7/08 - Diversity systemsMulti-antenna systems, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the receiving station
Methods and apparatuses are described herein for remote UE mobility management. Methods are proposed to consider the impact of coverage through PC5 interface when a remote UE is doing the cell (re)selection. A remote UE may select a serving cell considering the impact of coverage through PC5 interface when the remote UE and the Relay UE are in coverage of different cells. The remote UE may detect and reselect a cell via the Uu interface while it has selected a serving cell via a Relay UE. The remote UE may detect and reselect to a cell via a Relay UE while it has selected a serving cell via the Uu interface.
Wireless User Equipment, UE, and network apparatuses may be adapted to facilitate continuity of Multicast/Broadcast Service, MBS, across cells. A UE in idle/inactive mode, for example, may receive MBS assistance information comprising scheduling information defining MBS reception windows and perform a cell reselection evaluation process accordingly. An UE in connected mode may conduct and report MBS quality measurements and receive an RRC reconfiguration comprising an MBS configuration for a target cell, determine that MBS transmission progress differs between the source cell and the target cell, and recover lost MBS PDUs or delete duplicate MBS PDUs accordingly. A network apparatus, such as a gNB for example, may map a GPRS Tunneling Protocol Sequence Number of an MBS PDU, to a Packet Data Convergence Protocol Sequence Number in a target cell, and determine an MBS configuration for use by a UE requesting a handover accordingly.
Methods, systems, and devices may assist in performing group-based paging, such as downlink control information-based group paging, paging radio network temporary identifier- based group paging, wakeup signal-based group paging, or sweep-based group paging. Also, method, systems, and devices may assist in performing beam-based paging or configuring cross- slot scheduling for paging.
Multicast/Broadcast Service (MBS) for user equipments (UE) in Radio Resource Control (RRC) idle/inactive modes via signally of MBS frequency ranges and/or switching between frequency ranges as required. Bandwidth Part (BWP) operation for MBS in RRC IDLE and RRC INACTIVE states may be implemented using a dedicated MBS BWP or by sharing a frequency range with other operations. An MBS frequency range may be wider or narrower than an initial BWP used by a UE, for example. MBS frequency range configure may be achieved in a number of ways, such as via Control Resource Set (CORESET), search space, and/or PDCCH monitoring occasions pattern settings for MBS in RRC idle/inactive. Downlink scheduling without dynamic grant for MBS in RRC idle/inactive may include configured scheduling and/or semi-persistent scheduling. Downlink repetition for MBS in RRC idle/inactive may include PDSCH repetition and/or PDCCH repetition
