WO2025066064A1

WO2025066064A1 - Communication method, apparatus, and system for mission session

Info

Publication number: WO2025066064A1
Application number: PCT/CN2024/084244
Authority: WO
Inventors: Chenchen YANG; Hang Zhang; Xu Li; Weisen SHI
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2023-09-29
Filing date: 2024-03-27
Publication date: 2025-04-03
Anticipated expiration: 2026-03-29

Abstract

Provided are a communication method, apparatus, and system for a mission session. The method includes: receiving, by a first service data adaptation protocol (SDAP) entity, a packet; transmitting, by the first SDAP entity, a SDAP packet generated by the first SDAP entity based on the packet, where the SDAP packet includes information on a mission session, the mission session is to provide a mission service to a mission customer, and the mission service is a service for both PDU connectivity and data processing.

Description

COMMUNICATION METHOD, APPARATUS, AND SYSTEM FOR MISSION SESSION

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to US provisional patent application No. 63/586,621, filed on September 29, 2023, which is hereby incorporated by reference in its entirety.

TECHNICAL FIELD

The present disclosure relates generally to the field of communications technologies and, in particular, to a communication method, apparatus, and system for a mission session.

BACKGROUND

Many new trends will trigger the consideration and design of 6G/future wireless networks: new network infrastructure capability, e.g., cloud natured/friendly infrastructures that are broadly deployed; new (relative) matured techniques, e.g., AI large scale models, Data de-privacy, Block chain, etc. that have made significant progresses and significantly impact on the entire society and human life; new apps and services, e.g., AI services, Data (sensing) service, Digital world service, etc. that are broadly applied in industry/business and used by individual customers; more global/open/collaborative operation trend, i.e., a more open and more collaborative operation mode are becoming common practice in many fields.

However, for a next generation (e.g. sixth generation (6G) or later) network, or a legacy (e.g. fifth generation (5G) , fourth generation (4G) , third generation (3G) or second generation (2G) ) network, e.g., in 6G era, the 6G network is expected to not only for connectivity, but also for data processing.

This background information is provided to reveal information believed by the applicant to be of possible relevance to the present disclosure. No admission is necessarily intended, nor should be construed, that any of the preceding information constitutes prior art against the present disclosure.

SUMMARY

In a first aspect, a communication method is provided in the present disclosure, including:

receiving, by a first service data adaptation protocol (SDAP) entity, a packet;

transmitting, by the first SDAP entity, a SDAP packet generated by the first SDAP entity based on the packet, where the SDAP packet includes information on a mission session, the mission session is to provide a mission service to a mission customer, and the mission service is a service for both PDU connectivity and data processing.

In this way, the mission service can be supported by the information on a mission session included in the SDAP packet.

In a possible implementation of the first aspect, the mission session includes one or more data sessions, each data session includes an association terminates at a computing block (CB) entity executing at least one CB of a mission, the mission includes one or more CBs and each CB corresponds to a computational step toward achieving the mission service.

In a possible implementation of the first aspect, the data processing includes the executing the at least one CB of the mission.

In a possible implementation of the first aspect, the CB entity is deployed in one of: a device, a radio access network (RAN) , a core network (CN) , and a data network (DN) .

In a possible implementation of the first aspect, the computational step toward achieving the mission service includes one or more of: artificial intelligence (AI) training, AI inference, data pre-processing, data privacy protection, data cleaning, data collection, data analytics, sensing, data sanitization, data management, data normalization, data aggregation, data splitting, useless data filtering, data formatting, data adaptation, data feature engineering, data compression, data embedding, data representation learning, or data feature extraction.

In a possible implementation of the first aspect, the information on a mission session is included in a packet header of the SDAP packet or a payload of the SDAP packet.

In a possible implementation of the first aspect, the information on a mission session includes one or more of: a mission session identifier (ID) identifying a mission session, a data session identifier (ID) identifying a data session, assistance information used for assisting in distinguishing a data session or distinguishing a CB, a quality of service (QoS) flow identifier (QFI) identifying a QoS flow in the mission session, a stream ID identifying a stream frame, a reflective data session indication (RDSI) , or a reflective data session to radio bearer mapping indication (RDDI) , and the RDSI indicates whether a non-access stratum (NAS) is to be informed of an updated of a service data flow (SDF) to data session mapping rule, and the RDDI indicates whether a data session to radio bearer mapping rule is to be updated.

In a possible implementation of the first aspect, the first SDAP entity corresponds to a data session and is dedicated for a data session.

In other words, the granularity of the first SDAP entity can be the data session.

In a possible implementation of the first aspect, the first SDAP entity is used for mapping one or more packets of the data session to one or more radio bearers, the one or more packets include the packet.

In this way, the first SDAP entity is enabled to map one or more packets of the data session (data session traffic) to one or more radio bearers.

In a possible implementation of the first aspect, a mapping relationship between the data session and the one or more radio bearers includes a one-to-one mapping relationship or a one-to-multiple mapping relationship, the one-to-one mapping relationship indicates that the data session is mapped to one radio bearer, and the one-to-multiple mapping relationship indicates that the data session is mapped to multiple radio bearers.

In a possible implementation of the first aspect, the information on a mission session includes either or both of a RDSI and a RDDI.

In a possible implementation of the first aspect, the data session includes one or more QoS flows, and the first SDAP entity is used for mapping one or more packets of the one or more QoS flows of the data session to one or more radio bearers, the one or more packets include the packet.

In this way, the first SDAP entity is enabled to map one or more packets of the one or more QoS flows of the data session (data session traffic) to one or more radio bearers.

In a possible implementation of the first aspect, a mapping relationship between the one or more QoS flows of the data session and the one or more radio bearers includes one or more of: a one-to-one mapping relationship or a multiple-to-one mapping relationship; the one-to-one mapping relationship indicates that one QoS flow of the data session is mapped to one radio bearer, and the multiple-to-one mapping relationship indicates that multiple QoS flows of the data session are mapped to one radio bearer.

In a possible implementation of the first aspect, the information on a mission session includes a QFI, where the QFI indicates a QoS flow associated with the SDAP packet.

In a possible implementation of the first aspect, the data session includes one or more QUIC streams, and the first SDAP entity is used for mapping one or more packets of the one or more QUIC streams of the data session to one or more radio bearers, the one or more packets include the packet.

In this way, the first SDAP entity is enabled to map one or more packets of the one or more QUIC streams of the data session (data session traffic) to one or more radio bearers.

In a possible implementation of the first aspect, a mapping relationship between the one or more QUIC streams of the data session and the one or more radio bearers includes a one-to-one mapping relationship or a multiple-to-one mapping relationship;

the one-to-one mapping relationship indicates that one QUIC stream of the data session is mapped to one radio bearer, and the multiple-to-one mapping relationship indicates that multiple QUIC streams of the data session are mapped to one radio bearer.

In a possible implementation of the first aspect, the information on a mission session includes a stream ID, and the stream ID indicates a stream frame for the data session associated with the SDAP packet.

In a possible implementation of the first aspect, the first SDAP entity corresponds to a mission session, and the first SDAP entity is dedicated for the mission session and is shared by one or more data sessions of the mission session.

In other words, the granularity of the first SDAP entity can be the mission session.

In a possible implementation of the first aspect, the first SDAP entity is used for mapping one or more packets of the mission session to one or more radio bearers, the one or more packets include the packet.

In this way, the first SDAP entity is enabled to map one or more packets of the mission session (mission session traffic) to one or more radio bearers.

In a possible implementation of the first aspect, a mapping relationship between the mission session and the one or more radio bearers includes a one-to-one mapping relationship or a one-to-multiple mapping relationship; the one-to-one mapping relationship indicates that the mission session is mapped to one radio bearer, and the one-to-multiple mapping relationship indicates that the mission session are mapped to multiple radio bearers.

In a possible implementation of the first aspect, the mapping relationship between the mission session and the one or more radio bearers further includes a mapping relationship between one or more data sessions of the mission session and the one or more radio bearers; the mapping relationship between the one or more data sessions of the mission session and the one or more radio bearers includes one or more of: a one-to-one mapping relationship, a one-to-multiple mapping relationship, or a multiple-to-one mapping relationship; the one-to-one mapping relationship indicates that one data session of the mission session is mapped to one radio bearer, the one-to-multiple mapping relationship indicates that one data session of the mission session are mapped to multiple radio bearers, and the multiple-to-one mapping relationship indicates that multiple data sessions of the mission session are mapped to one radio bearer.

In a possible implementation of the first aspect, the information on a mission session includes either or both of a data session ID and assistance information, the data session ID is used to identify a data session, and the assistance information is used to assist in distinguishing the data session or distinguishing a CB.

In a possible implementation of the first aspect, each data session of the mission session includes at least one QoS flow, and the first SDAP entity is used for mapping one or more packets of one or more QoS flows of the one or more data sessions of the mission session to one or more radio bearers, the one or more packets include the packet.

In this way, the first SDAP entity is enabled to map one or more packets of one or more QoS flows of the one or more data sessions of the mission session (mission session traffic) to one or more radio bearers.

In a possible implementation of the first aspect, a mapping relationship between the one or more QoS flows of the one or more data sessions of the mission session and the one or more radio bearers includes one or more of: a one-to-one mapping relationship, or a multiple-to-one mapping relationship; the one-to-one mapping relationship indicates that a packet of one QoS flow of the one or more data sessions of the mission session is mapped to one radio bearer, and the multiple-to-one mapping relationship indicates that packets of multiple QoS flows of the one or more data sessions of the mission session are mapped to one radio bearer.

In a possible implementation of the first aspect, the information on a mission session includes a QFI and either or both of a data session ID and assistance information, where the QFI indicates a QoS flow associated with the SDAP packet, the data session ID is used to identify a data session, and the assistance information is used to assist in distinguishing the data session or distinguishing a CB.

In a possible implementation of the first aspect, the information on a mission session includes a QFI, and the QFI indicates a QoS flow associated with the SDAP packet, and the QFI includes either or both of: a field indicating a data session ID used to identify a data session, and a field indicating assistance information used to assist in distinguishing a data session or distinguishing a CB.

In a possible implementation of the first aspect, the mission session includes one or more QUIC streams, and the first SDAP entity is used for mapping one or more packets of the one or more QUIC streams of the mission session to one or more radio bearers, the one or more packets include the packet.

In this way, the first SDAP entity is enabled to map one or more packets of one or more QUIC streams of the one or more data sessions of the mission session (mission session traffic) to one or more radio bearers.

In a possible implementation of the first aspect, a mapping relationship between the one or more QUIC streams of the mission session and the one or more radio bearers includes a one-to-one mapping relationship or a multiple-to-one mapping relationship; the one-to-one mapping relationship indicates that a packet of one QUIC stream of the mission session is mapped to one radio bearer, and the multiple-to-one mapping relationship indicates that packets of multiple QUIC streams of the mission session are mapped to one radio bearer.

In a possible implementation of the first aspect, the information on a mission session includes a stream ID and either or both of a data session ID and assistance information, where the stream ID is used to identify a stream frame for the mission session associated with the SDAP packet, the data session ID is used to identify a data session, and the assistance information is used to assist in distinguishing a data session or distinguishing a CB.

In a possible implementation of the first aspect, the information on a mission session includes a stream ID, and the stream ID indicates a stream frame for the mission session associated with the SDAP packet, and the stream ID includes either or both of: a field indicating a data session ID used to identify a data session, and a field indicating assistance information used to assist in distinguishing a data session or distinguishing a CB.

In a possible implementation of the first aspect, the first SDAP entity corresponds to a network entity, the first SDAP entity is dedicated for the network entity and is shared by one or more mission sessions of the network entity, and the one or more mission sessions include the mission session.

In other words, the granularity of the first SDAP entity can be the network entity.

In a possible implementation of the first aspect, the first SDAP entity is used for mapping one or more packets of the network entity to one or more radio bearers, the one or more packets include the packet.

In this way, the first SDAP entity is enabled to map one or more packets of the network entity to one or more radio bearers.

In a possible implementation of the first aspect, a mapping relationship between the network entity and the one or more radio bearers includes a one-to-one mapping relationship or a one-to-multiple mapping relationship; the one-to-one mapping relationship indicates that one or more packets of one network entity are mapped to one radio bearer, and the one-to-multiple mapping relationship indicates that packets of one network entity are mapped to multiple radio bearers.

In a possible implementation of the first aspect, the mapping relationship between the network entity and the one or more radio bearers further includes a mapping relationship between one or more mission sessions of the network entity and the one or more radio bearers; the mapping relationship between the one or more mission sessions of the network entity and the one or more radio bearers includes one or more of: a one-to-one mapping relationship, a one-to-multiple mapping relationship, or a multiple-to-one mapping relationship; the one-to-one mapping relationship indicates that one mission session of the network entity is mapped to one radio bearer, the one-to-multiple mapping relationship indicates one mission session of the network entity is mapped to multiple radio bearers, and the multiple-to-one mapping relationship indicates that multiple mission sessions of the network entity are mapped to one radio bearer.

In a possible implementation of the first aspect, the mapping relationship between the one or more mission sessions of the network entity and the one or more radio bearers further includes a mapping relationship between one or more data sessions of the one or more mission sessions of the network entity and the one or more radio bearers; the mapping relationship between the one or more data sessions of the one or more mission sessions of the network entity and the one or more radio bearers includes one or more of: a one-to-one mapping relationship, a one-to-multiple mapping relationship, or a multiple-to-one mapping relationship; the one-to-one mapping relationship indicates that one data session of the one or more mission sessions of the network entity is mapped to one radio bearer, the one-to-multiple mapping relationship indicates that one data session of the one or more mission sessions of the network entity is mapped to multiple radio bearers, and the multiple-to-one mapping relationship indicates that multiple data sessions of the one or more mission sessions of the network entity are mapped to one radio bearer.

In a possible implementation of the first aspect, the information on a mission session includes one or more of: a mission session ID, a data session ID, or assistance information;

the mission session ID is used to identify a mission session, the data session ID is used to identify a data session included in the mission session, and the assistance information is used to assist in distinguishing the data session or distinguishing a CB.

In a possible implementation of the first aspect, the information on a mission session further includes either or both of a RDSI and a RDDI.

In a possible implementation of the first aspect, each data session of a mission session of a network entity includes at least one QoS flow, and the first SDAP entity is used for mapping one or more packets of one or more QoS flows to one or more radio bearers, the one or more packets include the packet.

In this way, the first SDAP entity is enabled to map one or more packets of one or more QoS flows to one or more radio bearers.

In a possible implementation of the first aspect, a mapping relationship between the one or more QoS flows and the one or more radio bearers includes one or more of: a one-to-one mapping relationship, or a multiple-to-one mapping relationship; the one-to-one mapping relationship indicates that one QoS flow is mapped to one radio bearer, and the multiple-to-one mapping relationship indicates that multiple QoS flows are mapped to one radio bearer.

In a possible implementation of the first aspect, the information on a mission session includes a QFI and one or more of: a mission session ID, a data session ID or assistance information, where the QFI indicates a QoS flow associated with the SDAP packet, the mission session ID is used to identify a mission session, the data session ID is used to identify a data session, and the assistance information is used to assist in distinguishing the data session or distinguishing a CB.

In a possible implementation of the first aspect, the information on a mission session includes a QFI, and the QFI indicates a QoS flow associated with the SDAP packet, and the QFI includes one or more of: a field indicating mission session ID used to identify a mission session, a field indicating a data session ID used to identify a data session, or a field indicating assistance information used to assist in distinguishing a data session or distinguishing a CB.

In a possible implementation of the first aspect, the one or more mission sessions of the network entity includes one or more QUIC streams, and the first SDAP entity is used for mapping one or more packets of the one or more QUIC streams of the network entity to one or more radio bearers, the one or more packets include the packet.

In this way, the first SDAP entity is enabled to map one or more packets of one or more QUIC streams to one or more radio bearers.

In a possible implementation of the first aspect, a mapping relationship between the one or more QUIC streams of the network entity and the one or more radio bearers includes a one-to-one mapping relationship or a multiple-to-one mapping relationship; the one-to-one mapping relationship indicates that one QUIC stream of the network entity is mapped to one radio bearer, and the multiple-to-one mapping relationship indicates that multiple QUIC streams of the network entity are mapped to one radio bearer.

In a possible implementation of the first aspect, the information on a mission session includes a stream ID and one or more of: a mission session ID, a data session ID or assistance information, where the stream ID is used to identify a stream frame for the network entity associated with the SDAP packet, the mission session ID is used to identify a mission session, the data session ID is used to identify a data session, and the assistance information is used to assist in distinguishing a data session or distinguishing a CB.

In a possible implementation of the first aspect, the information on a mission session includes a stream ID, where the stream ID indicates a stream frame for the network entity associated with the SDAP packet, and the stream ID includes one or more of: a field indicating mission session ID used to identify a mission session, a field indicating a data session ID used to identify a data session, or a field indicating assistance information used to assist in distinguishing a data session or distinguishing a CB.

In a possible implementation of the first aspect, the network entity is one of a device, a RAN node, a CB entity of a RAN, or a gateway (GW) entity.

In a possible implementation of the first aspect, where the one or more radio bearers include one or more data radio bearers, one or more mission data radio bearers, or one or more sidelink radio bearers, where the one or more data radio bearers are used for the PDU connectivity, the one or more mission data radio bearers are used for the mission service, and the one or more sidelink radio bearers are used for a sidelink service.

In a possible implementation of the first aspect, the first SDAP entity is deployed in an apparatus, and the apparatus is a device side apparatus or a RAN node side apparatus.

In a possible implementation of the first aspect, the method further includes:

receiving, by the device side apparatus, a first message from a RAN node side apparatus, where the first message includes configuration information, and the configuration information is used to establish, reconfigure, resume or release one or more SDAP entities including the first SDAP entity; and

establishing, reconfiguring, resuming or releasing, by the device side apparatus, the one or more SDAP entities including the first SDAP entity according to the first message.

In this way, the configuration information on SDAP entity is received by the device side apparatus is enabled to establish, reconfigure, resume or release the one or more SDAP entities for the mission session by receiving the configuration information on SDAP entity included in the first message.

In a possible implementation of the first aspect, the configuration information indicates one or more of: one or more mission sessions, one or more data sessions, one or more QoS flows, mapping information, or SDAP entity granularity information; and

the SDAP entity granularity information indicates that the first SDAP entity is an SDAP entity corresponding to a data session and dedicated for the data session, an SDAP entity corresponding to a mission session and dedicated for the mission session, or an SDAP entity corresponding to a network entity and dedicated for the network entity;

the mapping information includes one or more of:

a mapping relationship between the one or more mission sessions and the one or more data sessions,

a mapping relationship between the one or more data sessions and the one or more QoS flows, or

a mapping relationship among the one or more mission sessions, the one or more data sessions and the one or more QoS flows.

In a possible implementation of the first aspect, the one or more mission sessions are identified by one or more mission session IDs or a session group ID; the one or more data sessions are identified by one or more data session IDs; and the one or more QoS flows are identified by one or more QFIs.

In a possible implementation of the first aspect, the first message includes a radio bearer ID identifying a radio bearer and the one or more mission session IDs or the session group ID identifying the one or more mission sessions, and the one or more mission sessions are to be mapped to the radio bearer.

In a possible implementation of the first aspect, the first message includes a radio bearer ID identifying a radio bearer and the one or more data session IDs identifying the one or more data sessions, and the one or more data sessions are to be mapped to the radio bearer.

In a possible implementation of the first aspect, the first message includes a radio bearer ID identifying a radio bearer and the one or more QFIs identifying the one or more QoS flows, and the one or more QoS flows are to be mapped to the radio bearer.

In a possible implementation of the first aspect, the mapping relationship between the one or more mission sessions and the one or more data sessions indicates parts of the one or more data sessions identified by the one or more data session IDs belongs to a mission session of the one or more mission sessions identified by the one or more mission session IDs or the session group ID.

In a possible implementation of the first aspect, the mapping relationship between the one or more data sessions and the one or more QoS flows indicates parts of the one or more QoS flows identified by the one or more QFIs belongs to a data session of the one or more data sessions identified by the one or more data session IDs.

In a possible implementation of the first aspect, the mapping relationship among the one or more mission sessions, the one or more data sessions and the one or more QoS flows indicates: parts of the one or more QoS flows identified by the one or more QFIs belongs to a data session of the one or more data sessions identified by the one or more data session IDs, and parts of the one or more data sessions identified by the one or more data session IDs belongs to a mission session of the one or more mission sessions identified by the one or more mission session IDs or a session group ID.

In a possible implementation of the first aspect, the first SDAP entity corresponds to a data session and is dedicated for a data session, the configuration information includes a mission session ID, a data session ID, and one or more QFIs, and the mapping information is indicated by a sequence structure of the mission session ID, the data session ID, and the one or more QFIs.

In a possible implementation of the first aspect, the configuration information indicates the SDAP entity granularity information, and

the SDAP entity granularity information is indicated by an indication included in the configuration information; or

the SDAP entity granularity information is indicated by one data session ID listed in the configuration information.

In a possible implementation of the first aspect, the first SDAP entity corresponds to a mission session, and the first SDAP entity is dedicated for the mission session and is shared by one or more data sessions of the mission session, the configuration information includes: a mission session ID, one or more data session IDs, and one or more QFIs, and the mapping information is indicated by a sequence structure of the mission session ID, the one or more data session IDs, and the one or more QFIs.

the SDAP entity granularity information is indicated by one mission session ID listed in the configuration information.

In a possible implementation of the first aspect, the first SDAP entity corresponds to a network entity, the first SDAP entity is dedicated for the network entity and is shared by one or more mission sessions of the network entity, and the one or more mission sessions include the mission session, the configuration information includes: one or more mission session IDs, one or more data session IDs, one or more QFIs, and the mapping information is indicated by a sequence structure of the one or more mission session IDs, the one or more data session IDs, and the one or more QFIs.

the SDAP entity granularity information is indicated by multiple mission session IDs listed in the configuration information.

In a possible implementation of the first aspect, the indication is a string or a bitmap.

In a possible implementation of the first aspect, the configuration information further includes one or more values of assistance information.

In a possible implementation of the first aspect, the configuration information is determined by the RAN node side apparatus according to a second message from a CN node, and the second message is used by the RAN node side apparatus to determine the configuration information.

In this way, the RAN node side apparatus is enabled to determine the configuration information by receiving second message from the CN node.

In a possible implementation of the first aspect, the second message indicates one or more of: one or more mission sessions, one or more data sessions, one or more QoS flows, mapping information, or SDAP entity granularity information, and

the SDAP entity granularity information indicates that the first SDAP entity is an SDAP entity corresponding to a data session and dedicated for the data session, an SDAP entity corresponding to a mission session and dedicated for the mission session, or an SDAP entity corresponding to a network entity and dedicated for the network entity,

the mapping information includes one or more of: a mapping relationship between the one or more mission sessions and the one or more data sessions, or a mapping relationship between the one or more data sessions and the one or more QoS flows, or a mapping relationship among the one or more mission sessions, the one or more data sessions and the one or more QoS flows.

In a possible implementation of the first aspect, the one or more mission sessions are identified by one or more mission session IDs or a session group ID; the one or more data sessions are identified by one or more data session IDs; the one or more QoS flows are identified by one or more QFIs.

In a possible implementation of the first aspect, the mapping relationship between the one or more mission sessions and the one or more data sessions indicates parts of the one or more data sessions identified by the one or more data session IDs belongs to a mission session of the one or more mission sessions identified by the one or more mission session IDs or a session group ID.

In a possible implementation of the first aspect, the second message is used by the RAN node side apparatus to determine one or more of:

a number of radio bearers to be mapped to for a data session or a mission session;

at least one of one or more data sessions, one or more mission sessions, or one or more QoS flows, to be mapped to a radio bearer; or

the SDAP entity granularity information.

In a possible implementation of the first aspect, the receiving, by the device side apparatus, the first message from the RAN node side apparatus includes:

receiving, by the device side apparatus, the first message from the RAN node side apparatus in a radio bearer setup procedure, a radio bearer reconfiguration procedure, a radio bearer resume procedure, or a radio bearer release procedure.

In this way, the device side apparatus can be configured in a radio bearer setup procedure, a radio bearer reconfiguration procedure, a radio bearer resume procedure, or a radio bearer release procedure.

In a possible implementation of the first aspect, the method further includes:

receiving, by the RAN node side apparatus, a second message from a CN node, where the second message is used by the RAN node side apparatus to determine configuration information for the device side apparatus; and

determining, by the RAN node side apparatus, the configuration information for the device side apparatus.

In this way, the RAN node side apparatus is enabled to determine the configuration information for the device side apparatus by receiving second message from the CN node.

In a possible implementation of the first aspect, the determining the configuration information for the device side apparatus includes one or more of:

determining a number of radio bearers to be mapped to for a data session or a mission session;

determining at least one of one or more data sessions, one or more mission sessions, or one or more QoS flows, to be mapped to a radio bearer; or

determining the SDAP entity granularity information.

In a possible implementation of the first aspect, the first message or the second message includes a radio resource control (RRC) message or an X as a service (XaaS) service signaling bearer (XSB) message.

In a possible implementation of the first aspect, a value of the assistance information included in the information or a value of the assistance information included in the configuration information includes at least one of:an action ID identifying an action of data processing, a computing block ID (CBID) identifying a CB, a step ID identifying a step of a procedure, and a mission customer ID identifying a customer of a mission session.

In a possible implementation of the first aspect, the mission service is reduced to a service for PDU connectivity only.

In a possible implementation of the first aspect, the mission session is reduced to a PDU session to be used for PDU connectivity.

In a possible implementation of the first aspect, there is no CB entity involved in the mission session, or all CB entities involved in the mission session are dummy CB entities.

In a possible implementation of the first aspect, there is no data session belonging to the mission session, or all data sessions belong to the mission session are dummy data sessions.

In a second aspect, a communication method is provided in the present disclosure, including:

receiving, by a second service data adaptation protocol (SDAP) entity, a SDAP packet from a first SDAP entity, where the SDAP packet includes information on a mission session, the mission session is to provide a mission service to a mission customer, and the mission service is a service for both PDU connectivity and data processing; and

determining, by the second SDAP entity, according to the information on a mission session, which mission session the SDAP packet belongs to.

In this way, the mission service can be supported by the information on a mission session included in the SDAP packet. By virtue of the information, second SDAP entity receiving the SDAP packet can recognize which mission session the SDAP packet belongs to.

In a possible implementation of the second aspect, the mission session includes one or more data sessions, each data session includes an association terminates at a computing block (CB) entity executing at least one CB of a mission, the mission includes one or more CBs and each CB corresponds to a computational step toward achieving the mission service.

