Network slicing device, method and system

Abstract

This disclosure relates to network slicing. A network device (e.g., slice manager) is disclosed to create a network slice for integrated sensing and communication (ISAC). The network device may be further configured to create a plurality of network sub-slices comprising a first network sub-slice for sensing and a second network sub-slice for communication. A network function entity (e.g., call session control function) is configured to manage communication data and / or sensing data through the network slice for ISAC. In this way, a single management mechanism can be provided for managing the ISAC network slice. Further, based on the plurality of different network sub-slices, different traffic (i.e., communication data and sensing data) can be managed respectively, e.g., using different configurations or parameters.

Description

[0001] NETWORK SLICING DEVICE, METHOD AND SYSTEM

[0002] TECHNICAL FIELD

[0003] The present disclosure relates to the field of communications technology. For instance, this disclosure relates to devices, methods, and a system for network slicing.

[0004] BACKGROUND

[0005] In wireless communication networks, electronic devices, such as base stations (BS), user equipment (UE), or the like, wirelessly communicate with each other to send and / or receive data between one another. Sensing is a process of obtaining information about a device’s surroundings and / or itself. Sensing can also be used to obtain information about an target, such as its location, speed, distance, orientation, shape, texture, etc. This information can be used to improve communications in the network (e.g., “sensing-assisted communication”), as well as for other application-specific purposes (e.g., navigation).

[0006] Sensing in communication networks has typically been limited to an active approach, which involves a device receiving and processing a radio frequency (RF) sensing signal. Other sensing approaches, such as passive sensing (e.g., radar) and non-RF sensing (e.g., video imaging and other sensors) can address some limitations of active sensing. However, these other approaches are typically standalone systems implemented separately from the communication network. Alternatively, passive sensing is also being used, e.g., for object detection. FIG. 8 illustrates an example scenario where active sensing, passive sensing, and communication are integrated into one or more communication systems (e.g., mobile communication network, vehicle-to-everything network, integrated terrestrial and satellite mobile communication network, and wireless local area network).

[0007] The benefits of integrating communication and sensing in wireless communications networks have been recognized. It is thus desirable to provide improved system(s) and method(s) for sensing and communication integration in wireless communication networks.

[0008] SUMMARY

[0009] A conventional solution for integrated sensing and communications (ISAC) is to realize the two independent functions of wireless communications and wireless perception (or sensing) in a same system, in order to achieve mutual benefits. On one hand, the communications function and the sensing function can share the same frequency spectrum, and / or the same multiplex hardware, and / or the same signal processing modules, to complete different types of sensing services and to complete communications services. On the other hand, the sensing results can be used to assist access or management of the communications services, in order to improve service quality and communications efficiency.

[0010] However, a problem may arise regarding how to coordinate the sensing and communications services. For instance, it is not clear how to design an end-to-end architecture to enable smooth and efficient management and data exchange for the ISAC. For another example, different network slices have been standardized for different types of traffic. However, currently the ISAC is not defined for network slicing. Moreover, the ISAC may require different traffic requirements for communications data and sensing data respectively, which may not fit for the current network slicing.

[0011] In view of the above-mentioned problems and disadvantages, this disclosure aims to improve integrated sensing and communications for a wireless communications network. For instance, an objective of this disclosure may be to provide an efficient management and data transmission scheme for the ISAC services.

[0012] These and other objectives are achieved by the subject matter of the independent claims. Further implementation forms are apparent from the dependent claims, the description, and the drawings.

[0013] A first aspect of the present disclosure provides a network device configured to create a network slice for integrated sensing and communication (ISAC).

[0014] Optionally, the network slice may be referred to as a network slice instance.

[0015] It is noted that a single network slice is created to support the ISAC service. That is, communication data and sensing data are both transmitted through the created network slice.

[0016] Instead of creating two network slices for a sensing service and a communications service, respectively, using a single network slice for integrated sensing and communication may enhance the management efficiency, and thus save network slice resources.

[0017] In an implementation form of the first aspect, the network device may be further configured to create a plurality of network sub-slices of the network slice. The plurality of network sub-slices may be used for supporting various services, while still ensuring the various services are serviced under a same network slice. In this way, traffic of different types may be transmitted with various configurations using the network sub-slices. This facilitates the various demands of a service that has multiple different traffic types.

[0018] In a further implementation form of the first aspect, the plurality of network sub-slices may comprise a first network sub-slice for sensing and a second network sub-slice for communication.