In a possible implementation of the second aspect, the data processing includes the executing the at least one CB of the mission.

In a possible implementation of the second aspect, the CB entity is deployed in one of: a device, a radio access network (RAN) , a core network (CN) , and a data network (DN) .

In a possible implementation of the second aspect, the computational step toward achieving the mission service includes one or more of: artificial intelligence (AI) training, AI inference, data pre-processing, data privacy protection, data cleaning, data collection, data analytics, sensing, data sanitization, data management, data normalization, data aggregation, data splitting, useless data filtering, data formatting, data adaptation, data feature engineering, data compression, data embedding, data representation learning, or data feature extraction.

In a possible implementation of the second aspect, the information on a mission session is included in a packet header of the SDAP packet or a payload of the SDAP packet.

In a possible implementation of the second aspect, the information on a mission session includes one or more of: a mission session identifier (ID) identifying a mission session, a data session ID identifying a data session, assistance information used for assisting in distinguishing a data session or distinguishing a CB, a quality of service (QoS) flow identifier (QFI) identifying a QoS flow in the mission session, a stream ID identifying a stream frame, a reflective data session indication (RDSI) , or a reflective data session to radio bearer mapping indication (RDDI) , and the RDSI indicates whether a non-access stratum (NAS) is to be informed of an updated of a service data flow (SDF) to data session mapping rule, and the RDDI indicates whether a data session to radio bearer mapping rule is to be updated.

In a possible implementation of the second aspect, the second SDAP entity is deployed in an apparatus, and the apparatus is a device side apparatus or a RAN node side apparatus.

In a possible implementation of the second aspect, the method further includes:

receiving, by the device side apparatus, a first message from a RAN node side apparatus, where the first message includes configuration information, and the configuration information is used to establish, reconfigure, resume or release one or more SDAP entities including the second SDAP entity; and

establishing, reconfiguring, resuming or releasing, by the device side apparatus, the SDAP entities including the second SDAP entity according to the first message.

In a possible implementation of the second aspect, the configuration information indicates one or more of:one or more mission sessions, one or more data sessions, one or more QoS flows, mapping information, or SDAP entity granularity information; and

the SDAP entity granularity information indicates that the second SDAP entity is an SDAP entity corresponding to a data session and dedicated for the data session, an SDAP entity corresponding to a mission session and dedicated for the mission session, or an SDAP entity corresponding to a network entity and dedicated for the network entity;

the mapping information includes one or more of:

In a possible implementation of the second aspect, the one or more mission sessions are identified by one or more mission session IDs or a session group ID; the one or more data sessions are identified by one or more data session IDs; and the one or more QoS flows are identified by one or more QFIs.

In a possible implementation of the second aspect, the first message includes a radio bearer ID identifying a radio bearer, and the one or more mission session IDs or the session group ID identifying the one or more mission sessions, and the one or more mission sessions are to be mapped to the radio bearer.

In a possible implementation of the second aspect, the first message includes a radio bearer ID identifying a radio bearer and the one or more data session IDs identifying the one or more data sessions, and the one or more data sessions are to be mapped to the radio bearer.

In a possible implementation of the second aspect, the first message includes a radio bearer ID identifying a radio bearer and the one or more QFIs identifying the one or more QoS flows, and the one or more QoS flows are to be mapped to the radio bearer.

In a possible implementation of the second aspect, the mapping relationship between the one or more mission sessions and the one or more data sessions indicates parts of the one or more data sessions identified by the one or more data session IDs belongs to a mission session of the one or more mission sessions identified by the one or more mission session IDs or the session group ID.

In a possible implementation of the second aspect, the mapping relationship between the one or more data sessions and the one or more QoS flows indicates parts of the one or more QoS flows identified by the one or more QFIs belongs to a data session of the one or more data sessions identified by the one or more data session IDs.

In a possible implementation of the second aspect, the mapping relationship among the one or more mission sessions, the one or more data sessions and the one or more QoS flows indicates: parts of the one or more QoS flows identified by the one or more QFIs belongs to a data session of the one or more data sessions identified by the one or more data session IDs, and parts of the one or more data sessions identified by the one or more data session IDs belongs to a mission session of the one or more mission sessions identified by the one or more mission session IDs or a session group ID.

In a possible implementation of the second aspect, the second SDAP entity corresponds to a data session and is dedicated for a data session, the configuration information includes a mission session ID, a data session ID, and one or more QFIs, and the mapping information is indicated by a sequence structure of the mission session ID, the data session ID, and the one or more QFIs.

In a possible implementation of the second aspect, the configuration information indicates the SDAP entity granularity information, and

In a possible implementation of the second aspect, the second SDAP entity corresponds to a mission session, and the second SDAP entity is dedicated for the mission session and is shared by one or more data sessions of the mission session, the configuration information includes: a mission session ID, one or more data session IDs, and one or more QFIs, and the mapping information is indicated by a sequence structure of the mission session ID, the one or more data session IDs, and the one or more QFIs.

In a possible implementation of the second aspect, the second SDAP entity corresponds to a network entity, the second SDAP entity is dedicated for the network entity and is shared by one or more mission sessions of the network entity, and the one or more mission sessions include the mission session, the configuration information includes: one or more mission session IDs, one or more data session IDs, one or more QFIs, and the mapping information is indicated by a sequence structure of the one or more mission session IDs, the one or more data session IDs, and the one or more QFIs.

In a possible implementation of the second aspect, the indication is a string or a bitmap.

In a possible implementation of the second aspect, the configuration information further includes one or more values of assistance information.

In a possible implementation of the second aspect, the configuration information is determined by the RAN node side apparatus according to a second message from a CN node, and the second message is used by the RAN node side apparatus to determine the configuration information.

In a possible implementation of the second aspect, the second message indicates one or more of: one or more mission sessions, one or more data sessions, one or more QoS flows, mapping information, or SDAP entity granularity information, and

the SDAP entity granularity information indicates that the second SDAP entity is an SDAP entity corresponding to a data session and dedicated for the data session, an SDAP entity corresponding to a mission session and dedicated for the mission session, or an SDAP entity corresponding to a network entity and dedicated for the network entity,

In a possible implementation of the second aspect, the mapping relationship between the one or more mission sessions and the one or more data sessions indicates parts of the one or more data sessions identified by the one or more data session IDs belongs to a mission session of the one or more mission sessions identified by the one or more mission session IDs or a session group ID.

In a possible implementation of the second aspect, the second message is used by the RAN node side apparatus to determine one or more of:

the SDAP entity granularity information.

In a possible implementation of the second aspect, receiving the first message from the RAN node side apparatus includes:

receiving the first message from the RAN node side apparatus in a radio bearer setup procedure, a radio bearer reconfiguration procedure, a radio bearer resume procedure, or a radio bearer release procedure.

In a possible implementation of the second aspect, the method further includes:

In a possible implementation of the second aspect, the determining the configuration information for the device side apparatus includes one or more of:

determining the SDAP entity granularity information.

In a possible implementation of the second aspect, the first message or the second message includes a radio resource control (RRC) message or an X as a service (XaaS) service signaling bearer (XSB) message.

In a possible implementation of the second aspect, a value of the assistance information included in the configuration information includes at least one of: an action ID identifying an action of data processing, a CBID identifying a CB, a step ID identifying a step of a procedure, and a mission customer ID identifying a customer of a mission session.

In a possible implementation of the second aspect, the mission service is reduced to a service for PDU connectivity only.

In a possible implementation of the second aspect, the mission session is reduced to a PDU session to be used for PDU connectivity.

In a possible implementation of the second aspect, there is no CB entity involved in the mission session, or all CB entities involved in the mission session are dummy CB entities.

In a possible implementation of the second aspect, there is no data session belonging to the mission session, or all data sessions belong to the mission session are dummy data sessions.

In a third aspect, a communication apparatus is provided in the present disclosure, including:

a receiving module, configured to receive a packet; and

a transmitting module, configured to transmit a service data adaptation protocol (SDAP) packet generated by a first SDAP entity based on the packet, where the SDAP packet includes information on a mission session, the mission session is to provide a mission service to a mission customer, and the mission service is a service for both PDU connectivity and data processing.

In a fourth aspect, a communication apparatus is provided in the present disclosure, including:

a receiving module, configured to receive a service data adaptation protocol (SDAP) packet from a first SDAP entity, where the SDAP packet includes information on a mission session, the mission session is to provide a mission service to a mission customer, and the mission service is a service for both PDU connectivity and data processing; and

a determining module, configured to determine, according to the information on a mission session, which mission session the SDAP packet belongs to.

In a fifth aspect, an apparatus is provided in the present disclosure, including processing circuitry for performing the method in the first aspect or the second aspect or any possible implementations of the first aspect or the second aspect.

In a sixth aspect, a chip is provided in the present disclosure, including an input/output (I/O) interface and a processor, where the processor is configured to call and run a computer program stored in a memory, to enable a device installing with the chip to perform the method in the first aspect or the second aspect or any possible implementations of the first aspect or the second aspect.

In a seventh aspect, an electronic device is provided in the present disclosure, including:

one or more processors,

the one or more processors is configured to execute instructions stored in a memory, when the instructions are executed by the one or more processors, the method in the first aspect or any possible implementations of the first aspect is performed.

In an eighth aspect, an electronic device is provided in the present disclosure, including:

one or more processors,

the one or more processors is configured to execute instructions stored in a memory, when the instructions are executed by the one or more processors, the method in the second aspect or any possible implementations of the second aspect is performed.

In a ninth aspect, a server system is provided in the present disclosure, including the electronic device in the seventh aspect and the electronic device in the eighth aspect.

In a tenth aspect, a non-transitory computer-readable medium is provided in the present disclosure, carrying a program code which, when executed by a processor, the method in the first aspect or the second aspect or any possible implementations of the first aspect or the second aspect is performed.

In an eleventh aspect, a computer program product is provided in the present disclosure, including program code for performing the method in the first aspect or the second aspect or any possible implementations of the first aspect or the second aspect.

BRIEF DESCRIPTION OF DRAWINGS

The accompanying drawings are used to provide a further understanding of the present disclosure, constitute a part of the specification, and are used to explain the present disclosure together with the following specific example embodiments, but should not be construed as limiting the present disclosure.

FIG. 1 is a simplified schematic illustration of a communication system according to one or more embodiments of the present disclosure.

FIG. 2 is a schematic illustration of an example communication system according to one or more embodiments of the present disclosure.

FIG. 3 is a schematic illustration of a basic component structure of a communication system according to one or more embodiments of the present disclosure.

FIG. 4 illustrates a block diagram of a device in a communication system according to one or more embodiments of the present disclosure.

FIG. 5 illustrates a block diagram of 6G System conceptual structure according to one or more embodiments of the present disclosure.

FIG. 6 is a schematic illustration of 5G PDU session according to one or more embodiments of the present disclosure.

FIG. 7 is a schematic illustration of a 5G user plane protocol stack between UE and gNB according to one or more embodiments of the present disclosure.

FIG. 8 is a schematic illustration of a structure view of a SDAP sublayer according to one or more embodiments of the present disclosure.

FIG. 9 is a schematic illustration of a downlink (DL) SDAP data PDU format with a SDAP header according to one or more embodiments of the present disclosure.

FIG. 10 is a schematic illustration of an uplink (UL) SDAP data PDU format with a SDAP header according to one or more embodiments of the present disclosure.

FIG. 11 is a schematic illustration of SDAP configuration information when a DRB is established according to one or more embodiments of the present disclosure.

FIG. 12 is a schematic illustration of a SDAP configuration information element when an SDAP entity is established per PDU session according to one or more embodiments of the present disclosure.

FIG. 13 is a schematic illustration of a mission service provided by a 6G network according to one or more embodiments of the present disclosure.

FIG. 14 is a schematic illustration of a mission session for a mission service according to one or more embodiments of the present disclosure.

FIG. 15 is a schematic illustration of tunnels configured per data (inter-GW) session according to one or more embodiments of the present disclosure.

FIG. 16 is a schematic illustration of tunnels configured per mission session according to one or more embodiments of the present disclosure.

FIG. 17 is a schematic illustration of tunnels configured per network entity according to one or more embodiments of the present disclosure.

FIG. 18 is a schematic flowchart of a communication method according to one or more embodiments of the present disclosure.

FIG. 19 is a schematic illustration of a functional view of the SDAP sublayer for the mission service.

FIG. 20 is a schematic illustration of SDAP entities configured per data session according to one or more embodiments of the present disclosure.

FIG. 21 is a schematic illustration of a DL SDAP data PDU format for a SDAP entity per data session according to one or more embodiments of the present disclosure.

FIG. 22 is a schematic illustration of a UL SDAP data PDU format for a SDAP entity per data session according to one or more embodiments of the present disclosure.

FIG. 23 is a schematic illustration of SDAP entities configured per mission session according to one or more embodiments of the present disclosure.

FIG. 24 is a schematic illustration of a DL SDAP data PDU format for a SDAP entity per mission session with a QFI according to one or more embodiments of the present disclosure.

FIG. 25 is a schematic illustration of a UL SDAP data PDU format for a SDAP entity per mission session with a QFI according to one or more embodiments of the present disclosure.

FIG. 26 is a schematic illustration of a DL SDAP data PDU format for a SDAP entity per mission session without a QFI according to one or more embodiments of the present disclosure.

FIG. 27 is a schematic illustration of a UL SDAP data PDU format for a SDAP entity per mission session without a QFI according to one or more embodiments of the present disclosure.

FIG. 28 is a schematic illustration of SDAP entities configured per network entity according to one or more embodiments of the present disclosure.

FIG. 29 is a schematic illustration of a DL SDAP data PDU format for a SDAP entity per network entity with a QFI according to one or more embodiments of the present disclosure.

FIG. 30 is a schematic illustration of a UL SDAP data PDU format for a SDAP entity per network entity with a QFI according to one or more embodiments of the present disclosure.

FIG. 31 is a schematic illustration of a DL SDAP data PDU format for a SDAP entity per network entity without a QFI according to one or more embodiments of the present disclosure.

FIG. 32 is a schematic illustration of a UL SDAP data PDU format for a SDAP entity per network entity without a QFI according to one or more embodiments of the present disclosure.

FIG. 33 is a schematic illustration of a procedure for the SDAP entity configuration according to one or more embodiments of the present disclosure.

FIG. 34 is a schematic illustration of a SDAP configuration information element for a SDAP entity per data session according to one or more embodiments of the present disclosure.

FIG. 35 is a schematic illustration of another SDAP configuration information element for a SDAP entity per data session according to one or more embodiments of the present disclosure.

FIG. 36 is a schematic illustration of a SDAP configuration information element for a SDAP entity per mission session according to one or more embodiments of the present disclosure.

FIG. 37 is a schematic illustration of a SDAP configuration information element for a SDAP entity per network entity according to one or more embodiments of the present disclosure.

FIG. 38 is a schematic illustration of a SDAP configuration information element for a SDAP entity according to one or more embodiments of the present disclosure.

FIG. 39 is a schematic illustration of a procedure of determination of the configuration information according to one or more embodiments of the present disclosure.

FIG. 40 is a structural diagram of a communication apparatus according to one or more embodiments of the present disclosure.

DESCRIPTION OF EMBODIMENTS

In the following description, reference is made to the accompanying figures, which form part of the present disclosure, and which show, by way of illustration, specific aspects of examples of the present disclosure or specific aspects in which examples of the present disclosure may be used. It is understood that examples of the present disclosure may be used in other aspects and include structural or logical changes not depicted in the figures. The following detailed description, therefore, is not to be taken in a limiting sense, and the scope of the present disclosure is defined by the appended claims.

To assist in understanding the present disclosure, examples of wireless communication systems and devices are described below.

Example communication systems and devices

FIG. 1 is a simplified schematic illustration of a communication system according to one or more embodiments of the present disclosure. Referring to FIG. 1, as an illustrative example without limitation, a simplified schematic illustration of a communication system is provided. The communication system 100 includes a radio access network 120. The radio access network 120 may be a next generation (e.g. sixth generation (6G) or later) radio access network, or a legacy (e.g. 5G, 4G, 3G or 2G) radio access network. One or more communication electronic devices (ED) 110a, 110b, 110c, 110d, 110e, 110f, 110g, 110h, 110i, 110j (generically referred to as 110) may be interconnected to one another or connected to one or more network nodes (170a, 170b, generically referred to as 170) in the radio access network 120. A core network 130 may be a part of the communication system and may be dependent or independent of the radio access technology used in the communication system 100. Also the communication system 100 includes a public switched telephone network (PSTN) 140, the internet 150, and other networks 160.

FIG. 2 is a schematic illustration of an example communication system according to one or more embodiments of the present disclosure. FIG. 2 illustrates an example communication system 100. In general, the communication system 100 enables multiple wireless or wired elements to communicate data and other content. The purpose of the communication system 100 may be to provide content, such as voice, data, video, and/or text, via broadcast, multicast, groupcast, unicast, etc. The communication system 100 may operate by sharing resources, such as carrier spectrum bandwidth, between its constituent elements. The communication system 100 may include a terrestrial communication system and/or a non-terrestrial communication system. The communication system 100 may provide a wide range of communication services and applications (such as earth monitoring, remote sensing, passive sensing and positioning, navigation and tracking, autonomous delivery and mobility, etc. ) . The communication system 100 may provide a high degree of availability and robustness through a joint operation of a terrestrial communication system and a non-terrestrial communication system. For example, integrating a non-terrestrial communication system (or components thereof) into a terrestrial communication system can result in what may be considered a heterogeneous network including multiple layers. Compared to conventional communication networks, the heterogeneous network may achieve better overall performance through efficient multi-link joint operation, more flexible functionality sharing, and faster physical layer link switching between terrestrial networks and non-terrestrial networks.

The terrestrial communication system and the non-terrestrial communication system could be considered sub-systems of the communication system. In the example shown in FIG. 2, the communication system 100 includes electronic devices (ED) 110a, 110b, 110c, 110d (generically referred to as ED 110) , radio access networks (RANs) 120a, 120b, a non-terrestrial communication network 120c, a core network 130, a public switched telephone network (PSTN) 140, the internet 150, and other networks 160. The RANs 120a, 120b include respective base stations (BSs) 170a, 170b, which may be generically referred to as terrestrial transmit and receive points (T-TRPs) 170a, 170b. The non-terrestrial communication network 120c includes an access node 172, which may be generically referred to as a non-terrestrial transmit and receive point (NT-TRP) 172.

Any ED 110 may be alternatively or additionally configured to interface, access, or communicate with any T-TRP 170a, 170b and NT-TRP 172, the internet 150, the core network 130, the PSTN 140, the other networks 160, or any combination of the preceding. In some examples, ED 110a may communicate an uplink and/or downlink transmission over a terrestrial air interface 190a with T-TRP 170a. In some examples, the EDs 110a, 110b, 110c, and 110d may also communicate directly with one another via one or more sidelink air interfaces 190b. In some examples, ED 110d may communicate an uplink and/or downlink transmission over a non-terrestrial air interface 190c with NT-TRP 172.

The air interfaces 190a and 190b may use similar communication technology, such as any suitable radio access technology. For example, the communication system 100 may implement one or more channel access methods, such as code division multiple access (CDMA) , space division multiple access (SDMA) , time division multiple access (TDMA) , frequency division multiple access (FDMA) , orthogonal FDMA (OFDMA) , or single-carrier FDMA (SC-FDMA, also known as discrete Fourier transform spread OFDMA, DFT-s-OFDMA) in the air interfaces 190a and 190b. The air interfaces 190a and 190b may utilize other higher dimension signal spaces, which may involve a combination of orthogonal and/or non-orthogonal dimensions.

The non-terrestrial air interface 190c can enable communication between the ED 110d and one or multiple NT-TRPs 172 via a wireless link or simply a link. For some examples, the link is a dedicated connection for unicast transmission, a connection for broadcast transmission, or a connection between a group of EDs 110 and one or multiple NT-TRPs 172 for multicast transmission.

The RANs 120a and 120b are in communication with the core network 130 to provide the EDs 110a 110b, and 110c with various services such as voice, data, and other services. The RANs 120a and 120b and/or the core network 130 may be in direct or indirect communication with one or more other RANs (not shown) , which may or may not be directly served by core network 130, and may or may not employ the same radio access technology as RAN 120a, RAN 120b or both. The core network 130 may also serve as a gateway access between (i) the RANs 120a and 120b or EDs 110a 110b, and 110c or both, and (ii) other networks (such as the PSTN 140, the internet 150, and the other networks 160) . In addition, some or all of the EDs 110a 110b, and 110c may include functionality for communicating with different wireless networks over different wireless links using different wireless technologies and/or protocols. Instead of wireless communication (or in addition thereto) , the EDs 110a 110b, and 110c may communicate via wired communication channels to a service provider or switch (not shown) , and to the internet 150. PSTN 140 may include circuit switched telephone networks for providing plain old telephone service (POTS) . Internet 150 may include a network of computers and subnets (intranets) or both, and incorporate protocols, such as internet protocol (IP) , transmission control protocol (TCP) , user datagram protocol (UDP) . EDs 110a 110b, and 110c may be multimode devices capable of operation according to multiple radio access technologies, and incorporate multiple transceivers necessary to support such.

Basic component structure

FIG. 3 is a schematic illustration of a basic component structure of a communication system according to one or more embodiments of the present disclosure. FIG. 3 illustrates another example of an ED 110 and a base station 170a, 170b and/or 170c. The ED 110 is used to connect persons, objects, machines, etc. The ED 110 may be widely used in various scenarios including, for example, cellular communications, device-to-device (D2D) , vehicle to everything (V2X) , peer-to-peer (P2P) , machine-to-machine (M2M) , machine-type communications (MTC) , internet of things (IoT) , virtual reality (VR) , augmented reality (AR) , mixed reality (MR) , metaverse, digital twin, industrial control, self-driving, remote medical, smart grid, smart furniture, smart office, smart wearable, smart transportation, smart city, drones, robots, remote sensing, passive sensing, positioning, navigation and tracking, autonomous delivery and mobility, etc.

Each ED 110 represents any suitable end user device for wireless operation and may include such devices (or may be referred to) as a user equipment/device (UE) , a wireless transmit/receive unit (WTRU) , a mobile station, a fixed or mobile subscriber unit, a cellular telephone, a station (STA) , a machine type communication (MTC) device, a personal digital assistant (PDA) , a smartphone, a laptop, a computer, a tablet, a wireless sensor, a consumer electronics device, a smart book, a vehicle, a car, a truck, a bus, a train, or an IoT device, wearable devices (such as a watch, a pair of glasses, head mounted equipment, etc. ) , an industrial device, or an apparatus in (e.g. communication module, modem, or chip) or including the forgoing devices, among other possibilities. Future generation EDs 110 may be referred to using other terms. The base station 170a and 170b is a T-TRP and will hereinafter be referred to as T-TRP 170. Also shown in FIG. 3, a NT-TRP will hereinafter be referred to as NT-TRP 172. Each ED 110 connected to T-TRP 170 and/or NT-TRP 172 can be dynamically or semi-statically turned-on (i.e., established, activated, or enabled) , turned-off (i.e., released, deactivated, or disabled) and/or configured in response to one of more of: connection availability and connection necessity.

The ED 110 includes a transmitter 201 and a receiver 203 coupled to one or more antennas 204. Only one antenna 204 is illustrated to avoid congestion in the drawing. One, some, or all of the antennas 204 may alternatively be panels. The transmitter 201 and the receiver 203 may be integrated, e.g. as a transceiver. The transceiver is configured to modulate data or other content for transmission by at least one antenna 204 or network interface controller (NIC) . The transceiver is also configured to demodulate data or other content received by the at least one antenna 204. Each transceiver includes any suitable structure for generating signals for wireless or wired transmission and/or processing signals received wirelessly or by wire. Each antenna 204 includes any suitable structure for transmitting and/or receiving wireless or wired signals.

The ED 110 includes at least one memory 208. The memory 208 stores instructions and data used, generated, or collected by the ED 110. For example, the memory 208 could store software instructions or modules configured to implement some or all of the functionality and/or embodiments described herein and that are executed by one or more processing unit (s) (e.g., a processor 210) . Each memory 208 includes any suitable volatile and/or non-volatile storage and retrieval device (s) . Any suitable type of memory may be used, such as random access memory (RAM) , read only memory (ROM) , hard disk, optical disc, subscriber identity module (SIM) card, memory stick, secure digital (SD) memory card, on-processor cache, and the like.

The ED 110 may further include one or more input/output devices (not shown) or interfaces (such as a wired interface to the internet 150 in FIG. 1) . The input/output devices or interfaces permit interaction with a user or other devices in the network. Each input/output device or interface includes any suitable structure for providing information to or receiving information from a user, and/or for network interface communications. Suitable structures include, for example, a speaker, microphone, keypad, keyboard, display, touch screen, etc.

The ED 110 includes the processor 210 for performing operations including those operations related to preparing a transmission for uplink transmission to the NT-TRP 172 and/or the T-TRP 170; those operations related to processing downlink transmissions received from the NT-TRP 172 and/or the T-TRP 170; and those operations related to processing sidelink transmission to and from another ED 110. Processing operations related to preparing a transmission for uplink transmission may include operations such as encoding, modulating, transmit beamforming, and generating symbols for transmission. Processing operations related to processing downlink transmissions may include operations such as receive beamforming, demodulating and decoding received symbols. Depending upon the embodiment, a downlink transmission may be received by the receiver 203, possibly using receive beamforming, and the processor 210 may extract signaling from the downlink transmission (e.g. by detecting and/or decoding the signaling) . An example of signaling may be a reference signal transmitted by the NT-TRP 172 and/or by the T-TRP 170. In some embodiments, the processor 210 implements the transmit beamforming and/or the receive beamforming based on the indication of beam direction, e.g. beam angle information (BAI) , received from the T-TRP 170. In some embodiments, the processor 210 may perform operations relating to network access (e.g. initial access) and/or downlink synchronization, such as operations relating to detecting a synchronization sequence, decoding and obtaining the system information, etc. In some embodiments, the processor 210 may perform channel estimation, e.g. using a reference signal received from the NT-TRP 172 and/or from the T-TRP 170.

Although not illustrated, the processor 210 may form part of the transmitter 201 and/or part of the receiver 203. Although not illustrated, the memory 208 may form part of the processor 210.

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

The T-TRP 170 may be known by other names in some implementations, such as a base station, a base transceiver station (BTS) , a radio base station, a network node, a network device, a device on the network side, a transmit/receive node, a Node B, an evolved NodeB (eNodeB or eNB) , a Home eNodeB, a next Generation NodeB (gNB) , a transmission point (TP) , a site controller, an access point (AP) , a wireless router, a relay station, a terrestrial node, a terrestrial network device, a terrestrial base station, a base band unit (BBU) , a remote radio unit (RRU) , an active antenna unit (AAU) , a remote radio head (RRH) , a central unit (CU) , a distributed unit (DU) , a positioning node, among other possibilities. The T-TRP 170 may be a macro BS, a pico BS, a relay node, a donor node, or the like, or combinations thereof. The T-TRP 170 may refer to the forgoing devices or refer to apparatus (e.g. a communication module, a modem, or a chip) in the forgoing devices.

In some embodiments, the parts of the T-TRP 170 may be distributed. For example, some of the modules of the T-TRP 170 may be located remote from the equipment that houses the antennas 256 for the T-TRP 170, and may be coupled to the equipment that houses the antennas 256 over a communication link (not shown) sometimes known as front haul, such as common public radio interface (CPRI) . Therefore, in some embodiments, the term T-TRP 170 may also refer to modules on the network side that perform processing operations, such as determining the location of the ED 110, resource allocation (scheduling) , message generation, and encoding/decoding, and that are not necessarily part of the equipment that houses the antennas 256 of the T-TRP 170. The modules may also be coupled to other T-TRPs. In some embodiments, the T-TRP 170 may actually be a plurality of T-TRPs that are operating together to serve the ED 110, e.g. through the use of coordinated multipoint transmissions.

The T-TRP 170 includes at least one transmitter 252 and at least one receiver 254 coupled to one or more antennas 256. Only one antenna 256 is illustrated to avoid congestion in the drawing. One, some, or all of the antennas 256 may alternatively be panels. The transmitter 252 and the receiver 254 may be integrated as a transceiver. The T-TRP 170 further includes a processor 260 for performing operations including those related to: preparing a transmission for downlink transmission to the ED 110, processing an uplink transmission received from the ED 110, preparing a transmission for backhaul transmission to the NT-TRP 172, and processing a transmission received over backhaul from the NT-TRP 172. Processing operations related to preparing a transmission for downlink or backhaul transmission may include operations such as encoding, modulating, precoding (e.g. multiple input multiple output (MIMO) precoding) , transmit beamforming, and generating symbols for transmission. Processing operations related to processing received transmissions in the uplink or over backhaul may include operations such as receive beamforming, demodulating received symbols, and decoding received symbols. The processor 260 may also perform operations relating to network access (e.g. initial access) and/or downlink synchronization, such as generating the content of synchronization signal blocks (SSBs) , generating the system information, etc. In some embodiments, the processor 260 also generates an indication of beam direction, e.g. BAI, which may be scheduled for transmission by a scheduler 253. The processor 260 performs other network-side processing operations described herein, such as determining the location of the ED 110, determining where to deploy the NT-TRP 172, etc. In some embodiments, the processor 260 may generate signaling, e.g. to configure one or more parameters of the ED 110 and/or one or more parameters of the NT-TRP 172. Any signaling generated by the processor 260 is sent by the transmitter 252. Note that “signaling” , as used herein, may alternatively be called control signaling. Signaling may be transmitted in a physical layer control channel, e.g. a physical downlink control channel (PDCCH) , in which case the signaling may be known as dynamic signaling. Signaling transmitted in a downlink physical layer control channel may be known as Downlink Control Information (DCI) . Signaling transmitted in an uplink physical layer control channel may be known as Uplink Control Information (UCI) . Signaling transmitted in a sidelink physical layer control channel may be known as Sidelink Control Information (SCI) . Signaling may be included in a higher-layer (e.g., higher than physical layer) packet transmitted in a physical layer data channel, e.g. in a physical downlink shared channel (PDSCH) , in which case the signaling may be known as higher-layer signaling, static signaling, or semi-static signaling. Higher-layer signaling may also refer to Radio Resource Control (RRC) protocol signaling or Media Access Control –Control Element (MAC-CE) signaling.

The scheduler 253 may be coupled to the processor 260. The scheduler 253 may be included within or operated separately from the T-TRP 170. The scheduler 253 may schedule uplink, downlink, sidelink, and/or backhaul transmissions, including issuing scheduling grants and/or configuring scheduling-free (e.g., “configured grant” ) resources. The T-TRP 170 further includes a memory 258 for storing information and data. The memory 258 stores instructions and data used, generated, or collected by the T-TRP 170. For example, the memory 258 could store software instructions or modules configured to implement some or all of the functionality and/or embodiments described herein and that are executed by the processor 260.

Although not illustrated, the processor 260 may form part of the transmitter 252 and/or part of the receiver 254. Also, although not illustrated, the processor 260 may implement the scheduler 253. Although not illustrated, the memory 258 may form part of the processor 260.

The processor 260, the scheduler 253, the processing components of the transmitter 252, and the processing components of the receiver 254 may each be implemented by the same or different one or more processors that are configured to execute instructions stored in a memory, e.g. in the memory 258. Alternatively, some or all of the processor 260, the scheduler 253, the processing components of the transmitter 252, and the processing components of the receiver 254 may be implemented using dedicated circuitry, such as a programmed FPGA, a hardware accelerator (e.g., a GPU or AI accelerator) , or an ASIC.

Although the NT-TRP 172 is illustrated as a drone only as an example, the NT-TRP 172 may be implemented in any suitable non-terrestrial form, it should be noted that the NT-TRP 172 may be removed in some cases. Also, the NT-TRP 172 may be known by other names in some implementations, such as satellites and high altitude platforms, including international mobile telecommunication base stations and unmanned aerial vehicles, for example. Also, the NT-TRP 172 may be known by other names in some implementations, such as a non-terrestrial node, a non-terrestrial network device, or a non-terrestrial base station. The NT-TRP 172 includes a transmitter 272 and a receiver 274 coupled to one or more antennas 280. Only one antenna 280 is illustrated to avoid congestion in the drawing. One, some, or all of the antennas may alternatively be panels. The transmitter 272 and the receiver 274 may be integrated as a transceiver. The NT-TRP 172 further includes a processor 276 for performing operations including those related to: preparing a transmission for downlink transmission to the ED 110, processing an uplink transmission received from the ED 110, preparing a transmission for backhaul transmission to T-TRP 170, and processing a transmission received over backhaul from the T-TRP 170. Processing operations related to preparing a transmission for downlink or backhaul transmission may include operations such as encoding, modulating, precoding (e.g. MIMO precoding) , transmit beamforming, and generating symbols for transmission. Processing operations related to processing received transmissions in the uplink or over backhaul may include operations such as receive beamforming, demodulating received symbols, and decoding received symbols. In some embodiments, the processor 276 implements the transmit beamforming and/or receive beamforming based on beam direction information (e.g. BAI) received from the T-TRP 170. In some embodiments, the processor 276 may generate signaling, e.g. to configure one or more parameters of the ED 110. In some embodiments, the NT-TRP 172 implements physical layer processing, but does not implement higher layer functions such as functions at the medium access control (MAC) or radio link control (RLC) layer. As this is only an example, more generally, the NT-TRP 172 may implement higher layer functions in addition to physical layer processing.

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

The processor 276, the processing components of the transmitter 272, and the processing components of the receiver 274 may each be implemented by the same or different one or more processors that are configured to execute instructions stored in a memory, e.g. in the memory 278. Alternatively, some or all of the processor 276, the processing components of the transmitter 272, and the processing components of the receiver 274 may be implemented using dedicated circuitry, such as a programmed FPGA, a hardware accelerator (e.g., a GPU or AI accelerator) , or an ASIC. In some embodiments, the NT-TRP 172 may actually be a plurality of NT-TRPs that are operating together to serve the ED 110, e.g. through coordinated multipoint transmissions.

The T-TRP 170, the NT-TRP 172, and/or the ED 110 may include other components, but these have been omitted for the sake of clarity.

Basic module structure

One or more steps of the embodiment methods provided herein may be performed by corresponding units or modules, FIG. 4 illustrates a block diagram of a device in a communication system according to one or more embodiments of the present disclosure. FIG. 4 illustrates units or modules in a device, such as in the ED 110, in the T-TRP 170, or in the NT-TRP 172. For example, a signal may be transmitted by a transmitting unit or by a transmitting module. A signal may be received by a receiving unit or by a receiving module. A signal may be processed by a processing unit or a processing module. Other steps may be performed by an artificial intelligence (AI) or machine learning (ML) module, which can be chosen or removed according to actual requirements. The respective units or modules may be implemented using hardware, one or more components or devices that execute software, or a combination thereof. For instance, one or more of the units or modules may be a circuit such as an integrated circuit. Examples of an integrated circuit includes a programmed FPGA, a GPU, or an ASIC. For instance, one or more of the units or modules may be logical such as a logical function performed by a circuit, by a portion of an integrated circuit, or by software instructions executed by a processor. It will be appreciated that where the modules are implemented using software for execution by a processor for example, the modules may be retrieved by a processor, in whole or part as needed, individually or together for processing, in single or multiple instances, and that the modules themselves may include instructions for further deployment and instantiation. It should be noted that, the modules shown in FIG. 4 are only illustrative and should not be construed as limitations to the embodiments of the present disclosure, more or less modules may be included in the device, which is not limited here. For example, the transmitting module and the receiving module may be replaced with one transceiving module. For another example, the ML module can be included or excluded from the device, depending on actual needs.

Additional details regarding the EDs 110, the T-TRP 170, and the NT-TRP 172 are known to those of skill in the art. As such, these details are omitted here.

The solution described in the present disclosure may be applicable to a next generation (e.g. sixth generation (6G) or later) network, or a legacy (e.g. 5G, 4G, 3G or 2G) network.

The proposed 6G System architecture is defined to support 6G XaaS services by using techniques such as Network Function Virtualization and Network Slicing. The 6G System architecture utilizes service-based interactions between 6G services.

The 6G System leverages service-based architecture and XaaS concept. XaaS services in the 6G System are categorized into three layers. FIG. 5 illustrates a block diagram of 6G System conceptual structure according to one or more embodiments of the present disclosure. The 6G System conceptual structure is shown in FIG. 5.

Infrastructure Layer includes infrastructures supporting 6G services. Among them are wireless networks (RAN, CN) infrastructures, Cloud/data center infrastructures, satellite networks, storage/database infrastructures, and sensing networks, and etc. These infrastructures can be provided by a single provider or by multiple providers.

Each of the infrastructures could have its control and management functions, denoted as C/M functions, for infrastructure management. Each of these infrastructures is one type of Infrastructure as a Service.

Control and Management (C/M) layer includes control and management services of the 6G System. They are developed and deployed by using slicing techniques and utilizing resource provided by infrastructure layer. 6G services in Control and Management (C/M) layer are:

- Resource Management (RM) as a Service provides a capability of life-cycle management of a variety of slices and over-the-air resource assignment to wireless devices.

- Mission Management (MM) as a Service provides a capability to program provisioning of XaaS services at Service Layer to provide mission services.

- Confederation Network (CONET) as a Service provides a capability to enable multiple partners jointly provide 6G services. This capability is provided by confederation formation, mutual authentication, mutual authorization among partners and negotiation of agreement on recording and retracing of selected actions performed by partners, in order to assure a trustworthy environment of 6G System operations.

- Service Provisioning Management (SPM) as a Service provides a capability of control and management of 6G service access by customers and provisioning of requested services. The capability is provided by unified mutual authentication, authorization and policy, key management, QoS assurance and charging between any pair of XaaS service provider and customer. The customers include end-customers not only in physical world, but also digital representatives in digital world.

- Connectivity Management (CM) as a Service leverages 5G connectivity management functions, but with extension to include digital world.

- Protocol as a Service provides a capability to design service customized protocol stacks for identified interfaces. The protocol stacks could be pre-defined for on-demand selection, or could be on-demand designed.

- Network Security as a Service provides a capability for owners of infrastructures to detect potential security risks of their infrastructures.

A 6G mission is defined as a service provided to customers by the 6G System. A mission can be a type of services which is provided by a single 6G XaaS service or a type of services that needs contributions from multiple XaaS services.

XaaS services in C/M Layer support control and management of the 6G System itself and also provide support to verticals if requested. One example is that RM service can serve RAN for over-the-air resource management and can also provide service to a vertical for the vertical’s over-the-air resource allocation to its end-customers. The XaaS in C/M layer can be deployed by using slicing technique.

Service Layer includes 6G services which provide services to customers. In the 6G System conceptual structure:

- AI service may be denoted as NET4AI as a Service. Artificial Intelligence service provides AI capability to support a variety of AI applications.

- Service of data collection, data sanitization, data analysis and data delivery are denoted as DAM as a Service, this service provides a capability of lifecycle management of statistic data, including acquisition, de-privatization, analysis and delivery of data which are information statistic data from any types of sensors, devices, network functions, and etc.

- Service of storage and sharing of data may be denoted as NET4Data as a Service, this service provides a capability to trustworthily storage and share data under the control of owners of data and following recognized authorities’ regulations on control of identified data.

- Service to provide digital world may be denoted as NET4DW as a Service, Digital World service provides a capability to construct, control and manage digital world. Digital world is defined as digital realization of physical world.

- 6G block chain service may be denoted as NET4BC as a Service. 6G connectivity service is denoted as NET4Con as a Service. This service provides a capability to support 6G block chain services.

- Enhanced connectivity service, e.g., network for connectivity (NET4CON) as a service. This service provides a capability to support exchange of messages and data among new 6G services.

All XaaS services at this Layer are developed and deployed by using resource provided in infrastructure and utilizing Network Function Virtualization and Slicing techniques. The capability of each of 6G services is provided by its control and management functions and service specific data process functions.

In addition to support 6G XaaS services at Service Layer, 6G System leverages 5G System for provisioning of vertical services. The difference between 6G XaaS services and other verticals are that a vertical is a pure customer which needs other XaaS services to enable its operation, while each of XaaS services provide their capabilities to 6G customers.

Any pair of XaaS services of the 6G System could also be mutual customer and provider of each other. Some of examples are that an infrastructure owner provides its resource to XaaS services in Service Layer and C/M Layer; RM services may need the capabilities provided by NET4AI, DAM and NET4DW for its resource management for vertical slicing; CONET service and NET4Data service may need the capability provided by NET4BC for their operation.

The key concepts of 6G System includes:

- Define Basic XaaS Services by decoupling comprehensive types of services into basic XaaS services. A basic XaaS service provides unique capability to enable a specific type of service, such as NET4AI service, NET4DW service, DAM service, NET4Data service, Block chain service, mission management service, etc.

- Allow joint operation of the 6G System by multiple partners.

- Define Data Plane of the 6G System which includes processing functions of data plane of XaaS services. Programing the interconnection of these functions, by mission management service, enables to support a variety of customized customer services.

- Simplify 6G System architecture by categorizing basic control services and management services and combining them as basic XaaS services in Control and Management (C/M) Layer.

- Define C/M Plane of the 6G System which includes C/M functions in XaaS services and may include 5G CP (e.g., AMF) depending on implementation options.

- Define Basic Architecture Structure (BAS) which is a unified basic structure with minimized number of interfaces and is independent of types of infrastructures.

- Simplify standardization, development and deployment of the 6G System using the BAS concept, while supporting a variety of infrastructure deployment scenarios.

- Adapt to a variety of deployment scenarios by applying the BAS or a subset of it to infrastructures based on capability, capacity and requirement of the infrastructure networks.

- Leverage service-based interface (SBI) concept and apply SBI interaction in both 6G C/M plane and 6G data plane.

- Simplify SBI interfaces by introducing trustworthy GWs in Data Plane and C/M Plane of the 6G System.

- Improve trustworthiness from perspectives of operation of the 6G System by introducing CONET capability, NET4BC capability and anonymous service provisioning provided by the trustworthy GWs in the C/M plane and data plane of the 6G System.

- Improve trustworthiness from perspective of end customer privacy protection by unified mutual authentication, IDM, data sanitization and etc. provided by SPM service, DAM service and 6G Block Chain service.

- Simplify roaming management of wireless devices, in physical world and digital world, by unified authentication including all participated partners and customers.

- Support multiple development paths from 5G System to 6G System by defining multiple architecture options without incurring much efforts due to the introduction of the BAS concept.

- Support backward compatibility by utilizing benefits of SBA and its add-on feature. 5G users can use the 6G System to access 5G services.

- Support future extension by adding new XaaS services with minimized impact on standardization and deployment, due to the introduced anonymous service provisioning concept implemented in trustworthy GWs in 6G C/M plane and in 6G data plane.

Many new trends will trigger the consideration and design of 6G/future wireless networks:

- New network infrastructure capability, e.g., cloud natured/friendly infrastructures that are broadly deployed.

- New (relative) matured techniques, e.g., AI large scale models, Data de-privacy, Block chain, etc. that have made significant progresses and significantly impact on the entire society and human life.

- New apps and services, e.g., AI services, Data (sensing) service, Digital world service, etc. that are broadly applied in industry/business and used by individual customers.

- More global/open/collaborative operation trend, i.e., a more open and more collaborative operation mode are becoming common practice in many fields.

New expectation and stricter requirements on future networks also drive rethinking and development of new generation of wireless networks. These requirements include:

- Privacy and trustworthiness, etc.

- Simplified standardization.

- Rapid deployment.

- Etc.

All of the above drives 6G network architecture research work.

The proposed 6G network architecture (X-centric) are SBA (XaaS service) based and Cloud-native.

Requirements to 6G System network architecture design:

- The proposed 6G network architecture needs to support new 6G services which could be developed/deployed by 3rd parties.

- The proposed 6G network architecture needs to embrace more open ecosystem to open door to technical capable 3rd parties.

- The proposed 6G network architecture needs to enable better trustworthiness management.

In the related art, a PDU connectivity service is provided by 5G network. The PDU connectivity service is a service that provides exchange of PDUs between a UE and a Data Network (DN) . 5G network provides the PDU connectivity service to a UE via one or more PDU sessions. FIG. 6 is a schematic illustration of 5G PDU session according to one or more embodiments of the present disclosure. As shown in FIG. 6, for a PDU session, it is an association between the UE and a Data Network (DN) that provides a PDU connectivity service. There are intermediate network nodes (e.g., RAN node gNB, UPF) in the PDU session between the UE and the DN. One or more QoS flows may be transmitted via a PDU session. The QoS flow is the finest granularity of QoS differentiation in a PDU session. User plane traffic within a QoS flow of a PDU session receives the same traffic forwarding treatment (e.g. scheduling, admission threshold, delay, loss rate) .

On the network side, user plane tunnels (e.g., GPRS tunnelling protocol for user plane (GTP-U) tunnel) are established to deliver data of a PDU session. For example, there are a NG-U tunnel (e.g., N3 tunnel) between a RAN and a UPF, a tunnel (e.g., N9 tunnel) between two UPFs, and a tunnel (e.g., N6 tunnel) between a UPF and a DN, etc. The data of a PDU session is delivered via the tunnels on network side.

Over the air, a data radio bearer is established between UE and RAN. The data radio bearer transports a packet of a PDU session over the air. There is a one-to-multiple mapping between the PDU session and the data radio bearer. The data of a PDU session is mapped to one or more data radio bearers by RAN. For example, one QoS flow of a PDU session is mapped to one data radio bearer, and different QoS flows of the PDU session can be mapped to the same or different data radio bearers.

To establish a PDU session for data forwarding, the 5G control plane functions (e.g., access and mobility management function (AMF) , session management function (SMF) , RAN control plane (CP) ) configures the user plane functions (e.g., UPF, RAN user plane (UP) ) to establish the resources for the PDU session, e.g., to establish the tunnels (e.g., GTP-U tunnel) on the network side and data radio bearers over the air. For example, GTP-U tunnel (e.g., for N3 tunnel, N9 tunnel) is established per PDU session, and a GTP-U tunnel is dedicated to a PDU session. One or multiple data radio bearers are established over the air for a PDU session. Packet detection rule and forwarding action rule are configured to user plane function when the PDU session resource is setup under the control of control plane function. For example, the mapping between GTP-U tunnel and PDU session is configured to user plane function to enable data forwarding.

The QoS flow is the finest granularity of QoS differentiation in the PDU session. A QoS flow ID (QFI) is used to identify a QoS flow in the 5G System. User Plane traffic with the same QFI within a PDU Session receives the same traffic forwarding treatment (e.g. scheduling, admission threshold) . The QFI is carried in an encapsulation header on N3 (and N9) i.e. without any changes to the end to end packet header. QFI shall be used for all PDU Session Types. The QFI shall be unique within a PDU Session. The QFI may be dynamically assigned or may be equal to the 5G QoS identifier (5QI) . A QoS Flow is associated with QoS requirements as specified by QoS parameters and QoS characteristics.

User plane functions (e.g., UPF, RAN UP) performs suitable actions to deliver uplink and/or downlink data. For example, UPF classifies PDU layer packets for QoS flow marking (e.g., based on packet detection rule) and maps the QoS flows to GTP-U tunnels. And other user plane function (e.g., UPF, RAN) decides the QoS flow to which a received packet belongs based on the QoS flow identifier marked in the packet header, and decides the PDU session to which a received packet belongs, based on the tunnel via which the packet is delivered. RAN maps QoS flows of a PDU session received in a specific GTP-U tunnel to data radio bearers.

FIG. 7 is a schematic illustration of a 5G user plane protocol stack between UE and gNB according to one or more embodiments of the present disclosure, 5G user plane protocol stack between UE and gNB is depicted in FIG. 7. A data radio bearer (DRB) is configured with service data adaptation protocol (SDAP) sublayer, packet data convergence protocol (PDCP) sublayer, radio link control (RLC) sublayer, medium access control (MAC) sublayer and physical layer (PHY) .

The SDAP sublayer supports the functions such as:

- mapping between a QoS flow and a DRB for both DL and UL;

- marking QoS flow ID in both DL and UL packets;

- reflective QoS flow to DRB mapping for the UL SDAP data PDUs.

FIG. 8 is a schematic illustration of a structure view of a SDAP sublayer according to one or more embodiments of the present disclosure, the structure view of SDAP sublayer is depicted in FIG. 8. One PDU session is configured with one SDAP entity. One DRB is configured with one PDCP entity. The data of a PDU session including one or more QoS flows is mapped to one or more DRB (s) by the SDAP sublayer. A SDAP entity receives SDAP SDUs from upper layers and submits SDAP PDUs to its peer SDAP entity via lower layers. A SDAP entity receives SDAP PDUs from its peer SDAP entity via lower layers and delivers SDAP SDUs to upper layers.

FIG. 9 is a schematic illustration of a downlink (DL) SDAP data PDU format with a SDAP header according to one or more embodiments of the present disclosure, the DL SDAP data PDU format with the SDAP header is depicted in FIG. 9. The QFI field indicates the ID of the QoS flow to which the SDAP PDU belongs. The reflective QoS indication (RQI) indicates whether NAS should be informed of the updated of service data flow (SDF) to QoS flow mapping rules. The reflective QoS flow to DRB mapping indication (RDI) indicates whether QoS flow to DRB mapping rule should be updated. The data field includes the SDAP SDU.

FIG. 10 is a schematic illustration of an uplink (UL) SDAP data PDU format with a SDAP header according to one or more embodiments of the present disclosure, the UL SDAP data PDU format with the SDAP header is depicted in FIG. 10. The D/C bit indicates whether the SDAP PDU is an SDAP Data PDU or an SDAP Control PDU.

There are other SDAP data PDU formats, e.g., sidelink SDAP data PDU format, End-Marker Control PDU of SDAP, etc. More details on SDAP sublayer can be found in 3rd generation partnership project (3GPP) technical specification (TS) 37.324, which are omitted here.

User plane functions (e.g., UPF, RAN UP) performs suitable actions to deliver uplink and/or downlink data. For example, UPF classifies PDU layer packets for QoS flow marking (e.g., based on packet detection rule) and maps the QoS flows to GTP-U tunnels. And other user plane function (e.g., UPF, RAN) decides the QoS flow a received packet belongs to, based on the QoS flow identifier marked in the packet header, and decides the PDU session that a received packet belongs to, based on the tunnel via which the packet is delivered. RAN (i.e., SDAP) maps QoS flows of a PDU session received in a specific GTP-U tunnel to data radio bearers.

As described in 3GPP TS 37.324, the SDAP entities are located in the SDAP sublayer. Several SDAP entities may be defined for a UE. There is an SDAP entity configured for each individual PDU session for NR Uu. SDAP entity is per PDU session.

FIG. 11 is a schematic illustration of SDAP configuration information when a DRB is established according to one or more embodiments of the present disclosure, as shown in FIG. 11 from 3GPP TS 38.331, an SDAP entity is configured when a DRB is established or updated. FIG. 12 is a schematic illustration of a SDAP configuration information element when an SDAP entity is established per PDU session according to one or more embodiments of the present disclosure, the detailed SDAP configuration information elements (IEs) are depicted in FIG. 12.

As shown in FIG. 12, an SDAP entity is established per PDU session identified by a PDU session ID, and one or multiple QoS flows of the PDU session are mapped by the SDAP entity to the DRB. The one or multiple QoS flows are identified by QFIs (corresponding to IE mappedQoS-FlowsToAdd) .

The configuration information in FIG. 11 and FIG. 12 are transferred over the air, e.g., between a RAN node and UE via an RRC message. More details on the SDAP configuration can be found in 3GPP documents, e.g., TS 38.331, TS 37.324, which are omitted here.

However, for a next generation (e.g. sixth generation (6G) or later) network, or a legacy (e.g. 5G, 4G, 3G or 2G) network in 6G era, the 6G network is expected to not only for connectivity, but also for data processing. Thus, in 6G era, in-network data processing (computing) is supported.

In order to achieve the above objectives, a mission service is designed for 6G network. A mission is to achieve a designated goal, known as mission goal, which includes (1) providing PDU connectivity and optionally (2) providing data processing. A mission service is a service that provides achieving of a mission goal (i.e., PDU connectivity and/or data processing) . When the mission goal includes providing data processing, the mission goal is associated with specific computational problem (s) , and providing data processing refers to solving the specific computational problem (s) . In this case, the mission includes one or multiple computing blocks (CBs) and is associated with a networking procedure among the CBs for solving the specific computational problem (s) . A CB within the mission corresponds to a defined computational step toward the mission goal (i.e. solving the specific computational problem (s) ) and may be executed by a function of XaaS service (in the form of a task) , by a data network (DN) , or by a function of another mission service; accordingly, the CB is referred to as a task CB, an external CB or a sub-mission CB. A CB corresponds to a particular action of data processing, e.g., AI training, AI inference, data pre-processing, data de-privatization, data cleaning, data collection, data analytics, sensing, etc. Different CBs of a mission may be executed in sequence or parallel.