[0019] In a further implementation form of the first aspect, the network slice may be associated with identification information. The identification information comprises slice / service type information indicative that the network slice is for integrated sensing and communication.

[0020] Optionally, the slice / service type information may comprise a preset value indicating that the network slice is for integrated sensing and communication.

[0021] In a further implementation form of the first aspect, the identification information may comprise a service differentiator field identifying the network slice.

[0022] Optionally, the service differentiator field may comprise an ID value identifying the network slice.

[0023] In a further implementation form of the first aspect, the network device may be further configured to generate a first sub-slice identifier (SSI) and a second SSI. The first SSI is indicative of a first type of traffic belonging to the first network sub-slice. The second SSI is indicative of a second type of traffic belonging to the second network sub-slice.

[0024] Optionally, the first SSI may be a first preset value indicating the first type of traffic belonging to the first network sub-slice (e.g., sensing data). The second SSI may be a second preset value indicating the second type of traffic belonging to the second network sub-slice (e.g., communication data).

[0025] In a further implementation form of the first aspect, the first SSI and the second SSI may be embedded in the service differentiator field.

[0026] In a further implementation form of the first aspect, the first SSI and the second SSI may be indicated by virtual local area network (VLAN) tagging.

[0027] A second aspect of the present disclosure provides a network function entity configured to manage communication data and / or sensing data through a network slice for ISAC. The network slice is created by the network device of the first aspect. The network function entity is used to manage data transmitted through the network slice.

[0028] In an implementation form of the second aspect, the network function entity may be further configured to: differentiate sensing data of different types; and / or differentiate communication data of different types.

[0029] In a further implementation form of the second aspect, the network function entity may be further configured to: collect sensing data from radio access network; and estimate a user equipment (UE) location based on the collected sensing data.

[0030] In a further implementation form of the second aspect, the network function entity may be further configured to: collect sensing data of one or more base stations, optionally from an access and mobility management function; and construct an environmental mapping based on the collected sensing data.

[0031] In a further implementation form of the second aspect, the network function entity may be further configured to perform one or more of: objection detection;

[0032] 3D measurement; providing sensing data to one or more network functions; and providing broadcast sensing assistance to one or more UEs.

[0033] In a further implementation form of the second aspect, the network function entity may be at least a part of a core network device.

[0034] In a further implementation form of the second aspect, the network function entity may be at least a part of a device for an edge network or a radio access network.

[0035] A third aspect of the present disclosure provides a system comprising at least one network device according to the first aspect or any implementation form thereof, and at least one network function entity of the second aspect or any implementation form thereof. A fourth aspect of the present disclosure provides a method comprising creating, by a network device, a network slice for I SAC.

[0036] The method of the fourth aspect may share the same optional features and advantages of the network device of the first aspect.

[0037] A fifth aspect of the present disclosure provides a method comprising managing, by a network function entity, communication data and / or sensing data through a network slice for ISAC.

[0038] The method of the fifth aspect may share the same optional features and advantages of the network function entity of the second aspect.

[0039] A sixth aspect of the present disclosure provides a computer program comprising instructions which, when the program is executed by a computer, cause the computer to carry out the method according to the fourth aspect or any implementation form thereof.

[0040] A seventh aspect of the present disclosure provides a computer-readable medium comprising instructions which, when executed by a computer, cause the computer to carry out the method according to the fourth aspect or any implementation form thereof.

[0041] An eighth aspect of the present disclosure provides a chipset comprising instructions which, when executed by the chipset, cause the chipset to carry out the method according to the fourth aspect or any implementation form thereof.

[0042] A ninth aspect of the present disclosure provides a computer program comprising instructions which, when the program is executed by a computer, cause the computer to carry out the method according to the fifth aspect or any implementation form thereof.

[0043] A tenth aspect of the present disclosure provides a computer-readable medium comprising instructions which, when executed by a computer, cause the computer to carry out the method according to the fifth aspect or any implementation form thereof.