When the mission goal only includes providing PDU connectivity, the mission service may be reduced to a 5G PDU connectivity service. When the mission goal includes providing data processing, data is forwarded to one or more CB entities and processed by the CB entities, then processed data is forwarded to a next-hop, such as, another one or more CB entities, until the mission goal is completed.

FIG. 13 is a schematic illustration of a mission service provided by a 6G network according to one or more embodiments of the present disclosure. As shown in FIG. 13, each of the CB entities executing one or more CBs. The CB entities can be deployed in a device (e.g., a UE, a vehicle, a radar, a sensor, a drone, and an actuator) , a RAN, a CN, and even in a DN. In some cases, the CB entities are deployed on functions of XaaS services. The functions of XaaS services may be in a device, a RAN, a CN and a DN. In some cases, the mission service including the CB entities is configurable and under the control of C/M plane functions, e.g., a mission management function (MM) . As in FIG. 13, devices deploying CB entities and other CB entities provided by functions of XaaS services are involved in a mission service to perform data processing in parallel and/or sequence. The functions of XaaS services can be in one or more of: RAN, CN and DN. For example, CB entities 1, 2, 3 and 4 are provided by functions of XaaS services 1, 2, 3 and 4, respectively, and the two devices may also provide other CB entities (not illustrated in the figure) or not. In some cases, the CB entities 1, 2, 3 and 4 may be provided by one or more functions of a same XaaS service instead of 4 different functions of XaaS services. In some cases, zero, one or more of the 4 CB entities are in the DN, and the other CB entities are in one or more of: RAN, and CN. The CB entities and devices are connected via data trustworthy gateway (Data-TW-GW) . In some cases, the CB entity, Data-TW-GW are deployed on 6G data plane, and the data plane may be also termed as user plane, or enhanced user plane, etc. In some cases, the Data-TW-GW could be UPF, or enhanced UPF. CB entities (e.g., deployed in device, RAN, CN, DN and third parties) are connected via Data-TW-GW. The Data-TW-GW is helpful to get rid of mesh topology among CBs and to support anonymous communication among CBs.

For the data processing (computing) procedure within the mission service:

the two devices may deliver data (non-processed or processed data by CB entities in the devices) to CB entity 1 being provided by a function of XaaS service 1 (e.g., Data Analytics and Management (DAM) service) ;

CB entity 1 delivers the data directly or deliver the data after processing to CB entity 2 being provided by a function of XaaS service 2 (e.g., NET4AI service) , via Data-TW-GW 1;

in parallel, CB entity 2 receives data from CB entity 4 being provided by a function of XaaS service 4 (e.g., NET4DW service) , via Data-TW-GW 1 and Data-TW-GW 2;

and the data received by CB entity 2 from CB entity 4 is the processed results of the data received by CB entity 4 from CB entity 3 being provided by a function of XaaS service 3 (e.g., NET4Data) , via Data-TW-GW 2;

then CB entity 2 performs data processing of AI training (or AI inference, etc. ) using all the received data from CB entities 1, 3 and 4, and sends the processed results to CB entity 4;

CB entity 4 perform data processing using the data sent by CB entity 2 and the data from CB entity 3, and sends the processed results to CB entity 2; and then, back and forth data processing and forwarding are performed among CB entities 2, 3 and 4 until the mission goal is completed.

In some case, a mission corresponds to a service function chain as defined by internet engineering task force (IETF) , e.g., in request for comments (RFC) 7665. A service function chain is defined as a logical representation of an ordered set (sequence) of service functions that need to successively handle some traffic, e.g. traffic is first handled by service function1 (e.g. Deep Packet Inspection) , then service function 2 (e.g. TCP/IP optimization) and lastly by service function 3 (e.g. firewall) .

FIG. 14 is a schematic illustration of a mission session for a mission service according to one or more embodiments of the present disclosure, as shown in FIG. 14, a mission service subscriber (e.g., a 6G device, an application server (AS) ) accesses a mission service via one or multiple mission sessions.

The mission session is to provide a mission service to a mission customer, and the mission service is a service for both packet data unit (PDU) connectivity and data processing. In some cases, the mission service subscriber may also be referred to as a mission customer, which requests to access to the mission service.

Specifically, the mission session is an association between a network entity (e.g. a UE, a network function (NF) , and an application server (AS) ) and a Data Network (DN) , providing a mission service. And the DN may be virtual and dummy DN. A mission session includes the data forwarding and data processing resources to execute a mission. A mission session includes a collection (group) of data sessions and optional inter-GW sessions.

The mission service is a service that provides achieving of a mission goal (i.e., PDU connectivity and/or data processing) . When the mission goal includes providing data processing, the mission goal is associated with specific computational problem (s) , and providing data processing refers to solving the specific computational problem (s) . In this case, the mission includes one or multiple computing blocks (CBs) and is associated with a networking procedure among the CBs for solving the specific computational problem (s) . A CB within the mission corresponds to a defined computational step toward the mission goal (i.e. solving the specific computational problem (s) ) . In some cases, a CB is executed by a function of a XaaS service (in the form of a task) , by a data network (DN) , or by a function of another mission service; accordingly, the CB is referred to as a task CB, an external CB or a sub-mission CB. A CB corresponds to a particular action of data processing, e.g., AI training, AI inference, data pre-processing, data de-privatization, data cleaning, data collection, data analytics, sensing, etc. Different CBs of a mission may be executed in sequence or parallel.

The mission session includes one or more data sessions, each data session includes an association terminates at a computing block (CB) entity executing at least one CB of a mission, the mission includes one or more CBs and each CB corresponds to a computational step toward achieving the mission service. The data processing includes the executing the at least one CB of the mission. The computational step toward achieving the mission service can also be referred to as the computational step toward the mission goal cited above.

The mission session includes one or more data sessions, the one or more data sessions are used to deliver data of the one or more CBs, and the establishing either or both of the PDU connectivity resource and the data processing resource for the mission session includes establishing at least one of the one or more data sessions, where each data session includes an association terminates at one CB entity, one CB entity participates in one or more data sessions, and one CB entity participates in one or more mission sessions. The PDU connectivity resource can also be called the data forwarding resource cited above.

Furthermore, the CB entity is for executing at least one CB of a mission, the mission includes one or more CBs and each CB corresponds to a computational step toward achieving the mission service; where the data processing includes the executing the at least one CB of the mission.

Among them, the computational step toward achieving the mission service includes one or more of: artificial intelligence (AI) training, AI inference, data pre-processing, data privacy protection, data cleaning, data collection, data analytics, sensing, data sanitization, data management, data normalization, data aggregation, data splitting, useless data filtering, data formatting, data adaptation, data feature engineering, data compression, data embedding, data representation learning, or data feature extraction.

Specifically, the data session is an association at least terminates at a computing block (CB) entity to execute one or more CBs of a mission. The CB entity is an entity to execute the actions corresponding to the one or more CBs. Particular data transmission and/or data processing are executed among the CB entities in specific order (e.g., in sequence and/or parallel) to complete the mission. The CB entity is a network entity which can be deployed in:a device (e.g., UE, a vehicle, a radar, a sensor, a drone, and an actuator) , a RAN, a CN, and a DN. In some cases, the CB entity is deployed on a function of a XaaS service. The function of the XaaS service can be in a device, a RAN, a CN and a DN. In some cases, the CB entity is an entity of a data plane. In some cases, the CB entity is deployed on 6G data plane. In some cases, the CB entity is supported by a XaaS service, e.g., by a processing service function (PSF) of the XaaS service. Different CB entities may execute the same or different CBs. In some cases, a data session corresponds to one CB of a mission. In some cases, a data session corresponds to multiple CBs of a mission. In some cases, the CB entity may also be named as a CB DP entity.

In some cases, the data session may be regarded as only including the data forwarding resource for supporting the executing of one or more CBs of a mission, i.e., a pipe to connect a CB entity with another network entity, and the data processing resources configured in the CB entity do not belong to the data session.

In some cases, the data session may be regarded as including both of the data forwarding and data processing resources to execute one or more CBs of a mission, i.e., the data processing resources configured in the CB entity also belongs to the data session.

In some cases, a data session is an association between a CB entity and a Data-TW-GW.

In some cases, a data session is an association between a CB entity and another CB entity.

In some cases, for implementation, a data session is an association between a device (e.g., UE, a vehicle, a radar, a sensor, a drone, and an actuator) deployed with a CB entity and a Data-TW-GW. The Data-TW-GW may be deployed in a RAN or a CN.

In some cases, for implementation, a data session is an association between a Data-TW-GW and a processing service function (PSF) of a XaaS service, and a CB entity is deployed on the PSF. The Data-TW-GW may be deployed in a RAN or a CN. The PSF may be deployed in a RAN or a CN.

In some cases, for implementation, a data session is an association between a device and a PSF of a XaaS service. The PSF may be deployed in a RAN or a CN.

In some cases, for implementation, a data session is an association between a PSF and another PSF, and the two PSFs may be functions of a same or different XaaS services. Both or either of the two PSFs may be deployed in a RAN or a CN.

In some cases, for implementation, a data session is an association between a DN and a PSF of a XaaS service. The PSF may be deployed in a RAN or a CN.

In some cases, for implementation, a data session is an association between a DN and a Data-TW-GW. The Data-TW-GW may be deployed in a RAN or a CN.

In some cases, for implementation, a data session is an association between two devices.

In some cases, for implementation, a data session is an association between two DNs.

In some cases, for implementation, a data session is an association between a device and a DN.

The mission session further includes one or more inter-gateway (GW) sessions, each inter-GW session includes an association between two GW entities, and each GW entity is used for supporting communication among CB entities.

Specifically, the inter-GW session is an association between two Data-TW-GWs for data forwarding. In some cases, the Data-TW-GW could be UPF, or enhanced UPF. CB entities (e.g., deployed in device, RAN, CN and DN) are connected via Data-TW-GW. The Data-TW-GW is helpful to get rid of mesh topology among CBs and to support anonymous communication among CBs.

A CB entity (deployed in a device, a RAN, a CN or a DN) may participate into one or multiple mission sessions. A CB entity may participate into one or multiple data sessions.

A mission session can be identified by a mission session ID or a session group ID. A data session can be identified by a data session ID.

Referring to FIG. 14, a mission session includes one or multiple data sessions. There are two CB entities deployed in the RAN, two CB entities deployed in core network functions (NFs) or DN. Devices may also deploy CB entities or be active as CB entities not illustrated in the figure. The CB entity may be supported by a function of a XaaS service. Over the air, radio bearer is established between a device and a 6G RAN node. The data session is established between a device deploying a CB entity and a Data-TW-GW. Each device establishes one or multiple data sessions belongs to a mission session. One or multiple devices are involved in a mission session. Flexible mapping are enabled between a radio bearer and a data session. On network side, a data session is established between a CB entity and a Data-TW-GW. There could be one or multiple data sessions between a CB entity and a Data-TW-GW, and a CB entity (e.g., deployed in PSF of XaaS) could participate into one or multiple data sessions. A CB entity (e.g., deployed in PSF of XaaS) could participate into one or multiple mission sessions. One or multiple inter-GW sessions are established between Data-TW-GWs. As shown in FIG. 14, two devices are involved in a mission session, and each device establishes two data sessions. A data session may be mapped to a radio bearer, or multiple data sessions are mapped to a radio bearer. It does not rule out the possibility that a data session is mapped to multiple radio bearers. One of the two CB entities in a RAN establishes two data sessions illustrated as small rectangular boxes, another one of the two CB entities in the RAN establishes one data session. One CB entity in NFs or a DN establishes two data sessions, and one CB entity in the NFs or the DN establishes one data session. Two inter-GW sessions are established between the two Data-TW-GWs.

A mission includes no CBs (i.e. no computing-related functionalities) when its goal is only to provide PDU connectivity. In this case, a mission session is reduced to a PDU session. Different Mission Session Types can be defined: PDU connectivity only type, and both data connectivity and processing type (i.e., non PDU connectivity only type) . The PDU connectivity only type indicates that no CB entity is involved in the mission session, i.e., the mission session is reduced to PDU session in this case. In this case, the mission service is reduced to a service for PDU connectivity only. The both data connectivity and processing type (i.e., non PDU connectivity only type) indicates that there is at least one CB entity involved in the mission session, both data forwarding and processing are supported via the mission session, e.g., to support 6G services of data processing (e.g., AI, sensing, a data service) .

In some cases, the CB entity of a mission session is a virtual and dummy entity, e.g., for a mission session of PDU connectivity only type.

Furthermore, for the PDU connectivity only type, there is no data session belonging to the mission session, all data sessions belong to the mission session are dummy data sessions.

In the present disclosure, the terms forward (forwarding) , transmit (transmission) and deliver (delivery) are used interchangeably. Data connectivity and data forwarding are used interchangeably.

For example, one or multiple QoS flows are delivered in a data session. QoS flow is the finest granularity of QoS differentiation in the mission service. Traffic within the same QoS flow receives the same data processing treatment and data forwarding treatment. In some cases, a data session is implemented as a QoS flow.

New radio bearers dedicated for mission service may be established over the air on C/M plane and data plane to provide service with particular QoS. For example, new data radio bearer dedicated for a mission session is established over the air on data plane to provide service with particular QoS.

Different data sessions of a mission session may be mapped and connected via one or more Data-TW-GWs, e.g., depending on whether, and how many Data-TW-GWs are deployed.

Different data sessions of a mission session may be mapped and connected internally within a CB entity.

FIG. 15 is a schematic illustration of tunnels configured per data (inter-GW) session according to one or more embodiments of the present disclosure, as shown in FIG. 15, a rectangular represents a data session or an inter-GW session of a mission session, and a cylindrical represents a tunnel dedicatedly configured for a data session or an inter-GW session of the mission session. The tunnel is configured per data session for a mission session and cannot be shared by different data sessions or inter-GW sessions between two network entities. The type of the tunnel is not a limited to GTP-U tunnel, a QUIC connection, etc. CB entity 1 establishes data sessions 1 and 2 with Data-TW-GW 1. CB entity 2 establishes data sessions 3, 4 and 5 with Data-TW-GW 1. CB entity 3 establishes data sessions 1 and 2 with Data-TW-GW 2. There are inter-GW sessions 1 and 2 established between Data-TW-GW 1 and Data-TW-GW 2. Seven tunnels are established each of which is dedicated for a data session, and two tunnels are established each of which is dedicated for an inter-GW session. As illustrated by the dash line, data sessions 1 and 2 of CB entity 1 are mapped to data session 3 of CB entity 2 via Data-TW-GW 1, data session 3 of CB entity 2 is mapped to data session 4 of CB entity 2 within CB entity 2, data session 4 of CB entity 2 is mapped to inter-GW session 1 via Data-TW-GW 1, inter-GW session 1 is mapped to data session 2 of CB entity 3 via Data-TW-GW 2, data session 2 of CB entity 3 is mapped to data session 1 of CB entity 3 within CB entity 3, data session 1 of CB entity 3 is mapped to inter-GW session 2 via Data-TW-GW 2. For example, CB entity 1 executes CB 1 and CB 2 corresponding to data session 1 and data session 2, respectively. CB entity 1 sends the data processing results of CB 1 and CB 2 (corresponding to data session 1 and data session 2, respectively) to data session 3 of CB entity 2 via Data-TW-GW 1. CB entity 2 executes CB 3 to using the received data from CB entity 1 and then sends the new data processing results to CB entity 1. Back and forth data forwarding and data processing are performed between CB entity 1 and CB entity 2 until CB 1 and CB 2 of CB entity 1 and CB 3 of CB entity 2 are completed. Then CB entity 2 sends the final data processing results of CB 3 to data session 4 of CB entity 2. CB entity 2 executes CB 4 corresponding to data session 4 and sends data processing results to data session 2 of CB entity 3 via Data-TW-GW 1 and Data-TW-GW 2 through inter-GW session 1. CB entity 3 executes CB 6 corresponding to data session 2. Back and forth data forwarding and data processing are performed between CB entity 2 and CB entity 3 until CB 4 of CB entity 2 and CB 6 of CB entity 3 are completed. Then CB entity 3 sends the final data processing results of CB 6 to data session 1 of CB entity 3. CB entity 3 executes CB 7 corresponding to data session 1 and sends data processing results to data session 5 of CB entity 2 via Data-TW-GW 2 and Data-TW-GW 1 through inter-GW session 2. CB entity 2 executes CB 5 corresponding to data session 5. Back and forth data forwarding and data processing are performed between CB entity 3 and CB entity 2 until CB 5 of CB entity 2 and CB 7 of CB entity 3 are completed. Then the mission may be completed. It can be observed that, some data from CB entity 2 should be sent to CB entity 1 via Data-TW-GW 1, and some data from CB entity 2 should be sent to CB entity 3 via Data-TW-GW 1. In order to enable the CB entities and the Data-TW-GWs to deliver data in specific sequence of CBs of a mission via suitable tunnel, and to enable them to detect and recognize the packet received via a tunnel, data forwarding information, e.g., data mapping information and tunnel information, should be configured to the CB entities and Data-TW-GWs, and data processing information, e.g., CB sequence, should be configured to the CB entities.

In some cases, CB entity 1, CB entity 2 and Data-TW-GW 1 are in network domain 1, CB entity 3 and Data-TW-GW 2 are in network domain 2. Network domain 1 and Network domain 2 may be the same or not. The network domain includes but is not limited to a RAN, a CN, a DN and a terminal device. For example, network domain 1 is the RAN and network domain 2 is the CN, and vice versa. Network domain 1 is the RAN and network domain 2 is the DN, and vice versa. Network domain 1 is the CN and network domain 2 is the DN, and vice versa. Network domain 1 is the RAN and network domain 2 is the device, and vice versa.

In some cases, one or more of the network entities are in the DN. For example, CB entity 1, CB entity 2, Data-TW-GW 1 and Data-TW-GW 2 are in the CN, and CB entity 3 is in the DN. As another example, CB entity 1, CB entity 2 and Data-TW-GW 1 are in the RAN, Data-TW-GW 2 is in the CN, and CB entity 3 is in the DN. As another example, Data-TW-GW 2 and CB entity 3 are in the RAN, Data-TW-GW 1 is in the CN, and CB entity 1 and CB entity 2 are in the DN. As another example, Data-TW-GW 2, CB entity 3 and Data-TW-GW 1 are in the CN, and CB entity 1 and CB entity 2 are in the DN.

FIG. 16 is a schematic illustration of tunnels configured per mission session according to one or more embodiments of the present disclosure, as shown in FIG. 16, a rectangular represents a data session or an inter-GW session of a mission session, and a difference compared with FIG. 15 is that a cylindrical represents a tunnel configured for the mission session between two network entities. The tunnel is configured per mission session and may be shared by different data sessions or inter-GW sessions between the two network entities. The type of the tunnel is not limited to a GTP-U tunnel, a QUIC connection, etc. tunnel 1 between CB entity 1 and Data-TW-GW 1 for the mission session is established, tunnel 2 between CB entity 2 and Data-TW-GW 1 for the mission session is established, tunnel 3 between CB entity 3 and Data-TW-GW 2 for the mission session is established, and tunnel 4 between Data-TW-GW 1 and Data-TW-GW 2 for the mission session is established. For example, some packets (e.g., packets of data session 3) received from tunnel 2 should be forwarded by Data-TW-GW 1 to CB entity 1, but some packets (e.g., packets of data session 4) received from tunnel 2 should be forwarded by Data-TW-GW 1 to Data-TW-GW 2 then to CB entity 3. Different from the case where a dedicated tunnel is configured per data session, when the tunnel is configured per mission session, additional information should be configured to enable a CB entity and/or a Data-TW-GW to detect, recognize and deliver a packet, and necessary information should be encapsulated into a packet header.

FIG. 17 is a schematic illustration of tunnels configured per network entity according to one or more embodiments of the present disclosure, as shown in FIG. 17, compared with FIG. 15 and FIG. 16, there are two mission sessions illustrated, which are respectively represented by a dash line and a solid line, a rectangular represents a data session or an inter-GW session of a mission session, and a cylindrical represents a tunnel shared by the two mission sessions between the network entities. Three data sessions 1, 2 and 3 are established between CB entity 1 and Data-TW-GW 1, four data sessions 4, 5, 6 and 7 are established between CB entity 2 and Data-TW-GW 1, and two data sessions 1 and 2 are established between CB entity 3 and Data-TW-GW 2. Data sessions 1 and 2 of CB entity 1, data sessions 4 and 5 of CB entity 2, and data session 2 of CB entity 3 belong to mission session 1. Data session 3 of CB entity 1, data sessions 6 and 7 of CB entity 2 and data session 1 of CB entity 3 belong to mission session 2. The tunnel is configured per network entity. It means the tunnel can be shared by different mission sessions of the network entity. The type of the tunnel is not limited to a GTP-U tunnel, a QUIC connection, etc. Tunnel 1 between CB entity 1 and Data-TW-GW 1 for the two mission sessions is established, tunnel 2 between CB entity 2 and Data-TW-GW 1 for the two mission sessions is established, tunnel 3 between CB entity 3 and Data-TW-GW 2 for the two mission sessions is established, and tunnel 4 between Data-TW-GW 1 and Data-TW-GW 2 for the two mission sessions is established. For example, some packets (e.g., packets of data session 4) received from tunnel 2 should be forwarded by Data-TW-GW 1 to CB entity 1, but some packets (e.g., packets of data session 5) received from tunnel 2 should be forwarded by Data-TW-GW 1 to Data-TW-GW 2 then to CB entity 3. Different from the cases where a tunnel is configured per data session (per inter-GW session) or per mission session, when the tunnel is configured per network entity, additional information should be configured to enable a CB entity and a Data-TW-GW to detect, recognize and deliver a packet, and necessary information should be encapsulated into a packet header.

As described above, over the air, a radio bearer is established between a device and a 6G RAN node. Radio bearers dedicated for a mission service may be established over the air on a data plane to provide a service with particular QoS. For example, a data radio bearer dedicated for a mission session is established over the air on the data plane to provide service with particular QoS. One or multiple devices are involved in a mission session. Each device establishes one or multiple data radio bears corresponding to a mission session. As in FIG. 14, two devices are involved in a mission session, and each device establishes two data sessions. Flexible mapping is enabled between the radio bearer and the data session. A data session may be mapped to a radio bearer (one-to-one mapping) , or multiple data sessions are mapped to a radio bearer (multiple-to-one mapping) . It does not rule out the possibility that a data session is mapped to multiple radio bearers (one-to-multiple mapping) . There are the following problems to be solved:

- For a mission session, new function of the SDAP sublayer should be defined to support the mission service.

- The relationship between the SDAP entity and the mission session/data session should be designed, e.g., the number of SDAP entities to be configured for a mission session/data session.

- The mapping rule between the mission session/data session and the radio bearer (e.g., data radio bearer, or other newly defined radio bearer) should be designed, over the air between the device and the RAN, e.g., to support the one-to-one mapping, the one-to-multiple mapping, or the multiple-to-one mapping.

- New fields in the SDAP packet header are needed to support the mission session and the data session.

- The configuration information elements on the SDAP entity should be designed to establish the radio bearer for the mission session.

In this application, we design new functions of the SDAP sublayer to support the mission service, e.g., to support the mission session and the data session;

- Designing the schemes that an SDAP entity can be configured with different granularities, e.g., per data session, per mission session, or per network entity (e.g., per device, per RAN node, per CB entity of RAN, or per Data-TW-GW of RAN) . And the one-to-one mapping, the one-to-multiple mapping, or the multiple-to-one mapping between the SDAP entity and the data session, the mission session, or the QoS flows are supported;

- Defining new format of the SDAP packet header when SDAP entity is configured with different granularities, e.g., per data session, per mission session, or per network entity. The SDAP packet header includes one or more of new fields of: a mission session ID, a data session ID, assistance information, e.g., together with a QFI;

- Designing an SDAP configuration information element sent by the RAN to the device to configure the SDAP entity, e.g., when the SDAP entity is configured per data session, per mission session, or per entity. And design the procedure for the RAN to configure the device on the SDAP entity and

- Designing the information sent from the core network to the RAN to enable the RAN to decide the SDAP configuration information element.

As shown in FIG. 18, the communication method implemented by a first SDAP entity includes:

step 1: a first SDAP entity (SDAP entity 1 in FIG. 18) receives a packet; and

step 2: the first SDAP entity transmits a SDAP packet generated by the first SDAP entity based on the packet, where the SDAP packet includes information on a mission session, the mission session is to provide a mission service to a mission customer, and the mission service is a service for both PDU connectivity and data processing.

In some cases, the method further includes a step of determining the information on a mission session.

In some cases, the first SDAP entity is deployed in an apparatus, and the apparatus is a device side apparatus or a RAN node side apparatus.

Correspondingly, an embodiment of the present disclosure further provides a communication method, including:

step 2: a second SDAP entity receives a SDAP packet from a first SDAP entity, where the SDAP packet includes information on a mission session, the mission session is to provide a mission service to a mission customer, and the mission service is a service for both PDU connectivity and data processing; and

step 3: the second SDAP entity determines, according to the information on a mission session, which mission session the SDAP packet belongs to.

In some cases, the second SDAP entity is deployed in an apparatus, and the apparatus is a device side apparatus or a RAN node side apparatus.

In some cases, the information on a mission session is included in a packet header of the SDAP packet or a payload of the SDAP packet.

In some cases, the information on a mission session includes one or more of: a mission session ID identifying a mission session, a data session ID identifying a data session, assistance information used for assisting in distinguishing a data session or distinguishing a CB, a quality of service (QoS) flow identifier (QFI) identifying a QoS flow in the mission session, a stream ID identifying a stream frame, a reflective data session indication (RDSI) , or a reflective data session to radio bearer mapping indication (RDDI) , and the RDSI indicates whether a non-access stratum (NAS) is to be informed of an updated of a service data flow (SDF) to data session mapping rule, and the RDDI indicates whether a data session to radio bearer mapping rule is to be updated.

To support the mission service, new functions of the SDAP sublayer should be defined. FIG. 19 is a schematic illustration of a functional view of the SDAP sublayer for the mission service. The functional view of SDAP sublayer is depicted in Figure 19.

In some cases, a data session includes one or more QoS flows. One or more QoS flows are transmitted via a data session. The QoS flow is the finest granularity of QoS differentiation in the data session. Traffic within a QoS flow of a data session receives the same data forwarding treatment (e.g. scheduling, an admission threshold, delay, and a loss rate) and/or data processing treatment (e.g., data processing delay, data processing accuracy, and data processing privacy) . A QoS flow ID (QFI) is used to identify a QoS flow of a data session. The network entity uses the received QFI to determine the QoS flow and the QoS profile which are associated with the received packet of the data session. In this case, as in FIG. 19, functions of the SDAP sublayer for the mission session are:

- transfer of data plane data for the mission service;

- mapping between a QoS flow of a data session of a mission session and a radio bearer (e.g., a DRB, or other newly defined radio bearer (e.g., a mission data radio bearer, a sidelink radio bearer) ) for both DL and UL;

- marking one or more of: a data session ID, a mission session ID, assistance information (e.g., an action ID) , a QoS flow ID, in both DL and UL packets. Which of them are needed to be marked will be clarified in following descriptions, e.g., depending on the SDAP entity being configured per data session, per mission session, or per network entity (e.g., per device, per RAN node, per CB entity of the RAN, or per Data-TW-GW of the RAN) .

In some cases, the finest granularity of QoS differentiation for the mission service is data session instead of the QoS flow. In these case, as in FIG. 18, functions of the SDAP sublayer for mission session are:

- transfer of data plane data for the mission service;

- mapping between a data session of a mission session and a radio bearer (e.g., a DRB, or other newly defined radio bearer (e.g., a mission data radio bearer, a sidelink radio bearer) ) for both DL and UL;

- marking one or more of: a data session ID, a mission session ID, assistance information (e.g., an action ID) , in both DL and UL packets. Which of them are needed to be marked will be clarified in following descriptions, e.g., depending on the SDAP entity being configured per data session, per mission session, or per network entity (e.g., per UE, per RAN node, per CB entity of the RAN, or per Data-TW-GW of the RAN) . The SDAP packet transmitted by the first SDAP entity may be referred to as or included in the data plane data for the mission service cited above. The information on a mission session may include the one or more of: a data session ID, a mission session ID, assistance information (e.g., an action ID) , or a QoS flow ID that needed to be marked in both DL and UL packets cited above.

And the function component of SDAP entity “reflective QoS flow to radio bearer mapping” should be changed to function component “reflective data session to radio bearer mapping” to perform reflective data session to radio bearer mapping. The other function components and details can refer to TS 37.324 and the descriptions are omitted here.

SDAP entity granularity per data session

In some cases, for the method executed by the first SDAP entity, the first SDAP entity corresponds to a data session and is dedicated for a data session. That is, the SDAP entity is configured per data session. In other words, the granularity of the first SDAP entity can be the data session.

FIG. 20 is a schematic illustration of SDAP entities configured per data session according to one or more embodiments of the present disclosure. As in FIG. 20, the SDAP entity is configured per data session. A device and a RAN node are involved in one or more mission sessions. For example, the device and the RAN node are involved in mission session 1, mission session N, etc. One or more data sessions of each mission session are established between the device and the RAN node. For example, Data session 1 and data session 2 of mission session 1 are established between the device and the RAN node. One or more radio bearers are established between the device and the RAN. For example, radio bearer 1, 2, 3, 4 and other radio bearers are established between the device and the RAN node. In some cases, the one or more radio bearers include one or more data radio bearers, one or more mission data radio bearers, or one or more sidelink radio bearers, where the one or more data radio bearers are used for the PDU connectivity, the one or more mission data radio bearers are used for the mission service, and the one or more sidelink radio bearers are used for a sidelink service.

On the device and the RAN node side respectively, each SDAP entity is configured for each data session. For example, SDAP entity 1 and SDAP entity 2 are configured for data session 1 and data session 2, respectively.

In some cases, the first SDAP entity is used for mapping one or more packets of the data session to one or more radio bearers, the one or more packets include the packet received in step 1. A mapping relationship between the data session and the one or more radio bearers includes a one-to-one mapping relationship or a one-to-multiple mapping relationship, the one-to-one mapping relationship indicates that the data session is mapped to one radio bearer, and the one-to-multiple mapping relationship indicates that the data session is mapped to multiple radio bearers.

In some cases, for the one-to-one mapping relationship, one data session corresponds to one radio bearer, one radio bearer corresponds to one data session, and one or more packets of one data session are mapped to one radio bearer. For the one-to-multiple mapping relationship, one data session corresponds to multiple radio bearers, one radio bearer corresponds to one data session, and packets of one data session are mapped to multiple radio bearers. For example, Different packets of one data session can be mapped to different radio bearers of the multiple radio bearers, respectively. As another example, some packets of one data session can be mapped to one or some of the multiple radio bearers, and the other packets of the one data session can be mapped to the other radio bearers of the multiple radio bearers. It does not rule out other possibilities.

Specifically, a SDAP entity maps one or more packets of a data session to one or multiple radio bearers, i.e., the SDAP performs one-to-one mapping and one-to-multiple mapping between the data session and the radio bearer. As shown in FIG. 20, SDAP entity 1 maps packets of data session 1 to radio bearer 1 and radio bearer 2, and SDAP entity 2 maps packets of data session 2 to radio bearer 3 and radio bearer 4. It does not limit the cases where the SDAP entity maps packets of a data session to a radio bearer. The one-to-one mapping relationship may be referred to as the one-to-one mapping between the data session and the radio bearer cited above. The one-to-multiple mapping relationship may be referred to as the one-to-multiple mapping between the data session and the radio bearer cited above.

In some cases, the data session includes one or more QoS flows, and the first SDAP entity is used for mapping one or more packets of the one or more QoS flows of the data session to one or more radio bearers, the one or more packets include the packet received in step 1. A mapping relationship between the one or more QoS flows of the data session and the one or more radio bearers includes one or more of: a one-to-one mapping relationship or a multiple-to-one mapping relationship; the one-to-one mapping relationship indicates that one QoS flow of the data session is mapped to one radio bearer, and the multiple-to-one mapping relationship indicates that multiple QoS flows of the data session are mapped to one radio bearer.

In some cases, one or more QoS flows may be mapped onto one radio bearer. One QoS flow is mapped onto only one radio bearer.

Specifically, when a data session includes one or multiple QoS flows, a SDAP entity maps packets of the QoS flows of a data session to one or multiple radio bearers. In some cases, the packets of a QoS flow of a data session can only be mapped to one radio bearer, but different QoS flows of a data session can be mapped to a same radio bearer or to different radio bearers.

The information on a mission session includes a QFI, where the QFI indicates a QoS flow associated with the SDAP packet.

Specifically, when a SDAP entity is configured per data session, and a data session includes one or more QoS flows, i.e., QoS flow is the finest granularity of QoS differentiation for mission service. The QFI is included in the SDAP packet (e.g., a packet header, or a packet payload) . For example, the DL SDAP data PDU format with the SDAP header for the mission service is same with FIG. 9, and the UL SDAP data PDU format with the SDAP header for the mission service is same with FIG. 10.

In some cases, the information on a mission session includes either or both of a RDSI and a RDDI.

Specifically, when the data session instead of the QoS flow is the finest granularity of QoS differentiation for the mission service, the QFI is not included in the SDAP packet (e.g., the packet header, or the packet payload) . For example, FIG. 21 is a schematic illustration of a DL SDAP data PDU format for a SDAP entity per data session according to one or more embodiments of the present disclosure. The DL SDAP data PDU format with the SDAP header for the mission service is depicted in FIG. 21. The reserved (R) field could be set to 0 and ignored by the SDAP entity. The reflective data Session indication (RDSI) indicates whether NAS should be informed of the updated of service data flow (SDF) to data session mapping rules. The reflective data session to radio bearer mapping indication (RDDI) indicates whether data session to radio bearer mapping rule should be updated. The data field includes the SDAP SDU. The usage of the RDSI and the RDDI can follow the scheme of the RQI and the RDI, but the object is the data session instead of the QoS flow.

As another example, FIG. 22 is a schematic illustration of a UL SDAP data PDU format for a SDAP entity per data session according to one or more embodiments of the present disclosure, the UL SDAP data PDU format with the SDAP header is depicted in FIG. 22.

In some cases, a packet of the mission session is conveyed by SDAP protocol means.

When a SDAP entity is configured per data session, if the SDAP entity receives a packet (including the QFI or not depending on the finest granularity of QoS differentiation described above) , the SDAP entity can determine (optional a QoS flow of) a data session of a mission session which the packet belongs to. The data session can be determined because the SDAP entity is configured dedicatedly for the data session. The mission session can be determined because the data session belongs to the mission (e.g., the relation between mission session and data session is preconfigured to the SDAP entity when the mission session is established) . The QoS flow can be determined based on the QFI.

In some cases, the data session includes one or more QUIC streams, and the first SDAP entity is used for mapping one or more packets of the one or more QUIC streams of the data session to one or more radio bearers, the one or more packets include the packet. A mapping relationship between the one or more QUIC streams of the data session and the one or more radio bearers includes a one-to-one mapping relationship or a multiple-to-one mapping relationship; the one-to-one mapping relationship indicates that one QUIC stream of the data session is mapped to one radio bearer, and the multiple-to-one mapping relationship indicates that multiple QUIC streams of the data session are mapped to one radio bearer.

The information on a mission session includes a stream ID, and the stream ID indicates a stream frame for the data session associated with the SDAP packet.

Specifically, the QFI can be a stream ID when a QUIC connection is established for the mission session. The stream ID identifying a stream frame of a QUIC packet. A QUIC stream may be the finest granularity of QoS differentiation for the mission service.

SDAP entity granularity per mission session

In some cases, for the method executed by the first SDAP entity, the first SDAP entity corresponds to a mission session, and the first SDAP entity is dedicated for the mission session and is shared by one or more data sessions of the mission session. That is, the SDAP entity is configured per mission session. In other words, the granularity of the first SDAP entity can be the mission session.

FIG. 23 is a schematic illustration of SDAP entities configured per mission session according to one or more embodiments of the present disclosure. As in FIG. 23, the SDAP entity is configured per mission session. A device and a RAN node are involved in one or more mission sessions. For example, the device and the RAN node are involved in mission session 1, mission session N, etc. One or more data sessions of each mission session are established between the device and the RAN node. For example, data session 1 and data session 2 of mission session 1 are established between the device and the RAN node. One or more radio bearers are established between the device and the RAN. For example, radio bearer 1, 2, 3, 4 and other radio bearers are established between the device and the RAN node.

On the device and the RAN node side respectively, each SDAP entity is configured for each mission session. For example, SDAP entity 1 and SDAP entity 2 are configured for mission session 1 and mission session N, respectively. Each SDAP entity is shared by the data sessions of a mission session.

In some cases, the first SDAP entity is used for mapping one or more packets of the mission session to one or more radio bearers, the one or more packets include the packet received in step 1. A mapping relationship between the mission session and the one or more radio bearers includes a one-to-one mapping relationship or a one-to-multiple mapping relationship; the one-to-one mapping relationship indicates that the mission session is mapped to one radio bearer, and the one-to-multiple mapping relationship indicates that the mission session are mapped to multiple radio bearers. For the one-to-one mapping relationship, one mission session corresponds to one radio bearer, one radio bearer corresponds to one mission session, and one or more packets of one mission session are mapped to one radio bearer; for the one-to-multiple mapping relationship, one mission session corresponds to multiple radio bearers, one radio bearer corresponds to one mission session, and packets of one mission session are mapped to multiple radio bearers. For example, different packets of one mission session can be mapped to different radio bearers of the multiple radio bearers, respectively. As another example, some packets of one mission session can be mapped to one or some of the multiple radio bearers, and the other packets of the one mission session can be mapped to the other radio bearers of the multiple radio bearers. It does not rule out other possibilities. Specifically, a SDAP entity maps one or more packets of a mission session to one or multiple radio bearers, i.e., the SDAP performs one-to-one mapping and one-to-multiple mapping between the mission session and the radio bearer. As shown in the FIG. 23, SDAP entity 1 maps packets of mission session 1 to radio bearers 1, 2, 3 and 4, and SDAP entity 2 maps packets of mission session N to two radio bearers. It does not limit the cases where the SDAP entity maps packets of a mission session to a radio bearer. The one-to-one mapping relationship may be referred to as the one-to-one mapping between the mission session and the radio bearer cited above. The one-to-multiple mapping relationship may be referred to as the one-to-multiple mapping between the mission session and the radio bearer cited above.

In some cases, the mapping relationship between the mission session and the one or more radio bearers further includes a mapping relationship between one or more data sessions of the mission session and the one or more radio bearers; the mapping relationship between the one or more data sessions of the mission session and the one or more radio bearers includes one or more of: a one-to-one mapping relationship, a one-to-multiple mapping relationship, or a multiple-to-one mapping relationship; the one-to-one mapping relationship indicates that one data session of the mission session is mapped to one radio bearer, the one-to-multiple mapping relationship indicates that one data session of the mission session are mapped to multiple radio bearers, and the multiple-to-one mapping relationship indicates that multiple data sessions of the mission session are mapped to one radio bearer. Specifically, the SDAP entity maps packets of one or more data sessions of a mission session to one or more radio bearers, i.e., the SDAP performs one-to-one mapping, one-to-multiple mapping, and multiple-to-one mapping between the data session and the radio bearer. For example, as in the figure, the SDAP entity 1 maps packets of data session 1 to radio bearer 1 and radio bearer 2, and SDAP entity 2 maps packets of data session 2 to radio bearer 3 and radio bearer 4. It does not limit the cases where the SDAP entity maps packets of a data session to a radio bearer, or maps packets of multiple data sessions to a radio bearer. For example, the SDAP entity 1 maps packets of data session 1 to radio bearer 1, and maps packets of data session 2 to radio bearers 2, 3 and 4. As another example, the SDAP entity 1 maps some packets of data session 1 and some packets of data session 2 to radio bearer 1, maps the other packets of data session 1 to radio bearer 2, and maps the other packets of data session 2 to radio bearers 3 and 4. The one-to-one mapping relationship may be referred to as the one-to-one mapping between the data session and the radio bearer cited above. The one-to-multiple mapping relationship may be referred to as the one-to-multiple mapping between the data session and the radio bearer cited above. The multiple-to-one mapping relationship may be referred to as the multiple-to-one mapping between the data session and the radio bearer cited above.

The information on a mission session includes either or both of a data session ID and assistance information, the data session ID is used to identify a data session, and the assistance information is used to assist in distinguishing the data session or distinguishing a CB.

In some cases, each data session of the mission session includes at least one QoS flow, and the first SDAP entity is used for mapping one or more packets of one or more QoS flows of the one or more data sessions of the mission session to one or more radio bearers, the one or more packets include the packet received in step 1. A mapping relationship between the one or more QoS flows of the one or more data sessions of the mission session and the one or more radio bearers includes one or more of: a one-to-one mapping relationship, or a multiple-to-one mapping relationship; the one-to-one mapping relationship indicates that a packet of one QoS flow of the one or more data sessions of the mission session is mapped to one radio bearer, and the multiple-to-one mapping relationship indicates that packets of multiple QoS flows of the one or more data sessions of the mission session are mapped to one radio bearer.

Specifically, when each data session of a mission session includes one or multiple QoS flows. A SDAP entity maps packets of the QoS flows of one or multiple data sessions of the mission session to one or multiple radio bearers. In some cases, a SDAP entity maps packets of the QoS flows of a data session to one or multiple radio bearers. In some cases, the packets of a QoS flow of a data session can only be mapped to one radio bearer, but different QoS flows of a data session can be mapped to a same radio bearer or to different radio bearers. In some case, a SDAP entity maps packets of the QoS flows of multiple data sessions to one or multiple radio bearers.

In some cases, the information on a mission session includes a QFI and either or both of a data session ID and assistance information, where the QFI indicates a QoS flow associated with the SDAP packet, the data session ID is used to identify a data session, and the assistance information is used to assist in distinguishing the data session or distinguishing a CB.

In some cases, the information on a mission session includes a QFI, and the QFI indicates a QoS flow associated with the SDAP packet, and the QFI includes either or both of: a field indicating a data session ID used to identify a data session, and a field indicating assistance information used to assist in distinguishing a data session or distinguishing a CB. That is, one or more new fields within the QFI may be defined to include one or more of: a data session ID, assistance information, or a stream ID.

Specifically, when a SDAP entity is configured per mission session, and a data session includes one or more QoS flows, i.e., QoS flow is the finest granularity of QoS differentiation for mission service. The QFI and the data session ID and/or the assistance information is included in the SDAP packet (e.g., the packet header, or the packet payload) . The data session ID and/or the assistance information are included in the packet. Based on the data session ID and/or the assistance information, the network entity (e.g., the SDAP entity) can detect and distinguish which data session a packet of a mission session belongs to.

The assistance information is used to assist in distinguishing which data session of a mission session a packet belongs to, or distinguishing which CB a packet of a mission session belongs to.

When a data session ID alone is enough to be used to distinguish which data session a packet of a mission session belongs to, and the data session ID is encapsulated into the packet (e.g., the packet header, or the packet payload) , assistance information needs not to be included in the packet. For example, when a value of a data session ID is assigned globally unique within a mission session, or is assigned globally unique among different data session IDs of all data sessions of the mission session, the data session ID alone is enough to be used to distinguish packets.

When a data session ID alone is not enough to distinguish which data session a packet of a mission session belongs to, or the data session ID is not encapsulated into the packet (e.g., a packet header, or a packet payload) , assistance information needs to be configured. In some cases, a value of the assistance information may be one or more of: an action ID identifying an action of data processing, a CBID identifying a CB, a step ID identifying a step of a procedure, and a mission customer ID identifying a customer of a mission session. The data processing may be but not limited to AI training, AI inference, data pre-processing, data de-privatization (data privacy protection) , data cleaning, data collection, data analytics, sensing, data sanitization, data management, data normalization, useless data filtering, data feature engineering, data compression, data embedding, data representation learning, and data feature extraction.

In some cases, the data session ID and/or the assistance information to be detected or encapsulated in packet are configured by a C/M plane function (e.g., an mission control function (MCF) , a RRC layer) to the network entity (e.g., SDAP entity) . In some cases, before the configuration, the data session ID and/or the assistance information (e.g., to be detected from packet by a network entity) are reported to a C/M plane function by a peer node (e.g., a peer SDAP entity) of the network entity.

In some cases, if assistance information (e.g., an action ID, a CBID) alone is enough to be used to distinguish which data session a packet of a mission session belongs to, and the assistance information (e.g., an action ID) is encapsulated into the packet (e.g., the packet header, or the packet payload) , the data session ID need not be encapsulated into packet header.

In some cases, if assistance information (e.g., an action ID, a CBID) alone is not enough to be used to distinguish which data session a packet of a mission session belongs to, both of the data session ID and the assistance information (e.g., an action ID) are encapsulated into packet (e.g., packet header, or packet payload) .

For example, FIG. 24 is a schematic illustration of a DL SDAP data PDU format for a SDAP entity per mission session with a QFI according to one or more embodiments of the present disclosure. The DL SDAP data PDU format with the SDAP header for the mission service is depicted in FIG. 24, The Data session ID and/or assistance information (e.g., an action ID) field indicates the data session or the CB to which the SDAP PDU belongs. The QFI field indicates the ID of the QoS flow to which the SDAP PDU belongs. The QoS flow belongs to the data session indicated by the data session ID and/or the assistance information (e.g., an action ID) field. The reflective QoS indication (RQI) indicates whether NAS should be informed of the updated of service data flow (SDF) to QoS flow mapping rules. The reflective QoS flow to DRB mapping indication (RDI) indicates whether QoS flow to RB mapping rule should be updated. The data field includes the SDAP SDU.

For example, FIG. 25 is a schematic illustration of a UL SDAP data PDU format for a SDAP entity per mission session with a QFI according to one or more embodiments of the present disclosure. The UL SDAP data PDU format with the SDAP header for the mission service is depicted in FIG. 25. The data session ID and/or the assistance information (e.g., an action ID) field indicates the data session to which the SDAP PDU belongs. The QFI field indicates the ID of the QoS flow to which the SDAP PDU belongs. The QoS flow belongs to the data session indicated by the data session ID and/or the assistance information (e.g., an action ID) field.

Specifically, when the data session instead of the QoS flow is the finest granularity of QoS differentiation for the mission service, the QFI is not included in the SDAP packet (e.g., the packet header, or the packet payload) . For example, FIG. 26 is a schematic illustration of a DL SDAP data PDU format for a SDAP entity per mission session without a QFI according to one or more embodiments of the present disclosure. The DL SDAP data PDU format with the SDAP header for mission service is depicted in FIG. 26. The data session ID and/or the assistance information (e.g., an action ID) field indicates the data session to which the SDAP PDU belongs. The reflective data session indication (RDSI) indicates whether NAS should be informed of the updated of service data flow (SDF) to data session mapping rules. The reflective data session to radio bearer mapping indication (RDDI) indicates whether data Session to radio bearer mapping rule should be updated. The data field includes the SDAP SDU. The usage of the RDSI and the RDDI can follow the scheme of the RQI and the RDI, but the object is the data session instead of the QoS flow.

As another example, FIG. 27 is a schematic illustration of a UL SDAP data PDU format for a SDAP entity per mission session without a QFI according to one or more embodiments of the present disclosure. The UL SDAP data PDU format with the SDAP header is depicted in FIG. 27. The data session ID and/or the assistance information (e.g., an action ID) field indicates the data session to which the SDAP PDU belongs.

In some cases, the packet of the mission session is conveyed by the SDAP protocol means.

When a SDAP entity is configured per mission session, if the SDAP entity receives a packet including the data session ID and/or the assistance information (and optional the QFI, depending on the finest granularity of QoS differentiation described above) , the SDAP entity can determine (optional a QoS flow of) a data session of a mission session which the packet belongs to. The mission session can be determined because the SDAP entity is configured dedicatedly for the mission session. The data session can be based on the data session ID and/or the assistance information (e.g., an action ID) encapsulated in the packet (e.g., the packet header) . The QoS flow can be determined based on the QFI.

In some cases, the mission session includes one or more QUIC streams, and the first SDAP entity is used for mapping one or more packets of the one or more QUIC streams of the mission session to one or more radio bearers, the one or more packets include the packet. A mapping relationship between the one or more QUIC streams of the mission session and the one or more radio bearers includes a one-to-one mapping relationship or a multiple-to-one mapping relationship; the one-to-one mapping relationship indicates that a packet of one QUIC stream of the mission session is mapped to one radio bearer, and the multiple-to-one mapping relationship indicates that packets of multiple QUIC streams of the mission session are mapped to one radio bearer. In some cases, one or more QUIC streams may be mapped onto one radio bearer. One QUIC stream is mapped onto only one radio bearer.

In some cases, the information on a mission session includes a stream ID and either or both of a data session ID and assistance information, where the stream ID is used to identify a stream frame for the mission session associated with the SDAP packet, the data session ID is used to identify a data session, and the assistance information is used to assist in distinguishing a data session or distinguishing a CB.

In some cases, the information on a mission session includes a stream ID, and the stream ID indicates a stream frame for the mission session associated with the SDAP packet, and the stream ID includes either or both of: a field indicating data session ID used to identify a data session, and a field indicating assistance information used to assist in distinguishing a data session or distinguishing a CB. That is, one or more new fields within the stream ID may be defined to include one or more of: a data session ID, assistance information, or a QFI.

Specifically, the QFI or the data session ID can be the stream ID when the QUIC connection is established for the mission session. The stream ID identifying a stream frame of the QUIC packet. The QUIC stream may be the finest granularity of QoS differentiation for mission service.

SDAP entity granularity per network entity

In some cases, for the method executed by the first SDAP entity, the first SDAP entity corresponds to a network entity, the first SDAP entity is dedicated for the network entity and is shared by one or more mission sessions of the network entity, and the one or more mission sessions include the mission session. That is, the SDAP entity is configured per network entity. In other words, the granularity of the first SDAP entity can be the network entity. In some cases, the network entity is one of a device, a RAN node, a CB entity of a RAN, or a gateway (GW) entity.

FIG. 28 is a schematic illustration of SDAP entities configured per network entity according to one or more embodiments of the present disclosure. As in FIG. 28, SDAP entity is configured per network entity (e.g., per device, per RAN node, per CB entity of RAN, or per Data-TW-GW of the RAN) . A device and a RAN node are involved in one or more mission sessions. For example, the device and the RAN node are involved in mission session 1, mission session N, etc. One or more data sessions of each mission session are established between the device and the RAN node. For example, Data session 1 and data session 2 of mission session 1 are established between the device and the RAN node. One or more radio bearers are established between the device and the RAN. For example, radio bearer 1, 2, 3, 4 and other radio bearers are established between the device and the RAN node.

On the device and the RAN node side respectively, one SDAP entity is configured. For example, a SDAP entity is configured, and shared by mission session 1 and mission session N.

In some cases, the first SDAP entity is used for mapping one or more packets of the network entity to one or more radio bearers, the one or more packets include the packet. A mapping relationship between the network entity and the one or more radio bearers includes a one-to-one mapping relationship or a one-to-multiple mapping relationship; the one-to-one mapping relationship indicates that one or more packets of one network entity are mapped to one radio bearer, and the one-to-multiple mapping relationship indicates that packets of one network entity are mapped to multiple radio bearers. For the one-to-one mapping relationship, one network entity corresponds to one radio bearer, one radio bearer corresponds to one network entity, and one or more packets of one network entity are mapped to one radio bearer. For the one-to-multiple mapping relationship, one network entity corresponds to multiple radio bearers, one radio bearer corresponds to one network entity, and packets of one network entity are mapped to multiple radio bearers. For example, Different packets of one network entity can be mapped to different radio bearers of the multiple radio bearers, respectively. As another example, some packets of one network entity can be mapped to one or some of the multiple radio bearers, and the other packets of the one network entity can be mapped to the other radio bearers of the multiple radio bearers. It does not rule out other possibilities.

Specifically, a SDAP entity maps one or more packets of a network entity (e.g., the device, the RAN node) to one or multiple radio bearers. The SDAP entity further maps packets of one or more mission sessions to one or multiple radio bearers, i.e., the SDAP performs one-to-one mapping, one-to-multiple mapping, and multiple-to-one mapping between the mission session and the radio bearer. As shown in FIG. 28, the SDAP entity maps packets of mission session 1 to radio bearers 1, 2, 3 and 4, and maps packets of mission session N to radio bearers 5 and 6. It does not limit the cases where the SDAP entity maps packets of a mission session to a radio bearer, or maps packets of multiple mission sessions to a radio bearer. For example, the SDAP entity maps packets of mission session 1 to radio bearer 1, and maps packets of mission session N to radio bearers 2, 3, 4, 5 and 6. As another example, the SDAP entity maps some packets of mission session 1 and some packets of mission session N to radio bearer 1, maps the other packets of mission session 1 to radio bearer 2 and 3, and maps the other packets of mission session N to radio bearers 4, 5 and 6. The one-to-one mapping relationship may be referred to as the one-to-one mapping between the mission session and the radio bearer cited above. The one-to-multiple mapping relationship may be referred to as the one-to-multiple mapping between the mission session and the radio bearer cited above.