[0044] An eleventh aspect of the present disclosure provides a chipset comprising instructions which, when executed by the chipset, cause the chipset to carry out the method according to the fifth aspect or any implementation form thereof. It has to be noted that all devices, entities, elements, units, and means described in the present disclosure could be implemented in software or hardware elements or any kind of combination thereof. All steps that are performed by the various entities described in the present application as well as the functionalities described to be performed by the various entities are intended to mean that the respective entity is adapted to or configured to perform the respective steps and functionalities. Even if, in the following description, a specific functionality or step to be performed by external entities is not reflected in the description of a specific detailed element of that entity, which performs that specific step or functionality, it should be clear for a skilled person that these methods and functionalities can be implemented in respective software or hardware elements, or any kind of combination thereof.

[0045] BRIEF DESCRIPTION OF DRAWINGS

[0046] The above-described aspects and implementation forms will be explained in the following description in relation to the enclosed drawings, in which

[0047] FIG. 1 shows a network device 100 of this disclosure;

[0048] FIG. 2A shows an example of identification information 200 for identifying a network slice;

[0049] FIG. 2B shows an example of carrying sub-slice identifier;

[0050] FIG. 3A, 3B show examples of a network function entity of this disclosure;

[0051] FIG. 4 shows an example of end-to-end management of an ISAC network slice;

[0052] FIG. 5 shows a diagram of a method of this disclosure;

[0053] FIG. 6 shows a diagram of a further method of this disclosure;

[0054] FIG. 7 shows an application scenario of this disclosure; and

[0055] FIG. 8 shows an example of integrated sensing and communication.

[0056] DETAILED DESCRIPTION OF EMBODIMENTS

[0057] In FIGs. 1-7 below, corresponding elements may share the same features and function likewise. FIG. 1 shows a network device 100 of this disclosure. The network device 100 may be for a wireless (e.g., mobile) communication system. The wireless communication system may comprise at least one radio access network (RAN) and at least one core network (CN). Optionally, the wireless communication system may further comprise at least one one or more of an edge network, a transport network (TN), and a cloud network.

[0058] The network device 100 according to this disclosure is configured to create a single network slice 110 for ISAC. ISAC traffic (i.e., communication data and sensing data) are transmitted through the single network slice. In this way, an improved end-to-end management of ISAC traffic along the entire communication system architecture may be provided. The single network slice may cover the entire end-to-end architecture (e.g., from the RAN to the cloud network) according to functional split and / or service-end point requirements.

[0059] For instance, the network device may be referred to as a network slice management function (NSMF) or a network slice manager. In general, the network device may be any entity configured to provide management and orchestration (MANO) of network slices, e.g., a network function virtualization MANO (NFV MANO).

[0060] Optionally, the network device 110 may be further configured to create a plurality of network sub-slices of the network slice. In this way, the ISAC traffic may be treated differently based on the various network sub-slices (if necessary). For this purpose, the plurality of network sub-slices may comprise a first network sub-slice for sensing and a second network sub-slice for communication.

[0061] FIG. 2A shows an example of identification information 200 for identifying a network slice. The identification information 200 may be generated by the network device 100 for identifying the single network slice 110 for ISAC. For instance, the identification information may be a NAS (Non-access stratum) Information Element (IE) called “Single Network Slice Selection Assistance Information” (S- NSSAI). The identification information 200 may comprise slice / service type (SST) information (or field) 210 indicating that the type of the single network slice is ISAC. For instance, the SST 210 may be assigned with a dedicated value associated with ISAC service. Further, the identification information 200 may comprise a service differentiator (SD) field 220 identifying the single network slice 110.

[0062] The network device 100 may be configured to generate a first sub-slice identifier (SSI) and a second SSI. The first SSI is indicative of a first type of traffic belonging to the first network sub-slice (i.e., for sensing), and the second SSI is indicative of a second type of traffic belonging to the second network sub-slice (i.e., for communication). In this way, an extra level or refinement can be achieved in order to distinguish traffic of two types that belong to the same ISAC network slice. It is noted that the SSI may be replaced with any other indication information that could be used to indicate different types of traffic.

[0063] Optionally, the first SSI and the second SSI may be carried (indicated) in the identification information 200 of the network slice 110. For instance, the first SSI and the second SSI may be embedded in the service differentiator field 220 as an optional sub-field 221. Alternatively, the identification information 200 may comprise a further field (in addition to the SST 210 and SD 220) for indicating the first SSI and the second SSI (not shown in FIG. 2A).

[0064] FIG. 2B shows an alternative way of carrying SSI. As illustrated in FIG. 2B, the first SSI and the second SSI may be identified using MPLS protocol. For instance, the first SSI and the second SSI may be indicated through VLAN tagging, e.g., indicated through the TPID field.