In some cases, the mapping relationship between the network entity and the one or more radio bearers further includes a mapping relationship between one or more mission sessions of the network entity and the one or more radio bearers; the mapping relationship between the one or more mission sessions of the network entity and the one or more radio bearers includes one or more of: a one-to-one mapping relationship, a one-to-multiple mapping relationship, or a multiple-to-one mapping relationship; the one-to-one mapping relationship indicates that one mission session of the network entity is mapped to one radio bearer, the one-to-multiple mapping relationship indicates one mission session of the network entity is mapped to multiple radio bearers, and the multiple-to-one mapping relationship indicates that multiple mission sessions of the network entity are mapped to one radio bearer.

In some cases, the mapping relationship between the one or more mission sessions of the network entity and the one or more radio bearers further includes a mapping relationship between one or more data sessions of the one or more mission sessions of the network entity and the one or more radio bearers; the mapping relationship between the one or more data sessions of the one or more mission sessions of the network entity and the one or more radio bearers includes one or more of: a one-to-one mapping relationship, a one-to-multiple mapping relationship, or a multiple-to-one mapping relationship; the one-to-one mapping relationship indicates that one data session of the one or more mission sessions of the network entity is mapped to one radio bearer, the one-to-multiple mapping relationship indicates that one data session of the one or more mission sessions of the network entity is mapped to multiple radio bearers, and the multiple-to-one mapping relationship indicates that multiple data sessions of the one or more mission sessions of the network entity are mapped to one radio bearer.

Specifically, the SDAP entity maps packets of one or more data sessions of a mission session to one or more radio bearers, i.e., the SDAP performs one-to-one mapping, one-to-multiple mapping, and multiple-to-one mapping between the data session and the radio bearer. For example, As shown in FIG. 28, the SDAP entity maps packets of data session 1 to radio bearer 1 and radio bearer 2, maps packets of data session 2 to radio bearer 3 and radio bearer 4. It does not limit the cases where the SDAP entity maps packets of a data session to a radio bearer, or maps packets of multiple data sessions to a radio bearer. For example, the SDAP entity maps packets of data session 1 to radio bearer 1, and maps packets of data session 2 to radio bearers 2, 3 and 4. As another example, the SDAP entity maps some packets of data session 1 and some packets of data session 2 to radio bearer 1, maps the other packets of data session 1 to radio bearer 2, and maps the other packets of data session 2 to radio bearers 3 and 4. The one-to-one mapping relationship may be referred to as the one-to-one mapping between the data session and the radio bearer cited above. The one-to-multiple mapping relationship may be referred to as the one-to-multiple mapping between the data session and the radio bearer cited above. The multiple-to-one mapping relationship may be referred to as the multiple-to-one mapping between the data session and the radio bearer cited above.

In some cases, the information on a mission session includes one or more of: a mission session ID, a data session ID, or assistance information; the mission session ID is used to identify a mission session, the data session ID is used to identify a data session included in the mission session, and the assistance information is used to assist in distinguishing the data session or distinguishing a CB.

In some cases, each data session of a mission session of a network entity includes at least one QoS flow, and the first SDAP entity is used for mapping one or more packets of one or more QoS flows to one or more radio bearers, the one or more packets include the packet. A mapping relationship between the one or more QoS flows and the one or more radio bearers includes one or more of: a one-to-one mapping relationship, or a multiple-to-one mapping relationship; the one-to-one mapping relationship indicates that one QoS flow is mapped to one radio bearer, and the multiple-to-one mapping relationship indicates that multiple QoS flows are mapped to one radio bearer.

In some cases, the information on a mission session includes a QFI and one or more of: a mission session ID, a data session ID or assistance information, where the QFI indicates a QoS flow associated with the SDAP packet, the mission session ID is used to identify a mission session, the data session ID is used to identify a data session, and the assistance information is used to assist in distinguishing the data session or distinguishing a CB.

In some cases, the information on a mission session includes a QFI, and the QFI indicates a QoS flow associated with the SDAP packet, and the QFI includes one or more of: a field indicating mission session ID used to identify a mission session, a field indicating data session ID used to identify a data session, or a field indicating assistance information used to assist in distinguishing a data session or distinguishing a CB. That is, one or more new fields within the QFI may be defined to include one or more of: a mission session ID, a data session ID, assistance information, or a stream ID.

Specifically, when a SDAP entity is configured per network entity (i.e., a device, a RAN node) , and a data session includes one or more QoS flows, i.e., QoS flow is the finest granularity of QoS differentiation for the mission service. The QFI and one or more of: the mission session ID, the data session ID and the assistance information, are included in the SDAP packet (e.g., the packet header, or the packet payload) . Based on the one or more of the mission Session ID, the data session ID and the assistance information, the network entity can detect and distinguish which data session a packet received from the SDAP entity shared by multiple mission sessions belongs to. The assistance information is used to assist in distinguishing which data session a packet received/sent by a SDAP entity shared by mission sessions belongs to, or distinguishing which CB a packet of a mission session belongs to.

In some cases, when a mission session ID and a data session ID together are enough to be used to distinguish which data session a packet received/sent by a SDAP entity shared by mission sessions belongs to, and the mission session ID and the data session ID together are encapsulated into the packet (e.g., the packet header, or the packet payload) , the assistance information needs not to be included in the packet. For example, when the value of a data session ID is assigned globally unique within a mission session, and the value of a mission session ID is assigned globally unique among different mission sessions, the mission session ID and the data session ID together are enough to be used to distinguish packets.

In some cases, when a data session ID alone is enough to be used to distinguish which data session a packet received/sent by a SDAP entity shared by the mission sessions belongs to, and the data session ID is encapsulated into the packet (e.g., the packet header, or the packet payload) , the assistance information needs not to be included in the packet. For example, when a data session ID is assigned globally unique among different data session IDs of all the data sessions for all mission sessions established between two network entities, the data session ID alone is enough to be used to distinguish packets.

In some cases, when a mission session ID and a data session ID together are not enough to distinguish which data session a packet received/sent by a SDAP entity shared by mission sessions belongs to, the assistance information need be included in packet header.

In some cases, when a mission session ID and a data session ID together are enough to distinguish which data session a packet received/sent by a SDAP entity shared by mission sessions belongs to, but either the mission session ID or the data session ID (e.g., only the mission session ID, or the data session ID is encapsulated in the packet) is not encapsulated into the packet (e.g., the packet header, or the packet payload) , assistance information needs to be included in the packet header.

In some cases, when the assistance information is configured, the assistance information alone, or a mission session ID and the assistance information together, or a data session ID and the assistance information together, or a mission session ID, a data session ID and the assistance information together, should be enough to distinguish which data session a packet received from/delivered to a tunnel shared by mission sessions belongs to, and should be encapsulated in the packet.

In some cases, the assistance information may be one or more of: an action ID identifying an action of data processing, a CBID identifying a CB, a step ID identifying a step of a procedure, and a mission customer ID identifying a customer of a mission session. The data processing may be but not limited to AI training, AI inference, data pre-processing, data de-privatization (data privacy protection) , data cleaning, data collection, data analytics, sensing, data sanitization, data management, data normalization, useless data filtering, data feature engineering, data compression, data embedding, data representation learning, and data feature extraction.

In some cases, one or more of: the mission session ID, the data session ID and the assistance information to be detected or encapsulated in packet are configured by the C/M plane function (e.g., MCF) to the network entity. In some cases, before the configuration, the data session ID and/or the assistance information (e.g., to be detected from the packet by a network entity) are reported to the C/M plane function by a peer node of the network entity.

For the following descriptions, they are described taking that the mission session ID, the data session ID and the assistance information are all included in packet as example, it can be extended to the other cases, e.g., where the mission session ID and the data session ID or the assistance information is included in the packet.

For example, FIG. 29 is a schematic illustration of a DL SDAP data PDU format for a SDAP entity per network entity with a QFI according to one or more embodiments of the present disclosure. The DL SDAP data PDU format with the SDAP entity per network entity (e.g., per device, per RAN node, or per Data-TW-GW of the RAN) with the QFI is depicted in FIG. 29, the data session ID and/or the assistance information (e.g., an action ID) field indicates the data session to which the SDAP PDU belongs. The data session belongs to a mission session identified by the mission session ID field. The QFI field indicates the ID of the QoS flow to which the SDAP PDU belongs. The QoS flow belongs to the data session indicated by the data session ID and/or the assistance information (e.g., an action ID) field. The reflective QoS indication (RQI) indicates whether NAS should be informed of the updated of service data flow (SDF) to QoS flow mapping rules. The reflective QoS flow to DRB mapping indication (RDI) indicates whether the QoS flow to RB mapping rule should be updated. The data field includes the SDAP SDU.

For example, FIG. 30 is a schematic illustration of a UL SDAP data PDU format for a SDAP entity per network entity with a QFI according to one or more embodiments of the present disclosure. The UL SDAP data PDU format with the SDAP header for the mission service is depicted in FIG. 30. The data session ID and/or the assistance information (e.g., an action ID) field indicates the data session to which the SDAP PDU belongs. The data session belongs to a mission session identified by the mission session ID field. The QFI field indicates the ID of the QoS flow to which the SDAP PDU belongs. The QoS flow belongs to the data session indicated by the data session ID and/or the assistance information (e.g., an action ID) field.

When the data session instead of the QoS flow is the finest granularity of QoS differentiation for the mission service, the QFI is not included in the SDAP packet (e.g., the packet header, or the packet payload) . For example, FIG. 31 is a schematic illustration of a DL SDAP data PDU format for a SDAP entity per network entity without a QFI according to one or more embodiments of the present disclosure. The DL SDAP data PDU format with the SDAP header for the mission service is depicted in FIG. 31. The data session ID and/or the assistance information (e.g., an action ID) field indicates the data session to which the SDAP PDU belongs. The data session belongs to a mission session identified by the mission session ID field. The reflective data session indication (RDSI) indicates whether NAS should be informed of the updated of service data flow (SDF) to data session mapping rules. The reflective data session to radio bearer mapping indication (RDDI) indicates whether data session to radio bearer mapping rule should be updated. The data field includes the SDAP SDU. The usage of the RDSI and the RDDI can follow the scheme of the RQI and the RDI, but the object is the data session instead of the QoS flow.

As another example, FIG. 32 is a schematic illustration of a UL SDAP data PDU format for a SDAP entity per network entity without a QFI according to one or more embodiments of the present disclosure. The UL SDAP data PDU format with the SDAP header is depicted in FIG. 32. The data session ID and/or the assistance information (e.g., an action ID) field indicates the data session to which the SDAP PDU belongs. The data session belongs to a mission session identified by the mission session ID field.

When a SDAP entity is configured per network entity (e.g., per device, per RAN node, per CB entity of RAN, or per Data-TW-GW of the RAN) , if the SDAP entity receives a packet including the mission session ID, the data session ID and/or the assistance information (and optional the QFI, depending on the finest granularity of QoS differentiation described above) , the SDAP entity can determine (optional a QoS flow of) a data session of a mission session which the packet belongs to. The data session can be determined based on the data session ID and/or the assistance information (e.g., an action ID) encapsulated in the packet (e.g., the packet header) . The mission Session can be determined based on the mission session ID encapsulated in the packet (e.g., packet header) . The QoS flow can be determined based on the QFI.

In some cases, the one or more mission sessions of the network entity includes one or more QUIC streams, and the first SDAP entity is used for mapping one or more packets of the one or more QUIC streams of the network entity to one or more radio bearers, the one or more packets include the packet. A mapping relationship between the one or more QUIC streams of the network entity and the one or more radio bearers includes a one-to-one mapping relationship or a multiple-to-one mapping relationship; the one-to-one mapping relationship indicates that one QUIC stream of the network entity is mapped to one radio bearer, and the multiple-to-one mapping relationship indicates that multiple QUIC streams of the network entity are mapped to one radio bearer. In some cases, one or more QUIC streams may be mapped onto one radio bearer. One QUIC stream is mapped onto only one radio bearer.

In some cases, the information on a mission session includes a stream ID and one or more of: a mission session ID, a data session ID or assistance information, where the stream ID is used to identify a stream frame for the network entity associated with the SDAP packet, the mission session ID is used to identify a mission session, the data session ID is used to identify a data session, and the assistance information is used to assist in distinguishing a data session or distinguishing a CB.

In some cases, the information on a mission session includes a stream ID, where the stream ID indicates a stream frame for the network entity associated with the SDAP packet, and the stream ID includes one or more of: a field indicating mission session ID used to identify a mission session, a field indicating data session ID used to identify a data session, or a field indicating assistance information used to assist in distinguishing a data session or distinguishing a CB. That is, one or more new fields within the stream ID may be defined to include one or more of: a mission session ID, a data session ID, assistance information, or a QFI.

Specifically, the QFI or the data session ID can be the stream ID when the QUIC connection is established for mission session. The stream ID identifying a stream frame of the QUIC packet. The QUIC stream may be the finest granularity of QoS differentiation for the mission service.

The lengths of the new fields (e.g., the mission session ID, the data session ID and/or the assistance information, the RDDI, the RDSI, the QFI) described above are not limited.

It does not limit the locations and sequences of the new fields in SDAP packet, e.g., within, before, or after other existing fields. For example, the mission session ID field or the data session ID and/or the assistance information field can be in, before, or after the field of the Reserve (R) , the RQI, or the RDI.

SDAP entity configuration

In an implementation, the first SDAP entity may be deployed in an apparatus, and the apparatus may be a device side apparatus or a RAN node side apparatus, For the method executed by the first SDAP entity, the method further includes:

establishing, reconfiguring, resuming or releasing, by the device side apparatus, the SDAP entities including the first SDAP entity according to the first message.

In an implementation, the second SDAP entity may be deployed in an apparatus, and the apparatus may be a device side apparatus or a RAN node side apparatus. For the method executed by the second SDAP entity, the method further includes:

In some cases, the first message is used to add, modify, resume and release data radio bearers. The first message or the second message includes a radio resource control (RRC) message or an X as a service (XaaS) service signaling bearer (XSB) message.

FIG. 33 is a schematic illustration of a procedure for the SDAP entity configuration according to one or more embodiments of the present disclosure. As shown in FIG. 33, the method includes a RAN sends SDAP configuration information element to a device, e.g., via a RRC message, or other newly defined message (e.g., a message sent over newly defined XaaS service signaling bearer (XSB) ) . The first message may be referred to as the RRC message or other newly defined message that carries the SDAP configuration information element cited above. The configuration information may be referred to as the SDAP configuration information element cited above. The device side apparatus may be referred to as the device that receiving the SDAP configuration information element sent by the RAN cited above. It should be understood that the device side apparatus may also be the RAN cited above, which is not limited.

In some cases, for the method executed by the first SDAP entity, the configuration information indicates one or more of: one or more mission sessions, one or more data sessions, one or more QoS flows, mapping information, or SDAP entity granularity information; and the SDAP entity granularity information indicates that the first SDAP entity is an SDAP entity corresponding to a data session and dedicated for the data session, an SDAP entity corresponding to a mission session and dedicated for the mission session, or an SDAP entity corresponding to a network entity and dedicated for the network entity; the mapping information includes one or more of: a mapping relationship between the one or more mission sessions and the one or more data sessions, a mapping relationship between the one or more data sessions and the one or more QoS flows, or a mapping relationship among the one or more mission sessions, the one or more data sessions and the one or more QoS flows.

In some cases, for the method executed by the second SDAP entity, the configuration information indicates one or more of: one or more mission sessions, one or more data sessions, one or more QoS flows, mapping information, or SDAP entity granularity information; and the SDAP entity granularity information indicates that the second SDAP entity is an SDAP entity corresponding to a data session and dedicated for the data session, an SDAP entity corresponding to a mission session and dedicated for the mission session, or an SDAP entity corresponding to a network entity and dedicated for the network entity; the mapping information includes one or more of: a mapping relationship between the one or more mission sessions and the one or more data sessions, a mapping relationship between the one or more data sessions and the one or more QoS flows, or a mapping relationship among the one or more mission sessions, the one or more data sessions and the one or more QoS flows.

In some cases, for both the method executed by the first SDAP entity and the method executed by the second SDAP entity, the one or more mission sessions are identified by one or more mission session IDs or a session group ID; the one or more data sessions are identified by one or more data session IDs; the one or more QoS flows are identified by one or more QFIs.

For both the method executed by the first SDAP entity and the method executed by the second SDAP entity, in an embodiment, the first message includes a radio bearer ID identifying a radio bearer, and the one or more mission session IDs or the session group ID identifying the one or more mission sessions, and the one or more mission sessions are to be mapped to the radio bearer. In another embodiment, the first message includes a radio bearer ID identifying a radio bearer and the one or more data session IDs identifying the one or more data sessions, and the one or more data sessions are to be mapped to the radio bearer. In yet another embodiment, the first message includes a radio bearer ID identifying a radio bearer and the one or more data session IDs identifying the one or more data sessions, and the one or more data sessions are to be mapped to the radio bearer.

In some cases, for both the method executed by the first SDAP entity and the method executed by the second SDAP entity, the mapping relationship between the one or more mission sessions and the one or more data sessions indicates parts of the one or more data sessions identified by the one or more data session IDs belongs to a mission session of the one or more mission sessions identified by the one or more mission session IDs or the session group ID; the mapping relationship between the one or more data sessions and the one or more QoS flows indicates parts of the one or more QoS flows identified by the one or more QFIs belongs to a data session of the one or more data sessions identified by the one or more data session IDs; and the mapping relationship among the one or more mission sessions, the one or more data sessions and the one or more QoS flows indicates: parts of the one or more QoS flows identified by the one or more QFIs belongs to a data session of the one or more data sessions identified by the one or more data session IDs, and parts of the one or more data sessions identified by the one or more data session IDs belongs to a mission session of the one or more mission sessions identified by the one or more mission session IDs or a session group ID.

Specifically, the SDAP configuration information element (the configuration information) includes one or more of: one or multiple mission session IDs, one or multiple data session IDs (and/or assistance information) , (optional) one or multiple QFIs, mapping information, and SDAP entity granularity information. The QFI is optional, depending on whether QoS flow is the finest granularity of QoS differentiation as described above. The mapping information indicates the relationship of a mission session ID, one or multiple data session ID and (optional) one or multiple QFIs. It indicates one or multiple data sessions identified by the one or multiple data session IDs belongs to a mission session identified by the mission session ID, and optional one or multiple QoS flows identified by the one or multiple QFIs belongs to a data session. The SDAP entity granularity information indicates the SDAP entity is configured per data session, per mission session, or per network entity.

In some cases, the receiving, by the device side apparatus, the first message from the RAN node side apparatus includes: receiving, by the device side apparatus, the first message from the RAN node side apparatus in a radio bearer setup procedure, a radio bearer reconfiguration procedure, a radio bearer resume procedure, or a radio bearer release procedure.

For example, the configuration information element can be sent in radio bearer setup or update procedure, e.g., as in FIG. 6.

SDAP configuration information element (IE) for SDAP entity per data session, per mission session and per network entity are depicted in FIG. 34-FIG. 38, respectively. They are examples and are evolved from the SDAP configuration of 3GPP TS 38.331. More details could be referred to TS 38.331.

In some cases, for the method executed by the first SDAP entity, the first SDAP entity corresponds to a data session and is dedicated for a data session, the configuration information includes a mission session ID, a data session ID, and one or more QFIs, and the mapping information is indicated by a sequence structure of the mission session ID, the data session ID, and the one or more QFIs. The configuration information indicates the SDAP entity granularity information, and the SDAP entity granularity information is indicated by an indication included in the configuration information; or the SDAP entity granularity information is indicated by one data session ID listed in the configuration information.

In some cases, for the method executed by the second SDAP entity, the second SDAP entity corresponds to a data session and is dedicated for a data session, the configuration information includes a mission session ID, a data session ID, and one or more QFIs, and the mapping information is indicated by a sequence structure of the mission session ID, the data session ID, and the one or more QFIs. The configuration information indicates the SDAP entity granularity information, and the SDAP entity granularity information is indicated by an indication included in the configuration information; or the SDAP entity granularity information is indicated by one data session ID listed in the configuration information.

Specifically, FIG. 34 is a schematic illustration of a SDAP configuration information element for a SDAP entity per data session according to one or more embodiments of the present disclosure. FIG. 35 is a schematic illustration of another SDAP configuration information element for a SDAP entity per data session according to one or more embodiments of the present disclosure. The SDAP configuration IE for SDAP entity per data session is depicted in one of FIG. 34-FIG. 35. As shown in FIG. 34, the SDAP configuration IE includes: a mission session ID, a data session ID, one or multiple QFIs. The mapping between the mission session ID, the data session ID and the one or multiple QFIs is implicitly indicated, based on the sequence structure, and they are listed in sequence. As shown in FIG. 35, the SDAP configuration IE includes: a data session ID, one or multiple QFIs, and a mission session ID is listed outside of the SDAP configuration IE. The mapping between the mission session ID, the data session ID and the one or multiple QFIs is implicitly indicated, based on the sequence structure, and they are listed in sequence. As shown in FIG. 34 and FIG. 35, the SDAP entity granularity (the SDAP entity granularity information) is implicitly indicated because a maximum of only one data session ID can be listed in the SDAP configuration IE. In an alternative case, the SDAP entity granularity (the SDAP entity granularity information) is indicated by an indication included in the configuration information. As shown in FIG. 34 and FIG. 35, the data session identified by the data session ID belongs to the mission session identified by the mission session ID. The SDAP configuration IE indicates that the SDAP entity is configured for a data session identified by the data session ID, and the data session belongs to a mission session identified by the mission session ID, and the data session includes one or multiple QoS flows identified by the one or multiple QFIs. The maximum number of QoS flows corresponding to the SDAP entity is decided by the value of maximum number of QFIs (maxNrofQFIs) . If the finest granularity of QoS differentiation is data session instead of QoS flow, the minimum number of QFIs corresponding to the SDAP entity should be 0 instead of 1.

In some cases, for the method executed by the first SDAP entity, the first SDAP entity corresponds to a mission session, and the first SDAP entity is dedicated for the mission session and is shared by one or more data sessions of the mission session, the configuration information includes: a mission session ID, one or more data session IDs, and one or more QFIs, and the mapping information is indicated by a sequence structure of the mission session ID, the one or more data session IDs, and the one or more QFIs. The configuration information indicates the SDAP entity granularity information, and the SDAP entity granularity information is indicated by an indication included in the configuration information; or the SDAP entity granularity information is indicated by one mission session ID listed in the configuration information.

In some cases, for the method executed by the second SDAP entity, the second SDAP entity corresponds to a mission session, and the second SDAP entity is dedicated for the mission session and is shared by one or more data sessions of the mission session, the configuration information includes: a mission session ID, one or more data session IDs, and one or more QFIs, and the mapping information is indicated by a sequence structure of the mission session ID, the one or more data session IDs, and the one or more QFIs. The configuration information indicates the SDAP entity granularity information, and the SDAP entity granularity information is indicated by an indication included in the configuration information; or the SDAP entity granularity information is indicated by one mission session ID listed in the configuration information.

Specifically, FIG. 36 is a schematic illustration of a SDAP configuration information element for a SDAP entity per mission session according to one or more embodiments of the present disclosure. The SDAP configuration IE for SDAP entity per mission session is depicted in FIG. 36. The configuration IE includes: a mission session ID, one or multiple data session IDs, one or multiple QFIs. The mapping between the mission session ID, the one or multiple data session IDs and the one or multiple QFIs is implicitly indicated, based on the sequence structure. The SDAP entity granularity (the SDAP entity granularity information) is implicitly indicated because a maximum of only one mission session ID can be listed in the IE. In an alternative case, the SDAP entity granularity (the SDAP entity granularity information) is indicated by an indication included in the configuration information. The SDAP configuration IE indicates that the SDAP entity is configured for a mission session identified by the mission session ID, and the mission session includes one or multiple data sessions identified by the one or multiple data session IDs, and each data session includes one or multiple QoS flows identified by one or multiple QFIs. The maximum number of data sessions of the mission session is decided by the value of maximum number of data sessions (maxNrofDataSession) . The maximum number of QoS flows of a data session is decided by the value of maximum number of QFIs (maxNrofQFIs) . If the finest granularity of QoS differentiation is data session instead of QoS flow, the minimum number of QFIs corresponding to a data session ID should be 0 instead of 1.

In some cases, for the method executed by the first SDAP entity, the first SDAP entity corresponds to a network entity, the first SDAP entity is dedicated for the network entity and is shared by one or more mission sessions of the network entity, and the one or more mission sessions include the mission session, the configuration information includes: one or more mission session IDs, one or more data session IDs, one or more QFIs, and the mapping information is indicated by a sequence structure of the one or more mission session IDs, the one or more data session IDs, and the one or more QFIs. The configuration information indicates the SDAP entity granularity information, and the SDAP entity granularity information is indicated by an indication included in the configuration information; or the SDAP entity granularity information is indicated by multiple mission session IDs listed in the configuration information.

In some cases, for the method executed by the second SDAP entity, the second SDAP entity corresponds to a network entity, the second SDAP entity is dedicated for the network entity and is shared by one or more mission sessions of the network entity, and the one or more mission sessions include the mission session, the configuration information includes: one or more mission session IDs, one or more data session IDs, one or more QFIs, and the mapping information is indicated by a sequence structure of the one or more mission session IDs, the one or more data session IDs, and the one or more QFIs. The configuration information indicates the SDAP entity granularity information, and the SDAP entity granularity information is indicated by an indication included in the configuration information; or the SDAP entity granularity information is indicated by multiple mission session IDs listed in the configuration information.

Specifically, FIG. 37 is a schematic illustration of a SDAP configuration information element for a SDAP entity per network entity according to one or more embodiments of the present disclosure. The SDAP configuration IE for SDAP entity per network entity is depicted in FIG. 37. The configuration IE includes: one or multiple mission session IDs, one or multiple data session IDs, one or multiple QFIs. The mapping between the one or multiple mission session IDs, the one or multiple data session IDs and the one or multiple QFIs is implicitly indicated, based on the sequence structure. The SDAP entity granularity (the SDAP entity granularity information) is implicitly indicated because a number of mission sessions can be listed in the IE. In an alternative case, the SDAP entity granularity (the SDAP entity granularity information) is indicated by an indication included in the configuration information. The SDAP entity can be shared by multiple mission sessions. The maximum number of mission sessions can be configured is decided by the value of maximum number of mission sessions (maxNrofMissionSession) . The SDAP configuration IE indicates that the SDAP entity is configured and shared by one or multiple mission sessions identified by the one or multiple mission session IDs, and each mission session includes one or multiple data sessions identified by one or multiple data session IDs, and each data session includes one or multiple QoS flows identified by one or multiple QFIs. The maximum number of data sessions of a mission session is decided by the value of maximum number of data sessions (maxNrofDataSession) . The maximum number of QoS flows of a data session is decided by the value of maximum number of QFIs (maxNrofQFIs) . If the finest granularity of QoS differentiation is data session instead of QoS flow, the minimum number of QFIs corresponding to a data session ID should be 0 instead of 1.