[0065] The following Table 1 gives an example of definitions of a network slice for ISAC.

[0066] Table 1

[0067] Optionally, the network device 100 may be configured to instantiate a network slice 110 for ISAC with various configurations (e.g., QoS, latency, bandwidth, etc.) according to one or more of the different requirements:

[0068] Area / coverage capacity requirement (e.g., 3D mapping capacity);

[0069] Sensing requirements;

[0070] Charging requirement;

[0071] Degree of isolation requirement;

[0072] End-to-end latency requirement;

[0073] Mobility requirement;

[0074] Priority requirement;

[0075] Service availability requirement; and

[0076] Service reliability requirement.

[0077] A protocol stack of a communication system (e.g., 5G, 6G) may be adapted to support the sub-slices. For instance, QoS and slice selection for a Protocol Data Unit (PDU) session may be applied across Control and User Plane functions. Coordination of communication and sensing sub-slice capabilities require IP transport network functionalities with support from CSCF and other Control Plane functions (e.g., Network Function Repository Function). When a GTP-X encapsulates user packets from a RAN or User Plane Function (UPF) with sub-slice information (comprised in the network slice identification information 200) traverse a network domain (edge, TN, CN, ..), the network active components of the IP transport underlay may inspect the slice information and handle the sub-slice traffic steering requirements.

[0078] FIG. 3 A and 3B show a network function entity of this disclosure. The network function entity is configured to manage communication data and / or sensing data through a network slice for integrated sensing and communication. The network function entity may be centrally located in a communication system, or located in a distributed manner in the communication system.

[0079] FIG. 3 A shows a network function entity 310 that is centrally located in the core network of the communication system. That is, the network function entity 310 may be at least a part of a core network device. FIG. 3B shows network function entities 320, 330 that are distributed in the RAN and the edge network, respectively. That is, a network function entity of this disclosure may be at least a part of a device for edge network or RAN.

[0080] Each network function entity 310, 320, 330 may be a Call Session Control Function (CSCF) of a corresponding domain that is responsible for managing ISAC services for a UE, a base station, or an application within or attached to the core network, respectively.

[0081] Optionally, the CSCF may be adapted to: perform 3D environmental mapping; perform object detection, 3D measurements; provide sensing data (exposure) to other NFs (e.g., the LMF, AMF, gNB); provide sensing measurements to third-party consumers; acquisition of downlink sensing data; acquisition of uplink sensing data; communication and Sensing data coordination (transport provisioning); provide broadcast sensing assistance to UEs; assist ISAC slicing.

[0082] For instance, the CSCF may be configured to differentiate the sensing data and / or the communication data into different types. For example, the sensing data may be categorized into radar signal, light detection and ranging (e.g., LIDAR), and so on. The communication data may be categorized into data of various QoS, throughput, delay requirements.

[0083] Optioanlly, for target positioning, the CSCF may be configured to collect sensing data of a UE from a radio access network; and estimate the UE location based on the collected sensing data.

[0084] Optionally, for environment mapping, the CSCF may be configured to collect sensing data of one or more base stations (optionally from an access and mobility management function); and construct an environmental mapping based on the collected sensing data.

[0085] The following Table 2 gives some examples of service descriptors that is supported by the CSCF.

[0086] Table 2

[0087] In this way, beam management can be enhanced. The CSCF can exploit C-RAN capabilities to precisely estimate the UE (3D) position. This information can assist base stations in improving beam selection and management.

[0088] Further, CSCF may assist in environmental image construction. For instance, an Authentication Management Function (AMF) can redirect sensing data from multiple base stations to the CSCF for the definition of a high-resolution scenario map. This information is useful for traffic management operations in both line-of-sight (LOS) and non-line-of-sight (NLOS) scenarios. Further, the accuracy of localization and tracking may be improved. For instance, a Location Management Function (LMF) may require sensing information from the CSCF to compute advanced positioning techniques. Due to the usage of high frequencies, extremely high resolution may be reached, making sensing a suitable candidate for positioning. This is particularly helpful for indoor positioning and Vehicle-to-Everything (V2X) applications.