In an alternative case, the SDAP entity granularity (the SDAP entity granularity information) is indicated by an indication included in the SDAP configuration information. FIG. 38 is a schematic illustration of a SDAP configuration information element for a SDAP entity according to one or more embodiments of the present disclosure, the granularity of the SDAP entity is indicated by the indication (for example, the “granularity” shown in FIG. 38) which can be enumerated as one of: data session, mission session and entity. The indication is enumerated as data session for SDAP entity per data session. The indication is enumerated as mission session for SDAP entity per mission session. The indication is enumerated as entity for SDAP entity per network entity.

In some cases, the indication is a string or a bitmap.

The value of a mission session ID, data session ID can be also listed in the SDAP configuration IE, which are not illustrated in FIG. 34-FIG. 38.

In some cases, the configuration information further includes one or more values of assistance information. Specifically, the assistance information can be also included in the SDAP configuration IE (the configuration information) , which is not illustrated in FIG. 34-FIG. 38.

In some cases, a value of the assistance information included in the information or a value of the assistance information included in the configuration information includes at least one of: an action ID identifying an action of data processing, a CBID identifying a CB, a step ID identifying a step of a procedure, and a mission customer ID identifying a customer of a mission session.

Determination of the configuration information

In some cases, for both the method executed by the first SDAP entity and the method executed by the second SDAP entity, the configuration information is determined by the RAN node side apparatus according to a second message from a CN node, and the second message is used by the RAN node side apparatus to determine the configuration information.

In some cases, for the method executed by the first SDAP entity, the second message indicates one or more of: one or more mission sessions, one or more data sessions, one or more QoS flows, mapping information, or SDAP entity granularity information, and the SDAP entity granularity information indicates that the first SDAP entity is an SDAP entity corresponding to a data session and dedicated for the data session, an SDAP entity corresponding to a mission session and dedicated for the mission session, or an SDAP entity corresponding to a network entity and dedicated for the network entity, the mapping information includes one or more of: a mapping relationship between the one or more mission sessions and the one or more data sessions, or a mapping relationship between the one or more data sessions and the one or more QoS flows, or a mapping relationship among the one or more mission sessions, the one or more data sessions and the one or more QoS flows.

In some cases, for the method executed by the second SDAP entity, the second message indicates one or more of: one or more mission sessions, one or more data sessions, one or more QoS flows, mapping information, or SDAP entity granularity information, and the SDAP entity granularity information indicates that the second SDAP entity is an SDAP entity corresponding to a data session and dedicated for the data session, an SDAP entity corresponding to a mission session and dedicated for the mission session, or an SDAP entity corresponding to a network entity and dedicated for the network entity, the mapping information includes one or more of: a mapping relationship between the one or more mission sessions and the one or more data sessions, or a mapping relationship between the one or more data sessions and the one or more QoS flows, or a mapping relationship among the one or more mission sessions, the one or more data sessions and the one or more QoS flows.

In some cases, for both the method executed by the first SDAP entity and the method executed by the second SDAP entity, the mapping relationship between the one or more mission sessions and the one or more data sessions indicates parts of the one or more data sessions identified by the one or more data session IDs belongs to a mission session of the one or more mission sessions identified by the one or more mission session IDs or a session group ID; the mapping relationship between the one or more data sessions and the one or more QoS flows indicates parts of the one or more QoS flows identified by the one or more QFIs belongs to a data session of the one or more data sessions identified by the one or more data session IDs; and the mapping relationship among the one or more mission sessions, the one or more data sessions and the one or more QoS flows indicates: parts of the one or more QoS flows identified by the one or more QFIs belongs to a data session of the one or more data sessions identified by the one or more data session IDs, and parts of the one or more data sessions identified by the one or more data session IDs belongs to a mission session of the one or more mission sessions identified by the one or more mission session IDs or a session group ID.

In some cases, for both the method executed by the first SDAP entity and the method executed by the second SDAP entity, the second message is used by the RAN node side apparatus to determine one or more of: a number of radio bearers to be mapped to for a data session or a mission session; at least one of one or more data sessions, one or more mission sessions, or one or more QoS flows, to be mapped to a radio bearer; or the SDAP entity granularity information.

In an implementation, for both the method executed by the first SDAP entity and the method executed by the second SDAP entity, the method further includes:

determining, by the RAN node side apparatus, the configuration information for the device side apparatus. To enable the RAN to decide and send the SDAP configuration information elements to the device, necessary information should be notified to RAN in advance. The information included in the second message may be referred to as the necessary information cited above.

In some cases, for both the method executed by the first SDAP entity and the method executed by the second SDAP entity, the determining the configuration information for the device side apparatus includes one or more of: determining a number of radio bearers to be mapped to for a data session or a mission session; determining at least one of one or more data sessions, one or more mission sessions, or one or more QoS flows, to be mapped to a radio bearer; or determining the SDAP entity granularity information.

FIG. 39 is a schematic illustration of a procedure of determination of the configuration information according to one or more embodiments of the present disclosure. As shown in FIG. 39, the core network (CN) sends necessary information to the RAN to enable the RAN to decide the SDAP configuration information elements. The information (information included in the second message) sent from the CN to the RAN includes one or more of: one or multiple mission session IDs, one or multiple data session IDs (and/or assistance information) , (optional) one or multiple QFIs, mapping information, and (optional) SDAP entity granularity information. The QFI is optional, depending on whether the QoS flow is the finest granularity of QoS differentiation as described above. The mapping information indicates the relationship of a mission session ID, one or multiple data session ID and (optional) one or multiple QFIs. It indicates one or multiple data sessions identified by the one or multiple data session IDs belongs to a mission session identified by the mission session ID, and optional one or multiple QoS flows identified by the one or multiple QFIs belongs to a data session. The SDAP entity granularity information is optionally sent, it indicates the SDAP entity is configured per data session, per mission session, or per network entity. If the SDAP entity granularity information is sent, it assists the RAN to decide the SDAP entity granularity; otherwise, the SDAP entity granularity can be left as RAN intra-implementation, and left to be decided by RAN itself. For example, the CN (e.g., an MCF) sends mission session establishment request message to the RAN. The message includes the information above.

After the RAN receives the information, the RAN decides (determines) the SDAP configuration information elements (the configuration information) . For example, the RAN firstly decides the number of radio bearers to be setup or updated, and specific one or multiple data sessions or mission sessions or QoS flows are mapped to specific one or multiple radio bearers. Then the SDAP configuration information (the configuration information) is future decided based on the mapping relationship. The decision can be determined based on the available resources in radio network, the service requirement of mission service, and the information received from CN.Then the RAN sends the SDAP configuration information elements to devices, e.g., as per the procedure described in FIG. 39.

Next, embodiments of products related to the communication methods will be described.

FIG. 40 is a structural diagram of a communication apparatus according to one or more embodiments of the present disclosure, the communication apparatus may be the first network function or the second network function cited above. As shown in FIG. 40, the apparatus includes at least one processor 4002, an interface 4004 for communicating with other devices and a memory 4006. Among them, the memory 4006 may be stored with computer execution instructions, and the processor 4002 executes computer execution instructions stored in the memory 4006 to enable the apparatus to execute any of the above communication methods. It should be noted that, the memory 4006 may be included or excluded from the apparatus, depending on actual needs.

An embodiment of the present disclosure provides a communication apparatus, the communication apparatus may include:

a receiving module, configured to receive a packet; and

An embodiment of the present disclosure provides an apparatus including processing circuitry for performing any of the above communication methods.

An embodiment of the present disclosure provides a chip, including an input/output (I/O) interface and a processor, where the processor is configured to call and run a computer program stored in a memory, to enable a device installing with the chip to perform any of the above communication methods.

An embodiment of the present disclosure provides an apparatus, including: one or more processors; and the one or more processors is configured to execute instructions stored in a memory, when the instructions are executed by the one or more processors, any of the above communication methods is performed.

It should be noted that the apparatus in the present disclosure may also be implemented as a device, or one or more component included in a device, such as, a processor or a chip. The device may be user equipment, a terminal, a network device, a network function, a network node, or another network element, which is not limited in the present disclosure.

It should be understood that the processor may be an integrated circuit chip and has a signal processing capability. In an implementation process, steps of the foregoing method embodiments may be completed by using a hardware integrated logic circuit in the processor, or by using instructions in a form of software. The processor may be a general-purpose processor, a central processing unit (CPU) , a graphics processing unit (GPU) , a neural processing unit (NPU) , a system on chip (SoC) or another programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component. The processor may implement or perform the methods, the steps, and the logical block diagrams that are disclosed in the embodiments of the present disclosure. The general-purpose processor may be a microprocessor, or the processor may be any conventional processor or the like. The steps of the methods disclosed with reference to the embodiments of the present disclosure may be directly performed and completed by a hardware decoding processor, or may be performed and completed by using a combination of hardware in the decoding processor and a software module. The software module may be located in a mature storage medium in the art, such as a random-access memory, a flash memory, a read-only memory, a programmable read-only memory, an electrically erasable programmable memory, or a register. The storage medium is located in the memory, and the processor reads information in the memory and completes the steps of the foregoing methods in combination with hardware in the processor.

It may be understood that the memory in the embodiments of the present disclosure may be a volatile memory or a non-volatile memory, or may include both a volatile memory and a non-volatile memory. The non-volatile memory may be a read-only memory (Read-Only Memory, ROM) , a programmable read-only memory (Programmable ROM, PROM) , an erasable programmable read-only memory (Erasable PROM, EPROM) , an electrically erasable programmable read-only memory (Electrically EPROM, EEPROM) , or a flash memory. The volatile memory may be a random-access memory (Random Access Memory, RAM) and is used as an external cache. By way of example rather than limitation, many forms of RAMs may be used, and are, for example, a static random access memory (Static RAM, SRAM) , a dynamic random access memory (Dynamic RAM, DRAM) , a synchronous dynamic random access memory (Synchronous DRAM, SDRAM) , a double data rate synchronous dynamic random access memory (Double Data Rate SDRAM, DDR SDRAM) , an enhanced synchronous dynamic random access memory (Enhanced SDRAM, ESDRAM) , a synchronous link dynamic random access memory (Synchronous link DRAM, SLDRAM) , and a direct rambus random access memory (Direct Rambus RAM, DR RAM) .

It should be noted that the memory in the systems and the methods described in this specification includes but is not limited to these memories and a memory of any other appropriate type.

An embodiment of the present disclosure provides a communication system, including: the network function executing any of the above communication methods.

An embodiment of the present disclosure provides a non-transitory computer-readable medium carrying a program code which, when executed by a computer device, causes the computer device to perform any of the above communication methods.

Optionally, the storage medium may be specifically a memory.

An embodiment of the present disclosure provides a computer program product including computer code for performing any of the above communication methods.

Note that when the request or the response mentioned above includes multiple different contents for indicating multiple different pieces of information, the multiple contents can be indicated separately in multiple request/response messages or together in a request/response message.

Note that the network elements mentioned in the present disclosure are all logical network elements, which can be implemented as individual devices, or can be implemented as chips or modules that could be integrated into a certain device.

Although the present disclosure describes methods and processes with steps in a certain order, one or more steps of the methods and processes may be omitted or altered as appropriate. One or more steps may take place in an order other than that in which they are described, as appropriate.

Note that the expression “at least one of A or B” , as used herein, is interchangeable with the expression “A and/or B” . It refers to a list in which you may select A or B or both A and B. Similarly, “at least one of A, B, or C” , as used herein, is interchangeable with “A and/or B and/or C” or “A, B, and/or C” . It refers to a list in which you may select: A or B or C, or both A and B, or both A and C, or both B and C, or all of A, B and C. The same principle applies for longer lists having a same format.

Although the present disclosure is described, at least in part, in terms of methods, a person of ordinary skill in the art will understand that the present disclosure is also directed to the various components for performing at least some of the aspects and features of the described methods, be it by way of hardware components, software or any combination of the two. Accordingly, the technical solution of the present disclosure may be embodied in the form of a software product. A suitable software product may be stored in a pre-recorded storage device or other similar non-volatile or non-transitory computer readable medium, including DVDs, CD-ROMs, USB flash disk, a removable hard disk, or other storage media, for example. The software product includes instructions tangibly stored thereon that enable a processing device (e.g., a personal computer, a server, or a network device) to execute examples of the methods disclosed herein. The machine-executable instructions may be in the form of code sequences, configuration information, or other data, which, when executed, cause a machine (e.g., a processor or other processing device) to perform steps in a method according to examples of the present disclosure.

The present disclosure may be embodied in other specific forms without departing from the subject matter of the claims. The described example embodiments are to be considered in all respects as being only illustrative and not restrictive. Selected features from one or more of the above-described embodiments may be combined to create alternative embodiments not explicitly described, features suitable for such combinations being understood within the scope of this disclosure.

All values and sub-ranges within disclosed ranges are also disclosed. Also, although the systems, devices and processes disclosed and shown herein may include a specific number of elements/components, the systems, devices and assemblies could be modified to include additional or fewer of such elements/components. For example, although any of the elements/components disclosed may be referenced as being singular, the embodiments disclosed herein could be modified to include a plurality of such elements/components. The subject matter described herein intends to cover and embrace all suitable changes in technology.

Although embodiments have been described above with reference to the accompanying drawings, those of skill in the art will appreciate that variations and modifications may be made without departing from the scope thereof as defined by the appended claims.

Please note that the different examples may be implemented separately or combined. Although a combination of features is shown in the illustrated embodiments, not all of them need to be combined to realize the benefits of various examples of the present disclosure. In other words, a system or method designed according to an embodiment of the present disclosure will not necessarily include all of the features shown in any one of the figures or all of the portions schematically shown in the figures. Moreover, selected features of one example embodiment may be combined with selected features of other example embodiments.

Although this disclosure has been described with reference to illustrative embodiments, the description is not intended to be construed in a limiting sense. Various modifications and combinations of the illustrative embodiments, as well as other examples of the disclosure, will be apparent to persons skilled in the art upon reference to the description. It is therefore intended that the appended claims encompass any such modifications or embodiments.

Claims

A communication method, comprising:

receiving, by a first service data adaptation protocol (SDAP) entity, a packet; and

transmitting, by the first SDAP entity, a SDAP packet generated by the first SDAP entity based on the packet, wherein the SDAP packet includes information on a mission session, the mission session is to provide a mission service to a mission customer, and the mission service is a service for both PDU connectivity and data processing.
The method according to claim 1, wherein the mission session comprises one or more data sessions, each data session comprises an association terminates at a computing block (CB) entity executing at least one CB of a mission, the mission comprises one or more CBs and each CB corresponds to a computational step toward achieving the mission service.
The method according to claim 2, wherein the data processing comprises the executing the at least one CB of the mission.
The method according to claim 2 or 3, wherein the CB entity is deployed in one of: a device, a radio access network (RAN) , a core network (CN) , and a data network (DN) .
The method according to any one of claims 2-4, wherein the computational step toward achieving the mission service comprises one or more of: artificial intelligence (AI) training, AI inference, data pre-processing, data privacy protection, data cleaning, data collection, data analytics, sensing, data sanitization, data management, data normalization, data aggregation, data splitting, useless data filtering, data formatting, data adaptation, data feature engineering, data compression, data embedding, data representation learning, or data feature extraction.
The method according to any one of claims 3-5, wherein the information on a mission session is included in a packet header of the SDAP packet or a payload of the SDAP packet.
The method according to any one of claims 3-6, wherein the information on a mission session includes one or more of: a mission session identifier (ID) identifying a mission session, a data session ID identifying a data session, assistance information used for assisting in distinguishing a data session or distinguishing a CB, a quality of service (QoS) flow identifier (QFI) identifying a QoS flow in the mission session, a stream ID identifying a stream frame, a reflective data session indication (RDSI) , or a reflective data session to radio bearer mapping indication (RDDI) , and the RDSI indicates whether a non-access stratum (NAS) is to be informed of an updated of a service data flow (SDF) to data session mapping rule, and the RDDI indicates whether a data session to radio bearer mapping rule is to be updated.
The method according to any one of claims 3-7, wherein the first SDAP entity corresponds to a data session and is dedicated for a data session.
The method according to claim 8, wherein the first SDAP entity is used for mapping one or more packets of the data session to one or more radio bearers, the one or more packets include the packet.
The method according to claim 9, wherein a mapping relationship between the data session and the one or more radio bearers comprises a one-to-one mapping relationship or a one-to-multiple mapping relationship,

the one-to-one mapping relationship indicates that the data session is mapped to one radio bearer, and the one-to-multiple mapping relationship indicates that the data session is mapped to multiple radio bearers.
The method according to claim 9 or 10, wherein the information on a mission session includes either or both of a RDSI and a RDDI.
The method according to claim 8, wherein the data session includes one or more QoS flows, and the first SDAP entity is used for mapping one or more packets of the one or more QoS flows of the data session to one or more radio bearers, the one or more packets include the packet.
The method according to claim 12, wherein a mapping relationship between the one or more QoS flows of the data session and the one or more radio bearers comprises one or more of: a one-to-one mapping relationship or a multiple-to-one mapping relationship;

the one-to-one mapping relationship indicates that one QoS flow of the data session is mapped to one radio bearer, and the multiple-to-one mapping relationship indicates that multiple QoS flows of the data session are mapped to one radio bearer.
The method according to claim 12 or 13, wherein the information on a mission session includes a QFI, wherein the QFI indicates a QoS flow associated with the SDAP packet.
The method according to claim 8, wherein the data session includes one or more QUIC streams, and the first SDAP entity is used for mapping one or more packets of the one or more QUIC streams of the data session to one or more radio bearers, the one or more packets include the packet.
The method according to claim 15, wherein a mapping relationship between the one or more QUIC streams of the data session and the one or more radio bearers comprises a one-to-one mapping relationship or a multiple-to-one mapping relationship;

the one-to-one mapping relationship indicates that one QUIC stream of the data session is mapped to one radio bearer, and the multiple-to-one mapping relationship indicates that multiple QUIC streams of the data session are mapped to one radio bearer.
The method according to claim 15 or 16, wherein the information on a mission session includes a stream ID, and the stream ID indicates a stream frame for the data session associated with the SDAP packet.
The method according to any one of claims 3-7, wherein the first SDAP entity corresponds to a mission session, and the first SDAP entity is dedicated for the mission session and is shared by one or more data sessions of the mission session.
The method according to claim 18, wherein

the first SDAP entity is used for mapping one or more packets of the mission session to one or more radio bearers, the one or more packets include the packet.
The method according to claim 19, wherein a mapping relationship between the mission session and the one or more radio bearers comprises a one-to-one mapping relationship or a one-to-multiple mapping relationship;

the one-to-one mapping relationship indicates that the mission session is mapped to one radio bearer, and the one-to-multiple mapping relationship indicates that the mission session are mapped to multiple radio bearers.
The method according to claim 20, wherein the mapping relationship between the mission session and the one or more radio bearers further comprises a mapping relationship between one or more data sessions of the mission session and the one or more radio bearers;

the mapping relationship between the one or more data sessions of the mission session and the one or more radio bearers comprises one or more of: a one-to-one mapping relationship, a one-to-multiple mapping relationship, or a multiple-to-one mapping relationship;

the one-to-one mapping relationship indicates that one data session of the mission session is mapped to one radio bearer, the one-to-multiple mapping relationship indicates that one data session of the mission session are mapped to multiple radio bearers, and the multiple-to-one mapping relationship indicates that multiple data sessions of the mission session are mapped to one radio bearer.
The method according to any one of claims 19-21, wherein the information on a mission session includes either or both of a data session ID and assistance information, the data session ID is used to identify a data session, and the assistance information is used to assist in distinguishing the data session or distinguishing a CB.
The method according to claim 22, wherein the information on a mission session includes either or both of a RDSI and a RDDI.
The method according to claim 18, wherein each data session of the mission session includes at least one QoS flow, and the first SDAP entity is used for mapping one or more packets of one or more QoS flows of the one or more data sessions of the mission session to one or more radio bearers, the one or more packets include the packet.
The method according to claim 24, wherein a mapping relationship between the one or more QoS flows of the one or more data sessions of the mission session and the one or more radio bearers comprises one or more of: a one-to-one mapping relationship, or a multiple-to-one mapping relationship;

the one-to-one mapping relationship indicates that a packet of one QoS flow of the one or more data sessions of the mission session is mapped to one radio bearer, and the multiple-to-one mapping relationship indicates that packets of multiple QoS flows of the one or more data sessions of the mission session are mapped to one radio bearer.
The method according to claim 24 or 25, wherein the information on a mission session includes a QFI and either or both of a data session ID and assistance information, the QFI indicates a QoS flow associated with the SDAP packet, the data session ID is used to identify a data session, and the assistance information is used to assist in distinguishing the data session or distinguishing a CB.
The method according to claim 24 or 25, wherein the information on a mission session includes a QFI, and the QFI indicates a QoS flow associated with the SDAP packet, and the QFI includes either or both of: a field indicating a data session ID used to identify a data session, and a field indicating assistance information used to assist in distinguishing a data session or distinguishing a CB.
The method according to claim 18, wherein the mission session includes one or more QUIC streams, and the first SDAP entity is used for mapping one or more packets of the one or more QUIC streams of the mission session to one or more radio bearers, the one or more packets include the packet.
The method according to claim 28, wherein a mapping relationship between the one or more QUIC streams of the mission session and the one or more radio bearers comprises a one-to-one mapping relationship or a multiple-to-one mapping relationship;

the one-to-one mapping relationship indicates that a packet of one QUIC stream of the mission session is mapped to one radio bearer, and the multiple-to-one mapping relationship indicates that packets of multiple QUIC streams of the mission session are mapped to one radio bearer.
The method according to claim 28 or 29, wherein the information on a mission session includes a stream ID and either or both of a data session ID and assistance information, wherein the stream ID is used to identify a stream frame for the mission session associated with the SDAP packet, the data session ID is used to identify a data session, and the assistance information is used to assist in distinguishing a data session or distinguishing a CB.
The method according to claim 28 or 29, wherein the information on a mission session includes a stream ID, and the stream ID indicates a stream frame for the mission session associated with the SDAP packet, and the stream ID includes either or both of: a field indicating a data session ID used to identify a data session, and a field indicating assistance information used to assist in distinguishing a data session or distinguishing a CB.
The method according to any one of claims 3-7, wherein the first SDAP entity corresponds to a network entity, the first SDAP entity is dedicated for the network entity and is shared by one or more mission sessions of the network entity, and the one or more mission sessions include the mission session.
The method according to claim 32, wherein the first SDAP entity is used for mapping one or more packets of the network entity to one or more radio bearers, the one or more packets include the packet.
The method according to claim 33, wherein a mapping relationship between the network entity and the one or more radio bearers comprises a one-to-one mapping relationship or a one-to-multiple mapping relationship;

the one-to-one mapping relationship indicates that one or more packets of one network entity are mapped to one radio bearer, and the one-to-multiple mapping relationship indicates that packets of one network entity are mapped to multiple radio bearers.
The method according to claim 34, wherein the mapping relationship between the network entity and the one or more radio bearers further comprises a mapping relationship between one or more mission sessions of the network entity and the one or more radio bearers;

the mapping relationship between the one or more mission sessions of the network entity and the one or more radio bearers comprises one or more of: a one-to-one mapping relationship, a one-to-multiple mapping relationship, or a multiple-to-one mapping relationship;

the one-to-one mapping relationship indicates that one mission session of the network entity is mapped to one radio bearer, the one-to-multiple mapping relationship indicates one mission session of the network entity is mapped to multiple radio bearers, and the multiple-to-one mapping relationship indicates that multiple mission sessions of the network entity are mapped to one radio bearer.
The method according to claim 35, wherein the mapping relationship between the one or more mission sessions of the network entity and the one or more radio bearers further comprises a mapping relationship between one or more data sessions of the one or more mission sessions of the network entity and the one or more radio bearers;

the mapping relationship between the one or more data sessions of the one or more mission sessions of the network entity and the one or more radio bearers comprises one or more of: a one-to-one mapping relationship, a one-to-multiple mapping relationship, or a multiple-to-one mapping relationship;

the one-to-one mapping relationship indicates that one data session of the one or more mission sessions of the network entity is mapped to one radio bearer, the one-to-multiple mapping relationship indicates that one data session of the one or more mission sessions of the network entity is mapped to multiple radio bearers, and the multiple-to-one mapping relationship indicates that multiple data sessions of the one or more mission sessions of the network entity are mapped to one radio bearer.
The method according to any one of claims 33-36, wherein the information on a mission session includes one or more of: a mission session ID, a data session ID, or assistance information;

the mission session ID is used to identify a mission session, the data session ID is used to identify a data session included in the mission session, and the assistance information is used to assist in distinguishing the data session or distinguishing a CB.
The method according to claim 37, wherein the information on a mission session includes either or both of a RDSI and a RDDI.
The method according to claim 32, wherein each data session of a mission session of a network entity includes at least one QoS flow, and the first SDAP entity is used for mapping one or more packets of one or more QoS flows to one or more radio bearers, the one or more packets include the packet.
The method according to claim 39, wherein a mapping relationship between the one or more QoS flows and the one or more radio bearers comprises one or more of: a one-to-one mapping relationship, or a multiple-to-one mapping relationship;

the one-to-one mapping relationship indicates that one QoS flow is mapped to one radio bearer, and the multiple-to-one mapping relationship indicates that multiple QoS flows are mapped to one radio bearer.
The method according to claim 39 or 40, wherein the information on a mission session includes a QFI and one or more of: a mission session ID, a data session ID or assistance information, wherein the QFI indicates a QoS flow associated with the SDAP packet, the mission session ID is used to identify a mission session, the data session ID is used to identify a data session, and the assistance information is used to assist in distinguishing the data session or distinguishing a CB.
The method according to claim 39 or 40, wherein the information on a mission session includes a QFI, and the QFI indicates a QoS flow associated with the SDAP packet, and the QFI includes one or more of: a field indicating mission session ID used to identify a mission session, a field indicating a data session ID used to identify a data session, or a field indicating assistance information used to assist in distinguishing a data session or distinguishing a CB.
The method according to claim 32, wherein the one or more mission sessions of the network entity includes one or more QUIC streams, and the first SDAP entity is used for mapping one or more packets of the one or more QUIC streams of the network entity to one or more radio bearers, the one or more packets include the packet.
The method according to claim 43, wherein a mapping relationship between the one or more QUIC streams of the network entity and the one or more radio bearers comprises a one-to-one mapping relationship or a multiple-to-one mapping relationship;