[0089] In general, FIG. 3A and FIG. 3B shows two possible types of an edge-orchestrated network: centralized (e.g., in FIG. 3A) or distributed (e.g. in FIG. 3B). Centralized edge orchestration refers to that all the orchestration functions are performed by a central entity 310, e.g., a central edge orchestrator. Distributed edge orchestration consists of multiple edge orchestrators (320, 330) at each local edge site in the network. Optionally, the multiple edge orchestrators (320, 330) may be coordinated by a central edge orchestrator (not shown in FIG. 3B). Each local edge orchestration 320, 330 is responsible for managing resources and networking within each edge site and handling requests from the central orchestrator. Optionally, the central edge orchestrator 310 may be responsible for monitoring, provisioning, updating, and / or managing the local edge orchestrators. That is, the approaches in FIG. 3A and FIG. 3B may be combined.

[0090] The goal of edge orchestration in a network is a more intelligent network in which real-time network events, traffic, or other dynamic requests can be handled automatically at the edge of the network. This facilitates the efficient deployment of resources and enables near-instantaneous provisioning of network services. It can also help reallocate network resources across multiple devices within the network.

[0091] FIG. 4 shows an example of end-to-end management of an ISAC network slice.

[0092] The first ISAC network slice on the top of FIG. 4 shows an end-to-end path from an access network (AN) to a core network (CN). The first ISAC network slice may correspond to a PDU session and may be formed by multiple network slice subnet instances (NSSI) of each subnet (e.g., AN, edge network, transport network (TN), and CN). According to this disclosure, the first ISAC network slice comprises a first network sub-slice for sensing (also referred to as a sensing network sub-slice, or sensing sub-slice) and a second network sub-slice for communication (also referred to as a communication network subslice, or communication sub-slice). The first network sub-slice and the second network sub-slice may be associated with a data network (e.g., the DN 4 in FIG. 4) that provides sensing and communication services.

[0093] The second ISAC network slice in the middle of FIG. 4 shows different end-to-end paths for sensing and communication. For instance, similar to the first ISAC network slice, the second ISAC network slice also comprises a first network sub-slice for sensing and a second network sub-slice for communication. In this example, the first network sub-slice and the second network sub-slice may cover different paths: the first network sub-slice may be configured to provide sensing data from the AN to the edge network; while the second network sub-slice may be configured to provide communication data from the AN to the TN. In this way, the flexibility in delivering various ISAC traffic may be enhanced.

[0094] The third ISAC network slice at the bottom of FIG. 4 shows other different end-to-end paths for sensing and communication, which is similar to the second ISAC network slice.

[0095] It is noted that multiple ISAC slices may be combined to deliver service data. For instance, as shown in FIG. 4, the sensing sub-slice of the second ISAC network slice and the communication sub-slice of the third ISAC network slice are both associated with a data network (e.g., DN 2) that jointly provides sensing and communication service. In contrast, the sensing sub-slice of the third ISAC network slice is associated with a data network (e.g., DN1) that only provides sensing service, and the communication sub-slice of the second ISAC network slice is associated with a data network (e.g., DN3) that only provides communication service.

[0096] For providing end-to-end management of network slicing for ISAC, the network device 100 of FIG. 1 may be configured to map S-NSSAI and SSI to a transport service of a corresponding network slice. This operation may start with the PDU session creation. Mapping of PDU session parameters to underlay SST paths may be performed by a Session Management Function (SMF). SSI support may be added as an additional feature to the SMF, or directly performed by the CSCF, or as a CSCF extension to the SMF.

[0097] Further, the CSCF may be configured to monitor underlying transport path characteristics. If path characteristics are degraded, reassignment of the paths at the endpoints shall be performed. For all the affected PDU sessions (per slice or per sub-slice), degraded transport paths may be updated dynamically with similar alternate paths.

[0098] Further, for a 5G system (5GS), the CSCF may be integrated as part of the 5GS Service Based Interfaces in order to provide the flexibility to control the allocation of required characteristics among the end-to- end path during a 5GS signaling procedure (e.g. PDU Session Establishment).

[0099] Different management models can be supported in the context of ISAC network slicing. For instance, Network Slice as a Service (NSaaS), or Network Slices as Network Operator (NOP) internals may be used. NSaaS may be offered by a service provider to its customers in the form of a communication service. This service allows the customer to use and optionally manage the network slice instance.

[0100] For NOP internals, network slices are not part of a service provider’s service portfolio. This deployment may be used for internal network optimization purposes (e.g., beamforming).

[0101] FIG. 5 shows a diagram of a method 500 of this disclosure. The method 500 comprises the following steps: step 501: creating, by a network device, a network slice for integrated sensing and communication; and

[0102] (optional) step 502: creating, by the network device, a plurality of network sub-slices of the network slice comprising a first network sub-slice for sensing and a second network sub-slice for communication.

[0103] It is noted that the steps of method 500 may share the same functions and details from the perspective of FIGs. 1-4 described above.

[0104] FIG. 6 shows a diagram of a method 600 of this disclosure. The method 600 comprises the following steps: step 601: managing, by a network function entity, communication data and / or sensing data through a network slice for integrated sensing and communication.

[0105] It is noted that the step of method 600 may share the same functions and details from the perspective of FIGs. 3A, 3B, and 4 described above.

[0106] FIG. 7 shows an application scenario of this disclosure. FIG. 7 illustrates a 6G communication system comprising a 6G RAN, edge network, transport network, 6G CN, and cloud network.

[0107] The 6G RAN may comprise a base station equipped with an ISAC RF board that is capable of performing both communication and sensing as ISAC services.

[0108] For managing the ISAC traffic, a single network slice, i.e., ISAC network slice instance (NSI) is created, e.g., by an NSMF (not shown in FIG. 7). The ISAC NSI covers multiple sub-nets of the 6G system. In each sub-net (e.g., the cloud network, 6G CN, transport network, edge network, and 6G RAN), the ISAC NSI may be split into a corresponding network slice subnet instance (NSSI). According to this disclosure, the ISAC NSI may further comprise at least two network sub-slices: a first network sub-slice for sensing and a second network sub-slice for communication. It is noted that the notion of network sub-slice of this disclosure is different from the notion of network slice subnet instance. In network slicing, the NSSI forms part of the overall network slice instance that expands over different sub-nets (e.g., RAN, CN, TN etc). Examples include a RAN, core and transport NSSI. The network sub-slice of this disclosure is used to differentiate data transmitted through the network slice into a further granularity, in order to allow a single network slice to fulfill the transmission requirements of different types of traffic. That is, the multiple network sub-slices may be used to deliver different types of data in a single network slice. One or more CSCFs may be used to manage the ISAC traffic based on the created ISAC network slice. The CSCF may be located in various places in the 6G system. For instance, the 6G CN may comprise a centralized CSCF. The 6G RAN and the edge network may be built as a so-called “Cloud RAN” (C- RAN). The main concept of C-RAN is to decouple the BaseBand Units (BBU) and the Remote Radio Heads (RRH), and place the BBUs in an edge network (or BBU pools) for centralized processing. In this case, one or more distributed CSCFs may be located in the 6G RAN and / or edge network.

[0109] Communication and sensing data may be needed at different sub-networks of the 6G system and thus, shall be accessible at different parts of the architecture, including third-party. Accordingly, the sensing and communication data may be identified using a corresponding sub-slice identifier (SSI). In the meantime, the sensing and the communication data may still be streamed within the same ISAC network slice.

[0110] The CSCF is configured to manage (or control) the sensing and communication data that is “piped” through the ISAC network slice.

[0111] The communication and sensing data may have different plane options:

[0112] User Plane: the endpoint is represented by one or more User Plane Function (UPF)(s). The service consuming the User data is part of the Data Network;

[0113] Control Plane: the endpoint is one or more network functions (NFs) in the CN and / or RAN. There is no interaction with the data network, only device data are treated; and

[0114] Data Plane: device data is linked with the control entities and / or control functionalities in the data network.

[0115] In summation, this disclosure proposes to create a single network slice for ISAC. Further, the single network slice may comprise a first network sub-slice for sensing and a second network sub-slice for communication. The two sub-slices may be used to distinguish traffic of two different types that belong to the same ISAC network slice. A centralized network function entity, or multiple distributed network function entities may be adapted to manage the ISAC traffic through the entire system. In this way, an efficient management of ISAC traffic along the entire system can be achieved. Based on the sub-slices for sensing and communication, flexible network function positioning may be achieved. For instance, in a disaggregated manner, the sensing and communication data may have different routes and end points on top of the same logical infrastructure. In a monolithic manner, the communication and sensing data exploits may share the same logical infrastructure and endpoints.

[0116] Further, service isolation, resource provisioning, and QoS of ISAC applications may be improved. It is also possible to expose ISAC capabilities to third parties at different granularities.