the one-to-one mapping relationship indicates that one QUIC stream of the network entity is mapped to one radio bearer, and the multiple-to-one mapping relationship indicates that multiple QUIC streams of the network entity are mapped to one radio bearer.
The method according to claim 43 or 44, wherein the information on a mission session includes a stream ID and one or more of: a mission session ID, a data session ID or assistance information, wherein the stream ID is used to identify a stream frame for the network entity associated with the SDAP packet, the mission session ID is used to identify a mission session, the data session ID is used to identify a data session, and the assistance information is used to assist in distinguishing a data session or distinguishing a CB.
The method according to claim 43 or 44, wherein the information on a mission session includes a stream ID, wherein the stream ID indicates a stream frame for the network entity associated with the SDAP packet, and the stream ID includes one or more of: a field indicating mission session ID used to identify a mission session, a field indicating a data session ID used to identify a data session, or a field indicating assistance information used to assist in distinguishing a data session or distinguishing a CB.
The method according to any one of claims 32-46, wherein the network entity is one of a device, a RAN node, a CB entity of a RAN, or a gateway (GW) entity.
The method according to any one of claims 9-10, 12-13, 15-16, 19-21, 24-25, 28-29, 33-36, 39-40, 43-44, wherein the one or more radio bearers comprise one or more data radio bearers, one or more mission data radio bearers, or one or more sidelink radio bearers, wherein the one or more data radio bearers are used for the PDU connectivity, the one or more mission data radio bearers are used for the mission service, and the one or more sidelink radio bearers are used for a sidelink service.
The method according to any one of claims 1-48, wherein the first SDAP entity is deployed in an apparatus, and the apparatus is a device side apparatus or a RAN node side apparatus.
The method according to claim 49, further comprising:

receiving, by the device side apparatus, a first message from a RAN node side apparatus, wherein the first message includes configuration information, and the configuration information is used to establish, reconfigure, resume or release one or more SDAP entities including the first SDAP entity; and

establishing, reconfiguring, resuming or releasing, by the device side apparatus, the one or more SDAP entities including the first SDAP entity according to the first message.
The method according to claim 50, wherein the configuration information indicates one or more of: one or more mission sessions, one or more data sessions, one or more QoS flows, mapping information, or SDAP entity granularity information; and

the SDAP entity granularity information indicates that the first SDAP entity is an SDAP entity corresponding to a data session and dedicated for the data session, an SDAP entity corresponding to a mission session and dedicated for the mission session, or an SDAP entity corresponding to a network entity and dedicated for the network entity;

the mapping information includes one or more of:

a mapping relationship between the one or more mission sessions and the one or more data sessions,

a mapping relationship between the one or more data sessions and the one or more QoS flows, or

a mapping relationship among the one or more mission sessions, the one or more data sessions and the one or more QoS flows.
The method according to claim 51, wherein:

the one or more mission sessions are identified by one or more mission session IDs or a session group ID;

the one or more data sessions are identified by one or more data session IDs;

the one or more QoS flows are identified by one or more QFIs.
The method according to claim 52, wherein the first message includes a radio bearer ID identifying a radio bearer and the one or more mission session IDs or the session group ID identifying the one or more mission sessions, and

the one or more mission sessions are to be mapped to the radio bearer.
The method according to claim 52, wherein the first message includes a radio bearer ID identifying a radio bearer and the one or more data session IDs identifying the one or more data sessions, and

the one or more data sessions are to be mapped to the radio bearer.
The method according to claim 52, wherein the first message includes a radio bearer ID identifying a radio bearer and the one or more QFIs identifying the one or more QoS flows, and

the one or more QoS flows are to be mapped to the radio bearer.
The method according to claim 52, wherein the mapping relationship between the one or more mission sessions and the one or more data sessions indicates parts of the one or more data sessions identified by the one or more data session IDs belongs to a mission session of the one or more mission sessions identified by the one or more mission session IDs or the session group ID.
The method according to claim 52, wherein the mapping relationship between the one or more data sessions and the one or more QoS flows indicates parts of the one or more QoS flows identified by the one or more QFIs belongs to a data session of the one or more data sessions identified by the one or more data session IDs.
The method according to claim 52, wherein the mapping relationship among the one or more mission sessions, the one or more data sessions and the one or more QoS flows indicates: parts of the one or more QoS flows identified by the one or more QFIs belongs to a data session of the one or more data sessions identified by the one or more data session IDs, and parts of the one or more data sessions identified by the one or more data session IDs belongs to a mission session of the one or more mission sessions identified by the one or more mission session IDs or a session group ID.
The method according to claim 58, wherein the first SDAP entity corresponds to a data session and is dedicated for a data session, the configuration information includes a mission session ID, a data session ID, and one or more QFIs, and the mapping information is indicated by a sequence structure of the mission session ID, the data session ID, and the one or more QFIs.
The method according to claim 59, wherein the configuration information indicates the SDAP entity granularity information, and

the SDAP entity granularity information is indicated by an indication included in the configuration information; or

the SDAP entity granularity information is indicated by one data session ID listed in the configuration information.
The method according to claim 58, wherein the first SDAP entity corresponds to a mission session, and the first SDAP entity is dedicated for the mission session and is shared by one or more data sessions of the mission session, the configuration information includes: a mission session ID, one or more data session IDs, and one or more QFIs, and the mapping information is indicated by a sequence structure of the mission session ID, the one or more data session IDs, and the one or more QFIs.
The method according to claim 61, wherein the configuration information indicates the SDAP entity granularity information, and

the SDAP entity granularity information is indicated by an indication included in the configuration information; or

the SDAP entity granularity information is indicated by one mission session ID listed in the configuration information.
The method according to claim 58, wherein the first SDAP entity corresponds to a network entity, the first SDAP entity is dedicated for the network entity and is shared by one or more mission sessions of the network entity, and the one or more mission sessions include the mission session, the configuration information includes: one or more mission session IDs, one or more data session IDs, one or more QFIs, and the mapping information is indicated by a sequence structure of the one or more mission session IDs, the one or more data session IDs, and the one or more QFIs.
The method according to claim 63, wherein the configuration information indicates the SDAP entity granularity information, and

the SDAP entity granularity information is indicated by an indication included in the configuration information; or

the SDAP entity granularity information is indicated by multiple mission session IDs listed in the configuration information.
The method according to any one of claims 60, 62, 64, wherein the indication is a string or a bitmap.
The method according to any one of claims 50-65, wherein the configuration information further includes one or more values of assistance information.
The method according to any one of claims 50-66, wherein the configuration information is determined by the RAN node side apparatus according to a second message from a CN node, and the second message is used by the RAN node side apparatus to determine the configuration information.
The method according to claim 67, wherein the second message indicates one or more of: one or more mission sessions, one or more data sessions, one or more QoS flows, mapping information, or SDAP entity granularity information, and

the SDAP entity granularity information indicates that the first SDAP entity is an SDAP entity corresponding to a data session and dedicated for the data session, an SDAP entity corresponding to a mission session and dedicated for the mission session, or an SDAP entity corresponding to a network entity and dedicated for the network entity,

the mapping information includes one or more of: a mapping relationship between the one or more mission sessions and the one or more data sessions, or a mapping relationship between the one or more data sessions and the one or more QoS flows, or a mapping relationship among the one or more mission sessions, the one or more data sessions and the one or more QoS flows.
The method according to claim 68, wherein:

the one or more mission sessions are identified by one or more mission session IDs or a session group ID;

the one or more data sessions are identified by one or more data session IDs; and

the one or more QoS flows are identified by one or more QFIs.
The method according to claim 68, wherein the mapping relationship between the one or more mission sessions and the one or more data sessions indicates parts of the one or more data sessions identified by the one or more data session IDs belongs to a mission session of the one or more mission sessions identified by the one or more mission session IDs or a session group ID.
The method according to claim 68, wherein the mapping relationship between the one or more data sessions and the one or more QoS flows indicates parts of the one or more QoS flows identified by the one or more QFIs belongs to a data session of the one or more data sessions identified by the one or more data session IDs.
The method according to claim 68, wherein the mapping relationship among the one or more mission sessions, the one or more data sessions and the one or more QoS flows indicates: parts of the one or more QoS flows identified by the one or more QFIs belongs to a data session of the one or more data sessions identified by the one or more data session IDs, and parts of the one or more data sessions identified by the one or more data session IDs belongs to a mission session of the one or more mission sessions identified by the one or more mission session IDs or a session group ID.
The method according to any one of claims 68-72, wherein the second message is used by the RAN node side apparatus to determine one or more of:

a number of radio bearers to be mapped to for a data session or a mission session;

at least one of one or more data sessions, one or more mission sessions, or one or more QoS flows, to be mapped to a radio bearer; or

the SDAP entity granularity information.
The method according to any one of claims 50-73, wherein the receiving, by the device side apparatus, the first message from the RAN node side apparatus comprises:

receiving, by the device side apparatus, the first message from the RAN node side apparatus in a radio bearer setup procedure, a radio bearer reconfiguration procedure, a radio bearer resume procedure, or a radio bearer release procedure.
The method according to claim 49, further comprising:

receiving, by the RAN node side apparatus, a second message from a CN node, wherein the second message is used by the RAN node side apparatus to determine configuration information for the device side apparatus; and

determining, by the RAN node side apparatus, the configuration information for the device side apparatus.
The method according to claim 75, wherein the second message indicates one or more of: one or more mission sessions, one or more data sessions, one or more QoS flows, mapping information, or SDAP entity granularity information, and

the SDAP entity granularity information indicates that the first SDAP entity is an SDAP entity corresponding to a data session and dedicated for the data session, an SDAP entity corresponding to a mission session and dedicated for the mission session, or an SDAP entity corresponding to a network entity and dedicated for the network entity,

the mapping information includes one or more of: a mapping relationship between the one or more mission sessions and the one or more data sessions, or a mapping relationship between the one or more data sessions and the one or more QoS flows, or a mapping relationship among the one or more mission sessions, the one or more data sessions and the one or more QoS flows.
The method according to claim 76, wherein:

the one or more mission sessions are identified by one or more mission session IDs or a session group ID;

the one or more data sessions are identified by one or more data session IDs; and

the one or more QoS flows are identified by one or more QFIs.
The method according to claim 76, wherein the mapping relationship between the one or more mission sessions and the one or more data sessions indicates parts of the one or more data sessions identified by the one or more data session IDs belongs to a mission session of the one or more mission sessions identified by the one or more mission session IDs or a session group ID.
The method according to claim 76, wherein the mapping relationship between the one or more data sessions and the one or more QoS flows indicates parts of the one or more QoS flows identified by the one or more QFIs belongs to a data session of the one or more data sessions identified by the one or more data session IDs.
The method according to claim 76, wherein the mapping relationship among the one or more mission sessions, the one or more data sessions and the one or more QoS flows indicates: parts of the one or more QoS flows identified by the one or more QFIs belongs to a data session of the one or more data sessions identified by the one or more data session IDs, and parts of the one or more data sessions identified by the one or more data session IDs belongs to a mission session of the one or more mission sessions identified by the one or more mission session IDs or a session group ID.
The method according to any one of claims 76-80, wherein the determining the configuration information for the device side apparatus comprises one or more of:

determining a number of radio bearers to be mapped to for a data session or a mission session;

determining at least one of one or more data sessions, one or more mission sessions, or one or more QoS flows, to be mapped to a radio bearer; or

determining the SDAP entity granularity information.
The method according to any one of claims 50, 67, 74-75, wherein the first message or the second message comprises a radio resource control (RRC) message or an X as a service (XaaS) service signaling bearer (XSB) message.
The method according to any one of claims 7, 22, 26-27, 30-31, 37, 41-42, 45-46, 66, wherein a value of the assistance information included in the information or a value of the assistance information included in the configuration information includes at least one of: an action ID identifying an action of data processing, a computing block ID (CBID) identifying a CB, a step ID identifying a step of a procedure, and a mission customer ID identifying a customer of a mission session.
The method according to any one of claims 1-83, wherein the mission service is reduced to a service for PDU connectivity only.
The method according to claim 84, wherein the mission session is reduced to a PDU session to be used for PDU connectivity.
The method according to claim 85, wherein there is no CB entity involved in the mission session, or all CB entities involved in the mission session are dummy CB entities.
The method according to claim 86, wherein there is no data session belonging to the mission session, or all data sessions belong to the mission session are dummy data sessions.
A communication method, comprising:

receiving, by a second service data adaptation protocol (SDAP) entity, a SDAP packet from a first SDAP entity, wherein the SDAP packet includes information on a mission session, the mission session is to provide a mission service to a mission customer, and the mission service is a service for both PDU connectivity and data processing; and

determining, by the second SDAP entity, according to the information on a mission session, which mission session the SDAP packet belongs to.
The method according to claim 88, wherein the mission session comprises one or more data sessions, each data session comprises an association terminates at a computing block (CB) entity executing at least one CB of a mission, the mission comprises one or more CBs and each CB corresponds to a computational step toward achieving the mission service.
The method according to claim 89, wherein the data processing comprises the executing the at least one CB of the mission.
The method according to claim 89 or 90, wherein the CB entity is deployed in one of: a device, a radio access network (RAN) , a core network (CN) , and a data network (DN) .
The method according to any one of claims 89-91, wherein the computational step toward achieving the mission service comprises one or more of: artificial intelligence (AI) training, AI inference, data pre-processing, data privacy protection, data cleaning, data collection, data analytics, sensing, data sanitization, data management, data normalization, data aggregation, data splitting, useless data filtering, data formatting, data adaptation, data feature engineering, data compression, data embedding, data representation learning, or data feature extraction.
The method according to any one of claims 90-92, wherein the information on a mission session is included in a packet header of the SDAP packet or a payload of the SDAP packet.
The method according to any one of claims 90-93, wherein the information on a mission session includes one or more of: a mission session identifier (ID) identifying a mission session, a data session ID identifying a data session, assistance information used for assisting in distinguishing a data session or distinguishing a CB, a quality of service (QoS) flow identifier (QFI) identifying a QoS flow in the mission session, a stream ID identifying a stream frame, a reflective data session indication (RDSI) , or a reflective data session to radio bearer mapping indication (RDDI) , and the RDSI indicates whether a non-access stratum (NAS) is to be informed of an updated of a service data flow (SDF) to data session mapping rule, and the RDDI indicates whether a data session to radio bearer mapping rule is to be updated.
The method according to any one of claims 88-94, wherein the second SDAP entity is deployed in an apparatus, and the apparatus is a device side apparatus or a RAN node side apparatus.
The method according to claim 95, further comprising:

receiving, by the device side apparatus, a first message from a RAN node side apparatus, wherein the first message includes configuration information, and the configuration information is used to establish, reconfigure, resume or release one or more SDAP entities including the second SDAP entity; and

establishing, reconfiguring, resuming or releasing, by the device side apparatus, the SDAP entities including the second SDAP entity according to the first message.
The method according to claim 96, wherein the configuration information indicates one or more of: one or more mission sessions, one or more data sessions, one or more QoS flows, mapping information, or SDAP entity granularity information; and

the SDAP entity granularity information indicates that the second SDAP entity is an SDAP entity corresponding to a data session and dedicated for the data session, an SDAP entity corresponding to a mission session and dedicated for the mission session, or an SDAP entity corresponding to a network entity and dedicated for the network entity;

the mapping information includes one or more of:

a mapping relationship between the one or more mission sessions and the one or more data sessions,

a mapping relationship between the one or more data sessions and the one or more QoS flows, or

a mapping relationship among the one or more mission sessions, the one or more data sessions and the one or more QoS flows.
The method according to claim 97, wherein:

the one or more mission sessions are identified by one or more mission session IDs or a session group ID;

the one or more data sessions are identified by one or more data session IDs;

the one or more QoS flows are identified by one or more QFIs.
The method according to claim 98, wherein the first message includes a radio bearer ID identifying a radio bearer, and the one or more mission session IDs or the session group ID identifying the one or more mission sessions, and

the one or more mission sessions are to be mapped to the radio bearer.
The method according to claim 98, wherein the first message includes a radio bearer ID identifying a radio bearer and the one or more data session IDs identifying the one or more data sessions, and

the one or more data sessions are to be mapped to the radio bearer.
The method according to claim 98, wherein the first message includes a radio bearer ID identifying a radio bearer and the one or more QFIs identifying the one or more QoS flows, and

the one or more QoS flows are to be mapped to the radio bearer.
The method according to claim 98, wherein the mapping relationship between the one or more mission sessions and the one or more data sessions indicates parts of the one or more data sessions identified by the one or more data session IDs belongs to a mission session of the one or more mission sessions identified by the one or more mission session IDs or the session group ID.
The method according to claim 98, wherein the mapping relationship between the one or more data sessions and the one or more QoS flows indicates parts of the one or more QoS flows identified by the one or more QFIs belongs to a data session of the one or more data sessions identified by the one or more data session IDs.
The method according to claim 98, wherein the mapping relationship among the one or more mission sessions, the one or more data sessions and the one or more QoS flows indicates: parts of the one or more QoS flows identified by the one or more QFIs belongs to a data session of the one or more data sessions identified by the one or more data session IDs, and parts of the one or more data sessions identified by the one or more data session IDs belongs to a mission session of the one or more mission sessions identified by the one or more mission session IDs or a session group ID.
The method according to claim 104, wherein the second SDAP entity corresponds to a data session and is dedicated for a data session, the configuration information includes a mission session ID, a data session ID, and one or more QFIs, and the mapping information is indicated by a sequence structure of the mission session ID, the data session ID, and the one or more QFIs.
The method according to claim 105, wherein the configuration information indicates the SDAP entity granularity information, and

the SDAP entity granularity information is indicated by an indication included in the configuration information; or

the SDAP entity granularity information is indicated by one data session ID listed in the configuration information.
The method according to claim 104, wherein the second SDAP entity corresponds to a mission session, and the second SDAP entity is dedicated for the mission session and is shared by one or more data sessions of the mission session, the configuration information includes: a mission session ID, one or more data session IDs, and one or more QFIs, and the mapping information is indicated by a sequence structure of the mission session ID, the one or more data session IDs, and the one or more QFIs.
The method according to claim 107, wherein the configuration information indicates the SDAP entity granularity information, and

the SDAP entity granularity information is indicated by an indication included in the configuration information; or

the SDAP entity granularity information is indicated by one mission session ID listed in the configuration information.
The method according to claim 104, wherein the second SDAP entity corresponds to a network entity, the second SDAP entity is dedicated for the network entity and is shared by one or more mission sessions of the network entity, and the one or more mission sessions include the mission session, the configuration information includes: one or more mission session IDs, one or more data session IDs, one or more QFIs, and the mapping information is indicated by a sequence structure of the one or more mission session IDs, the one or more data session IDs, and the one or more QFIs.
The method according to claim 109, wherein the configuration information indicates the SDAP entity granularity information, and

the SDAP entity granularity information is indicated by an indication included in the configuration information; or

the SDAP entity granularity information is indicated by multiple mission session IDs listed in the configuration information.
The method according to any one of claims 106, 108, 110, wherein the indication is a string or a bitmap.
The method according to any one of claims 96-111, wherein the configuration information further includes one or more values of assistance information.
The method according to any one of claims 96-112, wherein the configuration information is determined by the RAN node side apparatus according to a second message from a CN node, and the second message is used by the RAN node side apparatus to determine the configuration information.
The method according to claim 113, wherein the second message indicates one or more of: one or more mission sessions, one or more data sessions, one or more QoS flows, mapping information, or SDAP entity granularity information, and

the SDAP entity granularity information indicates that the second SDAP entity is an SDAP entity corresponding to a data session and dedicated for the data session, an SDAP entity corresponding to a mission session and dedicated for the mission session, or an SDAP entity corresponding to a network entity and dedicated for the network entity,

the mapping information includes one or more of: a mapping relationship between the one or more mission sessions and the one or more data sessions, or a mapping relationship between the one or more data sessions and the one or more QoS flows, or a mapping relationship among the one or more mission sessions, the one or more data sessions and the one or more QoS flows.
The method according to claim 114, wherein:

the one or more mission sessions are identified by one or more mission session IDs or a session group ID;

the one or more data sessions are identified by one or more data session IDs; and

the one or more QoS flows are identified by one or more QFIs.
The method according to claim 114, wherein the mapping relationship between the one or more mission sessions and the one or more data sessions indicates parts of the one or more data sessions identified by the one or more data session IDs belongs to a mission session of the one or more mission sessions identified by the one or more mission session IDs or a session group ID.
The method according to claim 114, wherein the mapping relationship between the one or more data sessions and the one or more QoS flows indicates parts of the one or more QoS flows identified by the one or more QFIs belongs to a data session of the one or more data sessions identified by the one or more data session IDs.
The method according to claim 114, wherein the mapping relationship among the one or more mission sessions, the one or more data sessions and the one or more QoS flows indicates: parts of the one or more QoS flows identified by the one or more QFIs belongs to a data session of the one or more data sessions identified by the one or more data session IDs, and parts of the one or more data sessions identified by the one or more data session IDs belongs to a mission session of the one or more mission sessions identified by the one or more mission session IDs or a session group ID.
The method according to any one of claims 114-118, wherein the second message is used by the RAN node side apparatus to determine one or more of:

a number of radio bearers to be mapped to for a data session or a mission session;

at least one of one or more data sessions, one or more mission sessions, or one or more QoS flows, to be mapped to a radio bearer; or

the SDAP entity granularity information.
The method according to any one of claims 96-119, wherein the receiving the first message from the RAN node side apparatus comprises:

receiving the first message from the RAN node side apparatus in a radio bearer setup procedure, a radio bearer reconfiguration procedure, a radio bearer resume procedure, or a radio bearer release procedure.
The method according to claim 95, further comprising:

receiving, by the RAN node side apparatus, a second message from a CN node, wherein the second message is used by the RAN node side apparatus to determine configuration information for the device side apparatus; and

determining, by the RAN node side apparatus, the configuration information for the device side apparatus.
The method according to claim 121, wherein the second message indicates one or more of: one or more mission sessions, one or more data sessions, one or more QoS flows, mapping information, or SDAP entity granularity information, and

the SDAP entity granularity information indicates that the second SDAP entity is an SDAP entity corresponding to a data session and dedicated for the data session, an SDAP entity corresponding to a mission session and dedicated for the mission session, or an SDAP entity corresponding to a network entity and dedicated for the network entity,

the mapping information includes one or more of: a mapping relationship between the one or more mission sessions and the one or more data sessions, or a mapping relationship between the one or more data sessions and the one or more QoS flows, or a mapping relationship among the one or more mission sessions, the one or more data sessions and the one or more QoS flows.
The method according to claim 122, wherein:

the one or more mission sessions are identified by one or more mission session IDs or a session group ID;

the one or more data sessions are identified by one or more data session IDs;

the one or more QoS flows are identified by one or more QFIs.
The method according to claim 122, wherein the mapping relationship between the one or more mission sessions and the one or more data sessions indicates parts of the one or more data sessions identified by the one or more data session IDs belongs to a mission session of the one or more mission sessions identified by the one or more mission session IDs or a session group ID.
The method according to claim 122, wherein the mapping relationship between the one or more data sessions and the one or more QoS flows indicates parts of the one or more QoS flows identified by the one or more QFIs belongs to a data session of the one or more data sessions identified by the one or more data session IDs.
The method according to claim 122, wherein the mapping relationship among the one or more mission sessions, the one or more data sessions and the one or more QoS flows indicates: parts of the one or more QoS flows identified by the one or more QFIs belongs to a data session of the one or more data sessions identified by the one or more data session IDs, and parts of the one or more data sessions identified by the one or more data session IDs belongs to a mission session of the one or more mission sessions identified by the one or more mission session IDs or a session group ID.
The method according to any one of claims 122-126, wherein the determining the configuration information for the device side apparatus comprises one or more of:

determining a number of radio bearers to be mapped to for a data session or a mission session;

determining at least one of one or more data sessions, one or more mission sessions, or one or more QoS flows, to be mapped to a radio bearer; or

determining the SDAP entity granularity information.
The method according to any one of claims 96, 113, 120-121, wherein the first message or the second message comprises a radio resource control (RRC) message or an X as a service (XaaS) service signaling bearer (XSB) message.
The method according to claim 112, wherein a value of the assistance information included in the configuration information includes at least one of: an action ID identifying an action of data processing, a CBID identifying a CB, a step ID identifying a step of a procedure, and a mission customer ID identifying a customer of a mission session.
The method according to any one of claims 89-129, wherein the mission service is reduced to a service for PDU connectivity only.
The method according to claim 130, wherein the mission session is reduced to a PDU session to be used for PDU connectivity.
The method according to claim 131, wherein there is no CB entity involved in the mission session, or all CB entities involved in the mission session are dummy CB entities.
The method according to claim 132, wherein there is no data session belonging to the mission session, or all data sessions belong to the mission session are dummy data sessions.
A communication apparatus, comprising:

a receiving module, configured to receive a packet; and

a transmitting module, configured to transmit a service data adaptation protocol (SDAP) packet generated by a first SDAP entity based on the packet, wherein the SDAP packet includes information on a mission session, the mission session is to provide a mission service to a mission customer, and the mission service is a service for both PDU connectivity and data processing.
A communication apparatus, comprising:

a receiving module, configured to receive a service data adaptation protocol (SDAP) packet from a first SDAP entity, wherein the SDAP packet includes information on a mission session, the mission session is to provide a mission service to a mission customer, and the mission service is a service for both PDU connectivity and data processing; and

a determining module, configured to determine, according to the information on a mission session, which mission session the SDAP packet belongs to.
An apparatus comprising processing circuitry for performing the method according to any one of claims 1-133.
A chip, comprising an input/output (I/O) interface and a processor, wherein the processor is configured to call and run a computer program stored in a memory, to enable a device installing with the chip to perform the method according to any one of claims 1-133.
An apparatus, comprising:

one or more processors,

the one or more processors is configured to execute instructions stored in a memory, when the instructions are executed by the one or more processors, the method according to any one of claims 1-87 is performed.
An apparatus, comprising:

one or more processors,

the one or more processors is configured to execute instructions stored in a memory, when the instructions are executed by the one or more processors, the method according to any one of claims 88-133 is performed.
A communication system, comprising: the electronic device according to claim 138 and the electronic device according to claim 139.
A non-transitory computer-readable medium carrying a program code which, when executed by a processor, the method according to any one of claims 1-133 is performed.
A computer program product comprising program code for performing the method according to any one of claims 1-133.