[0117] It is noted that the devices and entities in the present disclosure may comprise processing circuitry configured to perform, conduct or initiate the various operations of the device / entity described herein, respectively. The processing circuitry may comprise hardware and software. The hardware may comprise analog circuitry or digital circuitry, or both analog and digital circuitry. The digital circuitry may comprise components such as application-specific integrated circuits (ASICs), field-programmable arrays (FPGAs), digital signal processors (DSPs), or multi-purpose processors. Optionally, the processing circuitry comprises one or more processors (or chipsets) and a non-transitory memory connected to the one or more processors. The non-transitory memory may carry executable program code which, when executed by the one or more processors, causes the device to perform, conduct or initiate the operations or methods described herein, respectively.

[0118] The present disclosure has been described in conjunction with various aspects as examples as well as implementations. However, other variations can be understood and effected by those persons skilled in the art and practicing the claimed subject matter, from the studies of the drawings, this disclosure and the independent claims. In the claims as well as in the description the word “comprising” does not exclude other elements or steps and the indefinite article “a” or “an” does not exclude a plurality. A single element or another unit may fulfill the functions of several entities or items recited in the claims. The mere fact that certain measures are recited in the mutual different dependent claims does not indicate that a combination of these measures cannot be used in an advantageous implementation.

Claims

CLAIMS1. A network device (100) configured to create a network slice (110) for integrated sensing and communication.

2. The network device (100) according to claim 1, wherein the network device (100) is further configured to create a plurality of network sub-slices (111, 113) of the network slice (110).

3. The network device (100) according to claim 2, wherein the plurality of network sub-slices comprises a first network sub-slice (111) for sensing and a second network sub-slice (113) for communication.

4. The network device (100) according to any one of claims 1 to 3, wherein the network slice (110) is associated with identification information (200), wherein the identification information (200) comprises slice / service type information (210) indicative that the network slice is for integrated sensing and communication.

5. The network device (100) according to claim 4, wherein the identification information (200) comprises a service differentiator field (220) identifying the network slice.

6. The network device (100) according to any one of claims 1 to 5, wherein the network device (100) is further configured to generate a first sub-slice identifier, and a second sub-slice identifier, wherein the first sub-slice identifier is indicative of a first type of traffic belonging to the first network sub-slice, and the second sub-slice identifier is indicative of a second type of traffic belonging to the second network sub-slice.

7. The network device (100) according to claim 6 dependent on claim 5, wherein the first sub-slice identifier and the second sub-slice identifier are embedded in the service differentiator field (220).

8. The network device (100) according to claim 6 or 7, wherein the first sub-slice identifier and the second sub-slice identifier are indicated by virtual local area network, VLAN, tagging.

9. A network function entity (310; 320; 330) configured to manage communication data and / or sensing data through a network slice for integrated sensing and communication.

10. The network function entity (310; 320; 330) according to claim 9, wherein the network function entity (310; 320; 330) is further configured to:differentiate sensing data of different types; and / or differentiate communication data of different types.

11. The network function entity (310; 320; 330) according to claim 9 or 10, wherein the network function entity is further configured to: collect sensing data from radio access network; and estimate a user equipment, UE, location based on the collected sensing data.

12. The network function entity (310; 320; 330) according to any one of claims 9 to 11, wherein the network function entity is further configured to: collect sensing data of one or more base stations, optionally from an access and mobility management function; and construct an environmental mapping based on the collected sensing data.

13. The network function entity (310; 320; 330) according to any one of claims 9 to 12, wherein the network function entity is further configured to perform one or more of: objection detection;3D measurement; providing sensing data to one or more network functions; and providing broadcast sensing assistance to one or more UEs.

14. The network function entity (310) according to any one of claims 9 to 13, wherein the network function entity (310) is at least a part of a core network device.

15. The network function entity (320; 330) according to any one of claims 9 to 14, wherein the network function entity (320; 330) is at least a part of a device for an edge network or a radio access network.

16. A system comprises at least one network device (100) according to any one of claims 1 to 8, and at least one network function entity (310; 320; 330) according to any one of claims 9 to 15.

17. A method (500) comprising: creating (501), by a network device, a network slice for integrated sensing and communication.

18. A method (600) comprising: managing (601), by a network function entity, communication data and / or sensing data through a network slice for integrated sensing and communication.

19. A computer program comprising instructions which, when the program is executed by a computer, cause the computer to perform the method according to claims 17 or 18.

Images